search

Quuxplusone / LLVMBugzillaTest

0 stars 0 forks source link

ld64.lld does not handle -v (print linker information) #42691

Closed Quuxplusone closed 3 years ago

Quuxplusone commented 5 years ago
Bugzilla Link PR43721
Status RESOLVED FIXED
Importance P normal
Reported by Boris Kolpackov (boris@codesynthesis.com)
Reported on 2019-10-19 08:08:24 -0700
Last modified on 2020-12-22 19:12:24 -0800
Version unspecified
Hardware PC MacOS X
CC llvm-bugs@lists.llvm.org, nicolasweber@gmx.de
Fixed by commit(s) http://reviews.llvm.org/rG77fb45e59e49d25fbc57854b62599ae24aa2c4c9
Attachments
Blocks
Blocked by
See also 
ld64.lld as of version 9.0.0 does not handle -v (nor --version). In contrast,
Apple's ld64 -v prints:

@(#)PROGRAM:ld  PROJECT:ld64-450.3
BUILD 18:45:16 Apr  4 2019
configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386
x86_64 x86_64h armv6m armv7k armv7m armv7em
LTO support using: LLVM version 10.0.1, (clang-1001.0.46.4) (static support for
22, runtime is 22)
TAPI support using: Apple TAPI version 10.0.1 (tapi-1001.0.4.1)

It would be nice if this option was recognized and at least something basic
like "LLD X.Y.Z" was printed (similar to other lld driver scripts which all
recognize --version).
Quuxplusone commented 3 years ago

ld64.lld is mostly dead, but there's a replacement in progress that will become ld64.lld in time. Until then, it's available as ld64.lld.darwinnew. It has a working -v, and in http://reviews.llvm.org/rG77fb45e59e49d25fbc57854b62599ae24aa2c4c9 we added a --version flag too. So this is a fixed as it's going to get.