Re: GCC 15.1.1 Status Report (2025-07-11)

2025-07-28 Thread Jakub Jelinek via Gcc
for start git rev-list basepoints/gcc-16..master --reverse --perl-regexp --author='^((?!(David Malcolm|GCC Administrator)).*)$' -- libgcobol gcc/cobol gcc/testsuite/cobol.dg ? I think all gccadmin and dmalcolm's commits you don't want to include. And you want to cherry pick it fr

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-28 Thread Robert Dubner
> -Original Message- > From: Thomas Schwinge > Sent: Monday, July 28, 2025 11:05 > To: Robert Dubner > Cc: Richard Biener ; Andreas Schwab ; > David > Malcolm ; gcc@gcc.gnu.org; gcc-patc...@gcc.gnu.org; > James > K. Lowden > Subject: RE: GCC 15.1.1 Sta

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-28 Thread Thomas Schwinge
idn't know, and that's > good. > > I have reached the point where I am convinced that what I would like to do > is not just hard, but impractical. I got to this point: > > git switch -C patched15 gcc/releases/gcc-15 > git cherry-pick -x \ > $(git rev-list ba

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-28 Thread Robert Dubner
> -Original Message- > From: Richard Biener > Sent: Monday, July 28, 2025 04:17 > To: Robert Dubner > Cc: Andreas Schwab ; Thomas Schwinge > ; > David Malcolm ; gcc@gcc.gnu.org; > gcc-patc...@gcc.gnu.org; > James K. Lowden > Subject: RE: GCC 15.1.1 Sta

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-28 Thread Richard Biener via Gcc
, and that's > good. > > I have reached the point where I am convinced that what I would like to do > is not just hard, but impractical. I got to this point: > > git switch -C patched15 gcc/releases/gcc-15 > git cherry-pick -x \ > $(git rev-list basepoints/gcc-1

gcc-16-20250727 is now available

2025-07-27 Thread GCC Administrator via Gcc
Snapshot gcc-16-20250727 is now available on https://gcc.gnu.org/pub/gcc/snapshots/16-20250727/ 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

Building runtime libraries separately, new GCC packaging in Nixpkgs

2025-07-27 Thread John Ericson via Gcc
Hello, I, like many other people, have had multi-target GCC on the back of my mind for years. For a little background on me, I am a maintainer of Nixpkgs/NixOS who does has done a lot of cross compilation work, and, of course, a single multi-target build is very useful for making cross

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-27 Thread Robert Dubner
that what I would like to do is not just hard, but impractical. I got to this point: git switch -C patched15 gcc/releases/gcc-15 git cherry-pick -x \ $(git rev-list basepoints/gcc-16..gcc/master \ --invert-grep --grep="Daily bump" \ -- libgcobol gcc/cobol gcc/testsuite

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-27 Thread Robert Dubner
Thanks to everybody. I actually did do the more specific searches over a range starting at the gcc-15 starting point; in my frustration I didn't copy the final actual command I used. I thought I needed to start at the original releases/gcc-15 point because that's where we branched

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-27 Thread Richard Biener via Gcc
On Sat, 26 Jul 2025, Robert Dubner wrote: > > > > -Original Message- > > From: Richard Biener > > Sent: Saturday, July 26, 2025 12:06 > > To: Robert Dubner > > Cc: gcc@gcc.gnu.org; gcc-patc...@gcc.gnu.org; James K. Lowden > > > > S

Re: GCC 15.1.1 Status Report (2025-07-11)

2025-07-27 Thread Andreas Schwab
On Jul 27 2025, Thomas Schwinge wrote: > Hi Bob! > > On 2025-07-27T08:55:04+0200, Andreas Schwab wrote: >> On Jul 26 2025, Robert Dubner wrote: >>> Follow-up: After poking around on the internet for inspiration, I used >>> >>> git log >>> bas

Re: GCC 15.1.1 Status Report (2025-07-11)

2025-07-27 Thread Thomas Schwinge
Hi Bob! On 2025-07-27T08:55:04+0200, Andreas Schwab wrote: > On Jul 26 2025, Robert Dubner wrote: >> Follow-up: After poking around on the internet for inspiration, I used >> >> git log >> basepoints/gcc-15~1..HEAD --reverse --grep="^gcc/cobol" --grep=&qu

Re: GCC 15.1.1 Status Report (2025-07-11)

2025-07-26 Thread Andreas Schwab
On Jul 26 2025, Robert Dubner wrote: > Follow-up: After poking around on the internet for inspiration, I used > > git log > basepoints/gcc-15~1..HEAD --reverse --grep="^gcc/cobol" --grep="^libgcobol" > --grep="cobol.dg" git rev-list --reverse --g

gcc-15-20250726 is now available

2025-07-26 Thread GCC Administrator via Gcc
Snapshot gcc-15-20250726 is now available on https://gcc.gnu.org/pub/gcc/snapshots/15-20250726/ 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

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-26 Thread Robert Dubner
> -Original Message- > From: Richard Biener > Sent: Saturday, July 26, 2025 12:06 > To: Robert Dubner > Cc: gcc@gcc.gnu.org; gcc-patc...@gcc.gnu.org; James K. Lowden > > Subject: Re: GCC 15.1.1 Status Report (2025-07-11) > > > > > Am 26.07

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-26 Thread Robert Dubner
> -Original Message- > From: Richard Biener > Sent: Saturday, July 26, 2025 12:06 > To: Robert Dubner > Cc: gcc@gcc.gnu.org; gcc-patc...@gcc.gnu.org; James K. Lowden > > Subject: Re: GCC 15.1.1 Status Report (2025-07-11) > > > > > Am 26.07

Re: GCC 15.1.1 Status Report (2025-07-11)

2025-07-26 Thread Richard Biener via Gcc
> Am 26.07.2025 um 01:31 schrieb Robert Dubner : > > Richard, this message of yours about changes for 15.2 RC has been > percolating in my head since I first saw it. > > So, today I gave it a shot. > > A significant amount of COBOL development has occurred in the fo

RE: GCC 15.1.1 Status Report (2025-07-11)

2025-07-25 Thread Robert Dubner
Richard, this message of yours about changes for 15.2 RC has been percolating in my head since I first saw it. So, today I gave it a shot. A significant amount of COBOL development has occurred in the four months since GCC-15 was released. I just built a patch that brought changes in COBOL from

gcc-14-20250725 is now available

2025-07-25 Thread GCC Administrator via Gcc
Snapshot gcc-14-20250725 is now available on https://gcc.gnu.org/pub/gcc/snapshots/14-20250725/ 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

gcc-13-20250724 is now available

2025-07-24 Thread GCC Administrator via Gcc
Snapshot gcc-13-20250724 is now available on https://gcc.gnu.org/pub/gcc/snapshots/13-20250724/ 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

Re: Inquiry about Loop Unswitching Behavior in GCC 15

2025-07-24 Thread Richard Biener via Gcc
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

Re: Inquiry about Loop Unswitching Behavior in GCC 15

2025-07-23 Thread Richard Biener via Gcc
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

Inquiry about Loop Unswitching Behavior in GCC 15

2025-07-23 Thread magic0826gc via Gcc
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,

gcc-16-20250720 is now available

2025-07-20 Thread GCC Administrator via Gcc
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

gcc-15-20250719 is now available

2025-07-19 Thread GCC Administrator via Gcc
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

Re: GNU cargo (as a plugin to GCC)

2025-07-19 Thread The Cuthour via Gcc
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

gcc-14-20250718 is now available

2025-07-18 Thread GCC Administrator via Gcc
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

Re: Question about GCC license for commercial use

2025-07-17 Thread Richard Kenner via Gcc
> 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.

gcc-13-20250717 is now available

2025-07-17 Thread GCC Administrator via Gcc
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

Re: Question about GCC license for commercial use

2025-07-17 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-17 Thread Richard Kenner via Gcc
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&

Re: Question about GCC license for commercial use

2025-07-17 Thread Eli Zaretskii via Gcc
> 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&

Re: Question about GCC license for commercial use

2025-07-17 Thread Richard Kenner via Gcc
> > 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

Re: Question about GCC license for commercial use

2025-07-17 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-17 Thread Richard Kenner via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

GNU cargo (as a plugin to GCC)

2025-07-16 Thread Basile Starynkevitch
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread David Brown via Gcc
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

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread 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 question was: do they fall under GPL when just using gcc - how complex or error prone their distribution concepts get

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Jonathan Wakely via Gcc
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, >

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Jonathan Wakely via Gcc
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 > > > > > >

Re: Question about GCC license for commercial use

2025-07-16 Thread 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,

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Richard Kenner via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Richard Kenner via Gcc
> 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

Re: Question about GCC license for commercial use

2025-07-16 Thread Eli Zaretskii via Gcc
> 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,

Re: Question about GCC license for commercial use

2025-07-16 Thread 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, pick the appropriate one. You're not discussing development of GCC so this belongs on the gcc-help list. Anyway ... > I hope this mes

Question about GCC license for commercial use

2025-07-16 Thread Qifan.Zhou via Gcc
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

Re: GCC 12.5 Released

2025-07-14 Thread Jakub Jelinek via Gcc
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

Re: GCC 12.5 Released

2025-07-14 Thread Richard Earnshaw (lists) via Gcc
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

Re: GCC 12.5 Released

2025-07-14 Thread Richard Biener via Gcc
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

gcc-16-20250713 is now available

2025-07-13 Thread GCC Administrator via Gcc
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

gcc-15-20250712 is now available

2025-07-12 Thread GCC Administrator via Gcc
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

Re: GCC 12.5 Released

2025-07-11 Thread Andrew Marlow via Gcc
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

gcc-14-20250711 is now available

2025-07-11 Thread GCC Administrator via Gcc
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

GCC 15.1.1 Status Report (2025-07-11)

2025-07-11 Thread Richard Biener via Gcc
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

GCC 12.5 Released

2025-07-11 Thread Richard Biener via Gcc
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

GCC 12 branch is now closed

2025-07-11 Thread Richard Biener via Gcc
The GCC 12 branch is now closed, no further changes can be pushed there.

gcc-13-20250710 is now available

2025-07-10 Thread GCC Administrator via Gcc
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

Re: GCC 12.5 Release Candidate available from gcc.gnu.org

2025-07-07 Thread Richard Biener via Gcc
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

Re: GCC 12.5 Release Candidate available from gcc.gnu.org

2025-07-06 Thread Iain Sandoe
> 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

gcc-16-20250706 is now available

2025-07-06 Thread GCC Administrator via Gcc
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

gcc-15-20250705 is now available

2025-07-05 Thread GCC Administrator via Gcc
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

gcc-14-20250704 is now available

2025-07-04 Thread GCC Administrator via Gcc
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

GCC 12.4.1 Status Report (2025-07-04), branch frozen for release

2025-07-04 Thread Richard Biener via Gcc
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

GCC 12.5 Release Candidate available from gcc.gnu.org

2025-07-04 Thread Richard Biener via Gcc
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

gcc-13-20250703 is now available

2025-07-03 Thread GCC Administrator via Gcc
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

gcc-12-20250702 is now available

2025-07-02 Thread GCC Administrator via Gcc
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

gcc-16-20250629 is now available

2025-06-29 Thread GCC Administrator via Gcc
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

gcc-15-20250628 is now available

2025-06-28 Thread GCC Administrator via Gcc
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

gcc-14-20250627 is now available

2025-06-27 Thread GCC Administrator via Gcc
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

gcc-13-20250626 is now available

2025-06-26 Thread GCC Administrator via Gcc
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

Updated invitation: Office Hours for the GNU Toolchain @ Monthly from 11am to 12pm on the last Thursday (EDT) (gcc@gcc.gnu.org)

2025-06-26 Thread Carlos O'Donell via Gcc
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

Synced invitation: Office Hours for the GNU Toolchain @ Monthly from 11am to 12pm on the last Thursday from Thu May 29 to Wed Jul 30 (EDT) (gcc@gcc.gnu.org)

2025-06-26 Thread Carlos O'Donell via Gcc
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

gcc-12-20250625 is now available

2025-06-25 Thread GCC Administrator via Gcc
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

gcc-16-20250622 is now available

2025-06-22 Thread GCC Administrator via Gcc
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

gcc-15-20250621 is now available

2025-06-21 Thread GCC Administrator via Gcc
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

gcc-14-20250620 is now available

2025-06-20 Thread GCC Administrator via Gcc
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

gcc-13-20250619 is now available

2025-06-19 Thread GCC Administrator via Gcc
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

RE: GCC harm in ARM

2025-06-19 Thread Bob Dubner
> -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 > >

GCC harm in ARM

2025-06-19 Thread Basile Starynkevitch
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

gcc-12-20250618 is now available

2025-06-18 Thread GCC Administrator via Gcc
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

gcc-16-20250615 is now available

2025-06-15 Thread GCC Administrator via Gcc
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

gcc-15-20250614 is now available

2025-06-14 Thread GCC Administrator via Gcc
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

gcc-14-20250613 is now available

2025-06-13 Thread GCC Administrator via Gcc
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

gcc-13-20250612 is now available

2025-06-12 Thread GCC Administrator via Gcc
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

gcc-12-20250611 is now available

2025-06-11 Thread GCC Administrator via Gcc
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

Introducing something like RPATH's $ORIGIN for GCC spec files

2025-06-11 Thread John Ericson via Gcc
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

gcc-16-20250608 is now available

2025-06-08 Thread GCC Administrator via Gcc
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

gcc-15-20250607 is now available

2025-06-07 Thread GCC Administrator via Gcc
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

gcc-14-20250606 is now available

2025-06-06 Thread GCC Administrator via Gcc
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

GCC 12.4.1 Status Report (2025-06-06)

2025-06-06 Thread Richard Biener via Gcc
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&#

gcc-13-20250605 is now available

2025-06-05 Thread GCC Administrator via Gcc
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

GCC 13.4.1 Status Report (2025-06-05)

2025-06-05 Thread Jakub Jelinek via Gcc
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

GCC 13.4 Released

2025-06-05 Thread Jakub Jelinek via Gcc
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

gcc-12-20250604 is now available

2025-06-04 Thread GCC Administrator via Gcc
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

  1   2   3   4   5   6   7   8   9   10   >