-
Notifications
You must be signed in to change notification settings - Fork 15
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
unexpected end of section #1480
Comments
That is an allmodconfig + ThinLTO build. |
ah, right, the "kconfig" is printed from the build.json (otherwise the config/build name is cutoff in github UI for me). |
Reported upstream: https://reviews.llvm.org/D105169#3116810 I believe current ToT should be fine, as it has a revert of that change: llvm/llvm-project@fd9b099 |
Closing as the problematic commit has been reverted and we have a reproducer so that it is fixed in the next revision. |
This is likely going to come back so I am preemptively reopening this. On Monday, I will try to distill down some of the warnings I see and start a thread with Josh and Peter upstream to see if there is any way to minimize the impact of this change in |
|
I am pretty sure all of these were a result of |
via https://github.com/ClangBuiltLinux/continuous-integration2/runs/3927890481?check_suite_focus=true:
I'm surprised to see
.lto.o
files as part of allmodconfig. Isn't LTO disabled for allmodconfig?The text was updated successfully, but these errors were encountered: