> This one also has a comment saying "but use ta" with TDEFAULT_POLICY_P,
> IIUC one of those must be wrong too?
Yea, I didn't update the comment, thanks for catching.
--
Regards
Robin
Commit e1769bdd4cef522ada32aec863feba41116b183a accidentally inserted
the documentation for the x86 -mstack-protector-guard-symbol option in the
wrong place. Fixed thusly.
gcc/ChangeLog
PR target/117150
* doc/invoke.texi (RS/6000 and PowerPC Options): Move description
of -
This was approved in Wrocław as LWG 3899.
libstdc++-v3/ChangeLog:
* include/std/generator (generator::yield_value): Add overload
taking lvalue element_of view, as per LWG 3899.
---
The issue suggests that this change avoids creating a new coroutine
frame, so I thought if I used a
On Wed, 11 Dec 2024 at 22:53, Jonathan Wakely wrote:
>
> On 03/12/24 17:05 +0100, Giuseppe D'Angelo wrote:
> >Hello,
> >
> >The attached patch adds the span(initializer_list) constructor, added
> >by P2447R6 for C++26.
> >
> >It seems that GCC is somewhat aggressive with its -Winit-list-lifetime
>
Any std::span constructor with a runtime length has a precondition
that the length is equal to N (except when N == std::dynamic_extent).
Currently every constructor with a runtime length does:
if constexpr (extent != dynamic_extent)
__glibcxx_assert(n == extent);
We can move those assertions i
On 03/12/24 17:05 +0100, Giuseppe D'Angelo wrote:
Hello,
The attached patch adds the span(initializer_list) constructor, added
by P2447R6 for C++26.
It seems that GCC is somewhat aggressive with its -Winit-list-lifetime
warning, which actively interferes with this feature. The idea of the
n
On Wed, 11 Dec 2024 at 21:18, Giuseppe D'Angelo
wrote:
>
> On 11/12/2024 21:41, Jonathan Wakely wrote:
> > Hmm, the warning is useful if somebody does:
> >
> > std::span s({1,2,3});
> >
> > So I think we do want the warning, but maybe give it a special case so
> > it doesn't warn for an rvalue std
On Thu, Dec 5, 2024 at 2:28 PM Bill Wendling wrote:
> On Thu, Dec 5, 2024 at 1:09 PM Qing Zhao wrote:
> > > On Dec 3, 2024, at 10:29, Qing Zhao wrote:
> > >> On Dec 3, 2024, at 10:07, Martin Uecker wrote:
> > >> The language extension does not exist yet, so there is no problem.
> > > Yeah, I sh
On Wed, 11 Dec 2024 13:29:29 PST (-0800), Robin Dapp wrote:
Hi,
this patch makes vcompress use the tail-undisturbed policy by default
and also uses the proper VL.
Regtested on rv64gcv and waiting for the CI.
Regards
Robin
PR target/117383
gcc/ChangeLog:
* config/riscv/riscv
Hi,
this patch makes vcompress use the tail-undisturbed policy by default
and also uses the proper VL.
Regtested on rv64gcv and waiting for the CI.
Regards
Robin
PR target/117383
gcc/ChangeLog:
* config/riscv/riscv-protos.h (enum insn_type): Use TU policy.
* config/ri
Hi,
On 29 Nov 2024, at 15:33, Simon Martin wrote:
> We currently ICE upon the following code, that is valid under
> -Wno-pointer-arith:
>
> === cut here ===
> int main() {
> decltype( [](auto) { return sizeof(void); } ) x;
> return x.operator()(0);
> }
> === cut here ===
>
> The problem is th
On 11/12/2024 21:41, Jonathan Wakely wrote:
Hmm, the warning is useful if somebody does:
std::span s({1,2,3});
So I think we do want the warning, but maybe give it a special case so
it doesn't warn for an rvalue std::span.
Do you have anything in mind to make this work?
Note that the above i
Jonathan Wakely writes:
> Here's a v2 patch that adds the static assert messages and now also
> tests allocation for member coroutines (with implicit and explicit
> object parameters).
>
> [2. text/plain; patch.txt]...
This revision looks good. Thanks! :-)
Have a lovely day.
--
Arsen Arsenov
On Tue, 3 Dec 2024 at 16:07, Giuseppe D'Angelo
wrote:
>
> Hello,
>
> The attached patch adds the span(initializer_list) constructor, added by
> P2447R6 for C++26.
>
> It seems that GCC is somewhat aggressive with its -Winit-list-lifetime
> warning, which actively interferes with this feature. The
The following patch is a better solution for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116778
The patch was successfully tested and bootstrapped on x86-64, aarch64,
ppc64le.
commit fca0ab08cd936464b152e9b45356f625eba27575
Author: Vladimir N. Makarov
Date: Wed Dec 11 15:36:21 2024 -0500
On Dez 05 2024, Jakub Jelinek wrote:
> --- gcc/testsuite/c-c++-common/toplevel-asm-1.c.jj2024-11-01
> 15:09:46.209708353 +0100
> +++ gcc/testsuite/c-c++-common/toplevel-asm-1.c 2024-11-01
> 19:25:47.512567789 +0100
> @@ -0,0 +1,25 @@
> +/* PR c/41045 */
> +/* { dg-do compile } */
> +/*
On Dec 11, 2024, Richard Biener wrote:
> I think These 0, 0 args are supposed to indicate Maximum extent of the
> resulting Access
Thanks, that looks much better indeed.
A bootstrap on aarch64-linux-gnu revealed that sometimes (for example,
when building shorten_branches in final.cc) we will f
On 07/11/2024 09:18, Christophe Lyon wrote:
This patch series re-implements the store_scatter and load_gather
intrinsincs using the new framework, similarly to previous series.
A few points worth mentioning:
- unlike other intrinsics, these ones have the predicate after the
mode in their nam
Alfie Richards writes:
> Hi Richard,
>
> Thank you for the feedback!
>
> On 10/12/2024 18:49, Richard Sandiford wrote:
>>> -/* Returns true if DECL is multi-versioned using the target attribute, and
>>> this
>>> - is the default version. This function can only be used for targets
>>> that do
On Tue, 2024-12-10 at 19:08 -0500, Jason Merrill wrote:
> On 12/10/24 6:05 PM, David Malcolm wrote:
> > On Sat, 2024-12-07 at 10:19 -0500, Jason Merrill wrote:
> > > On 11/15/24 8:02 PM, David Malcolm wrote:
> > > > This patch is a followup to:
> > > > "c++: use diagnostic nesting [PR116253]"
>
When printing nested messages with
-fdiagnostics-set-output=text:experimental-nesting=yes
avoid printing a line such as the "cc1plus:" in the following:
• note: set ‘-fconcepts-diagnostics-depth=’ to at least 2 for more
detail
cc1plus:
for "special" locations such as UNKNOWN_LOCA
No functional change intended.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r15-6114-ge4ef3aa2911f1a.
gcc/ChangeLog:
* input.cc (file_cache::initialize_input_context): Rename member
"in_context" to "m_input_context".
(file_cache::add_fi
On Fri, 2024-11-15 at 20:05 -0500, David Malcolm wrote:
> Introduce a helper function for complaining about "signed unsigned"
> and "short long". Add colorization there so that e.g. the 'signed'
> and 'unsigned' are given consisten contrasting colors in both the
> message and the quoted source.
>
On Wed, 11 Dec 2024 at 14:59, Arsen Arsenović wrote:
>
> Jonathan Wakely writes:
>
> >> + for (auto _ : gen("const This& argument", std::allocator_arg , &mr))
> >
> > I have no idea what the promise_type::operator new overload that takes
> > a const This& argument is for, but this invocation of
On Wed, 27 Nov 2024, Patrick Palka wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
> for trunk/14/13?
Ping.
It occurred to me that another way to fix this PR might be to tweak the
overload set pruning (for non-dependent calls) to un-specialize the
selected function
I think the term of art is "ping"?
If GCC needs something from me to proceed with this, please tell me what
it is.
--jkl
On Thu, 7 Nov 2024 17:28:33 -0500
"James K. Lowden" wrote:
> On Fri, 8 Nov 2024 13:52:55 +0100
> Jakub Jelinek wrote:
>
> > Rather than a diff from /dev/null,
> > > it
Jonathan Wakely writes:
> Like this?
>
> /home/jwakely/gcc/15/include/c++/15.0.0/generator:478:25: error:
> static assertion failed: the argument that follows std::allocator_arg
> must be convertible to the generator's allocator type
> 478 | static_assert(convertible_to,
> |
Jonathan Wakely writes:
>> + for (auto _ : gen("const This& argument", std::allocator_arg , &mr))
>
> I have no idea what the promise_type::operator new overload that takes
> a const This& argument is for, but this invocation of gen uses it, so
> ... yay?
Member coroutines can call that overloa
On Dec 11, 2024, Richard Biener wrote:
> Am 11.12.2024 um 14:50 schrieb Alexandre Oliva :
>> if (get_best_mode (end_bit - first_bit, first_bit, 0, 0,
> I think These 0, 0 args are supposed to indicate Maximum extent of the
> resulting Access - but Widening to the largest Mode fitting alignment
>
> Yes, please, I don't have commit access.
OK, done.
--
Eric Botcazou
On 12/11/24 4:11 AM, Jakub Jelinek wrote:
Hi!
Since r14-4771 the FE tries to differentiate between cases where the lhs
of a store allows changing the current union member and cases where it
doesn't, and cases where it doesn't includes everything that has gone
through the cxx_eval_constant_expres
> Am 11.12.2024 um 14:50 schrieb Alexandre Oliva :
>
> On Dec 10, 2024, Richard Biener wrote:
>
>>> On Mon, Dec 9, 2024 at 8:55 PM Alexandre Oliva wrote:
>>> Regstrapped on x86_64-linux-gnu. The aarch64 CI had reported a
>>> regression with v3, so I'm also running a regstrap on aarch64-lin
ping
> -Original Message-
> From: Tamar Christina
> Sent: Wednesday, December 4, 2024 12:17 PM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> ktkac...@gcc.gnu.org; Richard Sandiford
> Subject: [PATCH 2/7]AArch64: Add SVE support for simd clones [PR96342]
>
> Hi All,
>
>
ping
> -Original Message-
> From: Tamar Christina
> Sent: Wednesday, December 4, 2024 12:17 PM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> ktkac...@gcc.gnu.org; Richard Sandiford
> Subject: [PATCH 3/7]AArch64: Disable `omp declare variant' tests for aarch64
> [PR96342]
ping
> -Original Message-
> From: Tamar Christina
> Sent: Wednesday, December 4, 2024 12:18 PM
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; Richard Earnshaw ;
> ktkac...@gcc.gnu.org; Richard Sandiford
> Subject: [PATCH 7/7]AArch64: Implement vector concat of partial SVE vectors
>
> Hi All,
>
On Dec 10, 2024, Richard Biener wrote:
> On Mon, Dec 9, 2024 at 8:55 PM Alexandre Oliva wrote:
>> Regstrapped on x86_64-linux-gnu. The aarch64 CI had reported a
>> regression with v3, so I'm also running a regstrap on aarch64-linux-gnu,
>> but it will still be a while. Ok to install if it pass
On Wed, 11 Dec 2024 at 12:17, Arsen Arsenović wrote:
>
> Jonathan Wakely writes:
>
> > This was approved in Wrocław as LWG 3900, so that passing an incorrect
> > argument intended as an allocator will be ill-formed, instead of
> > silently ignored.
> >
> > This also renames the template parameter
This patch adds __flashx as a new named address space that allocates
objects in .progmemx.data. The handling is mostly the same or similar
to that of 24-bit space __memx, except that the output routines are
simpler and more efficient. Loads are emit inline when ELPMX or
LPMX is available. The a
Jonathan Wakely writes:
> This was approved in Wrocław as LWG 3900, so that passing an incorrect
> argument intended as an allocator will be ill-formed, instead of
> silently ignored.
>
> This also renames the template parameters and function parameters for
> the allocators, to align with the nam
On 11/12/2024 09:54, Tamar Christina wrote:
-Original Message-
From: Richard Sandiford
Sent: Wednesday, December 11, 2024 9:50 AM
To: Tamar Christina
Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
; ktkac...@gcc.gnu.org
Subject: Re: [PATCH 1/2]AArch64: Add CMP+CSEL and CMP+CSET for
Jennifer Schmitz writes:
> As follow-up to
> https://gcc.gnu.org/pipermail/gcc-patches/2024-October/665472.html,
> this patch implements folding of svmul by -1 to svneg for
> unsigned SVE vector types. The key idea is to reuse the existing code that
> does this fold for signed types and feed it as
ChangeLog:
* MAINTAINERS: Add myself to write after approval.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7d65ed64bdd..44153a7a51e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -630,6 +630,7 @@ Sa Liu saliu
Hi Richard,
Thank you for the feedback!
On 10/12/2024 18:49, Richard Sandiford wrote:
-/* Returns true if DECL is multi-versioned using the target attribute, and this
- is the default version. This function can only be used for targets that do
- not support the "target_version" attribute.
On Wed, 11 Dec 2024 at 11:02, Jonathan Wakely wrote:
>
> This was approved in Wrocław as LWG 3900, so that passing an incorrect
> argument intended as an allocator will be ill-formed, instead of
> silently ignored.
>
> This also renames the template parameters and function parameters for
> the all
This was just approved in Wrocław.
libstdc++-v3/ChangeLog:
* include/std/ostream (println): Pass stream's locale to
std::format, as per LWG 4088.
* testsuite/27_io/basic_ostream/print/1.cc: Check std::println
with custom locale. Remove unused brit_punc class.
---
This was approved in Wrocław as LWG 3900, so that passing an incorrect
argument intended as an allocator will be ill-formed, instead of
silently ignored.
This also renames the template parameters and function parameters for
the allocators, to align with the names in the standard. I found it too
co
Hello,
even though it is not my work, I would like to ping this patch. Having
it upstream would really help us a lot.
Thank you very much in advance,
Martin
On Wed, Nov 13 2024, Michael Matz wrote:
> Hello,
>
> this is essentially
>
> https://gcc.gnu.org/pipermail/gcc-patches/2024-May/6510
The patch optimizes code generation for comparisons of the form
X & C1 == C2. When the bitwise AND mask could fit in a 12-bit immediate
operand of RISC-V "andi" instruction with help of right shifting.
For example, C1 = 0x5550 and C2 = 0x1450.
These numbers can be stored using 12 bits, whic
Eric Botcazou, le mer. 11 déc. 2024 09:58:23 +0100, a ecrit:
> > Difference with v3: Refresh
> >
> > Samuel Thibault (3):
> > ada: Factorize bsd signal definitions
> > ada: Fix GNU/Hurd priority range
> > ada: Add GNU/Hurd x86_64 support
>
> Thanks, this looks good to me. Do you need me to
Thank you everyone.
I have pushed the changes.
Thanks,
Sangamesh
On Mon, Dec 9, 2024 at 12:48 PM swamy sangamesh
wrote:
> Hi David,
>
> I don't have write privileges for GCC repo.
> I have raised a request for write access and provided your email address
> as approver.
> Please approve the r
> -Original Message-
> From: Richard Sandiford
> Sent: Wednesday, December 11, 2024 9:50 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; ktkac...@gcc.gnu.org
> Subject: Re: [PATCH 1/2]AArch64: Add CMP+CSEL and CMP+CSET for cores that
> support it
>
> Tam
Tamar Christina writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Wednesday, December 11, 2024 9:32 AM
>> To: Tamar Christina
>> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>> ; ktkac...@gcc.gnu.org
>> Subject: Re: [PATCH 1/2]AArch64: Add CMP+CSEL and CMP+CSET for
Tamar Christina writes:
> Hi All,
>
> This sets the L1 data cache size for some cores based on their size in their
> Technical Reference Manuals.
>
> Today the port minimum is 256 bytes as explained in commit
> g:9a99559a478111f7fbeec29bd78344df7651c707, however like Neoverse V2 most
> cores
> ac
> -Original Message-
> From: Richard Sandiford
> Sent: Wednesday, December 11, 2024 9:32 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; ktkac...@gcc.gnu.org
> Subject: Re: [PATCH 1/2]AArch64: Add CMP+CSEL and CMP+CSET for cores that
> support it
>
> Tam
Tamar Christina writes:
> Hi All,
>
> GCC 15 added two new fusions CMP+CSEL and CMP+CSET.
>
> This patch enables them for cores that support based on their Software
> Optimization Guides and generically on Armv9-A. Even if a core does not
> support it there's no negative performance impact.
>
>
Hi!
Since r14-4771 the FE tries to differentiate between cases where the lhs
of a store allows changing the current union member and cases where it
doesn't, and cases where it doesn't includes everything that has gone
through the cxx_eval_constant_expression path on the lhs.
As the testcase shows,
Hi All,
This sets the L1 data cache size for some cores based on their size in their
Technical Reference Manuals.
Today the port minimum is 256 bytes as explained in commit
g:9a99559a478111f7fbeec29bd78344df7651c707, however like Neoverse V2 most cores
actually define the L1 cache size as 64-byte
Hi All,
GCC 15 added two new fusions CMP+CSEL and CMP+CSET.
This patch enables them for cores that support based on their Software
Optimization Guides and generically on Armv9-A. Even if a core does not
support it there's no negative performance impact.
Bootstrapped Regtested on aarch64-none-
Hello,
Giuseppe D'Angelo ha scritto:
Hello,
This patch fixes a C++26 deprecation warning in g++'s (not libstdc++)
autotests.
Please ignore; this has been independently fixed in
7aab1271b4afb6f3e9e8a01825fcb14750b29312 (thanks!).
Thank you,
--
Giuseppe D'Angelo
smime.p7s
Description: Firm
> Difference with v3: Refresh
>
> Samuel Thibault (3):
> ada: Factorize bsd signal definitions
> ada: Fix GNU/Hurd priority range
> ada: Add GNU/Hurd x86_64 support
Thanks, this looks good to me. Do you need me to merge it?
--
Eric Botcazou
> diff --git
> a/gcc/testsuite/gcc.target/riscv/rvv/xsfvector/sf_vfnrclip_x_f_qf.c
> b/gcc/testsuite/gcc.target/riscv/rvv/xsfvector/sf_vfnrclip_x_f_qf.c
> index 813f7860f645..3b46505e8f99 100644
> --- a/gcc/testsuite/gcc.target/riscv/rvv/xsfvector/sf_vfnrclip_x_f_qf.c
> +++ b/gcc/testsuite/gcc.ta
61 matches
Mail list logo
