GCC Help

• Thread Index

• Re: Optimisations and undefined behaviour
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: build gcc on os-x with fortran only
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: build gcc on os-x with fortran only
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• build gcc on os-x with fortran only
  • From: Denis Davydov <davydden@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Makefile issues
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: Makefile issues
  • From: Maximilain <king@xxxxxxxxxxxxxxxxxx>
• Re: Makefile issues
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Makefile issues
  • From: Maximilain <king@xxxxxxxxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Makefile issues
  • From: zxuiji <zxuiji@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Problem installing GCC without shared libraries
  • From: Roparzh Hemon <roparzhhemon@xxxxxxxxx>
• Re: Does -tree apply to armel?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Does -tree apply to armel?
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Does -tree apply to armel?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Optimisations and undefined behaviour
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Optimisations and undefined behaviour
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: commoning up template instantiations
  • From: Jay Foad <jay.foad@xxxxxxxxx>
• Re: UndefinedBehaviorSanitizer failed to deallocate
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Building GCC first time, getting test errors
  • From: Dev Guy <devguy.ca@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re:Re: FW: noreturn atribute and its optimization
  • From: boris smidt <borissmidt@xxxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: commoning up template instantiations
  • From: Jay Foad <jay.foad@xxxxxxxxx>
• Re: commoning up template instantiations
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: commoning up template instantiations
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• commoning up template instantiations
  • From: Jay Foad <jay.foad@xxxxxxxxx>
• Re: UndefinedBehaviorSanitizer failed to deallocate
  • From: Mason <slash.tmp@xxxxxxx>
• Re: UndefinedBehaviorSanitizer failed to deallocate
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: gcc on Red Hat EL 5.11 generating "GNU/Linux" OS/ABI binaries that are unusable on same system
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Possible Bug in gcc5.2
  • From: Matthias Goldhoorn <matthias.goldhoorn@xxxxxxx>
• gcc on Red Hat EL 5.11 generating "GNU/Linux" OS/ABI binaries that are unusable on same system
  • From: Jeff McWilliams <jeff.mcwilliams@xxxxxxxxx>
• Re: linker can't find libraries
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• linker can't find libraries
  • From: jenia.ivlev@xxxxxxxxx (jenia.ivlev)
• Re: FW: noreturn atribute and its optimization
  • From: Avi Kivity <avi@xxxxxxxxxxxx>
• Re: A puzzle: different optimization for compound-expressions
  • From: Bruno Loff <bruno.loff@xxxxxxxxx>
• FW: noreturn atribute and its optimization
  • From: boris smidt <borissmidt@xxxxxxxxxxx>
• Re: A puzzle: different optimization for compound-expressions
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• A puzzle: different optimization for compound-expressions
  • From: Bruno Loff <bruno.loff@xxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: question about gcc rtx
  • From: Jeff Law <law@xxxxxxxxxx>
• question about gcc rtx
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: Arkadiusz Drabczyk <arkadiusz@xxxxxxxxxxxx>
• Re: pass bash variable as argument to gcc
  • From: Bob Wilkinson <bob.wilkinson@xxxxxxxxxxx>
• pass bash variable as argument to gcc
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: gcc Export Control ECCN number if covered under EAR
  • From: Ian Lance Taylor <ianlancetaylor@xxxxxxxxx>
• Re: gcc Export Control ECCN number if covered under EAR
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: gcc Export Control ECCN number if covered under EAR
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Steve Ellcey <sellcey@xxxxxxxxxx>
• Re: Regarding GCC mips64 cross compiler for x86
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Regarding GCC mips64 cross compiler for x86
  • From: Sasi <ckmsasi@xxxxxxxxx>
• Re: gcc Export Control ECCN number if covered under EAR
  • From: Ian Lance Taylor <ianlancetaylor@xxxxxxxxx>
• RE: gcc Export Control ECCN number if covered under EAR
  • From: "Farhat, Sam (GE Aviation, US)" <samgeorge.farhat@xxxxxx>
• Re: How to find function_decl by identifier in plugin
  • From: Ivan Kulagin <kadet901@xxxxxxxxx>
• Re: gcc-5.2.0 fails to compile itself
  • From: john.frankish@xxxxxxxxxxx
• Re: [PATCH] clarify documentation of -Q --help=optimizers
  • From: staticx <mohamedboussaa3@xxxxxxxxx>
• Re: gcc-5.2.0 fails to compile itself
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to find function_decl by identifier in plugin
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: gcc-5.2.0 fails to compile itself
  • From: john.frankish@xxxxxxxxxxx
• Re: Disable all optimization options in GCC
  • From: Mohamed Boussaa <mohamedboussaa3@xxxxxxxxx>
• Re: gcc Export Control ECCN number if covered under EAR
  • From: Ian Lance Taylor <ianlancetaylor@xxxxxxxxx>
• UndefinedBehaviorSanitizer failed to deallocate
  • From: Alex Markin <alexanius@xxxxxxxxx>
• How to find function_decl by identifier in plugin
  • From: Ivan Kulagin <kadet901@xxxxxxxxx>
• gcc Export Control ECCN number if covered under EAR
  • From: "Farhat, Sam (GE Aviation, US)" <samgeorge.farhat@xxxxxx>
• [PATCH] clarify documentation of -Q --help=optimizers
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Martin Sebor <msebor@xxxxxxxxx>
• .rodata/.text size issue
  • From: Jun Li <ollyli@xxxxxxxxx>
• Re: Is there a way not to optimize out "static const" at -Os?
  • From: David Kang <dkang@xxxxxxx>
• Re: Is there a way not to optimize out "static const" at -Os?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Is there a way not to optimize out "static const" at -Os?
  • From: David Kang <dkang@xxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Inconsistent printf format warnings for macro in system headers
  • From: Olivier Blin <olivier.blin@xxxxxxxxxxxxxx>
• Re: [OpenACC] libgomp: cuMemHostGetDevicePointer error: invalid device
  • From: Νίκος Αντωνιάδης <annikos@xxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Mohamed Boussaa <mohamedboussaa3@xxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Lars Nielsen <lars@xxxxxxxxxxxxx>
• Re: Disable all optimization options in GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Disable all optimization options in GCC
  • From: Mohamed Boussaa <mohamedboussaa3@xxxxxxxxx>
• Re: [OpenACC] libgomp: cuMemHostGetDevicePointer error: invalid device
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Re: How to use C style directives in assembler ?
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• How to use C style directives in assembler ?
  • From: weiguixm <623674292@xxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: Inconsistent printf format warnings for macro in system headers
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Mike Stump <mikestump@xxxxxxxxxxx>
• Re: parameter passing for functions written in assembly.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: parameter passing for functions written in assembly.
  • From: vijay nag <vijunag@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Vinh Nguyen <vinhdizzo@xxxxxxxxx>
• Re: debugging the cross compiler
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• __thread keyword with gcc-4.9.2
  • From: Joël Krähemann <jkraehemann@xxxxxxxxx>
• debugging the cross compiler
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Mike Stump <mikestump@xxxxxxxxxxx>
• Re: STACK_POINTER_REGNUM
  • From: Jeff Law <law@xxxxxxxxxx>
• STACK_POINTER_REGNUM
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• gcc-5.2.0 fails to compile itself
  • From: john.frankish@xxxxxxxxxxx
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: john.frankish@xxxxxxxxxxx
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: how build only libsupc++
  • From: Ángel González <keisial@xxxxxxxxx>
• how build only libsupc++
  • From: fedor_qd <fedor_qd@xxxxxxx>
• RE: retaining unused static functions at -O1
  • From: "VandeVondele Joost" <joost.vandevondele@xxxxxxxxxxx>
• Re: retaining unused static functions at -O1
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• retaining unused static functions at -O1
  • From: "VandeVondele Joost" <joost.vandevondele@xxxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Inconsistent printf format warnings for macro in system headers
  • From: Olivier Blin <olivier.blin@xxxxxxxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• GCC Auto-Vectorization with Strided Writes
  • From: SDS <sds.biz.main@xxxxxxxxx>
• Re: gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: How to run the cpp(preprocessor) g++ tests?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• How to run the cpp(preprocessor) g++ tests?
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Problem with compiler not working after install
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Hadrien Grasland <hadrien.grasland@xxxxxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc instruction cost
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Hadrien Grasland <hadrien.grasland@xxxxxxxxxxxx>
• Re: x87 register clobber returns "unknown register name" error
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: gcc instruction cost
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• x87 register clobber returns "unknown register name" error
  • From: Hadrien Grasland <hadrien.grasland@xxxxxxxxxxxx>
• Re: gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Problem with compiler not working after install
  • From: Leonard Wohlsdorf <lwohlsdorf@xxxxxxxxxxx>
• Re: gcc instruction cost
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Undefined reference for static const class member
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Undefined reference for static const class member
  • From: "Hellmund, Andre-Marcel (MRT)" <andre-marcel.hellmund@xxxxxxx>
• Re: gcc instruction cost
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Order of passing optimization flags to gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Order of passing optimization flags to gcc
  • From: Mohamed Boussaa <mohamedboussaa3@xxxxxxxxx>
• gcc instruction cost
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: How to set REX prefix when using RDRAND?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: using __float128 and -std=c++11
  • From: Peter van Hoof <p.vanhoof@xxxxxx>
• Re: using __float128 and -std=c++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: using __float128 and -std=c++11
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• using __float128 and -std=c++11
  • From: Peter van Hoof <p.vanhoof@xxxxxx>
• Re: How to set REX prefix when using RDRAND?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• gcc trunk build ice i386_pe_seh_unwind_emit, cygwin64
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Re: How to set REX prefix when using RDRAND?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: How to set REX prefix when using RDRAND?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• [OpenACC] libgomp: cuMemHostGetDevicePointer error: invalid device
  • From: Νίκος Αντωνιάδης <annikos@xxxxxxxxx>
• Re: How to set REX prefix when using RDRAND?
  • From: Mason <slash.tmp@xxxxxxx>
• How to set REX prefix when using RDRAND?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Need help testing 4.9.3 after compiling with 4.8.4 on Mint Linux 17.2
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• gcov-tool.c invalid conversion error building gcc 5.2.0 on ia64 HPUX
  • From: Brian Groose <brian@xxxxxxxxxx>
• Re: Impact of GCC optimizations on resource consumption
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: What is the preferred way of building a cross compiler?
  • From: Henri Tuhola <henri.tuhola@xxxxxxxxx>
• gcc and binutils target is diffrent
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Impact of GCC optimizations on resource consumption
  • From: Mohamed Boussaa <mohamedboussaa3@xxxxxxxxx>
• Re: What is the preferred way of building a cross compiler?
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: What is the preferred way of building a cross compiler?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: What is the preferred way of building a cross compiler?
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• What is the preferred way of building a cross compiler?
  • From: Henri Tuhola <henri.tuhola@xxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: Porting gcc without porting Binutils?
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Porting gcc without porting Binutils?
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• gcc, code16 and variadic functions
  • From: "Andy Pont" <andy.pont@xxxxxxxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: Daniel Letai <dani@xxxxxxxxxxxx>
• Warn once for a deprecated class, and not each instantiation
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Need help testing 4.9.3 after compiling with 4.8.4 on Mint Linux 17.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Need help testing 4.9.3 after compiling with 4.8.4 on Mint Linux 17.2
  • From: Bryan Dunphy <b.dunphy.342@xxxxxxxxx>
• Re: Exception-Catching with gcc 4.x does not work on SunOS SPARC
  • From: Matthias Apitz <guru@xxxxxxxxxxx>
• Re: Exception-Catching with gcc 4.x does not work on SunOS SPARC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Exception-Catching with gcc 4.x does not work on SunOS SPARC
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Exception-Catching with gcc 4.x does not work on SunOS SPARC
  • From: Mason <mpeg.blue@xxxxxxx>
• Exception-Catching with gcc 4.x does not work on SunOS SPARC
  • From: Matthias Apitz <guru@xxxxxxxxxxx>
• Re: GCC internals - Instruction Patterns
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: GCC internals - Instruction Patterns
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: GCC internals - Instruction Patterns
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: GCC internals - Instruction Patterns
  • From: Jeff Law <law@xxxxxxxxxx>
• GCC internals - Instruction Patterns
  • From: htio2 <wenbin.leong@xxxxxxxxx>
• Re: GNU Java tools gcj and gij hang while trying to compile a java program
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: strong and weak Symbol
  • From: Yuxin Ren <ryx@xxxxxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Understanding compiler warning options
  • From: Martin Sebor <msebor@xxxxxxxxx>
• RE: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: GNU Java tools gcj and gij hang while trying to compile a java program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Add instructions in the beginning of a function
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• GNU Java tools gcj and gij hang while trying to compile a java program
  • From: Ivailo Ivanov <ivailo.ivanov@xxxxxxxxx>
• Add instructions in the beginning of a function
  • From: Marios Pomonis <mpomonis@xxxxxxxxxxxxxxx>
• RE: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: Understanding compiler warning options
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: "dclarke@xxxxxxxxxxxxx" <dclarke@xxxxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Consistency of function attributes between prototype and definition
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: "dclarke@xxxxxxxxxxxxx" <dclarke@xxxxxxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: "dclarke@xxxxxxxxxxxxx" <dclarke@xxxxxxxxxxxxx>
• Consistency of function attributes between prototype and definition
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Understanding compiler warning options
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• bug? gcc/graphite-poly.h:398:43: error: 'isl_constraint' has not been declared
  • From: "dclarke@xxxxxxxxxxxxx" <dclarke@xxxxxxxxxxxxx>
• Re: Minimal linker script for cortex M3 and M4 using gcc for c language applications
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• Re: Issue with g++/gcc 5.2.0 on cygwin about string and std cout
  • From: Tim Prince <n8tm@xxxxxxx>
• Issue with g++/gcc 5.2.0 on cygwin about string and std cout
  • From: "Pat. N." <patrickng9@xxxxxxxx>
• Minimal linker script for cortex M3 and M4 using gcc for c language applications
  • From: Sergio <hardmaker@xxxxxxxxx>
• Re: Understanding compiler warning options
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: objdump produced different results for Ubuntu and Windows
  • From: Helen Tang <huatang@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Vinh Nguyen <vinhdizzo@xxxxxxxxx>
• Re: objdump produced different results for Ubuntu and Windows
  • From: johnsfine@xxxxxxxxxxx
• Re: objdump produced different results for Ubuntu and Windows
  • From: ranganath ramachandra <ranga@xxxxxx>
• Re: Understanding compiler warning options
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Understanding compiler warning options
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• objdump produced different results for Ubuntu and Windows
  • From: Helen Tang <huatang@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Vinh Nguyen <vinhdizzo@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Vinh Nguyen <vinhdizzo@xxxxxxxxx>
• Re: AIX: Ignore duplicate symbols in multiple headers?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Fwd: Problems when use OpenACC with a Kernel
  • From: Thomas Schwinge <thomas@xxxxxxxxxxxxxxxx>
• Inform compiler null vectors from a template class can be combined?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Seeking advice on creating reduced testcase
  • From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
• Re: Compiling for i586 architecture - illegal instruction on executable
  • From: Johann Klammer <klammerj@xxxxxx>
• Re: Compiling for i586 architecture - illegal instruction on executable
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: Compiling for i586 architecture - illegal instruction on executable
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Re: Compiling for i586 architecture - illegal instruction on executable
  • From: Johann Klammer <klammerj@xxxxxx>
• Re: Compiling for i586 architecture - illegal instruction on executable
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Compiling for i586 architecture - illegal instruction on executable
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Re: Re: Seeking advice on creating reduced testcase
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Seeking advice on creating reduced testcase
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Seeking advice on creating reduced testcase
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Seeking advice on creating reduced testcase
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Re: Seeking advice on creating reduced testcase
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Problem compiling gcc 5.2.0 on VortexDX86 embedded
  • From: Renato Mendes <renato.mendes.pes@xxxxxxxxx>
• Seeking advice on creating reduced testcase
  • From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
• AIX: Ignore duplicate symbols in multiple headers?
  • From: Vinh Nguyen <vinhdizzo@xxxxxxxxx>
• Re: gcc 4.9.3: typedef referenced in a friend template function
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc 4.9.3: typedef referenced in a friend template function
  • From: Francis ANDRE <francis.andre.kampbell@xxxxxxxxx>
• Re: hoisting loop invariant loads?
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• hoisting loop invariant loads?
  • From: ranganath ramachandra <ranga@xxxxxx>
• Re: __ATOMIC_RELAXED and cache coherency
  • From: Victor <victor@xxxxxxxxx>
• Re: __ATOMIC_RELAXED and cache coherency
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• __ATOMIC_RELAXED and cache coherency
  • From: Victor <victor@xxxxxxxxx>
• GCC install-strip
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Compiling a Java-implemented JVM with GCJ
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Compiling a Java-implemented JVM with GCJ
  • From: Marko Dimjašević <marko@xxxxxxxxxxxxxx>
• Re: Building Gcc with private Glibc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Building Gcc with private Glibc
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Re: Trouble forcing an include with "-include"
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Trouble forcing an include with "-include"
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Trouble forcing an include with "-include"
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Fatal error during GCC 4.9.2 build
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• passing more parameters in ipa-split.c
  • From: Bilha Mendelson <bilha.mendelson@xxxxxxxxx>
• Re: built-in functions
  • From: Bruno Schneider <boschneider@xxxxxxxxx>
• Re: built-in functions
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: built-in functions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: built-in functions
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• built-in functions
  • From: Bruno Schneider <boschneider@xxxxxxxxx>
• Re: gcc5 and std::string
  • From: Mason <slash.tmp@xxxxxxx>
• RE:gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• RE:gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• Re: gcc5 and std::string
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE:gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• Re: gcc5 and std::string
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc5 and std::string
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE:gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• Re: gcc5 and std::string
  • From: David Abdurachmanov <david.abdurachmanov@xxxxxxxxx>
• RE:gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• Re: gcc5 and std::string
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc5 and std::string
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• gcc5 and std::string
  • From: PICCA Frederic-Emmanuel <frederic-emmanuel.picca@xxxxxxxxxxxxxxxxxxxxx>
• Re: Re: compiling gcc 5.x from the scratch: issues
  • From: Michael Mishourovsky <mike.mishky@xxxxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Re: compiling gcc 5.x from the scratch: issues
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Re: compiling gcc 5.x from the scratch: issues
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Re: compiling gcc 5.x from the scratch: issues
  • From: Michael Mishourovsky <mike.mishky@xxxxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Where are Darwin behaviors documented?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Where are Darwin behaviors documented?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: compiling gcc 5.x from the scratch: issues
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• compiling gcc 5.x from the scratch: issues
  • From: Michael Mishourovsky <mike.mishky@xxxxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• -ffloat-store behavior (Re: Susprising behavior of gcc on x86 (-m32))
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Re: Susprising behavior of gcc on x86 (-m32)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Susprising behavior of gcc on x86 (-m32)
  • From: Mathieu Malaterre <malat@xxxxxxxxxx>
• Fwd: meaning of -falign-loops=12
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• meaning of -falign-loops=12
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: [Consult] about git commit "e52beba PR debug/54694"
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• [Consult] about git commit "e52beba PR debug/54694"
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: vtable Emission inconsistency
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• vtable Emission inconsistency
  • From: Miko Vich <alexmudmiko@xxxxxxxxx>
• Detect if a code is candidate for vectorization ( AVX2 )
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: ADDR_EXPR in gimple
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Mason <slash.tmp@xxxxxxx>
• ADDR_EXPR in gimple
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• Need to the size of a record in gimple
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Mason <slash.tmp@xxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Mason <slash.tmp@xxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Stephan Gatzka <stephan.gatzka@xxxxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Curious behavior with MATLAB, C++ and exceptions
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Curious behavior with MATLAB, C++ and exceptions
  • From: Ricardo Telichevesky <ricardo@xxxxxxxx>
• Re: Choosing the right -march target architecture
  • From: Tim Prince <n8tm@xxxxxxx>
• Choosing the right -march target architecture
  • From: Mason <slash.tmp@xxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Using profile guided optimization in shared library error
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Re: Use BMI2 intrisic without enabling the BMI2 target for the whole translation unit
  • From: Ruben Laguna <ruben.laguna@xxxxxxxxx>
• Re: Function call inlining
  • From: "Matwey V. Kornilov" <matwey.kornilov@xxxxxxxxx>
• Re: Function call inlining
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC plugin question
  • From: Vanush Vaswani <vanush@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Stephan Gatzka <stephan.gatzka@xxxxxxxxx>
• Function call inlining
  • From: "Matwey V. Kornilov" <matwey.kornilov@xxxxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Help! Elderly fortran user.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Help! Elderly fortran user.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Help! Elderly fortran user.
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Help! Elderly fortran user.
  • From: Richard Conn Henry <rhenry1@xxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Use BMI2 intrisic without enabling the BMI2 target for the whole translation unit
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Use BMI2 intrisic without enabling the BMI2 target for the whole translation unit
  • From: Ruben Laguna <ruben.laguna@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Stephan Gatzka <stephan.gatzka@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Kostas Savvidis <ksavvidis@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: 128-bit integer - nonsensical documentation?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• 128-bit integer - nonsensical documentation?
  • From: Kostas Savvidis <ksavvidis@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: parameter type of -frandom-seed
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: ezmlm warning
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: ezmlm warning
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• parameter type of -frandom-seed
  • From: Stephan Gatzka <stephan.gatzka@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: Odd register-register move issue.
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Odd register-register move issue.
  • From: Simon Dardis <Simon.Dardis@xxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: converting function pointers to/from object pointers
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• converting function pointers to/from object pointers
  • From: Josef Wolf <jw@xxxxxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: static functions appearing in the symbol table
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: reproducible build
  • From: Stephan Gatzka <stephan.gatzka@xxxxxxxxx>
• Re: reproducible build
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: static functions appearing in the symbol table
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Gcc Error
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• reproducible build
  • From: Stephan Gatzka <stephan@xxxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• static functions appearing in the symbol table
  • From: Martin Faltesek <martin.faltesek@xxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: Gcc Error
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Gcc Error
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Gcc Error
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Re: declare global in gimple
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• Re: declare global in gimple
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: john smith <wempwer@xxxxxxxxx>
• Re: are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• are statically allocated structs always aligned to a machine word on x86/x86_64?
  • From: john smith <wempwer@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Use of constraints when mapping C variables to ASM symbolic names?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Use of constraints when mapping C variables to ASM symbolic names?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: declare global in gimple
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• Re: Unexpected value-at for NULL'd pointer with pthreads
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Unexpected value-at for NULL'd pointer with pthreads
  • From: Kyle Harper <kylejharper@xxxxxxxxx>
• Re: declare global in gimple
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• declare global in gimple
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• how to keep command line options but add more optimization flag to certain function
  • From: "Guo, Gcwenken" <gcwenken.guo@xxxxxxx>
• Re: -finstrument-function -O2 and printf() instrumentation
  • From: Stefan Ruppert <sr@xxxxxxxxx>
• Re: would like to create a new function out of a loop body
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: GCC: make -k check failed
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• GCC: make -k check failed
  • From: Marek Dolezel <marekdolezel@xxxxxxxxx>
• would like to create a new function out of a loop body
  • From: Bilha Mendelson <bilha.mendelson@xxxxxxxxx>
• Re: How to suppress "warning: -fPIC ignored for target..." under Cygwin
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: How to suppress "warning: -fPIC ignored for target..." under Cygwin
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: update: problems with ltdl versions and building newer versions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• update: problems with ltdl versions and building newer versions
  • From: "L. A. Walsh" <gcc@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• How to suppress "warning: -fPIC ignored for target..." under Cygwin
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Proper use of x86/x86_64 CPUID instruction with extended assembler
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Question about GNU cpp -P
  • From: "W. Michael Petullo" <mike@xxxxxxxx>
• Re: Tail call optimization on function with many arguments
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: init_priority and initialization of POD types
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: -finstrument-function -O2 and printf() instrumentation
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: Question about GNU cpp -P
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Tail call optimization on function with many arguments
  • From: "Lionel Villard" <villard@xxxxxxxxxx>
• Re: Where does C standard mention alignment requirements as written in gcc manual?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Where does C standard mention alignment requirements as written in gcc manual?
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: Where does C standard mention alignment requirements as written in gcc manual?
  • From: john smith <wempwer@xxxxxxxxx>
• Re: Where does C standard mention alignment requirements as written in gcc manual?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Where does C standard mention alignment requirements as written in gcc manual?
  • From: john smith <wempwer@xxxxxxxxx>
• problems with ltdl versions and building newer versions
  • From: "L. A. Walsh" <gcc@xxxxxxxxx>
• Re: Unable to compile GCC 5.2.0 on Debian 7
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• -finstrument-function -O2 and printf() instrumentation
  • From: Stefan Ruppert <sr@xxxxxxxxx>
• Re: Unable to compile GCC 5.2.0 on Debian 7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Unable to compile GCC 5.2.0 on Debian 7
  • From: admin@xxxxxxxxx
• Re: Pointer parameter in function optimized out - incorrectly
  • From: Jeff Law <law@xxxxxxxxxx>
• Question about GNU cpp -P
  • From: "W. Michael Petullo" <mike@xxxxxxxx>
• Re: Pointer parameter in function optimized out - incorrectly
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• Re: Pointer parameter in function optimized out - incorrectly
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Pointer parameter in function optimized out - incorrectly
  • From: James Kuyper <James.R.Kuyper@xxxxxxxx>
• Re: Parentheses not honored when using FMA
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Method to specify initialization order across translation units?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: [wwwdocs] Re: C++ Concepts available in trunk?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [wwwdocs] Re: C++ Concepts available in trunk?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• [wwwdocs] Re: C++ Concepts available in trunk?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Method to specify initialization order across translation units?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: C++ Concepts available in trunk?
  • From: "Dijk, J. van" <J.v.Dijk@xxxxxx>
• Re: Method to specify initialization order across translation units?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• init_priority and initialization of POD types
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Binaries
  • From: Teo Samarzija <teo.samarzija@xxxxxxxxx>
• Re: How to troubleshoot a crash under Cygwin at -O3?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: C++ Concepts available in trunk?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• C++ Concepts available in trunk?
  • From: "Dijk, J. van" <J.v.Dijk@xxxxxx>
• Re: Fwd: Re: Parentheses not honored when using FMA
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Fwd: Re: Parentheses not honored when using FMA
  • From: Tim Prince <tprince818.tp@xxxxxxxxx>
• Re: Parentheses not honored when using FMA
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Parentheses not honored when using FMA
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Parentheses not honored when using FMA
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Parentheses not honored when using FMA
  • From: Marcin Krotkiewski <marcin.krotkiewski@xxxxxxxxx>
• Re: How to troubleshoot a crash under Cygwin at -O3?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: How to troubleshoot a crash under Cygwin at -O3?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to troubleshoot a crash under Cygwin at -O3?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: pthread_cancel and C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: pthread_cancel and C++11
  • From: NightStrike <nightstrike@xxxxxxxxx>
• How to troubleshoot a crash under Cygwin at -O3?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: pthread_cancel and C++11
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: what options to pass to gcc for support of arm security extensions
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: How to compile gcc with custom CFLAGS
  • From: Simon Wright <simon@xxxxxxxxxxxx>
• How to compile gcc with custom CFLAGS
  • From: Jan Sommer <soja-lists@xxxxxxxxxxxxxxxxxx>
• pthread_cancel and C++11
  • From: John Saxton <john.saxton@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Linking problems on CentOS 4.9
  • From: Michael Smith <michael.smith@xxxxxxxxxxxxxx>
• Add codes in c-parser results in compilation error for gcc-4.7.2
  • From: k9119911 <xxx-protoss@xxxxxxxxxxxx>
• cilkplus vectorization problems
  • From: Marcin Krotkiewski <marcin.krotkiewski@xxxxxxxxx>
• Re: Cross compiled gcc 4.9.3 fails with 'unrecognised emulation mode: -dynamic-linker'
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Cross compiled gcc 4.9.3 fails with 'unrecognised emulation mode: -dynamic-linker'
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Cross compiled gcc 4.9.3 fails with 'unrecognised emulation mode: -dynamic-linker'
  • From: Fredrik Fornwall <fredrik@xxxxxxxxxxxx>
• RE: what options to pass to gcc for support of arm security extensions
  • From: "Shahin Ansari" <shansari@xxxxxxxxxxx>
• Re: Cross compiled gcc 4.9.3 fails with 'unrecognised emulation mode: -dynamic-linker'
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Method to specify initialization order across translation units?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Explicit instantiation and static objects in different modules
  • From: Nikolay Vorobyov <nik.vorobyov@xxxxxxxxx>
• Method to specify initialization order across translation units?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Cross compiled gcc 4.9.3 fails with 'unrecognised emulation mode: -dynamic-linker'
  • From: Fredrik Fornwall <fredrik@xxxxxxxxxxxx>
• Re: Explicit instantiation and static objects in different modules
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Explicit instantiation and static objects in different modules
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Explicit instantiation and static objects in different modules
  • From: Alexander Monakov <amonakov@xxxxxxxxx>
• Re: Explicit instantiation and static objects in different modules
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Explicit instantiation and static objects in different modules
  • From: Nikolay Vorobyov <nik.vorobyov@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Details of new std::string
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Details of new std::string
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: Union an alias when the difference is the volatile qualifier?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Union an alias when the difference is the volatile qualifier?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Union an alias when the difference is the volatile qualifier?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• AW: How to build stand-alone (statically linked) gcc?
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: Union an alias when the difference is the volatile qualifier?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: A Question
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Union an alias when the difference is the volatile qualifier?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• RE: what options to pass to gcc for support of arm security extensions
  • From: Sean Ansari <zohal52@xxxxxxxxx>
• RE: A Question
  • From: "Shahin Ansari" <shansari@xxxxxxxxxxx>
• Error building gcc-5.* with threads=win32
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: How to build stand-alone (statically linked) gcc?
  • From: Tim Prince <n8tm@xxxxxxx>
• How to build stand-alone (statically linked) gcc?
  • From: David Kang <dkang@xxxxxxx>
• Re: Link Errors
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Martin Sebor <msebor@xxxxxxxxx>
• Re: what options to pass to gcc for support of arm security extensions
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• RE: what options to pass to gcc for support of arm security extensions
  • From: "Shahin Ansari" <shansari@xxxxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: what options to pass to gcc for support of arm security extensions
  • From: Richard Earnshaw <Richard.Earnshaw@xxxxxxxxxxxx>
• Re: error when compiling gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Link Errors
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: When did -Wmaybe-unitialized make its appearance?
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• When did -Wmaybe-unitialized make its appearance?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Link Errors
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Re: error when compiling gcc
  • From: 纪明 <jiming@xxxxxxxxx>
• Re: error when compiling gcc
  • From: 纪明 <jiming@xxxxxxxxx>
• what options to pass to gcc for support of arm security extensions
  • From: "Shahin Ansari" <shansari@xxxxxxxxxxx>
• A Question
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Re: error when compiling gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: error when compiling gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• error when compiling gcc
  • From: 纪明 <jiming@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang <xili_gchen_5257@xxxxxxxxxxx>
• inline assembly statements in C source files using arm security extensions seems to trigger an error
  • From: Sean Ansari <zohal52@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: gcc 4.9.2 on rhel5
  • From: Ricardo Telichevesky <ricardo@xxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: gcc 4.9.2 on rhel5
  • From: Mikhail Maltsev <maltsevm@xxxxxxxxx>
• Re: gcc 4.9.2 on rhel5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• gcc 4.9.2 on rhel5
  • From: Ricardo Telichevesky <ricardo@xxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC support for C++ noexcept
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• GCC support for C++ noexcept
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Does ada work on x32 currently (gcc 5.x)?
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Re: libstdc++ pretty-printers vs. inspecting objects
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Using half-precision F16C intrinsics
  • From: voxner <voxner.dev@xxxxxxxxx>
• Re: Using half-precision F16C intrinsics
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• libstdc++ pretty-printers vs. inspecting objects
  • From: Avi Kivity <avi@xxxxxxxxxxxxxxxxxxxx>
• Using half-precision F16C intrinsics
  • From: voxner <voxner.dev@xxxxxxxxx>
• Does ada work on x32 currently (gcc 5.x)?
  • From: Giuseppe Caizzone <acaizzo@xxxxxxxxx>
• building gcc cross compiler:error: cannot find crti.o, configured --with-newlib
  • From: sindhu selvam <sindhu.ara.selvam@xxxxxxxxx>