Hi,
as discussed also on the autofdo pull request, LLVM solves the same
problem using -funique-internal-linkage-names
https://reviews.llvm.org/D73307
All non-public functions gets theis symbol renamed from
.__uniq.
Decadic is used since demanglers special case numerical suffixes.
In addition debug
On Mon, Jul 7, 2025 at 2:56 AM Kyrylo Tkachov wrote:
>
> Hi all,
>
> Similar to the BCAX patch, we can also use EOR3 for 64-bit modes,
> just by adjusting the mode iterator used.
> Thus for input:
>
> uint32x2_t
> bcax_s (uint32x2_t a, uint32x2_t b, uint32x2_t c)
> {
> return EOR3 (a, b, c);
> }
On 7/7/25 06:19, Kyrylo Tkachov wrote:
External email: Use caution opening links or attachments
Hi all,
Similar to the BCAX and EOR3 patterns from TARGET_SHA3 we can use the
SVE2 NBSL instruction for DImode arugments when they come in SIMD registers.
Minor nit: there is a typo in "arugments"
On 7/7/25 06:19, Kyrylo Tkachov wrote:
> External email: Use caution opening links or attachments
>
>
> Hi all,
>
> Similar to other patches in this series, this patch adds a splitter
> for DImode BSL1N operations, taking care to generate the right code
> in the GP regs case.
>
> Thus for the test
On Tue, Jul 8, 2025 at 5:02 AM H.J. Lu wrote:
>
> On Mon, Jul 7, 2025 at 11:08 PM Jason Merrill wrote:
> >
> > On 7/1/25 5:36 PM, H.J. Lu wrote:
> > > On Tue, Jul 1, 2025 at 9:37 PM Jason Merrill wrote:
> > >>
> > >> On 6/30/25 7:03 PM, H.J. Lu wrote:
> > >>> On Mon, Jun 30, 2025 at 10:36 PM Jas
This pattern enables the combine pass (or late-combine, depending on the case)
to merge a float-extended vec_duplicate into a plus-mult or minus-mult RTL
instruction.
Before this patch, we have three instructions, e.g.:
fcvt.s.h fa5,fa5
vfmv.v.f v24,fa5
vfmadd.vv v8,v24,v16
> On Jul 7, 2025, at 02:05, Richard Biener wrote:
>
> On Sat, Jul 5, 2025 at 2:10 PM Siddhesh Poyarekar wrote:
>>
>> On 2025-07-05 07:23, Richard Biener wrote:
OK, should I revert right away or can we wait till Qing returns on Monday?
>>>
>>> Monday is OK with me.
>>>
>>
>> Thanks, so
Andre,
I still don't get it, and the present version made it worse for me...
So let's see what I was thinking. There are the following types of
functions:
(0) impure, non-elemental functions, which likely have side-effects
(1) pure functions (in the f95 sense), i.e. pure non-elemental
(2)
Am 07.07.2025 um 23:02 schrieb Jonathan Wakely:
On Mon, 7 Jul 2025 at 22:01, Jonathan Wakely wrote:
On Mon, 7 Jul 2025 at 21:26, Björn Schäpers wrote:
From: Björn Schäpers
Sorry for the noise, this is the current version of the Patch.
-- >8 --
Windows does not provide a tzdata.zi, but ms
From: Björn Schäpers
Windows does not provide a tzdata.zi, but msys does. Use this, if
available, instead of the embedded (and possibly outdated) database.
libstdc++-v3/Changelog:
Use msys provided time zone information.
* src/c++20/tzdb.cc (zoneinfo_file): On Windows look rela
> -Original Message-
> From: Rainer Orth
> Sent: Monday, July 7, 2025 18:08
> To: Robert Dubner
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] cobol: Implement CXXFLAGS_FOR_COBOL.
>
> Hi Robert,
>
> > I have elsewhere described my frustration in trying, during
development,
> >
Ping!
On Thu, 26 Jun 2025 15:32:47 +0200
Andre Vehreschild wrote:
> Hi,
>
> I found a bug in the module cleanup expression at the end of the test. In the
> attached patch it is corrected.
>
> Regtests ok on x86_64-pc-linux-gnu / F41. Ok for mainline?
>
> Regards,
> Andre
>
> On Wed, 25
On Thu, Jul 03, 2025 at 09:35:49AM -0400, Jason Merrill wrote:
> On 7/2/25 7:58 PM, Patrick Palka wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
> > for trunk?
> >
> > -- >8 --
> >
> > Here the flag -fno-delete-null-pointer-checks causes the trivial address
> > co
From: Björn Schäpers
Windows does not provide a tzdata.zi, but msys does. Use this, if
available, instead of the embedded (and possibly outdated) database.
libstdc++-v3/Changelog:
Use msys provided time zone information.
* src/c++20/tzdb.cc (zoneinfo_file): On Windows look rela
From: Björn Schäpers
Windows does not provide a tzdata.zi, but msys does. Use this, if
available, instead of the embedded (and possibly outdated) database.
libstdc++-v3/Changelog:
Use msys provided time zone information.
* src/c++20/tzdb.cc (zoneinfo_file): On Windows look rela
From: Björn Schäpers
Sorry for the noise, this is the current version of the Patch.
-- >8 --
Windows does not provide a tzdata.zi, but msys does. Use this, if
available, instead of the embedded (and possibly outdated) database.
libstdc++-v3/Changelog:
Use msys provided time zone inform
For the title, I have created bugzilla PR120914. for this paper:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120914
On Fri, Jul 4, 2025 at 10:34 AM Luc Grosheintz
wrote:
> This implements P3029R1. In P3029R1, the CTAD for span is refined to
> permit deducing the extent of the span from an integ
On Mon, Jul 07, 2025 at 11:59:48AM -0400, Jason Merrill wrote:
> > Another case are targets with implicit -fno-delete-null-pointer-checks or
> > when users use that explicitly. In that case one variable or function can
> > actually end up being at address 0, so am not sure if it is correct to
> >
On 7/3/25 9:46 AM, Jakub Jelinek wrote:
On Thu, Jul 03, 2025 at 09:35:49AM -0400, Jason Merrill wrote:
On 7/2/25 7:58 PM, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
for trunk?
-- >8 --
Here the flag -fno-delete-null-pointer-checks causes the triv
On 7/2/25 7:58 AM, Alfie Richards wrote:
Hi Jason,
Thanks for the feedback, see below an updated patch.
OK.
Again reg-tested on Aarch64 and x86.
Thanks,
Alfie
-- >8 --
Add logic for the case of two FMV annotated functions with identical
signature other than the return type.
Previously th
Drop down from SVE2 to SVE1 as that's the minimum
required for the test, and since it's a mid-end test
add the aarch64_sve_hw check.
Regtested on aarch64-none-linux-gnu and no issues.
committed to master.
Thanks,
Tamar
gcc/testsuite/ChangeLog:
PR tree-optimization/120817
* gcc.
> On Jul 7, 2025, at 11:58, Siddhesh Poyarekar wrote:
>
> On 2025-07-07 09:33, Siddhesh Poyarekar wrote:
>>> The only difference between &a->fam[0] and &a->fam is not the value (that is
>>> the same), just the type in one case say int *, in the other int [0:] *.
>>> At least in GIMPLE pointer
On Mon, 7 Jul 2025 at 15:47, Torbjorn SVENSSON
wrote:
>
>
>
> On 2025-07-03 15:02, Christophe Lyon wrote:
> > ping^2 ?
>
> Looks fine to me, but as you know, my approval does not count.
>
Thanks for confirming I didn't miss anything from your intentions.
Christophe
> Kind regards,
> Torbjörn
>
>
On Fri, Jul 4, 2025 at 5:20 PM H.J. Lu wrote:
>
> On Thu, Jul 3, 2025 at 2:02 PM H.J. Lu wrote:
> >
> > On Wed, Jul 2, 2025 at 9:12 AM H.J. Lu wrote:
> > >
> > > While working on
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120881
> > >
> > > I tried to use check-function-bodies to v
On 7/7/25 8:39 AM, Andre Vehreschild wrote:
Ping!
OK for mainline.
Thanks,
Jerry
On Thu, 26 Jun 2025 15:32:47 +0200
Andre Vehreschild wrote:
Hi,
I found a bug in the module cleanup expression at the end of the test. In the
attached patch it is corrected.
Regtests ok on x86_64-pc-linux
On Sun, Jul 06, 2025 at 09:09:53PM +0800, Yuao Ma wrote:
> Hi Tobias,
>
> On 7/6/2025 6:34 PM, Tobias Burnus wrote:
> > As that commit is from 2020 and 2.69 in from 2012, it seems as if your
> > autoconf is too new. Can you re-check that the right version is at the
> > beginning of the PATH?
> >
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
This patch is an attempt to implement P2036R3 along with P2579R0, fixing
build breakages caused by P2036R3.
The simplest example is:
auto counter1 = [j=0]() mutable -> decltype(j) {
return j++;
};
which currently do
On Mon, 7 Jul 2025 at 21:26, Björn Schäpers wrote:
>
> From: Björn Schäpers
>
> Sorry for the noise, this is the current version of the Patch.
>
> -- >8 --
> Windows does not provide a tzdata.zi, but msys does. Use this, if
> available, instead of the embedded (and possibly outdated) database.
>
On Mon, 7 Jul 2025 at 22:01, Jonathan Wakely wrote:
>
> On Mon, 7 Jul 2025 at 21:26, Björn Schäpers wrote:
> >
> > From: Björn Schäpers
> >
> > Sorry for the noise, this is the current version of the Patch.
> >
> > -- >8 --
> > Windows does not provide a tzdata.zi, but msys does. Use this, if
>
This adds the new bitset constructor from string_view
defined in P2697 to the debug version of the type.
libstdc++-v3/Changelog:
PR libstdc++/119742
* include/debug/bitset: Add new ctor.
---
libstdc++-v3/include/debug/bitset | 12
1 file changed, 12 insertions(+)
dif
On Mon, Jul 7, 2025 at 11:08 PM Jason Merrill wrote:
>
> On 7/1/25 5:36 PM, H.J. Lu wrote:
> > On Tue, Jul 1, 2025 at 9:37 PM Jason Merrill wrote:
> >>
> >> On 6/30/25 7:03 PM, H.J. Lu wrote:
> >>> On Mon, Jun 30, 2025 at 10:36 PM Jason Merrill wrote:
>
> On 6/28/25 7:00 AM, H.J. Lu wr
Hi, thanks a lot for all the discussion so far on this issue.
An update on this:
1. I have reverted the 3 patches to support counted_by for pointers I have
committed last week from master.
2. At the same time: On the C FE code generation to .ACCESS_WITH_SIZE for
pointers with counted_by att
Hi,
The patches look good to me, the only real comment is about using header
guard, that I plan to do locally.
I am testing on full test suite now, and will merge them pending the
approval from Jonathan.
>From the patch that will set __cpp_lib_mdspan, do you want to create it? I
can also prepare
> On Wed, Jun 25, 2025 at 10:04:41AM +0200, Juergen Christ wrote:
> > On VXE targets, we can directly use the fp min/max instruction instead of
> > calling into libm for fmin/fmax etc.
> >
> > Provide fmin/fmax versions also for vectors even though it cannot be
> > called directly. This will be e
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Monday, July 7, 2025 10:38 AM
> To: GCC Patches
> Cc: Richard Sandiford ; Richard Earnshaw
> ; Alex Coplan ; Andrew
> Pinski
> Subject: [PATCH] aarch64: Improve popcountti2 with SVE
>
> Hi all,
>
> The TImode popcount sequence can be
On 2025-07-07 03:05, Richard Biener wrote:
Since the intent of the .ACCESS_WITH_SIZE was to associate the storage
of count with c to prevent reordering, maybe the semantically correct
solution here is that when c is a pointer, the frontend emits:
_2 = a->c;
_3 = &a->count;
_1 = .ACCE
On Mon, Jul 7, 2025 at 12:34 PM Luc Grosheintz
wrote:
>
>
> On 7/7/25 11:45, Tomasz Kaminski wrote:
> > On Mon, Jul 7, 2025 at 11:41 AM Luc Grosheintz >
> > wrote:
> >
> >> libstdc++-v3/ChangeLog:
> >>
> >> * include/bits/version.def (mdspan): Set to 202207 and remove
> >> no_s
On 7/5/25 01:13, Jonathan Wakely wrote:
Clang wants this change:
--- a/libstdc++-v3/include/std/mdspan
+++ b/libstdc++-v3/include/std/mdspan
@@ -509,7 +509,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
template
concept __mapping_of =
- is_same_v,
+ is_same_v,
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Monday, July 7, 2025 11:16 AM
> To: GCC Patches
> Cc: Richard Earnshaw ; Richard Sandiford
> ; Alex Coplan ; Andrew
> Pinski
> Subject: [PATCH 1/7] aarch64: Allow 64-bit vector modes in pattern for BCAX
> instruction
>
> Hi all,
>
> T
On Mon, Jul 07, 2025 at 01:06:44PM +0200, Juergen Christ wrote:
> Done. Should I send a v3?
If bootstrapped and the new tests are still successful (no need for a
full testsuite run I guess), then feel free to push immediately.
Tamar Christina writes:
>> -Original Message-
>> From: Kyrylo Tkachov
>> Sent: Monday, July 7, 2025 10:38 AM
>> To: GCC Patches
>> Cc: Richard Sandiford ; Richard Earnshaw
>> ; Alex Coplan ; Andrew
>> Pinski
>> Subject: [PATCH] aarch64: Improve popcountti2 with SVE
>>
>> Hi all,
>>
>>
On 7/7/25 13:24, Tomasz Kaminski wrote:
On Mon, Jul 7, 2025 at 12:34 PM Luc Grosheintz
wrote:
On 7/7/25 11:45, Tomasz Kaminski wrote:
On Mon, Jul 7, 2025 at 11:41 AM Luc Grosheintz
libstdc++-v3/ChangeLog:
* include/bits/version.def (mdspan): Set to 202207 and remove
From: "H.J. Lu"
xtensa ABI requires sign extension of signed 8/16-bit arguments to 32
bits and zero extension of unsigned 8/16-bit arguments to 32 bits.
TARGET_PROMOTE_PROTOTYPES is an optimization, not an ABI requirement.
Remove TARGET_PROMOTE_PROTOTYPES and define xtensa_promote_function_mode
t
On Wed, Jun 25 2025, Martin Jambor wrote:
> Hi,
>
> in contrib we have a script filter-clang-warnings.py which supposedly
> filters out uninteresting warnings emitted by clang when it compiles
> GCC. I'm not sure if anyone else uses it but our internal SUSE
> testing infrastructure does.
>
> Since
Hi,
in line with my previous patches introducing override where clang
warnings indicate that they are missing, this patch adds it to three
new member functions overriding ancestor virtual functions that do not
have them.
Since Andrew has pre-approved such changes for ranger, I am going to
push it
From: Pan Li
The rv32 doesn't support __uint128, and then we will have
error like below during test.
error: '__int128' is not supported on this target.
Thus, we disable the uint128_t related test when rv32.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/sat/sat_arith.h: Add xlen check fo
On Mon, Jul 07, 2025 at 07:51:52PM -0400, Siddhesh Poyarekar wrote:
> On 2025-07-07 17:47, Jakub Jelinek wrote:
> > Even 6 arguments is IMHO too much.
> > /* Expand the IFN_ACCESS_WITH_SIZE function:
> > ACCESS_WITH_SIZE (REF_TO_OBJ, REF_TO_SIZE, CLASS_OF_SIZE,
> > TYPE_OF
Hi Honza,
> On 8 Jul 2025, at 2:26 am, Jan Hubicka wrote:
>
> External email: Use caution opening links or attachments
>
>
> Hi,
> as discussed also on the autofdo pull request, LLVM solves the same
> problem using -funique-internal-linkage-names
> https://reviews.llvm.org/D73307
>
> All non-
> Am 08.07.2025 um 07:21 schrieb Jakub Jelinek :
>
> On Mon, Jul 07, 2025 at 07:51:52PM -0400, Siddhesh Poyarekar wrote:
>>> On 2025-07-07 17:47, Jakub Jelinek wrote:
>>> Even 6 arguments is IMHO too much.
>>> /* Expand the IFN_ACCESS_WITH_SIZE function:
>>>ACCESS_WITH_SIZE (REF_TO_OBJ, RE
> -Original Message-
> From: Richard Sandiford
> Sent: Monday, July 7, 2025 12:55 PM
> To: Kyrylo Tkachov
> Cc: GCC Patches ; Richard Earnshaw
> ; Alex Coplan ; Andrew
> Pinski
> Subject: Re: [PATCH 3/7] aarch64: Handle DImode BCAX operations
>
> Richard Sandiford writes:
> > Kyrylo Tk
> -Original Message-
> From: Remi Machet
> Sent: Monday, July 7, 2025 5:53 PM
> To: Kyrylo Tkachov ; GCC Patches patc...@gcc.gnu.org>
> Cc: Richard Sandiford ; Richard Earnshaw
> ; Alex Coplan ; Andrew
> Pinski
> Subject: Re: [PATCH 4/7] aarch64: Use EOR3 for DImode values
>
> On 7/7/25
On Tue, Jul 08, 2025 at 08:15:30AM +0200, Richard Biener wrote:
> > No. Because (most of the) pointer conversions are useless, if you have
> > _2 = &something.fam[0];
> > ...
> > _4 = &something.fam;
> > _5 = .ACCESS_WITH_SIZE (_4, ...);
> > (or whatever else where _4 has the carefully chosen p
> -Original Message-
> From: Kyrylo Tkachov
> Sent: Monday, July 7, 2025 11:19 AM
> To: GCC Patches
> Cc: Richard Sandiford ; Richard Earnshaw
> ; Alex Coplan ; Andrew
> Pinski
> Subject: [PATCH 4/7] aarch64: Use EOR3 for DImode values
>
> Hi all,
>
> Similar to BCAX, we can use EOR3 f
Minor fallout from HJ's recent change to the check-function-bodies code
in the testsuite.
The label isn't at all important here, so forcing it match is just a
waste of time. So this patch just skips over the label. It fixes a
handful of failures in testsuite:
unix//-march=rv32gcv: gcc: gc
This is a snapshot of work in progress, for reference.
bind_front(...) is uglified directly from the sample
implementation in P2714, at include/std/functional:1284 .
Test failures:
bind_front/1.cc:53: error: static assertion failed
bind_front/1.cc:57: error: static assertion failed
bind_front/1.c
On 7/7/25 9:24 PM, pan2...@intel.com wrote:
/**/
/* Saturation Add (unsigned and signed)
*/
diff --git a/gcc/testsuite/gcc.target/riscv/sat/sat_u_mul-run-1-u16-from-u128.c
> Is that correct? Don't you need to be testing that the platform has
> vector in addition to being rv64?
It is riscv.exp test, so I think vector extension is not required here.
Pan
-Original Message-
From: Jeff Law
Sent: Tuesday, July 8, 2025 11:45 AM
To: Li, Pan2 ; gcc-patches@gcc.
101 - 157 of 157 matches
Mail list logo
