-
Notifications
You must be signed in to change notification settings - Fork 14.4k
[PassBuilder][FatLTO] Expose FatLTO pipeline via pipeline string #146048
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Expose the FatLTO pipeline via `-passes="fatlto-pre-link<Ox>"`, similar to all the other optimization pipelines. This is to allow reproducing it outside clang. (Possibly also useful for C API users.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I wish I had thought of this earlier.
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/185/builds/21136 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/175/builds/21273 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/137/builds/21339 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/33/builds/19263 Here is the relevant piece of the build log for the reference
|
LLVM Buildbot has detected a new failure on builder Full details are available at: https://lab.llvm.org/buildbot/#/builders/16/builds/21783 Here is the relevant piece of the build log for the reference
|
With EXPENSIVE_CHECKS the fatlto.ll testcase fails because there is an unexpected
I suppose a bit more relaxation is needed. |
To fix test failure with expensive checks reports at: #146048 (comment)
@mikaelholmen Thanks, I believe 102c22c should fix it. |
Yep, thanks! |
To fix test failure with expensive checks reports at: llvm/llvm-project#146048 (comment)
…m#146048) Expose the FatLTO pipeline via `-passes="fatlto-pre-link<Ox>"`, similar to all the other optimization pipelines. This is to allow reproducing it outside clang. (Possibly also useful for C API users.)
To fix test failure with expensive checks reports at: llvm#146048 (comment)
…m#146048) Expose the FatLTO pipeline via `-passes="fatlto-pre-link<Ox>"`, similar to all the other optimization pipelines. This is to allow reproducing it outside clang. (Possibly also useful for C API users.)
To fix test failure with expensive checks reports at: llvm#146048 (comment)
Expose the FatLTO pipeline via
-passes="fatlto-pre-link<Ox>"
, similar to all the other optimization pipelines. This is to allow reproducing it outside clang. (Possibly also useful for C API users.)