Follows up on commit cd5d5ce235081005173566c99c592550021de058 by
additionally ignoring relative paths ending in "lto-wrapper.exe" as
can be the case for GCC cross-compiled for Windows.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Seems fine to me but can you also update lld/test/ELF/lto-plugin-ignore.s to test this case?
@tejohnson, Thanks for the review! I'm a newbie here, not sure that I have the ability to commit or see this all the way through. Is there any further action required on my part?
I can commit it for you today. If you plan to become an LLVM developer see the instructions here to obtain commit access: https://llvm.org/docs/Contributing.html#for-developers-to-commit-changes-from-git
@tejohnson, forgive my ignorance - Will this be included in an upcoming release, and if so do you know when that would be? Any chance it could be back-ported to the 15.0.x release track?
I think by default it would be released with 16.x, but it could presumably be backported to the next 15.0.x release.
I haven't done this before, but it looks like to get this backported to 15.0.5 you could follow the instructions at https://llvm.org/docs/GitHub.html to create an issue here:
https://github.com/llvm/llvm-project/milestone/16
and then add the necessary cherrypick command to it as described in the instructions. Is that something you can try? I haven't done it myself but let me know if you run into issues.