On Fri, May 23, 2025 at 2:39 AM Richard Biener
wrote:
>
> On Thu, May 22, 2025 at 3:11 AM Jeff Law wrote:
> >
> >
> >
> > On 5/18/25 10:38 AM, Andrew Pinski wrote:
> > > While working on improving forwprop and removal of
> > > forward_propagate_into_gimple_cond/forward_propagate_into_comparison,
This improves copy prop for aggregates by working over statements that don't
modify the access
just like how it is done for copying zeros.
To speed up things, we should only have one loop back on the vuse instead of
doing it twice for
each load/store assignments.
PR tree-optimization/142
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk/15?
-- >8 --
When emitting a primary module interface, we must re-stream any TU-local
entities that we saw in a partition. This patch adds the missing
members from core_vals.
As a drive-by fix, in some cases we might have a typedef
Apologies for late a late reply. A quick skim of the code
suggests that you can eliminate some of the range_check()
calls in the simplifications. For example, you have
+gfc_expr *
+gfc_simplify_acospi (gfc_expr *x)
+{
+ gfc_expr *result;
+
+ if (x->expr_type != EXPR_CONSTANT)
+return NULL;
On 4/14/25 9:57 AM, Jason Merrill wrote:
On 1/9/25 10:00 PM, Jason Merrill wrote:
Tested x86_64-pc-linux-gnu. Is the diagnostic.h change OK for trunk?
Ping?
Ping.
-- 8< --
To respect the #pragma diagnostic lines in libstdc++ headers when
compiling
with module std, we need to represent
Hi, Richard,
Thanks a lot for your comments and questions.
Please see my answers embedded below:
> On May 19, 2025, at 06:44, Richard Biener wrote:
>
> On Fri, May 16, 2025 at 3:34 PM Qing Zhao wrote:
>>
>> Control this with a new option -fdiagnostics-details.
>>
>> $ cat t.c
>> extern void
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
I wondered why we needed to push/pop_tinst_level in mangle_decl_string. And
apparently we don't need to anymore.
gcc/cp/ChangeLog:
* mangle.cc (mangle_decl_string): Don't push_tinst_level.
---
gcc/cp/mangle.cc | 22 +++---
On Fri, 23 May 2025 at 18:56, Paul Keir wrote:
>
> This patch implements C++26 "Enabling the Use of weak_ptr as Keys in
> Unordered Associative Containers", as specified in P1901R2.
Splendid, thanks. I'll review this more carefully next week.
Some quick comments:
This should define the __cpp_l
Documentation for `__cmpsf2` and similar functions currently indicate a
return type of `int`. This is not correct however; the `libgcc`
functions return `CMPtype`, the size of which is determined by the
`libgcc_cmp_return` mode.
Update documentation to use `CMPtype` and indicate that this is
targe
On 5/22/25 05:12, Robin Dapp wrote:
>>> AFAICT the main difference to standard mode switching is that we (ab)use it
>>> to set the rounding mode to the value it had initially, either at function
>>> entry or after a call. That's different to regular mode switching which
>>> assumes "static" rou
> Am 23.05.2025 um 17:35 schrieb Hans-Peter Nilsson :
>
> The 6.7 version is what's in Debian 11. I'll commit this as
> obvious in a few hours.
Thanks- I’ve also seen this on SLES and ppenSUSE Leap.
Richard
> -- >8 --
> Commit r16-833-gfbb7f1cb5d3c8b appears to have broken builds with
> m
This patch implements C++26 "Enabling the Use of weak_ptr as Keys in Unordered
Associative Containers", as specified in P1901R2.
I don't have write access.
Signed-off-by: Paul Keir
Tested on x86_64-linux.
libstdc++-v3/ChangeLog:
* include/bits/shared_ptr.h: Added owner_equal and owne
We already have the attribute on std::__is_constant_evaluated() but for
some reason not on std::is_constant_evaluated().
libstdc++-v3/ChangeLog:
* include/std/type_traits (is_constant_evaluated): Add
always_inline attribute.
---
Tested x86_64-linux.
Pushed to trunk.
libstdc++-
Since r16-154-gc91eb5a5c13f14 std::addressof is no less efficient than
std::__addressof, so change some uses of the latter to the former.
We can't change them all, because some uses need to compile as C++98
which only has std::__addressof.
libstdc++-v3/ChangeLog:
* include/bits/stl_const
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 will eventually mean that __int128
satisfies the std::integral conc
There are some names in Solaris libc headers which cause:
FAIL: 17_intro/names.cc -std=gnu++98 (test for excess errors)
FAIL: 17_intro/names.cc -std=gnu++11 (test for excess errors)
libstdc++-v3/ChangeLog:
* testsuite/17_intro/names.cc [__sun__] (a, i, n): Undefine.
---
Tested x86_64-
Hi Tobias,
The patch has been updated. Could you please take a look when you have a
chance?
> Can you add the PR number to the commit log ("PR fortran/113152")?
Done.
> Can you also update the documentation – as you already did for ATAND?
I think that's quite a lot of wording... Hoping to tack
On 5/23/25 10:35 AM, Nathaniel Shead wrote:
On Fri, May 23, 2025 at 10:23:51AM -0400, Jason Merrill wrote:
On 5/22/25 8:22 AM, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk/15?
(Also is renaming the old test OK/appropriate? Or should I keep it
before an
On 5/23/25 10:59 AM, Nathaniel Shead wrote:
Tested on x86_64-pc-linux-gnu (so far just modules.exp), OK for trunk if
full bootstrap+regtest succeeds?
OK.
-- >8 --
When streaming in a reference to a data member, we have an oversight
where we did not consider USING_DECLs, despite otherwise han
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 information that we don't need.
Long term I had been playing around with rewo
The 6.7 version is what's in Debian 11. I'll commit this as
obvious in a few hours.
-- >8 --
Commit r16-833-gfbb7f1cb5d3c8b appears to have broken builds with
makeinfo from texinfo 6.7 (Debian: 6.7.0.dfsg.2-6) - but not 6.8
(6.8-6+b1). With 6.7, I see (linebreaks manually added):
if [ xinfo = x
On Fri, 23 May 2025 at 16:31, Tomasz Kaminski wrote:
>
>
>
> On Fri, May 23, 2025 at 1:52 PM Jonathan Wakely wrote:
>>
>> On 23/05/25 10:03 +0100, Jonathan Wakely wrote:
>> >On 22/05/25 14:50 +0200, Tomasz Kamiński wrote:
>> >>From: Jonathan Wakely
>> >>
>> >>This papers implements C++26 std::in
On Fri, May 23, 2025 at 1:52 PM Jonathan Wakely wrote:
> On 23/05/25 10:03 +0100, Jonathan Wakely wrote:
> >On 22/05/25 14:50 +0200, Tomasz Kamiński wrote:
> >>From: Jonathan Wakely
> >>
> >>This papers implements C++26 std::indirect as specified
> >>in P3019 with amendment to move assignment fr
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 initialization
> > default-initialization of extents,
> > that you have noticed,
> Am 23.05.2025 um 16:49 schrieb Thomas Schwinge :
>
> This fell out of me looking into PR119835. This doesn't resolve the
> underlying
> issue, but instead of failing GIMPLE semantics verification just by chance in
> the 'GIMPLE pass: nrv' context, it makes the issue observable generally.
>
Tested on x86_64-pc-linux-gnu (so far just modules.exp), OK for trunk if
full bootstrap+regtest succeeds?
-- >8 --
When streaming in a reference to a data member, we have an oversight
where we did not consider USING_DECLs, despite otherwise handling them
here the same as fields. This patch corre
On 9/29/23 16:17, Jeff Law wrote:
On 9/5/23 01:12, Andrew Pinski wrote:
On Mon, Sep 4, 2023 at 11:06 PM Jeff Law via Gcc-patches
wrote:
On 9/1/23 11:30, Andrew Pinski via Gcc-patches wrote:
So it turns out there was a simplier way of starting to
improve VRP to start to fix PR 110131, P
On Wed, May 21, 2025 at 07:34:27PM +0200, Stefan Schulze Frielinghaus wrote:
> libstdc++-v3/ChangeLog:
>
> * testsuite/std/format/parse_ctx.cc: Fix typo for bfloat16 guard.
> ---
> Ok for mainline?
Just realized that I can use my super powers ;-) and pushed as obvious
in commit 08b4f6198de
This fell out of me looking into PR119835. This doesn't resolve the underlying
issue, but instead of failing GIMPLE semantics verification just by chance in
the 'GIMPLE pass: nrv' context, it makes the issue observable generally.
(... thereby regressing a small number of offloading test cases wher
On Fri, May 23, 2025 at 10:23:51AM -0400, Jason Merrill wrote:
> On 5/22/25 8:22 AM, Nathaniel Shead wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk/15?
> >
> > (Also is renaming the old test OK/appropriate? Or should I keep it
> > before and just name the new tests as t
On 5/22/25 8:22 AM, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk/15?
(Also is renaming the old test OK/appropriate? Or should I keep it
before and just name the new tests as tls1/2, with a comment referring
to pr113292?)
-- >8 --
The PR notes that we m
If we see a promoted subreg and TRULY_NOOP_TRUNCATION says the
truncation is not a noop, then all bits of the inner reg are live. We
cannot reduce the live mask to that of the mode of the subreg.
gcc/ChangeLog:
PR rtl-optimization/120050
* ext-dce.cc (ext_dce_process_uses): Break
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 initialization
default-initialization of extents,
that you have noticed, standard requires them to be value-initialized, and
add corresponding test?
On 5/9/25 11:37 AM, Simon Martin wrote:
Several gcc_assert through the C++ front-end involve seen_error (), that
does not take into account errors that were turned into warnings due to
-fpermissive or -Wtemplate-body.
Running the full C++ testsuite when forcing the use of -fpermissive
leads to I
2025-05-22 Kishan Parmar
* MAINTAINERS: Add myself to write after approval.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8993d176c22..ac7e4de112e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -717,6 +717,7 @@ Maxim Ostapenko
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 for such modes.
For this to work under -ffp-contract=on, we either ne
Unrestricted FMA contraction, combined with optimizations that create
copies of expressions, is causing hard-to-debug issues such as PR106902.
Since we implement conformant contraction now, switch C and C++ from
-ffp-contract=fast to either =off (under -std=c[++]NN like before, also
for C++ now), o
Hi Jakub,
On 21/05/2025 14:46, Christopher Bazley wrote:
Hi Jakub,
Thanks for your review.
On 21/05/2025 13:51, Jakub Jelinek wrote:
On Wed, May 21, 2025 at 01:42:01PM +0100, Christopher Bazley wrote:
On 21/05/2025 12:26, Christopher Bazley wrote:
Hi Joseph,
Thanks for reviewing my patch.
On 21/05/25 11:07 +0200, Tomasz Kamiński wrote:
This patch implements C++26 function_ref as specified in P0792R14,
with correction for constraints for constructor accepting nontype_t
parameter from LWG 4256.
As function_ref may store a pointer to the const object, __Ptrs::_M_obj is
changed to co
Status
==
The GCC 14 branch is open again for regression and documentation fixes.
Quality Data
Priority # Change from last report
--- ---
P10- 1
P2 603- 15
P3 133+ 23
P4
On Fri, May 23, 2025 at 01:40:20PM +0200, Richard Biener wrote:
> On Fri, 23 May 2025, Richard Biener wrote:
>
> > The following makes update_web_docs_git work on branches without
> > libgdiagnostic.
> >
> > I'm re-running update_web_docs_git with this, OK if it succeeds now?
>
> One more bit, t
On 23/05/25 10:03 +0100, Jonathan Wakely wrote:
On 22/05/25 14:50 +0200, Tomasz Kamiński wrote:
From: Jonathan Wakely
This papers implements C++26 std::indirect as specified
in P3019 with amendment to move assignment from LWG 4251.
PR libstdc++/119152
libstdc++-v3/ChangeLog:
---
Jakub poined out I'd forgotten the #cxx20-iterators on the new link.
And I've just realised it's a fragment not an anchor, so the commit
message is wrong, oops.
Pushed to wwwdocs.
htdocs/gcc-14/porting_to.html | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/htdocs/g
---
Pushed to wwwdocs.
htdocs/gcc-14/porting_to.html | 10 ++
htdocs/gcc-15/porting_to.html | 61 +++
2 files changed, 71 insertions(+)
diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index 2d8eaf3a..e8c2869b 100644
--- a/htdocs/gcc
On Fri, 23 May 2025, Richard Biener wrote:
> The following makes update_web_docs_git work on branches without
> libgdiagnostic.
>
> I'm re-running update_web_docs_git with this, OK if it succeeds now?
One more bit, the find command also fails.
OK?
Richard.
>From 97b55be8f9bb5d822371e463dff3bbe
On Fri, May 23, 2025 at 01:34:35PM +0200, Richard Biener wrote:
> The following makes update_web_docs_git work on branches without
> libgdiagnostic.
>
> I'm re-running update_web_docs_git with this, OK if it succeeds now?
>
> Thanks,
> Richard.
>
> maintainer_scripts/
> * update_web_docs_g
The following makes update_web_docs_git work on branches without
libgdiagnostic.
I'm re-running update_web_docs_git with this, OK if it succeeds now?
Thanks,
Richard.
maintainer_scripts/
* update_web_docs_git: Conditionalize libgdiagnostic processing
on presence.
---
maintainer-
On Fri, 2025-03-07 at 14:14 +0800, Lulu Cheng wrote:
> By default, vectorization is not enabled on LoongArch,
> resulting in the failure of these two test cases.
Hmm, but wouldn't every test in the vect/ directory automatically get -
mlsx (from DEFAULT_VECTCFLAGS in lib/target-supports.exp)?
>
>
On Fri, May 23, 2025 at 11:10:46AM +0200, Tobias Burnus wrote:
> OpenMP/C++: Avoid ICE for BIND_EXPR with empty BIND_EXPR_BLOCK [PR120413]
>
> PR c++/120413
>
> gcc/cp/ChangeLog:
>
> * semantics.cc (finish_omp_target_clauses_r): Handle
> BIND_EXPR with empty BIND_EXPR_BLOCK.
>
Hi Joseph,
> Add references to C23 subclauses to the documentation of
> implementation-defined behavior, and new entries for
> implementation-defined behavior new in C23; change some references in
> the text to e.g. "C99 and C11" to encompass C23 as well.
>
> Tested with "make info html pdf".
>
>
On Thu, May 22, 2025 at 3:11 AM Jeff Law wrote:
>
>
>
> On 5/18/25 10:38 AM, Andrew Pinski wrote:
> > While working on improving forwprop and removal of
> > forward_propagate_into_gimple_cond/forward_propagate_into_comparison,
> > I came cross a case where we end up with SSA_NAME in the resulting
Committed as r16-838-gb3d07ec7ac2ccd. When adding the testcase
originally in r15-6963-gfdeceba59bee60 seemingly the compile-time
FAIL when nvptx offload compilation is enabled was missed.
That's now fixed by using an effective target, avoiding the FAIL.
That there is an issue with such code was
On Thu, May 22, 2025 at 12:19 PM Richard Sandiford
wrote:
>
> As the rtl.texi documentation of RTX_AUTOINC expressions says:
>
> If a register used as the operand of these expressions is used in
> another address in an insn, the original value of the register is
> used. Uses of the register
This fixes a GCC 12-to-16 Regression related to an
unexpected empty BIND_EXPR_BLOCK, where nonetheless
aBIND_EXPR exists - just by not walking the hence non-existing variables
binding to that block.
Any comments before I commit this to mainline? I also intent to backport
it relatively soonish to
On 22/05/25 14:50 +0200, Tomasz Kamiński wrote:
From: Jonathan Wakely
This papers implements C++26 std::indirect as specified
in P3019 with amendment to move assignment from LWG 4251.
PR libstdc++/119152
libstdc++-v3/ChangeLog:
* include/Makefile.am: Add new header.
*
On 22/05/25 15:56, Richard Sandiford wrote:
External email: Use caution opening links or attachments
writes:
From: Dhruv Chawla
This patch modifies the shift expander to immediately lower constant
shifts without unspec. It also modifies the ADR, SRA and ADDHNB patterns
to match the lower
This patch would like to introduce the combine of vec_dup + vor.vv into
vor.vx on the cost value of GR2VR. The late-combine will take place if
the cost of GR2VR is zero, or reject the combine if non-zero like 1, 15
in test. There will be two cases for the combine:
OK, thanks.
--
Regards
Robin
57 matches
Mail list logo
