GCC Help

• Thread Index

• Re: bit test instruction
  • From: Jeff Law <law@xxxxxxxxxx>
• bit test instruction
  • From: James Bowman <jamesb@xxxxxxxxxxxx>
• Problem building gcc with C and Ada support for target powerpc-eabispe
  • From: LABARTHE Guillaume <guillaume.labarthe@xxxxxxxxx>
• Re: Passing @file option to linker
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Passing @file option to linker
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang S <gang.chen@xxxxxxxxxxxxx>
• flto-report output
  • From: Nilesh Asher <nilesh.asher@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chris Metcalf <cmetcalf@xxxxxxxxxx>
• Re: Subclassing CNI classes (GCJ)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Subclassing CNI classes (GCJ)
  • From: Andreas Besting <besting@xxxxxxxxxxxxx>
• Re: Is "undefined reference" the same as "unresolved external symbol"?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: cpp 4.8: Preprocessor Output: Is it possible to switch of the flags for the linemarkers
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• cpp 4.8: Preprocessor Output: Is it possible to switch of the flags for the linemarkers
  • From: Richard Sailer <Richard.Sailer@xxxxxx>
• Re: Is "undefined reference" the same as "unresolved external symbol"?
  • From: emkessler <ldgn86a@xxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang S <gang.chen@xxxxxxxxxxxxx>
• Re: [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Mike Stump <mikestump@xxxxxxxxxxx>
• [Consult] tile: How to construct testsuite for tile architecture without hardware.
  • From: Chen Gang S <gang.chen@xxxxxxxxxxxxx>
• alignas with templates
  • From: Gero Peterhoff <g.peterhoff@xxxxxxxxxxx>
• Re: Is "undefined reference" the same as "unresolved external symbol"?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Is "undefined reference" the same as "unresolved external symbol"?
  • From: emkessler <ldgn86a@xxxxxxxxx>
• test_real_width static assertion failure while cross building gcc-4.9 for x32
  • From: Helmut Grohne <helmut@xxxxxxxxxx>
• Re: Assist me for FOSS GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Assist me for FOSS GCC
  • From: Harjot kaur <harjotpandher93@xxxxxxxxx>
• HONOR_REG_ALLOC_ORDER for mips target
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: Running C test with g++?
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Re: Running C test with g++?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Running C test with g++?
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Re: Is "undefined reference" the same as "unresolved external symbol"?
  • From: Bernd Jendrissek <bernd@xxxxxxxxxxxxxx>
• Re: -fstack-protect
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Is "undefined reference" the same as "unresolved external symbol"?
  • From: emkessler <ldgn86a@xxxxxxxxx>
• Re: -fstack-protect
  • From: Jeff Law <law@xxxxxxxxxx>
• -fstack-protect
  • From: Mike Harrold <alexmudmiko@xxxxxxxxx>
• Expanding GOT table with xgot options fails
  • From: Alex Tern <ternvein@xxxxxxxxx>
• Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: libgccjit.so build fails with ISL enabled
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: libgccjit.so build fails with ISL enabled
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: libgccjit.so build fails with ISL enabled
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bitmap problem in gcc 4.9.2
  • From: Václav Zeman <vhaisman@xxxxxxxxx>
• libgccjit.so build fails with ISL enabled
  • From: Prathamesh Kulkarni <prathamesh.kulkarni@xxxxxxxxxx>
• Re: vtable origin in class information
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [PATCH v2] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
  • From: Chen Gang S <gang.chen@xxxxxxxxxxxxx>
• vtable origin in class information
  • From: Enes Goktas <e.goktas@xxxxx>
• Re: Dejagnu
  • From: Chung-Ju Wu <jasonwucj@xxxxxxxxx>
• Re: GCC 4.9.2 w/binutils 2.24 compile error
  • From: Chung-Ju Wu <jasonwucj@xxxxxxxxx>
• libssp visibility check broken?
  • From: Luke Allardyce <lukeallardyce@xxxxxxxxx>
• -O3 return performance degradation
  • From: Stefan de Konink <stefan@xxxxxxxxx>
• Using gcov for embedded systems
  • From: Channagoud <ckadabi@xxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Should I install 4.8.4 or 4.9.2 if I just want C++11
  • From: chengm204 <chengm349@xxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Problems with Keil5 with GNU Tools ARM Embedded 4.7 2013q3
  • From: marcoeusebio@xxxxxx
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• [Fwd: Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc]
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC Doesn't Properly Report Access to Uninitialized Pointer Variabl
  • From: Venkatramana Devarapally <devvrr@xxxxxxxxx>
• bitmap problem in gcc 4.9.2
  • From: vikram1729 <vsp1729@xxxxxxxxx>
• Fortran Compilation and updating assistance
  • From: Robert Samis <rsamis@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• RE: look at the assembly at certain address?
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Strict aliasing, int aliased with struct containing int
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Strict aliasing, int aliased with struct containing int
  • From: Maxim Mikityanskiy <maxtram95@xxxxxxxxx>
• Re: Strict aliasing, int aliased with struct containing int
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: _GLIBCXX14_CONSTEXPR
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Strict aliasing, int aliased with struct containing int
  • From: Maxim Mikityanskiy <maxtram95@xxxxxxxxx>
• _GLIBCXX14_CONSTEXPR
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GDB: look at the assembly at certain address?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• GDB: look at the assembly at certain address?
  • From: Bob Fang <dorafmon@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: finding about move vs copy in C++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: finding about move vs copy in C++
  • From: Anthony Shipman <als@xxxxxxxxxxxx>
• Re: finding about move vs copy in C++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• finding about move vs copy in C++
  • From: Anthony Shipman <als@xxxxxxxxxxxx>
• Re: gcc rejects enum/int compatibility
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: gcc rejects enum/int compatibility
  • From: Edwin Pujols <edwinpm5@xxxxxxxxx>
• gcc rejects enum/int compatibility
  • From: Andrew Makhorin <mao@xxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: hot pictures for Bar rafaeleli model
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Old Gcc and compile problems within certain amount of data...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Old Gcc and compile problems within certain amount of data...
  • From: "Itachi.Uchiha" <7joeblack8@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• RE: I cannot Post Qs
  • From: Arbol One <ArbolOne@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: __attribute__((optimize("-O2"))) doesn't work
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• __attribute__((optimize("-O2"))) doesn't work
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Android Native GCC 4.9.2 Build Fails at Dynamic libgcc
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Question about gcc / libgomp OpenMP task scheduling
  • From: Niclas Arndt <niclas_arndt@xxxxxxxxxxx>
• Re: Error in building gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error in building gcc
  • From: HEMANT PATNI <hemant.patni@xxxxxxxxx>
• Re: Error in building gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Error in building gcc
  • From: HEMANT PATNI <hemant.patni@xxxxxxxxx>
• Re: GCC 4.8.3 make all-target-libstdc++-v3 error: eh_arm.cc cannot use typeid with -fno-rtti
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Wierd Compiler Issue
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Wierd Compiler Issue
  • From: shomari sharpe <shomari.sharpe@xxxxxxxxx>
• GCC 4.8.3 make all-target-libstdc++-v3 error: eh_arm.cc cannot use typeid with -fno-rtti
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• cortex
  • From: Freeman Gilmore <freeman.gilmore@xxxxxxxxx>
• How do I avioid a plugin to be loaded in lto1
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mingw-64 80 bit precision for doubles works
  • From: navin p <navinp1281@xxxxxxxxx>
• Re: mingw-64 80 bit precision for doubles works
  • From: <sisyphus1@xxxxxxxxxxxxxxx>
• Re: Clean build with JIT fails at stage 2.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Clean build with JIT fails at stage 2.
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: mingw-64 80 bit precision for doubles works
  • From: Tim Prince <n8tm@xxxxxxx>
• mingw-64 80 bit precision for doubles works
  • From: navin p <navinp1281@xxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Clean build with JIT fails at stage 2.
  • From: Ed Smith-Rowland <3dw4rd@xxxxxxxxxxx>
• Re: Specify -ldl with libasan in XGCC Specs
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Richard Earnshaw <rearnsha@xxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Richard Earnshaw <rearnsha@xxxxxxx>
• Re: Specify -ldl with libasan in XGCC Specs
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Specify -ldl with libasan in XGCC Specs
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• trying out openacc 2.0
  • From: Mark Farnell <mark.farnell@xxxxxxxxx>
• Cross compiling and multiple sysroot question
  • From: "Steve Ellcey " <sellcey@xxxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Accessing non-existing varargs argument
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Accessing non-existing varargs argument
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• transactional memory support for mips target
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: I met a "strange" thing...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: I met a "strange" thing...
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• I met a "strange" thing...
  • From: Graziano Servizi <Graziano.Servizi@xxxxxxxxxx>
• extracting compiler options form a pre-compiled header file
  • From: Vincenzo Innocente <vincenzo.innocente@xxxxxxx>
• Re: gcc-c++ handling of default arguments
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Re: disable auto-vectorisation
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: disable auto-vectorisation
  • From: Gero Peterhoff <g.peterhoff@xxxxxxxxxxx>
• disable auto-vectorisation
  • From: Gero Peterhoff <g.peterhoff@xxxxxxxxxxx>
• GCC option to control function call epilogue
  • From: Chaoran Yang <chaoran@xxxxxxxx>
• Re: gcc-c++ handling of default arguments
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Re: gcc-c++ handling of default arguments
  • From: Michael Cronenworth <mike@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: failure notice
  • From: Grégory Vaumourin <gregory.vaumourin@xxxxxxxxx>
• Re: gcc-c++ handling of default arguments
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• gcc-c++ handling of default arguments
  • From: Michael Cronenworth <mike@xxxxxxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compilation security options for shared libraries and executables (daemon) with G++ 4.9.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: use of const keyword
  • From: Yu Sheng Oh <humbleoh@xxxxxxxxx>
• Re: use of const keyword
  • From: Yu Sheng Oh <humbleoh@xxxxxxxxx>
• use of const keyword
  • From: bostjanv <bostjanv@xxxxxxxxxxxx>
• Re: Compilation security options for shared libraries and executables (daemon) with G++ 4.9.2
  • From: Some Developer <someukdeveloper@xxxxxxxxx>
• Re: Compilation security options for shared libraries and executables (daemon) with G++ 4.9.2
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Compilation security options for shared libraries and executables (daemon) with G++ 4.9.2
  • From: Some Developer <someukdeveloper@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Fatal error during GCC 4.9.2 build
  • From: Michael Freitag <freitagm@xxxxxxxxxxxxxxxxx>
• Fatal error during GCC 4.9.2 build
  • From: Michael Freitag <freitagm@xxxxxxxxxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: A problem of template implicit instantiation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A problem of template implicit instantiation
  • From: Yu Sheng Oh <humbleoh@xxxxxxxxx>
• Re: A problem of template implicit instantiation
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• A problem of template implicit instantiation
  • From: Yu Sheng Oh <humbleoh@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: memory_order and C99
  • From: Andrew Haley <aph@xxxxxxxxxx>
• memory_order and C99
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Specify Glibc Location
  • From: Jake <jake.waksbaum@xxxxxxxxx>
• Re: Mingw-w64 and flto
  • From: Patrick Oppenlander <pattyo.lists@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.9.2 Build Fails at cc1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC 4.9.2 Build Fails at cc1
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: inline asm constraint for ymm0 register analogous to "Yz" for xmm0
  • From: vvsed <vvsed@xxxxxxxxxxx>
• inline asm constraint for ymm0 register analogous to "Yz" for xmm0
  • From: vvsed <vvsed@xxxxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Help Reporting a Bug
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Help Reporting a Bug
  • From: "Henning Thedens" <hete2@xxxxxx>
• Re: Using Compound Literal + type-punning to initialize static const array
  • From: Joseph Myers <joseph@xxxxxxxxxxxxxxxx>
• Re: Using Compound Literal + type-punning to initialize static const array
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Mingw-w64 and flto
  • From: Adrien Nader <adrien@xxxxxxxx>
• Re: Question about multiarch builds
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Question about multiarch builds
  • From: "Steve Ellcey " <sellcey@xxxxxxxxxx>
• Re: does #pragma GCC optimize work with gcc 4.9.2 LTO?
  • From: starlight.2014q4@xxxxxxxxxxx
• Re: Is there any way to give a warning when a nested function use its parent function's local variable value.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Is there any way to give a warning when a nested function use its parent function's local variable value.
  • From: Mark Farnell <mark.farnell@xxxxxxxxx>
• Re: Is there any way to give a warning when a nested function use its parent function's local variable value.
  • From: xinglp <xinglp@xxxxxxxxx>
• Mingw-w64 and flto
  • From: Greg Williamson <cheeseboy16@xxxxxxxxx>
• does #pragma GCC optimize work with gcc 4.9.2 LTO?
  • From: starlight.2014q4@xxxxxxxxxxx
• Using Compound Literal + type-punning to initialize static const array
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: arm a timer with initial expiration set to 0, doesnt work
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• arm a timer with initial expiration set to 0, doesnt work
  • From: jenia.ivlev@xxxxxxxxx (jenia.ivlev)
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Is there any way to give a warning when a nested function use its parent function's local variable value.
  • From: Mark Farnell <mark.farnell@xxxxxxxxx>
• Is there any way to give a warning when a nested function use its parent function's local variable value.
  • From: xinglp <xinglp@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Problem including gcc-plugin.h
  • From: Andres Tiraboschi <andres.tiraboschi@xxxxxxxxxxxxxxxxxxxxxx>
• Re: "expected primary-expression" error building gcc 4.8.3
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: question on template overload
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• question on template overload
  • From: Graziano Servizi <Graziano.Servizi@xxxxxxxxxx>
• "expected primary-expression" error building gcc 4.8.3
  • From: Allan Streib <astreib@xxxxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Help: Function prologue: mov vs push instruction
  • From: CJ <c.jaiprakash@xxxxxxxxx>
• Re: enforcing a hard page-zero segment for OSX binary deployment
  • From: Qianqian Fang <fangqq@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Unable to configure gcc 4.9.2 on mac OSX 10.10.1 with ISL 0.12.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• enforcing a hard page-zero segment for OSX binary deployment
  • From: Qianqian Fang <fangqq@xxxxxxxxx>
• Unable to configure gcc 4.9.2 on mac OSX 10.10.1 with ISL 0.12.2
  • From: Hemant <hemant.tm@xxxxxxxxx>
• Re: undefined reference to `_Unwind_GetIPInfo'
  • From: Andrew Haley <aph@xxxxxxxxxx>
• undefined reference to `_Unwind_GetIPInfo'
  • From: Pete Moore <Pete.Moore@xxxxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC Cortex-A17, "genattrtab: unknown value `alu_sreg' for `type' attribute"
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• Re: GCC Cortex-A17, "genattrtab: unknown value `alu_sreg' for `type' attribute"
  • From: Kyrill Tkachov <kyrylo.tkachov@xxxxxxx>
• Re: sqrt problem
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: sqrt problem
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: sqrt problem
  • From: Andrew Haley <aph@xxxxxxxxxx>
• sqrt problem
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Re: compiler warning about literal
  • From: Luchezar Belev <lukcho@xxxxxxxxx>
• Re: compiler warning about literal
  • From: Luchezar Belev <lukcho@xxxxxxxxx>
• Re: compiler warning about literal
  • From: Nicholas Mc Guire <der.herr@xxxxxxx>
• Re: compiler warning about literal
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: compiler warning about literal
  • From: Luchezar Belev <lukcho@xxxxxxxxx>
• compiler warning about literal
  • From: Luchezar Belev <lukcho@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Native GCC 4.9.0 Build Fails Building/Linking libgcc_s_so with Undefined Symbol
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• -fstrength-reduce
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: implementation of sizeof and typeof operator
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Detecting whether gcc supports complex types
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• implementation of sizeof and typeof operator
  • From: vikaspushkar <vikaskupushkar@xxxxxxxxx>
• Re: Detecting whether gcc supports complex types
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Detecting whether gcc supports complex types
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Question about asm memory constraints
  • From: David Wohlferd <dw@xxxxxxxxxxxxxxxxxx>
• building gcc 4.9.2 with Java enabled; top_builddir not found
  • From: Evangelos Drikos <drikosev@xxxxxxxxx>
• Dejagnu
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Generated ASM of a typical clamp
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Generated ASM of a typical clamp
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Atomic floats on x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: [PATCH v2] gdb/i387-tdep.c: Avoid warning for "-Werror=strict-overflow"
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Atomic floats on x86_64
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Why target program depends from system GCC
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Why target program depends from system GCC
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• GCC 4.9.2 manuals: GNAT User's Guide
  • From: Nikolai Wendorf <nick@xxxxxxxxxxxx>
• Setting build LIBS
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• arm arch configuration question
  • From: Andreas Tobler <andreast-list@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Q: split-stack app. links agains non-split-stack lib Posteingang
  • From: Oliver Kowalke <oliver.kowalke@xxxxxxxxx>
• Re: Gcc testsuite error
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Gcc testsuite error
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: advanced C++ features with GNU GCC for ARM
  • From: Andrew Haley <aph@xxxxxxxxxx>
• advanced C++ features with GNU GCC for ARM
  • From: Yermolenko Pavel <pavlo.yermolenko@xxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• GCC 4.9.2 w/binutils 2.24 compile error
  • From: Uri Moszkowicz <uri@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• building gcc for AIX
  • From: Michael Felt <aixtools@xxxxxxxxx>
• Fwd: when should --no-undefined flag be used for shared libraries
  • From: Domen Vrankar <domen.vrankar@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Dumping branch predictions made by gcc
  • From: saikatd <saikatdutta.pro2011@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Cross-compiling gcc? (sysroot confusion)
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Cross-compiling gcc? (sysroot confusion)
  • From: Pierre Ossman <ossman@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: split a parallel expression and then combine
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Regarding gcc testsuite
  • From: Andrew Bennett <Andrew.Bennett@xxxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• How to improve debuggability of inlined function?
  • From: Terry Guo <flameroc@xxxxxxxxx>
• split a parallel expression and then combine
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• gcc trunk failure, bad regeneration of plural.c
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Regarding gcc testsuite
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: AArch32 gcc mode
  • From: James Greenhalgh <james.greenhalgh@xxxxxxx>
• Re: AArch32 gcc mode
  • From: Vyacheslav Barinov <v.barinov@xxxxxxxxxxx>
• Re: AArch32 gcc mode
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Two class definitions in different translation units
  • From: Markus Trippelsdorf <markus@xxxxxxxxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Two class definitions in different translation units
  • From: Alex Markin <alexanius@xxxxxxxxx>
• Re: Two class definitions in different translation units
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: AArch32 gcc mode
  • From: James Greenhalgh <james.greenhalgh@xxxxxxx>
• Re: AArch32 gcc mode
  • From: Andrew Haley <aph@xxxxxxxxxx>
• AArch32 gcc mode
  • From: Slava Barinov <v.barinov@xxxxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: Gcc bug or not?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Gcc bug or not?
  • From: Geza Herman <geza@xxxxxxxxxxx>
• Re: Regarding gcc testsuite
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: gcc -l without source files invokes linker
  • From: Prathamesh Kulkarni <bilbotheelffriend@xxxxxxxxx>
• Re: gcc -l without source files invokes linker
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• gcc -l without source files invokes linker
  • From: Prathamesh Kulkarni <bilbotheelffriend@xxxxxxxxx>
• Problem with the plugin interface
  • From: Grégory Vaumourin <gregory.vaumourin@xxxxxxxxx>
• gcc build fails after svn up configure and make
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: 128 bit integers support in gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: configure of gcc failed after svn pull this morning
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: configure of gcc failed after svn pull this morning
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• configure of gcc failed after svn pull this morning
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• 128 bit integers support in gcc
  • From: Evelina Dumitrescu <evelina_dumitrescu@xxxxxxxxx>
• Re: Cross compiling 4.7.2 for arm on x86_64
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Generated ASM of a typical clamp
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Cross compiling 4.7.2 for arm on x86_64
  • From: Diederick Huijbers <diederickh@xxxxxxxxx>
• Re: C compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• C compiler
  • From: BASAVARAJ L KAGE <blkage@xxxxxxxxx>
• Regarding gcc testsuite
  • From: Manpreet Singh <mappysingh@xxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: Richard Earnshaw <rearnsha@xxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: "alexander.bubnov@xxxxxxxxx" <alexander.bubnov@xxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: "alexander.bubnov@xxxxxxxxx" <alexander.bubnov@xxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: "alexander.bubnov@xxxxxxxxx" <alexander.bubnov@xxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
• Re: cross compiler gcc 4.2.3 for FreeBSD 10
  • From: "alexander.bubnov@xxxxxxxxx" <alexander.bubnov@xxxxxxxxx>
• cross compiler gcc 4.2.3 for FreeBSD 10
  • From: "alexander.bubnov@xxxxxxxxx" <alexander.bubnov@xxxxxxxxx>
• Re: -Wzero-as-null-pointer-constant & extern "C" blocks
  • From: Nick <nospam@xxxxxxxxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: [Consult] g++: About "-Wunused-variable" for constant variable in header file
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: [Consult] g++: About "-Wunused-variable" for constant variable in header file
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• [Consult] g++: About "-Wunused-variable" for constant variable in header file
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Fwd: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
  • From: Johan Alfredsson <sduvan.gcc@xxxxxxxxx>
• GCC Plugin for Implementing Loop Interchange
  • From: aditya sasongko <aditya.sasongko0@xxxxxxxxx>
• Re: [Help-bash] Bash 2.05b build failure on OSX10.4
  • From: Geoff Down <geoffdown@xxxxxxxxxxxx>
• Re: [Consult] g++: About "-Wunused-variable" for constant variable initialized by function
  • From: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
• Re: -Wzero-as-null-pointer-constant & extern "C" blocks
  • From: Daniel Llorens <daniel.llorens@xxxxxxxxxx>
• Re: -Wzero-as-null-pointer-constant & extern "C" blocks
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -Wzero-as-null-pointer-constant & extern "C" blocks
  • From: Daniel Llorens <daniel.llorens@xxxxxxxxxx>
• Re: Question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Stage3 Bootstrap Fails...
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Question
  • From: David Hagood <david.hagood@xxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: stop gcc
  • From: Adrien Nader <adrien@xxxxxxxx>
• Re: stop gcc
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Re: stop gcc
  • From: Bert Wesarg <bert.wesarg@xxxxxxxxxxxxxx>
• stop gcc
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Re: GCC needs YOU!
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• gcc build error
  • From: Jason yang <red.wolf.s.husband@xxxxxxxxx>
• Applying -fno-builtin-xxx / -ffreestanding via pragama GCC / attribute optimize
  • From: Jeff Epler <jepler@xxxxxxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: (nessun oggetto)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• (nessun oggetto)
  • From: Graziano Servizi <Graziano.Servizi@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Sandy Harris <sandyinchina@xxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• .gcno files no longer generated by -fprofile-generate since GCC 4.4
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Enhance isatty() for GCC for use with GNU make?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Enhance isatty() for GCC for use with GNU make?
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Optimising away memset() calls?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Enhance isatty() for GCC for use with GNU make?
  • From: Ángel González <keisial@xxxxxxxxx>
• Re: Enhance isatty() for GCC for use with GNU make?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Enhance isatty() for GCC for use with GNU make?
  • From: Paul Smith <psmith@xxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Clément Péron <peron.clem@xxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Florian Weimer <fweimer@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Optimising away memset() calls?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Optimising away memset() calls?
  • From: Sandy Harris <sandyinchina@xxxxxxxxx>
• Build failure bash2.05b OSX10.4
  • From: Geoff Down <geoffdown@xxxxxxxxxxxx>
• Re: Solved
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Solved
  • From: Graziano Servizi <Graziano.Servizi@xxxxxxxxxx>
• Question
  • From: Graziano Servizi <Graziano.Servizi@xxxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• Re: A possible bug
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: A possible bug
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• Re: A possible bug
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A possible bug
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• Re: A possible bug
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• A possible bug
  • From: Ivo Doko <ivo.doko@xxxxxxxxx>
• RE: unspec in machine description file
  • From: Matthew Fortune <Matthew.Fortune@xxxxxxxxxx>
• Re: Local variables used inside an asm block are not recognized as used
  • From: Daniel Kamil Kozar <dkk089@xxxxxxxxx>
• Re: Local variables used inside an asm block are not recognized as used
  • From: David Wohlferd <dw@xxxxxxxxxxxxxxxxxx>
• Re: GCC needs YOU!
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• GCC needs YOU!
  • From: Manuel López-Ibáñez <lopezibanez@xxxxxxxxx>
• Local variables used inside an asm block are not recognized as used
  • From: Daniel Kamil Kozar <dkk089@xxxxxxxxx>
• Re: #error "Unable to find a suitable type for HOST_WIDE_INT"
  • From: Vladimír Fuka <vladimir.fuka@xxxxxxxxx>
• Undefined reference in libcommon, libbacktrace GCC 4.8 bootstrap
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• #error "Unable to find a suitable type for HOST_WIDE_INT"
  • From: Vladimír Fuka <vladimir.fuka@xxxxxxxxx>
• Re: Compiling for arm-none-eabi, but BFD doesn't support it.
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Compiling for arm-none-eabi, but BFD doesn't support it.
  • From: Rena <hyperhacker@xxxxxxxxx>
• GCC 4.8 Build Error 2 gcc/nm: exec: line -89: -pg not found
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Henrik Mannerström <henrik.mannerstrom@xxxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Henrik Mannerström <henrik.mannerstrom@xxxxxxxxx>
• Re: std::string clobbers memory when compiling without optimizations
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• std::string clobbers memory when compiling without optimizations
  • From: Henrik Mannerström <henrik.mannerstrom@xxxxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Clément Péron <peron.clem@xxxxxxxxx>
• Re: Crossed native compiler
  • From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
• -fdebug-prefix-map sometimes randomly has no effect?
  • From: Dave Gittins <dave.gittins@xxxxxxxxx>
• Re: Crossed native compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Crossed native compiler
  • From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
• Re: Crossed native compiler
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Crossed native compiler
  • From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Clément Péron <peron.clem@xxxxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Clément Péron <peron.clem@xxxxxxxxx>
• Re: Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Fwd: Compiling with -fdata-sections doesn't put the constant in the section expected
  • From: Clément Péron <peron.clem@xxxxxxxxx>
• Re: convert main to Function
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• convert main to Function
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• Re: GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: Why __gthread_active_p() is checked only in few functions?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Why __gthread_active_p() is checked only in few functions?
  • From: niXman <i.nixman@xxxxxxxxxxxxx>
• PPC E500v2 cross-compiler pthread_cancel aborting
  • From: "Carr, Chris (GE Intelligent Platforms)" <chris.carr@xxxxxx>
• Re: conversions betwwen function pointers and their calls
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• conversions betwwen function pointers and their calls
  • From: Dima Sorkin <dima.sorkin@xxxxxxxxx>
• Re: GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• Re: GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: gcc-help Digest 27 Sep 2014 11:46:57 -0000 Issue 4675
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Brian Drummond <brian@xxxxxxxxxxxxxxxxxx>
• GCC 4.7 on Android G++ Compiler Build Fail "This Linker Not Config To Use Sysroots"
  • From: Cyd Haselton <chaselton@xxxxxxxxx>
• Re: GCC vectorization of math functions similar to what LLVM does...
  • From: James Greenhalgh <james.greenhalgh@xxxxxxx>
• Re: Program will crash after using gcov
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• Re: Problems bootstrapping GCC on x86_64-unknown-cygwin
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Program will crash after using gcov
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• GCC vectorization of math functions similar to what LLVM does...
  • From: leon zadorin <leonleon77@xxxxxxxxx>
• Problems bootstrapping GCC on x86_64-unknown-cygwin
  • From: Steven Bosscher <stevenb.gcc@xxxxxxxxx>
• Program will crash after using gcov
  • From: Nan Xiao <xiaonan830818@xxxxxxxxx>
• [BUG] ICE in get_narrower, at tree.c:8532
  • From: Marcin Sobieszczanski <marciso.gcc@xxxxxxxxx>
• Finding positions of the instructions
  • From: Eugene Shatokhin <eugene.shatokhin@xxxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: RaJ M <smrajagopal@xxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: RaJ M <smrajagopal@xxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: RaJ M <smrajagopal@xxxxxxxxx>
• Re: static-const-integral in-class-init without explicit definition
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• static-const-integral in-class-init without explicit definition
  • From: RaJ M <smrajagopal@xxxxxxxxx>
• Re: Register Variables in c
  • From: Kayven Riese <kayvey@xxxxxxxxx>
• Re: mtlo/mflo instructions when issue width is increased (MIPS 5kc)
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• MinGW Windows-specific linking warnings
  • From: Patrick Plenefisch <phplenefisch@xxxxxxx>
• Re: Register Variables in c
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: gfortran
  • From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
• Re: Is accessing floating-point register slower than accessing cache-memory?
  • From: Gioh Kim <gioh.kim@xxxxxxx>
• Re: Register Variables in c
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Possible bug in gcc 4.4.7
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: Possible bug in gcc 4.4.7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Restricted user account creation in bugzila.
  • From: Marcin Sobieszczanski <marciso.gcc@xxxxxxxxx>
• RE: Possible bug in gcc 4.4.7
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: Is accessing floating-point register slower than accessing cache-memory?
  • From: James Greenhalgh <james.greenhalgh@xxxxxxx>
• Re: Register Variables in c
  • From: Tim Prince <n8tm@xxxxxxx>
• Register Variables in c
  • From: Ali Abdul Ghani <blade.vp2020@xxxxxxxxx>
• Is accessing floating-point register slower than accessing cache-memory?
  • From: Gioh Kim <gioh.kim@xxxxxxx>
• Re: mtlo/mflo instructions when issue width is increased (MIPS 5kc)
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Possible bug in gcc 4.4.7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• mtlo/mflo instructions when issue width is increased (MIPS 5kc)
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: Possible bug in gcc 4.4.7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: Possible bug in gcc 4.4.7
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: gfortran
  • From: BERTRAND Joël <joel.bertrand@xxxxxxxxxxx>
• Re: Possible bug in gcc 4.4.7
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: Possible bug in gcc 4.4.7
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Re: Possible bug in gcc 4.4.7
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Possible bug in gcc 4.4.7
  • From: "Andy Falanga (afalanga)" <afalanga@xxxxxxxxxx>
• Undefined symbol .LC531 during linker check gcc 3.4.5-p5 - c++ file compilation/linking
  • From: "Sairam Rangaswamy -X (sairanga - ARICENT TECHNOLOGIES MAURIITIUS LIMITED at Cisco)" <sairanga@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Paul Smith <paul@xxxxxxxxxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Hei Chan <structurechart@xxxxxxxxx>
• Error compiling GCC 4.8.3 on OSX 10.10
  • From: Adnan RIHAN <axel50397@xxxxxxxxx>
• Using LINK_SPEC to pass rpath to linker
  • From: Kenneth Chiu <kchiu@xxxxxxxxxxxxxxxxx>
• VLE support for powerpc e200zX family cpus.
  • From: "Raza, Saqlain" <Saqlain_Raza@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Oleg Endo <oleg.endo@xxxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: haynberg@xxxxxxxxx
• conversion warning bug?
  • From: Hariharan Sandanagobalane <hariharan.gcc@xxxxxxxxx>
• Re: Setting the dynamic linker with an environment variable
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: haynberg@xxxxxxxxx
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Changing Mantissa's Width in Non-IEEE Floating Point implementation
  • From: Sheheryar Qazi <sherry1.sherry1@xxxxxxxxx>
• RE: is portable aliasing possible in C++?
  • From: haynberg@xxxxxxxxx
• Re: Setting the dynamic linker with an environment variable
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: Setting the dynamic linker with an environment variable
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Increase the size of allocated memory space for basic blocks
  • From: Yue Chen <ychen.contact@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Jędrzej Dudkiewicz <jedrzej.dudkiewicz@xxxxxxxxx>
• Debugging test failure during SLES 12 build
  • From: Dominik Vogt <vogt@xxxxxxxxxxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Setting the dynamic linker with an environment variable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: haynberg@xxxxxxxxx
• Setting the dynamic linker with an environment variable
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Aaro Koskinen <aaro.koskinen@xxxxxx>
• Re: lib64 and --disable-multilib
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: lib64 and --disable-multilib
  • From: Andrew Haley <aph@xxxxxxxxxx>
• lib64 and --disable-multilib
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Exclude /lib and /usr/lib from the library search path
  • From: Shaun Jackman <sjackman@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Richard Biener <richard.guenther@xxxxxxxxx>
• MIPS 5kc backend - single issue or limited dual issue
  • From: Cherry Vanc <cherry.vanc@xxxxxxxxx>
• Re: removing unused functions during final link
  • From: Melvin Blades <melvin.blades@xxxxxxxxx>
• Re: is portable aliasing possible in C++?
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: Compiling project with g++ built in
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Register spill caused by gcc scheduler?
  • From: Terry Guo <flameroc@xxxxxxxxx>