Branch content is swapped.
rend3r opened this issue · comments
Branch "thirdparty-windows-amd64" contains i386-win32-tcc.exe
thirdparty-windows-i386 contains x86_64-win32-tcc.exe
#0 19:12:35 ᛋ thirdparty-windows-amd64 /v/vnew/thirdparty/tcc❱file tcc.exe
tcc.exe: PE32+ executable (console) x86-64 (stripped to external PDB), for MS Windows
#0 19:12:44 ᛋ thirdparty-windows-amd64 /v/vnew/thirdparty/tcc❱file i386-win32-tcc.exe
i386-win32-tcc.exe: PE32+ executable (console) x86-64 (stripped to external PDB), for MS Windows
#0 19:12:51 ᛋ thirdparty-windows-amd64 /v/vnew/thirdparty/tcc❱
#0 19:12:53 ᛋ thirdparty-windows-amd64 /v/vnew/thirdparty/tcc❱git co thirdparty-windows-i386
Branch 'thirdparty-windows-i386' set up to track remote branch 'thirdparty-windows-i386' from 'origin' by rebasing.
Switched to a new branch 'thirdparty-windows-i386'
#0 19:13:08 ᛋ thirdparty-windows-i386 /v/vnew/thirdparty/tcc❱
#0 19:13:09 ᛋ thirdparty-windows-i386 /v/vnew/thirdparty/tcc❱file tcc.exe
tcc.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
#0 19:13:12 ᛋ thirdparty-windows-i386 /v/vnew/thirdparty/tcc❱
#0 19:13:13 ᛋ thirdparty-windows-i386 /v/vnew/thirdparty/tcc❱file x86_64-win32-tcc.exe
x86_64-win32-tcc.exe: PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows
#0 19:13:18 ᛋ thirdparty-windows-i386 /v/vnew/thirdparty/tcc❱
Note that tcc.exe (the executable used by the v compiler) is the proper one - it is a 32bit one on branch thirdparty-windows-i386, and it is a 64bit one on branch thirdparty-windows-amd64
Oh, I see. File naming leads to misunderstooding.