gcc  

Messages by Thread

• 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
• GSoC 2025 – Excited About GCC Go Escape Analysis & Seeking Guidance Astha Pipania via Gcc
  • Re: GSoC 2025 – Excited About GCC Go Escape Analysis & Seeking Guidance Thomas Schwinge
  • Re: GSoC 2025 – Excited About GCC Go Escape Analysis & Seeking Guidance Ian Lance Taylor via Gcc
• Does gcc have different inlining heuristics on different platforms? Julian Waters via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Richard Biener via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Julian Waters via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Richard Biener via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Eric Botcazou via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Richard Biener via Gcc
  • Re: Does gcc have different inlining heuristics on different platforms? Julian Waters via Gcc
• [GSoC] Application feedback Shin Umeda via Gcc
• gcc-15-20250330 is now available GCC Administrator via Gcc
• gcc-14-20250329 is now available GCC Administrator via Gcc
• GSoC: Application Proposal for Simple File System for Nvidia and AMD GPU Code Testing Ambika Sharan via Gcc
  • Re: GSoC: Application Proposal for Simple File System for Nvidia and AMD GPU Code Testing Thomas Schwinge
  • Re: GSoC: Application Proposal for Simple File System for Nvidia and AMD GPU Code Testing Ambika Sharan via Gcc
• Introduction and Interest in GSoC 2025 with GCC Harsh Gupta via Gcc
• gcc-13-20250328 is now available GCC Administrator via Gcc
• [no subject] gage mikeil via Gcc
• GSoC 2025 Introduction & Interest in GCC Rust Front-End Ansh Jaiswar via Gcc
  • Re: GSoC 2025 Introduction & Interest in GCC Rust Front-End Martin Jambor
• gcc-12-20250327 is now available GCC Administrator via Gcc
• [GSoC][Enhance OpenACC support] Uncertain about Cache directive functionality and device_type clause goal Zhang lv via Gcc
  • Re: [GSoC][Enhance OpenACC support] Uncertain about Cache directive functionality and device_type clause goal Thomas Schwinge
  • Re: [GSoC][Enhance OpenACC support] Uncertain about Cache directive functionality and device_type clause goal Zhang lv via Gcc
• [GSoC]Fortran – run-time argument checking Gwen Fu via Gcc
• [RISC-V] vector segment load/store width as a riscv_tune_param Greg McGary
  • Re: [RISC-V] vector segment load/store width as a riscv_tune_param Robin Dapp via Gcc
  • Re: [RISC-V] vector segment load/store width as a riscv_tune_param Jeff Law via Gcc
  • Re: [RISC-V] vector segment load/store width as a riscv_tune_param Greg McGary
  • Re: [RISC-V] vector segment load/store width as a riscv_tune_param Robin Dapp via Gcc
  • Re: [RISC-V] vector segment load/store width as a riscv_tune_param Greg McGary
• [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Eldar Kusdavletov via Gcc
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Jakub Jelinek via Gcc
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Sam James via Gcc
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Eldar Kusdavletov via Gcc
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Andi Kleen
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Andi Kleen
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC waffl3x via Gcc
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Andi Kleen
  • Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC Eldar Kusdavletov via Gcc
• Re: Take A Look At 38,736 Users List of GitLab Catherine Hill via Gcc
• GSoC 2025 Proposal Submission: Type-Based Alias Analysis in GCC using TySan Sumit via Gcc
• message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Toon Moene
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Richard Earnshaw (lists) via Gcc
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Joseph Myers via Gcc
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Toon Moene
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Richard Earnshaw (lists) via Gcc
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Toon Moene
  • Re: message has lines too long for transport - Was: Fwd: Mail delivery failed: returning message to sender Richard Earnshaw (lists) via Gcc
• GSOC 2025 - Fortran - 2018/202x Yuao Ma via Gcc
  • Re: GSOC 2025 - Fortran - 2018/202x Martin Jambor
• gcc-15-20250323 is now available GCC Administrator via Gcc
• gcc-14-20250322 is now available GCC Administrator via Gcc
• Newcomer seeking Guidance on contributing GCC mannem navyasree via Gcc
  • Re: Newcomer seeking Guidance on contributing GCC David Malcolm via Gcc
• libgcc: Disable building shared objects ? Georg-Johann Lay via Gcc
  • Re: libgcc: Disable building shared objects ? Richard Biener via Gcc
  • Re: libgcc: Disable building shared objects ? Georg-Johann Lay via Gcc

• Earlier messages