GCC Help

• Thread Index

• Re: Preprocessed output in gcc 4.5.2
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Shea Levy <shea@xxxxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Shea Levy <shea@xxxxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Preprocessed output in gcc 4.5.2
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Shea Levy <shea@xxxxxxxxxxxx>
• Preprocessed output in gcc 4.5.2
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Shea Levy <shea@xxxxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Shea Levy <shea@xxxxxxxxxxxx>
• Re: Linker Error When Building gnat 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Linker Error When Building gnat 4.6.0
  • From: shea@xxxxxxxxxxxx
• Re: Problem Building cross GCC 4.6.0
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem Building cross GCC 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Massimiliano Cialdi <massimiliano.cialdi@xxxxxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Warning for incompatible pointer type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Massimiliano Cialdi <massimiliano.cialdi@xxxxxxxxxxxx>
• Warning for incompatible pointer type
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Re: Problem Building cross GCC 4.6.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problem Building cross GCC 4.6.0
  • From: shea@xxxxxxxxxxxx
• Re: Lifetime of local variables: global versus member function
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: arm-elf-gcc 4.6.0 build failure
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Lifetime of local variables: global versus member function
  • From: Jan van Dijk <jan@xxxxxxxxxxxxxxxxxx>
• Re: name of template friend function in template class
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• arm-elf-gcc 4.6.0 build failure
  • From: Massimiliano Cialdi <massimiliano.cialdi@xxxxxxxxxxxx>
• name of template friend function in template class
  • From: "." <burlen.loring@xxxxxxxxx>
• Re: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: "Nasser M. Abbasi" <nma@xxxxxxxxx>
• Re: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: "Nasser M. Abbasi" <nma@xxxxxxxxx>
• Re: will LTO help python modules?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Change default sizeof(long double) to 128-bit
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Change default sizeof(long double) to 128-bit
  • From: bd satish <bdsatish@xxxxxxxxx>
• Fwd: Re: Change default sizeof(long double) to 128-bit
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• will LTO help python modules?
  • From: Neal Becker <ndbecker2@xxxxxxxxx>
• Change default sizeof(long double) to 128-bit
  • From: bd satish <bdsatish@xxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• failed building gcc 4.6 from sources on linux mint 2.6.35-28-generic, when doing Fortran build
  • From: "Nasser M. Abbasi" <nma@xxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: gcc --prefix in chrooted environment
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Why does my executable size not change?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc --prefix in chrooted environment
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Why does my executable size not change?
  • From: richardcavell@xxxxxxxx
• Re: can't disable pointer-to-int-cast warnings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: How to give compiler error if a function parameter is not declared with __thread?
  • From: "Shaun Pinney" <shaun.pinney@xxxxxxxxxxxxxxxxxxx>
• Re: How to give compiler error if a function parameter is not declared with __thread?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: can't disable pointer-to-int-cast warnings
  • From: "Hargett, Matt" <matt.hargett@xxxxxxxxxxxx>
• RE: How to give compiler error if a function parameter is not declared with __thread?
  • From: "Shaun Pinney" <shaun.pinney@xxxxxxxxxxxxxxxxxxx>
• Re: can't disable pointer-to-int-cast warnings
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to give compiler error if a function parameter is not declared with __thread?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• can't disable pointer-to-int-cast warnings
  • From: "Hargett, Matt" <matt.hargett@xxxxxxxxxxxx>
• How to give compiler error if a function parameter is not declared with __thread?
  • From: "Shaun Pinney" <shaun.pinney@xxxxxxxxxxxxxxxxxxx>
• Re: Strings
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: confirm unsubscribe from gcc@xxxxxxxxxxx
  • From: César <divcesar@xxxxxxxxx>
• Re: GCC assembling with scheduling
  • From: n90p <nop144d@xxxxxxxxx>
• Re: Strings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Strings
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: GCC assembling with scheduling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• GCC assembling with scheduling
  • From: n90p <nop144d@xxxxxxxxx>
• Re: Strings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Strings
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: ICE in final linking stage with -flto
  • From: Gunther Piez <gpiez@xxxxxx>
• Re: gcc 4.6 build failure
  • From: naga raj <gnuuser.raj@xxxxxxxxx>
• Re: gcc 4.6 build failure
  • From: Mohamed Shafi <shafitvm@xxxxxxxxx>
• gcc 4.6 build failure
  • From: naga raj <gnuuser.raj@xxxxxxxxx>
• Re: Hooking address
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC backend development
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: GCC backend development
  • From: Radu Hobincu <radu.hobincu@xxxxxxxxxx>
• Re: Hooking address
  • From: nazgul144 <nlscotty@xxxxxxxxxxx>
• Re: Hooking address
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC backend development
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Hooking address
  • From: nazgul144 <nlscotty@xxxxxxxxxxx>
• GCC backend development
  • From: Radu Hobincu <radu.hobincu@xxxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: Zuxy Meng <zuxy.meng@xxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: Zuxy Meng <zuxy.meng@xxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Machine readable build log with gcc warnings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Bootstrap problem with current trunk?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: _mm_store_pd/s translated to movntpd/s
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ICE in final linking stage with -flto
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "rep ret" even for Intel CPUs?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Machine readable build log with gcc warnings
  • From: Martin Olsson <mnemo@xxxxxxxxxx>
• Bootstrap problem with current trunk?
  • From: Benjamin Redelings <benjamin.redelings@xxxxxxxxxxx>
• Re: _mm_store_pd/s translated to movntpd/s
  • From: Matthias Kretz <kretz@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: _mm_store_pd/s translated to movntpd/s
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: _mm_store_pd/s translated to movntpd/s
  • From: Matthias Kretz <kretz@xxxxxxxxxxxxxxxxxxxxxxxx>
• _mm_store_pd/s translated to movntpd/s
  • From: Matthias Kretz <kretz@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• RE: function overloading on __restrict__
  • From: "Eric Fernandez" <efernandez@xxxxxxxxxxxxxxxxxx>
• ICE in final linking stage with -flto
  • From: Gunther Piez <gpiez@xxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• RE: function overloading on __restrict__
  • From: "Eric Fernandez" <efernandez@xxxxxxxxxxxxxxxxxx>
• Best command line options for debug/release builds
  • From: richardcavell@xxxxxxxx
• "rep ret" even for Intel CPUs?
  • From: "Zuxy Meng" <zuxy.meng@xxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: [Fwd: C:How to program 3rdEd, fig18_03.cpp](g++ 4.4.3)(trouble on simple overload)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• [Fwd: C:How to program 3rdEd, fig18_03.cpp](g++ 4.4.3)(trouble on simple overload)
  • From: eric <fsshl@xxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• -D/U_FORTIFY_SOURCE, -fstack-protector(-all) and --enable/disable-libssp
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: creating a dll using a static library
  • From: Juan Ramírez <juanantonio.ram@xxxxxxxxx>
• Re: RE : creating a dll using a static library
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• minimal gcc install
  • From: Mike Rosset <mike.rosset@xxxxxxxxx>
• Re: function overloading on __restrict__
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• function overloading on __restrict__
  • From: Matthias Kretz <kretz@xxxxxxxxxxxxxxxxxxxxxxxx>
• RE : creating a dll using a static library
  • From: Luc MOULINIER <moumou@xxxxxxxx>
• Re: creating a dll using a static library
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: Weak symbols not overriden
  • From: "H.J. Lu" <hjl.tools@xxxxxxxxx>
• creating a dll using a static library
  • From: Luc MOULINIER <moumou@xxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Weak symbols not overriden
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: Weak symbols not overriden
  • From: Pan ruochen <panruochen@xxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: error: conflicting types for 'psignal'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Weak symbols not overriden
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• error: conflicting types for 'psignal'
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• psim problem -- loading file into psim memory space
  • From: "Mazer, Alan S (388H)" <Alan.S.Mazer@xxxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• gcc-hel
  • From: parkersonlarry@xxxxxxx
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: working on type declaration
  • From: <piervit@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Thomas Martitz <thomas.martitz@xxxxxxxxxxxxxxxxxxxxx>
• Weak symbols not overriden
  • From: Pan ruochen <panruochen@xxxxxxxxx>
• Weak symbols not overriden
  • From: Pan ruochen <panruochen@xxxxxxxxx>
• Re: [HELP]: Name conflicting in dynamically loading shared libraries
  • From: Jovi Zhang <bookjovi@xxxxxxxxx>
• Re: [HELP]: Name conflicting in dynamically loading shared libraries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• [HELP]: Name conflicting in dynamically loading shared libraries
  • From: Jovi Zhang <bookjovi@xxxxxxxxx>
• Re: working on type declaration
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem with member function template, template type and 'template' keyword
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• working on type declaration
  • From: <piervit@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: ARM thumbmode architecture question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Building a cross compiler, and unsure about the use of --without-headers
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem with member function template, template type and 'template' keyword
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem with member function template, template type and 'template' keyword
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Problem with member function template, template type and 'template' keyword
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Help For Installing gcc in Mac OS X 10.6
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Help For Installing gcc in Mac OS X 10.6
  • From: Ahmed Salmi <salmi.hassani@xxxxxxxxx>
• Re: ARM thumbmode architecture question
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Building a cross compiler, and unsure about the use of --without-headers
  • From: David Paterson <dnpaterson@xxxxxxxxx>
• Re: ARM thumbmode architecture question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• ARM thumbmode architecture question
  • From: Steffen Dettmer <steffen.dettmer@xxxxxxxxxxxxxx>
• Re: gcc 4.4.4 can freeze x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc 4.4.4 can freeze x86_64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Strings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: building native cross compiler
  • From: Mick McCreath <Mick.McCreath@xxxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• gcc 4.4.4 can freeze x86_64
  • From: "Wolfram R. Jarisch" <wolfram@xxxxxxxxxxxx>
• Strings
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Modifications to x86 __attribute__(__thiscall__) and __attribute__(cdecl) calling conventions
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: Modifications to x86 __attribute__(__thiscall__) and __attribute__(cdecl) calling conventions
  • From: Robert Butler <lighth7015@xxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: Modifications to x86 __attribute__(__thiscall__) and __attribute__(cdecl) calling conventions
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ARM EABI version 5 and bpabi.o
  • From: Andrew Haley <aph@xxxxxxxxxx>
• ARM EABI version 5 and bpabi.o
  • From: Sebastian Huber <sebastian.huber@xxxxxxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Modifications to x86 __attribute__(__thiscall__) and __attribute__(cdecl) calling conventions
  • From: Robert Butler <lighth7015@xxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: parameter evaluation order
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• parameter evaluation order
  • From: jessevdam <jessevdam@xxxxxxxxxxx>
• Re: Which Libraries Come With GCC 4.5.1
  • From: richardcavell@xxxxxxxx
• Re: Which Libraries Come With GCC 4.5.1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Which Libraries Come With GCC 4.5.1
  • From: Andrew Shepard <ashepard@xxxxxxxxxxx>
• Re: C compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• C compiler
  • From: "Rohit Rehan" <rohitrehan008@xxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: gcov in infinite loop
  • From: Paul Floyd <paulf@xxxxxxx>
• Re: [Bug target/46208] Sparc calling conventions (and overheads) in the embedded context
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• gcc linker (binder) error on AIX 5.2
  • From: Jose Luis <jose_luis_fdez_diaz@xxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Ishita Kapadiya <ishimegh@xxxxxxxxx>
• Re: Record Types and Arrays
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: A<T> is not derived from B<T>
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: relocation error: R_AMD64_PC32
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Ishita Kapadiya <ishimegh@xxxxxxxxx>
• Re: A<T> is not derived from B<T>
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Record Types and Arrays
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: relocation error: R_AMD64_PC32
  • From: asyropoulos@xxxxxxx
• Re: building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• Re: A<T> is not derived from B<T>
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• A<T> is not derived from B<T>
  • From: SPUeNTRUP - Kai Henningsen <Kai.Henningsen@xxxxxxx>
• Re: C-frontend NOP_EXPR help
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building native cross compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• C-frontend NOP_EXPR help
  • From: Markus Lottmann <lottvomschlott@xxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Ishita Kapadiya <ishimegh@xxxxxxxxx>
• building native cross compiler
  • From: Michael Zintakis <michael.zintakis@xxxxxxxxxxxxxx>
• [Bug target/46208] Sparc calling conventions (and overheads) in the embedded context
  • From: Zbigniew Chamski <zbigniew.chamski@xxxxxxxxx>
• Re: Code bloating
  • From: Frans Grotepass <fmgrotepass@xxxxxxxxxxx>
• Re: problem compiling 32 bit application on 64 bit Linux server
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• problem compiling 32 bit application on 64 bit Linux server
  • From: Ishita Kapadiya <ishimegh@xxxxxxxxx>
• Re: gcc4.1.2 and 4.3.2 has different default behavior
  • From: Yixuan Huang <yixuan178@xxxxxxxxx>
• Re: Code bloating
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Code bloating
  • From: denis campredon <denis.campredon@xxxxxxxxx>
• Re: relocation error: R_AMD64_PC32
  • From: David Kirkby <david.kirkby@xxxxxxxxxx>
• Re: relocation error: R_AMD64_PC32
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• relocation error: R_AMD64_PC32
  • From: asyropoulos@xxxxxxx
• Re: gcc4.1.2 and 4.3.2 has different default behavior
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc4.1.2 and 4.3.2 has different default behavior
  • From: Yixuan Huang <yixuan178@xxxxxxxxx>
• Re: Help building the newer gcc
  • From: Paul Floyd <paulf@xxxxxxx>
• Help building the newer gcc
  • From: Scott Smith <scott.smith155@xxxxxxxxxxx>
• Re: Multilib problem with arm-elf
  • From: Thomas Martitz <thomas.martitz@xxxxxxxxxxxxxxxxxxxxx>
• Re: Null pointer check elimination
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Null pointer check elimination
  • From: richardcavell@xxxxxxxx
• Re: Howto detect -std=c++0x mode?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Howto detect -std=c++0x mode?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Howto detect -std=c++0x mode?
  • From: Neal Becker <ndbecker2@xxxxxxxxx>
• Re: Null pointer check elimination
  • From: Jeff Law <law@xxxxxxxxxx>
• Multilib problem with arm-elf
  • From: Honza <xhpohanka@xxxxxxxxx>
• Null pointer check elimination
  • From: sankar chebolu <chnabsankar@xxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Re: loop unroll feedback
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• loop unroll feedback
  • From: Hoy Loper <hoy@xxxxxxxxx>
• Re: how to generate x86 "narrowing" divide instruction
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: how to generate x86 "narrowing" divide instruction
  • From: Jay Foad <jay.foad@xxxxxxxxx>
• Re: linker question, silent duplicate symbol problem
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: How to stop gcc caching
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
  • From: José Luis García Pallero <jgpallero@xxxxxxxxx>
• Questions about Gcc regression test.
  • From: guo xuepeng <flameroc@xxxxxxxxx>
• "White paper" about GCC front-end internals
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: Record Types and Arrays
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: How to stop gcc caching
  • From: richardcavell@xxxxxxxx
• Re: suggestion for GCC (1)
  • From: Enrico Weigelt <weigelt@xxxxxxxx>
• Re: How to stop gcc caching
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to stop gcc caching
  • From: richardcavell@xxxxxxxx
• Re: Precedence of GNU C++ extensions >? and <? (min/max operators)
  • From: Jeremy Hall <gcc.hall@xxxxxxxxx>
• Re: Compiler error using 4.5.2 with function template
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Compiler error using 4.5.2 with function template
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Compiler error using 4.5.2 with function template
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Precedence of GNU C++ extensions >? and <? (min/max operators)
  • From: Bob Plantz <plantz@xxxxxxxx>
• Compiler error using 4.5.2 with function template
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: Precedence of GNU C++ extensions >? and <? (min/max operators)
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Precedence of GNU C++ extensions >? and <? (min/max operators)
  • From: Jeremy Hall <gcc.hall@xxxxxxxxx>
• Re: linker question, silent duplicate symbol problem
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: linker question, silent duplicate symbol problem
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: linker question, silent duplicate symbol problem
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Need help for modifying the format of debug
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• linker question, silent duplicate symbol problem
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: Need help for modifying the format of debug
  • From: stephen <chency666@xxxxxxxxx>
• Re: gcc 4.6.0 with llibgomp for mingw64
  • From: Alen Skondro <askondro@xxxxxxxxx>
• Re: Need help for modifying the format of debug
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Need help for modifying the format of debug
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Need help for modifying the format of debug
  • From: stephen <chency666@xxxxxxxxx>
• Re: gcov in infinite loop
  • From: Paul Floyd <paulf@xxxxxxx>
• Re: Record Types and Arrays
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Record Types and Arrays
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: gcov in infinite loop
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• gcov in infinite loop
  • From: paulf@xxxxxxx
• Re: Disabling FMA instructions on an Itanium II platform
  • From: Tim Prince <n8tm@xxxxxxx>
• Disabling FMA instructions on an Itanium II platform
  • From: Raghu Reddy <rreddy@xxxxxxx>
• About gcov format
  • From: Виктор Малов <malvikus@xxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc 4.6.0 with llibgomp for mingw64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: pre-processor symbols and gcc -v
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• pre-processor symbols and gcc -v
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• gcc 4.6.0 with llibgomp for mingw64
  • From: Alen Skondro <askondro@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: Relocating code on cortex m3 but keeping data constant
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Relocating code on cortex m3 but keeping data constant
  • From: Dan Baldor <danbaldor@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: How to best cope with variadic input
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: How to best cope with variadic input
  • From: Maximilian Schneider <king@xxxxxxxxxxxxxxxxxx>
• Re: How to best cope with variadic input
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to best cope with variadic input
  • From: richardcavell@xxxxxxxx
• Re: Relocating code on cortex m3 but keeping data constant
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Relocating code on cortex m3 but keeping data constant
  • From: Dan Baldor <danbaldor@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How to query a constexpr std::tuple at compile time?
  • From: Lars Schmidt-Thieme <schmidt-thieme@xxxxxxxx>
• Re: C++ 'extern inline' magic possible?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• C++ 'extern inline' magic possible?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: Gcc vector extensions
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Gcc vector extensions
  • From: Hari Sandanagobalane <hariharans@xxxxxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Andrew Richardson <a.chardson@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: any m68k gurus out there?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: 3.4.6 build
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Relocating code on cortex m3 but keeping data constant
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Andrew Richardson <a.chardson@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Andrew Richardson <a.chardson@xxxxxxxxx>
• any m68k gurus out there?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Andrew Richardson <a.chardson@xxxxxxxxx>
• Re: UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• UnsatisfiedLinkError (gxx and gcj) with JNI and C++ but not C
  • From: Andrew Richardson <a.chardson@xxxxxxxxx>
• 3.4.6 build
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Output files with memry information?
  • From: Schnapphase <schnapphase@xxxxxxxxxxxxxx>
• Re: ftree-vectorize flag
  • From: vahagvahag <vahagvardanyan@xxxxxxxxx>
• Re: ftree-vectorize flag
  • From: Ira Rosen <IRAR@xxxxxxxxxx>
• Re: ftree-vectorize flag
  • From: vahagvahag <vahagvardanyan@xxxxxxxxx>
• Re: ftree-vectorize flag
  • From: Ira Rosen <IRAR@xxxxxxxxxx>
• ftree-vectorize flag
  • From: vahagvahag <vahagvardanyan@xxxxxxxxx>
• Re: Output files with memry information?
  • From: Nicholas Sherlock <n.sherlock@xxxxxxxxx>
• Output files with memry information?
  • From: Schnapphase <schnapphase@xxxxxxxxxxxxxx>
• Re: optimization, powerpc style
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Relocating code on cortex m3 but keeping data constant
  • From: Dan Baldor <danbaldor@xxxxxxxxx>
• Re: Must unwind in gcc be ported for gcj?
  • From: Bryce McKinlay <bmckinlay@xxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: horseloverFat <gabriel.satanovsky@xxxxxxxxx>
• Re: Must unwind in gcc be ported for gcj?
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• Must unwind in gcc be ported for gcj?
  • From: majia gm <gmmajia@xxxxxxxxx>
• Re: extern "C" function return types
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: extern "C" function return types
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• extern "C" function return types
  • From: Brian Kohan <bckohan@xxxxxxxxx>
• Re: make error in libstdc++-v3/libsupc++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make error in libstdc++-v3/libsupc++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: make error in libstdc++-v3/libsupc++
  • From: yuchape <yuchape@xxxxxxxxx>
• make error in libstdc++-v3/libsupc++
  • From: yuchape <yuchape@xxxxxxxxx>
• Re: FW: Huge binaries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: bound pointer to member
  • From: David Hagood <david.hagood@xxxxxxxxx>
• Re: bound pointer to member
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: bound pointer to member
  • From: "Klaus Rudolph" <lts-rudolph@xxxxxx>
• Re: FW: Huge binaries
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: FW: Huge binaries
  • From: "Hite, Christopher" <Christopher.Hite@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: bound pointer to member
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• bound pointer to member
  • From: "Klaus Rudolph" <lts-rudolph@xxxxxx>
• Re: Newbie new to the list
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Can You Put Comments Into GCC Compiler Options Files?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: plese help to install gcc 2.95.3 compiler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: FW: Huge binaries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: alias question
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: alias question
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: plese help to install gcc 2.95.3 compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: Rainer Orth <ro@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: plese help to install gcc 2.95.3 compiler
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Can You Put Comments Into GCC Compiler Options Files?
  • From: "Craig Dedo" <craig@xxxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: plese help to install gcc 2.95.3 compiler
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• plese help to install gcc 2.95.3 compiler
  • From: nayanalekha sugandanee <nayanalekhas@xxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: horseloverFat <gabriel.satanovsky@xxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: FW: Huge binaries
  • From: "Hite, Christopher" <Christopher.Hite@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: horseloverFat <gabriel.satanovsky@xxxxxxxxx>
• Re: options for later passes
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: a puzzle of struct in gcc (4.6.0 20110212).
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Problem creating PIC executable
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: Help with gcc partial link (option -ar)
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Help with gcc partial link (option -ar)
  • From: horseloverFat <gabriel.satanovsky@xxxxxxxxx>
• a puzzle of struct in gcc (4.6.0 20110212).
  • From: yansheng si <siyansheng@xxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: -lpthread -lstdc++ crashes on IRIX 6.5
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: options for later passes
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: FW: Huge binaries
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: options for later passes
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• options for later passes
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: FW: Huge binaries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• -lpthread -lstdc++ crashes on IRIX 6.5
  • From: "Peter O'Gorman" <pogma@xxxxxxxxxxxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: FW: Huge binaries
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: FW: Huge binaries
  • From: "Hite, Christopher" <Christopher.Hite@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: FW: Huge binaries
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: FW: Huge binaries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem creating PIC executable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: [OpenMP] use -fopenmp in a new front end
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• FW: Huge binaries
  • From: "Hite, Christopher" <Christopher.Hite@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problem creating PIC executable
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: R_PPC_REL24 relocation [...] __libc_start_main/__nptl_deallocate_tsd out of range
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: Re : [GCC front end] add new TREE CODE
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• [OpenMP] use -fopenmp in a new front end
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re : [GCC front end] add new TREE CODE
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: -funsigned-char option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Re: Problems g++ library compiling in QNX 6.5.0
  • From: bogdan <bceler@xxxxx>
• Re: -funsigned-char option
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -no-integrated-cpp option
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: -funsigned-char option
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Strange behaviour in derived class when using -std=c++0x
  • From: Jakob van Bethlehem <j.s.van.bethlehem@xxxxxxxxxxxx>
• Re: Strange behaviour in derived class when using -std=c++0x
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Strange behaviour in derived class when using -std=c++0x
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Strange behaviour in derived class when using -std=c++0x
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Strange behaviour in derived class when using -std=c++0x
  • From: Jakob van Bethlehem <j.s.van.bethlehem@xxxxxxxxxxxx>
• Re: -no-integrated-cpp option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -fcond-mismatch option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -flax-vector-conversions option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -funsigned-char option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -no-integrated-cpp option
  • From: asmwarrior <asmwarrior@xxxxxxxxx>
• -no-integrated-cpp option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• -fcond-mismatch option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• -flax-vector-conversions option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• -funsigned-char option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: Problems g++ library compiling in QNX 6.5.0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: alias question
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: Does extern "C" affect compilation mode
  • From: Graham Bloice <gbloice@xxxxxxxxx>
• Problems g++ library compiling in QNX 6.5.0
  • From: bogdan <bceler@xxxxx>
• Re: Does extern "C" affect compilation mode
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Does extern "C" affect compilation mode
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compilation of GCC-4.3.5 fails
  • From: Paul van Hoven <paul.van.hoven@xxxxxxxxxxxxxx>
• Does extern "C" affect compilation mode
  • From: Graham Bloice <gbloice@xxxxxxxxx>
• Re: alias question
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: alias question
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Why can't I LD_PRELOAD __assert_fail ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: why this testcase compile failed for gcc.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: alias question
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: alias question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: alias question
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re : can not make gcc-dev
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: alias question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: alias question
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: alias question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: alias question
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: alias question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why can't I LD_PRELOAD __assert_fail ?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why can't I LD_PRELOAD __assert_fail ?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Newbie new to the list
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: g++, I'm not able to produce debug info for some classes
  • From: "Vyacheslav V. Yurkov" <uvv.mail@xxxxxxxxx>
• Re: Newbie new to the list
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Why can't I LD_PRELOAD __assert_fail ?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: alias question
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Why can't I LD_PRELOAD __assert_fail ?
  • From: Chris Barry <cbarry@xxxxxxxxxxxxxxxx>
• Newbie new to the list
  • From: "[p e r c e p t i c o n]" <percepticon@xxxxxxxxx>
• alias question
  • From: xorbe <xorbe@xxxxxxxxx>
• Re: can not make gcc-dev
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: can not make gcc-dev
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: can not make gcc-dev
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: can not make gcc-dev
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Reducing testcase sets using GCC
  • From: Peter Watkins <peter_watkins@xxxxxxxxxx>
• can not make gcc-dev
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: Strange behavior with templates and G++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Strange behavior with templates and G++
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: infinite for-loop and related question
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Strange behavior with templates and G++
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• RE: Problem cross-compiling trunk for bfin
  • From: "Henderson, Stuart" <Stuart.Henderson@xxxxxxxxxx>
• Re: cross compile under linux|windows with tru64(alpha) target
  • From: Artifex Maximus <artifexor@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: How to use "thiscall" in g++, compatible with MS C++?
  • From: Miles Bader <miles@xxxxxxx>
• How to use "thiscall" in g++, compatible with MS C++?
  • From: yansheng si <siyansheng@xxxxxxxxx>
• why this testcase compile failed for gcc.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Thomas Martitz <thomas.martitz@xxxxxxxxxxxxxxxxxxxxx>
• Re: Problem cross-compiling trunk for bfin
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: infinite for-loop and related question
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Bob Plantz <plantz@xxxxxxxx>
• RE: infinite for-loop and related question
  • From: Jason Mancini <jayrusman@xxxxxxxxxxx>
• Re: infinite for-loop and related question
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• infinite for-loop and related question
  • From: Jason Mancini <jayrusman@xxxxxxxxxxx>
• Problem cross-compiling trunk for bfin
  • From: "Henderson, Stuart" <Stuart.Henderson@xxxxxxxxxx>
• Re: Bootstrap failure in libgcc stage 1 x86_64-linux-gnu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• [off topic] imaginary PowerPC instructions
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: R_PPC_REL24 relocation [...] __libc_start_main/__nptl_deallocate_tsd out of range
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Bootstrap failure in libgcc stage 1 x86_64-linux-gnu
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Bootstrap failure in libgcc stage 1 x86_64-linux-gnu
  • From: Ed Smith-Rowland <3dw4rd@xxxxxxxxxxx>
• Re: cross compile under linux|windows with tru64(alpha) target
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: cross compile under linux|windows with tru64(alpha) target
  • From: Artifex Maximus <artifexor@xxxxxxxxx>
• Re: need volatile for asm?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: need volatile for asm?
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: need volatile for asm?
  • From: Drasko DRASKOVIC <drasko.draskovic@xxxxxxxxx>
• Re: need volatile for asm?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• R_PPC_REL24 relocation [...] __libc_start_main/__nptl_deallocate_tsd out of range
  • From: Stefano Bonifazi <stefboombastic@xxxxxxxxx>
• Re: -nostdlib option!
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Variant code generation
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Variant code generation
  • From: sankar chebolu <chnabsankar@xxxxxxxxx>
• Re: need volatile for asm?
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• need volatile for asm?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: code gen for C string literals
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: optimization, powerpc style
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: code gen for C string literals
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: code gen for C string literals
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: code gen for C string literals
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: cross compile under linux|windows with tru64(alpha) target
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -nostdlib option!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• cross compile under linux|windows with tru64(alpha) target
  • From: Artifex Maximus <artifexor@xxxxxxxxx>
• Re: -nostdlib option!
  • From: Thomas Martitz <thomas.martitz@xxxxxxxxxxxxxxxxxxxxx>
• Re: -nostdlib option!
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: -nostdlib option!
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: -nostdlib option!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• New message
  • From: "Fito-Plant" <info@xxxxxxxxxxxxxx>
• Re: [GCC front end] add new TREE CODE
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: [GCC front end] add new TREE CODE
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: code gen for C string literals
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: dl_iterate_phdr support
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• [GCC front end] add new TREE CODE
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: code gen for C string literals
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: dl_iterate_phdr support
  • From: John Marino <gnugcc@xxxxxxxxx>
• Re: dl_iterate_phdr support
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: code gen for C string literals
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Are there locale functions taking locale_t arg(e.g. btowc_l)?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Are there locale functions taking locale_t arg(e.g. btowc_l)?
  • From: Larry Evans <cppljevans@xxxxxxxxxxxxxx>
• Re: Error when forward referencing an enum in a typedef
  • From: Graham Bloice <gbloice@xxxxxxxxx>
• Re: Bootstrap failure in libgcc stage 1 x86_64-linux-gnu
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Error when forward referencing an enum in a typedef
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Error when forward referencing an enum in a typedef
  • From: Graham Bloice <gbloice@xxxxxxxxx>
• please add mpc 0.8.2 to the infrastructure page
  • From: Kamaraju S Kusumanchi <raju.mailinglists@xxxxxxxxx>
• Bootstrap failure in libgcc stage 1 x86_64-linux-gnu
  • From: Ed Smith-Rowland <3dw4rd@xxxxxxxxxxx>
• dl_iterate_phdr support
  • From: John Marino <gnugcc@xxxxxxxxx>
• Re: C++ and garbage collection
  • From: Enrico Weigelt <weigelt@xxxxxxxx>
• code gen for C string literals
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: optimization, powerpc style
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: optimization, powerpc style
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: optimization, powerpc style
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• GFortranBinaries - Mac OS X Leopard
  • From: "Kenneth R. Morris \"Bob\"" <Kenneth.R.Morris@xxxxxxxxxxxxxxxxxxxxxxxxx>
• optimization, powerpc style
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Problem with compiling using -m32
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: Problem with compiling using -m32
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Problem with compiling using -m32
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problem with compiling using -m32
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: about function attributes for functions returning a pointer
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: about function attributes for functions returning a pointer
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: about function attributes for functions returning a pointer
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Regerding gcc 4.2.1 compiler for windows
  • From: Tim Prince <n8tm@xxxxxxx>
• Regerding gcc 4.2.1 compiler for windows
  • From: "parashar" <srishti.cse@xxxxxxxxx>
• Re: about function attributes for functions returning a pointer
  • From: Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx>
• Re: Why gcc manual does not explain some sections
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: where is __is_trivial used in type_traits 4.5.1 defined?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• where is __is_trivial used in type_traits 4.5.1 defined?
  • From: Larry Evans <cppljevans@xxxxxxxxxxxxxx>
• Why gcc manual does not explain some sections
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: SIGSEGV with C compiler/RTL. Possible scanf() problem.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: the difference between -mtune and -march
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: the difference between -mtune and -march
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• SIGSEGV with C compiler/RTL. Possible scanf() problem.
  • From: TPCgcc@xxxxxxxxxxxxxxxxxxx
• suggestion for GCC (1)
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: the difference between -mtune and -march
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: the difference between -mtune and -march
  • From: Miles Bader <miles@xxxxxxx>
• Re: the difference between -mtune and -march
  • From: keshav yadav <keshav.yadav2005@xxxxxxxxx>
• the difference between -mtune and -march
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: page size change on MIPS
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Thomas Martitz <thomas.martitz@xxxxxxxxxxxxxxxxxxxxx>
• Re: page size change on MIPS
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: mip64 cross gcc build problem
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: C++ and garbage collection
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• mip64 cross gcc build problem
  • From: Jacky Cao <cao.zhong1@xxxxxxxxx>
• RE: -nostdlib option!
  • From: "Manuel Coutinho" <manuel.coutinho@xxxxxxxxxx>
• Re: -nostdlib option!
  • From: Drasko DRASKOVIC <drasko.draskovic@xxxxxxxxx>
• RE: -nostdlib option!
  • From: "Manuel Coutinho" <manuel.coutinho@xxxxxxxxxx>
• Re: page size change on MIPS
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: -nostdlib option!
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: -nostdlib option!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• RE: -nostdlib option!
  • From: "Manuel Coutinho" <manuel.coutinho@xxxxxxxxxx>
• Re: -nostdlib option!
  • From: Drasko DRASKOVIC <drasko.draskovic@xxxxxxxxx>
• -nostdlib option!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: Do not spill variables/registers on the stack
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: suggestion for GCC (1)
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>