Mostly for compatibility reasons with link.exe this flag
makes sure we don't write a implib - not even when /implib
is also passed, that's how link.exe works.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lld/COFF/Options.td | ||
---|---|---|
60 | Thanks! Fixed. |
lld/COFF/Driver.cpp | ||
---|---|---|
1677 | nit: Variable arg is unused and causes a warning. Should this be using arg->getValue()? |
lld/COFF/Driver.cpp | ||
---|---|---|
1677 | I guess this should be args.hasArg(OPT_noimplib) instead. @thieta, what happens if the user specifies -noimplib -implib:otherfile.lib? Does the last argument win (i.e. we should use args.getLastArg(OPT_implib, OPT_noimplib) and see which one was set last, or is it the case that -noimplib always trumps -implib, regardless of their respective ordering? |
I'll take another pass after lunch - will verify what link does as well. If there is no change in functionality- can that be submitted as a NFC or should I open another review.
Yeah if it's just a NFC change getting rid of the warning, I'd say go ahead and push without review here.
I checked and they behave the same. I pushed a NFC for the warning here https://github.com/llvm/llvm-project/commit/837d16fb4c1cb00c5d0c72a0dff543f0bd5ff770
nit: Variable arg is unused and causes a warning. Should this be using arg->getValue()?