This is an archive of the discontinued LLVM Phabricator instance.

[Clang][Test]: Remaining "lld-link2" -> "lld-link"
ClosedPublic

Authored by Ericson2314 on Nov 3 2019, 7:34 AM.

Details

Reviewers
compnerd
rnk
Summary

No idea why these are still here.

Event Timeline

Ericson2314 created this revision.Nov 3 2019, 7:34 AM
Herald added a project: Restricted Project. · View Herald TranscriptNov 3 2019, 7:34 AM
Herald added a subscriber: cfe-commits. · View Herald Transcript
mstorsjo added a subscriber: mstorsjo.
compnerd accepted this revision.Nov 4 2019, 2:04 PM

Seems like a good idea since lld link2 has been made into lld link for a while now.

This revision is now accepted and ready to land.Nov 4 2019, 2:04 PM

I am curious, how did this work since there is no longer an lld-link2? Were these tests failing or not being run?

rnk accepted this revision.Nov 5 2019, 10:18 AM

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?

rnk added a comment.Feb 5 2020, 5:14 PM

I applied this locally, but the test doesn't pass. I can look into it tomorrow.

rnk added a comment.Feb 5 2020, 5:15 PM

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.

@rnk can we close this?

Herald added a project: Restricted Project. · View Herald TranscriptSep 21 2023, 9:11 AM
rnk closed this revision.Sep 21 2023, 9:27 AM
rnk added a subscriber: MaskRay.

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.