GCC Help

• Thread Index

• AW: Problem porting gcc 12
  • From: "Stefan Franke" <stefan@xxxxxxxxx>
• Re: Problem porting gcc 12
  • From: Kalamatee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem porting gcc 12
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem porting gcc 12
  • From: Kalamatee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem porting gcc 12
  • From: Kalamatee via Gcc-help <gcc-help@xxxxxxxxxxx>
• internal compiler error: Segmentation fault
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fwd: Multiple symbols defined in object files that should not be there.
  • From: Steve Thompson via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Multiple symbols defined in object files that should not be there.
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Multiple symbols defined in object files that should not be there.
  • From: Steve Thompson via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:
  • From: Sanniddha Chakrabarti via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [no subject]
  • From: Sanniddha Chakrabarti via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help cross-compiling gcc
  • From: Vincent Fortier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Large projects using -fmerge-all-constants?
  • From: Qwert Nerdish via Gcc-help <gcc-help@xxxxxxxxxxx>
• Wrong dwarf version does not allow to debug 32bit binary files
  • From: alexandre schenberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning for unsafe/insecure functions
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning for unsafe/insecure functions
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Warning for unsafe/insecure functions
  • From: Rajeev Bansal via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __attribute__ error ("message")
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• __attribute__ error ("message")
  • From: Jonny Grant <jg@xxxxxxxx>
• Alignas attribute for enums
  • From: Fahad Nayyar <fahad17049@xxxxxxxxxxx>
• Getting code coverage in Ada for tasks, protected objects and generics
  • From: "Beek, Graham via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Problem understand optimization with inline asm
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Where to find implementation of __int128_t
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Where to find implementation of __int128_t
  • From: Frederick Virchanza Gotham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem understand optimization with inline asm
  • From: Andrew Haley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem understand optimization with inline asm
  • From: Andrew Haley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem understand optimization with inline asm
  • From: Kalamatee via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __riscv_v_intrinsic status
  • From: Kito Cheng via Gcc-help <gcc-help@xxxxxxxxxxx>
• __riscv_v_intrinsic status
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc param min-pagesize
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: float is constructible from double, C++23's std::float13_t is not
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: float is constructible from double, C++23's std::float13_t is not
  • From: Filippo Bistaffa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: float is constructible from double, C++23's std::float13_t is not
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• float is constructible from double, C++23's std::float13_t is not
  • From: Filippo Bistaffa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: building gcc 3.0.4 on mips-dec-osf1: where are CPP definitions set?
  • From: Dennis Grevenstein via Gcc-help <gcc-help@xxxxxxxxxxx>
• [offtopic] old profiler prof on Debian (for -p profiling)
  • From: Basile Starynkevitch <basile@xxxxxxxxxxxxxxxxx>
• Re: building gcc 3.0.4 on mips-dec-osf1: where are CPP definitions set?
  • From: Dennis Grevenstein via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: building gcc 3.0.4 on mips-dec-osf1: where are CPP definitions set?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• building gcc 3.0.4 on mips-dec-osf1: where are CPP definitions set?
  • From: Dennis Grevenstein via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: intrinsics and sign-conversion
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: intrinsics and sign-conversion
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• intrinsics and sign-conversion
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Error building gcc master: gcc/opts.cc: -Werror=format-truncation
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Error building gcc master: gcc/opts.cc: -Werror=format-truncation
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Error building gcc master: gcc/opts.cc: -Werror=format-truncation
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Error building gcc master: gcc/opts.cc: -Werror=format-truncation
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Error building gcc master: gcc/opts.cc: -Werror=format-truncation
  • From: Alejandro Colomar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Header file dependency, rpath, soname and more with GCC
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:Header file dependency, rpath, soname and more with GCC
  • From: ljh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Header file dependency, rpath, soname and more with GCC
  • From: ljh via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Andrew Haley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Frederick Virchanza Gotham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Frederick Virchanza Gotham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Frederick Virchanza Gotham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Functions and Global Variables defined in Libraries
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Functions and Global Variables defined in Libraries
  • From: Frederick Virchanza Gotham via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Questions about std::generator
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Questions about std::generator
  • From: 이영민 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: std::shared_mutex deadlock
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::shared_mutex deadlock
  • From: Bastian Hauda via Gcc-help <gcc-help@xxxxxxxxxxx>
• Slight problem with nano_newlib in a bare metal build for an Efinity T-35.
  • From: Damien Towning via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fwd: Fwd: [PATCH] update copyright year in libstdcc++ manual
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Spelling mistake in libstdc++-v3/include/bits/cow_string.h
  • From: Jonny Grant <jg@xxxxxxxx>
• Error compiling gcc13 : profile count data file not found
  • From: Chris S via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Nguyen Duc Sy <sy.nguyen-duc@xxxxxxxxxxxxxx>
• Static analyzer (double-free): false positive for loops
  • From: Pierrick Philippe <pierrick.philippe@xxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Nguyen Duc Sy <sy.nguyen-duc@xxxxxxxxxxxxxx>
• Re: malloc for large allocations
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: malloc for large allocations
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• malloc for large allocations
  • From: bernardwidynski--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• [NEED HELP][GCOV] uncoverage virtual destructor
  • From: Nguyen Duc Sy <sy.nguyen-duc@xxxxxxxxxxxxxx>
• Re: Spelling mistake in libstdc++-v3/include/bits/cow_string.h
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [EXT]:Re: Need help with Proc compilation with GCC 4.8.3
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need help with Proc compilation with GCC 4.8.3
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [EXT]:Re: Need help with Proc compilation with GCC 4.8.3
  • From: "Mahankali, Sharath Kumar via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Need help with Proc compilation with GCC 4.8.3
  • From: "James K. Lowden" <jklowden@xxxxxxxxxxxxxxx>
• Spelling mistake in libstdc++-v3/include/bits/cow_string.h
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Need help with Proc compilation with GCC 4.8.3
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Need help with Proc compilation with GCC 4.8.3
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• note: non-delegitimized UNSPEC UNSPEC_SET_GOT (14) found in variable location
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Need help with Proc compilation with GCC 4.8.3
  • From: "Kondreddy, Vinay Kumar via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: fail with the following concept code
  • From: Watson Romero via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: fail with the following concept code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• fail with the following concept code
  • From: Watson Romero via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc trunk on riscv64
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• -fanalyzer false positive on gcc 12.1 and gcc 12.2
  • From: Martin Georgiev via Gcc-help <gcc-help@xxxxxxxxxxx>
• AddressSanitizer halt_on_error problems with gcc 9.4 x64
  • From: Edgar Mobile via Gcc-help <gcc-help@xxxxxxxxxxx>
• switch to tell which templates are instanciated
  • From: Julien D Arques via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: recommended optimization level when programming C++ contracts
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• recommended optimization level when programming C++ contracts
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to omit libc (newlib) on bare metal (freestanding)?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bootstrap failure on Fedora 37
  • From: Salvatore Filippone via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to omit libc (newlib) on bare metal (freestanding)?
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Bootstrap failure on Fedora 37
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bootstrap failure on Fedora 37
  • From: Salvatore Filippone via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bootstrap failure on Fedora 37
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Bootstrap failure on Fedora 37
  • From: Salvatore Filippone via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Marc Glisse via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Recursive SIGSEGV question
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Recursive SIGSEGV question
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tip to reduce manual template declaration?
  • From: Julien D Arques via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Tip to reduce manual template declaration?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Tip to reduce manual template declaration?
  • From: Julien D Arques via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Extra import symbol in debug build
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Extra import symbol in debug build
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Jonny Grant <jg@xxxxxxxx>
• Question about points-to analysis
  • From: Pierrick Philippe <pierrick.philippe@xxxxxxxx>
• Re: Could __builtin_printf parameters be optimized when being compiled
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Could __builtin_printf parameters be optimized when being compiled
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Bytes of long double - trouble . . .
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• ld.lld: error: unable to find library -lgcc_eh
  • From: jay Taylor <Jie@xxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross Compiling for riscv64
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Cross Compiling for riscv64
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• avr-gcc: direct register access suppresses optimization
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Using the kernel thread pointer on aarch64 (tpidr_el1)
  • From: Zach 1 via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Using the kernel thread pointer on aarch64 (tpidr_el1)
  • From: Kyrylo Tkachov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Using the kernel thread pointer on aarch64 (tpidr_el1)
  • From: Zach 1 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem cross-compiling gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem cross-compiling gcc
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Can't build gcc-trunk on Linux
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• build error --std=c++17 vs --std=c++23 -Wrestrict "may overlap up to 9223372036854775813 bytes at offset -3"
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Can't build gcc-trunk on Linux
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Can't build gcc-trunk on Linux
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Can't build gcc-trunk on Linux
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Random Crash Observed while running program compiled with latest gcc
  • From: praveen ab via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: std::string add nullptr attribute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiler error when using typedef void as function parameter with gcc 4.4.2
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compiler error when using typedef void as function parameter with gcc 4.4.2
  • From: "Singh, Mithun via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• std::string add nullptr attribute
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Random Crash Observed while running program compiled with latest gcc
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Random Crash Observed while running program compiled with latest gcc
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Random Crash Observed while running program compiled with latest gcc
  • From: praveen ab via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does this unrolled function write to the stack?
  • From: Gaelan Steele via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does this unrolled function write to the stack?
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does this unrolled function write to the stack?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does this unrolled function write to the stack?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why does this unrolled function write to the stack?
  • From: Gaelan Steele via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Cross compiler riscv64 building
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bytes of long double - trouble . . .
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bytes of long double - trouble . . .
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Cross compiler riscv64 building
  • From: Sagar Acharya via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bytes of long double - trouble . . .
  • From: henri.cloetens@xxxxxxxxxx
• Bytes of long double - trouble . . .
  • From: Sergey Smith <sergey-16a5@xxxxxxx>
• Help with GCC function attributes
  • From: Martin Georgiev via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Errors when trying to use C++ modules with cmake and GCC
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Errors when trying to use C++ modules with cmake and GCC
  • From: HHN via Gcc-help <gcc-help@xxxxxxxxxxx>
• define_cpu_unit syntax clarification
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how does -Wstringop-truncation work?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how does -Wstringop-truncation work?
  • From: Patrick Herbst via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: how does -Wstringop-truncation work?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• how does -Wstringop-truncation work?
  • From: Patrick Herbst via Gcc-help <gcc-help@xxxxxxxxxxx>
• Help about plugins - GIMPLE_COND
  • From: Pierrick Philippe <pierrick.philippe@xxxxxxxx>
• Re: Optimization auto-setting _FORTIFY_SOURCE ??
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Optimization auto-setting _FORTIFY_SOURCE ??
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Optimization auto-setting _FORTIFY_SOURCE ??
  • From: Patrick Herbst via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [GCC][Windows] header file inclusion on windows
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: [GCC][Windows] header file inclusion on windows
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [GCC][Windows] header file inclusion on windows
  • From: Mena Makary via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Christer Solskogen via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Arsen Arsenović via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Mark Butt <mark@xxxxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Michael Pape via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Correct way to provide a C callback function nside C++
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Correct way to provide a C callback function nside C++
  • From: Pepe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Gcov produces too little output
  • From: Edgar Mobile via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Mark Butt <mark@xxxxxxxxxxxxx>
• Re: Executable size
  • From: NightStrike via Gcc-help <gcc-help@xxxxxxxxxxx>
• Executable size
  • From: Mike Rejsa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building and install GCC 8.3.0, OpenBSD 7.2 on DEC Alpha EV5
  • From: Mark Butt <mark@xxxxxxxxxxxxx>
• Re: .data segment
  • From: ratheesh kannoth via Gcc-help <gcc-help@xxxxxxxxxxx>
• .data segment
  • From: ratheesh kannoth via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Active patch for c23 #embed feature?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Active patch for c23 #embed feature?
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: get make error when build gcc-13 on m1 MacOS 13
  • From: Iain Sandoe <iain@xxxxxxxxxxxx>
• Re: get make error when build gcc-13 on m1 MacOS 13
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• get make error when build gcc-13 on m1 MacOS 13
  • From: 徐保钰 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Plugin access machine code
  • From: Alex Wieser via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is it possible to insert own "function points" via define in code (similar to #line), especially for --coverage?
  • From: Simon Sobisch via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: no input files when calling gfortran
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling file with subroutines using gfortran
  • From: Patrick Begou via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: no input files when calling gfortran
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: no input files when calling gfortran
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling file with subroutines using gfortran
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling file with subroutines using gfortran
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: no input files when calling gfortran
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling file with subroutines using gfortran
  • From: Patrick Begou via Gcc-help <gcc-help@xxxxxxxxxxx>
• no input files when calling gfortran
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compiling file with subroutines using gfortran
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help cross-compiling gcc
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: help cross-compiling gcc
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help cross-compiling gcc
  • From: Vincent Fortier via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help cross-compiling gcc
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Finding repetitions of 8-tuple collections
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Finding repetitions of 8-tuple collections
  • From: Hans Lonsdale via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC+NVPTX -gpu=managed flag
  • From: "tempo.ordito_0m--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• help cross-compiling gcc
  • From: Vincent Fortier via Gcc-help <gcc-help@xxxxxxxxxxx>
• -fmakelist and -fmakeinit unrecognized options for gm2 (GCC) 13.0.0 20221228
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• C++ complier
  • From: Tuomas Lopez via Gcc-help <gcc-help@xxxxxxxxxxx>
• way to run some plugin before preprocessing stage
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Support for the -G option of the C frontend
  • From: John Scott via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC for Windows
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC for Windows
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Need Help: gcc suppport for bpf target
  • From: SuHsueyu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC for Windows
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• GCC for Windows
  • From: Oleksii Khramkov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Usability of --with-specs option
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Usability of --with-specs option
  • From: "Mahmoud, Abdulrahman (DI SW ICS MNA)" <Abdulrahman_Mahmoud@xxxxxxxxxx>
• Re: XOPEN, POSIX and BSD defines in C vs. C++ code
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• XOPEN, POSIX and BSD defines in C vs. C++ code
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Is there an intrinsic similar to _BitScanForward on Linux?
  • From: Václav Haisman via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC_EXEC_PREFIX or option -B needed to find cc1 and crt*.o files
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc optimization option value
  • From: hongjie wu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: virtual memory exhausted: Cannot allocate memory
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: which compiler is right (either to compile or to barf)...
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: virtual memory exhausted: Cannot allocate memory
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• which compiler is right (either to compile or to barf)...
  • From: leon zadorin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Avoiding stack buffer clear being optimised out
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Avoiding stack buffer clear being optimised out
  • From: Jonny Grant <jg@xxxxxxxx>
• Re: Is there an intrinsic similar to _BitScanForward on Linux?
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: virtual memory exhausted: Cannot allocate memory
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is there an intrinsic similar to _BitScanForward on Linux?
  • From: bootmgr--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• virtual memory exhausted: Cannot allocate memory
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• access to include path in front end
  • From: "James K. Lowden" <jklowden@xxxxxxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: `make pdf`: How is papersize configured?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• `make pdf`: How is papersize configured?
  • From: Jan-Benedict Glaw <jbglaw@xxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
  • From: Peter Dyballa via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: :got: modifier in assembler
  • From: Bob Plantz via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: :got: modifier in assembler
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• :got: modifier in assembler
  • From: Bob Plantz via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Saifi Khan <saifi.khan@xxxxxxxxx>
• Re: gcc linker compression
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc linker compression
  • From: hongjie wu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Yubin Ruan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: advertising on savannah.gnu.org
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• advertising on savannah.gnu.org
  • From: James Murphy <j@xxxxxxxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Voice message from a active contact in your list.
  • From: Telecom via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Martin Oberzalek via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Guaranteed copy elision
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-commit-mklog fails
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Does current gcc have segment compression option?
  • From: Wu yanan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-commit-mklog fails
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Does current gcc have segment compression option?
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-commit-mklog fails
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc-commit-mklog fails
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc-commit-mklog fails
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Does current gcc have segment compression option?
  • From: Wu yanan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Guaranteed copy elision
  • From: Yubin Ruan via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: "Saifi Khan" <saifi.khan@xxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Saifi Khan <saifi.khan@xxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Saifi Khan <saifi.khan@xxxxxxxxx>
• Re: top-level build target that triggers 'make doc-html-doxygen'
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• top-level build target that triggers 'make doc-html-doxygen'
  • From: Saifi Khan <saifi.khan@xxxxxxxxx>
• Download link
  • From: jack maroon via Gcc-help <gcc-help@xxxxxxxxxxx>
• errors message groups id?
  • From: Michel via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to check for a specific language in gcc/tree.cc?
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Linking to dynamic libraries compiled by old version g++
  • From: 孙世龙 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Linking to dynamic libraries compiled by old version g++
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Bootstrap fail, gcc-13-20221030 on macOS 13
  • From: Simon Wright via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: simd, redundant pcmpeqb and pxor
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: simd, redundant pcmpeqb and pxor
  • From: Hongtao Liu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: simd, redundant pcmpeqb and pxor
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• i need aarch64-w64-mingw32 target for gcc and binutils
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: simd, redundant pcmpeqb and pxor
  • From: Hongtao Liu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Linking to dynamic libraries compiled by old version g++
  • From: 孙世龙 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Bootstrap fail, gcc-13-20221030 on macOS 13
  • From: Simon Wright via Gcc-help <gcc-help@xxxxxxxxxxx>
• simd, redundant pcmpeqb and pxor
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Scope of 'new' TYPE_FIELDS and old TYPE_METHODS?
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCOV in standalone env, nostdlib
  • From: Erich via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Difference in -E output
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Difference in -E output
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Difference in -E output
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• Cross compiling C++ for MPC5200
  • From: Todd Sampson <tsampson@xxxxxxxxxxxxxxxxx>
• Re: Unions, common-initial subsequence and UB
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Unions, common-initial subsequence and UB
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: How to make sure GCC links only with old runtime that is supplied with the system
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to make sure GCC links only with old runtime that is supplied with the system
  • From: olologin via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Ignoring 'target specific option mismatch' on inline
  • From: "J.W. Jagersma via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: Ignoring 'target specific option mismatch' on inline
  • From: Hongtao Liu via Gcc-help <gcc-help@xxxxxxxxxxx>
• Ignoring 'target specific option mismatch' on inline
  • From: "J.W. Jagersma via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re[2]: RE: CreateProcess No such file or directory
  • From: fedor_qd@xxxxxxx
• Re: Arm AARCH64 string alignment in .rodata
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Arm AARCH64 string alignment in .rodata
  • From: Bob Plantz via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Can't I build gcc with multilib support?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Can't I build gcc with multilib support?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re:Can't I build gcc with multilib support?
  • From: alexandre schenberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: David Brown via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Can't I build gcc with multilib support?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Iain Sandoe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC V10.3 compiler issue.
  • From: David Edelsohn via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: GCC V10.3 compiler issue.
  • From: Iain Sandoe <iain@xxxxxxxxxxxx>
• Can't I build gcc with multilib support?
  • From: alexandre schenberg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Iain Sandoe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Declaring a function to be of wprintf style
  • From: Lee Shallis via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: help removing unnecessary zero-extension
  • From: Richard Sandiford via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Use coroutines for avr-gcc
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• help removing unnecessary zero-extension
  • From: William Tambe via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is it possible to build gcc itself and binutils-gdb statically?
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: AW: GCC builds with relative searchpaths instead of absolute
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: RE: CreateProcess No such file or directory
  • From: Tom Kacvinsky via Gcc-help <gcc-help@xxxxxxxxxxx>
• AW: GCC builds with relative searchpaths instead of absolute
  • From: <stefan@xxxxxxxxx>
• Re: RE: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC builds with relative searchpaths instead of absolute
  • From: Nuno Silva via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC builds with relative searchpaths instead of absolute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Use coroutines for avr-gcc
  • From: Wilhelm Meier <wilhelm.meier@xxxxxxxx>
• Re: GCC builds with relative searchpaths instead of absolute
  • From: Nuno Silva via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC builds with relative searchpaths instead of absolute
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC builds with relative searchpaths instead of absolute
  • From: Nuno Silva via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: RE: CreateProcess No such file or directory
  • From: fedor_qd@xxxxxxx
• RE: CreateProcess No such file or directory
  • From: Tamar Christina via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: CreateProcess No such file or directory
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• CreateProcess No such file or directory
  • From: mizo 91 via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Lead source at NAB Show 2022
  • From: Bridget Aguilar via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc inline asm unknown mnemonics problems
  • From: Andrew Haley via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Applying GNU style automatically
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc inline asm unknown mnemonics problems
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc inline asm unknown mnemonics problems
  • From: mike <gmbgmb@xxxxxxxxxxxxxx>
• Applying GNU style automatically
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Is GCC optimize 2d vector?
  • From: Леонид via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to move gcc to compile to my own architecture?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to move gcc to compile to my own architecture?
  • From: Jackson Pfeffer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: How to move gcc to compile to my own architecture?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• How to move gcc to compile to my own architecture?
  • From: Chengyin Yao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: attempt to compile gcc failed
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: attempt to compile gcc failed
  • From: Jerome Yanga via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: attempt to compile gcc failed
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• attempt to compile gcc failed
  • From: Jerome Yanga via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference when building GCC-4.8.1 MinGW-W64
  • From: LIU Hao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference when building GCC-4.8.1 MinGW-W64
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: sumbit localization updates?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• sumbit localization updates?
  • From: two--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference when building GCC-4.8.1 MinGW-W64
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: undefined reference when building GCC-4.8.1 MinGW-W64
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• undefined reference when building GCC-4.8.1 MinGW-W64
  • From: "i.nixman--- via Gcc-help" <gcc-help@xxxxxxxxxxx>
• About adding my Header file for C language
  • From: Toaha 111 via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCJ segfault
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• errors building gcc 12.2.0 on musl-libc
  • From: Mike Glover via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning: conditional outside an IT block for Thumb.
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning: conditional outside an IT block for Thumb.
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning: conditional outside an IT block for Thumb.
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warning: conditional outside an IT block for Thumb.
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Warning: conditional outside an IT block for Thumb.
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: one of those annoying little things
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: one of those annoying little things
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: one of those annoying little things
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: one of those annoying little things
  • From: "Matthew R. Wilson" <mwilson@xxxxxxxxxxxxxx>
• Re: one of those annoying little things
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: one of those annoying little things
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: one of those annoying little things
  • From: "Matthew R. Wilson" <mwilson@xxxxxxxxxxxxxx>
• Re: one of those annoying little things
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• one of those annoying little things
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Problem with evaluation order in assignment expression after c++17
  • From: cyb_yorkin--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Andrea Bocci <andrea.bocci@xxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Andrea Bocci <andrea.bocci@xxxxxxx>
• Re: Warn about conversion from floating point to integers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Reid Wahl via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Reid Wahl via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Reid Wahl via Gcc-help <gcc-help@xxxxxxxxxxx>
• -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
  • From: Reid Wahl via Gcc-help <gcc-help@xxxxxxxxxxx>
• Warn about conversion from floating point to integers
  • From: Andrea Bocci <andrea.bocci@xxxxxxx>
• riscv64: -march=rv64gcv1p0 vs riscv_vector.h
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>
  • From: Mathieu Malaterre via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: determining impact of vulnerability CVE-2022-27943 in libiberty/rust-demangle.c
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• determining impact of vulnerability CVE-2022-27943 in libiberty/rust-demangle.c
  • From: fus@xxxxxxxxxxxxxx
• riscv64: -march=rv64gcv1p0 vs <riscv_vector.h>
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: hppa2.0w-hp-hpux11.11 bootstrap comparison failure gcc 11.3.0 and 10.4.0
  • From: Jeff Law via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: False warnings on arm-gcc?
  • From: Martin Sebor via Gcc-help <gcc-help@xxxxxxxxxxx>
• False warnings on arm-gcc?
  • From: Amol via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: GCC 12.1 and C++23 <stacktrace>
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC 12.1 and C++23 <stacktrace>
  • From: Helmut Zeisel via Gcc-help <gcc-help@xxxxxxxxxxx>
• force the (gfortran) compiler to not optimize out a variable
  • From: David Brown <david@xxxxxxxxxxxxxxxxxxx>
• RE: GCC Version upgrade in AIX server
  • From: "Kondreddy, Vinay Kumar via Gcc-help" <gcc-help@xxxxxxxxxxx>
• [[__gnu__::__trivially_relocatable__]] and __is_trivially_relocatable?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Empty element in CPATH variable
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Empty element in CPATH variable
  • From: aiishymanel--- via Gcc-help <gcc-help@xxxxxxxxxxx>
• Can this function be auto vectorized with NEON?
  • From: Edgar Mobile via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: hppa2.0w-hp-hpux11.11 bootstrap comparison failure gcc 11.3.0 and 10.4.0
  • From: "Matthew R. Wilson" <mwilson@xxxxxxxxxxxxxx>
• Re: Try to understand output of -fdump-ipa-inline
  • From: Navid Rahimi via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Try to understand output of -fdump-ipa-inline
  • From: Edgar Mobile via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Try to understand output of -fdump-ipa-inline
  • From: Navid Rahimi via Gcc-help <gcc-help@xxxxxxxxxxx>
• hppa2.0w-hp-hpux11.11 bootstrap comparison failure gcc 11.3.0 and 10.4.0
  • From: Dennis Grevenstein via Gcc-help <gcc-help@xxxxxxxxxxx>
• Try to understand output of -fdump-ipa-inline
  • From: Edgar Mobile via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: archeology : Compiling gcc-3.4.6 on sparc sun4m Solaris 2.5.1
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Daniel Santos via Gcc-help <gcc-help@xxxxxxxxxxx>
• archeology : Compiling gcc-3.4.6 on sparc sun4m Solaris 2.5.1
  • From: Dennis Clarke via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Daniel Santos via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Daniel Santos via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Daniel Santos via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Compiling gcc-3.4.6 on sparc Solaris 9
  • From: Daniel Santos via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Followup on "Configure error question"
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Followup on "Configure error question"
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Followup on "Configure error question"
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• error: ‘__Y’ is used uninitialized for immintrin.h when compiled with -O3 -Wall -Winit-self -Werror
  • From: "Joshi, Tejas Sanjay via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Configure error question
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building x86 cross compiler on Mac M1
  • From: "Admin at thaibinh.me" <admin@xxxxxxxxxxx>
• Re: @end
  • From: Lic. Kai Olaf K e t e l h u t sīc via Gcc-help <gcc-help@xxxxxxxxxxx>
• @end
  • From: Lic. Kai Olaf K e t e l h u t sīc via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: error -mno-unaligned-access unrecognized command-line option
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: error -mno-unaligned-access unrecognized command-line option
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• Mail delivery failed: returning message to sender
  • From: Mail Delivery System <Mailer-Daemon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: error -mno-unaligned-access unrecognized command-line option
  • From: Xi Ruoyao via Gcc-help <gcc-help@xxxxxxxxxxx>
• error -mno-unaligned-access unrecognized command-line option
  • From: enric - serverand <enric@xxxxxxxxxxxxx>
• Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• build failure of old GCC: .../libstdc++.so.6: version `GLIBCXX_3.4.30' not found
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: GCC C compiler
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• GCC C compiler
  • From: John Houle via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Treat GCC cross compiler as a native compiler?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Treat GCC cross compiler as a native compiler?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Treat GCC cross compiler as a native compiler?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Treat GCC cross compiler as a native compiler?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Treat GCC cross compiler as a native compiler?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Treat GCC cross compiler as a native compiler?
  • From: Richard Sandiford via Gcc-help <gcc-help@xxxxxxxxxxx>
• Treat GCC cross compiler as a native compiler?
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Adonis Ling via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Adonis Ling via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Adonis Ling via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Why does different types of array subscript used to iterate affect auto vectorization
  • From: Alexander Monakov via Gcc-help <gcc-help@xxxxxxxxxxx>
• Query : On libasan Versions
  • From: "Sangamesh . \(MS/ECF1-XC\) via Gcc-help" <gcc-help@xxxxxxxxxxx>
• Re: no gcc.exe for windows 11
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why does different types of array subscript used to iterate affect auto vectorization
  • From: Adonis Ling via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: More configure fun...
  • From: Tamar Christina via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: no gcc.exe for windows 11
  • From: unlvsur unlvsur via Gcc-help <gcc-help@xxxxxxxxxxx>
• no gcc.exe for windows 11
  • From: Daniel Anderson via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc update help please
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Why functions like memcpy, memmove in libgcc are not weak linkage?
  • From: sotrdg sotrdg via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: More configure fun...
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: More configure fun...
  • From: Tamar Christina via Gcc-help <gcc-help@xxxxxxxxxxx>
• More configure fun...
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: gcc update help please
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• gcc update help please
  • From: "jm@xxxxxxxxxxxxxxxxxxx" <jm@xxxxxxxxxxxxxxxxxxx>
• Re: Passing member variable as parameter to the base class constructor: warning expected but not seen
  • From: Ronny Meeus via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Passing member variable as parameter to the base class constructor: warning expected but not seen
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Passing member variable as parameter to the base class constructor: warning expected but not seen
  • From: Ronny Meeus via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fw: Makefile format
  • From: Ming Cheng via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: A ARM target question
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Fw: Makefile format
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Fw: Makefile format
  • From: Ming Cheng via Gcc-help <gcc-help@xxxxxxxxxxx>
• Building gcc with AMD offloading fails building libssp
  • From: Andrew Ho via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Re: Some error when installing the gcc9.4.0，when "make".
  • From: 涂家礼 <jl.tu@xxxxxxxxxx>
• Re: Makefile format
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Makefile format
  • From: Ming Cheng via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: A ARM target question
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Segfault in libjava/prims.cc while compiling gcj
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Christophe Lyon via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: A ARM target question
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: __builtin_clzl code pattern
  • From: Gabriel Ravier via Gcc-help <gcc-help@xxxxxxxxxxx>
• __builtin_clzl code pattern
  • From: Florian Weimer via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Some error when installing the gcc9.4.0，when "make".
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Re[2]: Errors : '__INTPTR_TYPE__' undeclared while building GCC 12.1.0 for symbian
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: A ARM target question
  • From: Richard Earnshaw via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Re: Some error when installing the gcc9.4.0，when "make".
  • From: 涂家礼 <jl.tu@xxxxxxxxxx>
• Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Christophe Lyon via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>
• Anybody ever got an ARM Thumb-2 cross compiler to work?
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building Linux x86_64 to AIX PowerPC cross-compiler
  • From: Brian Groose <brian@xxxxxxxxxx>
• Re[2]: Errors : '__INTPTR_TYPE__' undeclared while building GCC 12.1.0 for symbian
  • From: Fiodar <fedor_qd@xxxxxxx>
• Re: A ARM target question
  • From: Stefan Ring via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building Linux x86_64 to AIX PowerPC cross-compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Segfault in libjava/prims.cc while compiling gcj
  • From: Zopolis0 via Gcc-help <gcc-help@xxxxxxxxxxx>
• Re: Building Linux x86_64 to AIX PowerPC cross-compiler
  • From: fedor_qd@xxxxxxx
• Re: A ARM target question
  • From: fedor_qd@xxxxxxx
• Building Linux x86_64 to AIX PowerPC cross-compiler
  • From: Paul Lucas via Gcc-help <gcc-help@xxxxxxxxxxx>
• A ARM target question
  • From: Gary Oblock via Gcc-help <gcc-help@xxxxxxxxxxx>
• -flto causes `undefined reference` for gcc builtins
  • From: Tobias Schramm via Gcc-help <gcc-help@xxxxxxxxxxx>
• RE: Errors creating executable for python script using cython and gcc
  • From: <jschwar@xxxxxxxxxxxxx>
• Errors creating executable for python script using cython and gcc
  • From: <jschwar@xxxxxxxxxxxxx>
• Warnings in GCC 12.1.0 builds
  • From: Fiodar Stryzhniou <fedor_qd@xxxxxxx>
• Re: Errors : '__INTPTR_TYPE__' undeclared while building GCC 12.1.0 for symbian
  • From: Fiodar Stryzhniou <fedor_qd@xxxxxxx>
• Re: Out of memory while building GCC 12.1.0
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Out of memory while building GCC 12.1.0
  • From: Fiodar Stryzhniou <fedor_qd@xxxxxxx>
• Re: Out of memory while building GCC 12.1.0
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Out of memory while building GCC 12.1.0
  • From: Fiodar Stryzhniou <fedor_qd@xxxxxxx>
• Errors : '__INTPTR_TYPE__' undeclared while building GCC 12.1.0 for symbian
  • From: Fiodar Stryzhniou <fedor_qd@xxxxxxx>
• Re: Out of memory while building GCC 12.1.0
  • From: Jonathan Wakely via Gcc-help <gcc-help@xxxxxxxxxxx>