gcc  

Messages by Thread

• Question about constructing vector types in GIMPLE pass Hanke Zhang via Gcc
  • Re: Question about constructing vector types in GIMPLE pass Marc Glisse via Gcc
  • Re: Question about constructing vector types in GIMPLE pass Hanke Zhang via Gcc
  • Re: Question about constructing vector types in GIMPLE pass Richard Biener via Gcc
• [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Jonathan Wakely via Gcc
  • Re: Re: [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: Re: [RFC] Linux system call builtins Jonathan Wakely via Gcc
  • Re: [RFC] Linux system call builtins Florian Weimer via Gcc
  • Re: [RFC] Linux system call builtins Alexander Monakov
  • Re: [RFC] Linux system call builtins Florian Weimer via Gcc
  • Re: [RFC] Linux system call builtins Alexander Monakov
  • Re: Re: [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Paul Iannetta via Gcc
  • Re: [RFC] Linux system call builtins Andrew Pinski via Gcc
  • Re: [RFC] Linux system call builtins Paul Iannetta via Gcc
  • Re: [RFC] Linux system call builtins Paul Koning via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Paul Koning via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Paul Floyd via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Szabolcs Nagy via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
  • Re: [RFC] Linux system call builtins Szabolcs Nagy via Gcc
  • [RFC] Linux system call builtins Matheus Afonso Martins Moreira via Gcc
• gcc-14-20240407 is now available GCC Administrator via Gcc
• gcc-13-20240406 is now available GCC Administrator via Gcc
• gcc-12-20240405 is now available GCC Administrator via Gcc
• RE: Project Selection Process and Timeline for GSoC 2024 Vedant5432 via Gcc
  • RE: Project Selection Process and Timeline for GSoC 2024 Martin Jambor
• GSoC "Nothrow detection" proposal review PRANIL DEY via Gcc
  • Re: GSoC "Nothrow detection" proposal review Martin Jambor
• [gimple-ssa] result_decl and ssa_name Pierrick Philippe
  • Re: [gimple-ssa] result_decl and ssa_name Richard Biener via Gcc
  • Re: [gimple-ssa] result_decl and ssa_name Pierrick Philippe
  • Re: [gimple-ssa] result_decl and ssa_name Richard Biener via Gcc
  • Re: [gimple-ssa] result_decl and ssa_name Pierrick Philippe
  • Re: [gimple-ssa] result_decl and ssa_name Richard Biener via Gcc
• Modifying GCC source code Dan via Gcc
• gcc-11-20240404 is now available GCC Administrator via Gcc
• How to get the default values for parameters? Hanke Zhang via Gcc
  • Re: How to get the default values for parameters? Jason Merrill via Gcc
• Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Jan Beulich via Gcc
  • Re: Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Jan Beulich via Gcc
  • Re: Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Jakub Jelinek via Gcc
  • Re: Patches submission policy change Jan Beulich via Gcc
  • Re: Patches submission policy change Richard Biener via Gcc
  • Re: Patches submission policy change Jan Beulich via Gcc
  • Re: Patches submission policy change Joel Sherrill
  • Re: Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Richard Earnshaw (lists) via Gcc
  • Re: Patches submission policy change Jason Merrill via Gcc
  • Re: Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Jonathan Wakely via Gcc
  • Re: Patches submission policy change Simon Marchi via Gcc
  • Re: Patches submission policy change Mark Wielaard
  • Re: Patches submission policy change Simon Marchi via Gcc
  • Re: Patches submission policy change Marc via Gcc
  • Re: Patches submission policy change Christophe Lyon via Gcc
  • Re: Patches submission policy change Mark Wielaard
  • Re: Patches submission policy change Jonathan Wakely via Gcc
  • Re: Patches submission policy change Mark Wielaard
  • Re: Patches submission policy change Jonathan Wakely via Gcc
  • Re: Patches submission policy change Mark Wielaard
• Re: [GSoC] Application RFC + Question - GENERIC dump Richard Biener via Gcc
  • Fwd: [GSoC] Application RFC + Question - GENERIC dump Thor Preimesberger via Gcc
  • Re: [GSoC] Application RFC + Question - GENERIC dump Richard Biener via Gcc
  • Re: [GSoC] Application RFC + Question - GENERIC dump Richard Biener via Gcc
  • Re: [GSoC] Application RFC + Question - GENERIC dump Martin Jambor
  • Re: [GSoC] Application RFC + Question - GENERIC dump Thor Preimesberger via Gcc
• gcc-14-20240331 is now available GCC Administrator via Gcc
• [GSoC] Interest in applying tmpod via Gcc
  • Re: [GSoC] Interest in applying Martin Jambor
• gcc-13-20240330 is now available GCC Administrator via Gcc
• gcc-12-20240329 is now available GCC Administrator via Gcc
• Security warning about xz library compromise Mark Wielaard
  • Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
  • Re: Sourceware mitigating and preventing the next xz-backdoor Sandra Loosemore
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Eggert
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Koning via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Ian Lance Taylor via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Martin Uecker via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Michael Matz via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Koning via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Martin Uecker via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jeffrey Walton via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Michael Matz via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Joel Sherrill
  • Re: Sourceware mitigating and preventing the next xz-backdoor Martin Uecker via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Andreas Schwab
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathan Wakely via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Floyd via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Andreas Schwab
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathon Anderson via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Martin Uecker via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Andrew Sutton via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Richard Biener via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Martin Uecker via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Michael Matz via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor anderson.jonathonm--- via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Andreas Schwab
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathon Anderson via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Koning via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jeffrey Walton via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Eggert
  • Re: Sourceware mitigating and preventing the next xz-backdoor Sam James via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Eggert
  • Re: Sourceware mitigating and preventing the next xz-backdoor Sam James via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Eggert
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathon Anderson via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Sam James via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathon Anderson via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Sam James via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Frank Ch. Eigler via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Frank Ch. Eigler via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Claudio Bantaloukas via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Boris Kolpackov
  • Re: Sourceware mitigating and preventing the next xz-backdoor Andreas Schwab
  • Re: Sourceware mitigating and preventing the next xz-backdoor Guinevere Larsen via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jeffrey Walton via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Koning via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jeffrey Walton via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Florian Weimer via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Joel Sherrill
  • Re: Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
  • Re: Sourceware mitigating and preventing the next xz-backdoor Alejandro Colomar via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
  • Re: Sourceware mitigating and preventing the next xz-backdoor Alejandro Colomar via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Alejandro Colomar via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Alejandro Colomar via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Tom Tromey
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jeff Law via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Mark Wielaard
  • Re: Sourceware mitigating and preventing the next xz-backdoor Toon Moene
  • Re: Sourceware mitigating and preventing the next xz-backdoor Paul Koning via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Ian Lance Taylor via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor Toon Moene
  • Re: Sourceware mitigating and preventing the next xz-backdoor Jonathan Wakely via Gcc
  • Re: Sourceware mitigating and preventing the next xz-backdoor James K. Lowden
• Hello World Toshihide Mitumaru via Gcc
• [no subject] M Hamza Nadeem via Gcc
• gcc-11-20240328 is now available GCC Administrator via Gcc
• A problem about g++ 4.8.5 shaoben zhu via Gcc
  • Re: A problem about g++ 4.8.5 Jonathan Wakely via Gcc
• Initial draft of GSOC proposal - Offloading to a separate process on the same host. Soumya Ranjan via Gcc
  • Re: Initial draft of GSOC proposal - Offloading to a separate process on the same host. Martin Jambor
  • Re: Initial draft of GSOC proposal - Offloading to a separate process on the same host. Soumya Ranjan via Gcc
• GSoC 2024 [Fortran - DO CONCURRENT] Seeking feedback/suggestions for project proposal Anuj Mohite via Gcc
  • Re: GSoC 2024 [Fortran - DO CONCURRENT] Seeking feedback/suggestions for project proposal Martin Jambor
• GSoC Timeline Review Nada Elsayed via Gcc
  • Re: GSoC Timeline Review Nada Elsayed via Gcc
  • Re: GSoC Timeline Review David Malcolm via Gcc
  • Re: GSoC Timeline Review David Malcolm via Gcc
  • Re: GSoC Timeline Review Martin Jambor
  • Re: GSoC Timeline Review Eric Feng via Gcc
• Building Single Tree for a Specific Set of CFLAGS Joel Sherrill via Gcc
  • Re: Building Single Tree for a Specific Set of CFLAGS Christophe Lyon via Gcc
  • Re: Building Single Tree for a Specific Set of CFLAGS Kai Ruottu via Gcc
  • Re: Building Single Tree for a Specific Set of CFLAGS Joel Sherrill
  • Re: Building Single Tree for a Specific Set of CFLAGS Christophe Lyon via Gcc
• unneeded spills of SF values on xtensa with FPU Max Filippov via Gcc
• AutoFDO tools for GCC Eugene Rozenfeld via Gcc
  • Re: AutoFDO tools for GCC Richard Biener via Gcc
  • Re: AutoFDO tools for GCC Andi Kleen via Gcc
  • Re: AutoFDO tools for GCC Jason Merrill via Gcc
  • Re: AutoFDO tools for GCC Snehasish Kumar via Gcc
• Sourceware 2024 - The Plan Mark Wielaard
• re: P2996R2 Jeffrey Cliff via Gcc
  • Re: P2996R2 Jonathan Wakely via Gcc
• gcc-14-20240324 is now available GCC Administrator via Gcc
• Re: [musl] GCC optimizer is provably junk. Here is the evidence. Tomas Volf via Gcc
  • Re: [musl] GCC optimizer is provably junk. Here is the evidence. Rich Felker
• Is --as-needed the default these days? Yuri Kanivetsky via Gcc
  • Re: Is --as-needed the default these days? Jonathan Wakely via Gcc
  • Re: Is --as-needed the default these days? Yuri Kanivetsky via Gcc
  • Re: Is --as-needed the default these days? Andrew Pinski via Gcc
  • Re: Is --as-needed the default these days? Yuri Kanivetsky via Gcc
• "GSoC" M Hamza Nadeem via Gcc
  • Re: "GSoC" Martin Jambor
  • Re: "GSoC" M Hamza Nadeem via Gcc
  • Re: "GSoC" Martin Jambor
  • "GSoC" M Hamza Nadeem via Gcc
• gcc-13-20240323 is now available GCC Administrator via Gcc
• gcc-12-20240322 is now available GCC Administrator via Gcc
• Interest in Contributing to OpenACC Support & Code Offloading Projects for GSOC Soumya Ranjan via Gcc
  • Re: Interest in Contributing to OpenACC Support & Code Offloading Projects for GSOC Martin Jambor
• gcc-11-20240321 is now available GCC Administrator via Gcc
• Office Hours for the GNU Toolchain on 2024-03-28 at 11am EST5EDT. Carlos O'Donell via Gcc
• aliasing Martin Uecker via Gcc
  • Re: aliasing Richard Biener via Gcc
  • Re: aliasing Martin Uecker via Gcc
  • Re: aliasing Martin Uecker via Gcc
  • Re: aliasing Richard Biener via Gcc
  • Re: aliasing Martin Uecker via Gcc
  • Re: aliasing David Brown

• Earlier messages
• Later messages