GCC Help

• Thread Index

• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Reserve space in stack
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Reserve space in stack
  • From: "sztfg@xxxxxxxxx" <sztfg@xxxxxxxxx>
• Re: -fstack-protector and STL string
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Reserve space in stack
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Reserve space in stack
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Reserve space in stack
  • From: sztfg@xxxxxxxxx
• Issue with templates and asm register constraints
  • From: "Alex Kodat" <alexkodat@xxxxxxxxx>
• Re: use of qcmplx qsqrt qimag etc.
  • From: penava_b <bastien.penavayre@xxxxxxxxxx>
• use of qcmplx qsqrt qimag etc.
  • From: Erin Farbar <erin.farbar@xxxxxxxxx>
• Re: Caching of math functions
  • From: Matthias Pfaller <leo@xxxxxxxx>
• libc kann weg
  • From: aw8962348@xxxxxx
• Re: Caching of math functions
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Caching of math functions
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Caching of math functions
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: how to access the online manuals?
  • From: "Carol LePage" <clepage@xxxxxxxxxxxxxx>
• unnoticed invalid dereference when using address sanitizer
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: how to access the online manuals?
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• Re: how to access the online manuals?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• how to access the online manuals?
  • From: "Carol LePage" <clepage@xxxxxxxxxxxxxx>
• Creating one large precompiled header from multitude of other (possibly also precompiled) headers.
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• Re: AW: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• AW: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Printing float scenarios (32 vs 64 bit parameters)
  • From: "Brian R. Hall" <hall@xxxxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• Re: gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• gcc-5.3.0 libstdc++-v3: configure: error: No support for this host/target combination for arm-none-eabi
  • From: "onkel.jack@xxxxxxxxxxx" <onkel.jack@xxxxxxxxxxx>
• Re: include files
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: (Building GCC) mtune=native and internal compiler error at emit-rtl.c:1027
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• (Building GCC) mtune=native and internal compiler error at emit-rtl.c:1027
  • From: Seth Junot <xsetech@xxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Didier Kryn <kryn@xxxxxxxx>
• Re: m68k toolchain
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• Re: gold --incremental not producing DWARF such that nm can handle it, internal error
  • From: Cary Coutant <ccoutant@xxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: include files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: include files
  • From: Bob Gardenier <bob.gardenier@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: gold --incremental not producing DWARF such that nm can handle it, internal error
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Why does -Wabi-tag complain when -std=c++03?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Why does -Wabi-tag complain when -std=c++03?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• -fstack-protector and STL string
  • From: "Martin Richtarsky" <s@xxxxxxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• How to provide coexisting std::string's (with and without abi:cxx11) in GCC 5.1 and above?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC 5.1 and UndefinedBehaviorSanitizer gained a few new sanitization options
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Where are the GCC 5.1 docs?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Where are the GCC 5.1 docs?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• GCC 5.1 and UndefinedBehaviorSanitizer gained a few new sanitization options
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• gold --incremental not producing DWARF such that nm can handle it, internal error
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• is -fPIC safe for executable programs, or must -fPIE be used?
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• Re: cross g++ sysroot and headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: m68k toolchain
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• cross g++ sysroot and headers
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: bug or just an invalid commanline ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bug or just an invalid commanline ?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Find offset of block instruction in function
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Find offset of block instruction in function
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: bug or just an invalid commanline ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• bug or just an invalid commanline ?
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• m68k toolchain
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: LTO Error: operand type mismatch for `div'
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• LTO Error: operand type mismatch for `div'
  • From: Hannes Domani <ssbssa@xxxxxxxx>
• Re: What are files named .fuse_hidden... ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• What are files named .fuse_hidden... ?
  • From: Dave Wagler <rebelxt@xxxxxxx>
• Re: type0identifiers as identifier
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: type0identifiers as identifier
  • From: vijay nag <vijunag@xxxxxxxxx>
• Re: Why the "--with-sysroot" option is not shown when I use the "--help" option?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why the "--with-sysroot" option is not shown when I use the "--help" option?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: addr2line ends up off by 1 line numbers when -O0 is used
  • From: Ángel González <keisial@xxxxxxxxx>
• trying to characterize the circumstances under which backtrace() works reliably
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• Re: addr2line ends up off by 1 line numbers when -O0 is used
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• Re: addr2line ends up off by 1 line numbers when -O0 is used
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• trouble building gcc-5.3.0
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• addr2line ends up off by 1 line numbers when -O0 is used
  • From: Britton Kerin <britton.kerin@xxxxxxxxx>
• Re: Bus Fault
  • From: spflanze <sepflanze@xxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Error: selected processor does not support `bx lr' in ARM mode
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Why the "--with-sysroot" option is not shown when I use the "--help" option?
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Bus Fault
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Error: selected processor does not support `bx lr' in ARM mode
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Bus Fault
  • From: spflanze <sepflanze@xxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Help in tracking down unusual apparent 5.2.0 LTO issue
  • From: Matt Godbolt <matt@xxxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Error: selected processor does not support `bx lr' in ARM mode
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• Error: selected processor does not support `bx lr' in ARM mode
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Jeff Law <law@xxxxxxxxxx>
• 6.0-20160313 snapshot - bootstrap-lto without using --disable-werror at configure
  • From: David Kredba <nheghathivhistha@xxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: RFC: Very long alternative lists for RTL patterns like move
  • From: Jeff Law <law@xxxxxxxxxx>
• RFC: Very long alternative lists for RTL patterns like move
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: What does "profil" means in C++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Building a cross-compiler for a Raspberry Pi
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <chengang@xxxxxxxxxxxxxxxx>
• Building a cross-compiler for a Raspberry Pi
  • From: YuGiOhJCJ Mailing-List <yugiohjcj-mailinglist@xxxxxxxxxxx>
• Re: Compiling Samba with LTO
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Your page doesn't seem to work properly.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compiling Samba with LTO
  • From: Ralph Boehme <slow@xxxxxxxxx>
• Eclipse GCov issues
  • From: Oscar Pauly <opaulyc@xxxxxxxxx>
• Re: Your page doesn't seem to work properly.
  • From: Mason <slash.tmp@xxxxxxx>
• augmenting the standard include path
  • From: scs@xxxxxxxxxx (Steve Summit)
• Re: fp problem building arm cross-compiler
  • From: scs@xxxxxxxxxx (Steve Summit)
• Re: What does "profil" means in C++
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: What does "profil" means in C++
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: What does "profil" means in C++
  • From: Andrew Haley <aph@xxxxxxxxxx>
• What does "profil" means in C++
  • From: Patrick Begou <Patrick.Begou@xxxxxxxxxxxxxxxxxxxx>
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Failing to build native gcc-5 on powerpc-linux-gnuspe
  • From: John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx>
• Re: fp problem building arm cross-compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• fp problem building arm cross-compiler
  • From: scs@xxxxxxxxxx (Steve Summit)
• Fw: Testing crosscompiler
  • From: fedor_qd <fedor_qd@xxxxxxx>
• Re: building gcc 5.3 with gmp,mpfr,mpc,isl in tree results in error relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 5.3 with gmp,mpfr,mpc,isl in tree results in error relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• building gcc 5.3 with gmp,mpfr,mpc,isl in tree results in error relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <chengang@xxxxxxxxxxxxxxxx>
• Re: where in gcc sources is foobar.o written?
  • From: Mark Galeck <mark_galeck@xxxxxxxxxxx>
• Re: where in gcc sources is foobar.o written?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• where in gcc sources is foobar.o written?
  • From: Mark Galeck <mark_galeck@xxxxxxxxxxx>
• 1 of 5,609 gcc trunk: OpenACC offload to nvptx
  • From: Salvatore Filippone <filippone.salvatore@xxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Use AVX/AVX512 selectively
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• [non-]Issue with CRTP template code example in GCC 5.2.1
  • From: Diptorup Deb <diptorup@xxxxxxxxxx>
• Re: reload.c and doubly-indirect memory references
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: building old gcc3 for i386-linux on recent x86-linux?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxx>
• LTO vs zero length bit fields
  • From: Jay Foad <jay.foad@xxxxxxxxx>
• Re: reload.c and doubly-indirect memory references
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: reload.c and doubly-indirect memory references
  • From: Pip Cet <pipcet@xxxxxxxxx>
• GCC GSOC 2016
  • From: Ayush Goel <ayushgoel1610@xxxxxxxxx>
• Use AVX/AVX512 selectively
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: gcc base and peak options for spec-2006
  • From: Alex Markin <alexanius@xxxxxxxxx>
• Re: Your page doesn't seem to work properly.
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• Your page doesn't seem to work properly.
  • From: Amber Marshall <amber.marshall@xxxxxxxxxxxxx>
• Re: reload.c and doubly-indirect memory references
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc base and peak options for spec-2006
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: gcc base and peak options for spec-2006
  • From: Tim Prince <n8tm@xxxxxxx>
• gcc base and peak options for spec-2006
  • From: Alex Markin <alexanius@xxxxxxxxx>
• Re: reload.c and doubly-indirect memory references
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: how to measure total time spent in waiting for mutex without cswitch ?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: how to measure total time spent in waiting for mutex without cswitch ?
  • From: Navin Parakkal <navinp1912@xxxxxxxxx>
• reload.c and doubly-indirect memory references
  • From: Pip Cet <pipcet@xxxxxxxxx>
• Seg fault when app & shared lib built with -static-libstdc++
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• how to measure total time spent in waiting for mutex without cswitch ?
  • From: Navin Parakkal <navinp1912@xxxxxxxxx>
• Re: Help with intel mic target building
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Warning for converting (possibly) negative float/double to unsigned int
  • From: Bradley Lucier <lucier@xxxxxxxxxxxxxxx>
• Re: Help with intel mic target building
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Inline assembly without inputs considered const/pure?
  • From: Matthias Pfaller <leo@xxxxxxxx>
• Re: building old gcc3 for i386-linux on recent x86-linux?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• gcc-5.3.0 tests fail
  • From: Michael Meyer <spyqqqdia@xxxxxxxxx>
• gcc-5.3.0 tests fail
  • From: Michael Meyer <spyqqqdia@xxxxxxxxx>
• Re: Inline static data causes a section type conflict
  • From: Benedek Thaler <thalerbenedek@xxxxxxxxx>
• Re: Inline static data causes a section type conflict
  • From: Bernd Edlinger <bernd.edlinger@xxxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: LMH <lmh_users-groups@xxxxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: LMH <lmh_users-groups@xxxxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: Preprocess files with gcc/gfortran vs. cpp
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Fwd: Preprocess files with gcc/gfortran vs. cpp
  • From: Nick Papior <nickpapior@xxxxxxxxx>
• Re: building old gcc3 for i386-linux on recent x86-linux?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxx>
• Re: building old gcc3 for i386-linux on recent x86-linux?
  • From: LMH <lmh_users-groups@xxxxxxxxxxx>
• building old gcc3 for i386-linux on recent x86-linux?
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxx>
• optimization options controlled by user
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: Inline static data causes a section type conflict
  • From: Benedek Thaler <thalerbenedek@xxxxxxxxx>
• recompiling between binary-compatible GCC versions
  • From: David Shrader <dshrader@xxxxxxxx>
• Re: Inline static data causes a section type conflict
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Inline static data causes a section type conflict
  • From: Benedek Thaler <thalerbenedek@xxxxxxxxx>
• setting loop buffer size in the gcc
  • From: Virendra Kumar Pathak <kumarvir.pathak@xxxxxxxxx>
• Re: Does dereferencing a volatile pointer produce a volatile element?
  • From: Didier Kryn <kryn@xxxxxxxx>
• Re: Does dereferencing a volatile pointer produce a volatile element?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: difficulty building gcc 4.6.3 on MacOS
  • From: scs+gcc@xxxxxxxxxx (Steve Summit)
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Does dereferencing a volatile pointer produce a volatile element?
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Does dereferencing a volatile pointer produce a volatile element?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: GCC 5.3.0 in Rhel7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++: Difference between calling memcpy and __builtin_memcpy
  • From: Martin Sebor <msebor@xxxxxxxxx>
• difficulty building gcc 4.6.3 on MacOS
  • From: scs@xxxxxxxxxx (Steve Summit)
• Re: fortran macos binaries
  • From: FX <fxcoudert@xxxxxxxxx>
• Re: fortran macos binaries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: s390x (64 bit) macro expansion WCOREDUMP
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• fortran macos binaries
  • From: Debra Weisenstein <dkweis@xxxxxxxxx>
• C++: Difference between calling memcpy and __builtin_memcpy
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Implement link-time optimization safe explicit_bzero()?
  • From: Manuel López-Ibáñez <manuel.lopez-ibanez@xxxxxxxxxxxxxxxx>
• Re: s390x (64 bit) macro expansion WCOREDUMP
  • From: Richard Plangger <planrichi@xxxxxxxxx>
• Implement link-time optimization safe explicit_bzero()?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: s390x (64 bit) macro expansion WCOREDUMP
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• s390x (64 bit) macro expansion WCOREDUMP
  • From: Richard Plangger <planrichi@xxxxxxxxx>
• Re: GCC 5.3.0 in Rhel7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.3.0 in Rhel7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Installing gcc to nonstandard location
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.3.0 in Rhel7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc with--disable-static --enable-shared
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Fwd: Installing gcc to nonstandard location
  • From: Tom Close <tom.close@xxxxxxxxxx>
• Re: Werror
  • From: manojmaybe <manojmaybe000@xxxxxxxxx>
• Re: Surprising "parse error in template argument list"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to get access/visibility of functions, variables, typedefs and templates?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: Werror
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Werror
  • From: manojmaybe <manojmaybe000@xxxxxxxxx>
• Re: Werror
  • From: Mason <slash.tmp@xxxxxxx>
• Re: building gcc with--disable-static --enable-shared
  • From: Gabriel VLASIU <gabriel@xxxxxxxxxx>
• Werror
  • From: manojmaybe <manojmaybe000@xxxxxxxxx>
• Re: Questions on Microsoft C Exceptions, Gcc, and Gdb
  • From: Ángel González <keisial@xxxxxxxxx>
• building gcc with--disable-static --enable-shared
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Questions on Microsoft C Exceptions, Gcc, and Gdb
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Modify array type into pointer type for VAR_DECL
  • From: Cristina Georgiana Opriceana <cristina.opriceana@xxxxxxxxx>
• Re: g++v5.2.1 problems with LTO and funtional behavior
  • From: Mason <slash.tmp@xxxxxxx>
• g++v5.2.1 problems with LTO and funtional behavior
  • From: "Rigoberto L. Salgado Reyes" <rlsalgado@xxxxxx>
• Re: Insert call to malloc in gimple
  • From: Cristina Georgiana Opriceana <cristina.opriceana@xxxxxxxxx>
• libsanitizer by cross toolchain
  • From: Yakov Yazlovitsky <yakov@xxxxxxx>
• Re: How to add custom library paths while compiling nginx from source code
  • From: Ángel González <keisial@xxxxxxxxx>
• How to add custom library paths while compiling nginx from source code
  • From: Sebastian Tarach <sebastian@xxxxxxxxxx>
• How to get access/visibility of functions, variables, typedefs and templates?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: LTO setup
  • From: Fabio Coatti <fabio.coatti@xxxxxxxxx>
• Re: LTO setup
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: LTO setup
  • From: Fabio Coatti <fabio.coatti@xxxxxxxxx>
• Re: Possible performance issue with gfortran? denormalized numbers
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Possible performance issue with gfortran? denormalized numbers
  • From: Toon Moene <toon@xxxxxxxxx>
• Re: Possible performance issue with gfortran? denormalized numbers
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Possible performance issue with gfortran? denormalized numbers
  • From: Toon Moene <toon@xxxxxxxxx>
• Re: LTO setup
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: LTO setup
  • From: Fabio Coatti <fabio.coatti@xxxxxxxxx>
• Re: LTO setup
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: g++-arm-none-eabi system includes and implicit extern "C"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• LTO setup
  • From: Fabio Coatti <fabio.coatti@xxxxxxxxx>
• g++-arm-none-eabi system includes and implicit extern "C"
  • From: Josh Bialkowski <josh.bialkowski@xxxxxxxxx>
• Fwd: Help about how to bootstrap gcc with local version glibc other than system one
  • From: "Bin.Cheng" <amker.cheng@xxxxxxxxx>
• Possible performance issue with gfortran? denormalized numbers
  • From: Jose Miguel Reynolds Barredo <jmrb2002@xxxxxxxxx>
• Inline static data causes a section type conflict
  • From: Benedek Thaler <thalerbenedek@xxxxxxxxx>
• Re: [AARCH64] question about RELA relocations
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Exceptions declaration and static analysis
  • From: dvd <dvd+nntp@xxxxxx>
• Re: Exceptions declaration and static analysis
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Exceptions declaration and static analysis
  • From: dvd <dvd+nntp@xxxxxx>
• GCC bug?
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: cross-compiling LM32 internal error while linking
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxxxxxxx>
• cross-compiling LM32 internal error while linking
  • From: Federico Vaga <federico.vaga@xxxxxxxxx>
• RE: GCC 4.9 #32 special value?
  • From: Jens Vankeirsbilck <jens.vankeirsbilck@xxxxxxxxxxx>
• Re: How to parse a record bitmask field in plugin?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: Loops in GCC preprocessor needed
  • From: penava_b <bastien.penavayre@xxxxxxxxxx>
• How to parse a record bitmask field in plugin?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: How to get function declaration source file/line from definition?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: Loops in GCC preprocessor needed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Loops in GCC preprocessor needed
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Loops in GCC preprocessor needed
  • From: Nulik Nol <nuliknol@xxxxxxxxx>
• Re: GCC 4.9 #32 special value?
  • From: Jeff Law <law@xxxxxxxxxx>
• GCC 4.9 #32 special value?
  • From: Jens Vankeirsbilck <jens.vankeirsbilck@xxxxxxxxxxx>
• Re: sorry, unimplemented: Graphite loop optimizations cannot be used
  • From: dE <de.techno@xxxxxxxxx>
• Re: GCC vector element access pointers in C++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: GCC vector element access pointers in C++
  • From: Marius Miknis <marius.miknis@xxxxxxxxxxxxxxxx>
• Re: GCC vector element access pointers in C++
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCC vector element access pointers in C++
  • From: Marius Miknis <marius.miknis@xxxxxxxxxxxxxxxx>
• Re: sorry, unimplemented: Graphite loop optimizations cannot be used
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• sorry, unimplemented: Graphite loop optimizations cannot be used
  • From: dE <de.techno@xxxxxxxxx>
• Re: Surprising "parse error in template argument list"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Surprising "parse error in template argument list"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: dereferencing type-punned pointer will break strict-aliasing rules
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Surprising "parse error in template argument list"
  • From: John Marshall <jm18@xxxxxxxxxxxx>
• Re: How to get function declaration source file/line from definition?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: How to get function declaration source file/line from definition?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: How to get function declaration source file/line from definition?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• How to get function declaration source file/line from definition?
  • From: crasypantz <ihavecrazypants@xxxxxxxxxxx>
• Re: Trying to download GCC v5.3
  • From: Gerald Pfeifer <gerald@xxxxxxxxxxx>
• [plugin] Issue with life cycle of attributes argument when passed to new function calls
  • From: penava_b <bastien.penavayre@xxxxxxxxxx>
• dereferencing type-punned pointer will break strict-aliasing rules
  • From: Marcel Behlau <marcel.behlau@xxxxxxxx>
• Re: error while building trunk (only for c++) on ubuntu 14.04 LTS
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• error while building trunk (only for c++) on ubuntu 14.04 LTS
  • From: acc2 <meinaccountnr2@xxxxxx>
• Exceptions on AIX causing IOT/Abort trap
  • From: Brian Groose <brian@xxxxxxxxxx>
• Re: semi-newbie | static compilation/linking gfortran
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• semi-newbie | static compilation/linking gfortran
  • From: Evan Cooch <evan.cooch@xxxxxxxxx>
• Conditional compilation when using -fsanitize=thread
  • From: Alex Bennée <alex.bennee@xxxxxxxxxx>
• Re: Insert call to malloc in gimple
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Insert call to malloc in gimple
  • From: Cristina Georgiana Opriceana <cristina.opriceana@xxxxxxxxx>
• Re: Documentation about C++ Concepts
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Esteban Hernández <eshernan@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Esteban Hernández <eshernan@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Esteban Hernández <eshernan@xxxxxxxxx>
• Re: gcc porting: how to generate floating point multiply-add instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• gcc porting: how to generate floating point multiply-add instruction?
  • From: David Kang <dkang@xxxxxxx>
• Help with ICE using polymorphic lambda
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: how to work around "plugin needed to handle lto object"
  • From: Niklas Gürtler <profclonk@xxxxxxxxx>
• trunk bootstrap: undefined reference to `std::basic_istream<char
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: New type trait primitives in GCC 5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: how to work around "plugin needed to handle lto object"
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• New type trait primitives in GCC 5
  • From: Nathan Ridge <zeratul976@xxxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Johann Klammer <klammerj@xxxxxx>
• Re: [AARCH64] question about RELA relocations
  • From: Jiong Wang <jiong.wang@xxxxxxxxxxxx>
• Re: GCC 5.2 Pass does not get called
  • From: Cristina Georgiana Opriceana <cristina.opriceana@xxxxxxxxx>
• Re: [AARCH64] question about RELA relocations
  • From: Andrew Pinski <pinskia@xxxxxxxxx>
• [AARCH64] question about RELA relocations
  • From: weixiangyu <weixiangyu@xxxxxxxxxx>
• Re: Building gcc 5.2.1 on AIX 7.2
  • From: Gabriel VLASIU <gabriel@xxxxxxxxxx>
• Re: Building gcc 5.2.1 on AIX 7.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Building gcc 5.2.1 on AIX 7.2
  • From: Gabriel VLASIU <gabriel@xxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Building gcc 5.2.1 on AIX 7.2
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Building gcc 5.2.1 on AIX 7.2
  • From: Gabriel VLASIU <gabriel@xxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Paul Smith <psmith@xxxxxxx>
• GCC 5.3.0: ASAN gives "unknown-crash" error
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• gfortran on OS X El Capitan
  • From: Taha Dawoodbhoy <tahad17@xxxxxxxxxx>
• how to work around "plugin needed to handle lto object"
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: ABI for C and C++ on x86
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to determine when a C++11 move is synthesized?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to determine when a C++11 move is synthesized?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: ABI for C and C++ on x86
  • From: Jim Blandy <jimb@xxxxxxxxxxxx>
• Re: How to determine when a C++11 move is synthesized?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to determine when a C++11 move is synthesized?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to determine when a C++11 move is synthesized?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: ABI for C and C++ on x86
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• ABI for C and C++ on x86
  • From: Jim Blandy <jimb@xxxxxxxxxxxx>
• How to determine when a C++11 move is synthesized?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to compile gcc entirely with an external compiler?
  • From: Yuri <yuri@xxxxxxxxx>
• Re: How to compile gcc entirely with an external compiler?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 5.2 Pass does not get called
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Fwd: GCC 5.2 Pass does not get called
  • From: Cristina Georgiana Opriceana <cristina.opriceana@xxxxxxxxx>
• gcov & va_arg
  • From: Jerome Arbez-Gindre <jeromearbezgindre@xxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Bernd Edlinger <bernd.edlinger@xxxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Hadrien Grasland <hadrien.grasland@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Hi ! help please
  • From: user user <uid0022@xxxxxxxxx>
• Re: Hi ! help please
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Hi ! help please
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Hi ! help please
  • From: user user <uid0022@xxxxxxxxx>
• Re: Hi ! help please
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: What is 'mov (%r11,%rax,1),%dl'?
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• What is 'mov (%r11,%rax,1),%dl'?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Hi ! help please
  • From: Vincent Diepeveen <diep@xxxxxxxxx>
• Re: Hi ! help please
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Hi ! help please
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Hi ! help please
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: alloca and parameter passing
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Hi ! help please
  • From: Vincent Diepeveen <diep@xxxxxxxxx>
• Hi ! help please
  • From: user user <uid0022@xxxxxxxxx>
• Re: alloca and parameter passing
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: how to compile a lower gcc/glibc version compatible binary?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: alloca and parameter passing
  • From: Jeff Law <law@xxxxxxxxxx>
• alloca and parameter passing
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: how to compile a lower gcc/glibc version compatible binary?
  • From: Mason <slash.tmp@xxxxxxx>
• Re: how to compile a lower gcc/glibc version compatible binary?
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• how to compile a lower gcc/glibc version compatible binary?
  • From: Derek Ch <rcheng881@xxxxxxxxxxxxxxxxxxxx>
• warning: style of line directive is a GCC extension [enabled by default]
  • From: Steven Stewart-Gallus <sstewartgallus00@xxxxxxxxxxxxxxx>
• Re: __RDSEED__ defined, but no _rdseed* prototypes?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• __RDSEED__ defined, but no _rdseed* prototypes?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• How to compile gcc entirely with an external compiler?
  • From: Yuri <yuri@xxxxxxxxx>
• libgomp plugin: do not force JIT target SM version (was: GCC OpenAcc executables problems)
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: SIGSEGV in '_Unwind_Backtrace'
  • From: Soumya Koduri <skoduri@xxxxxxxxxx>
• Re: SIGSEGV in '_Unwind_Backtrace'
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: SIGSEGV in '_Unwind_Backtrace'
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• SIGSEGV in '_Unwind_Backtrace'
  • From: Soumya Koduri <skoduri@xxxxxxxxxx>
• Re: Documentation about C++ Concepts
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Documentation about C++ Concepts
  • From: Akim Demaille <akim.demaille@xxxxxxxxx>
• Re: exclusion macros ifdef, else and endif
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Documentation about C++ Concepts
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Documentation about C++ Concepts
  • From: Akim Demaille <akim.demaille@xxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• Re: Help with SH2E -O2 instruction ordering with volatile
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Help with SH2E -O2 instruction ordering with volatile
  • From: Alex Brown <alex.g.brown@xxxxxxxxx>
• exclusion macros ifdef, else and endif
  • From: Joël Krähemann <jkraehemann@xxxxxxxxx>
• Re: GCC 5.3: UBSAN versus -static-libstdc++
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCC 5.3: UBSAN versus -static-libstdc++
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: Build gcc-4.8.2 error -- gcc-4.8.1/x86_64-unknown-linux-gnu/libgomp
  • From: sam8dec <sam8dec@xxxxxxxxx>
• Re: arm gcc: info about branches on svn and git
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: arm gcc: info about branches on svn and git
  • From: Massimiliano Cialdi <cialdi@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Esteban Hernández <eshernan@xxxxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Nathan Sidwell <nathan@xxxxxxx>
• Re: GCC OpenAcc executables problems
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• GCC OpenAcc executables problems
  • From: Esteban Hernández <eshernan@xxxxxxxxx>
• Seek help, if GCC can be installed on android tablet PC
  • From: aasimabdulrehman <aasimabdulrehman@xxxxxxxxx>
• Re: arm gcc: info about branches on svn and git
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: arm gcc: info about branches on svn and git
  • From: Massimiliano Cialdi <cialdi@xxxxxxxxx>
• Random C code generator
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: arm gcc: info about branches on svn and git
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• arm gcc: info about branches on svn and git
  • From: Massimiliano Cialdi <cialdi@xxxxxxxxx>
• Re: Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Inconsistent warning/error message by GCC while linking 32/64 bit binary/library
  • From: vijay nag <vijunag@xxxxxxxxx>
• Re: Inconsistent warning/error message by GCC while linking 32/64 bit binary/library
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Inconsistent warning/error message by GCC while linking 32/64 bit binary/library
  • From: vijay nag <vijunag@xxxxxxxxx>
• Re: C++11 packaged_task<> with reference arg
  • From: "M. Manfred" <mx2927@xxxxxxxxx>
• Re: C++11 packaged_task<> with reference arg
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• C++11 packaged_task<> with reference arg
  • From: "M. Manfred" <mx2927@xxxxxxxxx>
• Add extra RTX code
  • From: Jens Vankeirsbilck <jens.vankeirsbilck@xxxxxxxxxxx>
• Re: Fwd: Problem with Cross Compiler for V850
  • From: Jeff Law <law@xxxxxxxxxx>
• Fwd: Problem with Cross Compiler for V850
  • From: Hooman Habibi <hooman.habibi.g@xxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Bernd Edlinger <bernd.edlinger@xxxxxxxxxx>
• Re: Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Re: Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Foating point: tracking change in between gcc 4.4.7 and gcc 4.9.2
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• Re: gcc 6.0 and openmp 4.5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc 6.0 and openmp 4.5
  • From: Alin Marin Elena <alinm.elena@xxxxxxxxx>
• Re: gcc 6.0 and openmp 4.5
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc 6.0 and openmp 4.5
  • From: Alin Marin Elena <alinm.elena@xxxxxxxxx>
• Re: gcc 6.0 and openmp 4.5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc 6.0 and openmp 4.5
  • From: Alin Marin Elena <alinm.elena@xxxxxxxxx>
• How build gcc parts with different options?
  • From: fedor_qd@xxxxxxx
• Re: gcc.gnu.org web access problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Build gcc-4.8.2 error -- gcc-4.8.1/x86_64-unknown-linux-gnu/libgomp
  • From: GHui <ugiwgh@xxxxxxxxx>
• gcc.gnu.org web access problem
  • From: Phillip Wyman <pwyman@xxxxxxx>
• Re: Problem building 4.7.4 on AIX 5.2
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Problem building 4.7.4 on AIX 5.2
  • From: Albert Chin <gcc-help@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: invalid conversion from typeX** to const typeX**
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Build gcc-4.8.2 error -- gcc-4.8.1/x86_64-unknown-linux-gnu/libgomp
  • From: sam8dec <sam8dec@xxxxxxxxx>
• Re: Problems building 4.7.4, 4.8.5, 4.9.3, 5.2.0 on HP-UX 11.31/PA
  • From: Albert Chin <gcc-help@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Problems building 4.7.4, 4.8.5, 4.9.3, 5.2.0 on HP-UX 11.31/PA
  • From: Albert Chin <gcc-help@xxxxxxxxxxxxxxxxxxxxxxxxx>
• G++ denies to inline at -Os because "call is unlikely ...".
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Build error in glibc using GCC-4.9.2
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Build error in glibc-2.5 using GCC-4.9.2
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Fail Links
  • From: Ahmad Zaky <mubarok21@xxxxxxxxx>
• builtins and fwait
  • From: David Wohlferd <dw@xxxxxxxxxxxxxxxxxx>
• Re: Left shift of negative value
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Left shift of negative value
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Left shift of negative value
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Left shift of negative value
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Left shift of negative value
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Left shift of negative value
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Left shift of negative value
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Left shift of negative value
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Left shift of negative value
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Left shift of negative value
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: dwarf2 problem in gcc-4.9.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• dwarf2 problem in gcc-4.9.2
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Anthony Brandon <anthony.brandon@xxxxxxxxx>
• AW: default specs file
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• `ashlhi3' matches `ashlqi3' error
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Initialized variables in .bss
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• default specs file
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: Initialized variables in .bss
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Initialized variables in .bss
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Initialized variables in .bss
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Initialized variables in .bss
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Initialized variables in .bss
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: set SHORT_TYPE_SIZE to 8
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: ICE: SEGFAULT in mem rtx - GCC-4.5.1
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Re: set SHORT_TYPE_SIZE to 8
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: How to devirtualize one class?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Flags turned on by GCC standard optimizations
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: ICE: SEGFAULT in mem rtx - GCC-4.5.1
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Question about default optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: Question about default optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question about default optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: set SHORT_TYPE_SIZE to 8
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Question about default optimizations
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Question about default optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question about default optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: ICE: SEGFAULT in mem rtx - GCC-4.5.1
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Question about default optimizations
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Question about default optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: set SHORT_TYPE_SIZE to 8
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: set SHORT_TYPE_SIZE to 8
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Question about default optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• set SHORT_TYPE_SIZE to 8
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• reg: building gnat 4.6.4 using gcc-4.5.1
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• ICE: SEGFAULT in mem rtx - GCC-4.5.1
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• libiconv problem on OS X
  • From: Alexander Regueiro <alexreg@xxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Question about default optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: frv cross-compiler?
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: Flags turned on by GCC standard optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: Flags turned on by GCC standard optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Flags turned on by GCC standard optimizations
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: regarding msp430 addhi3_cy
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Address Sanitizer vs. swapcontext
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Luis <luiceur@xxxxxxxxx>
• Re: Compiling x86 code
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Compiling x86 code
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Address Sanitizer vs. swapcontext
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compiling x86 code
  • From: <29jr48+4pm9iwb1l08rc@xxxxxxxxxxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Anthony Brandon <anthony.brandon@xxxxxxxxx>
• Re: Compiling x86 code
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Luis <luiceur@xxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Compiling x86 code
  • From: EdibleChicken <edible@xxxxxxxxxxxx>
• Re: gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• gcc-5.2: error :Checking multilib configuration for libgomp...
  • From: Luis <luiceur@xxxxxxxxx>
• Re: What does ``-quiet'' option do?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• What does ``-quiet'' option do?
  • From: Utku Gültopu <ugultopu@xxxxxxxxx>
• Address Sanitizer vs. swapcontext
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• debugging the cross compiler
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Using the gcc c compiler with a custom set of mnemonics
  • From: Jeff Law <law@xxxxxxxxxx>
• Using the gcc c compiler with a custom set of mnemonics
  • From: Daniel <daknuett@xxxxxxxxx>
• Re: Makefile issues
  • From: zxuiji <zxuiji@xxxxxxxxx>
• regarding msp430 addhi3_cy
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: How to devirtualize one class?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• How to devirtualize one class?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Fwd: No sscanf Expected Type Warnings When Used Through A Template
  • From: Thomas Thorne <tafthorne@xxxxxxxxx>
• Re: error could not split insn
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: What pattern should I use to get a CMOV?
  • From: Mathieu Malaterre <mathieu.malaterre@xxxxxxxxx>
• error could not split insn
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: frv cross-compiler?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: What pattern should I use to get a CMOV?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: What pattern should I use to get a CMOV?
  • From: Tim Prince <n8tm@xxxxxxx>
• What pattern should I use to get a CMOV?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Anthony Brandon <anthony.brandon@xxxxxxxxx>
• frv cross-compiler?
  • From: Waldemar Brodkorb <wbx@xxxxxxxxxxx>
• Re: failing to build powerpc crosscompiler due to thread.cc
  • From: "Zdenek Sojka" <zsojka@xxxxxxxxx>
• Re: failing to build powerpc crosscompiler due to thread.cc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• failing to build powerpc crosscompiler due to thread.cc
  • From: "Zdenek Sojka" <zsojka@xxxxxxxxx>
• Re: GCC cross compiler target library installation directory
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC cross compiler target library installation directory
  • From: Cinolt Yuklair <cinoltyuklair@xxxxxxxxx>
• Re: Trying to compile gcc 5.2.0 for ARM Cortex-M4
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: Trying to compile gcc 5.2.0 for ARM Cortex-M4
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• Re: Trying to compile gcc 5.2.0 for ARM Cortex-M4
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Trying to compile gcc 5.2.0 for ARM Cortex-M4
  • From: Johannes Bauer <dfnsonfsduifb@xxxxxx>
• Re: No sscanf Expected Type Warnings When Used Through A Template
  • From: Thomas Thorne <tafthorne@xxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: No sscanf Expected Type Warnings When Used Through A Template
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• No sscanf Expected Type Warnings When Used Through A Template
  • From: Thomas Thorne <tafthorne@xxxxxxxxx>
• Re: new trunk dependence on nanosleep()
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Member initialization list warning flag
  • From: Anthony Brandon <anthony.brandon@xxxxxxxxx>
• Re: new trunk dependence on nanosleep()
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: new trunk dependence on nanosleep()
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• new trunk dependence on nanosleep()
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Running GPU programs with gcc.
  • From: Wei Huang <whuang@xxxxxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: Makefile issues
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Function Multiversioning (FMV) in mainline
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Problem installing GCC without shared libraries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Member initialization list warning flag
  • From: Manuel López-Ibáñez <manuel.lopez-ibanez@xxxxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Member initialization list warning flag
  • From: Zygmunt Ptak <zygmuntptak@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: C inlines that are also builtins.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• C inlines that are also builtins.
  • From: Sergey Organov <sorganov@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Fwd: Re: Fwd: Porting gcc to new hardware
  • From: samy adel <samy.adel@xxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>