gcc  

Messages by Thread

• 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
  • Re: libgcc: Disable building shared objects ? Richard Biener via Gcc
  • Re: libgcc: Disable building shared objects ? Georg-Johann Lay via Gcc
• Construction Estimates & 3D Renderings Neil Crocombe via Gcc
• gcc-12-20250320 is now available GCC Administrator via Gcc
• FSF Live Memorabilia Auction - item of interest for Gcc members Eko Kai Alanah Owen via Gcc
• Announce: GNU MPFR 4.2.2 is released Vincent Lefevre
• Undeliverable: Front certainly player travel can third. SMTP-1 postmaster--- via Gcc
• [GSOC 2025] Interests in extending the static analysis pass(es): support for C++ or CPython API zzmic via Gcc
  • Re: [GSOC 2025] Interests in extending the static analysis pass(es): support for C++ or CPython API zzmic via Gcc
• GSoC Interest in enhancing OpenACC support Pau Sum via Gcc
  • Re: GSoC Interest in enhancing OpenACC support Thomas Schwinge
• Remove duplication for the handling of attributes between different frontends in GCC Basile Starynkevitch
• i386 EBCDIC Paul Edwards via Gcc
  • Re: i386 EBCDIC Paul Edwards via Gcc
• Proposed GSoC project to enhance the GCC GNAT Ada front end Tucker Taft via Gcc
  • Re: Proposed GSoC project to enhance the GCC GNAT Ada front end Sam James via Gcc
  • Re: Proposed GSoC project to enhance the GCC GNAT Ada front end Tucker Taft via Gcc
  • Re: Proposed GSoC project to enhance the GCC GNAT Ada front end Martin Jambor
  • Re: Proposed GSoC project to enhance the GCC GNAT Ada front end Tucker Taft via Gcc
  • Re: Proposed GSoC project to enhance the GCC GNAT Ada front end Tucker Taft via Gcc
• Re: Some doubt about participating in GCC community Martin Jambor
  • Re: Some doubt about participating in GCC community Jonathan Wakely via Gcc
  • Re: Some doubt about participating in GCC community Martin Jambor
• Rust: error[E0554]: `#![feature]` may not be used on the stable release channel Toon Moene
  • Re: Rust: error[E0554]: `#![feature]` may not be used on the stable release channel Iain Sandoe via Gcc
  • Re: Rust: error[E0554]: `#![feature]` may not be used on the stable release channel Thomas Schwinge
• [gnu.org #2021668] Robert Joseph Dubner GCC, GDB Craig Topham via RT via Gcc
• Dose "-Wall -Wextra" contain -Wconversion -Wfloat-conversion ? Gwen Fu via Gcc
• คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ TPL Group via Gcc
  • คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ TPL Group via Gcc
  • คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ TPL Group via Gcc
  • คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ TPL Group via Gcc
  • คุณเดือดร้อน เราช่วยคุณได้ ไม่มีโอนก่อนไม่มีมัดจำ TPL Group1999 via Gcc
• gnUcompileBlood Ebrahim Khalil via Gcc
• gcc-15-20250316 is now available GCC Administrator via Gcc
• GSoC 2025 Rust Front-End: Name Resolution Pass Rewrite Christina / via Gcc
  • Re: GSoC 2025 Rust Front-End: Name Resolution Pass Rewrite Martin Jambor
  • Re: GSoC 2025 Rust Front-End: Name Resolution Pass Rewrite Jie via Gcc
• gcc-14-20250315 is now available GCC Administrator via Gcc
• GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Arijit Kumar Das via Gcc
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Andrew Stubbs
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Arijit Kumar Das via Gcc
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Andrew Stubbs
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Thomas Schwinge
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Arijit Kumar Das via Gcc
  • Re: GSoC 2025: In-Memory Filesystem for GPU Offloading Tests Arijit Kumar Das via Gcc
• COBOL test cases Robert Dubner
  • Re: COBOL test cases Jakub Jelinek via Gcc
  • Re: COBOL test cases Jakub Jelinek via Gcc
  • RE: COBOL test cases Robert Dubner
  • Re: COBOL test cases Richard Biener via Gcc
  • Re: COBOL test cases Jakub Jelinek via Gcc
  • RE: COBOL test cases Robert Dubner
  • RE: COBOL test cases Robert Dubner
  • Re: COBOL test cases Andreas Schwab
• bounds checking / VLA types Martin Uecker via Gcc
  • Re: bounds checking / VLA types Yeoul Na via Gcc
  • Re: bounds checking / VLA types Martin Uecker via Gcc
  • Re: bounds checking / VLA types Yeoul Na via Gcc
  • Re: bounds checking / VLA types Martin Uecker via Gcc
  • Re: bounds checking / VLA types Yeoul Na via Gcc
  • Re: bounds checking / VLA types Martin Uecker via Gcc
  • Re: bounds checking / VLA types Bill Wendling via Gcc
  • Re: bounds checking / VLA types Martin Uecker via Gcc
  • Re: bounds checking / VLA types Bill Wendling via Gcc
  • Re: bounds checking / VLA types Martin Uecker via Gcc

• Earlier messages
• Later messages