We already allow the ABI names for GPR in inline asm clobber list, so
for consistency allow the ABI names for FPR as well.
Reported-by: Yao Zi
gcc/ChangeLog:
* config/loongarch/loongarch.h (ADDITIONAL_REGISTER_NAMES): Add
fa0-fa7, ft0-ft16, and fs0-fs7.
gcc/testsuite/ChangeLog:
The problem here is there was a compare debug since the discriminators
would still take into account debug statements. For the edge we would look
at the first statement after the labels and that might have been a debug
statement.
So we need to skip over debug statements otherwise we could get diff
-Original Message-
From: Robert Dubner
Sent: Saturday, March 15, 2025 22:15
To: Jakub Jelinek
Subject: RE: [PATCH]cobol: create new
gcc/testsuite/cobol.dg/group1/check_88.cob test
> -Original Message-
> From: Jakub Jelinek
> Sent: Saturday, March 15, 2025 20:57
> To: Rober
> -Original Message-
> From: Jakub Jelinek
> Sent: Saturday, March 15, 2025 20:57
> To: Robert Dubner ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH]cobol: create new
> gcc/testsuite/cobol.dg/group1/check_88.cob test
[...]
>
> I don't know what the line length limits in COBOL are (and
On 3/15/25 19:24, Gerald Pfeifer wrote:
On Thu, 13 Mar 2025, Jose E. Marchesi wrote:
This patch adds a link to the Algol 68 front-end development list to
lists.html. OK?
Sure.
+ https://gcc.gnu.org/ml/algol68/";>algol68 is
+ the discussion and development list for the Algol 68 language fr
On Thu, 13 Feb 2025, Georg-Johann Lay wrote:
> Applied the following avr news to gcc-15:
Thanks!
> + Support has been added for the new option
> + href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#index-mno-call-main";
> + >-mno-call-main. Instead of calling
> main,
> +it
On Thu, 13 Mar 2025, Jose E. Marchesi wrote:
> This patch adds a link to the Algol 68 front-end development list to
> lists.html. OK?
Sure.
> + https://gcc.gnu.org/ml/algol68/";>algol68 is
> + the discussion and development list for the Algol 68 language front
> + end of GCC, and the correspo
Hi!
Sorry, my mail got somehow truncated.
On Sun, Mar 16, 2025 at 01:42:52AM +0100, Jakub Jelinek wrote:
> On Sat, Mar 15, 2025 at 04:14:48PM -0500, Robert Dubner wrote:
> > --- /dev/null
> > +++ b/gcc/testsuite/cobol.dg/group1/check_88.cob
> > @@ -0,0 +1,116 @@
> > +*> { dg-do run }
> > +*> { dg
On Sat, Mar 15, 2025 at 04:14:48PM -0500, Robert Dubner wrote:
> --- /dev/null
> +++ b/gcc/testsuite/cobol.dg/group1/check_88.cob
> @@ -0,0 +1,116 @@
> +*> { dg-do run }
> +*> { dg-output "-><-\n" }
> +*> { dg-output "-> <-\n" }
> +*> { dg-output "->\"\"\"<-\n" }
> +*> { dg-output "->000<-\n" }
>
This works on a x86_64-linux machine, although I had to do a complete
rebuild to make it take.
If this meets with the approval of the global reviewers, please apply it,
with a suitable commit message.
The main characteristic of my trying to cope with modifying my workflow
and coping with the GCC
Hello,
I'm attaching the patch for constexpr stable_partition.
Thank you,
--
Giuseppe D'Angelo
From 08b4984cb9a5b4ed3e904698b4a6997bde3088c3 Mon Sep 17 00:00:00 2001
From: Giuseppe D'Angelo
Date: Sat, 15 Mar 2025 00:15:36 +0100
Subject: [PATCH 2/2] libstdc++: add constexpr stable_partition
Thi
Hello,
These two patches complete the implementation of P2562R1 for C++26 (the
paper is called "constexpr Stable Sorting", but these other permutation
algorithms are also included).
You can also find them on Forgejo here:
https://forge.sourceware.org/gcc/gcc-TEST/pulls/44
with some addition
Hi,
The attached patch is a cleanup and improvement of a test that I've
added in r15-8048-gdf0e6509bf7442. Since the test is identical for
shared_ptr and weak_ptr, I've centralized it to reduce future
maintenance, and extended it to cover more cases.
Thank you,
--
Giuseppe D'Angelo
From 3199
On 3/14/25 2:29 PM, Vineet Gupta wrote:
Hi,
On 12/3/24 03:02, Jiawei wrote:
This patch series introduces support for RISC-V Profiles RV20, RV22[1],
and RV23[2][3].The updates enhance compatibility and streamline the process
of leveraging RISC-V Profiles through the -march option. These addit
On Fri, 14 Mar 2025, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs since r15-8025.
> tree_nop_conversion_p doesn't imply TREE_TYPE (@0) is uselessly convertible
> to type, e.g. they could be INTEGER_TYPEs with the same precision but
> different TYPE_SIGN.
>
> The following patch jus
On 3/11/25 9:10 AM, Robin Dapp wrote:
Hi,
in the somewhat convoluted vector code of PR119114 we extracting
a mask value from a vector mask. After some
middle-end simplifications we end up with a value of -2. Its
lowest bit is correctly unset representing "false".
When initializing a bitmak
On 3/13/25 4:19 AM, Robin Dapp wrote:
Hi,
since updating to Fedora 41 I have been seeing ignored python exceptions
like the following when using 'git gcc-verify' = contrib/gcc_changelog/
git_check_commit.py.
Checking 90fcc1f4f1a5537e8d30628895a07cbb2e7e16ff: OK
Exception ignored in: 0x7ff8
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/gcc/de.po
(This file, 'gcc-15-b20250216.de.po', h
> Am 14.03.2025 um 16:19 schrieb Jakub Jelinek :
>
> Hi!
>
> The following patch adds cobol effective target and uses it to guard main
> loop in cobol.dg/dg.exp, so that we don't run the tests on unsupported
> multilibs.
>
> Tested on x86_64-linux with
> make check-cobol RUNTESTFLAGS='--targ
On Thu, Mar 13, 2025 at 08:31:24AM +, Kyrylo Tkachov wrote:
>
> I forgot during the review, but a patch needs a ChangeLog entry.
> Could you provide one please to add to the commit log?
>
I have submitted the patch again in the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2025-Marc
Hello world,
the attached patch, tested with "tidy -e", puts the two parts
mentioning UNSSIGNED into a single paragraph, mentions
extensions to -fc-prototypes and mentions -Wexternal-interface-mismatch.
Comments, suggestions for better wording?
If not, I'll probably commit tomorrow.
Best regar
This destructor declaration serves no purpose, as pointed out by LWG
3903 which was approved at Varna, June 2023.
libstdc++-v3/ChangeLog:
* include/std/span (span::~span): Remove, as per LWG 3903.
---
Tested x86_64-linux.
libstdc++-v3/include/std/span | 2 --
1 file changed, 2 deletion
On Fri, Mar 07, 2025 at 09:41:15PM -0800, Kees Cook wrote:
> On Tue, Feb 18, 2025 at 11:51:41AM -0800, Kees Cook wrote:
> > On Fri, Feb 14, 2025 at 11:21:07AM +0100, Jakub Jelinek wrote:
> > > On Thu, Feb 13, 2025 at 02:10:25PM +0100, Jakub Jelinek wrote:
> > > > Kees, are you submitting this under
* Richard Biener:
> @@ -3869,6 +3867,18 @@ gen_command_line_string (cl_decoded_option *options,
>case OPT_fchecking_:
> /* Ignore these. */
> continue;
> + case OPT_D:
> + case OPT_U:
> + if (startswith (options[i].arg, "_FORTIFY_SOURCE")
> + && (options[
Tested on x86_64-pc-linux-gnu, does this look OK for trunk? We could
use a direct constexpr test for this from_range vector ctor code path,
but that'll be easier once we make the __gnu_test range/iterators
constexpr-friendly. For now I just added an end-to-end test, which
seems good to have too.
+ Aaron
> On Mar 6, 2025, at 4:27 PM, Yeoul Na wrote:
>
> Hi Qing,
>
> Thanks for writing up the RFC and keeping us in the loop. Are you planning to
> add “__self.” to GCC's C++ compiler as well in the future? The problem we
> have with “__self” being a default way of annotating bounds is th
On 10 Mar 2025, at 18:30, Martin Uecker wrote:
> Am Montag, dem 10.03.2025 um 16:45 -0400 schrieb John McCall:
>>> On 10 Mar 2025, at 15:34, Martin Uecker wrote:
> Am Montag, dem 10.03.2025 um 15:00 -0400 schrieb John McCall:
>>> That said, my preference is still to just give preference to
On Thu, Mar 6, 2025 at 6:28 AM Jonathan Wakely wrote:
>
> We need to include in C++23 and later, so that
> __pair_like_convertible_from can use __pair_like.
>
> libstdc++-v3/ChangeLog:
>
> * include/bits/ranges_util.h: Include .
> ---
>
> Very lightly tested on x86_64-linux.
>
> I noticed
On Tue, Mar 11, 2025 at 2:58 AM Richard Biener wrote:
>
> The following makes sure to convert the folded expression to the
> original expression type.
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?
>
> Thanks,
> Richard.
>
> PR middle-end/119204
> * builtins.cc (fold_
Testcases for patterns `((a ^ b) & c) cmp d | a != b -> (0 cmp d | a != b)`
and `(a ^ b) cmp c | a != b -> (0 cmp c | a != b)` were failing on some
targets, like PowerPC.
This patch moves the optimization to reassoc. Doing so, we can now handle
cases where the related conditions appear in an AND e
On Wed, 12 Mar 2025 at 08:05, Richard Biener wrote:
>
> On Tue, Mar 11, 2025 at 5:58 PM Christophe Lyon
> wrote:
> >
> > In https://gcc.gnu.org/contribute.html#patches we ask to use [PR]
> > without the Bugzilla component identifier and with no space between
> > 'PR' and the number, but git_c
I would like to gently ping this.
Thanks,
Filip Kastl
On Mon 2025-02-17 10:52:22, Filip Kastl wrote:
> Hi,
>
> I'm mentioning a change I made in the gcc-15/changes.html file. Validated
> with
> the W3 Validator. Is this ok to be pushed?
>
> Cheers,
> Filip Kastl
>
>
> -- 8< --
>
>
> ---
Hi,
this patch fixes issue with speculation and x264. With profile feedback
we first introduce speculative calls to mc_chroma which is called indirectly.
Then we propagate constants acorss these calls (which is useful transform) but
then speculation_useful_p decides that these speculations are not
Incremental LTO disabled cleanup of output_files since they have to
persist in ltrans cache.
This unintetionally also kept temporary early debug "*.debug.temp.o"
files.
Bootstrapped/regtested on x86_64-linux.
Ok for trunk?
lto-plugin/ChangeLog:
* lto-plugin.c (cleanup_handler): Keep only
Hi!
The following testcase ICEs since r15-8025.
tree_nop_conversion_p doesn't imply TREE_TYPE (@0) is uselessly convertible
to type, e.g. they could be INTEGER_TYPEs with the same precision but
different TYPE_SIGN.
The following patch just adds a convert so that it creates a valid IL
even in thos
> OK.
Thanks Robin.
> Not that I see it as absolute necessity but I don't mind either way.
> We don't just want to tweak the asm checks, though. The code is indeed
> worse than before.
I see, will leave other similar cases like cond_widen_complicate-[4|8] as is.
And it seems no other failures f
Hi Martin,
The C design of VLAs misunderstood dependent typing.
For a program to be validly typed when there are dependent types, you need to
be able to write down the types of any values and variables at program points
where they are in use. This is problematic when there are assignments to
> -Original Message-
> From: Rainer Orth
> Sent: Thursday, March 13, 2025 15:07
> To: James K. Lowden
> Cc: Andreas Schwab ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
>
> Hi James,
>
> > Our intention, tell me if you disagree, i
Hello,
On 01/03/2025 16:50, Giuseppe D'Angelo wrote:
It's also on Forge here
https://forge.sourceware.org/gcc/gcc-TEST/pulls/34
together with a workaround for the ICE (please ignore that, the GCC
mirror hasn't synced the proper fix just yet.)
This has now been committed as r15-7853-gde23192
This patch requires the to be submitted GOMP_interop patch, which
handles the generic libgomp parts. But once it is available, this
patch adds support for the foreign runtimes cuda/cuda_driver/hip
for nvptx and hip/hsa for gcn.
The patch is based on my old RFC patch
https://gcc.gnu.org/pipermail/
On Thu, 13 Mar 2025 20:06:58 +0100
Rainer Orth wrote:
> Hi James,
>
> > Our intention, tell me if you disagree, is that cobol is enabled if
> >
> > 1. --enable-languages=all, and
> > 2. the host and target are "known good", x86_64 or aarch64
>
> you tend to forget there's a world outside of L
On Thu, Mar 6, 2025 at 6:37 AM Jonathan Wakely wrote:
>
> The recently-approved Standard Library Hardening proposal (P3471R4)
> gives pop_front and pop_back member functions hardened preconditions,
> but std::list was missing assertions on them. Our other sequence
> containers do have assertions o
This was added in commit f553b1aaa2b1b925c918e5dcf966290b045321c2
"Refactor duplicated code into 'gcc/testsuite/lib/gcc-dg.exp:find-dg-do-what'",
for use by 'gcc/testsuite/lib/target-supports.exp'. The latter is used by
several test suites, 'gcc/testsuite/lib/gcc-dg.exp' however doesn't get loaded
On Thu, 6 Mar 2025 at 20:13, Jonathan Wakely wrote:
>
> The r15-2326-gea435261ad58ea change missed a static_assert for
> is_move_constructible_v in expected::value()&&. When
> exceptions are enabled, the program is ill-formed if the error type is
> not move constructible, because we can't construct
On 3/7/25 6:45 AM, Nathaniel Shead wrote:
On Thu, Mar 06, 2025 at 11:00:46AM -0500, Jason Merrill wrote:
On 2/8/25 7:32 AM, Nathaniel Shead wrote:
On Fri, Feb 07, 2025 at 11:11:21AM -0500, Jason Merrill wrote:
On 2/7/25 9:28 AM, Nathaniel Shead wrote:
On Fri, Feb 07, 2025 at 08:14:23AM -0500,
We have long had the fold:
/* Pattern match
tem = (sizetype) ptr;
tem = tem & algn;
tem = -tem;
... = ptr p+ tem;
and produce the simpler and easier to analyze with respect to alignment
... = ptr & ~algn; */
But the gimple in gcc.target/aarch64/sve/pr98119.c has a var
Am Freitag, dem 14.03.2025 um 14:42 -0400 schrieb John McCall:
> On 14 Mar 2025, at 14:13, Martin Uecker wrote:
>
> > Am Freitag, dem 14.03.2025 um 10:11 -0700 schrieb David Tarditi:
> > > Hi Martin,
> > >
> > > The C design of VLAs misunderstood dependent typing.
> >
> > They probably did not c
Hello,
sorry to come late to the party.
Le 08/03/2025 à 13:52, Thomas Koenig a écrit :
diff --git a/gcc/fortran/interface.cc b/gcc/fortran/interface.cc
index edec907d33a..e3bc22f25e5 100644
--- a/gcc/fortran/interface.cc
+++ b/gcc/fortran/interface.cc
@@ -5836,6 +5836,8 @@ gfc_get_formal_from_
Just a quick question: would you be interested in receiving the Bio-IT World
Conference & Expo 2025 attendance details?
Attendees: Executive, Director, Manager, Professor, Scientist/Tecnologist,
Sales & Marketing, Assistant and many.
Regards,
Erin Lewis
x86 conditional branch (jcc) target can be either a label or a symbol.
Add a pass to fold tail call with jcc by turning:
jcc .L6
...
.L6:
jmp tailcall
into:
jcc tailcall
Immediately before the pass which turning REG_EH_REGION notes back into
NOTE_INSN_EH_REGI
On Wed, Mar 12, 2025 at 11:53 AM Jonathan Wakely wrote:
> >Could you add a test for functor that is only rvalue-callable (only
> >operator() &&).
> >There was discussion about this case on reflector, so I think it would be
> >good to document that they are not supported.
>
> Like this?
>
Yes. LGT
On Mon, 10 Mar 2025 19:10:26 +0100
Richard Biener wrote:
> > What is the right answer? Designated initializers are part of C99,
> > but weren't added to C++ until C++20
> > (https://en.cppreference.com/w/cpp/language/initialization).
> > Strictly speaking, we should remove all of them, because o
Hi!
As the first of a few patches to enable libstdc++ for GCN, nvptx targets,
and eventually for OpenACC, OpenMP offloading use, I intend to push the
attached 'GCN, nvptx: Allow for "hosted" libstdc++ build'. Any
objections? It's not exactly pretty, but gets the job done. (..., and
some more fi
libstdc++-v3/ChangeLog:
* doc/xml/manual/strings.xml: Tweak formatting. Add example
using lambda.
* doc/html/manual/strings.html: Regenerate.
---
Pushed to trunk.
libstdc++-v3/doc/html/manual/strings.html | 19 ++-
libstdc++-v3/doc/xml/manual/strings.xml
Am Montag, dem 10.03.2025 um 15:00 -0400 schrieb John McCall:
>
...
> That said, my preference is still to just give preference to the field name,
> which sidesteps any need for disambiguation syntax and avoids this whole
> problem where structs can be broken by just adding a global variable tha
I’ve been working on bound-safe extensions for C since 2016. I did the Checked
C work.
Here’s my perspective on the discussion. I think language features should make
the common case easy to use, have concise syntax, and be easy to understand.
The bounds safety extensions will be used by milli
On Thu, Mar 13, 2025 at 05:10:07PM +, Andre Vieira (lists) wrote:
> Apologies for the delay, had been waiting on some other relevant patches to
> go in to make sure we didn't break any valid existing behaviours. It should
> all be working properly now. I think I've also addressed all your comme
Dear all,
the attached patch fixes a bogus error due to a cyclic dependency that
is found because gfc_traverse_expr also descends into the length type
of character variables. If the length is determined by the variable
declaration (e.g. assumed-length), it is pre-determined and cannot
be relevan
Hi Harald,
The solution is to use the auxiliary parameter of gfc_traverse_expr
to control whether to descend into character length or not.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
Looks good to me.
Thanks for the patch!
Best regards
Thomas
I do wonder, since gcobol.3 documents parts of the libgcobol API(?),
whether it should be named libgcobol.3 instead though?
OK?
Thanks,
Richard.
PR cobol/119302
gcc/cobol/
* Make-lang.in: Use $(GCOBOL_INSTALL_NAME) for gcobol.3 manpage
upon install.
---
gcc/cobol/Make
Hi Thomas,
Thomas Koenig wrote:
Attached is a long overdue bug fix, given that OpenMP's declare variant
is supported in gfortran sincer12-4409-g724ee5a0093da4 (Oct 2021).
(and in C/C++ since r10-3744-g94e7f906ca5c73, Oct 2019). While 'omp
declare simd' was already handled in the .mod file, 'de
I wonder why sometimes my line breaks are preserved and at other times all
eaten.
Next try ...
Tobias Burnus wrote:
Hi Thomas,
Thomas Koenig wrote:
Just one question - as this will change the module file, will we still
be compatible with reading gfortran 8 to gfortran 14-written module
file
Hi Tobias,
Attached is a long overdue bug fix, given that OpenMP's declare variant
is supported in gfortran sincer12-4409-g724ee5a0093da4 (Oct 2021). (and
in C/C++ since r10-3744-g94e7f906ca5c73, Oct 2019). While 'omp declare
simd' was already handled in the .mod file, 'declare variant' was no
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
Alternatively, could still mark gnu_inline functions as non-vague, we
just need to do so more aggressively; but given this is specifically to
solve a modules issue I felt may as well keep it confined to there given
your previous comm
"Robin Dapp" writes:
> Hi,
>
> since updating to Fedora 41 I have been seeing ignored python exceptions
> like the following when using 'git gcc-verify' =
> contrib/gcc_changelog/git_check_commit.py.
>
> Checking 90fcc1f4f1a5537e8d30628895a07cbb2e7e16ff: OK
> Exception ignored in:
> Traceback (
Seems as if my distro defaults now to Python 3.13 and that
is more sensitive - or it is due a change in a newer Git module.
At least I the following new exception showed up when using
./contrib/gcc-changelog/git_check_commit.py -v -p Exception ignored in:
Traceback (most
recent call last): Fil
66 matches
Mail list logo
