Using __gnu_lto_slim to detect -fno-fat-lto-objects

2023-02-22 Thread Florian Weimer via Gcc
Can we use the COMMON symbol __gnu_lto_slim to detect -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker plugin)? We currently build the distribution with -ffat-lto-objects, and I want to switch away from that. Packages will need to opt in to -ffat-lto-objects if static objects t

Re: Using __gnu_lto_slim to detect -fno-fat-lto-objects

2023-02-22 Thread Richard Biener via Gcc
On Wed, Feb 22, 2023 at 9:19 AM Florian Weimer via Gcc wrote: > > Can we use the COMMON symbol __gnu_lto_slim to detect > -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker > plugin)? Yes. > We currently build the distribution with -ffat-lto-objects, and I want > to switch away

Re: Using __gnu_lto_slim to detect -fno-fat-lto-objects

2023-02-22 Thread Florian Weimer via Gcc
* Richard Biener: > On Wed, Feb 22, 2023 at 9:19 AM Florian Weimer via Gcc > wrote: >> >> Can we use the COMMON symbol __gnu_lto_slim to detect >> -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker >> plugin)? > > Yes. Great, thanks. >> We currently build the distribution with

Re: Using __gnu_lto_slim to detect -fno-fat-lto-objects

2023-02-22 Thread Richard Biener via Gcc
On Wed, Feb 22, 2023 at 9:28 AM Florian Weimer wrote: > > * Richard Biener: > > > On Wed, Feb 22, 2023 at 9:19 AM Florian Weimer via Gcc > > wrote: > >> > >> Can we use the COMMON symbol __gnu_lto_slim to detect > >> -fno-fat-lto-objects on contemporary GNU/Linux (with the LTO linker > >> plugin

GCC 13.0.1 Status Report (2023-02-22)

2023-02-22 Thread Richard Biener via Gcc
Status == The GCC development branch which will become GCC 13 is in regression and documentation fixing mode (Stage 4) until we reach zero P1 regressions and branch for the release. We are making slow progress towards this goal, new bugs are coming in at a high pace. Please help triaging UNC

GSOC 2023 Contribution Request

2023-02-22 Thread Kritika Rag via Gcc
Hello Everyone! I’m Kritika Rag, a Computer Science pre-final year undergraduate student from India. I’m quite passionate about web development and competitive programming and now I’m looking forward to contributing to open-source projects. I believe that GSOC 2023 would provide me with the best w

[RISC-V] [SIG-toolchain] Meeting will be canceled (Feb 23, 2023)

2023-02-22 Thread jiawei
Hi all, Tomorrow's meeting will be canceled, since there were few new topics to discuss. The next RISC-V GNU Toolchain meeting is collecting topics: https://docs.google.com/document/d/1JSs-BSlPJ3QYbAb-Add1TlbYx0nOT1ur3jcsITIJ01U/edit?usp=sharing Please add what want to discuss in the nex

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

2023-02-22 Thread Jonathan Wakely via Gcc
On Tue, 21 Feb 2023 at 22:55, David Malcolm via Gcc wrote: > IIRC I saw you post a few days ago about trying to build gcc on your M2 > laptop; did you manage this? Building GCC trunk from a git checkout, > and hacking in a "hello world" warning would be a great place to start. > See the guide abo

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

2023-02-22 Thread Shengyu Huang via Gcc
Hi Dave, > But a better place to look would probably be in our bugzilla; see the > links on the wiki page: > https://gcc.gnu.org/wiki/StaticAnalyzer > The "open bugs" list currently has 41 "RFE" bugs ("request for > enhancement" i.e. ideas for new features), some of which might make > suitable

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

2023-02-22 Thread Iain Sandoe
Hi Shengyu, > On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc wrote: > >> IIRC I saw you post a few days ago about trying to build gcc on your M2 >> laptop; did you manage this? Building GCC trunk from a git checkout, >> and hacking in a "hello world" warning would be a great place to start. >>

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

2023-02-22 Thread Iain Sandoe
Hi Shengyu, oops finger-trouble… > On 22 Feb 2023, at 14:53, Iain Sandoe wrote: >> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc wrote: > > Possibly my bad - there are some additional fixes needed for newer Darwin on > the 12 branch (I need to re-release 12.1 Darwin): 12.2… > https://git

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

2023-02-22 Thread David Malcolm via Gcc
On Wed, 2023-02-22 at 15:11 +0100, Shengyu Huang wrote: > Hi Dave, > > > > But a better place to look would probably be in our bugzilla; see > > the > > links on the wiki page: > >  https://gcc.gnu.org/wiki/StaticAnalyzer  > > The "open bugs" list currently has 41 "RFE" bugs ("request for > > enh

Re: GSOC 2023 Contribution Request

2023-02-22 Thread Martin Jambor
Hello Kritika, we are delighted that you decided to apply for GSoC and that you are interested in choosing GCC as the project to contribute to. On Mon, Feb 13 2023, Kritika Rag via Gcc wrote: > Hello Sir/Mam, > > I’m Kritika Rag, a Computer Science pre-final year undergraduate student > from Indi

Re: GSOC 2023 Contribution Request

2023-02-22 Thread Kritika Rag via Gcc
Thank you for your response Martin. Actually I sent this mail a week ago and yeah now the wiki page of gcc has been updated (although I'm very much sure these topics were listed over there but that's totally fine) and so today itself I sent another mail with expressing an interest in working on "C+