GCC Help

• Thread Index

• 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>
• Re: LTO and global variables used to create a memory area
  • From: Niklas Dusenlund <niklas@xxxxxxxxxxxx>
• Re: LTO and global variables used to create a memory area
  • From: Niklas Dusenlund <niklas@xxxxxxxxxxxx>
• Re: LTO and global variables used to create a memory area
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• LTO and global variables used to create a memory area
  • From: Niklas Dusenlund <niklas@xxxxxxxxxxxx>
• Profiler call emitted after stack alignment, clobbers argument pointer
  • From: "J.W. Jagersma via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• How to determine what is default x86-64 -march= value for a given release of gcc?
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re:
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: Piyumali Dissanayake via Gcc-help <gcc-help@xxxxxxxxxxx>
• building ADA for bare-metal ARM processor
  • From: David Dudley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: replicate a legacy old gcc-3.4.0 arm-elf cross-toolchain?
  • From: Dennis Luehring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: EXTERNAL-Re: Inquiry Regarding -Wrange-loop-construct Warning Behavior in GCC 14
  • From: Sunil Kumar Dora <sunilkumar.dora@xxxxxxxxxxxxxxxx>
• Re: replicate a legacy old gcc-3.4.0 arm-elf cross-toolchain?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• replicate a legacy old gcc-3.4.0 arm-elf cross-toolchain?
  • From: Dennis Luehring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiry Regarding -Wrange-loop-construct Warning Behavior in GCC 14
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiry Regarding -Wrange-loop-construct Warning Behavior in GCC 14
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Inquiry Regarding -Wrange-loop-construct Warning Behavior in GCC 14
  • From: Sunil Kumar Dora <sunilkumar.dora@xxxxxxxxxxxxxxxx>
• How to update all SSA names in CFG after creating new PHI node?
  • From: Tianyang Chou via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::chrono: g++ 12.4 vs 13+ on bare metal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about hardware_destructive_interference_size for riscv64
  • From: Levi Zim via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about hardware_destructive_interference_size for riscv64
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Question about hardware_destructive_interference_size for riscv64
  • From: Levi Zim via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: full relocatable binaries without relocation table
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• full relocatable binaries without relocation table
  • From: Joshua Hudson via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Unnecessary header file inclusion
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Unnecessary header file inclusion
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to have a default specs file config file?
  • From: Dimitri Ledkov via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to have a default specs file config file?
  • From: Dimitri Ledkov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re: std::variant corruption
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::variant corruption
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::variant corruption
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::variant corruption
  • From: "James K. Lowden" <jklowden@xxxxxxxxxxxxxxx>
• Re: std::chrono: g++ 12.4 vs 13+ on bare metal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::chrono: g++ 12.4 vs 13+ on bare metal
  • From: Georg Gast <georg-gcc@xxxxxxxxxxxxxxxx>
• Re: std::chrono: g++ 12.4 vs 13+ on bare metal
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::chrono: g++ 12.4 vs 13+ on bare metal
  • From: Georg Gast <georg-gcc@xxxxxxxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Andrew C Aitchison via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -ffast-math algebraic optimizations on custom number types
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• -ffast-math algebraic optimizations on custom number types
  • From: Kai Song via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: sd@xxxxxxxxxxxxxx
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Trying to use the very new musttail attribute in 15.0.0
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Fiodar <fedor_qd@xxxxxxx>
• Trying to use the very new musttail attribute in 15.0.0
  • From: Bradley Lucier via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: __cxa_rethrow instead of __cxa_end_catch when omitting curly braces
  • From: Christoph Rüthing <christoph@xxxxxxxxxxxxx>
• AW: __cxa_rethrow instead of __cxa_end_catch when omitting curly braces
  • From: Christoph Rüthing <christoph@xxxxxxxxxxxxx>
• Re: __cxa_rethrow instead of __cxa_end_catch when omitting curly braces
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• __cxa_rethrow instead of __cxa_end_catch when omitting curly braces
  • From: Christoph Rüthing <christoph@xxxxxxxxxxxxx>
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: Georg Gast <georg-gcc@xxxxxxxxxxxxxxxx>
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: sd@xxxxxxxxxxxxxx
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: sd@xxxxxxxxxxxxxx
• Адк.: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: Фёдар . <fedor_qd@xxxxxxx>
• gcov can't collect gcda for systemd process(pid=1)
  • From: m17826839720 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Build Gcc 14.2 for arm-none-eabi: Gcc git or source from ARM developer?
  • From: Georg Gast <georg-gcc@xxxxxxxxxxxxxxxx>
• Fwd: GCC arm target does not generate the correct code for adc patterns
  • From: coshvji cujmlqef via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is Symbian configuration for crtfastmath.o correct?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is Symbian configuration for crtfastmath.o correct?
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re: Custom Float Instructions
  • From: Amit Hiremath via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Amit Hiremath via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GNU C++ toolchain for NVIDIA Grace cpu?
  • From: Tamar Christina via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is there a way to check if a tree_node is variable in GCC?
  • From: Tianyang Chou via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constexpr operator new?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GNU C++ toolchain for NVIDIA Grace cpu?
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: constexpr operator new?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: noexcept
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GNU C++ toolchain for NVIDIA Grace cpu?
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to initialize target backends properly
  • From: Simon Richter <Simon.Richter@xxxxxxxxxx>
• constexpr operator new?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• GNU C++ toolchain for NVIDIA Grace cpu?
  • From: David Aldrich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Regarding gcc compatibility with libc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Regarding gcc compatibility with libc
  • From: Kal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Amit Hiremath <amit.hmath@xxxxxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Amit Hiremath <amit.hmath@xxxxxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: Custom Float Instructions
  • From: Amit Hiremath <amit.hmath@xxxxxxxxxxxxxx>
• Re: Custom Float Instructions
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Custom Float Instructions
  • From: Amit Hiremath <amit.hmath@xxxxxxxxxxxxxx>
• Re: Inquiry About GCC 7.5.0 Compatibility with macOS 14 Sonoma on Apple M3
  • From: Iain Sandoe <idsandoe@xxxxxxxxxxxxxx>
• Re: Inquiry About GCC 7.5.0 Compatibility with macOS 14 Sonoma on Apple M3
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Inquiry About GCC 7.5.0 Compatibility with macOS 14 Sonoma on Apple M3
  • From: Sheideh Homayon via Gcc-help <gcc-help@xxxxxxxxxxx>
• Cross compiler build for Ada build fails with "unrecognized intrinsic subprogram"
  • From: Ahmad Bamba via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: libgcc crossback fails
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: libgcc crossback fails
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fw: libgcc crossback fails
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does gcc build try to link lpthreads and ldl for x86_64-w64-mingw32 host?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does gcc build try to link lpthreads and ldl for x86_64-w64-mingw32 host?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does gcc build try to link lpthreads and ldl for x86_64-w64-mingw32 host?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why does gcc build try to link lpthreads and ldl for x86_64-w64-mingw32 host?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why does gcc build try to link lpthreads and ldl for x86_64-w64-mingw32 host?
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• noexcept
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: cmath
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: cmath
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: cmath
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: cmath
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: cmath
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• cmath
  • From: Sven Bieg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: creating a new integer type in C (incompatible with other types)
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• creating a new integer type in C (incompatible with other types)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: array_type_nelts + 1 for VLAs
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: LoongArch incorrect codegen for std::byte_swap
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: array_type_nelts + 1 for VLAs
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: LoongArch incorrect codegen for std::byte_swap
  • From: Andrew Pinski via Gcc-help <gcc-help@xxxxxxxxxxx>
• array_type_nelts + 1 for VLAs
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• LoongArch incorrect codegen for std::byte_swap
  • From: pifminns deettnta via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: error: call of overloaded ‘to_chars(std::array<char, 10>::pointer, std::array<char, 10>::pointer, const int&, std::chars_format)’ is ambiguous
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• error: call of overloaded ‘to_chars(std::array<char, 10>::pointer, std::array<char, 10>::pointer, const int&, std::chars_format)’ is ambiguous
  • From: Saifi Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Accessing location_t on type_required attribute inside handler in plugin
  • From: Olle Lögdahl via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Building libstdc++ for MemorySanitizer
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building libstdc++ for MemorySanitizer
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building libstdc++ for MemorySanitizer
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building libstdc++ for MemorySanitizer
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building libstdc++ for MemorySanitizer
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building libstdc++ for MemorySanitizer
  • From: Phil Phil via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 11 with libstdc++-v3 fails to build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC 11 with libstdc++-v3 fails to build
  • From: Aleksi Venäläinen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: urgent issue: Asking forTechnical Support
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• urgent issue: Asking forTechnical Support
  • From: "王芳" <wangfang@xxxxxxxxxxxxxx>
• Re: how to install g77 and run
  • From: LMH via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Jack Pugmire via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Jack Pugmire via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how to install g77 and run
  • From: Toon Moene <toon@xxxxxxxxx>
• Re: how to install g77 and run
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• how to install g77 and run
  • From: Damaraju Phaneswararao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: [COMMITTED] Regenerate c.opt.urls
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• [COMMITTED] Regenerate c.opt.urls
  • From: Mark Wielaard <mark@xxxxxxxxx>
• Re: gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc-14-1-0: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
  • From: Mark Wielaard <mark@xxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Hard links created when installing gcc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to debug lto failures
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to debug lto failures
  • From: Manuel Lauss via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: ☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Hard links created when installing gcc
  • From: Jack Pugmire via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why can't statically linked programs have dynamic symbol table?
  • From: Fengkai Sun via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC option to create assembly listing with C source
  • From: Henrik Holst via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC option to create assembly listing with C source
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC option to create assembly listing with C source
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to use type_traits in a module unit without import std?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to get started with contribution.
  • From: Muskan Yadav via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [AVR] Specify location of __attribute__((__progmem__))
  • From: Levente via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [AVR] Specify location of __attribute__((__progmem__))
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• [no subject]
  • From: Unknown
• [AVR] Specify location of __attribute__((__progmem__))
  • From: Levente via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Register pressure reduction techniques on an accumulator machine
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Register pressure reduction techniques on an accumulator machine
  • From: Filip Kokosiński via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building GCC, compiler flags do not propagate through Makefiles
  • From: Gordon Steemson via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: libstdc++.so did not link cause of libm.a was not compiled with fpic
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how to build gcc-13.3.0 without "-g" option ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how to build gcc-13.3.0 without "-g" option ?
  • From: Valerii Valeev via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how to build gcc-13.3.0 without "-g" option ?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• how to build gcc-13.3.0 without "-g" option ?
  • From: Valerii Valeev via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC 7.5.0 on PPC Mac OS X 10.4.11/Tiger (ppc-apple-darwin8) reports "ld: bl out of range ..."
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• how to get frame size from debug info?
  • From: Red Plait <redp@xxxxxxx>
• Re: libstdc++.so did not link cause of libm.a was not compiled with fpic
  • From: Klaus Rudolph via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Vectorisation of loop does not work with different variable names
  • From: Max Sagebaum <max.sagebaum@xxxxxxxxxxxxxxxxx>
• Re: Vectorisation of loop does not work with different variable names
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: libstdc++.so did not link cause of libm.a was not compiled with fpic
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: libstdc++.so did not link cause of libm.a was not compiled with fpic
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• AI gcc?
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problems building cross compiler on x86 host for arm
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• libstdc++.so did not link cause of libm.a was not compiled with fpic
  • From: Klaus Rudolph via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problems building cross compiler on x86 host for arm
  • From: Klaus Rudolph via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcov stand alone environment failing
  • From: Christopher Campbell via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problems building cross compiler on x86 host for arm
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Inquiries regarding the specifications of __builtin_aarch64_simd_qi (__builtin_aarch64_simd_qi の仕様に関して問い合わせ)
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• problems building cross compiler on x86 host for arm
  • From: Klaus Rudolph via Gcc-help <gcc-help@xxxxxxxxxxx>
• Inquiries regarding the specifications of __builtin_aarch64_simd_qi (__builtin_aarch64_simd_qi の仕様に関して問い合わせ)
  • From: "Narishima, Keiichirou via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Vectorisation of loop does not work with different variable names
  • From: Max Sagebaum <max.sagebaum@xxxxxxxxxxxxxxxxx>
• riscv needs to set a better default
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• libgcov with arm-none-eabi standalone platform embedded controller
  • From: Christopher Campbell via Gcc-help <gcc-help@xxxxxxxxxxx>
• Request for clarification on gcc test results deviations
  • From: Harish Sadineni via Gcc-help <gcc-help@xxxxxxxxxxx>
• Need help with runtime error "libgomp: target function wasn't mapped"
  • From: Patrick Begou via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Which GCC version start to support RISC-V RVV1.0
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Attribute with identifiers arguments
  • From: דידי אפשטיין via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: subobject init override
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: subobject init override
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Which GCC version start to support RISC-V RVV1.0
  • From: Erick Kuo-Chen Huang(黃國鎭) via Gcc-help <gcc-help@xxxxxxxxxxx>
• Libgcov.a
  • From: Christopher Campbell via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Gejoe Daniel via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Required Help-Reg
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: Unknown
• Re: Required Help-Reg
  • From: sunderchand via Gcc-help <gcc-help@xxxxxxxxxxx>
• Required Help-Reg
  • From: sunderchand via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Certificate leave application request
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Certificate leave application request
  • From: Brian Khumalo via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Build fails to find installed Glibc at Stage 2 of bootstrapping
  • From: rubisetcie via Gcc-help <gcc-help@xxxxxxxxxxx>
• gdb8.2 works very slow when running gcc11.2 binaries
  • From: "Bar, Yaniv via Gcc-help" <gcc-help@xxxxxxxxxxx>
• [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Gejoe Daniel via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: Hongtao Liu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC Installation breaks older header files
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• A question about flexible array members
  • From: Benoît Dufour via Gcc-help <gcc-help@xxxxxxxxxxx>
• how to build __builtin_va_arg_pack() example
  • From: Massimiliano Cialdi via Gcc-help <gcc-help@xxxxxxxxxxx>
• [analyzer] __attribute__((malloc)) when pointer is returned in argument
  • From: Alon Bar-Lev via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to set alignment and READONLY of a brand new section
  • From: Massimiliano Cialdi via Gcc-help <gcc-help@xxxxxxxxxxx>
• subobject init override
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: anand akhare via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: request for bugzilla account
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• request for bugzilla account
  • From: 胡启志 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: official gnu as reference for x86 instructions - specifically cmpxchg
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• official gnu as reference for x86 instructions - specifically cmpxchg
  • From: anand akhare via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Optimization of signed integer overflow since GCC 8
  • From: "Richard Earnshaw \(lists\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Optimization of signed integer overflow since GCC 8
  • From: Rademacher Lars via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: question on alignment of anonymous unions inside structs
  • From: Henrik Holst via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: question on alignment of anonymous unions inside structs
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• question on alignment of anonymous unions inside structs
  • From: Henrik Holst via Gcc-help <gcc-help@xxxxxxxxxxx>
• __float128 support
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: In need of help to understand the program behaviour while loading shared libraries and at linking time.
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Reconciling -save-temps intermediate file with cfg
  • From: Matthias Pfaller <leo@xxxxxxxx>
• gcc 10.5: libsanitizer: "-fsanitize=leak" Issue
  • From: "Estner, Michael via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Reconciling -save-temps intermediate file with cfg
  • From: 0xd--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 15?
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Gejoe Daniel via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 15?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• In need of help to understand the program behaviour while loading shared libraries and at linking time.
  • From: ShriHari <shrihari@xxxxxxxxxxxxx>
• Re: Gcc Use
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Gcc Use
  • From: peppermint--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [Regarding GCOV].gcda:stamp mismatch with notes file
  • From: Gejoe Daniel via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: problem with lto
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Music 101
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Strange message : fatal error, run-time library not installed correctly
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• problem with lto
  • From: 王淳洋 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Request for IP Troubleshooting
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Request for IP Troubleshooting
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Request for IP Troubleshooting
  • From: Zaven Karapetyan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Confusion on the latest git
  • From: Stuff Received <stuff@xxxxxxxxxxxxxxxxx>
• How can I get the linker to use the correct function
  • From: Chris Abbott via Gcc-help <gcc-help@xxxxxxxxxxx>
• Confusion on the latest git
  • From: Stuff Received <stuff@xxxxxxxxxxxxxxxxx>
• Re: Difference between *-none-elf and *-linux-gnu configurations
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Difference between *-none-elf and *-linux-gnu configurations
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Difference between *-none-elf and *-linux-gnu configurations
  • From: Johannes Krottmayer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC __asm__( … )
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC __asm__( … )
  • From: alines #7777 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: Stefan Franke <stefan@xxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: optimizer discards sign information
  • From: <stefan@xxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: optimizer discards sign information
  • From: <stefan@xxxxxxxxx>
• Re: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: optimizer discards sign information
  • From: <stefan@xxxxxxxxx>
• Re: optimizer discards sign information
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: optimizer discards sign information
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• optimizer discards sign information
  • From: <stefan@xxxxxxxxx>
• Re: simple optimisation question
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• simple optimisation question
  • From: zamfofex <zamfofex@xxxxxxxx>
• Re: Multiple libstdc++ builds
  • From: John F via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Multiple libstdc++ builds
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Multiple libstdc++ builds
  • From: John F via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bug in GCC's resolution of C++20 reversed operator== functions?
  • From: Chris Peterson <cpeterso@xxxxxxxxxxxx>
• Re: Bug in GCC's resolution of C++20 reversed operator== functions?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Bug in GCC's resolution of C++20 reversed operator== functions?
  • From: Chris Peterson <cpeterso@xxxxxxxxxxxx>
• Re: g++ with VLA
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: g++ with VLA
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: g++ with VLA
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• g++ with VLA
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: GCC's thin lto PLEASE
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC's thin lto PLEASE
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC's thin lto PLEASE
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC's thin lto PLEASE
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: your mail
  • From: Centurion via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: your mail
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• [no subject]
  • From: Centurion via Gcc-help <gcc-help@xxxxxxxxxxx>
• Missing __asan_stack_free in Custom KASAN Implementation
  • From: Julian Zboril <julian.zboril@xxxxxx>
• Re: Building the latest master GCC using msys2.
  • From: Peter0x44 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building the latest master GCC using msys2.
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building the latest master GCC using msys2.
  • From: peter0x44 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: a problem when using gcc
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• a problem when using gcc
  • From: guo via Gcc-help <gcc-help@xxxxxxxxxxx>
• Suggestions for gnuc extensions
  • From: l lerasi via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: Gnu compiler version 4.7.0, dialect -std=c99 with -fshort-enums vs. GHS with --short_enum
  • From: Homam Alkhateeb <Homam.Alkhateeb@xxxxxxxxxx>
• Re: Gnu compiler version 4.7.0, dialect -std=c99 with -fshort-enums vs. GHS with --short_enum
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• AW: Gnu compiler version 4.7.0, dialect -std=c99 with -fshort-enums vs. GHS with --short_enum
  • From: Homam Alkhateeb <Homam.Alkhateeb@xxxxxxxxxx>
• Re: mfix-cortex-a53
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: mfix-cortex-a53
  • From: Wilco Dijkstra via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: mfix-cortex-a53
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: mfix-cortex-a53
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Gnu compiler version 4.7.0, dialect -std=c99 with -fshort-enums vs. GHS with --short_enum
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Gnu compiler version 4.7.0, dialect -std=c99 with -fshort-enums vs. GHS with --short_enum
  • From: Homam Alkhateeb <Homam.Alkhateeb@xxxxxxxxxx>
• mfix-cortex-a53
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: Sunandha Sunandha via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Suggesting
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Suggesting
  • From: Henrik Mannerström via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Understanding GCC Behaviour
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Suggesting
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Suggesting
  • From: Sergio Peña via Gcc-help <gcc-help@xxxxxxxxxxx>
• Understanding GCC Behaviour
  • From: Pouria Khajepour via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Using -frandom-seed=0 for reproducible builds?
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Using -frandom-seed=0 for reproducible builds?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Gcc version affects program execution efficiency
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Gcc version affects program execution efficiency
  • From: abzhou36 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [wwwdocs] GCC processor independent install?
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• [wwwdocs] GCC processor independent install?
  • From: Vru Inbvi via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: About Multilib
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: ECCN GCC/GDB
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• ECCN GCC/GDB
  • From: "Giovanna Perez \(CW\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: About Multilib
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: About Multilib
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: About Multilib
  • From: Kai Ruottu via Gcc-help <gcc-help@xxxxxxxxxxx>
• About Multilib
  • From: yuucyf via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Troubles with C++20 modules and CMake
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Troubles with C++20 modules and CMake
  • From: "Hlusicka, Jakub \(Ceske vysoke uceni technicke v Praze -...\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: GCC build from source. Where does a build of GCC, put the "gcc" executable???
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC build from source. Where does a build of GCC, put the "gcc" executable???
  • From: gemesys--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiler message -Wunused confusion
  • From: Jędrzej Dudkiewicz via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Download GCC Compiler
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Download GCC Compiler
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiler message -Wunused confusion
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiler message -Wunused confusion
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Compiler message -Wunused confusion
  • From: "A. Mc. via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Download GCC Compiler
  • From: Debjyoti Ghosh via Gcc-help <gcc-help@xxxxxxxxxxx>
• GNAT License
  • From: S Beard via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: What does gcc does and more details of gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• What does gcc does and more details of gcc
  • From: Qwame Owusu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Sanitizer CHECK failed: sanitizer_allocator_primary64.h:133
  • From: Deepthi H via Gcc-help <gcc-help@xxxxxxxxxxx>
• test case failures for bad-mapper-3.C in gcc-13.2.0
  • From: Sadineni Harish via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Sanitizer CHECK failed: sanitizer_allocator_primary64.h:133
  • From: Sam James via Gcc-help <gcc-help@xxxxxxxxxxx>
• Sanitizer CHECK failed: sanitizer_allocator_primary64.h:133
  • From: Deepthi H via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fwd: Problems building gcc
  • From: T Rex via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fwd: Problems building gcc
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Problems building gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fwd: Problems building gcc
  • From: T Rex via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problems building gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Info about libatomic not automatically linked with C11 code
  • From: Vincenzo Palazzo via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problems building gcc
  • From: T Rex via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Amol Surati via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Assignment of union containing const-qualifier member
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: AW: autoinc / postinc not used
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Issues compiling gcc 12.3.0
  • From: Damas Joao CHST via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Issues compiling gcc 12.3.0
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Issues compiling gcc 12.3.0
  • From: Damas Joao CHST via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Issues compiling gcc 12.3.0
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Issues compiling gcc 12.3.0
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Issues compiling gcc 12.3.0
  • From: Damas Joao CHST via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiry for gcc test results
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Inquiry for gcc test results
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Inquiry for gcc test results
  • From: Sadineni Harish via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Errors in building gcc-4.4.3
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• AW: AW: autoinc / postinc not used
  • From: <stefan@xxxxxxxxx>
• Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors in building gcc-4.4.3
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Errors in building gcc-4.4.3
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• libstdc++ build error: ‘__val_a’ may be used uninitialized [-Werror=maybe-uninitialized]
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: Reporting unnecessary inclusion of header files.
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Reporting unnecessary inclusion of header files.
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Reporting unnecessary inclusion of header files.
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Reporting unnecessary inclusion of header files.
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Reporting unnecessary inclusion of header files.
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: autoinc / postinc not used
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Errors in building gcc-4.4.3
  • From: Yaxuan Wen via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: autoinc / postinc not used
  • From: <stefan@xxxxxxxxx>
• RE: Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: "Dallman, John via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: autoinc / postinc not used
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• autoinc / postinc not used
  • From: <stefan@xxxxxxxxx>
• Re: Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: "Dallman, John via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [patch,avr,applied] Fix PR target/113156 - ICE when building libgcc
  • From: Levente via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is there a way to use __builtin___memcpy_chk() for compiler-generated memcpy calls?
  • From: "Dallman, John via Gcc-help" <gcc-help@xxxxxxxxxxx>
• [patch,avr,applied] Fix PR target/113156 - ICE when building libgcc
  • From: Georg-Johann Lay <avr@xxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC Init Flexible Array Member
  • From: Rodrigo Abreu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Can't compile GCC-14 for AVR
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Can't compile GCC-14 for AVR
  • From: Levente via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Do definitions in headers still help optimization?
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Do definitions in headers still help optimization?
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Do definitions in headers still help optimization?
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Do definitions in headers still help optimization?
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Do definitions in headers still help optimization?
  • From: Licht Martin Werner via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Question about GNU Compiler Collection
  • From: Stuff Received <stuff@xxxxxxxxxxxxxxxxx>
• Re: Question about GNU Compiler Collection
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Question about GNU Compiler Collection
  • From: "McKenna, Stewart via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Mark Rutland via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• -Wmissing-field-initializers on C++ warns about missing initializer despite designated initializers present
  • From: Jakob Hasse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran Compiler Download
  • From: niXman via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran Compiler Download
  • From: Ovais Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gfortran Compiler Download
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• gfortran Compiler Download
  • From: Ovais Khan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• LIBRARY_PATH priority - Reg
  • From: Lakshmi Narayana Velayudam via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Get Help for Your Accurate Project Estimation Requirement
  • From: Cody Cox via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: Mark Rutland via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference to `__aarch64_cas4_sync' error on arm64 native build
  • From: richard clark via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Odd error with the "X" inline assembly constraint
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Odd error with the "X" inline assembly constraint
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: pragma GCC optimize prevents inlining
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: --enable-nls doesn't work as expected
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: --enable-nls doesn't work as expected
  • From: niXman via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: --enable-nls doesn't work as expected
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• --enable-nls doesn't work as expected
  • From: niXman via Gcc-help <gcc-help@xxxxxxxxxxx>