GCC Help

• Thread Index

• Re: Math Performance(exp)
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Math Performance(exp)
  • From: "Blankenship, David" <David.Blankenship@xxxxxxxxxxxxxx>
• RE: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Alexandre Beaugy" <beaugy.ext@xxxxxxxxxxxxxxxxx>
• Re: Is strongly-typed programming conceivable for C code using gcc ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• RE: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Alexandre Beaugy" <beaugy.ext@xxxxxxxxxxxxxxxxx>
• Re: configure error on gmp and mpfr
  • From: NightStrike <nightstrike@xxxxxxxxx>
• amq not found
  • From: "Maldonado-Salgado, Jose (Space Technology)" <jose.maldonado-salgado@xxxxxxx>
• Re: GCC, How do I show what the default include path is.
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: a question about macro __GNUC__
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC, How do I show what the default include path is.
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• Re: Is strongly-typed programming conceivable for C code using gcc ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• RE: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Alexandre Beaugy" <beaugy.ext@xxxxxxxxxxxxxxxxx>
• Re: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• a question about macro __GNUC__
  • From: "Lu Fan" <carboy.lu@xxxxxxxxx>
• Re: Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• Is strongly-typed programming conceivable for C code using gcc ?
  • From: "Alexandre Beaugy" <beaugy.ext@xxxxxxxxxxxxxxxxx>
• Re: configure error on gmp and mpfr
  • From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxx>
• Re: configure error on gmp and mpfr
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: GCC, How do I show what the default include path is.
  • From: G-Mail <pelle2004@xxxxxxxxx>
• Re: GCC, How do I show what the default include path is.
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• GCC, How do I show what the default include path is.
  • From: G-Mail <pelle2004@xxxxxxxxx>
• configure error on gmp and mpfr
  • From: "qin zhao" <redmuts@xxxxxxxxx>
• Re: gcc: installation problem, cannot exec `cc1': No such file or directory
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: How to make asm constraints for member variables?
  • From: gcchelp.5.adept@xxxxxxx
• Re: differentiating between tree node and phi node
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Re: Specifying cross-compile flags for newlib
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Two quick C++ performace inquiries
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• RE: Specifying cross-compile flags for newlib
  • From: "Robert Cragie" <rcc@xxxxxxxxxx>
• Re: Two quick C++ performace inquiries
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Specifying cross-compile flags for newlib
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Specifying cross-compile flags for newlib
  • From: "Robert Cragie" <rcc@xxxxxxxxxx>
• Re: How to make asm constraints for member variables?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Coding conventions -- command line option vs command-line option
  • From: Robert Kiesling <kiesling@xxxxxxxxxxxxx>
• Re: Coding conventions -- command line option vs command-line option
  • From: Robert Kiesling <kiesling@xxxxxxxxxxxxx>
• How to make asm constraints for member variables?
  • From: Christian Schüler <gcchelp.5.adept@xxxxxxx>
• Re: differentiating between tree node and phi node
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Behaviour of -msse -march=athlon
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Question On Endianness And Solaris Sparc Versus IA32 File Systems
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• differentiating between tree node and phi node
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Behaviour of -msse -march=athlon
  • From: Ryan Hill <dirtyepic@xxxxxxxxxx>
• Question On Endianness And Solaris Sparc Versus IA32 File Systems
  • From: Thomas Dineen <tdineen@xxxxxxxxxxxxx>
• Re: help with including modified libc functions
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• help with including modified libc functions
  • From: verbal <rastageorge@xxxxxxxxx>
• Help in Installing GCC4.2.1 on Solaris server
  • From: Hua Jie Lee <h.lee2@xxxxxxxxxxxxxxxxxxxx>
• 4.2.1 installation on x86_64_unkown-linux-gnu: a test failed [no such instruction: 'cmpxchg16b ld(%rip)']
  • From: Soohong Peter Kim <spkim@xxxxxxxxxxxxxx>
• Problem installing gcc-4.2.1 on Solaris 8
  • From: Garey Mills <gmills@xxxxxxxxxxxxxxxxxxxx>
• Re: can gcc warn about this ambiguous function call in a '?:'?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• RE: Options for PowerPC and to run with vxWorks
  • From: "Rupert Wood" <me@xxxxxxxxx>
• Options for PowerPC and to run with vxWorks
  • From: "Maldonado-Salgado, Jose (Space Technology)" <jose.maldonado-salgado@xxxxxxx>
• Re: gcc: installation problem, cannot exec `cc1': No such file or directory
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc: installation problem, cannot exec `cc1': No such file or directory
  • From: "Ernest L. Williams Jr." <ernesto@xxxxxxxxxxxxxxxxx>
• can gcc warn about this ambiguous function call in a '?:'?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: gcc: installation problem, cannot exec `cc1': No such file or directory
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: malloc, new with cross-compiler gcc 2.95.3 on ARM9
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: C++ compiler cannot create executables
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: Help in installing GCC 4.2.0!
  • From: leehj <leehj@xxxxxxxxxxxxxxxxxxx>
• C++ compiler cannot create executables
  • From: "IVAN ANGELOV" <ivangotoy@xxxxxxxxx>
• Re: Who have already used the new GCC option "-fvisibility=hidden" in Mingw+Msys?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Help building GCC
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Help building GCC
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• RE: Help building GCC
  • From: "Maldonado-Salgado, Jose (Space Technology)" <jose.maldonado-salgado@xxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• RE: Help building GCC
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: Help building GCC
  • From: "Maldonado-Salgado, Jose (Space Technology)" <jose.maldonado-salgado@xxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• gcc: installation problem, cannot exec `cc1': No such file or directory
  • From: "Ernest L. Williams Jr." <ernesto@xxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• malloc, new with cross-compiler gcc 2.95.3 on ARM9
  • From: "Peter Skvarka" <ps@xxxxxxxxxxxxxxxxx>
• Re: I need a help for SimpleScalar
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• RE: Who have already used the new GCC option "-fvisibility=hidden" in Mingw+Msys?
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• Re: Who have already used the new GCC option "-fvisibility=hidden" in Mingw+Msys?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Who have already used the new GCC option "-fvisibility=hidden" in Mingw+Msys?
  • From: Perty Cay <perty_cay@xxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• RE: Can new operator return NULL ?
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Can new operator return NULL ?
  • From: "Peter Skvarka" <ps@xxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• I need a help for SimpleScalar
  • From: naghmeh.karimi@xxxxxxxx
• I need a help for SimpleScalar
  • From: naghmeh.karimi@xxxxxxxx
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Cross Compiling for Cocoa Libraries x86 Linux
  • From: Leo Przybylski <przybyls@xxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: __sync_lock_test_and_set on ARM
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• __sync_lock_test_and_set on ARM
  • From: "Phil Endecott" <spam_from_gcc_help_2@xxxxxxxxxxxx>
• Re: GCC not calling __main()?
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: Question on applicability of --with-gnu-*
  • From: NightStrike <nightstrike@xxxxxxxxx>
• GCC not calling __main()?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Re: AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: ericbambach1@xxxxxxxxxxxx
• Re: AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: ericbambach1@xxxxxxxxxxxx
• Re: AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: ericbambach1@xxxxxxxxxxxx
• Re: AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Question about gcc include-fixed directory
  • From: "Liu Yu-B13201" <B13201@xxxxxxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: "Clemens Eisserer" <linuxhippy@xxxxxxxxx>
• AIX 5.3 GCC 4.2.1 libstdc++ Linker Problems
  • From: ericbambach1@xxxxxxxxxxxx
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Thomas Unterthiner <thomas_unterthiner@xxxxxx>
• Re: ISO C90 Compiler Where to get it from ?
  • From: sonatabar bar <sonatabar@xxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: Sunil Amitkumar Janki <devel.sjanki@xxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: "Clemens Eisserer" <linuxhippy@xxxxxxxxx>
• Re: Howto compile gcc-3.3.6 with gcc-4.1?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Howto compile gcc-3.3.6 with gcc-4.1?
  • From: "Clemens Eisserer" <linuxhippy@xxxxxxxxx>
• Re: Help in installing GCC 4.2.0!
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• Re: question aboue ARM code generation?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: question aboue ARM code generation?
  • From: "阎淼" <yanmiaobest@xxxxxxxxx>
• Help in installing GCC 4.2.0!
  • From: Hua Jie Lee <h.lee2@xxxxxxxxxxxxxxxxxxxx>
• Re: question aboue ARM code generation?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• question aboue ARM code generation?
  • From: "阎淼" <yanmiaobest@xxxxxxxxx>
• inttypes.h
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• RE: Problem with using "pEdge==NULL"
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Sunil Amitkumar Janki <devel.sjanki@xxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Problem with using "pEdge==NULL"
  • From: Erik <sigra@xxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Sunil Amitkumar Janki <devel.sjanki@xxxxxxxxx>
• Re: Build GCC 4.1.2 with ECJ 1.4
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Build GCC 4.1.2 with ECJ 1.4
  • From: Sunil Amitkumar Janki <devel.sjanki@xxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Thomas Unterthiner <thomas_unterthiner@xxxxxx>
• Re: pthread_create/gcc/gcc-libc bug?
  • From: Juan Carlos Franzoy <jfranzoy@xxxxxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Thomas Unterthiner <thomas_unterthiner@xxxxxx>
• Re: gcc for different architectures
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• gcov and libtool
  • From: Tobias Kräntzer <misc@xxxxxxxxxxxxxxxxxxx>
• cinttypes.h
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• gfortran fails with ICE on x86_64-pc-mingw32
  • From: NightStrike <nightstrike@xxxxxxxxx>
• gcc for different architectures
  • From: Soner "Sevinç" <sevinchess@xxxxxxxxx>
• Re: Problems using Vector Extensions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Problems using Vector Extensions
  • From: Thomas Unterthiner <thomas_unterthiner@xxxxxx>
• Re: ISO C90 Compiler Where to get it from ?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: ISO C90 Compiler Where to get it from ?
  • From: sonatabar bar <sonatabar@xxxxxxxxx>
• Re: ISO C90 Compiler Where to get it from ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: ISO C90 Compiler Where to get it from ?
  • From: Ted Byers <r.ted.byers@xxxxxxxxxx>
• ISO C90 Compiler Where to get it from ?
  • From: sonatabar bar <sonatabar@xxxxxxxxx>
• Re: libgomp.so CentOS - shared object cannot be dlopen()ed
  • From: residentmoron <resident.moron@xxxxxxxxx>
• Question on applicability of --with-gnu-*
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: building gcc fails on target=x86_64-pc-mingw32
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: building gcc fails on target=x86_64-pc-mingw32
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: building gcc fails on target=x86_64-pc-mingw32
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: libgomp.so CentOS - shared object cannot be dlopen()ed
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: building gcc fails on target=x86_64-pc-mingw32
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• libgomp.so CentOS - shared object cannot be dlopen()ed
  • From: residentmoron <resident.moron@xxxxxxxxx>
• building gcc fails on target=x86_64-pc-mingw32
  • From: NightStrike <nightstrike@xxxxxxxxx>
• problems building gcc v4.2.1
  • From: Jeffrey Holle <jeffreyholle@xxxxxxxxxxxxx>
• syntax errors in gcc-4.2.1's stdarg.h
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Is malloc allocating memory on the virtual memory space ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• RE: Is malloc allocating memory on the virtual memory space ?
  • From: "Guerra-Salcedo, Cesar M" <cesar.guerra-salcedo@xxxxxxxx>
• Re: Is malloc allocating memory on the virtual memory space ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Is malloc allocating memory on the virtual memory space ?
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Is malloc allocating memory on the virtual memory space ?
  • From: "Guerra-Salcedo, Cesar M" <cesar.guerra-salcedo@xxxxxxxx>
• Re: Compiling after f2c
  • From: Omar Gutiérrez Arenas <tardebut@xxxxxxxx>
• Re: syntax errors in gcc-4.2.1's stdarg.h
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• syntax errors in gcc-4.2.1's stdarg.h
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Precompile Headers. What is Best Practice?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compiling after f2c
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Precompile Headers. What is Best Practice?
  • From: John Carter <john.carter@xxxxxxxxxx>
• pthread_create/gcc/gcc-libc bug?
  • From: Juan Carlos Franzoy <jfranzoy@xxxxxxxxxxxx>
• Compiling after f2c
  • From: Omar Gutiérrez Arenas <tardebut@xxxxxxxx>
• pthread_create/gcc/gcc-libc bug?
  • From: "Juan Carlos Franzoy" <jfranzoy@xxxxxxxxx>
• Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: how to make use of more memory on HP-UX when comiling with gcc
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Kernel miscompile with -march=c3
  • From: Mark Hindley <mark@xxxxxxxxxxxxxx>
• Problem with using "pEdge==NULL"
  • From: Jeffrey Holle <jeffreyholle@xxxxxxxxxxxxx>
• Re: loading multiple C++ runtimes but not mixing ABIs?
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Basic question: Is binutils required for bootstrap stage 1 C compiler build?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Re: loading multiple C++ runtimes but not mixing ABIs?
  • From: Ken Raeburn <raeburn@xxxxxxxxxxx>
• gcc version
  • From: Erik Leunissen <e.leunissen@xxxxxxxxx>
• Re: loading multiple C++ runtimes but not mixing ABIs?
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• how to make use of more memory on HP-UX when comiling with gcc
  • From: "Guerra-Salcedo, Cesar M" <cesar.guerra-salcedo@xxxxxxxx>
• Does g++ have a intel/msdn __COUNTER__ macro equivalent??
  • From: me <mgbg25171@xxxxxxxxxxxxxxxx>
• Re: .p2align
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: Assembly symbol generation
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Assembly symbol generation
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: gcc 64-bit (assembly) information
  • From: Mihai Donțu <mdontu@xxxxxxxxxxxxxxx>
• Re: Assembly symbol generation
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• gcc 64-bit (assembly) information
  • From: Katana Steel <webmaster@xxxxxxxxx>
• Assembly symbol generation
  • From: Katana Steel <webmaster@xxxxxxxxx>
• Adding another language after configure .. make ... install
  • From: "Peter Chegwidden" <peter@xxxxxxxxxxxxxxx>
• Re: Fine tuning gcc build to machine specific properties
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Fine tuning gcc build to machine specific properties
  • From: Ted Byers <r.ted.byers@xxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• removing a statement from SSA representation
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: SPARC64 64-bit tool chain
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: SPARC64 64-bit tool chain
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Fine tuning gcc build to machine specific properties
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Fine tuning gcc build to machine specific properties
  • From: Ted Byers <r.ted.byers@xxxxxxxxxx>
• Re: How to remove the option -Qy to as
  • From: Andrea Marongiu <marongiu_andrea@xxxxxxxx>
• SPARC64 64-bit tool chain
  • From: Sunil Amitkumar Janki <devel.sjanki@xxxxxxxxx>
• RFC: GCC should warn when evaluating a pointer return type from a function used in a conditional that performs arithmetic with it
  • From: "Darryl L. Miles" <darryl-mailinglists@xxxxxxxxxxxx>
• Re: loading multiple C++ runtimes but not mixing ABIs?
  • From: Ken Raeburn <raeburn@xxxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>
• Re: loading multiple C++ runtimes but not mixing ABIs?
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Re: building something with nanotime
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: building something with nanotime
  • From: "Jim Stapleton" <stapleton.41@xxxxxxxxx>
• loading multiple C++ runtimes but not mixing ABIs?
  • From: Ken Raeburn <raeburn@xxxxxxxxxxx>
• Re: building something with nanotime
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Anyone knows how to
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Anyone knows how to "undergrade" gcc ?? -- non expert user
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• building something with nanotime
  • From: "Jim Stapleton" <stapleton.41@xxxxxxxxx>
• Re: Problem building stage 1 ARM C compiler
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Problem building stage 1 ARM C compiler
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Anyone knows how to "undergrade" gcc ?? -- non expert user
  • From: "D'arito" <espasapalau@xxxxxxxxx>
• glitchy dmg installer
  • From: Stephen Judd <judd@xxxxxxxxxxxxxxxxxx>
• __CLASS__
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: How to remove the option -Qy to as
  • From: Jim Wilson <wilson@xxxxxxxxxxxx>
• Specifying the location/behavior of the stack?
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• Re: How to remove the option -Qy to as
  • From: Pedro Alves <pedro_alves@xxxxxxxxxxxxxxx>
• cross compiler MinGW->PowerPC
  • From: "Lippold, Roland" <Roland.Lippold@xxxxxxxxxxxxx>
• problems building gcc3.2 on suse 10.1
  • From: Paul Gayle <ldnblk@xxxxxxxxxxx>
• Re: Inline assembly and local variable storage
  • From: Subu Krishnamoorthy <subu@xxxxxxxxxx>
• Re: GCC - Preserving statement expression results on stack
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: Inline assembly and local variable storage
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Average number of instructions per line of kernel code
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Average number of instructions per line of kernel code
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• Re: Can something similar to &x=&y be accomplished in C
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: How to remove the option -Qy to as
  • From: Brian Sidebotham <micros@xxxxxxxxxxx>
• How to remove the option -Qy to as
  • From: Andrea Marongiu <marongiu_andrea@xxxxxxxx>
• Re: GCC - Preserving statement expression results on stack
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Linker question
  • From: "Borut Kastelic" <borut.kastelic@xxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Inline assembly and local variable storage
  • From: Subu Krishnamoorthy <subu@xxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help with -march and -mcpu issues
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Help with -march and -mcpu issues
  • From: Rick Mann <rmann@xxxxxxxxxxxxxxx>
• GCC - Preserving statement expression results on stack
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Can something similar to &x=&y be accomplished in C
  • From: "Jim Stapleton" <stapleton.41@xxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Solution sought to GCC 4.1.1 backtrace problem
  • From: David Daney <ddaney@xxxxxxxxxx>
• Solution sought to GCC 4.1.1 backtrace problem
  • From: Blair Barnett <blairbarnett@xxxxxxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: Mac OS X cross compile for i386-elf
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Local disable of specific warnings for a section of code
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Local disable of specific warnings for a section of code
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Can something similar to &x=&y be accomplished in C
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: Can something similar to &x=&y be accomplished in C
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Can something similar to &x=&y be accomplished in C
  • From: "Jim Stapleton" <stapleton.41@xxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: can gcc compile from memory buffer?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: "Adam Olsen" <rhamph@xxxxxxxxx>
• GNAT/GCC 4.2 build problem on FreeBSD-CURRENT
  • From: Karel Miklav <karel.miklav@xxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: can gcc compile from memory buffer?
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Local disable of specific warnings for a section of code
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• can gcc compile from memory buffer?
  • From: "jonatan perry" <jonatan44@xxxxxxxxx>
• Mac OS X cross compile for i386-elf
  • From: "Ben Abernathy" <ben.abernathy@xxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: "Adam Olsen" <rhamph@xxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: "Adam Olsen" <rhamph@xxxxxxxxx>
• Re: stdint.h
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: call stack's order of parameters
  • From: Andre Kirchner <supercroc1974@xxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: "Adam Olsen" <rhamph@xxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: SUSv3's "memory location" and threads
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: how to code global indirect branches ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help about calculation of 'S' notation for a relocatable ELF execute for MIPS arch
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• SUSv3's "memory location" and threads
  • From: "Adam Olsen" <rhamph@xxxxxxxxx>
• Re: set of statements using a variable
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• how to code global indirect branches ?
  • From: "Jiayuan" <jerrygonair@xxxxxxxxxxx>
• Help about calculation of 'S' notation for a relocatable ELF execute for MIPS arch
  • From: "PRC" <panruochen@xxxxxxxxx>
• Re: recasting an error to a warning?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• movaps missaligment in threads
  • From: solo_the_chaos2 <solo_the_chaos@xxxxx>
• Re: call stack's order of parameters
  • From: Andre Kirchner <supercroc1974@xxxxxxxxx>
• call stack's order of parameters
  • From: Andre Kirchner <supercroc1974@xxxxxxxxx>
• Re: char y = 469;
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: char y = 469;
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Re: -fno-stack-protector not ensuring binary compatibility
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: char y = 469;
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• -fno-stack-protector not ensuring binary compatibility
  • From: Pádraig Brady <P@xxxxxxxxxxxxxx>
• Re: char y = 469;
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Re: char y = 469;
  • From: "Richard Li" <richardpku@xxxxxxxxx>
• Re: char y = 469;
  • From: stf_polska <stf_polska@xxxxx>
• Re: char y = 469;
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: char y = 469;
  • From: "Diego Novillo" <dnovillo@xxxxxxxxxx>
• Re: char y = 469;
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: char y = 469;
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: char y = 469;
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: GCC asm block optimizations on x86_64
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• GCC asm block optimizations on x86_64
  • From: "Darryl L. Miles" <darryl-mailinglists@xxxxxxxxxxxx>
• Re: Building gmp and mpfr within gcc
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Building gmp and mpfr within gcc
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• .p2align
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: compile errors from gcc
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: compile errors from gcc
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Building gmp and mpfr within gcc
  • From: NightStrike <nightstrike@xxxxxxxxx>
• compile errors from gcc
  • From: D Macean <donaldo@xxxxxx>
• Re: Finding the address of a symbol in a release build
  • From: "Peter Waller" <peter.waller@xxxxxxxxx>
• Re: Building gmp and mpfr within gcc
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Building gmp and mpfr within gcc
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Finding the address of a symbol in a release build
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• char y = 469;
  • From: stf_polska <stf_polska@xxxxx>
• Re: Simple Question on CPU specific Optimization Options
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Finding the address of a symbol in a release build
  • From: "Peter Waller" <peter.waller@xxxxxxxxx>
• Re: gcc can not distinguish the same file or same class with the different module or library
  • From: "summer xia" <xiaguangt@xxxxxxxxx>
• Re: Simple Question on CPU specific Optimization Options
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Warning using sprintf("%llu", uint64_t) on AMD64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Simple Question on CPU specific Optimization Options
  • From: "Hofman, Gertjan (BI35)" <Gertjan.Hofman@xxxxxxxxxxxxx>
• Re: Warning using sprintf("%llu", uint64_t) on AMD64
  • From: tabris <tabris@xxxxxxxxxx>
• Re: No way to cleanup at thread exit for __thread variables?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxx>
• Re: C - Pass by reference to pointers
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• Re: C - Pass by reference to pointers
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• C - Pass by reference to pointers
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• Re: Warning using sprintf("%llu", uint64_t) on AMD64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Warning using sprintf("%llu", uint64_t) on AMD64
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• Warning using sprintf("%llu", uint64_t) on AMD64
  • From: tabris <tabris@xxxxxxxxxx>
• Re: building 4.2.1 from 3.4.6 on NetBSD/amd64 3.1
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• Re: No way to cleanup at thread exit for __thread variables?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: removing a statement
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Wrong list, please ignore this thread!
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: building 4.2.1 from 3.4.6 on NetBSD/amd64 3.1
  • From: Chris Jones <chris@xxxxxxxxxx>
• CMAKE_MODULE_PATH not remembered?
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: removing a statement
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• removing a statement
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• building 4.2.1 from 3.4.6 on NetBSD/amd64 3.1
  • From: Chris Jones <chris@xxxxxxxxxx>
• No way to cleanup at thread exit for __thread variables?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxx>
• is 'app' reserved?
  • From: Yan Seiner <yan@xxxxxxxxxx>
• File Not found error
  • From: Donald R Laster Jr <don_sfw@xxxxxxxxxxx>
• Re: Two errors creating a converter between two types
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Two errors creating a converter between two types
  • From: tirengarfio <tirengarfio@xxxxxxxxxxx>
• Re: Help with gfortran
  • From: "Asher Langton" <langton2@xxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help with gfortran
  • From: Tim Prince <tprince@xxxxxxxxxxxx>
• Re: gcc can not distinguish the same file or same class with the different module or library
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Help with gfortran
  • From: Sébastien Le Roux <leroux@xxxxxxxxxxxxxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Tom Bachmann <e_mc_h2@xxxxxx>
• is there a general linux development mailing list?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• stdint.h
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Tom Bachmann <e_mc_h2@xxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc can not distinguish the same file or same class with the different module or library
  • From: "summer xia" <xiaguangt@xxxxxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Bad option: -march=native on gcc 4.2.1?
  • From: Matt Fago <fago@xxxxxxxxxxxxx>
• Re: Bad option: -march=native on gcc 4.2.1?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Bad option: -march=native on gcc 4.2.1?
  • From: Matt Fago <fago@xxxxxxxxxxxxx>
• Re: pragma-like warning turn off ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: how to compile enum as signed independent of enum value range?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Error when I try to run bootstrap in an open source problem on RedHat 4
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: error no such file or directory B
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: recasting an error to a warning?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Adding dependencies to shared objects
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Bad option: -march=native on gcc 4.2.1?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc - Automatic library searching
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: set of statements using a variable
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Re: set of statements using a variable
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: set of statements using a variable
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• set of statements using a variable
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• gcc 4.2.1 on Niagara (UltraSPARC T1): output uses UltraSPARC3 Extensions?
  • From: Irwin Tillman <irwin@xxxxxxxxxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• Re: Maintaining multiple stacks
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Maintaining multiple stacks
  • From: Tom Bachmann <e_mc_h2@xxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: "Richard Li" <richardpku@xxxxxxxxx>
• Re: Is gcc a complete universal (not bound to any OS) c compiler?
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Is gcc a complete universal (not bound to any OS) c compiler?
  • From: Shawn Cyberpunk <samika@xxxxxxxxxxxxxx>
• Re: gcc can not distinguish the same file or same class with the different module or library
  • From: "summer xia" <xiaguangt@xxxxxxxxx>
• Re: Problem building cross compiler
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Problem building cross compiler
  • From: Dave Williss <dwilliss@xxxxxxxxxxxxxxx>
• VMX128 AltiVec variant support?
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Re: gcc can not distinguish the same file or same class with the different module or library
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: GCC cpp to mips! Help Please!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• GCC cpp to mips! Help Please!
  • From: "Derrick Washington" <derrick_chi@xxxxxxx>
• pragma-like warning turn off ?
  • From: "Sunzir Deepur" <sunzird@xxxxxxxxx>
• Re: how to compile library files
  • From: "Sisyphus" <sisyphus1@xxxxxxxxxxxxxxx>
• how to compile library files
  • From: bjamali@xxxxxxxx
• Re: Basic install problem.
  • From: Andreas Tobler <toa@xxxxxxxxxxx>
• Re: Basic install problem.
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Basic install problem.
  • From: "Robert Jones" <robertgbjones@xxxxxxxxx>
• Re: Adding dependencies to shared objects
  • From: Christoph Bartoschek <bartoschek@xxxxxx>
• Re: Adding dependencies to shared objects
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Adding dependencies to shared objects
  • From: Christoph Bartoschek <bartoschek@xxxxxx>
• Re: trunk fails to bootstrap under Linux
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• RE: Template Inheritance Bug ?
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Template Inheritance Bug ?
  • From: Kalugsky Uriy <urik@xxxxxxxxxxxxx>
• trunk fails to bootstrap under Linux
  • From: Philippe Schaffnit <P.Schaffnit@xxxxxxxxxxxxxxxxxxxxx>
• Re: high level loop optimizations in gcc-4.1.2
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• Bad option: -march=native on gcc 4.2.1?
  • From: Matt Fago <fago@xxxxxxxxxxxxx>
• Error when I try to run bootstrap in an open source problem on RedHat 4
  • From: "ying lcs" <yinglcs@xxxxxxxxx>
• Re: GCC 4.1.2 / glibc Pthreads requires macro defined to get 'standard' functionality
  • From: "Eddy [the Obsessed] Cullen" <eddy@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: gcc compile error. Can't find a .h file
  • From: "ying lcs" <yinglcs@xxxxxxxxx>
• Re: gcc compile error. Can't find a .h file
  • From: Sergei Organov <osv@xxxxxxxxx>
• gcc compile error. Can't find a .h file
  • From: "ying lcs" <yinglcs@xxxxxxxxx>
• RE: GCC 4.1.2 / glibc Pthreads requires macro defined to get 'standard' functionality
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Help about 'addend' of The ELF specification
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• gcc - Automatic library searching
  • From: "Sampei02" <sampei02@xxxxxxxxxx>
• high level loop optimizations in gcc-4.1.2
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Same trouble on 4.2.1 build as 4.2.0??
  • From: "Paul Paskvan" <Paul.Paskvan@xxxxxxxxxxxxx>
• Re: GCC 4.1.2 / glibc Pthreads requires macro defined to get 'standard' functionality
  • From: "Eddy [the Obsessed] Cullen" <eddy@xxxxxxxxxxxxxxxxxxxxxxx>
• recasting an error to a warning?
  • From: Mark Winstead <mwinstead@xxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: Dorit Nuzman <DORIT@xxxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Re: Is -ftree-vectorize enabled by default at any -On?
  • From: Dorit Nuzman <DORIT@xxxxxxxxxx>
• error no such file or directory B
  • From: siretb <siretb@xxxxxxx>
• Re: Is -ftree-vectorize enabled by default at any -On?
  • From: Ira Rosen <IRAR@xxxxxxxxxx>
• Re: question - optimization and const
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: GCC 4.1.2 / glibc Pthreads requires macro defined to get 'standard' functionality
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: question - optimization and const
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• Re: Problems building 4.2.1 cross compiler for ppc-eabi
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• Re: Segmentation fault when trying to call a function locating in .data section
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Segmentation fault when trying to call a function locating in .data section
  • From: "PRC" <panruochen@xxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: Dorit Nuzman <DORIT@xxxxxxxxxx>
• Re: Problems building 4.2.1 cross compiler for ppc-eabi
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• GCC 4.1.2 / glibc Pthreads requires macro defined to get 'standard' functionality
  • From: "Eddy [the Obsessed] Cullen" <eddy@xxxxxxxxxxxxxxxxxxxxxxx>
• Problem building libada
  • From: JonY <10walls@xxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Re: Help about 'addend' of The ELF specification
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Helping out the Vectorizer
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• Help about 'addend' of The ELF specification
  • From: "PRC" <panruochen@xxxxxxxxx>
• Helping out the Vectorizer
  • From: Gordan Bobic <gordan@xxxxxxxxxx>
• Re: help building gcc-4.2.1 with GMP and MPFR updates
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Link error involving DSO
  • From: VunderBob <robert.w.hostetler@xxxxxxxx>
• question - optimization and const
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• how to compile enum as signed independent of enum value range?
  • From: "Michael Brand" <michael.brand@xxxxxxxxxxxxxxxx>
• Problems building 4.2.1 cross compiler for ppc-eabi
  • From: Dirk Heinrichs <dirk.heinrichs.ext@xxxxxxx>
• mipsel-linux-gcc:the alignment of segment is 64k,it's too big!
  • From: "qinghua fan" <fanqh0820@xxxxxxxxx>
• Re: gcc inline asm
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• processes memory consumption
  • From: "Manal Helal" <manalorama@xxxxxxxxx>
• Re: help building gcc-4.2.1 with GMP and MPFR updates
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• help building gcc-4.2.1 with GMP and MPFR updates
  • From: Warren L Dodge <warrend@xxxxxxxxxxxxxxxxxx>
• Re: -finline-limit
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• compiling gcc4.2.1 failure
  • From: "jiaqi zhang" <zation.busy@xxxxxxxxx>
• Re: -finline-limit
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: How to force libtool to use g++ to create shared library
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• In this case, bzip2 will decline to write compressed output to a terminal, as this would be entirely incomprehensible and therefore pointless.
  • From: "Linoy Manikad" <Linoy.Manikad@xxxxxxxxxxxxxxxxx>
• Re: Error when building GCC from source tar (version 4.1.2)
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Error when building GCC from source tar (version 4.1.2)
  • From: "Paul Hartman" <paul_hartman@xxxxxxxxxxx>
• Re: gcc and initialization
  • From: "Ph. Marek" <philipp@xxxxxxxxxxxxx>
• Re: gcc and initialization
  • From: Steve Kreyer <steve.kreyer@xxxxxx>
• Re: compiling gcc4.2.1 failure
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: compiling gcc4.2.1 failure
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• gcc and initialization
  • From: "Ph. Marek" <philipp@xxxxxxxxxxxxx>
• gcc inline asm
  • From: Rokas Masiulis <roma1390@xxxxxxxxxxxxxxx>
• Re: How do I create/initialize a large class static (const?) array?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• How do I create/initialize a large class static (const?) array?
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• compiling gcc4.2.1 failure
  • From: "jiaqi zhang" <zation.busy@xxxxxxxxx>
• Re: about ignoring "#pragma weak symbol"
  • From: Erik Leunissen <e.leunissen@xxxxxxxxx>
• about ignoring "#pragma weak symbol"
  • From: Erik Leunissen <e.leunissen@xxxxxxxxx>
• Re: Are Class static methods inlined / inlinable?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Is -ftree-vectorize enabled by default at any -On?
  • From: "Zuxy Meng" <zuxy.meng@xxxxxxxxx>
• -finline-limit
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• Re: new gcc compiler for pdp10 architecture
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• How to force libtool to use g++ to create shared library
  • From: "Chandrasekaran R" <chandrasekaran.r@xxxxxxxxxxxxxx>
• Are Class static methods inlined / inlinable?
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: help please with simple one!
  • From: "Raghu Vadapalli" <raghuv119@xxxxxxxxx>
• multiple arch
  • From: Mohsen Pahlevanzadeh <mohsen@xxxxxxxxxxxxxxxxx>
• Re: new gcc compiler for pdp10 architecture
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: help please with simple one!
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• help please with simple one!
  • From: "Raghu Vadapalli" <raghuv119@xxxxxxxxx>
• new gcc compiler for pdp10 architecture
  • From: Martin Chaney <chaney@xxxxxxx>
• Re: how to display gcc header file search path?
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Re: Newbie question: I cant declare an object with a constructor made by myself.
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• how to display gcc header file search path?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Newbie question: I cant declare an object with a constructor made by myself.
  • From: tirengarfio <tirengarfio@xxxxxxxxxxx>
• RE: Regarding suitable ld(linker) for gcc 4.1.2 64 bit for HP UX PA-RISC
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• RE: yacc Error when building GCC from source tar (version 4.1.2)
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• RE: FREE touble
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• RE: Linking into objects using C++
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Linking into objects using C++
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Linking into objects using C++
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: FREE touble
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Where I can download recent version of 64 bit ld (linker tool) for gcc 4.1.2 -HP UX PA-RISC
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• FREE touble
  • From: johny@xxxxxxxxxxxxxx
• Regarding suitable ld(linker) for gcc 4.1.2 64 bit for HP UX PA-RISC
  • From: "Chandrasekaran R" <chandrasekaran.r@xxxxxxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Where I can download recent version of 64 bit ld (linker tool) for gcc 4.1.2 -HP UX PA-RISC
  • From: "Chandrasekaran R" <chandrasekaran.r@xxxxxxxxxxxxxx>
• Re: keep getting "undefined reference to" linker error
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• keep getting "undefined reference to" linker error
  • From: "H.S." <hs.samix@xxxxxxxxx>
• Re: yacc Error when building GCC from source tar (version 4.1.2)
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• yacc Error when building GCC from source tar (version 4.1.2)
  • From: "Paul Hartman" <paul_hartman@xxxxxxxxxxx>
• Re: Newbie question: classes "A" and "B". A "B" object declared inside class "A"
  • From: Holger Blasum <hbl@xxxxxxxxx>
• Newbie question: classes "A" and "B". A "B" object declared inside class "A"
  • From: tirengarfio <tirengarfio@xxxxxxxxxxx>
• Re: mips gcc -O1: Address exception error on store doubleword
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: stack pointer instructions in subroutine
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: Newbie compiling -> "undefined reference to" error
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: stack pointer instructions in subroutine
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• stack pointer instructions in subroutine
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• RE: Newbie compiling -> "undefined reference to" error
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Newbie compiling -> "undefined reference to" error
  • From: tirengarfio <tirengarfio@xxxxxxxxxxx>
• Re: Can't get a performance boots when using openmp/gomp
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: Can't get a performance boots when using openmp/gomp
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• RE: Help needed in debugging the program
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Build failure under Linux
  • From: Philippe Schaffnit <P.Schaffnit@xxxxxxxxxxxxxxxxxxxxx>
• Re: Build failure under Linux
  • From: Pranav Bhandarkar <pranav.bhandarkar@xxxxxxxxxxxx>
• Re: Can't get a performance boots when using openmp/gomp
  • From: Ruud Schramp <spam2@xxxxxxxxxxx>
• Re: Can't get a performance boots when using openmp/gomp
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Build failure under Linux
  • From: Philippe Schaffnit <P.Schaffnit@xxxxxxxxxxxxxxxxxxxxx>
• Help needed in debugging the program
  • From: "Chandrasekaran R" <chandrasekaran.r@xxxxxxxxxxxxxx>
• Can't get a performance boots when using openmp/gomp
  • From: Ruud Schramp <spam2@xxxxxxxxxxx>
• Run time problem incatching exception from a shared library
  • From: "syam prasad" <nagabhairu.syam@xxxxxxxxx>
• Run time problem incatching exception from a shared library
  • From: "Chandrasekaran R" <chandrasekaran.r@xxxxxxxxxxxxxx>
• Re: alignment warning
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: rope in libstdc++
  • From: Joe Buck <Joe.Buck@xxxxxxxxxxxx>
• Re: rope in libstdc++
  • From: "Jonathan Wakely" <jwakely.gcc@xxxxxxxxx>
• Re: rope in libstdc++
  • From: Joe Buck <Joe.Buck@xxxxxxxxxxxx>
• rope in libstdc++
  • From: "Brendan Miller" <catphive@xxxxxxxxxxxx>
• Re: alignment warning
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: alignment warning
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• forcing link against a dll on win32 cygwin
  • From: Mathieu Lacage <mathieu.lacage@xxxxxxxxxxxxxxx>
• Re: alignment warning
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: alignment warning
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• RE: alignment warning
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: alignment warning
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Errors occur when trying to build a cross gcc with host=cygwin, target=mips-elf and build=linux
  • From: "PRC" <panruochen@xxxxxxxxx>
• Re: alignment warning
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• alignment warning
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: -mlong-calls seems unvailable on mips-elf-gcc 3.4.0
  • From: David Daney <ddaney@xxxxxxxxxx>
• -mlong-calls seems unvailable on mips-elf-gcc 3.4.0
  • From: "PRC" <panruochen@xxxxxxxxx>
• Re: Problem in building DLL : cannot find -luser32
  • From: "syam prasad" <nagabhairu.syam@xxxxxxxxx>
• Re: Compililation Of GCC-4.3.0 via SVN
  • From: STEVE555 <stevenward666@xxxxxxxxxxx>
• Re: Compililation Of GCC-4.3.0 via SVN
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compililation Of GCC-4.3.0 via SVN
  • From: STEVE555 <stevenward666@xxxxxxxxxxx>
• Re: Problem in building DLL : cannot find -luser32
  • From: jim marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Re: FREE touble
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• Re: FREE touble
  • From: "Lijuan Hai" <hailijuan@xxxxxxxxx>
• FREE touble
  • From: johny@xxxxxxxxxxxxxx
• Re: Compiler options for PowerPC
  • From: Jakob Lechner <jakob.lechner@xxxxxxxxxxxxxxxxxxxx>
• Re: -Bgroup?
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Re: Compiling GCC using existing binutils
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compiling GCC using existing binutils
  • From: Brendon Costa <brendon@xxxxxxxxxxxxx>
• Re: Compiler options for PowerPC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Compiler options for PowerPC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compiling GCC using existing binutils
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: flag to disable -Wextra check for unsigned compared to 0
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: About the prefetch
  • From: Jakob Lechner <jakob.lechner@xxxxxxxxxxxxxxxxxxxx>
• RE: flag to disable -Wextra check for unsigned compared to 0
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: About the prefetch
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• About the prefetch
  • From: Yang_Jialin@xxxxxxx
• Re: Compiler options for PowerPC
  • From: Jakob Lechner <jakob.lechner@xxxxxxxxxxxxxxxxxxxx>
• Re: SSA names
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• SSA names
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Compililation Of GCC-4.3.0 via SVN
  • From: STEVE WARD <stevenward666@xxxxxxxxxxx>
• Compiling GCC using existing binutils
  • From: Brendon Costa <brendon@xxxxxxxxxxxxx>
• flag to disable -Wextra check for unsigned compared to 0
  • From: Ethan Tira-Thompson <ejt@xxxxxxxxxxxxxx>
• Re: gcc-help Digest 17 Jul 2007 16:12:44 -0000 Issue 2448
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Need help building Ada in gcc 4.2.1 on Fedore 6
  • From: David Gressett <jdgressett@xxxxxxxxxxxxxxx>
• Re: Antwort: Re: C statements in assembler listing
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Antwort: Re: C statements in assembler listing
  • From: gunnar.piel@xxxxxxx
• Re: C statements in assembler listing
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• C statements in assembler listing
  • From: gunnar.piel@xxxxxxx
• Re: Compiling GCC-4.3.0 via SVN
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Compiling GCC-4.3.0 via SVN
  • From: STEVE WARD <stevenward666@xxxxxxxxxxx>
• Re: Problem in building DLL : cannot find -luser32
  • From: "syam prasad" <nagabhairu.syam@xxxxxxxxx>
• Re: invalid pointer error
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Choosing the right TLS access model
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Re: invalid pointer error
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: invalid pointer error
  • From: "Mohamed Shafi" <shafitvm@xxxxxxxxx>
• Re: invalid pointer error
  • From: Anitha Boyapati <anithab@xxxxxxxxxxx>
• invalid pointer error
  • From: "Mohamed Shafi" <shafitvm@xxxxxxxxx>
• Re: hidden symbol __dso_handle reference: link error, lost attachments
  • From: Gary Hughes-Fenchel <ghughesf@xxxxxxxxx>
• Re: hidden symbol __dso_handle reference: link error
  • From: Gary Hughes-Fenchel <ghughesf@xxxxxxxxx>
• Re: Choosing the right TLS access model
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem in building DLL : cannot find -luser32
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Re: Disabling call graph optimizations
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Choosing the right TLS access model
  • From: ludo@xxxxxxx (Ludovic Courtès)
• Re: Disabling call graph optimizations
  • From: "Sunzir Deepur" <sunzird@xxxxxxxxx>
• Re: Mixing code compiled with different optimization levels
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Mixing code compiled with different optimization levels
  • From: Saikiran Madugula <hummerbliss@xxxxxxxxx>
• Re: x86 Intrinsics in GCC 4.2 (_mm_slli_epi32)
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Why is "uint64_t bits = reinterpret_cast<uint64_t>(1.5);" invalid?
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: x86 Intrinsics in GCC 4.2 (_mm_slli_epi32)
  • From: "Mike Lewis" <mikelikespie@xxxxxxxxx>
• Re: x86 Intrinsics in GCC 4.2 (_mm_slli_epi32)
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• x86 Intrinsics in GCC 4.2 (_mm_slli_epi32)
  • From: "Mike Lewis" <mikelikespie@xxxxxxxxx>
• Re: Disabling call graph optimizations
  • From: Diego Novillo <dnovillo@xxxxxxxxxx>
• Disabling call graph optimizations
  • From: JTXX <jtxx000@xxxxxxxxxxx>
• Problem in building DLL : cannot find -luser32
  • From: "syam prasad" <nagabhairu.syam@xxxxxxxxx>
• RE: Robust detection of endianness at compile time.
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Miles Bader <miles@xxxxxxx>
• RE: Robust detection of endianness at compile time.
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Why do I get: cannot declare variable 'sc' to be of abstract type...
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Why do I get: cannot declare variable ? sc¹ to be of abstract type...
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Why do I get: cannot declare variable ‘sc’ to be of abstract type...
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Compiler options for PowerPC
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Compiler options for PowerPC
  • From: Jakob Lechner <jakob.lechner@xxxxxxxxxxxxxxxxxxxx>
• RE: Robust detection of endianness at compile time.
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: How to change CR/LF to LF when compile gcc-4.1.2 in Mingw32 in Windows XP
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• How to change CR/LF to LF when compile gcc-4.1.2 in Mingw32 in Windows XP
  • From: haibin zhang <dragzhb@xxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Dean Anderson <dean@xxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: -Bgroup?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: operator new[] and operator delete[]
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: operator new[] and operator delete[]
  • From: "Wesley Smith" <wesley.hoke@xxxxxxxxx>
• RE: operator new[] and operator delete[]
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• operator new[] and operator delete[]
  • From: "Wesley Smith" <wesley.hoke@xxxxxxxxx>
• Why am I seeing these warnings from system header files?
  • From: "Kevin Regan" <k.regan@xxxxxx>
• -Bgroup?
  • From: Henry <dimensiondude.oss@xxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: cr5-6 registers on i386
  • From: Clemens Kolbitsch <clemens.kol@xxxxxx>
• Re: GCC-3.3.6 and MIPS instruction "EHB"
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC-3.3.6 and MIPS instruction "EHB"
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Robust detection of endianness at compile time.
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: cr5-6 registers on i386
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: configure warning - test: too many arguments
  • From: Brian Sidebotham <micros@xxxxxxxxxxx>
• GCC-3.3.6 and MIPS instruction "EHB"
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• cr5-6 registers on i386
  • From: Clemens Kolbitsch <clemens.kol@xxxxxx>