On Thu, Jul 24, 2025 at 8:40 AM Richard Biener
wrote:
>
> On Thu, Jul 24, 2025 at 2:39 AM magic0826gc via Gcc wrote:
> >
> > Dear GCC Developers,
> > I'm writing to report an observation regarding loop unswitching behavior
> > when compiling the attached co
On Thu, Jul 24, 2025 at 2:39 AM magic0826gc via Gcc wrote:
>
> Dear GCC Developers,
> I'm writing to report an observation regarding loop unswitching behavior when
> compiling the attached code with GCC 15 using -O2 -funswitch-loops
> optimization flags. Here's a detai
Dear GCC Developers,
I'm writing to report an observation regarding loop unswitching behavior when
compiling the attached code with GCC 15 using -O2 -funswitch-loops optimization
flags. Here's a detailed analysis of the issue:
Code Overview:
int
foo(double *a, double *b, double *c,
Snapshot gcc-16-20250720 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250720/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250719 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250719/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
2025年7月17日 2:25:44 JST、Basile Starynkevitch より:
>
>The Cuthour wrote to the GCC mailing list
>
>> I understand that GNU Make and C++ Modules address many current challenges
>> with headers and dependency management.
>>
>> But what I'm suggesting is a build+p
Snapshot gcc-14-20250718 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250718/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> AFAIU, having the shared libraries in separate files means they are
> not "combined" with the program's code. That's how I understand what
> RMS told me back then, in the quote that I brought up.
Nothing in the GCC Runtime Exception says that the "Target Code" consists
of a single file.
Snapshot gcc-13-20250717 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250717/
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
> Date: Thu, 17 Jul 2025 05:23:50 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > I don't see how distributing in the same tarball would solve the
> > problem.
> >
> > S
for several of its features). I
> would then make a single tarball including both Emacs- and
> Grep-related files. Does that mean that I'm not under an obligation
> to provide source code of _both_ Emacs and Grep? I don't think so.
That has nothing to do with the issue here. We&
> Date: Thu, 17 Jul 2025 03:43:29 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > > Yes, but the discussion wasn't about "as a separate file", but as a file
> > > that&
> > Yes, but the discussion wasn't about "as a separate file", but as a file
> > that's part of the distribution of another program.
>
> A shared library is always a separate file.
Yes, of course. What I meant is that it's not *being distributed
separately*. For example, it can be in the same t
> Date: Thu, 17 Jul 2025 02:28:36 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > That's not what RMS told me when I asked him some time ago. He said
> > that, since libgcc DLL an
> That's not what RMS told me when I asked him some time ago. He said
> that, since libgcc DLL and libstdc++ DLL are basically separate files
> and thus separate builds of the libraries, the run-time exception you
> pointed to is not applicable to them. Quoting his response back then:
>
> Ther
> Date: Wed, 16 Jul 2025 19:03:21 +0200
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
> From: David Brown
>
> >> Well they didn't ask about distributing the DLLs :-)
> >
> > They did, indirectly: programs compiled by MinGW GCC are linked
> > agains
>
Hello all,
The Cuthour wrote to the GCC mailing list
> I understand that GNU Make and C++ Modules address many current challenges
> with headers and dependency management.
>
> But what I'm suggesting is a build+package manager tightly integrated with the
> compiler
On 16/07/2025 17:37, Eli Zaretskii via Gcc wrote:
From: Jonathan Wakely
Date: Wed, 16 Jul 2025 16:12:01 +0100
Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
Please stop giving bad advice and direct people to read the
appropriate documentation
> Date: Wed, 16 Jul 2025 17:44:41 +0200
> From: Dennis Luehring via Gcc
>
> Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc:
> > Unless the Windows loader can find them on
> > the end-user's machine, it will refuse to run the program.
>
> the initial q
Am 16.07.2025 um 17:37 schrieb Eli Zaretskii via Gcc:
Unless the Windows loader can find them on
the end-user's machine, it will refuse to run the program.
the initial question was: do they fall under GPL when just using gcc -
how complex or error prone their distribution concepts get
> From: Jonathan Wakely
> Date: Wed, 16 Jul 2025 16:12:01 +0100
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
>
> On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
> >
> > > Please stop giving bad advice and direct people to read the
> > > appropriate d
On Wed, 16 Jul 2025 at 15:59, Eli Zaretskii wrote:
>
> > From: Jonathan Wakely
> > Date: Wed, 16 Jul 2025 15:08:50 +0100
> > Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
> >
> > > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
>
> From: Jonathan Wakely
> Date: Wed, 16 Jul 2025 15:08:50 +0100
> Cc: qifan.z...@xpeedic.com, gcc@gcc.gnu.org
>
> > > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> > > but not if the program is linked to their DLL versions (and th
On Wed, 16 Jul 2025 at 15:06, Jonathan Wakely wrote:
>
> On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote:
> >
> > > Date: Wed, 16 Jul 2025 11:12:44 +0100
> > > Cc: gcc , gcc-help
> > > From: Jonathan Wakely via Gcc
> > >
> > >
On Wed, 16 Jul 2025 at 13:21, Eli Zaretskii wrote:
>
> > Date: Wed, 16 Jul 2025 11:12:44 +0100
> > Cc: gcc , gcc-help
> > From: Jonathan Wakely via Gcc
> >
> > On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
> > >
> > > Dear GCC Team,
> Date: Wed, 16 Jul 2025 06:49:23 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > Not if we are talking about Windows binaries intended to be used by
> > people who don't have GCC in
> Not if we are talking about Windows binaries intended to be used by
> people who don't have GCC installed. (The OP asked about MinGW, which
> is why I bring up this case.) These DLLs are part of the MinGW GCC
> installation, but do not come with the OS OOTB.
But then what t
> Date: Wed, 16 Jul 2025 06:20:42 -0700 (PDT)
> Cc: gcc@gcc.gnu.org, jwakely@gmail.com, qifan.z...@xpeedic.com
> From: ken...@adacore.com (Richard Kenner)
>
> > AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> > but not if the program is link
> AFAIU, this is accurate if libgcc and libstdc++ are linked statically,
> but not if the program is linked to their DLL versions (and therefore
> the DLLs must be distributed with the resulting program). In the
> latter case, the LGPL exception doesn't apply, and distributing these
> DLLs falls u
> Date: Wed, 16 Jul 2025 11:12:44 +0100
> Cc: gcc , gcc-help
> From: Jonathan Wakely via Gcc
>
> On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
> >
> > Dear GCC Team,
>
> Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org,
On Wed, 16 Jul 2025 at 10:06, Qifan.Zhou via Gcc wrote:
>
> Dear GCC Team,
Please don't email both gcc@gcc.gnu.org and gcc-h...@gcc.gnu.org, pick
the appropriate one. You're not discussing development of GCC so this
belongs on the gcc-help list.
Anyway ...
> I hope this mes
Dear GCC Team,
I hope this message finds you well. I'm writing to seek official clarification
regarding the use of GCC compilers in our proprietary, closed-source commercial
software development.
Our specific use case involves:
1.
Using GCC executables (gcc.exe<https://gcc.exe/>, g
On Mon, Jul 14, 2025 at 10:19:43AM +0100, Richard Earnshaw (lists) via Gcc
wrote:
> On 14/07/2025 08:04, Richard Biener via Gcc wrote:
> > On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc
> > wrote:
> >>
> >> Hello Richard,
> >>
> >> Than
On 14/07/2025 08:04, Richard Biener via Gcc wrote:
> On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc wrote:
>>
>> Hello Richard,
>>
>> Thank you for making these announcements, they are very useful and
>> informative. But I have one small request to make. Pl
On Sat, Jul 12, 2025 at 7:06 AM Andrew Marlow via Gcc wrote:
>
> Hello Richard,
>
> Thank you for making these announcements, they are very useful and
> informative. But I have one small request to make. Please include a link to
> the web page that describes the changes from the
Snapshot gcc-16-20250713 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250713/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250712 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250712/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
particular
release, 12.5, the release notes link can be seen from
https://gcc.gnu.org/gcc-12 (the changes are at
https://gcc.gnu.org/gcc-12/changes.html).
On Fri, 11 Jul 2025 at 13:51, Richard Biener wrote:
> The GNU Compiler Collection version 12.5 has been released.
>
> GCC 12.5 is
Snapshot gcc-14-20250711 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250711/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
The releases/gcc-15 branch is open for regression and documentation fixes.
This is now the time to prepare for the GCC 15.2 release - a release
candidate is planned for Friday Aug 1st, three weeks from now, with
the GCC 15.2 release following a week after that.
Please go over reported
The GNU Compiler Collection version 12.5 has been released.
GCC 12.5 is a bug-fix release from the GCC 12 branch
containing important fixes for regressions and serious bugs in
GCC 12.4 with more than 241 bugs fixed since the previous release.
This is also the last release from the GCC 12 branch
The GCC 12 branch is now closed, no further changes can be pushed
there.
Snapshot gcc-13-20250710 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250710/
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
On Mon, 7 Jul 2025, Iain Sandoe wrote:
>
>
> > On 4 Jul 2025, at 08:53, Richard Biener via Gcc wrote:
> >
> > The first release candidate for GCC 12.5 is available from
> >
> > https://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
> > ftp
> On 4 Jul 2025, at 08:53, Richard Biener via Gcc wrote:
>
> The first release candidate for GCC 12.5 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
> ftp://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
>
> and shortly its mirrors
Snapshot gcc-16-20250706 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250706/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250705 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250705/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-14-20250704 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250704/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Status
==
The gcc-12 branch is now frozen for release and closing of
the branch.
Quality Data
Priority # Change from last report
--- ---
P10
P2 572 - 44
P3 112
P4 192
P5
The first release candidate for GCC 12.5 is available from
https://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
ftp://gcc.gnu.org/pub/gcc/snapshots/12.5.0-RC-20250704/
and shortly its mirrors. It has been generated from git commit
r12-11250-gb71ac987cd1499.
I have so far bootstrapped
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
Snapshot gcc-12-20250702 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250702/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-16-20250629 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250629/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250628 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250628/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-14-20250627 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250627/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20250626 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250626/
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
Peter Bergner
libc-al...@sourceware.org
dilfri...@gentoo.org
binut...@sourceware.org
gcc@gcc.gnu.org
g...@sourceware.org
View all guest info
https://calendar.google.com/calendar/event?action=VIEW&eid=MjVqczBqZ2x2aWFkZ2QyczNzYTJoMmdwb2VfUjIwMjUwNzMxVDE1MDAwM
e.l...@linaro.org
berg...@linux.ibm.com
Peter Bergner
libc-al...@sourceware.org
dilfri...@gentoo.org
binut...@sourceware.org
gcc@gcc.gnu.org
g...@sourceware.org
~~//~~
Invitation from Google Calendar: https://calendar.google.com/calendar/
You are receiving this email because you are an attendee on
Snapshot gcc-12-20250625 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250625/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-16-20250622 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250622/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250621 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250621/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-14-20250620 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250620/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20250619 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250619/
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
> -Original Message-
> From: Basile Starynkevitch
> Sent: Thursday, June 19, 2025 11:51
> To: Bob Dubner
> Cc: gcc@gcc.gnu.org
> Subject: GCC harm in ARM
>
> HEllo,
>
>
> Bob Dubner wrote on gcc@
> >
> > Thus, the statement
> >
HEllo,
Bob Dubner wrote on gcc@
>
> Thus, the statement
>
> CALL "foo"
>
> might be the equivalent, implemented in C, of
>
> extern foo(...); //External reference
> foo();
>
> or
>
> static foo(...); // For
Snapshot gcc-12-20250618 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250618/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-16-20250615 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250615/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250614 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250614/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-14-20250613 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250613/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20250612 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250612/
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
Snapshot gcc-12-20250611 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250611/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
x27;t know where GCC will be run from.
Just as ELF RPATHs have $ORIGIN, which is relative the executable itself, I
wonder if we could introduce a variable to spec files which would be the
directory where the spec file is located.
I am not too familiar with spec files, so I wanted to ask here i
Snapshot gcc-16-20250608 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250608/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250607 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250607/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-14-20250606 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250606/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Status
==
The gcc-12 branch open for regression and documentation fixes.
We plan to close the branch with the release of GCC 12.5 where
a release candidate is planned at Jul 4th and the release a
week after, Jul 11th. Note that since this is going to be
the last release from the branch it&#
Snapshot gcc-13-20250605 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250605/
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
Status
==
The GCC 13.4 release tarballs have been created, the releases/gcc-13
branch is open again for regression and documentation bugfixing.
GCC 13.5 can be expected in a year and a few months unless something
serious changes the plans.
Quality Data
Priority
The GNU Compiler Collection version 13.4 has been released.
GCC 13.4 is a bug-fix release from the GCC 13 branch
containing important fixes for regressions and serious bugs in
GCC 13.3 with more than 129 bugs fixed since the previous release.
This release is available from the FTP servers listed
Snapshot gcc-12-20250604 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250604/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
I bootstrapped and tested on Power8 and Power9 BE in both 32-bit and
64-bit modes, and on Power8, Power9 & Power10 LE in 64-bit mode, and
everything looks good.
On 30/05/25 9:16 pm, Jakub Jelinek via Gcc wrote:
> The second release candidate for GCC 13.4 is available from
>
Snapshot gcc-16-20250601 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250601/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250531 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250531/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hello,
I’m working on a new test tool for the eBPF backend under GSoC that
will integrate with the DejaGnu testsuite. I want to share my
implementation plan and get feedback from the community.
The tool executes compiled eBPF programs in a virtual machine and
validates them against the kernel veri
Snapshot gcc-14-20250530 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250530/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hi Heiko,
Thanks for the patch! I've pushed everything except for:
Heiko Eißfeldt writes:
> @@ -832,8 +832,8 @@
> (aarch64-w64-mingw32). At present, this target
> supports C and C++ for base Armv8-A, but with some caveats:
>
> - Although most variadic functions work, the i
The second release candidate for GCC 13.4 is available from
https://gcc.gnu.org/pub/gcc/snapshots/13.4.0-RC-20250530/
ftp://gcc.gnu.org/pub/gcc/snapshots/13.4.0-RC-20250530/
and shortly its mirrors. It has been generated from git commit
r13-9730-gec78a0d9962f144.
I have so far bootstrapped
Snapshot gcc-13-20250529 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250529/
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
Status
==
The GCC 13 branch is now frozen for the GCC 13.4 release, a release
candidate is being prepared.
All changes to the branch require release manager approval.
Quality Data
Priority # Change from last report
--- ---
P1
The first release candidate for GCC 13.4 is available from
https://gcc.gnu.org/pub/gcc/snapshots/13.4.0-RC-20250529/
ftp://gcc.gnu.org/pub/gcc/snapshots/13.4.0-RC-20250529/
and shortly its mirrors. It has been generated from git commit
r13-9726-gaf73c8bf5168848.
I have so far bootstrapped
Snapshot gcc-12-20250528 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250528/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Thanks for the reminder!
I have now adapted the patch.
Greetings, Heiko
--- "GCC 15 Release Series — Changes, New Features, and Fixes - GNU Project.html.org" 2025-04-30 15:09:45.736597984 +0200
+++ "GCC 15 Release Series — Changes, New Features, and Fixes - GNU Project.html&qu
Snapshot gcc-16-20250525 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250525/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 16 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250524 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250524/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Heiko Eißfeldt writes:
> Hi,
>
> here is a patch for some mostly minor typos in
> https://gcc.gnu.org/gcc-15/changes.html.
> My fixes might be wrong of course, so they are just suggestions.
>
> Also, the linked page https://gcc.gnu.org/gcc-15/porting_to.html
> contains
Snapshot gcc-14-20250523 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250523/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
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
The GNU Compiler Collection version 14.3 has been released.
GCC 14.3 is a bug-fix release from the GCC 14 branch
containing important fixes for regressions and serious bugs in
GCC 14.2 with more than 211 bugs fixed since the previous release.
This release is available from the FTP servers listed
Snapshot gcc-13-20250522 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250522/
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
On Thu, May 15, 2025 at 5:09 PM Richard Biener via Gcc wrote:
>
> The first release candidate for GCC 14.3 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/14.3.0-RC-20250515/
> ftp://gcc.gnu.org/pub/gcc/snapshots/14.3.0-RC-20250515/
>
> and shortly its
1 - 100 of 21544 matches
Mail list logo
