Re: [PATCH] libstdc++: Add lvalue overload for generator::yield_value

2024-12-24 Thread Arsen Arsenović
Hi Jonathan, Sorry for taking a while to look at this. Jonathan Wakely writes: > 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 i

Re: [PATCH v3] RISC-V: Fix code gen for reduction with length 0 [PR118182]

2024-12-24 Thread Robin Dapp
> `.MASK_LEN_FOLD_LEFT_PLUS`(or `mask_len_fold_left_plus_m`) is expecting the > return value will be the start value even if the length is 0. > > However current code gen in RISC-V backend is not meet that semantic, it will > result a random garbage value if length is 0. > > Let example by current

Re: [PATCH] simplify-rtx: Limit number of elts in when encoding.

2024-12-24 Thread Richard Sandiford
"Robin Dapp" writes: > [PATCH] varasm: Use native_encode_rtx for constant vectors. > > optimize_constant_pool hashes vector masks by native_encode_rtx and > merges identically hashed values in the constant pool. Afterwards the > optimized values are written in output_constant_pool_2. > > However,

[PATCH 1/2] libstdc++: don't implicit-construct _Yielded_decvref [PR118022]

2024-12-24 Thread Arsen Arsenović
Evening! This patchset includes fixes for two bugs in libstdc++s implementation of std::generator, namely PR118196 and PR118022. There's little to note about these fixes. Tested on x86_64-pc-linux-gnu via 'make -j17 check' with 'set v3_std_list { 98 11 14 17 20 23 26 }' in the libstdc++ build di

[PATCH 2/2] libstdc++: add missing return in generator assignment operator [PR118196]

2024-12-24 Thread Arsen Arsenović
libstdc++-v3/ChangeLog: PR libstdc++/118196 * include/std/generator (generator::operator=(generator)): Add missing 'return *this;'. * testsuite/24_iterators/range_generators/move-assign-missing-return.C: New test. --- libstdc++-v3/include/std/generator

RE: [PATCH] Document refactoring of the option -fcf-protection=x.

2024-12-24 Thread Liu, Hongtao
> -Original Message- > From: Gerald Pfeifer > Sent: Wednesday, December 25, 2024 11:40 AM > To: Liu, Hongtao > Cc: gcc-patches@gcc.gnu.org; hjl.to...@gmail.com > Subject: Re: [PATCH] Document refactoring of the option -fcf-protection=x. > > On Fri, 12 Jan 2024, Gerald Pfeifer wrote: >

[pushed] wwwdocs: gcc-14: Reword the update on -fcf-protection

2024-12-24 Thread Gerald Pfeifer
Pushed after confirmation from Hongtao. Gerald --- htdocs/gcc-14/changes.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index ba9fc680..5d324767 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/chan

[pushed] wwwdocs: readings: parisc.wiki.kernel.org is now parisc.docs.kernel.org

2024-12-24 Thread Gerald Pfeifer
--- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 28a2097d..6ca9cc07 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -245,7 +245,7 @@ names. Manufacturer: HP PA-RISC is preferred over

[pushed] wwwdocs: readings: Update RISC-V specifications link

2024-12-24 Thread Gerald Pfeifer
--- htdocs/readings.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/readings.html b/htdocs/readings.html index 103fd453..28a2097d 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -264,7 +264,7 @@ names. riscv Manufacturer: Many (open ISA standard

[pushed] wwwdocs: gcc-9: Update Thread Building Blocks location on GitHub

2024-12-24 Thread Gerald Pfeifer
--- htdocs/gcc-9/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html index 47d2f2a2..0facfdab 100644 --- a/htdocs/gcc-9/changes.html +++ b/htdocs/gcc-9/changes.html @@ -675,7 +675,7 @@ $ g++ typo.cc The C+

Re: [PATCH] Document refactoring of the option -fcf-protection=x.

2024-12-24 Thread Gerald Pfeifer
On Fri, 12 Jan 2024, Gerald Pfeifer wrote: > On Wed, 10 Jan 2024, liuhongt wrote: >> To override -fcf-protection, -fcf-protection=none needs to be added >> and then with -fcf-protection=xxx. > I'm afraid I am struggling with the English of this, but need more time to > untangle and suggest an alte