-
Notifications
You must be signed in to change notification settings - Fork 98
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
Seek for rebase #1140
Comments
I'll look into it. |
I pushed a new rebase. |
@smeenai It seems this too recent commit is not included. Do we have a standard / policy of choosing a base commit to synchronize with? |
I picked a base commit from Tuesday, so we missed out by one day :) I can just run another rebase though, it should hopefully be pretty quick and painless given that I just performed one. Edited to add: we generally pick a base commit on the day we start the rebase, make sure it's in a good state (passed |
@smeenai thanks for all rebase work and getting our community happy to be living on the edge :D |
Pushed a new rebase. @seven-mile your work enabled us to get rid of a ClangIR-specific change we had to Targets.h, which is very nice :) |
Hi all!
I have the next question: when do you plan the next rebase?
The reason I'm asking is that the previous one was done in the moment when a bug existed in the trunk and it kind of affects ClangIR as well.
Reprocase:
clang tmp.c -O2 --target=aarch64-none-linux-gnu -c
(one may enable -fclangir as well, it doesn't change anything)This code fails with the weird error in the llvm's
DAGCombiner
I did not try to bisect to identify the exact commit in trunk, but the point is - the bug is already fixed, I checked it with the current
main
branch ofllvm-project
and it would be great if we do the rebasing one daycc @bcardosolopes
The text was updated successfully, but these errors were encountered: