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
On Fri, 18 Apr 2025, 20:14 Siva Sai Manchem via Gcc,
wrote:
> Hi Team,
>
> I hope you're doing well.
>
> We wanted to bring to your attention that one of our customers, who is
> utilizing Zscaler services, is currently facing difficulties accessing your
> website. Up
Hi Team,
I hope you're doing well.
We wanted to bring to your attention that one of our customers, who is
utilizing Zscaler services, is currently facing difficulties accessing your
website. Upon reviewing the issue, we found that the website is being
blocked when accessed via Zscaler IPs.
To en
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
On 17/04/2025 12:19, Wasim Khan via Gcc wrote:
>
>
>> -Original Message-
>> From: Richard Earnshaw (lists)
>> Sent: 17 April 2025 14:57
>> To: Wasim Khan ; gcc-h...@gcc.gnu.org;
>> gcc@gcc.gnu.org
>> Subject: Re: memcpy issue with arm-gnu-toolc
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
On 17/04/2025 07:49, Wasim Khan via Gcc wrote:
> Hi,
>
> I have a custom implementation of memcpy() function and don't want to use
> implementation provided by libc.a.
> Things works fine with toolchain version 12.3 and my local implementation in
> utils.c is considere
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
> -Original Message-
> From: Richard Earnshaw (lists)
> Sent: 17 April 2025 14:57
> To: Wasim Khan ; gcc-h...@gcc.gnu.org;
> gcc@gcc.gnu.org
> Subject: Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-
> none-elf
>
> [You don't of
++ 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
I recommend creating a different name for your own memcpy() implementation,
and use that. You may also make it configurable which implementation to use.
On Thu, Apr 17, 2025, 08:51 Wasim Khan via Gcc-help
wrote:
> Hi,
>
> I have a custom implementation of memcpy() function and don'
nking ...
/opt/arm-gnu-toolchain-*-aarch64-none-elf/bin/aarch64-none-elf-gcc \
-nodefaultlibs \
-nostartfiles \
-mcpu=cortex-a55 \
-Wl,--gc-sections \
-Wl,--build-id=none \
-T /opt/test.lds \
-Wl,-Map=/opt/test.map \
-Wl,--no-warn-rwx-seg
Hello,
I'm looking to contribute as a newcomer and came across PR116163 –
RFE: add a linting tool for DejaGnu tests.
I’d like to implement the remaining features mentioned in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116163#c19
If no one is currently working on this, I’d be happy to prepare a p
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
Thanks for the help!
best regards,
Julian
On Mon, Apr 14, 2025 at 7:57 PM Jonathan Wakely wrote:
>
> On Mon, 14 Apr 2025 at 11:53, Julian Waters wrote:
> >
> > Hi Jonathan,
> >
> > Yep, unfortunately #pragma GCC poison is far too restrictive, it
> > doesn&#x
Hello GCC and GNU support, I am the proxy service lead for Lockheed Martin and
something seems to be blocking our traffic when our US users try to reach
https://gcc.gnu.org/onlinedocs/. Our Non-US users do not have the same issues.
Our reserved Zscaler IP Space for US users is the following
On Mon, 14 Apr 2025 at 14:47, Julian Waters wrote:
>
> Hi Jonathan,
>
> Thanks for the suggestion, it seems promising. I switched out the
> error attribute for the warning attribute at first, since they should
> be equivalent except warning just warns instead of erroring. This
> results in the lin
On Mon, 14 Apr 2025 at 11:53, Julian Waters wrote:
>
> Hi Jonathan,
>
> Yep, unfortunately #pragma GCC poison is far too restrictive, it
> doesn't check if it is a function call to that particular banned
> function, it restricts any and all use of that identifier in the code
On Mon, 14 Apr 2025 at 12:57, Jonathan Wakely wrote:
>
> On Mon, 14 Apr 2025 at 11:53, Julian Waters wrote:
> >
> > Hi Jonathan,
> >
> > Yep, unfortunately #pragma GCC poison is far too restrictive, it
> > doesn't check if it is a function call to that par
Hi Jonathan,
Yep, unfortunately #pragma GCC poison is far too restrictive, it
doesn't check if it is a function call to that particular banned
function, it restricts any and all use of that identifier in the code
altogether. Not only does this mean you can't use overloads of a
banne
On Mon, 14 Apr 2025 at 10:11, Julian Waters via Gcc wrote:
>
> Hi all,
>
> A codebase I'm working with has decided that poisoning certain
> standard library functions is necessary, as it explicitly does not use
> those functions unless absolutely necessary for its own rea
support to help with this. Something like:
#pragma GCC forbidden void *malloc(size_t) // Forbids malloc from
being called anywhere
#pragma GCC permitted push
#pragma GCC permitted void *malloc(size_t)
void *ptr = malloc(1); // This callsite must use malloc, bypassing the
usual restriction
#pragma GC
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
Dear Professor Burnus and the Fortran Project Team,
I am writing to sincerely apologize for my late submission of the proposal
for the “Fortran – 2018/202x” project. I understand that the deadline was
April 8th, and I regret not meeting the required timeline.
Due to unforeseen circumstances, I wa
Thank you for trying.
Also if possible can I receive any guidance for next year hopefully. Since
I am new and am learning things.
If possible any guidance would be helpful for my growth
Though I like to work for GCC more are there any other ways which can help
me to contribute.
Thanks for the
Dear Professor Burnus and the Fortran Project Team,
I am writing to sincerely apologize for my late submission of the proposal
for the “Fortran – 2018/202x” project. I understand that the deadline was
April 8th, and I regret not meeting the required timeline.
Due to unforeseen circumstances, I wa
Dear Professor Burnus and the Fortran Project Team,
I hope this message finds you well. I am writing to confirm that my formal
and primary email address for all project-related communications is
peeyushmaurya@gmail.com. Please note that although my previous apology
was sent from peeyushmaurya2
Thank you for your detailed explanation of "dummy parameter" !
>It is still unclear to me what you are trying to accomplish.
>Implicit typying and implicit interfaces are a compile-time
>thing.
...
>An -fcheck=implicit-type option that generates a runtime
>error that does not make sense to m
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
On Mon, Apr 07, 2025 at 02:42:10PM +0800, Gwen Fu wrote:
> Thanks for your reply !
> >The word "parameter" has very a specific meaning in Fortran. The
> >entity that is passed into a function or subroutine is an "actual
> >argument". The entity within the functions associated with the
> >"actual ar
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,
external
libraries.
Implementation Notes:
We first will need to extend the parser to handle specification of the bind
clause.
The files that we’ll need to use for this will be
gcc/c-family/c-pragma.cc<http://c-pragma.cc/>, gcc/c-parser.cc, and
cp/cp-parser.cc<http://cp-parser.cc/> (For ju
Thanks for your reply !
>The word "parameter" has very a specific meaning in Fortran. The
>entity that is passed into a function or subroutine is an "actual
>argument". The entity within the functions associated with the
>"actual argument" is a "dummy argument".
Can I understand "dummy parameters"
classes and ongoing mid-semester examinations). I plan to
> finish it as soon as I get some time. I have set up the development
> environment though. I have installed Debian 12 (multiboot) onto my laptop
> and installed all necessary packages. Newlib and GCC sources are at my hand.
>
>
Hi, I'm sorry about the delay in sharing my proposal, submitting my
proposal for review.
https://docs.google.com/document/d/1Ffaqcm37d6W9IPAoYvg1jYShNjw-YNgaGVEeBW1B8oY/edit?usp=sharing
i.f90 -fcheck=in
> f951: Warning: command-line option ‘-fpreconditions’ is valid for D but not
> for Fortran
> $ gfortran --help=check
> cc1: warning: unrecognized argument to ‘--help=’ option: ‘check’
> So Is this related to the project ?
I've already pointed out that some of
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
external
libraries.
Implementation Notes:
We first will need to extend the parser to handle specification of the bind
clause.
The files that we’ll need to use for this will be
gcc/c-family/c-pragma.cc<http://c-pragma.cc/>, gcc/c-parser.cc, and
cp/cp-parser.cc<http://cp-parser.cc/> (Fo
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 3/19/25 4:14 AM, Georg-Johann Lay wrote:
Am 16.03.25 um 14:51 schrieb Jeff Law via Gcc:
On 3/13/25 5:39 AM, Georg-Johann Lay via Gcc wrote:
There are situations where knowledge about which bits
of a value are (not) set can be used for optimization.
For example in an insn combine pattern
UKZN email disclaimer:
The contents of this e-mail may contain personal information, and/or privileged
information, and/or confidential information. The information contained herein
is therefore only meant for consumption by the recipient mentioned and for the
purpose as specified in the body
On Fri, Apr 4, 2025 at 12:17 AM Robert Dubner wrote:
>
> The COBOL compiler has this routine:
>
> void
> gg_exit(tree exit_code)
> {
> tree the_call =
> build_call_expr_loc(location_from_lineno(),
> builtin_decl_explicit (BUILT_IN_EXIT),
>
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
Am 21.03.25 um 19:16 schrieb Georg-Johann Lay via Gcc:
Am 21.03.25 um 01:02 schrieb Jeff Law:
On 3/19/25 4:14 AM, Georg-Johann Lay wrote:
Am 16.03.25 um 14:51 schrieb Jeff Law via Gcc:
On 3/13/25 5:39 AM, Georg-Johann Lay via Gcc wrote:
There are situations where knowledge about which bits
e. I have set up the development
environment though. I have installed Debian 12 (multiboot) onto my laptop
and installed all necessary packages. Newlib and GCC sources are at my hand.
> Do you have access to a system with an AMD GPU supported by GCC, or any
Nvidia GPU?
Yes, my laptop has an Nvi
I'm working on ensuring that the GIMPLE semantics used by smtgcc are
correct, and I have a lot of questions about the details. I'll be sending
a series of emails with these questions. This first one is about pointers
in general.
Each section starts with a description of the semantics I've impl
libgccjit)?
If not, do you have any idea of how we could do this?
Thanks.From 320d91cd348f6bb2f2b9dbd7760d63a31f48984e Mon Sep 17 00:00:00 2001
From: Guillaume Gomez
Date: Sun, 16 Mar 2025 23:34:02 +0100
Subject: [PATCH] Add support for `access` attribute
---
gcc/c-family/c-attribs.cc | 3
Hi,
I know that PDB support has been worked on in binutils. I thinkt
he missing piece is to get GCC to emit CodeView debug information that
binutils will turn into a PDBm (not sure if the work is complete in
binutils, either).
What's the status of this? I ask because our WIndows offeri
My doubt :
1.Does the compilation option only need to support fortran versions above
9, o5r does it also need to support fortran 77?
2.Regarding parameter checking, *my idea is that after the user creates an
array of a specified size, it is passed into the function as a parameter*.
However, the arr
Hi GCC developers,
I'm sharing the draft proposal for my GSoC project titled "Fortran 2018/202x".
It has already been posted on the Fortran mailing list, where I received
valuable feedback from gfortran developers.
As mentioned on the GCC GSoC page, proposals should also be sh
> 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
Here is my (potentially naive) understanding of how we may implement bind() and
device_type (probably in a follow-up email) in GCC. These are primary parts of
the project that I am interested in. I would be open to exploring the cache
directive as well though would like to start with a limited
Hello!
My name is Carter. I’m looking to become active in the GCC community. I would
of course love to be funded through GSoC (and will most definitely be
submitting a formal proposal) but will contribute regardless of this. I’m
interesting in the OpenACC parts of the posted projects, so
On 23/03/2025 20:26, Toon Moene wrote:
> I had the following message when sending test results to gcc-testresults
> *starting* today (3 times):
>
> Note that the message is generated by *my* exim4 "mail delivery software"
> (Debian Testing) - it is not the *receiving* s
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
t reading from a unsigned char
declaration. Since the
declaration __gg__data_return_code is just 1 byte the 2-byte store
cannot possibly alias it.
Richard.
> Richard.
>
> >
> > > -Original Message-
> > > From: Richard Biener
> > > Sent: Friday, April 4, 2
to implement the LANG_HOOKS_POST_OPTIONS hook and
do
flag_strict_aliasing = 0;
therein.
Richard.
>
> > -Original Message-
> > From: Richard Biener
> > Sent: Friday, April 4, 2025 03:02
> > To: Robert Dubner
> > Cc: GCC Mailing List
> > Subject: Re: COBOL:
Hi Thomas,
Thanks for your detailed response! I've updated the proposal based on the
feedback. Please kindly check it out. Thanks a lot!
Project Goals and Tasks
GCC currently only partially supports the features specified in OpenACC
2.6. This project aims to enhance GCC's OpenACC supp
On Fri, Apr 4, 2025 at 3:37 AM Krister Walfridsson
wrote:
>
> On Thu, 3 Apr 2025, Richard Biener wrote:
>
> > On Thu, Apr 3, 2025 at 2:23 AM Krister Walfridsson via Gcc
> > wrote:
> >>
> >> I have more questions about GIMPLE memory semantics for smtgcc.
&
On Thu, 3 Apr 2025, Richard Biener wrote:
On Thu, Apr 3, 2025 at 2:23 AM Krister Walfridsson via Gcc
wrote:
I have more questions about GIMPLE memory semantics for smtgcc.
As before, each section starts with a description of the semantics I've
implemented (or plan to implement), follow
));
Still, you may try to use the same ECF attributes than gcc/builtins.def..
> Perhaps it is because you are using ECF_TM_PURE when defining the
> built-in in cobol1.cc:
>
> #define ATTR_TMPURE_NORETURN_NOTHROW_LEAF_COLD_LIST
> (ECF_TM_PURE|ECF_NORETURN|ECF_NOTHROW|ECF_LEAF|ECF
"exit", ATTR_TMPURE_NORETURN_NOTHROW_LEAF_COLD_LIST);
In gcc/builtins.def:
DEF_LIB_BUILTIN(BUILT_IN_EXIT, "exit", BT_FN_VOID_INT,
ATTR_NORETURN_NOTHROW_LIST)
So you want ECF_NORETURN and ECF_NOTHROW.
> I stated that poorly. After I generate the GENERIC, and I h
> 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 Thu, Apr 3, 2025 at 2:23 AM Krister Walfridsson via Gcc
wrote:
>
> I have more questions about GIMPLE memory semantics for smtgcc.
>
> As before, each section starts with a description of the semantics I've
> implemented (or plan to implement), followed by concrete question
>
> This expands on implementation details, compares different approaches
> (in-memory vs. RPC-based solutions), and identifies relevant GCC components
> to modify.
>
> 1. Overview of Implementation Approaches
>
> Currently, GCC’s GPU offloading test framework lacks support
I have more questions about GIMPLE memory semantics for smtgcc.
As before, each section starts with a description of the semantics I've
implemented (or plan to implement), followed by concrete questions if
relevant. Let me know if the described semantics are incorrect or
incomplete.
Accessi
, and unused
variables. Can you go into a little more depth on the project? For example
what is GCC internal infrastructure that is currently being used called? Is
it GIMPLE (according to chatgpt)?
I would also like to maybe test this code with maybe an unused variable and
put a breakpoint in the
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
On Tue, Apr 01, 2025 at 10:09:56AM +0200, Martin Jambor wrote:
> The simple fix is to initialize the variable to nullptr in the source,
> of course. :-)
It is a false positive.
gimple *stmt;
...
for (gsi = gsi_last_bb (bb); !gsi_end_p (gsi); gsi_prev (&gsi))
{
stmt = gsi_stmt (gsi);
Hello Piyush.
> I’m resending this email from my university account as my previous
> message isn’t showing in the GCC mailing list archives. I’ve cc’d the
> project mentors in case this email also fails to deliver. Apologies
> for any duplicate notifications, and thank
t; .global Global memory, shared by all threads.
>
> Implemented via 'TARGET_ENCODE_SECTION_INFO', GCC/nvptx then uses
> special-cased instructions for accessing the respective memory regions.
>
> Now, given a 'const' array (with whatever element type; not i
On Tue, Apr 01, 2025 at 09:19:08AM +0200, Richard Biener via Gcc wrote:
> On Tue, Apr 1, 2025 at 12:04 AM Thomas Schwinge
> wrote:
> > In Nvidia PTX, "A state space is a storage area with particular
> > characteristics. All variables reside in some state space. [.
On Mon, Mar 31, 2025 at 9:15 PM Eric Botcazou wrote:
>
> > 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
Dear Sir/Madam,
I just wanted to ask about the build of gcc. I know it is a required step
before applying to GCC for the GSoC 2025. However, I get an error.
Here is the error:
/home/stoplight/GitProjects/GCC-PROJECT/gcc/build/object/./prev-gcc/xg++
-B/home/stoplight/GitProjects/GCC-PROJECT/gcc
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 you please let me know if everything is in order and whether I can
proceed with submitting
I hope you're doing well! I'm incredibly excited about the "GCC Go Escape
Analysis" project for GSoC 2025. I've spent time reviewing past
contributions, including the 2024 work related to Go in GCC, and I’m eager
to build on that progress in a meaningful way.
After going
p to speed if I could, but I don't even know where to start
or look :(
best regards,
Julian
On Mon, Mar 31, 2025 at 8:09 PM Richard Biener
wrote:
>
> On Mon, Mar 31, 2025 at 1:20 PM Julian Waters via Gcc wrote:
> >
> > Hi all,
> >
> > I've been trying to ch
ining works on the 2 platforms, what
are the differences (If any) between Linux and Windows when it comes
to inlining, particularly involving the flatten attribute? Is there a
list of differences that is easily accessible somewhere, or
alternatively is there somewhere in the gcc source where the
he
icate errors.
Background:
I am a sophomore student at San Jose State University, and have been
messing around with compilers lately.
I've previously modified GCC to support C++ exception handling and the
standard library on AVR. I am quite
familiar with C and C++. I've mostly had experience
Snapshot gcc-15-20250330 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250330/
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-20250329 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250329/
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
Simple File System for Nvidia and AMD GPU Code Generation Testing
2. Project Description and Goals
-
This project aims to enhance the GCC testing framework for GPU-targeted
code generation by developing a simple "in-memory" file system or an RPC
mechanism for devices to a
Dear GCC Mentors,
I hope this email finds you well.
My name is Harsh Gupta, and I am a second-year BTech Computer Science and
Design student at Madhav Institute of Technology and Science in Gwalior,
India. I am passionate about systems programming, compilers, and
open-source software. I am
Snapshot gcc-13-20250328 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250328/
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
Hey folks,
My colleague Nicolas Savoire created a compiler reproducer[0] for the
effect -- you can see a side-by-side comparison of code compiled with GCC
8.x and 9.x where 8.x emits fmov instructions and 9.x does not. He further
used this example as a git bisect criteria and eventually found the
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
knowledge of Rust.
I am applying for GSoC 2025 and am particularly interested in the "Rewrite Rust
Lints" project
Am Donnerstag, dem 27.03.2025 um 17:01 -0700 schrieb Bill Wendling via Gcc:
> On Tue, Mar 25, 2025 at 10:13 PM Martin Uecker wrote:
> > Am Dienstag, dem 25.03.2025 um 19:09 -0700 schrieb Bill Wendling:
> > > On Tue, Mar 18, 2025 at 3:04 PM Martin Uecker wrote:
> > > &g
1 - 100 of 10147 matches
Mail list logo
