rorth wrote:
> Hi, since we are wrapping up LLVM 19.1.0 we are very strict with the fixes we
> pick at this point. Can you please respond to the following questions to help
> me understand if this has to be included in the final release or not.
I guess it's best for @petrhosek to make the fina
https://github.com/rorth edited https://github.com/llvm/llvm-project/pull/107362
___
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/rorth created
https://github.com/llvm/llvm-project/pull/107362
As detailed in Issue #101667, two `profile` tests `FAIL` on 32-bit SPARC, both
Linux/sparc64 and Solaris/sparcv9 (where the tests work when enabled):
```
Profile-sparc :: ContinuousSyncMode/runtime-counter-reloc
https://github.com/rorth milestoned
https://github.com/llvm/llvm-project/pull/107362
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
rorth wrote:
It's difficult: on one hand it fixes a Solaris/SPARC build failure. On the
other, it's said to cause problems for an out-of-tree z/OS port.
Unfortunately, the developers refuse to publish their code, so it's almost
impossible to reason about that code.
https://github.com/llvm/l
Author: Rainer Orth
Date: 2024-08-20T13:34:13+02:00
New Revision: 9301cd5b57c09214256edf19753e2e047a5b5f91
URL:
https://github.com/llvm/llvm-project/commit/9301cd5b57c09214256edf19753e2e047a5b5f91
DIFF:
https://github.com/llvm/llvm-project/commit/9301cd5b57c09214256edf19753e2e047a5b5f91.diff
L
rorth wrote:
The Solaris/sparcv9 build just completed successfully: no regressions relative
to rc2.
https://github.com/llvm/llvm-project/pull/104916
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin
rorth wrote:
This can now be closed: one part (PR #101012) has already been merged and the
necessary rest is now PR #104916.
https://github.com/llvm/llvm-project/pull/101236
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https
https://github.com/rorth closed https://github.com/llvm/llvm-project/pull/101236
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
rorth wrote:
I know, that's how I did it for the original PR. However, when it turned out
16e9bb9cd7f50ae2ec7f29a80bc3b95f528bfdbf was necessary too to unbreak the
Solaris/sparcv9 build, I added a separate cherry pick just for that one. I
guess I should just have closed the original PR and a
https://github.com/rorth edited https://github.com/llvm/llvm-project/pull/101236
___
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/rorth created
https://github.com/llvm/llvm-project/pull/101236
Backport of fcd6bd5587cc376cd8f43b60d1c7d61fdfe0f535 and
16e9bb9cd7f50ae2ec7f29a80bc3b95f528bfdbf to `release/19.x` branch.
>From 7d97041c217bcb4b04cacb3a5d17285f8b241a88 Mon Sep 17 00:00:00 2001
From: Rainer Ort
https://github.com/rorth milestoned
https://github.com/llvm/llvm-project/pull/101236
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
rorth wrote:
Yes: there have been no issues on `main` whatsoever, so it should be safe
enough.
https://github.com/llvm/llvm-project/pull/100322
___
llvm-branch-commits mailing list
llvm-branch-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mail
rorth wrote:
I guess it's reasonably safe, though as patch author I may be biased. The
`LD_LIBRARY_PATH*` part will only affect x86 and has been tested on both
Solaris and Linux. The current `RPATH` handling is plain wrong, so no harm
here.
Maybe give it a couple of days soak time on `main`
rorth wrote:
> @tstellar What do you think about merging this PR to the release branch?
I thing this would be very useful: we already have two Issues filed for this
problem, and `test-release.sh` is probably almost exclusively exercised during
release testing/building.
The risk should be limi
16 matches
Mail list logo