GCC Help

• Thread Index

• Re: how to include some dll functions in a project
  • From: bigbig <stephane.bigler@xxxxxxx>
• Re: information about ld invocation and defaults ?
  • From: Dave Nadler <Dave.Nadler@xxxxxxxxxx>
• Re: information about ld invocation and defaults ?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: information about ld invocation and defaults ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: information about ld invocation and defaults ?
  • From: Dave Nadler <Dave.Nadler@xxxxxxxxxx>
• Re: information about ld invocation and defaults ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• information about ld invocation and defaults ?
  • From: Dave Nadler <Dave.Nadler@xxxxxxxxxx>
• Re: how to include some dll functions in a project
  • From: Christophe Meessen <meessen@xxxxxxxxxxxxx>
• Re: /usr/bin/ld: unrecognized option
  • From: Artūras Moskvinas <arturas.moskvinas@xxxxxxxxx>
• Fwd: how to include some dll functions in a project
  • From: "Alexey Salmin" <alexey.salmin@xxxxxxxxx>
• Re: how to include some dll functions in a project
  • From: bigbig <stephane.bigler@xxxxxxx>
• Re: /usr/bin/ld: unrecognized option
  • From: hce <webmail.hce@xxxxxxxxx>
• Re: /usr/bin/ld: unrecognized option
  • From: Artūras Moskvinas <arturas.moskvinas@xxxxxxxxx>
• Re: _Unwind_Backtrace vs. _Unwind_RaiseException unwinding
  • From: Roy Krischer <rkrische@xxxxxxxxxxxxxxxx>
• /usr/bin/ld: unrecognized option
  • From: hce <webmail.hce@xxxxxxxxx>
• how to include some dll functions in a project
  • From: bigbig <stephane.bigler@xxxxxxx>
• Re: _Unwind_Backtrace vs. _Unwind_RaiseException unwinding
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: compiling a library with another gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• <gcc@xxxxxxxxxxx>,
  • From: "mal reddy y" <malreddy.y@xxxxxxxxx>
• RE: Explicit template instantiation and -fvisibility. Gcc bug?
  • From: <J.S.Wijnhout@xxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: Rohit <will.u.tellmemore@xxxxxxxxx>
• _Unwind_Backtrace vs. _Unwind_RaiseException unwinding
  • From: Roy Krischer <rkrische@xxxxxxxxxxxxxxxx>
• compiling a library with another gcc
  • From: mafaldalou <lorenasanvicente@xxxxxxxxx>
• Re: c++ static object not created
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: c++ static object not created
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: c++ static object not created
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: long math functions on cygwin
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: c++ static object not created
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: long math functions on cygwin
  • From: "Manal Helal" <manalorama@xxxxxxxxx>
• RE: gcc 4.3.2 compilation failure on aix 5.3
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• RE: GCC in AIX
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Re: Libmudflap-failures-gcc4.1.2
  • From: fche@xxxxxxxxxx (Frank Ch. Eigler)
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: Rohit <will.u.tellmemore@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: Rohit <will.u.tellmemore@xxxxxxxxx>
• Re: Mingw gcc 4.4.0 64bit garbage collector bug?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: Rohit <will.u.tellmemore@xxxxxxxxx>
• Re: gcc 4.3.2 compilation failure on aix 5.3
  • From: "David Edelsohn" <dje.gcc@xxxxxxxxx>
• Sorry, OK now (Re: GCC Build failure - null "program" arg to ylwrap)
  • From: Dave Nadler <Dave.Nadler@xxxxxxxxxx>
• GCC Build failure - null "program" arg to ylwrap
  • From: Dave Nadler <Dave.Nadler@xxxxxxxxxx>
• Problem
  • From: Timo Kreuzer <timo.kreuzer@xxxxxx>
• Re: c++ static object not created
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: c++ static object not created
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: Mingw gcc 4.4.0 64bit garbage collector bug?
  • From: NS <nightstrike@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• c++ static object not created
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• RE: GCC in AIX
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• RE: long math functions on cygwin
  • From: "Anandkumar, CB IN BLR SISL" <anand.cb@xxxxxxxxxxx>
• Libmudflap-failures-gcc4.1.2
  • From: "mal reddy y" <malreddy.y@xxxxxxxxx>
• Re: change to gcc from lcc
  • From: "Alexey Salmin" <alexey.salmin@xxxxxxxxx>
• Re: libstdc++ and --with-sysroot
  • From: "Jon Dufresne" <jon.dufresne@xxxxxxxxx>
• Re: libstdc++ and --with-sysroot
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: libstdc++ and --with-sysroot
  • From: "Jon Dufresne" <jon.dufresne@xxxxxxxxx>
• Re: libstdc++ and --with-sysroot
  • From: Andrew Haley <aph@xxxxxxxxxx>
• libstdc++ and --with-sysroot
  • From: "Jon Dufresne" <jon.dufresne@xxxxxxxxx>
• R: missing terminating ' character
  • From: Alessandro Pellegrini <alessandro.pellegrini@xxxxxx>
• Re: missing terminating ' character
  • From: Hariharan <hariharans@xxxxxxxxxxxx>
• Re: missing terminating ' character
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: GCC suggestions needed
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Mingw gcc 4.4.0 64bit garbage collector bug?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: missing terminating ' character
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Explicit template instantiation and -fvisibility. Gcc bug?
  • From: "Jeroen Wijnhout" <jeroen.wijnhout@xxxxxxxxx>
• Re: Explicit template instantiation and -fvisibility. Gcc bug?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• missing terminating ' character
  • From: Hariharan <hariharans@xxxxxxxxxxxx>
• Re: long math functions on cygwin
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: long math functions on cygwin
  • From: Andrew Haley <aph@xxxxxxxxxx>
• long math functions on cygwin
  • From: Manal Helal <manalorama@xxxxxxxxx>
• Re: GCC suggestions needed
  • From: Niklaus <niklaus@xxxxxxxxx>
• Re: How cpp deal with #abi(n32) ?
  • From: "Pan ruochen" <panruochen@xxxxxxxxx>
• Re: GCC suggestions needed
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Inlining "unexpected behaviour"
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Inlining "unexpected behaviour"
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Inlining "unexpected behaviour"
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How cpp deal with #abi(n32) ?
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• Re: GCC suggestions needed
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Transformations used in GCC
  • From: "Rob Quill" <rob.quill@xxxxxxxxx>
• Re: GCC suggestions needed
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: GCC suggestions needed
  • From: Niklaus <niklaus@xxxxxxxxx>
• Explicit template instantiation and -fvisibility. Gcc bug?
  • From: "Jeroen Wijnhout" <jeroen.wijnhout@xxxxxxxxx>
• Re: GCC suggestions needed
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• GCC suggestions needed
  • From: Niklaus <niklaus@xxxxxxxxx>
• How cpp deal with #abi(n32) ?
  • From: "Pan ruochen" <panruochen@xxxxxxxxx>
• Re: G++ issues
  • From: "Eric Fernandez" <efernandez@xxxxxxxxxxxxxxxxxx>
• Re: GCC Error
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Get function declaration on GCC 3.3
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Speify address for a function while compiling
  • From: "Anandkumar, CB IN BLR SISL" <anand.cb@xxxxxxxxxxx>
• Speify address for a function while compiling
  • From: raghu2383 <raghunathansrinivas@xxxxxxxxx>
• GCC Error
  • From: Denisius <fanatica0@xxxxxxxxxxx>
• G++ issues
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: CC compiler problem
  • From: Shawn Minisall <trekker182@xxxxxxxxx>
• Get function declaration on GCC 3.3
  • From: Le Ton Chanh <letonchanh@xxxxxxxxx>
• mixing gc with someon else's lib
  • From: "Jack Andrews" <effbiae@xxxxxxxxx>
• Re: CC compiler problem
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc incremental build
  • From: Andrew Haley <aph@xxxxxxxxxx>
• CC compiler problem
  • From: Shawn <trekker182@xxxxxxxxx>
• gcc incremental build
  • From: "ankit jindal" <ankitj.jindal@xxxxxxxxx>
• gcc incremental build
  • From: "ankit jindal" <ankitj.jindal@xxxxxxxxx>
• Re: gcc working with libcurl
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• gcc working with libcurl
  • From: c0d3walk3r <dev@xxxxxxxxx>
• Re: search path of header files
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• search path of header files
  • From: "ranjith kumar" <ranjithproxy@xxxxxxxxx>
• Re: long pointer issue with newer gcc compilers
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: long pointer issue with newer gcc compilers
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: dynamic_cast() between a program and a dlopen()ed library
  • From: edam <edam@xxxxxxxxxxxxx>
• long pointer issue with newer gcc compilers
  • From: wcrotty <bill.crotty@xxxxxxxxxxxx>
• Re: dynamic_cast() between a program and a dlopen()ed library
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: dynamic_cast() between a program and a dlopen()ed library
  • From: Eric Gorr <mailist@xxxxxxxxxxxx>
• R: Re: Jump to registers
  • From: Alessandro Pellegrini <alessandro.pellegrini@xxxxxx>
• dynamic_cast() between a program and a dlopen()ed library
  • From: edam <edam@xxxxxxxxxxxxx>
• Re: Jump to registers
  • From: Andrew Haley <aph@xxxxxxxxxx>
• [Fwd: Re: incorrect debug information with -O2 and above options]
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• R: Re: Jump to registers
  • From: Alessandro Pellegrini <alessandro.pellegrini@xxxxxx>
• Re: Jump to registers
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Jump to registers
  • From: Alessandro Pellegrini <alessandro.pellegrini@xxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Problems with -fvisibility in GCC4.3.
  • From: "Jeroen Wijnhout" <jeroen.wijnhout@xxxxxxxxx>
• Re: finding gcc's installation prefix
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• help with missing library..
  • From: "Vinod Pisharody" <vinod.pisharody@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: finding gcc's installation prefix
  • From: prj@xxxxxxxxxxx (Paul Jarc)
• Re: finding gcc's installation prefix
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• finding gcc's installation prefix
  • From: prj@xxxxxxxxxxx (Paul Jarc)
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: incorrect debug information with -O2 and above options
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• Re: incorrect debug information with -O2 and above options
  • From: Andrew Haley <aph@xxxxxxxxxx>
• incorrect debug information with -O2 and above options
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• Re: GCC 4.3.2 in AIX 5.3 - More on this
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• can gcc 4.3.2 be compiled with -m64 on powerpc Mac?
  • From: Yolande Serra <serra@xxxxxxxxxxxxxxxx>
• RE: change to gcc from lcc
  • From: "Anandkumar, CB IN BLR SISL" <anand.cb@xxxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: change to gcc from lcc
  • From: Brian McGrew <brian@xxxxxxxxxxxxx>
• change to gcc from lcc
  • From: Anna Sidera <eep6sa1@xxxxxxxxx>
• RE: Compiling GCC 4.3.2 on Solaris 8 Sparc
  • From: "Michael J. Huber" <Michael.Huber@xxxxxxxxxxxx>
• Compiling GCC 4.3.2 on Solaris 8 Sparc
  • From: "Michael J. Huber" <Michael.Huber@xxxxxxxxxxxx>
• RE: GCC 4.3.2 in AIX 5.3 - More on this
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: gcc-4.2.4
  • From: "Tom Browder" <tom.browder@xxxxxxxxx>
• Re: Passing args in stack or register for each function
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: -ffunction-sections and profiling
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -ffunction-sections and profiling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Marc Glisse <marc.glisse+gcc@xxxxxxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• GCC 4.3.2 in AIX 5.3
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• -ffunction-sections and profiling
  • From: Tim Abbott <tabbott@xxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Passing args in stack or register for each function
  • From: Le Ton Chanh <letonchanh@xxxxxxxxx>
• RE: GCC in AIX
  • From: "Rob Sherry" <rsherry@xxxxxxxxxxxxxxxx>
• installing gcc-4.3.2 on powerpc running OS 10.4.11
  • From: Yolande Serra <serra@xxxxxxxxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: compile new gcc 4.3.2
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC in AIX
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• compile new gcc 4.3.2
  • From: Yolande Serra <serra@xxxxxxxxxxxxxxxx>
• Re: GCC in AIX
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• GCC in AIX
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• why does __builtin_types_compatible_p work this way?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: rules for __builtin_types_compatible_p??
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: rules for __builtin_types_compatible_p??
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: 32 x 32 -> 64 bit widening multiply on x86_64
  • From: Mark Dickinson <dickinsm@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: 32 x 32 -> 64 bit widening multiply on x86_64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Cooperation request: ScienceStage.com - the online portal for institutes, scientists and universities
  • From: "contact@xxxxxxxxxxxxxxx"<contact@xxxxxxxxxxxxxxx>
• RE: GCC 4.3.2 installation on Linux
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• 32 x 32 -> 64 bit widening multiply on x86_64
  • From: "Mark Dickinson" <dickinsm@xxxxxxxxx>
• RE: GCC 4.3.2 installation on Linux
  • From: "Anandkumar, CB IN BLR SISL" <anand.cb@xxxxxxxxxxx>
• RE: trying to compile vlc with gcc
  • From: Some user <sendspam@xxxxxxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: how to enable -mlong-double-128 option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: GCC 4.3.2 installation on Linux
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• gcc 3.3 for Mac OS X 10.5
  • From: Judith Schenk <jschenk@xxxxxxxxxxxx>
• Re: GCC 4.3.2 installation on Linux
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• GCC 4.3.2 installation on Linux
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• RE: How to force gcc warn the conditions which are true of false forever?
  • From: "Anandkumar, CB IN BLR SISL" <anand.cb@xxxxxxxxxxx>
• Re: how to enable -mlong-double-128 option
  • From: "Jason Pernito" <jpernito@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Re: "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: Andrew Haley <aph@xxxxxxxxxx>
• "../.././gcc/c-common.c", line 2259: invalid token: short_fract_type_no...
  • From: "kamaraju kusumanchi" <raju.mailinglists@xxxxxxxxx>
• Gfortran installation
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• rules for __builtin_types_compatible_p?? (was: __builtin_types_compatible_p and 'char *' vs. 'char []')
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: socket programming
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: how to enable -mlong-double-128 option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc-4.3.2 native build failed
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• Re: socket programming
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Re: socket programming
  • From: Sven Eschenberg <eschenb@xxxxxxxxxxxxxxxxxxx>
• Re: gcc-4.3.2 native build failed
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• socket programming
  • From: "ranjith kumar" <ranjithproxy@xxxxxxxxx>
• gcc-4.3.2 native build failed
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• Re: how to distribute binary tools
  • From: "Eric Fisher" <joefoxreal@xxxxxxxxx>
• Fix bug in earlier GCC release
  • From: "Johan Ekberg" <johan.ekberg@xxxxxxxx>
• Re: how to distribute binary tools
  • From: "Jason Pernito" <jpernito@xxxxxxxxx>
• how to distribute binary tools
  • From: "Eric Fisher" <joefoxreal@xxxxxxxxx>
• how to enable -mlong-double-128 option
  • From: "Jason Pernito" <jpernito@xxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: "Frank Lagor" <dfranci@xxxxxxxxxxxxxx>
• Re: Verification that taking address of a nested function always requires executable stack
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: Saturated integer addition in C
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• __builtin_types_compatible_p and 'char *' vs. 'char []'
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• RE: Spin locks
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Spin locks
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: Spin locks
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Spin locks
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Spin locks
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Verification that taking address of a nested function always requires executable stack
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: Saturated integer addition in C
  • From: "Rohit Garg" <rpg.314@xxxxxxxxx>
• Re: Verification that taking address of a nested function always requires executable stack
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Verification that taking address of a nested function always requires executable stack
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: "Frank Lagor" <dfranci@xxxxxxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: "Frank Lagor" <dfranci@xxxxxxxxxxxxxx>
• Re: compiler install fails- reason is not immediately clear
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• compiler install fails- reason is not immediately clear
  • From: "Frank Lagor" <dfranci@xxxxxxxxxxxxxx>
• Re: Saturated integer addition in C
  • From: Lawrence Crowl <crowl@xxxxxxxxxx>
• Re: e500 architecture and branch instructions
  • From: "Claude Vittoria" <claude.vittoria@xxxxxxxxx>
• Re: strange dynamic_cast problem
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: e500 architecture and branch instructions
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: "Axel Freyn" <Axel-Freyn@xxxxxx>
• strange dynamic_cast problem
  • From: Eric Gorr <mailist@xxxxxxxxxxxx>
• Saturated integer addition in C
  • From: "Liam Vrilehen" <vrilehen@xxxxxxxxxxxxxx>
• Re: How to get more detailed compiler output?
  • From: Unga <unga888@xxxxxxxxx>
• e500 architecture and branch instructions
  • From: "Claude Vittoria" <claude.vittoria@xxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: How to force gcc warn the conditions which are true of false forever?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Copy constructor not being called on function return
  • From: Stuart Brooks <stuartb@xxxxxxxxx>
• RE: Copy constructor not being called on function return
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to force gcc warn the conditions which are true of false forever?
  • From: Nicholas Sherlock <n.sherlock@xxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• How to force gcc warn the conditions which are true of false forever?
  • From: "Pan ruochen" <panruochen@xxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: Best way of compiling applications to run on older linux distros
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Best way of compiling applications to run on older linux distros
  • From: Tom Quarendon <tom.quarendon@xxxxxxxxxxxxx>
• Re: Copy constructor not being called on function return
  • From: Stuart Brooks <stuartb@xxxxxxxxx>
• Re: using gcc to build a control flow graph
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• using gcc to build a control flow graph
  • From: "Tanya Gornak" <errizo@xxxxxxxxx>
• Re: Copy constructor not being called on function return
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: How to get more detailed compiler output?
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Copy constructor not being called on function return
  • From: Stuart Brooks <stuartb@xxxxxxxxx>
• ICE when using templates
  • From: "Johan Ekberg" <johan.ekberg@xxxxxxxx>
• Re: -isystem /usr/include - a bad idea? System header files not found
  • From: Jens Seidel <jensseidel@xxxxxxxxxxxx>
• How to get more detailed compiler output?
  • From: Unga <unga888@xxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Install error, gcc-4.3.2 on FC8
  • From: William Estrada <MrUmunhum@xxxxxxxxxxx>
• Re: Flat Binaries for i386
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Why this code can't be compiled
  • From: "Max Dmitrichenko" <dmitrmax@xxxxxxxxx>
• Re: Why this code can't be compiled
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• RE: trying to compile vlc with gcc
  • From: "Rupert Wood" <me@xxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: How to write a macro to concatenate two symbols without spaces between them?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: 96 bit pointer reset only the least 64 bits
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• How to write a macro to concatenate two symbols without spaces between them?
  • From: "Pan ruochen" <panruochen@xxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• RE: trying to compile vlc with gcc
  • From: Some user <sendspam@xxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• 96 bit pointer reset only the least 64 bits
  • From: Nir Piterman <nir.piterman@xxxxxxxxxxxx>
• Flat Binaries for i386
  • From: "Gary Partis" <gary@xxxxxxxxxxxx>
• Re: another problem
  • From: FX <fxcoudert@xxxxxxxxx>
• Why this code can't be compiled
  • From: "Max Dmitrichenko" <dmitrmax@xxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: trying to compile vlc with gcc
  • From: "Rupert Wood" <me@xxxxxxxxx>
• -ftest-coverage -fprofile-arcs doesnt produce the datafiles ?
  • From: "Jani Mikkonen" <jani.mikkonen@xxxxxxxxx>
• trying to compile vlc with gcc
  • From: Some user <sendspam@xxxxxxxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Florian Weimer <fw@xxxxxxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: Vladimir Simonov <sv@xxxxx>
• -isystem /usr/include - a bad idea? System header files not found
  • From: Jens Seidel <jensseidel@xxxxxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gfortran read stdin
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: YueGuang <ygxyvesuvius@xxxxxxxxx>
• Lininkg libs in non-standard dirs
  • From: eddy <bremby@xxxxxxxxx>
• Re: How can I build gcc for arm on a x86_64 machine?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• How can I build gcc for arm on a x86_64 machine?
  • From: YueGuang <ygxyvesuvius@xxxxxxxxx>
• Using Eclipse for developing GCC
  • From: Le Ton Chanh <letonchanh@xxxxxxxxx>
• gfortran read stdin
  • From: coml <coml@xxxxxxxxxx>
• Informations about profile driven optimizations
  • From: "Clemens Eisserer" <linuxhippy@xxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Galloth <lordgalloth@xxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: "Rohit Garg" <rpg.314@xxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: "Andrew Bell" <andrew.bell.ia@xxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: unexpected speedup by manual inlining
  • From: Andrew Haley <aph@xxxxxxxxxx>
• unexpected speedup by manual inlining
  • From: "Rohit Garg" <rpg.314@xxxxxxxxx>
• Re: Help with inline assembly constraints
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Failure to build GCC 4.3.2: HAVE_LIMITS_H not defined
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Help with inline assembly constraints
  • From: "Jason Garrett-Glaser" <darkshikari@xxxxxxxxx>
• Re: How can pass arguments in registers in GCC?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• /usr/include/c++/4.2/exception:59: multiple definition of `root_category'
  • From: "@" <andriy.tylychko@xxxxxxxxx>
• How can pass arguments in registers in GCC?
  • From: Le Ton Chanh <letonchanh@xxxxxxxxx>
• "make install" of gcc-4.2.4 fails
  • From: aschulth <aschulth@xxxxxxxxxxxxxx>
• Re: c++: too many templates?
  • From: "Andrew Bell" <andrew.bell.ia@xxxxxxxxx>
• Re: __BASENAME__?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• __BASENAME__?
  • From: John Breitenbach <breiten@xxxxxxxxxxx>
• Re: double to int cast and rounding issues
  • From: Andrew Haley <aph@xxxxxxxxxx>
• double to int cast and rounding issues
  • From: "Eric Fernandez" <efernandez@xxxxxxxxxxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: Building GCC - gcc: Internal compiler error: program cc1 got fatal signal 11
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Building GCC - gcc: Internal compiler error: program cc1 got fatal signal 11
  • From: "Aaron G. Stemen" <agstemen@xxxxxxxxxxx>
• Re: c++: too many templates?
  • From: "@" <andriy.tylychko@xxxxxxxxx>
• Re: The caller should allocate stack frames for argument area?
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: c++: too many templates?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: GCC-4.3.0 install from src fails during "make"
  • From: Andrew Haley <aph@xxxxxxxxxx>
• GCC-4.3.0 install from src fails during "make"
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: c++: too many templates?
  • From: Arturs Zoldners <az@xxxxxxx>
• c++: too many templates?
  • From: "@" <andriy.tylychko@xxxxxxxxx>
• Re: GCC-4.1.2: gfortran not getting installed
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: Error: installation problem, cannot exec `cc1' ..'as', etc..
  • From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxx>
• The caller should allocate stack frames for argument area?
  • From: "Pan ruochen" <panruochen@xxxxxxxxx>
• Re: Maybe g++ bug (in stl_algo.h 0x08048beb in std::__unguarded_partition)
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: Maybe g++ bug (in stl_algo.h 0x08048beb in std::__unguarded_partition)
  • From: Niklaus <niklaus@xxxxxxxxx>
• Re: A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• RE: A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: A little bit of C fun...
  • From: me22 <me22.ca@xxxxxxxxx>
• RE: A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: Maybe g++ bug (in stl_algo.h 0x08048beb in std::__unguarded_partition)
  • From: "Chris Jefferson" <chris@xxxxxxxxxxxxxxx>
• RE: A little bit of C fun...
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• RE: A little bit of C fun...
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Re: A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• Error: installation problem, cannot exec `cc1' ..'as', etc..
  • From: steroidmicros <bob@xxxxxxxxxxxxxxxxx>
• RE: GCC-4.1.2: gfortran not getting installed
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• RE: GCC-4.1.2: gfortran not getting installed
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Determining size of embedded blobs
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• GCC-4.1.2: gfortran not getting installed
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: Issue with allocating stack space to local variables (frame pointer)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Issue with allocating stack space to local variables (frame pointer)
  • From: "Sivaprasad.pv" <sivaprasad.pv@xxxxxxxxxxxxxxxxxx>
• Re: A little bit of C fun...
  • From: me22 <me22.ca@xxxxxxxxx>
• A little bit of C fun...
  • From: John Carter <john.carter@xxxxxxxxxx>
• buildtin_choose_expr not acting as i would expect from documentation
  • From: "Kristian Jerpetjøn" <kristian.jerpetjoen@xxxxxxxxx>
• Re: gcc command line from inside c source
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc command line from inside c source
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc command line from inside c source
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Determining size of embedded blobs
  • From: Jean Hoderd <jhoderd@xxxxxxxxx>
• Re: gcc command line from inside c source
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Re: Determining size of embedded blobs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: movem for coldfire FW: [netburner.com #22025]
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc command line from inside c source
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Issue with allocating stack space to local variables (frame pointer)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Determining size of embedded blobs
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Determining size of embedded blobs
  • From: Jean Hoderd <jhoderd@xxxxxxxxx>
• Re: GCC: Address of member pointer
  • From: Duane Ellis <duane-gcc-help@xxxxxxxxxxxxxx>
• GCC: Address of member pointer
  • From: Arkansaw <barry.porter@xxxxxxxxxxxxxxxx>
• Re: GCC bug when using boost typeof
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: mpfr-related link errors
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: "relocation truncated to fit: R_MIPS_26 " with gcc 4.1.2 toolchain
  • From: dbadhani <dbadhani@xxxxxxxxx>
• GCC bug when using boost typeof
  • From: "Peng Yu" <pengyu.ut@xxxxxxxxx>
• SPARC memory alignment
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: mpfr-related link errors
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• mpfr-related link errors
  • From: Bob Walters <mostlyharmless77@xxxxxxxxx>
• configure error: Fortran name-mangling scheme... - with gcc & gfortran-4.1.0
  • From: "Sangamesh B" <forum.san@xxxxxxxxx>
• Re: build error: error: '_U' was not declared in this scope
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• build error: error: '_U' was not declared in this scope
  • From: "M R Swami Reddy" <MR.Swami.Reddy@xxxxxxx>
• RE: structure packing.
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• structure packing.
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• Re: builtins.c compile errors
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• builtins.c compile errors
  • From: Bob Walters <mostlyharmless77@xxxxxxxxx>
• Re: Problem building cross-compiler for mips
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• pthread_rwlock problem
  • From: "Alexey Salmin" <alexey.salmin@xxxxxxxxx>
• Re: thread build on solaris
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxxxxx>
• Maybe g++ bug (in stl_algo.h 0x08048beb in std::__unguarded_partition)
  • From: Niklaus <niklaus@xxxxxxxxx>
• movem for coldfire FW: [netburner.com #22025]
  • From: "Jerry Auth" <gauth@xxxxxxxxx>
• gcc command line from inside c source
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Issue with allocating stack space to local variables (frame pointer)
  • From: "Sivaprasad.pv" <sivaprasad.pv@xxxxxxxxxxxxxxxxxx>
• RE: Problem building cross-compiler for mips
  • From: Jay <jay.krell@xxxxxxxxxxx>
• Re: typedef templates
  • From: Deng Xiyue <manphiz@xxxxxxxxx>
• typedef templates
  • From: "Harmon Nine" <harmon.nine@xxxxxxxxx>
• Re: Problem building cross-compiler for mips
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: Problem building cross-compiler for mips
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• RE: Problem building cross-compiler for mips
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Re: Problem building cross-compiler for mips
  • From: Eduardo Brito <pg12188@xxxxxxxxxxxxxxxx>
• Re: Problem building cross-compiler for mips
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Problem building cross-compiler for mips
  • From: Eduardo Brito <pg12188@xxxxxxxxxxxxxxxx>
• Re: Problem building gcc 3.4.6 on 64 bit linux machine
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: tiande <tiande@xxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: "MICHAEL R. MEISSNER" <meissner@xxxxxxxxxxxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: tiande <tiande@xxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: tiande <tiande@xxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: tiande <tiande@xxxxxxxxx>
• RE: Gfortran and load flags
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: __sync_bool_compare_and_swap and structures
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Gfortran and load flags
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Need line number info in .so files created with GCC 4.3.2
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• __sync_bool_compare_and_swap and structures
  • From: Robert Lemmen <robertle@xxxxxxxxxxxxxx>
• Gfortran and load flags
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Why do gcc support empty struct extension for?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Need line number info in .so files created with GCC 4.3.2
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Why do gcc support empty struct extension for?
  • From: tiande <tiande@xxxxxxxxx>
• Need line number info in .so files created with GCC 4.3.2
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Library tripled in size with GCC 4.2
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Re: Library tripled in size with GCC 4.2
  • From: Eric Gorr <mailist@xxxxxxxxxxxx>
• Re: Library tripled in size with GCC 4.2
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Re: Library tripled in size with GCC 4.2
  • From: Eric Gorr <mailist@xxxxxxxxxxxx>
• RE: Help with malloc
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• randomized bss section?
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• RE: Library tripled in size with GCC 4.2
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Library tripled in size with GCC 4.2
  • From: Eric Gorr <mailist@xxxxxxxxxxxx>
• Re: debugging "break point" in optimized code?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• ISO_C_BINDING intrinsics
  • From: James Rinkevich <james.rinkevich@xxxxxxxxx>
• debugging "break point" in optimized code?
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Possible ARM 4.1.2 g++ optimizer bug
  • From: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Bob Plantz <plantz@xxxxxxxx>
• Re: "human readable" optimized code
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Re: "human readable" optimized code
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• "human readable" optimized code
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Re: relocatable code and object files and shared libraries
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: relocatable code and object files and shared libraries
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Possibly emutls_destroy() has a problem on HP UX 11,23 PA RISC
  • From: Steve Ellcey <sje@xxxxxxxxxx>
• Re: Building a Gcc cross-compiler for a new system (init not working)
  • From: "Thomas Epperson" <epperson@xxxxxxxxxxxxxxxxxx>
• relocatable code and object files and shared libraries
  • From: "ranjith kumar" <ranjithproxy@xxxxxxxxx>
• Re: cygwin : gcc-3.2 make problem
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Fwd: Building a Gcc cross-compiler for a new system (init not working)
  • From: "Thomas Epperson" <epperson@xxxxxxxxxxxxxxxxxx>
• cygwin : gcc-3.2 make problem
  • From: kuldeep singh <kuldeephti@xxxxxxxxx>
• Possibly emutls_destroy() has a problem on HP UX 11,23 PA RISC
  • From: wllsp <wllsp@xxxxxxxxx>
• Re: Help with extended asm syntax and related topics
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Help with extended asm syntax and related topics
  • From: Kai Henningsen <kai.extern@xxxxxxxxxxxxxx>
• Re: question. type long long
  • From: Tim Prince <TimothyPrince@xxxxxxxxxxxxx>
• question. type long long
  • From: Александр Струняшев <alexxander19@xxxxxxxxx>
• Re: Building a Gcc cross-compiler for a new system (init not working)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Building a Gcc cross-compiler for a new system (init not working)
  • From: "Thomas Epperson" <epperson@xxxxxxxxxxxxxxxxxx>
• Help with extended asm syntax and related topics
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Help disabling GNU extensions in output of the C preprocessor
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Help disabling GNU extensions in output of the C preprocessor
  • From: "Jose Miguel de la Rosa Trevin" <delarosatrevin@xxxxxxxxx>
• Re: Absurd declarations, and how gcc deals with them.
  • From: Eljay Love-Jensen <eljay@xxxxxxxxx>
• Re: Absurd declarations, and how gcc deals with them.
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Re: Absurd declarations, and how gcc deals with them.
  • From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxx>
• Re: Absurd declarations, and how gcc deals with them.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Absurd declarations, and how gcc deals with them.
  • From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxx>
• Re: Follow up on __cyg_ ... functions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help with malloc
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• RE: Help with malloc
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Re: Help with malloc
  • From: Eljay Love-Jensen <eljay@xxxxxxxxx>
• Re: Help with malloc
  • From: "Andrew Bell" <andrew.bell.ia@xxxxxxxxx>
• Help with malloc
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Frank Mehnert <fm3@xxxxxxxxxxxxxxxxxxxx>
• why doesnt this compile!?
  • From: Coderx20 <Master.huricane@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Building a debuggable cc1plus.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: assert customization
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Follow up on __cyg_ ... functions
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Richard Harvey Chapman <hchapman@xxxxxxxx>
• Re: Follow up on __cyg_ ... functions
  • From: Bill Mahoney <bmahoney@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Richard Harvey Chapman <hchapman-gcc-help@xxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Jens Kilian <jens.kilian@xxxxxxxxxx>
• Re: gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Frank Mehnert <fm3@xxxxxxxxxxxxxxxxxxxx>
• Re: Follow up on __cyg_ ... functions
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building GCC without an assembler
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Follow up on __cyg_ ... functions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• gcc
  • From: "Jair Santos" <jsantos4567@xxxxxxx>
• Building GCC without an assembler
  • From: Gobaan_Raveendran@xxxxxxxx
• Follow up on __cyg_ ... functions
  • From: Bill Mahoney <bmahoney@xxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: John Breitenbach <breiten@xxxxxxxxxxx>
• Re: help with c++ namespace visibility rules problem
  • From: me22 <me22.ca@xxxxxxxxx>
• help with c++ namespace visibility rules problem
  • From: David Mansfield <david@xxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Win32 and symbols left over from linking to GMP 4.2.4
  • From: "bruce.axtens" <bruce.axtens@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Richard Harvey Chapman <hchapman-gcc-help@xxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: setting pointer width
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• setting pointer width
  • From: "Shah Harshit" <harshit@xxxxxxxxxxxxxxxxxxxx>
• Re: Any way to locally apply no-strict-alias?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Any way to locally apply no-strict-alias?
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Frank Mehnert <fm3@xxxxxxxxxxxxxxxxxxxx>
• Re: building gcc-4.4 with graphite
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• building gcc-4.4 with graphite
  • From: Olivier Marsden <Olivier.Marsden@xxxxxxxxxx>
• RE: gcc not properly installed - cannot find libraries
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• RE: gcc not properly installed - cannot find libraries
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• RE: gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: gcc not properly installed - cannot find libraries
  • From: "Austin, Alex" <Alex.Austin@xxxxxxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• Re: gcc not properly installed - cannot find libraries
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Assistance locating runtime library function
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Building a debuggable cc1plus.
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• gcc not properly installed - cannot find libraries
  • From: FlaDude1 <steves@xxxxxxxxxxxxxx>
• Assistance locating runtime library function
  • From: Bill Mahoney <bmahoney@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Richard Harvey Chapman <hchapman-gcc-help@xxxxxxxx>
• Re: Building GCC 4.3.2 fails
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: How to force all functions to have full prologs and epilogs in optimized code?
  • From: Yuri <yuri@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: 'do {} while (0)' replacement
  • From: Christoph Bartoschek <bartoschek@xxxxxx>
• 'do {} while (0)' replacement
  • From: Frank Mehnert <fm3@xxxxxxxxxxxxxxxxxxxx>
• Re: How to force all functions to have full prologs and epilogs in optimized code?
  • From: John Breitenbach <breiten@xxxxxxxxxxx>
• Re: How to force all functions to have full prologs and epilogs in optimized code?
  • From: Yuri <yuri@xxxxxxxxx>
• Building a debuggable cc1plus.
  • From: "Simon Hill" <yacwroy@xxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Arturs Zoldners <az@xxxxxxx>
• Re: How to force all functions to have full prologs and epilogs in optimized code?
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• How to force all functions to have full prologs and epilogs in optimized code?
  • From: Yuri <yuri@xxxxxxxxx>
• assert customization
  • From: jchristof <jchristofmartin@xxxxxxxxx>
• Re: -O1 single optimization parameter
  • From: Andrew Haley <aph@xxxxxxxxxx>
• -O1 single optimization parameter
  • From: "massimiliano cialdi" <cialdi@xxxxxxxxx>
• Re: Runtime issue
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Re: Runtime issue
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: Runtime issue
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Runtime issue
  • From: Baurzhan Ismagulov <ibr@xxxxxxxxxxx>
• Runtime issue
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• libstdc++ parallel mode fill
  • From: "Kay-Michael Wuerzner" <wuerzner@xxxxxxxxx>
• Re: "relocation truncated to fit: R_MIPS_26 " with gcc 4.1.2 toolchain
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: jackfrost <jackfrost@xxxxxxx>
• "relocation truncated to fit: R_MIPS_26 " with gcc 4.1.2 toolchain
  • From: dbadhani <dbadhani@xxxxxxxxx>
• Re: memcpy question
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: memcpy question
  • From: Michael.Schmidt@xxxxxxxxxx
• memcpy question
  • From: Michael.Schmidt@xxxxxxxxxx
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Michael Meissner <meissner@xxxxxxxxxxxxxxxxxx>
• Re: checking for suffix of object files failed when build gcc4.3.2 in ubuntu
  • From: "simon Ye" <kuangye19840410@xxxxxxxxx>
• Re: checking for suffix of object files failed when build gcc4.3.2 in ubuntu
  • From: Eus <eus@xxxxxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building GCC 4.3.2 fails
  • From: Andrew Haley <aph@xxxxxxxxxx>
• AIX gcc help
  • From: "Vardhan, Sundara (GE Infra, Energy)" <sundara.vardhan@xxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Jari Kuusisto <jari.h.kuusisto@xxxxxxxxx>
• Re: Building GCC 4.3.2 fails
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Building GCC 4.3.2 fails
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Jari Kuusisto <jari.h.kuusisto@xxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: jackfrost <jackfrost@xxxxxxx>
• Building GCC 4.3.2 fails
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Jari Kuusisto <jari.h.kuusisto@xxxxxxxxx>
• Re: GCC 3.4.5 (C++ Standards)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Force consecutive operation when using asm volatile macro
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• GCC 3.4.5 (C++ Standards)
  • From: Bradford Fisher <fisher.127@xxxxxxxxxx>
• Re: How to disable exceptions with g++
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• How to disable exceptions with g++
  • From: "Angel Tsankov" <fn42551@xxxxxxxxxxxxxxxx>
• Force consecutive operation when using asm volatile macro
  • From: Jari Kuusisto <jari.h.kuusisto@xxxxxxxxx>
• Re: Performance problem
  • From: Christoph Bartoschek <bartoschek@xxxxxx>
• Re: -mno-align-long-strings and -fformat-extensions
  • From: Unga <unga888@xxxxxxxxx>
• checking for suffix of object files failed when build gcc4.3.2 in ubuntu
  • From: "simon Ye" <kuangye19840410@xxxxxxxxx>
• RE: failed to link for 64 bit application in solaris10
  • From: Jay <jay.krell@xxxxxxxxxxx>
• Re: GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• GCC is 7 times slower than Intel? How to optimize? Need help!!
  • From: jackfrost <jackfrost@xxxxxxx>
• Re: link order
  • From: "Tom Browder" <tom.browder@xxxxxxxxx>
• link order
  • From: matiw <matiwater@xxxxxxxxx>
• gcc 4.2.3 and reference parameters
  • From: "Devin Dawson" <mrhanky7@xxxxxxxxx>
• -mno-align-long-strings and -fformat-extensions
  • From: Unga <unga888@xxxxxxxxx>
• Re: compiling large functions
  • From: Martin Wiebusch <martin.wiebusch@xxxxxxx>
• Re: compiling large functions
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• compiling large functions
  • From: Martin Wiebusch <martin.wiebusch@xxxxxxx>
• getting error while compiling with gcc version 4.1.2 (error: no matching function for call)
  • From: "Murtuja Bharmal" <bharmal.murtuja@xxxxxxxxx>
• Re: How to add a new option to gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Regarding machine modes
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Guide to add new architecture in gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problems with Cortex, floating point and multilib
  • From: "Øyvind Harboe" <oyvind.harboe@xxxxxxxxx>
• Re: Guide to add new architecture in gcc
  • From: "Rohit Garg" <rpg.314@xxxxxxxxx>
• RE: How to add a new option to gcc
  • From: "ORC_developer" <heguojin@xxxxxxxxx>
• Re: How to add a new option to gcc
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• How to add a new option to gcc
  • From: "ORC_developer" <heguojin@xxxxxxxxx>
• Re: Is reading from std::vector thread safe?
  • From: me22 <me22.ca@xxxxxxxxx>
• Is reading from std::vector thread safe?
  • From: "Chris Hamons" <chris.hamons@xxxxxxxxx>
• FW: [gnu.org #379891] failed to link for 64 bit application in solaris 10
  • From: "Jack Rong" <jack.rong@xxxxxxxxxxxxx>
• Linking error when compile a test application with gnet
  • From: "ying lcs" <yinglcs@xxxxxxxxx>
• Regarding machine modes
  • From: "Sivaprasad.pv" <sivaprasad.pv@xxxxxxxxxxxxxxxxxx>
• Guide to add new architecture in gcc
  • From: kwkhoo <wei@xxxxxxxxxx>
• RE: Configure and make only CC1 ??
  • From: "duongtu" <duongtu@xxxxxxxxx>
• Re: Configure and make only CC1 ??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Configure and make only CC1 ??
  • From: Tu <duongtu@xxxxxxxxx>
• Determining floating point ABI on ARM
  • From: Michael Starzinger <michi@xxxxxxxxxxxxxxxxxxxxx>
• Re: Stack checking option for ARM
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Configure and make only CC1 ??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Burt Bicksler <bbicksler@xxxxxxxxxxxxxxxx>
• Stack checking option for ARM
  • From: "Bruce Sutherland" <bruce.sutherland@xxxxxxxxxxxxxxxxxxxx>
• Configure and make only CC1 ??
  • From: "duongtu" <duongtu@xxxxxxxxx>
• Re: how is strcmp implemented so efficiently?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: unrecognized call_value instruction
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Memory initialization (not)
  • From: Duane Ellis <duane-gcc-help@xxxxxxxxxxxxxx>
• re: Different object code generated each time file is compiled
  • From: Duane Ellis <duane-gcc-help@xxxxxxxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: how is strcmp implemented so efficiently?
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Burt Bicksler <bbicksler@xxxxxxxxxxxxxxxx>
• how is strcmp implemented so efficiently?
  • From: Reza Roboubi <reza@xxxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Burt Bicksler <bbicksler@xxxxxxxxxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: Different object code generated each time file is compiled
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: Different object code generated each time file is compiled
  • From: Kai Henningsen <kai.extern@xxxxxxxxxxxxxx>
• Different object code generated each time file is compiled
  • From: Burt Bicksler <bbicksler@xxxxxxxxxxxxxxxx>
• Re: Memory initialization (not)
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: Memory initialization (not)
  • From: Eljay Love-Jensen <eljay@xxxxxxxxx>
• Re: Memory initialization (not)
  • From: Jim Dougherty <j_dougherty@xxxxxxxx>
• Re: Memory initialization (not)
  • From: John Fine <johnsfine@xxxxxxxxxxx>