gcc-12-20240405 is now available

2024-04-05 Thread GCC Administrator via Gcc
Snapshot gcc-12-20240405 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20240405/ 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

Re: Sourceware mitigating and preventing the next xz-backdoor

2024-04-05 Thread Andrew Sutton via Gcc
> > > > > I think the key difference here is that Autotools allows arbitrarily > generated code to be executed at any time. More modern build systems > require the use of specific commands/files to run arbitrary code, e.g. > CMake (IIRC [`execute_process()`][2] and [`ExternalProject`][3]), Meson >

Re: [GSoC] Application RFC + Question - GENERIC dump

2024-04-05 Thread Thor Preimesberger via Gcc
Hey all, I just checked, and it does appear to be the case that proposals can't be updated anymore. I do agree with all the proposed amendments (and would pick to move JSON to HTML), and I'll double-check to see if there's a way to push them into the application. I'm on JST for right now, if my

RE: Project Selection Process and Timeline for GSoC 2024

2024-04-05 Thread Vedant5432 via Gcc
Hello, I am a potential contributor for GSoC 2024, I made a submission for the project Extend the Static Analysis Pass, I was wondering about the process of ranking the proposals and the general timelines when the applicants will be notified if their proposals will be considered potentially? Would

GSoC "Nothrow detection" proposal review

2024-04-05 Thread PRANIL DEY via Gcc
Hello GCC Community, I am Pranil Dey and I had submitted a proposal for the project "Improve nothrow detection in GCC", but as the deadline period was a holiday time I wanted to ask you to review my proposal now. I am already getting familiar with the code but I wanted some pointers for now till se

Re: [GSoC] Application RFC + Question - GENERIC dump

2024-04-05 Thread Martin Jambor
Hello, On Fri, Apr 05 2024, Richard Biener via Gcc wrote: > On Tue, Apr 2, 2024 at 1:16 PM Richard Biener > wrote: >> >> On Tue, Apr 2, 2024 at 11:14 AM Thor Preimesberger via Gcc >> wrote: >> > >> > Forgot to CC the mailing list - mea culpa. >> > >> > -- Forwarded message - >> >

Re: [gimple-ssa] result_decl and ssa_name

2024-04-05 Thread Pierrick Philippe
On 05/04/2024 14:46, Richard Biener wrote: > On Fri, Apr 5, 2024 at 1:59 PM Pierrick Philippe > wrote: >> Hi all, >> >> I do have a question regarding ssa_name and result_decl. >> >> For example on the following gimple function: >> >> int f () >> { >> int x; >> int D.2747; >> int _2; >> >>

Re: [GSoC] Application RFC + Question - GENERIC dump

2024-04-05 Thread Richard Biener via Gcc
On Tue, Apr 2, 2024 at 1:16 PM Richard Biener wrote: > > On Tue, Apr 2, 2024 at 11:14 AM Thor Preimesberger via Gcc > wrote: > > > > Forgot to CC the mailing list - mea culpa. > > > > -- Forwarded message - > > From: Thor Preimesberger > > Date: Tue, Apr 2, 2024 at 5:57 PM > > Su

Re: [gimple-ssa] result_decl and ssa_name

2024-04-05 Thread Richard Biener via Gcc
On Fri, Apr 5, 2024 at 1:59 PM Pierrick Philippe wrote: > > Hi all, > > I do have a question regarding ssa_name and result_decl. > > For example on the following gimple function: > > int f () > { > int x; > int D.2747; > int _2; > >: > x_1 = 42; > _2 = x_1; > >: > : > return _2

[gimple-ssa] result_decl and ssa_name

2024-04-05 Thread Pierrick Philippe
Hi all, I do have a question regarding ssa_name and result_decl. For example on the following gimple function: int f () {   int x;   int D.2747;   int _2;   :   x_1 = 42;   _2 = x_1;   : :   return _2; } On the above example, using the macro SSA_NAME_VAR() on _2 does not yield anything usa

Re: Patches submission policy change

2024-04-05 Thread Christophe Lyon via Gcc
On Thu, 4 Apr 2024 at 10:12, Jan Beulich wrote: > > On 03.04.2024 15:11, Christophe Lyon wrote: > > On Wed, 3 Apr 2024 at 10:30, Jan Beulich wrote: > >> > >> On 03.04.2024 10:22, Christophe Lyon wrote: > >>> Dear release managers and developers, > >>> > >>> TL;DR: For the sake of improving precom

Re: Patches submission policy change

2024-04-05 Thread Christophe Lyon via Gcc
Hi Mark, On 4/4/24 23:35, Mark Wielaard wrote: Hi Christophe, On Wed, Apr 03, 2024 at 10:22:24AM +0200, Christophe Lyon via Gdb wrote: TL;DR: For the sake of improving precommit CI coverage and simplifying workflows, I’d like to request a patch submission policy change, so that we now include