gcc  

Messages by Thread

• • Re: How to test for errors without line? Andreas Schwab
  • Re: How to test for errors without line? Thomas Koenig via Gcc
  • Re: How to test for errors without line? Maciej W. Rozycki
• Copyright assignment form request Ben Wu via Gcc
  • Re: Copyright assignment form request Mark Wielaard
  • Re: Copyright assignment form request Jonathan Wakely via Gcc
• GCC 1.0 Source Code Carlos Jorge Sebastião Moreira via Gcc
  • Re: GCC 1.0 Source Code Mark Wielaard
  • Re: GCC 1.0 Source Code Joe Monk via Gcc
  • Re: GCC 1.0 Source Code Richard Earnshaw (lists) via Gcc
  • Re: GCC 1.0 Source Code Jeff Law via Gcc
  • Re: GCC 1.0 Source Code Richard Earnshaw (lists) via Gcc
• gcc-14-20250919 is now available GCC Administrator via Gcc
• gcc-16-20250914 is now available GCC Administrator via Gcc
• gcc-13-20250918 is now available GCC Administrator via Gcc
• gccrs August 2025 Monthly report Arthur Cohen
• New OS Target: unable to emulate ‘XF’ connor horman via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ H.J. Lu via Gcc
  • Fwd: New OS Target: unable to emulate ‘XF’ connor horman via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ H.J. Lu via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ connor horman via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ connor horman via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ connor horman via Gcc
  • Re: New OS Target: unable to emulate ‘XF’ connor horman via Gcc
• With g++, how can I have class member symbols evaluated at runtime instead of link time? Erich E. Hoover via Gcc
• [ARM] LDRD/STRD with write back Visda.Vokhshoori--- via Gcc
  • Re: [ARM] LDRD/STRD with write back Visda.Vokhshoori--- via Gcc
  • Fw: [ARM] LDRD/STRD with write back Visda.Vokhshoori--- via Gcc
• Clarification about RTL shifts semantics Christophe Lyon via Gcc
  • Re: Clarification about RTL shifts semantics Richard Biener via Gcc
  • Re: Clarification about RTL shifts semantics Jakub Jelinek via Gcc
  • Re: Clarification about RTL shifts semantics Richard Biener via Gcc
  • Re: Clarification about RTL shifts semantics Michael Matz via Gcc
  • Re: Clarification about RTL shifts semantics Richard Sandiford
  • Re: Clarification about RTL shifts semantics Richard Biener via Gcc
  • Re: Clarification about RTL shifts semantics Jakub Jelinek via Gcc
  • Re: Clarification about RTL shifts semantics Christophe Lyon via Gcc
  • Re: Clarification about RTL shifts semantics Richard Biener via Gcc
  • Re: Clarification about RTL shifts semantics Christophe Lyon via Gcc
  • Re: Clarification about RTL shifts semantics Richard Sandiford
• Regenerating *.opt.urls doesn't do anything Thomas Koenig via Gcc
  • Re: Regenerating *.opt.urls doesn't do anything Arsen Arsenović via Gcc
  • Re: Regenerating *.opt.urls doesn't do anything Mark Wielaard
  • Re: Regenerating *.opt.urls doesn't do anything Thomas Koenig via Gcc
• negative indexes Paul Edwards via Gcc
  • Re: negative indexes H.J. Lu via Gcc
• gcc-15-20250913 is now available GCC Administrator via Gcc
• gcc-14-20250912 is now available GCC Administrator via Gcc
• RISC-V nightly performance testing of GCC on SPEC CPU 2017 Luke Lau via Gcc
  • Re: RISC-V nightly performance testing of GCC on SPEC CPU 2017 Robin Dapp via Gcc
  • Re: RISC-V nightly performance testing of GCC on SPEC CPU 2017 Luke Lau via Gcc
• gcc-13-20250911 is now available GCC Administrator via Gcc
• Sourceware Together; Open Office Friday 16:00 UTC Mark Wielaard
  • Re: Sourceware Together; Open Office Friday 16:00 UTC Mark Wielaard
• Build error on master branch Alejandro Colomar via Gcc
  • Re: Build error on master branch Jonathan Wakely via Gcc
  • Re: Build error on master branch Jakub Jelinek via Gcc
  • Re: Build error on master branch Alejandro Colomar via Gcc
• Inconsistencies in docs for -Wall and -Wextra warnings Jonathan Wakely via Gcc
  • Re: Inconsistencies in docs for -Wall and -Wextra warnings Sandra Loosemore
• Cvvvvvv Keith Suhr via Gcc
• Bugzilla incorrectly requests to select product Rainer Orth via Gcc
  • Re: Bugzilla incorrectly requests to select product Mark Wielaard
  • Re: Bugzilla incorrectly requests to select product Rainer Orth via Gcc
• GCC Compiler 11.2.0 Issue List Manoj Tiwari via Gcc
  • Re: GCC Compiler 11.2.0 Issue List Jonathan Wakely via Gcc
  • Re: GCC Compiler 11.2.0 Issue List Richard Biener via Gcc
• Attribute for custom memset function Chris Packham via Gcc
  • Re: Attribute for custom memset function NightStrike via Gcc
  • Re: Attribute for custom memset function Chris Packham via Gcc
  • Re: Attribute for custom memset function Andrew Pinski via Gcc
  • Re: Attribute for custom memset function Florian Weimer via Gcc
  • Re: Attribute for custom memset function Jonathan Wakely via Gcc
• GNU Tools Weekly News Week 2 (September 7, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 3 (September 14, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 4 (September 21, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 6 (October 5, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 7 (October 12, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 8 (October 19, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 9 (October 26, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 10 (November 2, 2025) GNU Tools weekly via Gcc
  • Re: GNU Tools Weekly News Week 11 (November 9, 2025) GNU Tools weekly via Gcc
  • Re: GNU Tools Weekly News Week 11 (November 9, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 12 (November 16, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 13 (November 23, 2025) GNU Tools weekly via Gcc
  • GNU Tools Weekly News Week 14 (November 30, 2025) GNU Tools weekly via Gcc
• gcc-16-20250907 is now available GCC Administrator via Gcc
• [no subject] Mohammed EL Faouatih via Gcc
• gcc-15-20250906 is now available GCC Administrator via Gcc
• gcc-14-20250905 is now available GCC Administrator via Gcc
• OpenMP team start overhead for non-nested and cached team Matthew Malcomson via Gcc
• gcc-13-20250904 is now available GCC Administrator via Gcc
• Weekly news letter for GNU toolchain: Week 1 (August 31, 2025) GNU Tools weekly via Gcc
  • Re: Weekly news letter for GNU toolchain: Week 1 (August 31, 2025) GNU Tools weekly via Gcc
• is there any GCC plugin extracting call graph information? Basile Starynkevitch
  • Re: is there any GCC plugin extracting call graph information? Basile Starynkevitch
• git repo locked? Rainer Orth via Gcc
  • Re: git repo locked? Richard Biener via Gcc
  • Re: git repo locked? Jakub Jelinek via Gcc
  • Re: git repo locked? Andre Vehreschild via Gcc
  • Re: git repo locked? Andre Vehreschild via Gcc
  • Re: git repo locked? Jonathan Wakely via Gcc
  • Re: git repo locked? Andre Vehreschild via Gcc
  • Re: git repo locked? Richard Biener via Gcc
  • Re: git repo locked? Jonathan Wakely via Gcc
  • Re: git repo locked? Jakub Jelinek via Gcc
  • Re: git repo locked? Andre Vehreschild via Gcc
• C++ vs. -ftrivial-auto-var-init= Jakub Jelinek via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= Jason Merrill via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= Qing Zhao via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Jakub Jelinek via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Qing Zhao via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Jakub Jelinek via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Qing Zhao via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Jason Merrill via Gcc
  • Re: C++ vs. -ftrivial-auto-var-init= vs. vacuous initialization & jumps Jakub Jelinek via Gcc
• gcc-16-20250831 is now available GCC Administrator via Gcc
• Weekly news letter about GNU toolchain Andrew Pinski via Gcc
  • Re: Weekly news letter about GNU toolchain Mark Wielaard
  • Re: Weekly news letter about GNU toolchain Andrew Pinski via Gcc
  • Re: Weekly news letter about GNU toolchain Adhemerval Zanella Netto via Gcc
  • Re: Weekly news letter about GNU toolchain Andrew Pinski via Gcc
• gcc-15-20250830 is now available GCC Administrator via Gcc
• gcc-14-20250829 is now available GCC Administrator via Gcc
• gcc-13-20250828 is now available GCC Administrator via Gcc
• Providing more precise "excess errors" message in DejaGnu Sam James via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Rainer Orth via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Richard Biener via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Jeff Law via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Iain Sandoe
  • Re: Providing more precise "excess errors" message in DejaGnu Richard Earnshaw (lists) via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Thiago Jung Bauermann via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Pedro Alves
  • Re: Providing more precise "excess errors" message in DejaGnu Jeff Law via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Iain Sandoe
  • Re: Providing more precise "excess errors" message in DejaGnu Jacob Bachmeyer via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Richard Earnshaw via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Iain Sandoe
  • Re: Providing more precise "excess errors" message in DejaGnu Richard Earnshaw via Gcc
  • Re: DejaGnu structured logs (was: Providing more precise "excess errors" message in DejaGnu) Jacob Bachmeyer via Gcc
  • Re: DejaGnu structured logs Rob Savoye via Gcc
  • Re: DejaGnu structured logs David Malcolm via Gcc
  • Re: DejaGnu structured logs Jacob Bachmeyer via Gcc
  • Re: DejaGnu structured logs Jacob Bachmeyer via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu David Malcolm via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Christophe Lyon via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Richard Earnshaw (lists) via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Christophe Lyon via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Jeff Law via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Joseph Myers via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Sam James via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Joseph Myers via Gcc
  • Re: Providing more precise "excess errors" message in DejaGnu Jacob Bachmeyer via Gcc
• Anubis for inbox.sourceware.org Mark Wielaard
• gcc-16-20250824 is now available GCC Administrator via Gcc
• gcc-15-20250823 is now available GCC Administrator via Gcc
• gcc-14-20250822 is now available GCC Administrator via Gcc
• gcc-13-20250821 is now available GCC Administrator via Gcc
• DejaGnu fail despite equivalent output binaries Thomas de Bock via Gcc
  • Re: DejaGnu fail despite equivalent output binaries Jonathan Wakely via Gcc
  • Re: DejaGnu fail despite equivalent output binaries Thomas de Bock via Gcc
• Guidance on potential directions for contributing to GCC Ujjwal Shekhar via Gcc
  • Re: Guidance on potential directions for contributing to GCC Sam James via Gcc
  • Re: Guidance on potential directions for contributing to GCC Ujjwal Shekhar via Gcc
  • Re: Guidance on potential directions for contributing to GCC Sam James via Gcc
• [no subject] Mohammed Alanazi via Gcc
• re follow up! zara join via Gcc
• Messed up trunk branch on gcc-test on forge Andrew Pinski via Gcc
  • Re: Messed up trunk branch on gcc-test on forge Mark Wielaard
  • Re: Messed up trunk branch on gcc-test on forge Claudio Bantaloukas via Gcc
  • Re: Messed up trunk branch on gcc-test on forge Jonathan Wakely via Gcc
• GNU Tools Cauldron 2025 - We are almost there! Jose E. Marchesi via Gcc
• Condition coverage counters Sebastian Huber
  • Re: Condition coverage counters Jørgen Kvalsvik
  • Re: Condition coverage counters Sebastian Huber
  • Re: Condition coverage counters Jørgen Kvalsvik
  • Re: Condition coverage counters Sebastian Huber
• gcc-16-20250817 is now available GCC Administrator via Gcc
• gcc-15-20250816 is now available GCC Administrator via Gcc
• gcc-14-20250815 is now available GCC Administrator via Gcc
• gcc-13-20250814 is now available GCC Administrator via Gcc
• Current ports without maintainers Andrew Pinski via Gcc
  • Re: Current ports without maintainers Jeff Law via Gcc
  • Re: Current ports without maintainers Joel Sherrill via Gcc
  • Re: Current ports without maintainers Joseph Myers via Gcc
  • Re: Current ports without maintainers Iain Sandoe
  • Re: Current ports without maintainers Richard Biener via Gcc
  • Re: Current ports without maintainers Jeff Law via Gcc
  • Re: Current ports without maintainers Iain Sandoe
  • Re: Current ports without maintainers Mark Wielaard
  • Re: Current ports without maintainers Joel Sherrill via Gcc
  • Re: Current ports without maintainers Mark Wielaard
  • Re: Current ports without maintainers Jeff Law via Gcc
  • Re: Current ports without maintainers Mark Wielaard
  • Re: Current ports without maintainers Jeff Law via Gcc
  • Re: Current ports without maintainers Mark Wielaard
  • Re: Current ports without maintainers Jeff Law via Gcc
  • Re: Current ports without maintainers Richard Biener via Gcc
• Questions regarding exception handling capability when libgcc is statically linked Andras Lehotay-Kery via Gcc
• gcc-16-20250810 is now available GCC Administrator via Gcc

• Earlier messages
• Later messages