No idea why these are still here.
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 40450 Build 40557: arc lint + arc unit
Event Timeline
I am curious, how did this work since there is no longer an lld-link2? Were these tests failing or not being run?
These tests don't actually need to run the linker. They were constructing a command line to run "lld-link2", which didn't exist. Actually performing the link would've failed.
Do I need to do anything more with this, or will somebody else just merge this at come point?
Oh, here's the linker it has found:
$ find ../clang/ -iname '*lld-link2' ../clang/test/Driver/Inputs/Windows/ARM/8.1/usr/bin/ld.lld-link2
So this is truly a test of the ld.otherlinker feature pattern, not some special case driver feature. I guess we should leave the test alone.
Closing, we left the test alone, it still uses -fuse-ld=lld-link2. Perhaps in the future we should reconsider this, but that's how things stand now, and we aren't going to land this patch as is. + @MaskRay , who has thought about -fuse-ld= semantics.
So this is truly a test of the ld.otherlinker feature pattern, not some special case driver feature. I guess we should leave the test alone.
Closing, we left the test alone, it still uses -fuse-ld=lld-link2. Perhaps in the future we should reconsider this, but that's how things stand now, and we aren't going to land this patch as is. + @MaskRay , who has thought about -fuse-ld= semantics.
Yes, we can leave the test alone. The ld.<name> convention is mainly for ELF.