Snapshot gcc-15-20250920 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250920/
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
Probably the closest you will get is the 0.9 release
https://gcc.gnu.org/pub/gcc/old-releases/gcc-1/
Joe
On Sat, Sep 20, 2025 at 8:16 AM Mark Wielaard wrote:
> Hi Carlos,
>
> On Sat, Sep 20, 2025 at 03:31:44AM +0100, Carlos Jorge Sebastião Moreira
> via Gcc wrote:
> > I ne
Hi Carlos,
On Sat, Sep 20, 2025 at 03:31:44AM +0100, Carlos Jorge Sebastião Moreira via
Gcc wrote:
> I need the source code of GCC 1.0, seem to be not available from gcc
> website.
There is https://gcc.gnu.org/pub/gcc/old-releases/ which contains
various old releases, including gcc 0.9 an
Hello.
My name os Carlos Moreira.
I need the source code of GCC 1.0, seem to be not available from gcc
website.
Thanks
Snapshot gcc-14-20250919 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250919/
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-16-20250914 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250914/
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-13-20250918 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250918/
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, Sep 8, 2025 at 1:57 PM Jonathan Wakely via Gcc wrote:
>
> On Mon, 8 Sept 2025 at 12:02, Manoj Tiwari via Gcc-help
> wrote:
> >
> > Hello Team,
>
> Please don't cross-post to both gcc@gcc.gnu.org and
> gcc-h...@gcc.gnu.org, pick one.
>
> > I
On Mon, 8 Sept 2025 at 12:02, Manoj Tiwari via Gcc-help
wrote:
>
> Hello Team,
Please don't cross-post to both gcc@gcc.gnu.org and
gcc-h...@gcc.gnu.org, pick one.
> I am currently working with gcc version 11.2.0 and would like to understand
> if there are any known issues o
Snapshot gcc-15-20250913 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250913/
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-20250912 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250912/
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 Luke,
> In LLVM we have been carrying out nightly runs of SPEC CPU 2017 and
> llvm-test-suite[1] for Clang on RISC-V hardware. We’ve been using it to find
> areas of improvement and to track performance regressions.
>
> Recently we've also extended it to build and test G
> On 12 Sep 2025, at 22:41, Robin Dapp wrote:
>
> Can lnt also show an absolute best/"best ever" or does that require to set a
> specific baseline run? Also I'm getting
>
> InvalidRequestError("Can't determine which FROM clause to join from, there
> are
> multiple FROMS which can join to t
Hi GCC devs,
In LLVM we have been carrying out nightly runs of SPEC CPU 2017 and
llvm-test-suite[1] for Clang on RISC-V hardware. We’ve been using it to find
areas of improvement and to track performance regressions.
Recently we've also extended it to build and test GCC nightly, whi
Snapshot gcc-13-20250911 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250911/
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
Hello Team,
I am currently working with gcc version 11.2.0 and would like to understand
if there are any known issues or defects in this release excluding security
vulnerabilities.
Specially, I am interested in
1. Functional Bugs
2. Performance related concerns
3. Compatibility Issues
4
Snapshot gcc-16-20250907 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250907/
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-20250906 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250906/
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-20250905 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250905/
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-20250904 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250904/
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 Wed, 2025-09-03 at 18:54 +0200, Basile Starynkevitch wrote:
> Hello
>
> Is there any open source GCC plugin extracting the call graph information?
>
> https://fse.studenttheses.ub.rug.nl/9153/1/hoogendorp10.pdf is relevant (but
> I don't know if there is an open sour
Hello
Is there any open source GCC plugin extracting the call graph information?
https://fse.studenttheses.ub.rug.nl/9153/1/hoogendorp10.pdf is relevant (but I
don't know if there is an open source tool usable on Linux)
Regards.
--
Basile STARYNKEVITCH
8 rue
Snapshot gcc-16-20250831 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250831/
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-20250830 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250830/
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-20250829 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250829/
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-20250828 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250828/
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-16-20250824 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250824/
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-20250823 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250823/
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-20250822 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250822/
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
Ujjwal Shekhar writes:
> Thank you for your reply! This definitely looks interesting, and I can see
> myself using it quite a bit as well.
You're welcome! And thanks for your interest.
>
> As a first step, I’m looking into Clang’s __builtin_dump_struct. In the
> meantime, are there any initia
work that might have been done but not updated yet?
Thanks,
Ujjwal
From: Sam James
Sent: 22 August 2025 00:05
To: Ujjwal Shekhar via Gcc
Cc: Ujjwal Shekhar
Subject: Re: Guidance on potential directions for contributing to GCC
Ujjwal Shekhar via Gcc writes
Snapshot gcc-13-20250821 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250821/
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
Ujjwal Shekhar via Gcc writes:
> Greetings,
> I’m a final-year university student with some extra time this
> semester, and I’d like to contribute to GCC (not as part of
> GSoC). Although I don’t have prior compiler development experience, I
> have strong working knowledge of C/C+
Greetings,
I’m a final-year university student with some extra time this semester, and I’d
like to contribute to GCC (not as part of GSoC). Although I don’t have prior
compiler development experience, I have strong working knowledge of C/C++ and
low-level programming. Previously, I contributed
On Wed, 20 Aug 2025 at 08:40, Claudio Bantaloukas wrote:
>
> I can set up the forge bot user to do a regular sync using the same infra
> used for the PRs.
> Just give the go ahead.
That would be useful, thanks.
gcc-TEST/master and gcc-TEST/trunk should both be sync'd with
gcc
I can set up the forge bot user to do a regular sync using the same infra used
for the PRs.
Just give the go ahead.
From: Mark Wielaard
Date: Wednesday, 20 August 2025 at 01:38
To: Andrew Pinski
Cc: fo...@sourceware.org , gcc@gcc.gnu.org
Subject: Re: Messed up trunk branch on gcc-test on
Hi,
On Tue, Aug 19, 2025 at 04:42:33PM -0700, Andrew Pinski wrote:
> Hi all,
> I accidentally messed up the trunk branch on gcc-test repo on the forge.
> I clicked merge+fastforward button on a pull request thinking it was just a
> rebase for the pull request.
> Since it is jus
Hi all,
I accidentally messed up the trunk branch on gcc-test repo on the forge.
I clicked merge+fastforward button on a pull request thinking it was just a
rebase for the pull request.
Since it is just the test repo, I am not too worried at this stage.
Is there a way to "revert"
Snapshot gcc-16-20250817 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250817/
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-20250816 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250816/
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-20250815 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250815/
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-20250814 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250814/
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-16-20250810 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250810/
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-20250809 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250809/
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-20250808 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250808/
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 GNU Compiler Collection version 15.2 has been released.
GCC 15.2 is a bug-fix release from the GCC 15 branch
containing important fixes for regressions and serious bugs in
GCC 15.1 with more than 123 bugs fixed since the previous release.
This release is available from the FTP servers listed
The GCC 15.2 release is done and the releases/gcc-15 branch is open
for regression and documentation fixes again.
Quality Data
Priority # Change from last report
--- ---
P1 - 1
P2 591- 5
P3
Snapshot gcc-13-20250807 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250807/
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
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 01/08/25 6:35 pm, Richard Biener via Gcc wrote:
> The first release candidate for GCC 15.2 is available from
>
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 01/08/25 6:35 pm, Richard Biener via Gcc wrote:
> The first release candidate for GCC 15.2 is available from
>
Snapshot gcc-16-20250803 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250803/
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-14-20250801 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250801/
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 first release candidate for GCC 15.2 is available from
https://gcc.gnu.org/pub/gcc/snapshots/15.2.0-RC-20250801/
and shortly its mirrors. It has been generated from git commit
r15-10189-ge14a895275d08d.
I have so far bootstrapped and tested the release candidate on
x86_64-linux.
Please
Snapshot gcc-13-20250731 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250731/
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
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
> -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
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
> -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
, 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
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
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
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
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
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
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
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
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
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
> -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
> -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
> 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
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
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
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
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
1 - 100 of 21591 matches
Mail list logo
