On 3/25/25 8:24 AM, Richard Biener wrote:
The following resolves missing reservations for DFmode *movdf_internal
loads and stores, visible as 'nothing' in -fsched-verbose=2 dumps.
Bootstrap and regtest running on x86_64-unknown-linux-gnu.
PR target/119010
* config/i386/zn4zn5
On 3/25/25 05:12, Tobias Burnus wrote:
On August 24, 2024 Tobias Burnus wrote:
[...] it documents the code added at "[patch][rfc] libgomp: Add OpenMP
interop support to nvptx + gcn plugin",
https://gcc.gnu.org/pipermail/gcc-patches/2024-August/661207.html
Quite some time has passed and those
Hi,
On Tue, Mar 25 2025, Sam James wrote:
> r15-7961-gdc47161c1f32c3 fixes a typo in ao_compare::compare_ao_refs
> but there wasn't a testcase available at the time. Now there is.
>
> Thanks to Andrew for the testcase.
>
> gcc/testsuite/ChangeLog:
> PR testsuite/119382
>
> * gcc.dg/ipa
> The imov and imovx classified stores miss reservations in the znver4/5
> pipeline description. The following adds them.
>
> Bootstrap and regtest pending on x86_64-unknown-linux-gnu.
>
> OK?
>
> PR target/119010
> * config/i386/zn4zn5.md (znver4_imov_double_store,
> znver5_i
> On Tue, 25 Mar 2025, Richard Biener wrote:
>
> > The following resolves missing reservations for DFmode *movdf_internal
> > loads and stores, visible as 'nothing' in -fsched-verbose=2 dumps.
> >
> > Bootstrap and regtest running on x86_64-unknown-linux-gnu.
>
> The alternative for the larger s
On Tue, Mar 25, 2025 at 11:06:05AM -0400, Jason Merrill wrote:
> > The patch introduces 2 new warnings.
> > -Wmusttail-local-addr
> > which is turn on by default and warns for the always dumb cases of passing
> > an address of a local variable or parameter to musttail call's argument.
>
> I don't
Hi!
As discussed here and in bugzilla, [[clang::musttail]] attribute in clang
not just strongly asks for tail call or error, but changes behavior.
To quote:
https://clang.llvm.org/docs/AttributeReference.html#musttail
"The lifetimes of all local variables and function parameters end immediately
be
More details: Alignment with llvm
(https://github.com/llvm/llvm-project/pull/131592)
BRs,
Lin
> -Original Message-
> From: Hu, Lin1
> Sent: Tuesday, March 25, 2025 4:10 PM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com
> Subject: [PATCH v2] i386: Add "s_" as Satura
On Tue, Mar 25, 2025 at 08:47:49AM +0100, Richard Biener wrote:
> On Mon, 24 Mar 2025, Jakub Jelinek wrote:
>
> > On Mon, Mar 24, 2025 at 10:55:44PM +0100, Jakub Jelinek wrote:
> > > If it was HOST_WIDE_INT_MAX + (size_t) 1 to ~(size_t) 0, previously it
> > > would
> > > be false and now is false
On 3/21/25 9:00 AM, Jakub Jelinek wrote:
Hi!
Here is an updated version of Surya's PR116028 fix from August, which got
reverted because it caused bootstrap failures on aarch64, later on bootstrap
comparison errors there as well and problems on other targets as well.
The changes compared to the
On 3/25/25 11:18, Thomas Schwinge wrote:
Hi Tom!
On 2022-03-22T14:41:46+0100, Tom de Vries via Gcc-patches
wrote:
Starting with ptx isa version 6.3, a ptx directive .alias is available.
Regarding the following item specifically:
Unreferenced aliases are not emitted (these can occur f.i. w
Hi Tom!
On 2022-03-22T14:41:46+0100, Tom de Vries via Gcc-patches
wrote:
> Starting with ptx isa version 6.3, a ptx directive .alias is available.
Regarding the following item specifically:
> Unreferenced aliases are not emitted (these can occur f.i. when inlining a
> call to an alias). This
On Mon, Mar 24, 2025 at 09:50:26AM -0700, Andi Kleen wrote:
> gcc/ChangeLog:
>
> PR gcov-profile/118442
> * cfg-flags.def (MUSTTAIL):
> * profile.cc (branch_prob):
> * tree-cfg.cc (gimple_flow_call_edges_add):
Descriptions missing.
> --- a/gcc/cfg-flags.def
> +++ b/gcc/cf
Sorry Kito, that we're having so much back and forth here, it's not my
intention to block anything (not that I could anyway). I just want to
make sure I properly understand the rationale (or the spec, rather).
Oh, ok, I got the point why you confused on this, the new condition is
little bit `i
- "TARGET_VECTOR"
+ "TARGET_VECTOR && 0"
Would you mind adding a comment here before committing, maybe even reference
the PR? Not that we want to keep this around for long anyway but just to make
sure :)
--
Regards
Robin
On Mon, Mar 24, 2025 at 5:11 PM Iain Sandoe wrote:
>
> This adds support for target-configured specs for library-specific
> specs. Initially, we will use this for the libm (but it's then
> required by other pending patches).
>
> The first patch adds to the driver and the library, the second makes
This was fixed last year by r15-2409-g017e3f89b081e4 (and backports), so
just add the testcase.
libstdc++-v3/ChangeLog:
PR libstdc++/118699
* testsuite/27_io/filesystem/operations/copy.cc: Check copying a
file to a directory.
---
Tested x86_64-linux and x86_64-mingw-w64.
From: Philip Herron
gcc/rust/ChangeLog:
* hir/rust-hir-dump.cc (Dump::visit): add guards
Signed-off-by: Philip Herron
---
gcc/rust/hir/rust-hir-dump.cc | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/gcc/rust/hir/rust-hir-dump.cc b/gcc/rust/hir/rust-hi
LWG 4229 points out that the std::ranges::to wording refers to class
types, but I added an assertion using std::is_class_v which only allows
non-union class types. LWG consensus is that unions should be allowed,
so this additionally uses std::is_union_v.
libstdc++-v3/ChangeLog:
* include/
On 25/03/2025 12:05, Tobias Burnus wrote:
A GCC 15 regression turned out to be a bug in Newlib related to
undefined behavior that just started to trigger in some cases.
As it is now fixed, it makes IMHO sense to mention that Newlib
commit in GCC's install documentation for AMD GPUs.
Comments, s
101 - 120 of 120 matches
Mail list logo