gcc  

Messages by Thread

• Request for Removal of Personal Information from Relevant Messages Homam Alkhateeb
  • Re: Request for Removal of Personal Information from Relevant Messages Jonathan Wakely via Gcc
• GCC development mailing list. Martin C. Foster
  • Re: GCC development mailing list. Jonathan Wakely via Gcc
• [no subject] Grumpy Oman via Gcc
• gcc-16-20250518 is now available GCC Administrator via Gcc
• gcc-15-20250517 is now available GCC Administrator via Gcc
• gcc-14-20250516 is now available GCC Administrator via Gcc
• gcc-13-20250515 is now available GCC Administrator via Gcc
• Target hook TARGET_MODES_TIEABLE_P Stefan Schulze Frielinghaus via Gcc
• Question for maintainers: ARCv3 port feasibility Andrew Stubbs
  • Re: Question for maintainers: ARCv3 port feasibility Richard Biener via Gcc
  • Re: Question for maintainers: ARCv3 port feasibility Andrew Stubbs
  • Re: Question for maintainers: ARCv3 port feasibility Claudiu Zissulescu Ianculescu via Gcc
  • Re: Question for maintainers: ARCv3 port feasibility Oleg Endo via Gcc
  • Re: Question for maintainers: ARCv3 port feasibility Paul Koning via Gcc
  • Re: Question for maintainers: ARCv3 port feasibility Andrew Stubbs
• GCC 14.3 Release Candidate available from gcc.gnu.org Richard Biener via Gcc
• GCC 14.2.1 Status Report (2025-05-15), branch frozen for release Richard Biener via Gcc
• gcc-12-20250514 is now available GCC Administrator via Gcc
• GCC Development Plan update? ASSI
  • Re: GCC Development Plan update? Jonathan Wakely via Gcc
  • Re: GCC Development Plan update? Jonathan Wakely via Gcc
  • Re: GCC Development Plan update? ASSI
  • Re: GCC Development Plan update? Jakub Jelinek via Gcc
  • Re: GCC Development Plan update? Jonathan Wakely via Gcc
  • Re: GCC Development Plan update? Jonathan Wakely via Gcc
  • Re: GCC Development Plan update? Jonathan Wakely via Gcc
  • Re: GCC Development Plan update? ASSI
• Welcome GCC GSoC 2025 participants! Martin Jambor
• Generating compile_commands.json for GCC source code Yuao Ma via Gcc
  • Re: Generating compile_commands.json for GCC source code Sam James via Gcc
  • Re: Generating compile_commands.json for GCC source code Yuao Ma via Gcc
• Question About GPU-Powered Parallel Compilation in GCC Nikhil Patil via Gcc
  • Re: Question About GPU-Powered Parallel Compilation in GCC Richard Biener via Gcc
  • Re: Question About GPU-Powered Parallel Compilation in GCC Nikhil Patil via Gcc
  • Re: Question About GPU-Powered Parallel Compilation in GCC Dmitry Mikushin
  • Re: Question About GPU-Powered Parallel Compilation in GCC Andrew Stubbs
  • Re: Question About GPU-Powered Parallel Compilation in GCC Richard Biener via Gcc
  • Question About GPU-Powered Parallel Compilation in GCC Basile Starynkevitch
• GCC ME sa8210821--- via Gcc
• gcc-16-20250511 is now available GCC Administrator via Gcc
• Пријавите се на Google налог Google via Gcc
• Testing for prototypes generated from Fortran Thomas Koenig via Gcc
  • Re: Testing for prototypes generated from Fortran Harald Anlauf via Gcc
  • Re: Testing for prototypes generated from Fortran Thomas Koenig via Gcc
  • Re: Testing for prototypes generated from Fortran Harald Anlauf via Gcc
  • Re: Testing for prototypes generated from Fortran Richard Biener via Gcc
  • Re: Testing for prototypes generated from Fortran Ben Boeckel via Gcc
• gcc-15-20250510 is now available GCC Administrator via Gcc
• gcc-14-20250509 is now available GCC Administrator via Gcc
• gcc-13-20250508 is now available GCC Administrator via Gcc
• gcc-12-20250507 is now available GCC Administrator via Gcc
• Sourceware Open Office Friday, May 9, 16:00 UTC Mark Wielaard
• a super regular RISC that encodes constants in immediate blocks Michael Clark via Gcc
• Detecting noexceptness Magnus Fromreide via Gcc
• GCC 15 20250503 dont install its libgccjit.h in the same way as GCC 14 Basile Starynkevitch
  • Re: GCC 15 20250503 dont install its libgccjit.h in the same way as GCC 14 Andreas Schwab
  • Re: GCC 15 20250503 dont install its libgccjit.h in the same way as GCC 14 Lorenzo Salvadore via Gcc
• gcc-16-20250504 is now available GCC Administrator via Gcc
• gcc-15-20250503 is now available GCC Administrator via Gcc
• gcc-14-20250502 is now available GCC Administrator via Gcc
• RFC callback attribute Jakub Jelinek via Gcc
• Added Support sa8210821--- via Gcc
• gcc-13-20250501 is now available GCC Administrator via Gcc
• checking=fold seems to take a long, long time (at least on AArch64) ... Toon Moene
  • Re: checking=fold seems to take a long, long time (at least on AArch64) ... Andrew Pinski via Gcc
• gcc-12-20250430 is now available GCC Administrator via Gcc
• Review for gcc-15/changes.html Heiko Eißfeldt
  • Re: Review for gcc-15/changes.html Richard Earnshaw (lists) via Gcc
  • Re: Review for gcc-15/changes.html Heiko Eißfeldt
  • Re: Review for gcc-15/changes.html Richard Earnshaw (lists) via Gcc
  • Re: Review for gcc-15/changes.html Richard Sandiford via Gcc
  • Re: Review for gcc-15/changes.html Kyrylo Tkachov via Gcc
• GCC 13.3.1 Status Report (2025-04-28) Richard Biener via Gcc
• GCC 14.2.1 Status Report (2025-04-28) Richard Biener via Gcc
• gcc-16-20250427 is now available GCC Administrator via Gcc
• [PATCH v2] gcc: do not apply store motion on loop with no exits. Xin Wang via Gcc
  • Re: [PATCH v2] gcc: do not apply store motion on loop with no exits. ywgrit via Gcc
  • Re: [PATCH v2] gcc: do not apply store motion on loop with no exits. Sam James via Gcc
• [PATCH] gcc: do not apply store motion on loop with no exits. 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. Xin Wang via Gcc
• gcc-15-20250426 is now available GCC Administrator via Gcc
• gcc-14-20250425 is now available GCC Administrator via Gcc
• [PATCH] Do not apply store motion on loop with no exits. Xin Wang via Gcc
  • [PATCH] Do not apply store motion on loop with no exits. Xin Wang via Gcc
  • Re: [PATCH] Do not apply store motion on loop with no exits. ywgrit via Gcc
  • Re: [PATCH] Do not apply store motion on loop with no exits. Richard Biener via Gcc
  • [PATCH] Do not apply store motion on loop with no exits. Xin Wang via Gcc
  • [PATCH] Do not apply store motion on loop with no exits. Xin Wang via Gcc
• GCC 15.1.1 Status Report (2025-04-25) Jakub Jelinek via Gcc
• GCC 15.1 Released Jakub Jelinek via Gcc
• gcc-13-20250424 is now available GCC Administrator via Gcc
• Synced invitation: Office Hours for the GNU Toolchain @ Monthly from 11am to 12pm on the last Thursday from Thu Apr 25, 2024 to Wed May 28 (EDT) (gcc@gcc.gnu.org) Carlos O'Donell via Gcc
• Synced invitation: Office Hours for the GNU Toolchain @ Thu Dec 26, 2024 11am - 12pm (EST) (gcc@gcc.gnu.org) codonell--- via Gcc
• Updated invitation: Office Hours for the GNU Toolchain @ Monthly from 11am to 12pm on the last Thursday (EDT) (gcc@gcc.gnu.org) Carlos O'Donell via Gcc
• Second GCC 15.1 Release Candidate available from gcc.gnu.org Jakub Jelinek via Gcc
  • Re: Second GCC 15.1 Release Candidate available from gcc.gnu.org jeevitha via Gcc
• Sourceware infrastructure updates for Q1 2025 Mark Wielaard
• scraperbot protection - Patchwork and Bunsen behind Anubis Mark Wielaard
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Guinevere Larsen via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Jonathan Wakely via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Guinevere Larsen via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Jonathan Wakely via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Aurelien Jarno via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Chris Packham via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Christophe Lyon via Gcc
  • Re: scraperbot protection - Patchwork and Bunsen behind Anubis Frank Ch. Eigler via Gcc
• gcc-15-20250420 is now available GCC Administrator via Gcc
• gcc-14-20250419 is now available GCC Administrator via Gcc
• gcc-13-20250418 is now available GCC Administrator via Gcc
• Accessability of the site gcc.gnu.org Siva Sai Manchem via Gcc
  • Re: Accessability of the site gcc.gnu.org Jonathan Wakely via Gcc
  • Re: Accessability of the site gcc.gnu.org Mark Wielaard
• gcc-12-20250417 is now available GCC Administrator via Gcc
• GCC 15.1 Release Candidate available from gcc.gnu.org Jakub Jelinek via Gcc
  • Re: GCC 15.1 Release Candidate available from gcc.gnu.org jeevitha via Gcc
• GCC 16.0.0 Status Report (2025-04-17) Richard Biener via Gcc
• GCC 15.0.1 Status Report (2025-04-17), branch frozen for release Richard Biener via Gcc
• RE: GCOV issue with GCC-14.2 Wasim Khan via Gcc
• memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf Wasim Khan via Gcc
  • Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf Levente via Gcc
  • Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf Richard Earnshaw (lists) via Gcc
  • RE: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf Wasim Khan via Gcc
  • Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf Richard Earnshaw (lists) via Gcc
• Contributing to PR116163 - DejaGnu Test Linting Tool Piyush Raj via Gcc
• Something Blocking Access from Lockheed Martin External IP Space to gcc.gnu.org justin.colon--- via Gcc
  • Re: Something Blocking Access from Lockheed Martin External IP Space to gcc.gnu.org Mark Wielaard
• Compiler support for forbidding certain methods from being called Basile Starynkevitch
• Compiler support for forbidding certain methods from being called Julian Waters via Gcc
  • Re: Compiler support for forbidding certain methods from being called Jonathan Wakely via Gcc
  • Re: Compiler support for forbidding certain methods from being called Julian Waters via Gcc
  • Re: Compiler support for forbidding certain methods from being called Jonathan Wakely via Gcc
  • Re: Compiler support for forbidding certain methods from being called Jonathan Wakely via Gcc
  • Re: Compiler support for forbidding certain methods from being called Julian Waters via Gcc
  • Re: Compiler support for forbidding certain methods from being called Jonathan Wakely via Gcc
• gcc-15-20250413 is now available GCC Administrator via Gcc
• gcc-14-20250412 is now available GCC Administrator via Gcc
• gcc-13-20250411 is now available GCC Administrator via Gcc
• gcc-12-20250410 is now available GCC Administrator via Gcc
• Apology for Late Proposal Submission – Fortran 2018/202x Project Peeyush Maurya via Gcc
  • Re: Apology for Late Proposal Submission – Fortran 2018/202x Project Martin Jambor
  • Re: Apology for Late Proposal Submission – Fortran 2018/202x Project Peeyush Maurya via Gcc
  • Apology for Late Proposal Submission – Fortran 2018/202x Project Peeyush Maurya via Gcc
• Confirmation of Current Email Address and Apology for Late Submission Peeyush Maurya via Gcc
• Gsoc: Do Concurrent Request for Review ahmad tariq via Gcc
• gcc-15-20250406 is now available GCC Administrator via Gcc
• [GSoC] Initial Draft Carter Weidman via Gcc
  • [GSoC] Initial Draft Carter Weidman via Gcc
• gcc-14-20250405 is now available GCC Administrator via Gcc
• [no subject] Ndlelanhle Makhathini (223038204) via Gcc
• gcc-13-20250321 is now available GCC Administrator via Gcc
• 'TREE_READONLY' for 'const' array in C vs. C++ Thomas Schwinge
  • Re: 'TREE_READONLY' for 'const' array in C vs. C++ Richard Biener via Gcc
  • Re: 'TREE_READONLY' for 'const' array in C vs. C++ Jakub Jelinek via Gcc
  • nvptx: Don't use PTX '.const', constant state space [PR119573] (was: 'TREE_READONLY' for 'const' array in C vs. C++) Thomas Schwinge
  • Re: 'TREE_READONLY' for 'const' array in C vs. C++ Alexander Monakov
• gcc-12-20250403 is now available GCC Administrator via Gcc
• Pointer semantics in GIMPLE Krister Walfridsson via Gcc
  • Re: Pointer semantics in GIMPLE Richard Biener via Gcc
  • Re: Pointer semantics in GIMPLE Krister Walfridsson via Gcc
  • Re: Pointer semantics in GIMPLE Richard Biener via Gcc
  • Re: Pointer semantics in GIMPLE Krister Walfridsson via Gcc
• Remove duplication for the handling of attributes between different frontends Antoni Boucher via Gcc
  • Re: Remove duplication for the handling of attributes between different frontends Richard Biener via Gcc
• Status of PDB support Tom Kacvinsky via Gcc
  • Re: Status of PDB support Jeff Law via Gcc
• GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs Gwen Fu via Gcc
  • Re: GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs Steve Kargl via Gcc
  • Re: GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs Gwen Fu via Gcc
  • Re: GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs Steve Kargl via Gcc
  • Re: GSoC[Fortran Runtime argument check ] Draft of Proposal and some doubts about the needs Gwen Fu via Gcc
• GSoC Draft Proposal Submission: Fortran 2018/202x Yuao Ma via Gcc
• gcc-13-20250404 is now available GCC Administrator via Gcc
• [GSoC] OpenACC bind() and device_type Carter Weidman via Gcc
• GSoC OpenACC Carter Weidman via Gcc
  • Re: GSoC OpenACC Thomas Schwinge
• RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
  • RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
  • Re: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Jose E. Marchesi via Gcc
  • Re: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Jose E. Marchesi via Gcc
  • RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
  • COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
  • Re: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Richard Biener via Gcc
  • RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
  • Re: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Richard Biener via Gcc
  • Re: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Richard Biener via Gcc
  • RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is optimized away. Robert Dubner
• COBOL: A call to builtin_decl_explicit (BUILT_IN_EXIT) is being optimized away Robert Dubner
• Memory access in GIMPLE Krister Walfridsson via Gcc
  • Re: Memory access in GIMPLE Richard Biener via Gcc
  • Re: Memory access in GIMPLE Krister Walfridsson via Gcc
  • Re: Memory access in GIMPLE Richard Biener via Gcc
• Re: [GSoC] Tooling for running BPF GCC tests on a live kernel Jose E. Marchesi via Gcc
  • Re: [GSoC] Tooling for running BPF GCC tests on a live kernel Piyush Raj via Gcc
  • Re: [GSoC] Tooling for running BPF GCC tests on a live kernel Jose E. Marchesi via Gcc
  • Re: [GSoC] Tooling for running BPF GCC tests on a live kernel Piyush Raj via Gcc
• GSoC mandatory step error Leul Abiy via Gcc
  • Re: GSoC mandatory step error Martin Jambor
  • Re: GSoC mandatory step error Jakub Jelinek via Gcc
  • Re: GSoC mandatory step error Thomas Schwinge

• Earlier messages