Re: New AArch64 maintainers and reviewers appointed
On Wed, Jul 2, 2025 at 8:36 PM David Edelsohn wrote: > > I am pleased to announce that the GCC Steering Committee has appointed Tamar > Christina as AArch64 maintainer. I am pleased to announce that the GCC > Steering Committee has appointed Alex Coplan, Alice Carlotti, Andrew Pinski, > and Wilco Dijkstra as AArch64 reviewers. > > Please join me in congratulating Tamar, Alex, Alice, Andrew, and Wilco on > their new roles. Thanks and congrats to others. > > All, please update your respective listings in the MAINTAINERS file. Updated in r16-1987 . Thanks, Andrew > > Happy hacking! > David >
Re: scan-*-dump-times across multiple functions considered harmful
On 02/07/2025 18:59, David Malcolm wrote:
...
Brainstorming some ideas on other possible approaches on making our
tests less brittle; for context I did some investigation back in 2018
about implementing "optimizations remarks" like clang does: diagnostics
about optimization decisions, so you could have a dg directive like
this on a particular line:
foo (); /* { dg-remark "inlined call to 'foo' into 'bar'" } */
I like the idea. However, it seems unlikely that we can make a
clean switchover in this decade, unless you find one or more
corporate sponsors.
We probably always want dump files without a rigid structure, because
it makes it easier to add debug output when you flesh out a new pass
or a change to an existing one. We can make the calls that generate
the json output also emit output in the dump file, so we won't carry
a doubled maintenance burden; however, this means the current ad-hoc
messages would become more unified; thus the testsuite will have to
be adjusted.
FWIW, even you you were to get rid of the current dump files (which
I think would be stifling for GCC development for the above
reasons), you would have to adjust the testsuite.
So, we could use the json framework for new dump output that is
contributed before or along with the parts of the testsuite that
scan for it, but for any legacy dump output that is scanned for
in the testsuite, that requires to adjust the testsuite. More
than 26K dejagnu scan-*-dump* directives in the gcc15 testsuite.
And you'll have a bit flag day, or a ton of small ones. Plus
all the friction that this will create with porting patches up
and down gcc versions.
That is a lot of thankless work, which I can't imagine doing as a
hobby. And condifering people at the start of their career who
might think of doing some unpaid drudge work in hope of getting
recognition that'll get them some paid work, with paying work
for GCC drying up, they would more likely do something for LLVM,
which also seems to better align with the skills of recent
graduates.
So, unless/until you have (a) corporate sponsor(s) to pay for
the work on the existing testsuite - and that work is
successfully concluded - we will have to find a way to
make the scans of the dump files more maintainable.
In fact, if we can solve the maintenance hassle of having
multiple in a test by making the scan patterns more specific,
so we don't have to split the tests up, that will put us in
better position if/when the transition to a more organized
optimization records system is made.
Re: New AArch64 maintainers and reviewers appointed
> On 3 Jul 2025, at 05:35, David Edelsohn via Gcc wrote: > > I am pleased to announce that the GCC Steering Committee has appointed > Tamar Christina as AArch64 maintainer. I am pleased to announce that the > GCC Steering Committee has appointed Alex Coplan, Alice Carlotti, Andrew > Pinski, and Wilco Dijkstra as AArch64 reviewers. > > Please join me in congratulating Tamar, Alex, Alice, Andrew, and Wilco on > their new roles. Congratulations all! Great to see more review perspectives on aarch64 patches. Thanks, Kyrill > > All, please update your respective listings in the MAINTAINERS file. > > Happy hacking! > David
gcc-13-20250703 is now available
Snapshot gcc-13-20250703 is now available on https://gcc.gnu.org/pub/gcc/snapshots/13-20250703/ and on various mirrors, see https://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 13 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-13 revision f3689dc2061481fa789dbf7b6ab55a8e5f52f198 You'll find: gcc-13-20250703.tar.xz Complete GCC SHA256=1f666bf56953522777a24229f11ff372843e010c368bf3b803059b1f1d8ecf67 SHA1=dfca604d906cb4f3c172fe4de0255edbc6fbce59 Diffs from 13-20250626 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-13 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: connorweston...@yahoo.com Domain binningupbeachcaravanpark.com.au has exceeded the max defers and failures per hour (11/5 (55%)) allowed. Message discarded. Reporting-MTA: dns; cp-rsl04.per01.ds.network Action: failed Final-Recipient: rfc822;connorweston833@yahoo.com Status: 5.0.0
