https://github.com/Patryk27 closed
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Patryk27 wrote:
Ah, I see - so the only remaining option is for Zig to apply the patch on its
own side, it seems.
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.ll
Patryk27 wrote:
Not sure what's the next step (can't merge it myself here :-P) - cc @nikic?
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/
Patryk27 wrote:
Alright, backported!
I changed the logic from `emit relocations only for large jumps` to `emit
relocations always`, which - pleasantly enough - means we don't have to
backport #118015 per se (since linker is able to do this magic-wrapping-thingie
on its own).
As for testing,
https://github.com/Patryk27 edited
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/Patryk27 edited
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/Patryk27 updated
https://github.com/llvm/llvm-project/pull/125081
Sorry, this diff is unavailable.
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-co
Patryk27 wrote:
I see, I’ll do my best, then! Let’s keep this pull request open and I’ll report
back.
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-b
Patryk27 wrote:
Ah, that tracks! Is there a timeline for getting rustc to LLVM 20?
Also, @alexrp - is Zig planning on upgrading soon as well? If not, I can try to
prepare a different backport, one that doesn't require modifying
`shouldForceRelocation()` (not 100% sure that's possible, but I ca
Patryk27 wrote:
> because the changes to shouldForceRelocation are ABI-breaking.
Huh, interesting - out of curiosity, why do they break the ABI if those jumps
are local to functions?
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-co
https://github.com/Patryk27 edited
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
https://github.com/Patryk27 milestoned
https://github.com/llvm/llvm-project/pull/125081
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Patryk27 wrote:
A little context - I'd like to get it merged to 19.x, so that I can pull it to
rustc - it fixes a minor codegen issue within the AVR backend, which causes
some firmwares not to get compiled, crashing LLVM.
https://github.com/llvm/llvm-project/pull/113969
___
Patryk27 wrote:
cc @benshi001 / @aykevl 🙂
https://github.com/llvm/llvm-project/pull/106993
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
Patryk27 wrote:
> Is this PR a fix for a regression or a critical issue?
It's a fix for critical issue within the AVR codegen which causes it to
generate invalid binaries and/or crash llvm (depending on which concrete code
path is taken).
It was spotted downstream in Rust, https://github.com/
Patryk27 wrote:
@benshi001 / @aykevl, is there something we can do to push this forward or it's
waiting for someone else?
https://github.com/llvm/llvm-project/pull/106993
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://
Patryk27 wrote:
Thanks!
We need both
https://github.com/llvm/llvm-project/commit/86a60e7f1e8f361f84ccb6e656e848dd4fbaa713
and
https://github.com/llvm/llvm-project/pull/106739/commits/af15b6dff67e7aa1997ae0294e0bc01a3fe5a438;
the original issue was https://github.com/llvm/llvm-project/pull/1
Patryk27 wrote:
Ah, I've just checked and I can't set miilestones, though :-//
https://github.com/llvm/llvm-project/pull/106729
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llv
Patryk27 wrote:
Can I somehow help here? Usually I'd cherry-pick changes from
https://github.com/llvm/llvm-project/pull/106739 into here myself, but since
I'm not the author of the pull request, I can't modify it 👀
(and we'd probably like to avoid having two separate backport pull requests to
Patryk27 wrote:
cc @benshi001 - not sure if you can approve backports as well, but maybe you'll
know who to ping if so 😅
https://github.com/llvm/llvm-project/pull/85422
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://l
https://github.com/Patryk27 created
https://github.com/llvm/llvm-project/pull/85422
Backporting #85277, at the request of
https://github.com/rust-lang/llvm-project/pull/171#issuecomment-143797.
>From bb49a9f39c5643ed7503c78b56bfc28388e21709 Mon Sep 17 00:00:00 2001
From: Patryk Wychowaniec
21 matches
Mail list logo
