With 6a75496836ea14bcfd2f4b59d35a1cad4ac58cee, these two options are no longer
forwarded to GCC. This patch restores the original behavior.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM.
clang/test/Driver/gcc_forward.c | ||
---|---|---|
5 | Moving nostartfiles before nostdlib to keep an alphabetical order. Similarly, specs can precede static. |
Can D83648 be closed now?
BTW, can you describe a bit about your use cases? Forwarding options to gcc does not seem common nowadays...
Yes, I have closed it.
BTW, can you describe a bit about your use cases? Forwarding options to gcc does not seem common nowadays...
It's probably not used very common, but we do have some baremetal use cases still relying on these flags to be propagated to GCC.
clang/test/Driver/gcc_forward.c | ||
---|---|---|
5 | Thanks for pointing this out. I did not realize the flags are ordered. Will update the patch shortly. |
LGTM.
It's probably not used very common, but we do have some baremetal use cases still relying on these flags to be propagated to GCC.
Thanks for the explanation! (Though I think in these cases calling ld or ld.lld directly might be better?)
And apologies about the friction but I hope the current behavior is better than the previous whether many unrelated options can be forwarded and many can cause warnings on GCC side.
No worries. Hopefully, these flags are the only outliers. Thanks for reviewing the patch!
Moving nostartfiles before nostdlib to keep an alphabetical order.
Similarly, specs can precede static.