Hi,
I am a retired software engineer. I'm looking for projects where I might
be useful. I would like to get on your mailing list.
I listened to an interview with Jonathan Wakely on the podcast cppcast
and contributing to the gcc standard library sounded interesting.
Thanks,
> and contributing to the gcc standard library sounded interesting.
Hi Chris, thanks for your interest and for listening to the podcast.
We have a wiki page about the basics of getting started with GCC contributions:
https://gcc.gnu.org/wiki/GettingStarted
That's not specific to the C++ li
Snapshot gcc-16-20250518 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250518/
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-20250517 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250517/
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-20250516 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250516/
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-20250515 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250515/
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
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 mirrors. It has been generated from git commit
r14-11789-gaa4cd614456de6.
I have so far bootstrapped
Status
==
The GCC 14 branch is now frozen for the GCC 14.3 release, a release
candidate is being prepared.
All changes to the branch require release manager approval.
Previous Report
===
https://gcc.gnu.org/pipermail/gcc/2025-April/245990.html
Snapshot gcc-12-20250514 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250514/
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
On Wed, 14 May 2025 at 21:26, Jonathan Wakely wrote:
>
> On Wed, 14 May 2025 at 20:56, ASSI wrote:
> >
> > Jonathan Wakely via Gcc writes:
> > > For 13.4 the link on the https://gcc.gnu.org home page for the gcc 13
> > > status goes to https://gcc.gnu.org/
On Wed, 14 May 2025 at 20:56, ASSI wrote:
>
> Jonathan Wakely via Gcc writes:
> > For 13.4 the link on the https://gcc.gnu.org home page for the gcc 13
> > status goes to https://gcc.gnu.org/pipermail/gcc/2025-April/245992.html
> > which says:
> > "The plan i
On Wed, May 14, 2025 at 09:55:07PM +0200, ASSI wrote:
> That seems appropriate for the GCC Releases document, while the one I
> linked to is advertised to show "future releases and an alternative view
> of the release history". But I get it that it's just not getting an
Jonathan Wakely via Gcc writes:
> For 13.4 the link on the https://gcc.gnu.org home page for the gcc 13
> status goes to https://gcc.gnu.org/pipermail/gcc/2025-April/245992.html
> which says:
> "The plan is to do a release candidate for GCC 13.4 on Thursday, May
> 29th, one wee
Jonathan Wakely via Gcc writes:
> On Wed, 14 May 2025 at 19:12, ASSI wrote:
>>
>>
>> The current schedule as published at
>>
>> https://gcc.gnu.org/develop.html
>>
>> ends with the 16.1 release.
>
> No it doesn't btw - it ends with the 1
n 13.4 is to be expected so I can better plan the
> > releases for Cygwin.
>
> At approximately the same time of year as 11.5 and 12.4 were released.
For 13.4 the link on the https://gcc.gnu.org home page for the gcc 13
status goes to https://gcc.gnu.org/pipermail/gcc/2025-April/245992.ht
On Wed, 14 May 2025 at 19:12, ASSI wrote:
>
>
> The current schedule as published at
>
> https://gcc.gnu.org/develop.html
>
> ends with the 16.1 release.
No it doesn't btw - it ends with the 15.1 release and with stage 1 for
gcc 16, we're still a year away from the
On Wed, 14 May 2025 at 19:12, ASSI wrote:
>
>
> The current schedule as published at
>
> https://gcc.gnu.org/develop.html
>
> ends with the 16.1 release. Is there an updated / extended version
> available that shows the planned releases for the next half year at
> least?
No, but you can extrapol
The current schedule as published at
https://gcc.gnu.org/develop.html
ends with the 16.1 release. Is there an updated / extended version
available that shows the planned releases for the next half year at
least? Specifically, I would like to know if (and when) a 12.5 is
planned and when 13.4
Hello,
I am pleased to announce that we will have as many as six
contributors working on GCC as part of their Google Summer of Code
(GSoC) projects in 2025! In no particular order:
- Arijit Kumar Das will work on implementing a simple in-memory file
system for running offloading tests on
t; optimization — instead of the usual serial approach, and potentially
> > leveraging *GPU acceleration* (like CUDA) for this.
> >
> > I was wondering if this concept has been explored in GCC, or if there are
> > any existing resources, discussions, or directions I could look
rated compilation
database (the JSON file). It seems that files located within the GCC directory,
such as fold-const-call.cc, are not included. This is curious because these
specific files are not typically compiled directly by xgcc or xg++, yet one
might expect them to be captured if they are part o
Yuao Ma via Gcc writes:
> Hello GCC developers,
> I am trying to generate a compile_commands.json file for the GCC source code.
> This file is very useful for various development tools and IDE integrations.
> Since GCC uses a Makefile-based build system, I attempted to use be
Hello GCC developers,
I am trying to generate a compile_commands.json file for the GCC source code.
This file is very useful for various development tools and IDE integrations.
Since GCC uses a Makefile-based build system, I attempted to use bear
(https://github.com/rizsotto/Bear) to capture the
On Tue, May 13, 2025 at 12:51 PM Andrew Stubbs wrote:
>
> On 12/05/2025 15:27, Nikhil Patil via Gcc wrote:
> > Hi Richard,
> >
> > Thank you so much for the reply!
> >
> > You're absolutely right about using CPU threads. I’m just really curious
> >
On 12/05/2025 15:27, Nikhil Patil via Gcc wrote:
Hi Richard,
Thank you so much for the reply!
You're absolutely right about using CPU threads. I’m just really curious
about whether GPU acceleration could somehow be explored for compilation,
even if it’s not traditionally well-suited. I kn
instead of relying on
heuristics. The starting point for these technologies is polyhedral
analysis - I recommend reading about it in addition to a classical compiler
course.
Kind regards,
Dmitry.
пн, 12 мая 2025 г. в 16:31, Nikhil Patil via Gcc :
> Hi Richard,
>
> Thank you so much for th
me to respond!
On Mon, 12 May 2025 at 18:51, Richard Biener
wrote:
> On Mon, May 12, 2025 at 2:55 PM Nikhil Patil via Gcc
> wrote:
> >
> > Hi GCC Team,
> >
> > I'm fairly new to the world of compilers and trying to understand how
> they
> > work in more
On Mon, May 12, 2025 at 2:55 PM Nikhil Patil via Gcc wrote:
>
> Hi GCC Team,
>
> I'm fairly new to the world of compilers and trying to understand how they
> work in more depth. Recently, I started exploring the idea of *parallelizing
> the internal steps of compilation*
Hi GCC Team,
I'm fairly new to the world of compilers and trying to understand how they
work in more depth. Recently, I started exploring the idea of *parallelizing
the internal steps of compilation* — such as parsing, code generation, and
optimization — instead of the usual serial approach
Yahoo Mail: Search, Organize, Conquer
Snapshot gcc-16-20250511 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250511/
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-20250510 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250510/
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-20250509 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250509/
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-20250508 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250508/
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-20250507 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250507/
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
), so this is
> expected.
By the way, there is an open bug report on bugzilla with submitted pathes
to suggest to change it, as operating systems (FreeBSD, Linux distros, others?)
would like to install different versions of GCC simultaneously but the actual
choice causes conflicts.
In ca
On Mai 05 2025, Basile Starynkevitch wrote:
> and to my surprise its libgccjit.h was installed under /usr/local/include/ and
libgccjit.h has always been installed in $(includedir), so this is
expected.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552
Hello all,
On Debian/trixie/x86-64 I did compile GCC-15-20240503 (untarred under
/usr/src/Lang) configured as
'/usr/src/Lang/gcc-15-20250503/configure' '-v' '--prefix=/usr/local' \
'--with-gcc-major-version-only' '--program-suffix=-my-15'
Snapshot gcc-16-20250504 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250504/
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-20250503 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250503/
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-20250502 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250502/
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-20250501 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250501/
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
"Richard Earnshaw (lists) via Gcc" writes:
> On 30/04/2025 18:34, Heiko Eißfeldt wrote:
>>> - FEAT_LRCPC2 (+rcpc2), enabled by default for
>>> + FEAT_RCPC2 (+rcpc2), enabled by default for
>>>
>>> and
>>>
>>>
Hi Heiko,
Thanks for doing this...
> On 30 Apr 2025, at 18:53, Richard Earnshaw (lists) via Gcc
> wrote:
>
> On 30/04/2025 17:23, Heiko Eißfeldt wrote:
>> Hi,
>>
>> here is a patch for some mostly minor typos in
>> https://gcc.gnu.org/gcc-15/changes
Snapshot gcc-12-20250430 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250430/
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
T_RCPC3 instructions, when support for the instructions is
>>
>> These are incorrect. The features really are FEAT_LRCPC2/3.
>>
>> Otherwise, I think these look generally like improvements.
>>
>> R.
>
>
> That is interesting. I did a grep on gcc trunk for
FEAT_LRCPC2/3.
Otherwise, I think these look generally like improvements.
R.
That is interesting. I did a grep on gcc trunk for 'FEAT_.*RCPC' and got
this
./gcc/common/config/aarch64/cpuinfo.h: FEAT_RCPC,
./gcc/common/config/aarch64/cpuinfo.h: FEAT_RCPC2,
./gcc/common/config/aarch64
On 30/04/2025 17:23, Heiko Eißfeldt wrote:
> 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
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 the now outdated
"Note: GCC 15 has not been released ye
Status
==
The gcc-13 branch is open for regression and documentation fixes.
It's time to plan for the GCC 13.4 release following the planned
GCC 14.3 release. The plan is to do a release candidate for GCC 13.4
on Thursday, May 29th, one week after the GCC 14.3 release followed
by the r
Hey folks,
I thought I'll post a follow up here in case it is of wider interest.
First, my colleague Nicolas Savoire did a Git bisect and identified the
commit[0] that stopped GCC from choosing AArch64 FP registers for pointer
storage. He even created a reproducer[1] on Godbolt that show
Status
==
The GCC 14 branch is open for regression and documentation fixes. We
are planning for the GCC 14.3 release on May 22th which means scheduling
a release candidate on May 15th in about two weeks from now.
Please work through your assigned bugs and regression fixes and
backport fixes
ywgrit writes:
> I encountered one problem with loop-im pass.
> I compiled the program dhry2reg which belongs to
> unixbench(https://github.com/kdlucas/byte-unixbench).
>
> The gcc used
> gcc (GCC) 12.3.0
>
> The commands executed as following
> make
> ./Run -c -i
Snapshot gcc-16-20250427 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/16-20250427/
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
I encountered one problem with loop-im pass.
I compiled the program dhry2reg which belongs to unixbench(
https://github.com/kdlucas/byte-unixbench).
The gcc used
gcc (GCC) 12.3.0
The commands executed as following
make
./Run -c -i 1 dhry2reg
The results are shown below.
Dhrystone 2 using
The temporary variable will not be wrote back to memory as there
is no exit of inifinite loop, so we prohibit applying store motion
on loops with no exits.
Signed-off-by: Xin Wang
---
gcc/tree-ssa-loop-im.cc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/tree-ssa-loop-im.cc b/gcc
Signed-off-by: Xin Wang
---
gcc/tree-ssa-loop-im.cc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gcc/tree-ssa-loop-im.cc b/gcc/tree-ssa-loop-im.cc
index 225964c6215..de0450f5192 100644
--- a/gcc/tree-ssa-loop-im.cc
+++ b/gcc/tree-ssa-loop-im.cc
@@ -3355,6 +3355,9
Snapshot gcc-15-20250426 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250426/
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-20250425 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250425/
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 15.1 release tarballs have been created, the releases/gcc-15
branch is open again for regression and documentation bugfixing.
GCC 15.2 can be expected in about two months unless something serious
changes the plans.
Quality Data
Priority # Change
The GCC developers are proud to announce a new major GCC release, 15.1.
The C frontend now defaults to the GNU C23 dialect. Some code needs
porting for this, see https://gcc.gnu.org/gcc-15/porting_to.html#c23
for more details. Some remaining C23 features have been implemented,
as well as some
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 24/04/25 4:30 am, Peter Bergner wrote:
>
> The second release candidate for GCC 15.1 is available from
>
> htt
Snapshot gcc-13-20250424 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250424/
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
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 the event.
Forw
.com
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 the event.
Forwarding this invitation could allow any
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=MjVqczBqZ2x2aWFkZ2QyczNzYTJoMmdwb2VfUjIwMjUwNTI5VDE1MDAwM
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 24/04/25 4:28 am, Peter Bergner wrote:
>
> The first release candidate for GCC 15.1 is available from
>
> https:/
The second release candidate for GCC 15.1 is available from
https://gcc.gnu.org/pub/gcc/snapshots/15.1.0-RC-20250423/
ftp://gcc.gnu.org/pub/gcc/snapshots/15.1.0-RC-20250423/
and shortly its mirrors. It has been generated from git commit
r15-9577-g3483a2b39591db06.
I have so far bootstrapped
Snapshot gcc-15-20250420 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250420/
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-20250419 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250419/
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-20250418 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250418/
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-20250417 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250417/
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
The first release candidate for GCC 15.1 is available from
https://gcc.gnu.org/pub/gcc/snapshots/15.1.0-RC-20250418/
ftp://gcc.gnu.org/pub/gcc/snapshots/15.1.0-RC-20250418/
and shortly its mirrors. It has been generated from git commit
r15-9556-g96171a5cc7b99cb6.
I have so far bootstrapped
Status
==
We have reached zero P1 regressions and branched for the GCC 15
release. This leaves trunk which is to become GCC 16 next year
open for general development, Stage 1, again. Please refrain
from disrupting git master too much so that last-minute fixes
for GCC 15.1 can be staged
We have branched for the GCC 15 release. All changes on the releases/gcc-15
branch require release manager approval now.
Quality Data
Priority # Change from last report
--- ---
P1 - 17
P2 580
++ gcc@gcc.gnu.org
> -Original Message-
> From: Wasim Khan
> Sent: 15 April 2025 12:41
> To: gcc-h...@gcc.gnu.org
> Subject: GCOV issue with GCC-14.2
>
> Hi,
>
> I am using GCOV for test coverage in a project using instructions for
> freestanding environm
Hi, sorry for bumping this again
I forgot to mention that Windows inlining, from what I remember, was
ok before gcc 14 landed. It seemed that only once gcc 14 came about
that the insane inlining started happening. This might point to the
inlining heuristics having changed, but unfortunately gcc
Snapshot gcc-15-20250413 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250413/
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-20250412 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250412/
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-20250411 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250411/
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-20250410 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250410/
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 a lot, Andi!
I’ve submitted the final version of the proposal on the GSoC platform. I
really appreciate your feedback, as well as the input from everyone who
took the time to review and help refine the idea. It made a significant
difference.
I hope for the opportunity to contribute to GCC
Hello
Apologies for sending my draft proposal so close to the deadline. You
can find it here:
https://docs.google.com/document/d/1UL-mGDWyfEjne3f6uEZOI5KG4s9XTP53QZ_LJjoqn-s/edit?usp=sharing
Please share any comments or suggestions you might have. If any
section needs more clarity, do let me know,
Snapshot gcc-15-20250406 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250406/
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
On 2025-04-06 10:46, Eldar Kusdavletov wrote:
Thanks, Andi — I’ve updated the proposal to reflect your feedback,
especially around separating frontend and backend phases. I now
describe the backend instrumentation as building on existing
per-function timevars and focusing on trace formatting and
Snapshot gcc-14-20250405 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250405/
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
hear that LTO support on Windows is behind Linux though. I'd help
> get that up to speed if I could, but I don't even know where to start
> or look :(
You can see what -fuse-linker-plugin says, what gcc/auto-host.h contains
for HAVE_LTO_PLUGIN. I don't know whether the BFD linke
On Mon, Mar 31, 2025 at 11:14:47PM +0300, Eldar Kusdavletov wrote:
> I wanted to follow up on my previous email regarding my interest in
> participating in Google Summer of Code with GCC. I saw the discussion in the
> thread, but it seems there was no final confirmation.
>
> Could
Snapshot gcc-13-20250321 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250321/
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-20250403 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250403/
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
> You can see what -fuse-linker-plugin says, what gcc/auto-host.h contains
> for HAVE_LTO_PLUGIN. I don't know whether the BFD linker (or mold)
> supports linker plugins on windows. I do know that libiberty simple-object
> does not support PE, that is, at _least_ (DWARF) debugin
Snapshot gcc-13-20250404 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250404/
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,
and sorry for a somewhat late reply.
On Fri, Mar 28 2025, Ansh Jaiswar via Gcc wrote:
> Dear GCC Developers,
>
> I am Ansh Jaiswar , a second-year Computer Science student interested in
> compilers and systems programming. I have experience with C/C++ and basic
> kn
On Fri, Apr 04, 2025 at 07:21:47AM +0300, Eldar Kusdavletov wrote:
> Thanks. I’ve submitted a more concrete version of the proposal — attaching it
> here.
>
> I’ve taken a brief look at Clang’s implementation, but the idea isn’t to
> follow
> it exactly — rather, to provide a similar kind of trac
mber
> of passes there At that level you (and likely should) account
> below functions to individual statements and declarations.
> You may also need to limit yourself to specific
> languages (e.g. C/C++ only)
>
> I would separate these two cases in the project plan because
>
On Mon, Mar 31, 2025 at 1:20 PM Julian Waters via Gcc wrote:
>
> Hi all,
>
> I've been trying to chase down an issue that's been driving me insane
> for a while now. It has to do with the flatten attribute being
> combined with LTO. I've heard that flatten a
> On Tue, Apr 1, 2025 at 8:07 PM Jose E. Marchesi
> wrote:
>>
>> Hello Piyush.
> Hello Jose,
>
>> Sounds like a quite good background.
> Thank you!
>
>> Have you built GCC from sources?
> Yes, I have. I built GCC while working on LFS and recently reb
On Tue, Apr 1, 2025 at 8:07 PM Jose E. Marchesi
wrote:
>
> Hello Piyush.
Hello Jose,
> Sounds like a quite good background.
Thank you!
> Have you built GCC from sources?
Yes, I have. I built GCC while working on LFS and recently rebuilt it,
running the test suite while going through
On Wed, Apr 2, 2025 at 6:35 AM Thomas Schwinge wrote:
>
> On 2025-03-31T19:48:16+0530, Astha Pipania via Gcc wrote:
> > I hope you're doing well!
>
> Astha, welcome to GCC!
>
> > I'm incredibly excited about the "GCC Go Escape
> > Analysis&qu
Hi Astha, Ian!
On 2025-03-31T19:48:16+0530, Astha Pipania via Gcc wrote:
> I hope you're doing well!
Astha, welcome to GCC!
> I'm incredibly excited about the "GCC Go Escape
> Analysis" project for GSoC 2025.
... which is listed on
<https://gcc.gnu.org/
1 - 100 of 21442 matches
Mail list logo
