GCC Help

• Thread Index

• [no subject]
  • From: Unknown
• help wanted explaining a C++ LTO-related symbol initialization bug
  • From: "G. Branden Robinson via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: help wanted explaining a C++ LTO-related symbol initialization bug
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: help wanted explaining a C++ LTO-related symbol initialization bug
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: All US mirrors broken?
  • From: Gerald Pfeifer <gerald@xxxxxxxxxxx>
• Re: help wanted explaining a C++ LTO-related symbol initialization bug
  • From: "G. Branden Robinson via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Compiler 11.2.0 Issue List
  • From: Manoj Tiwari via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC Compiler 11.2.0 Issue List
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Compiler 11.2.0 Issue List
  • From: Richard Biener via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Shiva Subramanian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Porting GCC
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Porting GCC
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to trigger "'void' must be the only parameter and unnamed
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to trigger "'void' must be the only parameter and unnamed
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to trigger "'void' must be the only parameter and unnamed
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Flag for global variable DSE (dead store elimination)
  • From: Levo D via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: "hans.gustav.aberg--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cybersecurity Risk Assessment Request from Emerson for GNU Compiler Collection
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Cybersecurity Risk Assessment Request from Emerson for GNU Compiler Collection
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: How to identify unnecessary include header files
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• How to identify unnecessary include header files
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• a preprocessor bug (?) on processing a floating constant
  • From: Andrew Makhorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Understanding GCC Development Versions, Front Ends, and Libraries
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Understanding GCC Development Versions, Front Ends, and Libraries
  • From: Heime via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: What info is compiled into gcc and what can be changed at runtime?
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• What info is compiled into gcc and what can be changed at runtime?
  • From: Jan Strąkowski via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [INTERNAL DRAFT] Questions regarding exception handling capability when libgcc is statically linked
  • From: Andras Lehotay-Kery via Gcc-help <gcc-help@xxxxxxxxxxx>
• [INTERNAL DRAFT] Questions regarding exception handling capability when libgcc is statically linked
  • From: Andras Lehotay-Kery via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Zdenek Sojka via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Zdenek Sojka via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• riscv64 -mcmodel=medany relocation truncated to fit: R_RISCV_PCREL_HI20 against symbol ...
  • From: Zdenek Sojka via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about GCC license for commercial use
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Trouble building GCC on MinGW/MSYS2
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about GCC license for commercial use
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Question about GCC license for commercial use
  • From: "Qifan.Zhou via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Trouble building GCC on MinGW/MSYS2
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Trouble building GCC on MinGW/MSYS2
  • From: Adam Wood via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Imple Lee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley J Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Rules about type of comparison of gcc vector types
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Rules about type of comparison of gcc vector types
  • From: Imple Lee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need help building a Canadian Cross
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need help building a Canadian Cross
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need help building a Canadian Cross
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Need help building a Canadian Cross
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is PRE architecture dependent? aarch64 vs x86_64
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Is PRE architecture dependent? aarch64 vs x86_64
  • From: Bradley J Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Need help building a Canadian Cross
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Backend initialization on RISC-V
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Backend initialization on RISC-V
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: GCC compilation performance under RAM starvation
  • From: "Krystian Kazmierczak \(Nokia\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• building libgccjit on illumos
  • From: Neal Sidhwaney via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: GCC compilation performance under RAM starvation
  • From: "Krystian Kazmierczak \(Nokia\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Why does a return statement generate an abort
  • From: Andrew Haley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 15.1 : print fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 15.1 : print fail
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC 15.1 : print fail
  • From: Luc ROLLAND via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Debug symbols for libstdc++ x86_64-w64-mingw32
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Debug symbols for libstdc++ x86_64-w64-mingw32
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Debug symbols for libstdc++ x86_64-w64-mingw32
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Debug symbols for libstdc++ x86_64-w64-mingw32
  • From: Jonas Kvinge via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does a return statement generate an abort
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::from_chars limitation
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::from_chars limitation
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does a return statement generate an abort
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• std::from_chars limitation
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Tom V <t.gcc@xxxxxxxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Tom V <t.gcc@xxxxxxxxxxxxxxxx>
• Re: Where attribute((aligned)) is allowed to decrease alignment
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Where attribute((aligned)) is allowed to decrease alignment
  • From: Tom V <t.gcc@xxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Change in function signature of `__tsan_func_exit` in gcc15
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Change in function signature of `__tsan_func_exit` in gcc15
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Change in function signature of `__tsan_func_exit` in gcc15
  • From: Jakub Jelinek via Gcc-help <gcc-help@xxxxxxxxxxx>
• Change in function signature of `__tsan_func_exit` in gcc15
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: [Help] Options to cross compile gcc14
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• [Help] Options to cross compile gcc14
  • From: Jose Gomez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling an objective-c source, I don't know how to resolve the compiler error.
  • From: Iain Sandoe <iain@xxxxxxxxxxxx>
• Re: Compiling an objective-c source, I don't know how to resolve the compiler error.
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Compiling an objective-c source, I don't know how to resolve the compiler error.
  • From: Jean-Marc Farinas via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -funsafe-math-optimizations effect on linking mkl
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -funsafe-math-optimizations effect on linking mkl
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -funsafe-math-optimizations effect on linking mkl
  • From: Nicola Giuliani via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -funsafe-math-optimizations effect on linking mkl
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Tim Froggatt via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Tim Froggatt via Gcc-help <gcc-help@xxxxxxxxxxx>
• -funsafe-math-optimizations effect on linking mkl
  • From: Nicola Giuliani via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constraint for inline assembly with one register used for both an input variable and an output variable
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Gcov support for dynamically loaded so files
  • From: Shweta Pednekar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Tim Froggatt via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Tim Froggatt via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about optimisation options
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Questions about optimisation options
  • From: Tim Froggatt via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Inquiry About Video/Audio Meeting Options for GCC Patch Reviews
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The module does not support non ASCII characters
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Please remove my mail Id from the list
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Please remove my mail Id from the list
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Please remove my mail Id from the list
  • From: Sudha Sarita via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GNU Compiler Collection
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GNU Compiler Collection
  • From: Andrew Goh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AP Credits
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AP Credits
  • From: Storm Fire via Gcc-help <gcc-help@xxxxxxxxxxx>
• AP Credits
  • From: Storm Fire via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: --enable-host-shared and slower compiler
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• --enable-host-shared and slower compiler
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The module does not support non ASCII characters
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• The module does not support non ASCII characters
  • From: 17185349200 <17185349200@xxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Minimum requirements for a custom libc
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: [RFC v1 0/5] Returning (adjusted) arrays
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: صادق via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Restore STDC++ Header Removal
  • From: Reid Sutherland <reid@xxxxxxxxxxxxxxxxxx>
• Re: Restore STDC++ Header Removal
  • From: Reid Sutherland <reid@xxxxxxxxxxxxxxxxxx>
• Re: Restore STDC++ Header Removal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Restore STDC++ Header Removal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Restore STDC++ Header Removal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Restore STDC++ Header Removal
  • From: Reid Sutherland <reid@xxxxxxxxxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Andrew Bell via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: UBSAN-safe way to convert from unsigned int to int
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• UBSAN-safe way to convert from unsigned int to int
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Inquiry About Video/Audio Meeting Options for GCC Patch Reviews
  • From: "Dora, Sunil Kumar" <SunilKumar.Dora@xxxxxxxxxxxxx>
• [RFC v1 1/5] gcc/c/c-decl.cc: Return arrays
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RFC v1 3/5] gcc/c/c-parser.cc: Refactor code
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RFC v1 5/5] dbg
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RFC v1 4/5] gcc/c/c-parser.cc: Extend the scope a little bit
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RFC v1 0/5] Returning (adjusted) arrays
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RFC v1 2/5] gcc/c/c-decl.cc: Allow VMTs at file scope
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extracting AST from GCC
  • From: Zuhal Altuntaş via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about difference in assembly generation
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Extracting AST from GCC
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Question about difference in assembly generation
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Question about difference in assembly generation
  • From: Laurent Carlier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 15.1.0 and binutils 2.44 - dangerous relocation: unsupported relocation on ARM
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Extracting AST from GCC
  • From: Zuhal Altuntaş via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Need to understand what GCC is attempting to do at a failure point
  • From: "Cowley, Kevin via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Need to understand what GCC is attempting to do at a failure point
  • From: Andrew Bell via Gcc-help <gcc-help@xxxxxxxxxxx>
• Need to understand what GCC is attempting to do at a failure point
  • From: "Cowley, Kevin via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: status of libjit vs GNU lightning vs libgccjit
  • From: Aleksey Demakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: status of libjit vs GNU lightning vs libgccjit
  • From: Willis Blackburn via Gcc-help <gcc-help@xxxxxxxxxxx>
• Read: GCC compilation performance under RAM starvation
  • From: "Krystian Kazmierczak \(Nokia\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: status of libjit vs GNU lightning vs libgccjit
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: status of libjit vs GNU lightning vs libgccjit
  • From: Roland Plüss via Gcc-help <gcc-help@xxxxxxxxxxx>
• status of libjit vs GNU lightning vs libgccjit
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• GCC 15.1.0 and binutils 2.44 - dangerous relocation: unsupported relocation on ARM
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: GCC compilation performance under RAM starvation
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: GCC compilation performance under RAM starvation
  • From: sd@xxxxxxxxxxxxxx
• Re: GCC compilation performance under RAM starvation
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC compilation performance under RAM starvation
  • From: "Krystian Kazmierczak \(Nokia\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Possible gcc 15 modules regression w/ TU-local entity in constexpr function
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Possible gcc 15 modules regression w/ TU-local entity in constexpr function
  • From: Marcel Laverdet <marcel@xxxxxxxxxxxx>
• Informing for the use of the tool as per the License Terms and Conditions given
  • From: Sangharatna Godboley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• RE: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf
  • From: Wasim Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf
  • From: Levente via Gcc-help <gcc-help@xxxxxxxxxxx>
• memcpy issue with arm-gnu-toolchain-14.2.rel1-x86_64-aarch64-none-elf
  • From: Wasim Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: GCOV issue with GCC-14.2
  • From: Wasim Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCOV issue with GCC-14.2
  • From: Wasim Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem with Virtual Memory Subcontexts
  • From: Maria Fay Garcia via Gcc-help <gcc-help@xxxxxxxxxxx>
• Modified GCC issues - Custom 64-bit PowerPC EABI compiler generates junk assembly
  • From: Aiden Isik via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: blocking source IPs
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• blocking source IPs
  • From: Joe Tammariello <jat@xxxxxxxxxxx>
• Re: Overly Verbose Error Message for Invalid STL Container Type (e.g., std::vector<int&>)
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Overly Verbose Error Message for Invalid STL Container Type (e.g., std::vector<int&>)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Overly Verbose Error Message for Invalid STL Container Type (e.g., std::vector<int&>)
  • From: abdul rehman via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: feature request: -std=c++-latest, -std=c-latest, -std=gnu++-latest and probably more
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• feature request: -std=c++-latest, -std=c-latest, -std=gnu++-latest and probably more
  • From: janezz55 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc.gnu.org down?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc.gnu.org down?
  • From: Michael Welsh Duggan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc.gnu.org down?
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is anyone working on RTL to LLVM bitcode?
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• gcc.gnu.org down?
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to track the call stack of gcc (libbacktrace)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: How to cherry-pick patches from the master branch to releases/gcc-14?
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is anyone working on RTL to LLVM bitcode?
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is anyone working on RTL to LLVM bitcode?
  • From: Qwert Nerdish via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to cherry-pick patches from the master branch to releases/gcc-14?
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: cc1 posix_spawnp compilation error with gcc 14.2.0 on Ubuntu 24.04
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: cc1 posix_spawnp compilation error with gcc 14.2.0 on Ubuntu 24.04
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to cherry-pick patches from the master branch to releases/gcc-14?
  • From: Jin Ma via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Expectations around COBOL platform support
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Expectations around COBOL platform support
  • From: "Matthew R. Wilson" <mwilson@xxxxxxxxxxxxxx>
• Re: Expectations around COBOL platform support
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Expectations around COBOL platform support
  • From: Peter Bergner via Gcc-help <gcc-help@xxxxxxxxxxx>
• Expectations around COBOL platform support
  • From: "Matthew R. Wilson" <mwilson@xxxxxxxxxxxxxx>
• Re: Plugin to print a GCC type (e.g. C++-friendly way)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Plugin to print a GCC type (e.g. C++-friendly way)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: std::abs(long)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::abs(long)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: std::abs(long)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: std::abs(long)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::abs(long)
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to generate a changelog
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::abs(long)
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to generate a changelog
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to generate a changelog
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to generate a changelog
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: PIE executables on bare-metal Cortex-M: -fpie vs -fPIE and relocation handling
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• cc1 posix_spawnp compilation error with gcc 14.2.0 on Ubuntu 24.04
  • From: Scott Smedley <scott@xxxxxxxxxxxxxxxxx>
• Re: Do we need to go through all use cases when conducting a make check
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Do we need to go through all use cases when conducting a make check
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• PIE executables on bare-metal Cortex-M: -fpie vs -fPIE and relocation handling
  • From: Massimiliano Cialdi via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: error 403 , help plis
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• error 403 , help plis
  • From: jhordy perez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Module Mapper File on gcc 15 c++23: what am I doing wrong?
  • From: Igor Machado via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Importing <print> failing
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Importing <print> failing
  • From: Rud Merriam via Gcc-help <gcc-help@xxxxxxxxxxx>
• Importing <print> failing
  • From: Rud Merriam via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Seeking some advice on reading C++ front-end source code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Seeking some advice on reading C++ front-end source code
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Minimum requirements for a custom libc
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to track the call stack of gcc (libbacktrace)
  • From: Ian Lance Taylor via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to track the call stack of gcc (libbacktrace)
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: How to track the call stack of gcc
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: How to track the call stack of gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to track the call stack of gcc
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assistance Required for Installing Latest Version of GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Assistance Required for Installing Latest Version of GCC
  • From: Rugwesh KOlekar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assistance Required for Installing Latest Version of GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: testing GCC builds
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assistance Required for Installing Latest Version of GCC
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: testing GCC builds
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Assistance Required for Installing Latest Version of GCC
  • From: Rugwesh KOlekar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: The time_zone tests that fail
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• The time_zone tests that fail
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Michael Welsh Duggan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiry regarding upstream fix for C preprocessor Line number issue
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why would my include/c++/14.2.0/iostream not be found ?
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Alberto Gcchelp via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Inquiry regarding upstream fix for C preprocessor Line number issue
  • From: Geeta Dora via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Guidance on Decompiling GCC 11.4.0 Optimized Code
  • From: manoj alladawar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why would my include/c++/14.2.0/iostream not be found ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Is the std module compiled by default when building?
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Is the std module compiled by default when building?
  • From: Alberto Gcchelp via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problem with gcc 14.2.0 targeting bfin-linux (FDPIC)
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: when compiling error "cc1plus: fatal error: gengtype-lex.cc: No such file or dir"
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• when compiling error "cc1plus: fatal error: gengtype-lex.cc: No such file or dir"
  • From: Gwen Fu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: testing GCC builds
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: testing GCC builds
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• testing GCC builds
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: problem with gcc 14.2.0 targeting bfin-linux (FDPIC)
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• problem with gcc 14.2.0 targeting bfin-linux (FDPIC)
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: Mexico IPs 403 forbidden access
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Mexico IPs 403 forbidden access
  • From: Mark Wielaard <mark@xxxxxxxxx>
• Mexico IPs 403 forbidden access
  • From: Braulio Martínez via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: why did you ban my ip from gcc.gnu.org ?
  • From: Mark Wielaard via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: why did you ban my ip from gcc.gnu.org ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• why did you ban my ip from gcc.gnu.org ?
  • From: Felipe Fernandes da Costa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: rahl <rahl@xxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: rahl <rahl@xxxxxxxxxx>
• [PATCH v1] Revert "futex.2: Make the example use C11 atomics rather than GCC builtins"
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: rahl <rahl@xxxxxxxxxx>
• Re: Incorrect const in futex(2) example code
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: none
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• [no subject]
  • From: Soufiane Elkhotfi via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcov incorrect coverage results
  • From: Aaron Merey via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Incomplete array element type as function argument (C mode)
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Incomplete array element type as function argument (C mode)
  • From: Beni Falk via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: TU-local entity error question
  • From: Thomas Khyn via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: TU-local entity error question
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: Saifi Khan <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc build errors out with 'Error: symbol `_GLOBAL__sub_I.00099_tzdb.cc' is already defined'
  • From: SAIFI <saifi@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: How to properly build gcc/libgcc with both mno-red-zone and mcmodel=kernel on x86_64 ?
  • From: Ludovic Delabre via Gcc-help <gcc-help@xxxxxxxxxxx>
• TU-local entity error question
  • From: Thomas Khyn via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: To access gcc.gnu.org received Forbiden
  • From: Thomacelli via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Bento Borges Schirmer <bbschirmer@xxxxxxxxxxx>
• Re: To access gcc.gnu.org received Forbiden
  • From: Mark Wielaard <mark@xxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Bento Borges Schirmer <bbschirmer@xxxxxxxxxxx>
• To access gcc.gnu.org received Forbiden
  • From: Thomacelli via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC decimal floating point support
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC decimal floating point support
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC decimal floating point support
  • From: Eugene Galkin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Assembling a VAR_DECL in a custom way
  • From: Georg-Johann Lay via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Tips to compile very very giant code
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Tips to compile very very giant code
  • From: Bento Borges Schirmer <bbschirmer@xxxxxxxxxxx>
• R: _Pragma diagnostic not working
  • From: Luca Bacci via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: leticia xo via Gcc-help <gcc-help@xxxxxxxxxxx>
• _Pragma diagnostic not working
  • From: Luca Bacci via Gcc-help <gcc-help@xxxxxxxxxxx>
• Defining a fixed-address section in a linker script for a static-pie binary
  • From: "Eugene Sh. via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Two Build Errors with BUILD_CONFIG="bootstrap-O1"
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Two Build Errors with BUILD_CONFIG="bootstrap-O1"
  • From: JohnyTheCarrot via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Geeta Dora via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Andrew Pinski via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Geeta Dora via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Andrew Pinski via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Geeta Dora via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Fails to Compile When Command Line Argument Size Exceeds 128KB
  • From: Geeta Dora via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Behavior of constructor with default arguments
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Behavior of constructor with default arguments
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Behavior of constructor with default arguments
  • From: Creeperxie via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fastest Single-Unit Compile CPU
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fastest Single-Unit Compile CPU
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Fastest Single-Unit Compile CPU
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• how to find find the source path line and col of a gcc_jit_location (GCC-15, Linux)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Understanding arm_sve.h
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Understanding arm_sve.h
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Understanding arm_sve.h
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Understanding arm_sve.h
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Understanding arm_sve.h
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• [RISC-V] Defining fixed-size RVV tuple types (GCC 14.2)
  • From: 杨旺 <yangwang@xxxxxxxxxxx>
• AW: ARMv7: VLDR instruction for unaligned address (GCC 9.5.0)
  • From: Christian Gudrian via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: ARMv7: VLDR instruction for unaligned address (GCC 9.5.0)
  • From: Christian Gudrian via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: ARMv7: VLDR instruction for unaligned address (GCC 9.5.0)
  • From: Christian Gudrian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: ARMv7: VLDR instruction for unaligned address (GCC 9.5.0)
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• ARMv7: VLDR instruction for unaligned address (GCC 9.5.0)
  • From: Christian Gudrian via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help build a complete buildroot
  • From: Felipe Fernandes da Costa via Gcc-help <gcc-help@xxxxxxxxxxx>
• OpenMP nvptx and amdgcn offloading - questions on speed, grid size and printf
  • From: Qianqian Fang via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: int constexpr foo[1] = { 4 }; static int j = *foo;
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• int constexpr foo[1] = { 4 }; static int j = *foo;
  • From: Daria via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Calling convention weaknesses in 32-bit embedded ARM
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Calling convention weaknesses in 32-bit embedded ARM
  • From: Trampas Stern via Gcc-help <gcc-help@xxxxxxxxxxx>
• Calling convention weaknesses in 32-bit embedded ARM
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Implementation of fixed width floating-point types
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Implementation of fixed width floating-point types
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• GDB debugging showing wrong code
  • From: Trampas Stern via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: forcing Debian/trixie system GCC (or Linux Mint) to always compile with DWARF debug info
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• forcing Debian/trixie system GCC (or Linux Mint) to always compile with DWARF debug info
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: Enabling monotonic and realtime clocks for libstdc++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Enabling monotonic and realtime clocks for libstdc++
  • From: Caden via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compilation Bugs caused by lto-wrapper changes for x86_64-w64-mingw32
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compilation Bugs caused by lto-wrapper changes for x86_64-w64-mingw32
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Suppressing the warning: "variably modified '<variable>' at file scope" generated due to floating-point computation in an integer expression
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Suppressing the warning: "variably modified '<variable>' at file scope" generated due to floating-point computation in an integer expression
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Yu Sheng Oh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Suppressing the warning: "variably modified '<variable>' at file scope" generated due to floating-point computation in an integer expression
  • From: "beni.falk--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Yu Sheng Oh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fwd: constant expression context for `std::string_view`
  • From: Yu Sheng Oh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constant expression context for `std::string_view`
  • From: Yu Sheng Oh via Gcc-help <gcc-help@xxxxxxxxxxx>
• constant expression context for `std::string_view`
  • From: Yu Sheng Oh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: IPv4 deny list for gcc.gnu.org?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: IPv4 deny list for gcc.gnu.org?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• IPv4 deny list for gcc.gnu.org?
  • From: Matt Fleming via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Archaeology question : what is the last release to support XYZ ?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Archaeology question : what is the last release to support XYZ ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Archaeology question : what is the last release to support XYZ ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Archaeology question : what is the last release to support XYZ ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Archaeology question : what is the last release to support XYZ ?
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Bazel Symbolic Links
  • From: "vaishali.pundir--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Scoped attribute directive ignored diagnostic (false positive?)
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Scoped attribute directive ignored diagnostic (false positive?)
  • From: Martin Uecker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Scoped attribute directive ignored diagnostic (false positive?)
  • From: Martin Uecker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Scoped attribute directive ignored diagnostic (false positive?)
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Scoped attribute directive ignored diagnostic (false positive?)
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bazel Symbolic Links
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Bazel Symbolic Links
  • From: "vaishali.pundir--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Bazel Symbolic Links
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Bazel Symbolic Links
  • From: "vaishali.pundir--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Bazel Symbolic Links
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Bazel Symbolic Links
  • From: "vaishali.pundir--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: M-chip
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: M-chip
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: M-chip
  • From: Bert Gold via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: M-chip
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: M-chip
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: M-chip
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• M-chip
  • From: Bert Gold via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Thomas Madlener via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Thomas Madlener via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Inconsistent -Wparentheses warnigs for gcc>=13 with -std=c++20?
  • From: Thomas Madlener via Gcc-help <gcc-help@xxxxxxxxxxx>
• help build a complete buildroot
  • From: Felipe Fernandes da Costa via Gcc-help <gcc-help@xxxxxxxxxxx>
• c++ modules automatic dependency generation
  • From: Klaus Rudolph via Gcc-help <gcc-help@xxxxxxxxxxx>
• Install strip host components but not target libaries?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Facing Issues while building GCC 8.5.0 on AIX 7.1.4
  • From: Charudatta Jadhav via Gcc-help <gcc-help@xxxxxxxxxxx>
• About MAINTAINERS
  • From: Arvin Zhong <Arvin.Zhong@xxxxxxxxxxxx>
• Facing Issues while building GCC 8.5.0 on AIX 7.1.4
  • From: Charudatta Jadhav via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GDB debugger and my PYTHON hate eachother
  • From: Etienne Buira via Gcc-help <gcc-help@xxxxxxxxxxx>
• GDB debugger and my PYTHON hate eachother
  • From: aotto <aotto1968@xxxxxxxxxxx>
• auto void*
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Output Symbol not Relocatable with -fPIC
  • From: Ahmad Nouralizadeh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Non-Type Template Parameter Pack in Module gives "recursive lazy load" "failed to load pendings for"
  • From: Manuel Bellersen <manuel@xxxxxxxxx>
• Re: GCC Output Symbol not Relocatable with -fPIC
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Output Symbol not Relocatable with -fPIC
  • From: Ahmad Nouralizadeh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Output Symbol not Relocatable with -fPIC
  • From: Ahmad Nouralizadeh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Output Symbol not Relocatable with -fPIC
  • From: Ahmad Nouralizadeh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Exception not caught with gcc-8.2.0
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Exception not caught with gcc-8.2.0
  • From: Prasath P via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Output Symbol not Relocatable with -fPIC
  • From: Ahmad Nouralizadeh via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to add non-standard custom instruction with two destination registers in riscv-gnu-toolchain
  • From: Claudio Frongia via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: George Rinker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: George Rinker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: Peter0x44 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: George Rinker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: Peter0x44 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constructor
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: LMH via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran compiler problems
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• gfortran compiler problems
  • From: George Rinker via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Constructor
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Constructor
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [External] Re: _GLIBCXX11_USE_C99_STDLIB not being enabled
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: [External] Re: _GLIBCXX11_USE_C99_STDLIB not being enabled
  • From: "Dass, Reena Collins via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: _GLIBCXX11_USE_C99_STDLIB not being enabled
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• _GLIBCXX11_USE_C99_STDLIB not being enabled
  • From: "Dass, Reena Collins via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: unclear error message: operator->() must be a non-static member function
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• unclear error message: operator->() must be a non-static member function
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re: PGO option is not working and not documented
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• PGO option is not working and not documented
  • From: 潘凌安 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC soft limit for length of an identifier (C99 specification)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC soft limit for length of an identifier (C99 specification)
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gcc 94 / 10.2 has no GCC 20 ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Gcc 94 / 10.2 has no GCC 20 ?
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to know if GCC-7.5.0 affected by CVE-2021-37322
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to know if GCC-7.5.0 affected by CVE-2021-37322
  • From: Vivek Anand via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need to know if GCC-7.5.0 affected by CVE-2021-37322
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Need to know if GCC-7.5.0 affected by CVE-2021-37322
  • From: Vivek Anand via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem configuring with --with-specs
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: _Float16 handling changed in gcc 13?
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: _Float16 handling changed in gcc 13?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• _Float16 handling changed in gcc 13?
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: C Standard Libraries
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to properly build gcc/libgcc with both mno-red-zone and mcmodel=kernel on x86_64 ?
  • From: Ludovic Delabre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC runtime exception
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC runtime exception
  • From: Pascal Porcon via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why GCC-12 still inlined function which declared as noinline?
  • From: Tianyang Chou via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning on useless 'const' in a function declaration
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning on useless 'const' in a function declaration
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Warning on useless 'const' in a function declaration
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning on useless 'const' in a function declaration
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning on useless 'const' in a function declaration
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Warning on useless 'const' in a function declaration
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Common options funny things
  • From: Etienne Buira via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to issue a warning if a C++ template is defined as 'inline' or 'static'
  • From: "R. Diez via Gcc-help" <gcc-help@xxxxxxxxxxx>
• GCC does not build with latest MPC
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiler error
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compiler error
  • From: Natalie Tracy Anne Bloxam via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Ken Cunningham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling GMP dependency
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compiling GMP dependency
  • From: Hans Åberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: All US mirrors broken?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-14: -Wimplicit-function-declaration was promoted to an error
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc-14: -Wimplicit-function-declaration was promoted to an error
  • From: Jason Mancini via Gcc-help <gcc-help@xxxxxxxxxxx>
• All US mirrors broken?
  • From: Jason Mancini via Gcc-help <gcc-help@xxxxxxxxxxx>