Without the message, the compiler output can be very short, e.g.
as short as a `required from here`. If the output includes the
line of code that trigges the static_assert, the user might
interpret it as "must be a standard integer", which is incorrect,
because that term doesn't cover extended inte
While reading the compiler output of
make check-target-libstdc++-v3
for buggy code, e.g. cmp_equal(1.0, 1.0), the error message
was very short, and I saw no hint that neither of the two
template arguments weren't integers. Essentially, the trace
was:
1. my faulty line
2. required from he
On Mon, 26 May 2025 at 18:35, Christophe Lyon
wrote:
>
> We get lots of error messages when compiling arm_neon.h under
> e.g. -mcpu=cortex-m55, because Neon builtins are enabled only when
> !TARGET_HAVE_MVE. This has been the case since MVE support was
> introduced.
>
> This patch uses an approac
On Mon, 26 May 2025 at 18:14, Christophe Lyon
wrote:
>
> Remove #pragma GCC target ("arch=armv8.2-a+bf16") and preceding
> target and is thus useless.
I guess this should read:
Remove #pragma GCC target ("arch=armv8.2-a+bf16") since it matches the preceding
pragma GCC target and is thus useless.
-(define_expand "avg3_floor"
- [(set (match_operand: 0 "register_operand")
- (truncate:
-(ashiftrt:VWEXTI
- (plus:VWEXTI
- (sign_extend:VWEXTI
- (match_operand: 1 "register_operand"))
- (sign_extend:VWEXTI
- (match_operand: 2 "register_operand"))]
+(define_expan
Pushed to trunk :)
On Wed, May 21, 2025 at 2:35 AM Jeff Law wrote:
>
>
>
> On 5/19/25 12:48 AM, Kito Cheng wrote:
> > Hi Jin:
> >
> > Thanks for heads up:)
> >
> > Hi Jeff:
> >
> > I've rebased that on the trunk and everything seems right, do you think
> > it's OK for the trunk?
> Yea, let's get
This was noticed in the review of copy propagation for aggregates
patch, instead of checking for a NULL or a non-ssa name of vuse,
we should instead check if it the vuse is a default name and stop
then.
Bootstrapped and tested on x86_64-linux-gnu.
gcc/ChangeLog:
* tree-ssa-forwprop.cc (o
As part of the review of copy prop for aggregates, it was
mentioned there should be some statistics added, and I noticed
the memcpy->memset was missing the statistics too. So this adds
that.
gcc/ChangeLog:
* tree-ssa-forwprop.cc (optimize_memcpy_to_memset): Adds
statistics when th
On Wed, Nov 27, 2024 at 11:45:40AM -0500, Patrick Palka wrote:
> On Fri, 8 Nov 2024, Nathaniel Shead wrote:
>
> > Does this approach seem reasonable? I'm pretty sure that the way I've
> > handled the templating here is unideal but I'm not sure what a neat way
> > to do what I'm trying to do here
From: Pan Li
The signed avg_floor totally match the sematics of fixed point
rvv insn vaadd, within round down. Thus, leverage it directly
to implement the avf_floor.
The spec of RVV is somehow not that clear about the difference
between the float point and fixed point for the rounding that
disc
From: Pan Li
Add asm and run testcase for avg_floor vaadd implementation.
The below test suites are passed for this patch series.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/avg.h: New test.
* gcc.target/riscv/rvv/autovec/avg_dat
From: Pan Li
Some existing avg_floor test need updated due to change to
leverage vaadd.vv directly.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vls/avg-1.c: Update asm check
to vaadd.
* gcc.target/riscv/rvv/autovec/vls/avg-2.c: Ditto.
* gcc.target/ris
From: Pan Li
The spec of RVV is somehow not that clear about the difference
between the float point and fixed point for the rounding that
discard least-significant information.
For float point which is not two's complement, the "discard
least-significant information" indicates truncation round.
> > It's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119181
>
> Please mention that in the changelog. Also ...
Changed.
> Please put this condition in the set of conds we test in the else branch of
> ...
>
> > > /* Do not place the same access in the interleaving chain
> > > twice.
Ping^2
在 2025/5/13 下午2:06, Lulu Cheng 写道:
Ping?
在 2025/5/9 上午10:14, Lulu Cheng 写道:
From: ChengLulu
PR target/99217
gcc/ChangeLog:
* config/mips/mips.cc (mips_start_function_definition):
Implements the functionality of '-fpatchable-function-entry='.
(mips_print_patchable_fun
On 5/26/25 01:18, Robin Dapp wrote:
>> 2. OK'ish: A bunch of testcases see more reads/writes as PRE of redundant
>> read/writes is punted to later passes which obviously needs more work.
>>
>> 3. NOK: We loose the ability to instrument local RM writes - especially in
>> the
>> testsuite.
>> e.g.
Hi Homza.
> On 26 May 2025, at 7:48 pm, Jan Hubicka wrote:
>
> External email: Use caution opening links or attachments
>
>
>>
>>
>>> On 26 May 2025, at 5:34 pm, Jan Hubicka wrote:
>>>
>>> External email: Use caution opening links or attachments
>>>
>>>
>>> Hi,
>>> also, please, can you
On Mon, May 26, 2025 at 1:40 PM Andrew Pinski wrote:
>
> On Mon, May 26, 2025 at 5:36 AM Richard Biener
> wrote:
> >
> > On Sun, May 18, 2025 at 10:58 PM Andrew Pinski
> > wrote:
> > >
> > > This implements a simple copy propagation for aggregates in the similar
> > > fashion as we already do f
On Mon, May 26, 2025 at 5:36 AM Richard Biener
wrote:
>
> On Sun, May 18, 2025 at 10:58 PM Andrew Pinski
> wrote:
> >
> > This implements a simple copy propagation for aggregates in the similar
> > fashion as we already do for copy prop of zeroing.
> >
> > Right now this only looks at the previo
On May 26, 2025, Xi Ruoyao wrote:
> gcc/testsuite/ChangeLog:
> * lib/target-supports-dg.exp (dg-do-if): Pass the line number
> to
> dg-do.
Thanks! I support that fix, FWIW.
Indeed, an identical fix was included (but remains unreviewed) in
https://gcc.gnu.org/pipermail/gcc-patches/
On 5/26/25 18:17, Tomasz Kaminski wrote:
On Mon, May 26, 2025 at 4:15 PM Luc Grosheintz
wrote:
Implements the parts of layout_left that don't depend on any of the
other layouts.
libstdc++-v3/ChangeLog:
* include/std/mdspan (layout_left): New class.
* src/c++23/std.cc.in:
Am 26.05.25 um 18:36 schrieb Steve Kargl:
On Mon, May 26, 2025 at 09:30:59AM +, Yuao Ma wrote:
Hi Steve,
I looked at the patch in a bit more detail, and
I am not thrilled with large-scale whitespace
changes mingled with functional changes. It makes
the patch harder to read and review.
I'
Committed as r16-883-g5d6ed6d604ff94.
Silence errors when the error supports nvptx offloading.
Seehttps://gcc.gnu.org/PR118694 (esp. comment 9) why we
cannot easily nesting silence the error.
(Short answer: 'target' call is different if teams is present
but that's only known when processing the
Hi All,
The following patch has been bootstrapped and regtested on powerpc64le-linux.
After r12-5752-gd08236359eb229, a new bif infrastructure was introduced
which stopped using opaque vector types (e.g. opaque_V4SI_type_node)
for overloaded built-in functions, which led to incorrect and
misleadi
Ok, I'll give it another try.
Trying to use the same approach for targets using gnu.ver and others
thought, seems more reasonable to me.
François
On 22/05/2025 09:28, Jonathan Wakely wrote:
On Thu, 22 May 2025, 08:26 Jonathan Wakely, wrote:
On Thu, 15 May 2025, 06:26 François Dumo
On Mon, May 26, 2025 at 09:30:59AM +, Yuao Ma wrote:
> Hi Steve,
>
> > I looked at the patch in a bit more detail, and
> > I am not thrilled with large-scale whitespace
> > changes mingled with functional changes. It makes
> > the patch harder to read and review.
>
> I'm not sure which file y
We get lots of error messages when compiling arm_neon.h under
e.g. -mcpu=cortex-m55, because Neon builtins are enabled only when
!TARGET_HAVE_MVE. This has been the case since MVE support was
introduced.
This patch uses an approach similar to what we do on aarch64, but only
partially since Neon i
In indirect/ctor.cc test_inplace_ctor function was defined, but never
called.
PR libstdc++/119152
libstdc++-v3/ChangeLog:
* testsuite/std/memory/indirect/ctor.cc: Run test_inplace_ctor.
---
Tested on x86_64-linux. Pushed to trunk.
libstdc++-v3/testsuite/std/memory/indirect/ctor
On Mon, May 26, 2025 at 4:15 PM Luc Grosheintz
wrote:
> Implements the parts of layout_left that don't depend on any of the
> other layouts.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/mdspan (layout_left): New class.
> * src/c++23/std.cc.in: Add layout_left.
>
> Signed-off-by:
Remove #pragma GCC target ("arch=armv8.2-a+bf16") and preceding
target and is thus useless.
gcc/ChangeLog:
* config/arm/arm_neon.h: Remove useless push/pop pragmas.
---
gcc/config/arm/arm_neon.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/gcc/config/arm/arm_neon.h b/gcc/confi
This effective target implicitly expects -march=armv8-a, otherwise
with a toolchain configured for instance with
--with-cpu=cortex-m0 --with-float=soft,
it fails even when trying
-mfpu=crypto-neon-fp-armv8 -mfloat-abi=softfp:
arm_neon.h:45:2: error: #error "NEON intrinsics not available with the
s
Jakub Jelinek wrote:
There is also BIND_EXPR_VARS, dunno if that should be walked instead or
in addition.
The usage is to ensure that variables are mapped with lambdas (→
closure_vars_accessed.add (…)) but not if they are local variables (→
data->local_decls.add (var)).
The 'closure_vars_ac
Like we do in other effective-targets, add "-mcpu=unset
-march=armv8-a" directly when setting et_arm_v8_neon_flags in
arm_v8_neon_ok_nocache, to avoid having to add these two flags in all
users of arm_v8_neon_ok.
This avoids duplication and possible typos.
gcc/testsuite/ChangeLog:
* lib/t
On Mon, 26 May 2025 at 17:14, Christophe Lyon
wrote:
>
> Commit r15-7152-g57b706d141b87c removed
> /* { dg-do run { target*-*-linux* *-*-gnu* *-*-uclinux* } } */
>
> from these tests, turning them into 'compile' only tests, even when
> they could be executed.
>
> This patch adds
> /* { dg-do run }
Commit r15-7152-g57b706d141b87c removed
/* { dg-do run { target*-*-linux* *-*-gnu* *-*-uclinux* } } */
from these tests, turning them into 'compile' only tests, even when
they could be executed.
This patch adds
/* { dg-do run } */
which is OK since the tests are correctly skipped if needed thank
PING²
On May 12, 2025, Tobias Burnus wrote:
PING.
There is actually a minor update as meanwhile CUDA 12.8 was
released that added the 'f' suffix and sm_103 and sm_121.
Still, the pattern remains the same; hence, a normal PING.
On April 25, 2025, Tobias Burnus wrote:
The idea of -march-map= i
Hi Jason
> On 26 May 2025, at 15:07, Jason Merrill wrote:
>
> Tested x86_64-pc-linux-gnu, OK for trunk?
>
> Iain, will you verify that one of your coroutine testcases breaks without this
> fix?
Yes; all current coroutine ramp cleanups are exposed to (potential) UB at -O >
0.
This patch reso
On Mon, 26 May 2025, Richard Biener wrote:
> On Fri, May 23, 2025 at 2:31 PM Alexander Monakov wrote:
> >
> > In PR 105965 we accepted a request to form FMA instructions when the
> > source code is using a narrow generic vector that contains just one
> > element, corresponding to V1SF or V1DF mo
Tested x86_64-pc-linux-gnu, OK for trunk?
Iain, will you verify that one of your coroutine testcases breaks without this
fix? I don't think lambda or anonymous union uses of DECL_VALUE_EXPR can break
in the same way, though this change is also correct for them.
-- 8< --
This PR noted that fold_
[mdspan.layout.left.cons] of N4950 states that this ctor is not
noexcept. Since, all other ctors of layout_left, layout_right or
layout_stride are noexcept, the choice was made, based on
[res.on.exception.handling], to make this ctor noexcept.
Two other major implementations of the STL make the sa
Implements the tests for layout_stride and for the features of the other
two layouts that depend on layout_stride.
libstdc++-v3/ChangeLog:
* testsuite/23_containers/mdspan/layouts/class_mandate_neg.cc: Add
tests for layout_stride.
* testsuite/23_containers/mdspan/layouts/c
Implements a suite of tests for the currently implemented parts of
layout_left. The individual tests are templated over the layout type, to
allow reuse as more layouts are added.
libstdc++-v3/ChangeLog:
* testsuite/23_containers/mdspan/layouts/class_mandate_neg.cc: New test.
* tes
Adds tests for layout_right and for the parts of layout_left that depend
on layout_right.
libstdc++-v3/ChangeLog:
* testsuite/23_containers/mdspan/layouts/class_mandate_neg.cc: Add
tests for layout_stride.
* testsuite/23_containers/mdspan/layouts/ctors.cc: Add tests for
Implements the remaining parts of layout_left and layout_right; and all
of layout_stride.
The implementation of layout_stride::mapping::is_exhaustive applies
the following change to the standard:
4266. layout_stride::mapping should treat empty mappings as exhaustive
https://cplusplus.github.io
On Mon, 19 May 2025, Tamar Christina wrote:
> > > +-param=vect-scalar-cost-multiplier=
> > > +Common Joined UInteger Var(param_vect_scalar_cost_multiplier) Init(1)
> > IntegerRange(0, 10) Param Optimization
> > > +The scaling multiplier to add to all scalar loop costing when performing
> > vec
libstdc++-v3/ChangeLog:
* include/std/mdspan(__mdspan::_ExtentsStorage): Change name
of private member _M_dynamic_extens to _M_dyn_exts.
* include/std/mdspan(extents): Change name of private member
from _M_dynamic_extents to _M_exts.
* include/std/mdspan: Fi
On Mon, 19 May 2025, Tamar Christina wrote:
> > >/* Complete the target-specific cost calculations. */
> > >loop_vinfo->vector_costs->finish_cost (loop_vinfo->scalar_costs);
> > >vec_prologue_cost = loop_vinfo->vector_costs->prologue_cost ();
> > > @@ -12373,6 +12394,13 @@ vect_transf
Implements the parts of layout_left that don't depend on any of the
other layouts.
libstdc++-v3/ChangeLog:
* include/std/mdspan (layout_left): New class.
* src/c++23/std.cc.in: Add layout_left.
Signed-off-by: Luc Grosheintz
---
libstdc++-v3/include/std/mdspan | 304 +++
Implement the parts of layout_left that depend on layout_right; and the
parts of layout_right that don't depend on layout_stride.
libstdc++-v3/ChangeLog:
* include/std/mdspan (layout_right): New class.
* src/c++23/std.cc.in: Add layout_right.
Signed-off-by: Luc Grosheintz
---
l
This follows up on:
https://gcc.gnu.org/pipermail/libstdc++/2025-May/061572.html
Note that this patch series can only be applied after merging:
https://gcc.gnu.org/pipermail/libstdc++/2025-May/061653.html
The important changes since v3 are:
* Fixed and testsed several related overflow issues th
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
A class to simplify implementation of -fdump-lang-foo with support for
pp_printf using %D and such.
gcc/cp/ChangeLog:
* cxx-pretty-print.h (class cxx_dump_pretty_printer): New.
* error.cc (cxx_dump_pretty_printer): Ctor/dto
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
This patch adds a dump with a trace of template instantiations, indented
based on the depth of recursive instantiation. -lineno adds the location
that triggered the instantiation, -details adds non-instantiation
sbustitutions.
The instantia
On Mon, May 19, 2025 at 10:42 AM Li Xu wrote:
>
> From: xuli
>
> This patch would like to support vector SAT_ADD when one of the op
> is singed IMM.
>
> void __attribute__((noinline)) \
> vec_sat_s_add_imm_##T##_fmt_1##_##INDEX (T *out, T *op_1, unsigned limi
On Mon, May 19, 2025 at 10:41 AM Li Xu wrote:
>
> From: xuli
>
> This patch would like to support .SAT_ADD when IMM=-1.
>
> Form1:
> T __attribute__((noinline)) \
> sat_s_add_imm_##T##_fmt_1##_##INDEX (T x) \
> {\
> T sum
On Fri, May 23, 2025 at 11:31:26AM -0400, Jason Merrill wrote:
> On 5/21/25 10:15 PM, Nathaniel Shead wrote:
> > Another approach would be to fix 'write_class_def' to handle these
> > declarations better, but that ended up being more work and felt fragile.
> > It also meant streaming a lot more inf
On Mon, May 26, 2025 at 4:57 AM Christophe Lyon
wrote:
>
> ,,
>
> On Mon, 26 May 2025 at 12:54, Andrew Pinski (QUIC)
> wrote:
> >
> > > -Original Message-
> > > From: Christophe Lyon
> > > Sent: Monday, May 26, 2025 3:09 AM
> > > To: Andrew Pinski (QUIC)
> > > Cc: gcc-patches@gcc.gnu.or
On Sun, May 18, 2025 at 10:58 PM Andrew Pinski wrote:
>
> This implements a simple copy propagation for aggregates in the similar
> fashion as we already do for copy prop of zeroing.
>
> Right now this only looks at the previous vdef statement but this allows us
> to catch a lot of cases that show
On Fri, May 16, 2025 at 4:05 AM Hongtao Liu wrote:
>
> It's https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119181
Please mention that in the changelog. Also ...
> On Fri, May 16, 2025 at 10:02 AM liuhongt wrote:
> >
> > The patch tries to solve miss vectorization for below case.
> >
> > void
> >
On Mon, May 26, 2025 at 2:20 PM Luc Grosheintz
wrote:
>
>
> On 5/26/25 13:53, Tomasz Kaminski wrote:
> > On Mon, May 26, 2025 at 1:32 PM Luc Grosheintz >
> > wrote:
> >
> >>
> >>
> >> On 5/26/25 11:43, Tomasz Kaminski wrote:
> >>> On Mon, May 26, 2025 at 11:35 AM Luc Grosheintz <
> >> luc.groshe
On 5/26/25 13:53, Tomasz Kaminski wrote:
On Mon, May 26, 2025 at 1:32 PM Luc Grosheintz
wrote:
On 5/26/25 11:43, Tomasz Kaminski wrote:
On Mon, May 26, 2025 at 11:35 AM Luc Grosheintz <
luc.groshei...@gmail.com>
wrote:
On 5/22/25 15:21, Tomasz Kaminski wrote:
For the stride and p
On 5/26/25 11:43, Tomasz Kaminski wrote:
On Mon, May 26, 2025 at 11:35 AM Luc Grosheintz
wrote:
On 5/22/25 15:21, Tomasz Kaminski wrote:
For the stride and product computation, we should perform them in
Extent::size_type, not index_type.
The latter may be signed, and we may hit UB in mu
On Mon, May 26, 2025 at 1:32 PM Luc Grosheintz
wrote:
>
>
> On 5/26/25 11:43, Tomasz Kaminski wrote:
> > On Mon, May 26, 2025 at 11:35 AM Luc Grosheintz <
> luc.groshei...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On 5/22/25 15:21, Tomasz Kaminski wrote:
> >>>
> >>> For the stride and product comp
,,
On Mon, 26 May 2025 at 12:54, Andrew Pinski (QUIC)
wrote:
>
> > -Original Message-
> > From: Christophe Lyon
> > Sent: Monday, May 26, 2025 3:09 AM
> > To: Andrew Pinski (QUIC)
> > Cc: gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH] testsuite: Fix pr101145inf*.c testcases
> > [PR117
> -Original Message-
> From: Christophe Lyon
> Sent: Monday, May 26, 2025 3:09 AM
> To: Andrew Pinski (QUIC)
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] testsuite: Fix pr101145inf*.c testcases
> [PR117494]
>
> Hi Andrew,
>
> On Sun, 17 Nov 2024 at 22:49, Andrew Pinski
> wrote:
From: Pan Li
This patch would like to combine the vec_duplicate + vxor.vv to the
vxor.vx. From example as below code. The related pattern will depend
on the cost of vec_duplicate from GR2VR. Then the late-combine will
take action if the cost of GR2VR is zero, and reject the combination
if the
Since floating point and vector registers overlap on s390, more
efficient code can be generated to extract FPRs from VRs.
Additionally, for double vectors, more efficient code can be generated
to load specific lanes.
Bootstrapped and regtested on s390x.
gcc/ChangeLog:
* config/s390/vecto
Hi Andrew,
On Sun, 17 Nov 2024 at 22:49, Andrew Pinski wrote:
>
> Instead of doing a dg-run with a specific target check for linux.
> Use signal as the effective-target since this requires the use
> of ALARM signal to do the testing.
> Also use check_vect in the main and renames main to main1 to
On 26/05/25 12:58, Jan Hubicka wrote:
External email: Use caution opening links or attachments
Hi,
Ping?
Sorry for the delay. I think I finally got auto-fdo running on my box
and indeed I see that if function is cloned later, the profile is lost.
There are .suffixes added before afdo pass (su
I forgot to send this to the list :(.
Forwarded Message
From: Xi Ruoyao
To: Alexandre Oliva
Cc: Xi Ruoyao
Subject: [PATCH] testsuite: Fix up dg-do-if
Date: 05/26/25 17:59:32
The line number needs to be passed to dg-do, instead of being stripped.
Fixes 'compile: syntax error
>
>
> > On 26 May 2025, at 5:34 pm, Jan Hubicka wrote:
> >
> > External email: Use caution opening links or attachments
> >
> >
> > Hi,
> > also, please, can you add an testcase? We should have some coverage for
> > auto-fdo specific issues
> I was looking for this too. AFIK we dont do a
On Mon, May 26, 2025 at 11:35 AM Luc Grosheintz
wrote:
>
>
> On 5/22/25 15:21, Tomasz Kaminski wrote:
> >
> > For the stride and product computation, we should perform them in
> > Extent::size_type, not index_type.
> > The latter may be signed, and we may hit UB in multiplying non-zero
> > extent
2. OK'ish: A bunch of testcases see more reads/writes as PRE of redundant
read/writes is punted to later passes which obviously needs more work.
3. NOK: We loose the ability to instrument local RM writes - especially in the
testsuite.
e.g.
a. instrinsic setting a static RM
b. get_frm
On 5/22/25 15:21, Tomasz Kaminski wrote:
For the stride and product computation, we should perform them in
Extent::size_type, not index_type.
The latter may be signed, and we may hit UB in multiplying non-zero
extents, before reaching the zero.
Then I observe the following issues:
1. When
The following adjusts the expected messages after -fopt-info-vec
was improved for (masked) epilogues.
Pushed.
* gcc.target/i386/vect-epilogues-5.c: Adjust.
---
gcc/testsuite/gcc.target/i386/vect-epilogues-5.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gcc/tests
From: Pan Li
Add asm dump check test for vec_duplicate + vxor.vv combine to vxor.vx,
with the GR2VR cost is 0, 2 and 15.
The below test suites are passed for this patch.
* The rv64gcv fully regression test.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/vx_vf/vx-1-i16.c: Add a
On Mon, 26 May 2025, Konstantinos Eleftheriou wrote:
> In `store_bit_field_1`, when the value to be written in the bitfield
> and/or the bitfield itself have vector modes, non-canonical subregs
> are generated, like `(subreg:V4SI (reg:V8SI x) 0)`. If one them is
> a scalar, this happens only when
Hi, all
Enable -mapxf will change some patterns about adc/sbb.
Hence gcc will raise an extra mov like
movq8(%rdi), %rax
adcq%rax, 8(%rsi), %rax
movq%rax, 8(%rdi)
rather than
movq8(%rsi), %rax
adcq%rax, 8(%rdi)
The patch add more ki
On Fri, May 23, 2025 at 2:31 PM Alexander Monakov wrote:
>
> In PR 105965 we accepted a request to form FMA instructions when the
> source code is using a narrow generic vector that contains just one
> element, corresponding to V1SF or V1DF mode, while the backend does not
> expand fma patterns fo
The -mcmodel=large option was originally added to handle generation of
large binaries with large PLTs. However, when compiling the Linux
kernel with allyesconfig the output binary is so large that the jump
instruction 26-bit immediate is not large enough to store the jump
offset to some symbols wh
> On 26 May 2025, at 5:34 pm, Jan Hubicka wrote:
>
> External email: Use caution opening links or attachments
>
>
> Hi,
> also, please, can you add an testcase? We should have some coverage for
> auto-fdo specific issues
I was looking for this too. AFIK we dont do any testing currently.
On Fri, May 23, 2025 at 5:25 PM Tomasz Kaminski wrote:
>
>
> On Fri, May 23, 2025 at 4:22 PM Luc Grosheintz
> wrote:
>
>>
>>
>> On 5/22/25 15:21, Tomasz Kaminski wrote:
>> > Thanks for working on the patches, they look solid, comments.
>> >
>> > Could you prepare a separate patch to fix initiali
In `store_bit_field_1`, when the value to be written in the bitfield
and/or the bitfield itself have vector modes, non-canonical subregs
are generated, like `(subreg:V4SI (reg:V8SI x) 0)`. If one them is
a scalar, this happens only when the scalar mode is different than the
vector's inner mode.
Th
On Fri, May 23, 2025 at 6:58 PM Jonathan Wakely wrote:
> Currently we only provide std::abs(__int128) and std::abs(__float128)
> for non-strict modes, i.e. -std=gnu++NN but not -std=c++NN.
>
> This defines those overloads for strict modes too, as a small step
> towards resolving PR 96710 (which w
On Sat, May 24, 2025 at 5:06 PM NightStrike wrote:
>
>
> On Thu, May 22, 2025 at 08:54 Tomasz Kamiński wrote:
>
>> From: Jonathan Wakely
>>
>> This papers implements C++26 std::indirect as specified
>
>
> “This patch”?
>
Indeed. I will fix it before committing. Thank you.
On Sat, May 24, 2025 at 1:29 PM Luc Grosheintz
wrote:
> The array that stores the dynamic extents used to be default
> initialized. The standard requires value intialization. This
> commit fixes the bug and adds a test.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/mdspan: Value initializ
OK, thanks.
--
Regards
Robin
Hi,
also, please, can you add an testcase? We should have some coverage for
auto-fdo specific issues
Honza
0002-AUTOFDO-Merge-profiles-of-clones-before-annotating.patch
Description: 0002-AUTOFDO-Merge-profiles-of-clones-before-annotating.patch
Hi,
> Ping?
Sorry for the delay. I think I finally got auto-fdo running on my box
and indeed I see that if function is cloned later, the profile is lost.
There are .suffixes added before afdo pass (such as openmp offloading or
nested functions) and there are .suffixes added afer afdo (by ipa
clonin
88 matches
Mail list logo
