-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
llvm: update to 19.1.7 and add import libs fix for LLD #23136
Conversation
lgtm. ok to merge despite it timing out? |
I had built each package in CLANG64 env before committing, so it should be fine, but if you want, I can just split it into two PRs. |
I think it's fine to just merge |
apply_git_patch_with_msg() { | ||
for _patch in "$@" | ||
do | ||
msg2 "Applying ${_patch}" | ||
patch -Nbp1 -i "${srcdir}/${_patch}" | ||
done | ||
} | ||
|
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.
This function looks exactly like the apply_patch_with_msg
function immediately above it. Is there some reason for another copy?
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.
Good point, this is a leftover.
At first I tried to apply the patch to a specific directory (lld/
) but git patches require -p2
so I created this helper. Then I found out it's not going to work because the patch modifies llvm/
and lld/
at once. And here comes my mistake for modifying the new helper instead of using the previous one.
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.
Created #23152
Fixes #21017