gcc  

Messages by Thread

• • 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
• GNU MPFR 4.2.2 Release Candidate Vincent Lefevre
• Discover the Latest Trends at Bio-IT World Expo 2025 Erin Lewis
  • RE: Discover the Latest Trends at Bio-IT World Expo 2025 Erin Lewis
• gcc-13-20250314 is now available GCC Administrator via Gcc
• Sourceware Survey 2025 Mark Wielaard
  • Sourceware Survey 2025 Mark Wielaard
  • Re: Sourceware Survey 2025 Mark Wielaard
  • Re: Sourceware Survey 2025 Mark Wielaard
• gcc-12-20250313 is now available GCC Administrator via Gcc
• Using nonzero_bits() in insn conditions? Georg-Johann Lay via Gcc
  • Re: Using nonzero_bits() in insn conditions? Jeff Law via Gcc
  • Re: Using nonzero_bits() in insn conditions? Georg-Johann Lay via Gcc
  • Re: Using nonzero_bits() in insn conditions? Jeff Law via Gcc
  • Re: Using nonzero_bits() in insn conditions? Georg-Johann Lay via Gcc
  • Re: Using nonzero_bits() in insn conditions? Georg-Johann Lay via Gcc
• Gsoc: Fortran-Do Concurrent ahmad tariq via Gcc
  • Re: Gsoc: Fortran-Do Concurrent Martin Jambor
• (GSoC) I am interested in contributing to GCC's Rust Front-End Joey Pandina via Gcc
  • Re: (GSoC) I am interested in contributing to GCC's Rust Front-End Martin Jambor
• GSOC interest in Extend the static analysis pass Basile Starynkevitch
  • Re: GSOC interest in Extend the static analysis pass Sam James via Gcc
• Supporting “crippled” MIPS implementations as cpu option mzpqnxow via Gcc
  • Re: Supporting “crippled” MIPS implementations as cpu option Gabriel Ravier via Gcc
  • Re: Supporting “crippled” MIPS implementations as cpu option Andrew Pinski via Gcc
  • Re: Supporting “crippled” MIPS implementations as cpu option Maciej W. Rozycki
• enquiry about GSoC Manish Mathe via Gcc
  • Re: enquiry about GSoC Martin Jambor
• GSOC: Guidance on LTO, and Static Analysis Projects Yatindra Indoria via Gcc
  • Re: GSOC: Guidance on LTO, and Static Analysis Projects Sam James via Gcc
• GSOC interest in Extend the static analysis pass, [OpenACC] Kaaden Ruman via Gcc
  • Re: GSOC interest in Extend the static analysis pass, [OpenACC] Sam James via Gcc
  • Re: GSOC interest in Extend the static analysis pass, [OpenACC] Thomas Schwinge
• GCC does not optimize well enough with vectors on bitshift Qwert Nerdish via Gcc
  • Re: GCC does not optimize well enough with vectors on bitshift Qwert Nerdish via Gcc
  • Re: GCC does not optimize well enough with vectors on bitshift Matt Godbolt
  • Re: GCC does not optimize well enough with vectors on bitshift Jason Merrill via Gcc
• The Alydar45810 via Gcc
  • the Bill Kossen via Gcc
• [GSoC][Fortran – DO CONCURRENT] Interest in 2025 GSoC – Fortran DO CONCURRENT Auto-Parallelization Zhang lv via Gcc
  • Re: [GSoC][Fortran – DO CONCURRENT] Interest in 2025 GSoC – Fortran DO CONCURRENT Auto-Parallelization Martin Jambor
• gcc-15-20250309 is now available GCC Administrator via Gcc
• gcc-14-20250308 is now available GCC Administrator via Gcc
• a super regular RISC that encodes constants in immediate blocks. Michael Clark via Gcc
• make error when builing gcc Gwen Fu via Gcc
  • Re: make error when builing gcc LIU Hao via Gcc
  • Re: make error when builing gcc Jonathan Wakely via Gcc
  • Re: make error when builing gcc LIU Hao via Gcc
  • Re: make error when builing gcc Jonathan Wakely via Gcc
  • Re: make error when builing gcc Gwen Fu via Gcc
  • Re: make error when builing gcc Jonathan Wakely via Gcc
  • Re: make error when builing gcc Jonathan Wakely via Gcc
  • Re: make error when builing gcc Jonathan Wakely via Gcc
• gcc-13-20250307 is now available GCC Administrator via Gcc
• What branch to use for the Algol 68 front-end Jose E. Marchesi via Gcc
  • Re: What branch to use for the Algol 68 front-end Richard Earnshaw (lists) via Gcc
  • Re: What branch to use for the Algol 68 front-end Mark Wielaard
  • Re: What branch to use for the Algol 68 front-end Jose E. Marchesi via Gcc

• Earlier messages
• Later messages