lld-link /lib allows creating mixed-bitness lib files; lib.exe doesn't allow that

[nico]

Bugzilla Link	38782
Resolution	FIXED
Resolved on	Jun 07, 2019 18:36
Version	unspecified
OS	Windows NT
Blocks	#38313
CC	@pcc

Extended Description

C:\src\chrome\src>type f1.c
void f1() {}

C:\src\chrome\src>type f2.c
void f2() {}

C:\src\chrome\src>"third_party\llvm-build\Release+Asserts\bin\clang-cl.exe" -m64 -c f1.c

C:\src\chrome\src>"third_party\llvm-build\Release+Asserts\bin\clang-cl.exe" -m32 -c f2.c

C:\src\chrome\src>lib /out:foo.lib f1.obj f2.obj
Microsoft (R) Library Manager Version 14.14.26428.1
Copyright (C) Microsoft Corporation. All rights reserved.

f2.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'

C:\src\chrome\src>"third_party\llvm-build\Release+Asserts\bin\lld-link.exe" /lib /out:foo.lib f2.obj f1.obj

Not allowing this seems like a good choice.

[nico]

https://reviews.llvm.org/D62913

[nico]

Fixed in r362798. Filed bug 42180 with some related follow-up issues I noticed while working on that.

[nico]

mentioned in issue #38313