GCC Help

• Thread Index

• Re: powerpc-ibm-aix5.2.0.0 bootstrap failure
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Finding the amount of free memory (Was: Optimize causes an error.)
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Where is docs for typeid(x).name()?
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: shared object, inline members and backward compatibility
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: powerpc-ibm-aix5.2.0.0 bootstrap failure
  • From: Steve Edwards <edwardss@xxxxxxxxx>
• shared object, inline members and backward compatibility
  • From: jfranzoy <jfranzoy@xxxxxxxxxxxx>
• Re: Optimize causes an error.
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: powerpc-ibm-aix5.2.0.0 bootstrap failure
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Optimize causes an error.
  • From: LWATCDR <lwatcdr@xxxxxxxxx>
• Re: cannot figure out how to use gcj of the gcc
  • From: hill0093 <hill0093@xxxxxxx>
• Re: cannot figure out how to use gcj of the gcc
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: cannot figure out how to use gcj of the gcc
  • From: hill0093 <hill0093@xxxxxxx>
• Re: Optimize causes an error.
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Debug problem
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Dependency output path question
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• powerpc-ibm-aix5.2.0.0 bootstrap failure
  • From: Steve Edwards <edwardss@xxxxxxxxx>
• Re: Optimize causes an error.
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Cross gcc build problem
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• RE: Debug problem
  • From: "Arora Yogesh-a22623" <yogesh.arora@xxxxxxxxxxxx>
• Re: Cross gcc build problem
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: best size of a c module
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Dependency output path question
  • From: Michael Morrell <mrm94040@xxxxxxxxx>
• Re: best size of a c module
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help with gcc - compile option to list/report modules included in compiled program
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: Optimize causes an error.
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Optimize causes an error.
  • From: LWATCDR <lwatcdr@xxxxxxxxx>
• Re: Cross gcc build problem
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Cross gcc build problem
  • From: Laine Walker-Avina <lwalkera@xxxxxxxx>
• Re: best size of a c module
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• best size of a c module
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Help with gcc - compile option to list/report modules included in compiled program
  • From: "Jeffrey Thorson" <Jeffrey.Thorson@xxxxxxxxxxxxx>
• Re: how to change the default path from /usr/include for gcc using CFLAGS
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Debug problem
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• how to change the default path from /usr/include for gcc using CFLAGS
  • From: "Koyel Mukherjee" <koyelmjee@xxxxxxxxx>
• Re: Debug problem
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: --Help
  • From: Lionel B <lionelb.nospam@xxxxxxxxx>
• --Help
  • From: Lifu Liu <lifuliu@xxxxxxxxx>
• RE: Debug problem
  • From: "Arora Yogesh-a22623" <yogesh.arora@xxxxxxxxxxxx>
• Re: Debug problem
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Constant singleton object initialization
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help about mipsel-linux-gcc 4.1.2 asm codes.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Debug problem
  • From: "Arora Yogesh-a22623" <yogesh.arora@xxxxxxxxxxxx>
• Re: Is -O9 legitimate?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• RE: WELCOME to gcc-help@xxxxxxxxxxx
  • From: "Arora Yogesh-a22623" <yogesh.arora@xxxxxxxxxxxx>
• malformed object, illegal reference
  • From: Jann Röder <roederja@xxxxxxxxxxxxxxx>
• Constant singleton object initialization
  • From: Helge Bahmann <hcb@xxxxxxxxxxxxxxx>
• Re: Cross gcc build problem
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Help about mipsel-linux-gcc 4.1.2 asm codes.
  • From: "Sync ma" <sync.jma@xxxxxxxxx>
• Re: c++ global object space
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Is -O9 legitimate?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• c++ global object space
  • From: "Kevin Yohe" <kevin@xxxxxxxxxx>
• calling c++ from fortran
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• Cross compiler for iPhone
  • From: Charles Miller <cmiller@xxxxxxxxxxxxxxxxxxxxxx>
• Is -O9 legitimate?
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• segmentation fault in main() when -fstack-check
  • From: "gregry ." <gregry_7@xxxxxxxxx>
• Re: Cross gcc build problem
  • From: Laine Walker-Avina <lwalkera@xxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: Assign pointers of different objects to the same pointer
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• unaligned stores
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Automatically initialize all global variables/arrays in GCC.
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• Re: Build error: xgcc: java/parse-scan.c: No such file or directory
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• Re: Cross gcc build problem
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: sebastian <sebastian.bw@xxxxxxxxxx>
• newbie question
  • From: "Leonardo Santagostini" <lsantagostini@xxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• Build error: xgcc: java/parse-scan.c: No such file or directory
  • From: Martin Berger <maca.berger@xxxxxxxxxx>
• Re: Automatically initialize all global variables/arrays in GCC.
  • From: "Kevin Hung" <cykhung@xxxxxxxxx>
• Cross gcc build problem
  • From: Laine Walker-Avina <lwalkera@xxxxxxxx>
• Re: Automatically initialize all global variables/arrays in GCC.
  • From: "Michael Meissner" <michael.meissner@xxxxxxx>
• Re: liveness analysis with stack slots
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• C++ in embedded systems
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Maurizio Vitale <mav@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: sebastian <sebastian.bw@xxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: sebastian <sebastian.bw@xxxxxxxxxx>
• Re: liveness analysis with stack slots
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• liveness analysis with stack slots
  • From: Maurizio Vitale <mav@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: me22 <me22.ca@xxxxxxxxx>
• RE: Assign pointers of different objects to the same pointer
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• Re: Assign pointers of different objects to the same pointer
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Assign pointers of different objects to the same pointer
  • From: sebastian <sebastian.bw@xxxxxxxxxx>
• Default INCLUDE and LIBRARY DIRECTORY PATHS for gcc
  • From: "Digvijoy Chatterjee" <chatterjee.digvijoy@xxxxxxxxx>
• Automatically initialize all global variables/arrays in GCC.
  • From: "Kevin Hung" <cykhung@xxxxxxxxx>
• missing "std::move"
  • From: fafa <fafa@xxxxxxxxxxx>
• sh crashed during make
  • From: NightStrike <nightstrike@xxxxxxxxx>
• RE: G++ and excemtion
  • From: Laurent Marzullo <laurent@xxxxxxxxx>
• RE: G++ and excemtion
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: difference between aligned and unaligned acceses
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• G++ and excemtion
  • From: Laurent Marzullo <laurent@xxxxxxxxx>
• Re: from tree to rtl
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• How do you force link time symbol resolution to a particular library on linux g++
  • From: "Sudha Iyer" <sudha.k.iyer@xxxxxxxxx>
• Re: version of gcc
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• version of gcc
  • From: "BEGIN Thibault (GFI)" <AT.GFI.BEGIN@xxxxxxxxxxxxxxx>
• Re: Right C FLAGS for my processor
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Right C FLAGS for my processor
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: Right C FLAGS for my processor
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Right C FLAGS for my processor
  • From: Roberto Guida <roberto.guida@xxxxxxxxxx>
• difference between aligned and unaligned acceses
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• from tree to rtl
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Probleme with G++, shared library and exception
  • From: Laurent Marzullo <laurent@xxxxxxxxx>
• Re: How to give avr-gcc the ability to understand binary (eg. b00010110)
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: gcc-4.1.1: ssp (stack smashing protector) for aix ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• Re: gcc-4.1.1: ssp (stack smashing protector) for aix ?
  • From: David Edelsohn <dje@xxxxxxxxxxxxxx>
• Re: GCC problems with Altivec / PowerPC
  • From: David Edelsohn <dje@xxxxxxxxxxxxxx>
• Re: printing rtx variable
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Vectorization in gcc 4.1.1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: How to give avr-gcc the ability to understand binary (eg. b00010110)
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• How to give avr-gcc the ability to understand binary (eg. b00010110)
  • From: lynx.abraxas@xxxxxxxxxx
• Re: cannot figure out how to use gcj of the gcc
  • From: David Daney <ddaney@xxxxxxxxxx>
• cannot figure out how to use gcj of the gcc
  • From: hill0093 <hill0093@xxxxxxx>
• printing rtx variable
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: for loop: different results on cygwin and on linux
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Vectorization in gcc 4.1.1
  • From: Ramesh.Kadambi@xxxxxxx
• for loop: different results on cygwin and on linux
  • From: "Lemaitre Laurent-r29173" <Laurent.Lemaitre@xxxxxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: "Phil Endecott" <spam_from_gcc_help@xxxxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: installed, compiled, how to link?
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: "Phil Endecott" <spam_from_gcc_help@xxxxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: "Phil Endecott" <spam_from_gcc_help@xxxxxxxxxxxx>
• Re: Can I force a word read-modify-write instread of a byte write?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: gcc and lcc
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• gcc and lcc
  • From: Muzahid Hossain <saadi@xxxxxxxxx>
• Can I force a word read-modify-write instread of a byte write?
  • From: "Phil Endecott" <spam_from_gcc_help@xxxxxxxxxxxx>
• Re: Is fastcall broken?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: fpa glibc-2.2.5 for a native armv4l toolchain [resolved]
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• RE: installed, compiled, how to link?
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: gcc assembler
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: fpa glibc-2.2.5 for a native armv4l toolchain [resolved]
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• RE: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• RE: c++ template instanciation and dlls on win32
  • From: Danny Smith <dannysmith@xxxxxxxxxxxx>
• RE: installed, compiled, how to link?
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• RE: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: fpa glibc-2.2.5 for a native armv4l toolchain
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• movdqa and movdqu
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• RE: installed, compiled, how to link?
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: fpa glibc-2.2.5 for a native armv4l toolchain
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: gcc binaries for Solaris 2.5
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• re: c++ template instanciation and dlls on win32
  • From: Mathieu Lacage <Mathieu.Lacage@xxxxxxxxxxxxxxx>
• re: c++ template instanciation and dlls on win32
  • From: Danny Smith <dannysmith@xxxxxxxxxxxx>
• gcc assembler
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• fpa glibc-2.2.5 for a native armv4l toolchain
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: linking internal executible functions: "undefined reference to" ???
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: installed, compiled, how to link?
  • From: David Daney <ddaney@xxxxxxxxxx>
• installed, compiled, how to link?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: Is fastcall broken?
  • From: Danny Smith <dannysmith@xxxxxxxxxxxx>
• c++ template instanciation and dlls on win32
  • From: Mathieu Lacage <Mathieu.Lacage@xxxxxxxxxxxxxxx>
• linking internal executible functions: "undefined reference to" ???
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: Is fastcall broken?
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• RE: Is fastcall broken?
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Is fastcall broken?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Is fastcall broken?
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• internal compiler error: Segmentation fault
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• RE: Are java executables standalone?
  • From: hill0093 <hill0093@xxxxxxx>
• RE: Are java executables standalone?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• gcc binaries for Solaris 2.5
  • From: "Ken Hickey" <khickey@xxxxxxxxxxxxxxxxx>
• RE: Are java executables standalone?
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• RE: Are java executables standalone?
  • From: hill0093 <hill0093@xxxxxxx>
• RE: Are java executables standalone?
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Are java executables standalone?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: Are java executables standalone?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Is fastcall broken?
  • From: Angus <angus@xxxxxxxxxx>
• Are java executables standalone?
  • From: hill0093 <hill0093@xxxxxxx>
• Re: Building only C++ libraries
  • From: Michael Helmich <aixrepairman@xxxxxxxx>
• Bootstrap problem on powerpc-ibm-aix5.1.0.0
  • From: Steve Edwards <edwardss@xxxxxxxxx>
• Re: Is fastcall broken?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Problem loading GCC 4.0 libraries into Java app
  • From: Zoltan Foley-Fisher <zoltan@xxxxxxxxx>
• Re: template function inlining in g++ version < 4.0
  • From: Stephan Tolksdorf <andorxor@xxxxxx>
• Bi-Architecture build problem on Opteron
  • From: Michael Heissmeier <michael63@xxxxxxx>
• Is fastcall broken?
  • From: Angus <angus@xxxxxxxxxx>
• gcc-4.1.1: ssp (stack smashing protector) for aix ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• template function inlining in g++ version < 4.0
  • From: Stephan Tolksdorf <andorxor@xxxxxx>
• Re: can i cross compile glibc then copy it to the host(target) for use ?
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: -fPIC and shared object
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• -fPIC and shared object
  • From: "Olivier Delannoy" <olivier.delannoy@xxxxxxxxx>
• Re: can i cross compile glibc then copy it to the host(target) for use ?
  • From: David Daney <ddaney@xxxxxxxxxx>
• can i cross compile glibc then copy it to the host(target) for use ?
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Precompiled headers making for some odd trouble...
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: any companies provide services for building gcc on different platforms?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: varargs
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Similarities between gcc and binutils
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Similarities between gcc and binutils
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Similarities between gcc and binutils
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Tracking down a difference in test_results for 4.3.0-20070622
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: autovectorization and aligned access
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Building only C++ libraries
  • From: David Daney <ddaney@xxxxxxxxxx>
• autovectorization and aligned access
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: any companies provide services for building gcc on different platforms?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: How to use GCC testsuite..?
  • From: Tehila Meyzels <TEHILA@xxxxxxxxxx>
• Re: How to use GCC testsuite..?
  • From: Saurabh Verma <saurabh.verma@xxxxxxxxxx>
• Re: Building only C++ libraries
  • From: Michael Helmich <aixrepairman@xxxxxxxx>
• Re: c++ const aggregate vs constructor
  • From: Xiaolong Tang <txltamu@xxxxxxxxx>
• Re: How to use GCC testsuite..?
  • From: Tehila Meyzels <TEHILA@xxxxxxxxxx>
• any companies provide services for building gcc on different platforms?
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Solaris 64 bit build environment
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Optimizing constructors/destructors for embedded systems
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Question on warnings for compiling gcc from svn source
  • From: David Daney <ddaney@xxxxxxxxxx>
• Solaris 64 bit build environment
  • From: "Manickam, Loganathan \(HCL\)" <lmanickam@xxxxxxxxxxxxxxx>
• Re: option to see the Intermediate repersantation (AST,GIMPLE,RTL)
  • From: "sameer sinha" <sameer0201@xxxxxxxxx>
• Re: order of -L options created by gcc for the linker
  • From: tjevon <tjevon09@xxxxxxxxx>
• Re: Locale problem / debugging libstdc++
  • From: "Jens Berlips" <jens.berlips@xxxxxxxxx>
• Re: Optimizing constructors/destructors for embedded systems
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: c++ const aggregate vs constructor
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: c++ const aggregate vs constructor
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Does GCC assign any type to enums that can be specified in an assignment operator?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: order of -L options created by gcc for the linker
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Building only C++ libraries
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: option to see the Intermediate repersantation (AST,GIMPLE,RTL)
  • From: Ramana Radhakrishnan <ramana.radhakrishnan@xxxxxxxxxxxx>
• Question on warnings for compiling gcc from svn source
  • From: NightStrike <nightstrike@xxxxxxxxx>
• How to use GCC testsuite..?
  • From: "Venkatesan Jeevanandam" <Venkatesan_jeevanandam@xxxxxxxxxxxx>
• option to see the Intermediate repersantation (AST,GIMPLE,RTL)
  • From: "sameer sinha" <sameer0201@xxxxxxxxx>
• c++ const aggregate vs constructor
  • From: "Kevin Yohe" <kevin@xxxxxxxxxx>
• varargs
  • From: Constantine Kousoulos <wuwei@xxxxxxxxxxx>
• Re: relation between gcc/glibc version and linux kernel version??
  • From: Mike Stump <mrs@xxxxxxxxx>
• Re: The (black?) art of inlining...
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Re: Does GCC assign any type to enums that can be specified in an assignment operator?
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: The (black?) art of inlining...
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Optimizing constructors/destructors for embedded systems
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• The (black?) art of inlining...
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• order of -L options created by gcc for the linker
  • From: tjevon <tjevon09@xxxxxxxxx>
• Re: Help compiling 4.3.0
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Help compiling 4.3.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• loop peeling in autovectorization
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Help compiling 4.3.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Building gcc 4.2.0 cross-compiler (host=i386-apple-darwin8.10.1, target=powerpc-apple-darwin7)
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Building gcc 4.2.0 cross-compiler (host=i386-apple-darwin8.10.1, target=powerpc-apple-darwin7)
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: Linking problem gcj and c++
  • From: David Daney <ddaney@xxxxxxxxxx>
• Building gcc 4.2.0 cross-compiler (host=i386-apple-darwin8.10.1, target=powerpc-apple-darwin7)
  • From: William Gallafent <william@xxxxxxxxxx>
• Building only C++ libraries
  • From: Michael Helmich <aixrepairman@xxxxxxxx>
• Re: Optimizing constructors/destructors for embedded systems
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: Error building gcc/g++ 4.1.1 on AIX 5.2
  • From: Michael Helmich <aixrepairman@xxxxxxxx>
• Re: Does GCC assign any type to enums that can be specified in an assignment operator?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Optimizing constructors/destructors for embedded systems
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Can we use GCC testsuite to test other C compilers...?
  • From: "Venkatesan Jeevanandam" <Venkatesan_jeevanandam@xxxxxxxxxxxx>
• Linking problem gcj and c++
  • From: Carsten Rasmussen <carsten.rasmussen@xxxxxxxxxxx>
• Error building gcc/g++ 4.1.1 on AIX 5.2
  • From: Michael Helmich <aixrepairman@xxxxxxxx>
• Optimizing constructors/destructors for embedded systems
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: Help compiling 4.3.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: typedef conflict in GCC and JAVA
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Help compiling 4.3.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Help compiling 4.3.0
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Help compiling 4.3.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Help compiling 4.3.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• RE: Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GCC with __asm__ generic temporary register query
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• GCC with __asm__ generic temporary register query
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• RE: Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• RE: Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Does GCC assign any type to enums that can be specified in an assignment operator?
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: typedef conflict in GCC and JAVA
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Does GCC assign any type to enums that can be specified in an assignment operator?
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: Re: Help compiling gcc 4.2.0
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Macros for function definitions/calls
  • From: "chadwick.b" <chadwick@xxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• RE: typedef conflict in GCC and JAVA
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: typedef conflict in GCC and JAVA
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• RE: typedef conflict in GCC and JAVA
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: typedef conflict in GCC and JAVA
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Re: typedef conflict in GCC and JAVA
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• typedef conflict in GCC and JAVA
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• does gcc 2.95.3 support softfloat ?
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: Help compiling gcc 4.2.0
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Help compiling gcc 4.2.0
  • From: "Lee Rhodes" <lee@xxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: arm-elf make check fixincludes failures
  • From: Brian Sidebotham <micros@xxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Fwd: Locale problem / debugging libstdc++
  • From: "Jens Berlips" <jens.berlips@xxxxxxxxx>
• arm-elf make check fixincludes failures
  • From: Brian Sidebotham <micros@xxxxxxxxxxx>
• reordering of passes
  • From: "P. Pavan Kumar" <pavankumar@xxxxxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Brian Sidebotham <micros@xxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: From what versions of binutils, gcc, and glibc did "--with-sysroot" become available ??
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: From what versions of binutils, gcc, and glibc did "--with-sysroot" become available ??
  • From: David Daney <ddaney@xxxxxxxxxx>
• From what versions of binutils, gcc, and glibc did "--with-sysroot" become available ??
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Ryan Mansfield <rmansfield@xxxxxxx>
• Re: Help configuring gcc
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Help configuring gcc
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Help configuring gcc
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: constructors/destructors compiled twice
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Help configuring gcc
  • From: Luke Dickens <lwd03@xxxxxxxxxxxx>
• constructors/destructors compiled twice
  • From: Kövesdi György <kgy@xxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: ~OT: any proposals to add provision for binary integer values
  • From: Shriramana Sharma <samjnaa@xxxxxxxxx>
• Re: Problem building 4.2.0 on Solaris 10 (SPARC)
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: GCC file timestamp
  • From: Jed Dai <mingdai@xxxxxxx>
• Re: Problem building 4.2.0 on Solaris 10 (SPARC)
  • From: Luke Dalessandro <luked@xxxxxxxxxxxxxxxx>
• Re: Problem building 4.2.0 on Solaris 10 (SPARC)
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Problem building 4.2.0 on Solaris 10 (SPARC)
  • From: Luke Dalessandro <luked@xxxxxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: building/installing GCC and crtx.o's confusion
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• building/installing GCC and crtx.o's confusion
  • From: "michael.a" <wild.eyed.boy.from.freecloud@xxxxxxxxx>
• Re: gcc 2.7.2.3 source code
  • From: "robehe ravanifard" <robehe.rf@xxxxxxxxx>
• Re: Strange memory allocation int a[atoi(argv[1])] ?!
  • From: chimi <gchimi@xxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• mul instruction
  • From: "stefano carucci" <stecarucci@xxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• Re: FW: Help with GDB analyzing assembler code
  • From: Matthew Woehlke <mw_triad@xxxxxxxxxxxxxxxxxxxxx>
• GCC 4.2.0: optimisation appears to break C++ compile/link
  • From: Lionel B <lionelbuk@xxxxxxxxxxx>
• RE: gcc 2.7.2.3 source code
  • From: "Rupert Wood" <me@xxxxxxxxx>
• gcc 2.7.2.3 source code
  • From: "robehe ravanifard" <robehe.rf@xxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: tom peng <tompeng@xxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: tom peng <tompeng@xxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: tom peng <tompeng@xxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Query regarding GFORTRAN rules.
  • From: manish <manishagg22@xxxxxxxxx>
• remove library path from
  • From: Hiroki Kaminaga <kaminaga@xxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: tom peng <tompeng@xxxxxxxxxxxxx>
• Re: Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Size of C/C++ data type from GNU GCC/g++ compiled ELF 64-bit LSB executable, AMD x86-64 vs. ELF 32-bit LSB executable, Intel 80386
  • From: tom peng <tompeng@xxxxxxxxxxxxx>
• Re: Inline Assembly under MIPS
  • From: David Daney <ddaney@xxxxxxxxxx>
• Inline Assembly under MIPS
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• Re: Temporary objects
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Default parameters - problems
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• FW: Help with GDB analyzing assembler code
  • From: "Navarro, Sylvia" <snavarro@xxxxxxxxxx>
• Gcc 2.95.3 error
  • From: "dimitris mavrikis" <jeam25@xxxxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• Re: Building gcc error
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: gcc 4.2.0 build fails on mac os 10.4.9, intel, /usr/bin/libtool: fatal error in ld64
  • From: "dan hitt" <dan.hitt@xxxxxxxxx>
• Re: Building gcc error
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Building gcc error
  • From: "Gabriel E Rovira Palm" <garovira@xxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: <ivan@xxxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: "Alan Carvalho de Assis" <acassis@xxxxxxxxx>
• Re: Re: increasing var twice in a statement
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Re: increasing var twice in a statement
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: jlh <jlh@xxxxxx>
• Re: increasing var twice in a statement
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: Christian Böhme <monodhs@xxxxxx>
• Re: increasing var twice in a statement
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: increasing var twice in a statement
  • From: Chris Wolstenholme <chris@xxxxxxxxxxxxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: Christian Böhme <monodhs@xxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: debian gcc produces hello*
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Fwd: Default parameters - problems
  • From: "anitha boyapati" <anitha.boyapati@xxxxxxxxx>
• Default parameters - problems
  • From: "anitha boyapati" <anitha.boyapati@xxxxxxxxx>
• Re: debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• Re: debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• Re: debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• Re: increasing var twice in a statement
  • From: Willi Mann <willi@xxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: increasing var twice in a statement
  • From: jlh <jlh@xxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• RE: increasing var twice in a statement
  • From: "chris@xxxxxxxxxxxxxxxxxxxx" <chris@xxxxxxxxxxxxxxxxxxxx>
• Re: GCC 4.2 ARM build fails (Link tests are not allowed after GCC_NO_EXECUTABLES)
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• increasing var twice in a statement
  • From: Willi Mann <willi@xxxxxx>
• Re: invalid conversion from const char** to char**
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• Re: invalid conversion from const char** to char**
  • From: me22 <me22.ca@xxxxxxxxx>
• GCC 4.2 ARM build fails (Link tests are not allowed after GCC_NO_EXECUTABLES)
  • From: Sergey Stasishin <stasishin@xxxxxxxxxxxxx>
• GCC 4.2 ARM build fails (Link tests are not allowed after GCC_NO_EXECUTABLES)
  • From: Sergey Stasishin <stasishin@xxxxxxxxxxxxx>
• Re: Building a cross-compiler for powerpc-eabi
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: GCC-provided runtime libraries.
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: GCC-provided runtime libraries.
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Sources of mathematical functions
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Sources of mathematical functions
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Sources of mathematical functions
  • From: Архипов Дмитрий <arkhipov@xxxxxxxxxxxxxx>
• invalid conversion from const char** to char**
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Building a cross-compiler for powerpc-eabi
  • From: Timo Kerstan <timo.kerstan@xxxxxxxxxxxxxxxx>
• Re: GCC-provided runtime libraries.
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• HI problem in MAKE
  • From: "C.NARSIMHA RAJU" <narsimha_raju@xxxxxxxxxxxxxxxxxxx>
• Re: GCC multilib building failure
  • From: Xiaolong Tang <txlzte@xxxxxxxxxxxx>
• Re: GCC-provided runtime libraries.
  • From: Christian Böhme <monodhs@xxxxxx>
• GCC multilib building failure
  • From: Xiaolong Tang <txltamu@xxxxxxxxx>
• Re: GCC-provided runtime libraries.
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• GCC problems with Altivec / PowerPC
  • From: Przemyslaw Iskra <sparky@xxxxxxxxxxxxx>
• Re: debian gcc produces hello*
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• GCC-provided runtime libraries.
  • From: Christian Böhme <monodhs@xxxxxx>
• Re: GCC Assembler Modifiers
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: GCC Assembler Modifiers
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: GCC Assembler Modifiers
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• Re: GCC Assembler Modifiers
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• GCC Assembler Modifiers
  • From: "Mohamed Bamakhrama" <bamakhrama@xxxxxxxxx>
• std::string missing from gcc 4.0?
  • From: Adrian <adrian.down@xxxxxxxxx>
• Re: sizeof( function )
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: "Martin Krischik" <krischik@xxxxxxxxxxxxxxxxxxxxx>
• Re: debian gcc produces hello*
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• Re: debian gcc produces hello*
  • From: <ivan@xxxxxxxxxx>
• Re: debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• Re: debian gcc produces hello*
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• debian gcc produces hello*
  • From: rmodesi <rmodesi@xxxxxxx>
• invoking glibc to thread-safe mode
  • From: "Jiayuan Meng" <jerrygonair@xxxxxxxxxxx>
• Re: ~OT: any proposals to add provision for binary integer values
  • From: "Lawrence Crowl" <crowl@xxxxxxxxxx>
• Re: Building gcc-4.2.0 under IRIX64
  • From: "Hugo R. Hernandez-Mora" <hugo.hernandez@xxxxxxxxxxxxx>
• Re: GCC vs G++
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: ~OT: any proposals to add provision for binary integer values
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• need help with linker error
  • From: Chris Newman <Chris.Newman@xxxxxxxxxxx>
• ~OT: any proposals to add provision for binary integer values
  • From: Shriramana Sharma <samjnaa@xxxxxxxxx>
• Re: dealing with built-in functions
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: dealing with built-in functions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: dealing with built-in functions
  • From: flo@xxxxxxxxx
• Re: dealing with built-in functions
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: STL in G++?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: dealing with built-in functions
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• STL in G++?
  • From: Dean Anderson <dean@xxxxxxx>
• Building 3.2.2 error
  • From: "Gabriel Rovira" <garovira@xxxxxxxxx>
• Fwd: [MPICH] non-blocking sending/receiving an array
  • From: "Manal Helal" <manalorama@xxxxxxxxx>
• Re: GCC vs G++
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: GCC vs G++
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: Building gcc-4.2.0 under IRIX64
  • From: David Daney <ddaney@xxxxxxxxxx>
• Building gcc-4.2.0 under IRIX64
  • From: "Hugo R. Hernandez-Mora" <hugo.hernandez@xxxxxxxxxxxxx>
• dealing with built-in functions
  • From: Florian Gleixner <flo@xxxxxxxxx>
• Re: More on type qualifiers ignored on function return type
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: sizeof( function )
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: More on type qualifiers ignored on function return type
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: sizeof( function )
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• More on type qualifiers ignored on function return type
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: sizeof( function )
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: sizeof( function )
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Modifying prolouge function in gcc
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxxxx>
• sizeof( function )
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: No warning about accidental cast(?)
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxxxx>
• Re: No warning about accidental cast(?)
  • From: Arend-Jan Wijtzes <ajwytzes@xxxxxxxxxxxx>
• Re: No warning about accidental cast(?)
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: jboolean conflict error
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• jboolean conflict error
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• No warning about accidental cast(?)
  • From: Arend-Jan Wijtzes <ajwytzes@xxxxxxxxxxxx>
• Re: Strange memory allocation int a[atoi(argv[1])] ?!
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: "C" beginner help ask:
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• Re: "C" beginner help ask:
  • From: "Wesley Smith" <wesley.hoke@xxxxxxxxx>
• "C" beginner help ask:
  • From: Gordiano <sagrav@xxxxxxxxxxx>
• Re: GCC vs G++
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: GCC vs G++
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Strange memory allocation int a[atoi(argv[1])] ?!
  • From: chimi <gchimi@xxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxxxx>
• Re: gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• gcc 4.1.0 issue, fixed with 4.1.2?
  • From: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxxxx>
• Re: static declaration of foo follows non-static declaration
  • From: Aseem Rastogi <aseem@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: static declaration of foo follows non-static declaration
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: static declaration of foo follows non-static declaration
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• RE: static declaration of foo follows non-static declaration
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Re: static declaration of foo follows non-static declaration
  • From: Aseem Rastogi <aseem@xxxxxxxxxxxxxxxxxxxxxxx>
• static declaration of foo follows non-static declaration
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• GCC vs G++
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Re: Help building gcc with x86-64 support
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Temporary objects
  • From: Aseem Rastogi <aseem@xxxxxxxxxxxxxxxxxxxxxxx>
• RE: Help building gcc with x86-64 support
  • From: "Rupert Wood" <me@xxxxxxxxx>
• Help building gcc with x86-64 support
  • From: Willow Schlanger <wrschlanger@xxxxxxxxx>
• CSV format
  • From: Mohsen Pahlevanzadeh <mohsen@xxxxxxxxxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: Installing GNU G++ compiler on Mac OS
  • From: Alexander Wieder <awieder@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Installing GNU G++ compiler on Mac OS
  • From: Parvathi Kumar <pmalangi@xxxxxxxxx>
• Re: i686-gcc vs i586-Suse Linux
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• printing cfg
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• modifications at gimple level
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• [help] - build a gcc 2.95.3 fpa tool chain from/with a 3.4.5 vfp chain
  • From: Hayden Thring <hjthring@xxxxxxxxxxx>
• Re: Modifying prolouge function in gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Modifying prolouge function in gcc
  • From: Nick Maclaren <nmm1@xxxxxxxxxxxxx>
• Modifying prolouge function in gcc
  • From: SandeepThorat <sathorat2003@xxxxxxxxx>
• Re: gcc_assert
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: where did -minline-all-stringops go?
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: where did -minline-all-stringops go?
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• RE: where did -minline-all-stringops go?
  • From: "Rupert Wood" <me@xxxxxxxxx>
• where did -minline-all-stringops go?
  • From: Jim Marshall <jim.marshall@xxxxxxxxxxxxxxxxx>
• gcc_assert
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Static Functions in Linker Map File -
  • From: "kanishk rastogi" <kanishk.85@xxxxxxxxx>
• Static Functions in Linker Map File -
  • From: "Alok Singh" <aloks@xxxxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: John Carter <john.carter@xxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Building _statically linked_ crosscompiler toolchain.
  • From: David Daney <ddaney@xxxxxxxxxx>
• Building _statically linked_ crosscompiler toolchain.
  • From: John Carter <john.carter@xxxxxxxxxx>
• gfortran compiling error
  • From: "Kurt Meyer" <kwm9866@xxxxxxxxx>
• Re: tricore-gcc port help
  • From: "Kapil Kumar" <kaps2121@xxxxxxxxx>
• Re: need help
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: tricore-gcc port help
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: tricore-gcc port help
  • From: "Kapil Kumar" <kaps2121@xxxxxxxxx>
• need help
  • From: ASHA GOWDA <gowda_asha2k@xxxxxxxxx>
• Re: i686-gcc vs i586-Suse Linux
  • From: "Martin Krischik" <martin@xxxxxxxxxxxx>
• Re: Compiling for Xtensa
  • From: "Praveen Raghavan" <praveen@xxxxxxxxxxxxxx>
• Re: Compiling for Xtensa
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• RE: i686-gcc vs i586-Suse Linux
  • From: "Atwood, Robert C" <r.atwood@xxxxxxxxxxxxxx>
• how to build executable instructions blocks dynamically ?
  • From: "Gorgonite" <gorgonite@xxxxxxxxxxx>
• Re: Compiling for Xtensa
  • From: "Praveen Raghavan" <praveen@xxxxxxxxxxxxxx>
• Re: Compiling for Xtensa
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• scope of a varible in gcc source code
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: GNU gcc 3.4.6 Compile Error on Solaris 10
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: tricore-gcc port help
  • From: "Kapil Kumar" <kaps2121@xxxxxxxxx>
• RE: i686-gcc vs i586-Suse Linux
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• GNU gcc 3.4.6 Compile Error on Solaris 10
  • From: "Bruce Butler" <BButler@xxxxxxxxxxx>
• Re: tricore-gcc port help
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: i686-gcc vs i586-Suse Linux
  • From: "Atwood, Robert C" <r.atwood@xxxxxxxxxxxxxx>
• Re: i686-gcc vs i586-Suse Linux
  • From: "Martin Krischik" <krischik@xxxxxxxxxxxxxxxxxxxxx>
• Re: corresponding option in GCC for -brtl
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• tricore-gcc port help
  • From: "Kapil Kumar" <kaps2121@xxxxxxxxx>
• corresponding option in GCC for -brtl
  • From: <Dhiraj.Nilange@xxxxxxxxxxxxxxxxxx>
• Re: i686-gcc vs i586-Suse Linux
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• i686-gcc vs i586-Suse Linux
  • From: Ахметов Казбек <k_akhmetov@xxxxx>
• Re: Setting up a cross-compile
  • From: Dave Williss <dwilliss@xxxxxxxxxxxxxxx>
• Re: 64 bit library doesn't build using makefile
  • From: "Prasad Athawale" <prasadis@xxxxxxxxx>
• Re: Switch to obtain "narrowing" warnings
  • From: "j t" <mark473@xxxxxxxxx>
• Re: Switch to obtain "narrowing" warnings
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Gcov and thread-safety
  • From: Holger Blasum <hbl@xxxxxxxxx>
• Re: Switch to obtain "narrowing" warnings
  • From: "j t" <mark473@xxxxxxxxx>
• Re: Switch to obtain "narrowing" warnings
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: segmentation fault
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: segmentation fault
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Switch to obtain "narrowing" warnings
  • From: "j t" <mark473@xxxxxxxxx>
• Re: Dynamic section entry in ARM ELF file.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Compiling for Xtensa
  • From: "Praveen Raghavan" <praveen@xxxxxxxxxxxxxx>
• Re: error: gcc_gettext_width
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: error: gcc_gettext_width
  • From: Daniel Wilson <lakeat@xxxxxxx>
• Re: Removing data member from virtual base causes wrong member function to be called
  • From: "Trent Apted" <tapted@xxxxxxxxx>
• Re: 64 bit library doesn't build using makefile
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• 64 bit library doesn't build using makefile
  • From: "Prasad Athawale" <prasadis@xxxxxxxxx>
• Dynamic section entry in ARM ELF file.
  • From: "Rajesh Paul" <rajesh.paul@xxxxxxxxxxxxxx>
• Re: Removing data member from virtual base causes wrong member function to be called
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Removing data member from virtual base causes wrong member function to be called
  • From: "Trent Apted" <tapted@xxxxxxxxx>
• Re: error: gcc_gettext_width
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• error: gcc_gettext_width
  • From: Daniel Wilson <lakeat@xxxxxxx>
• RE: newbe macro preprocessor question
  • From: "John (Eljay) Love-Jensen" <eljay@xxxxxxxxx>
• RE: newbe macro preprocessor question
  • From: "Andrea Partinico" <andrea.partinico@xxxxxxxxx>
• Re: printing "tree" type data
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Converting to 64-bit
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• newbe macro preprocessor question
  • From: "Andrea Partinico" <andrea.partinico@xxxxxxxxx>
• printing "tree" type data
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• How to find function name from function pointer?
  • From: "Gaurav Jain" <gaurav.anywhere@xxxxxxxxx>
• Converting to 64-bit
  • From: arpit jain <dreams_arpit@xxxxxxxxxxx>
• PING: RE: How to enable mudflap with gcc-4.x
  • From: "Deepen Mantri" <Deepen.Mantri@xxxxxxxxxxxxxxx>
• Building final gcc cross-compiler
  • From: Vandra Akos <axos88@xxxxxxxxxxxx>
• Re: final gcc compiler can't find pthread.h even though it *is* in the include dir
  • From: Vandra Akos <axos88@xxxxxxxxxxxx>
• final gcc compiler can't find pthread.h even though it *is* in the include dir
  • From: Vandra Akos <axos88@xxxxxxxxxxxx>
• gcc 4.2.0 build fails on mac os 10.4.9, intel, /usr/bin/libtool: fatal error in ld64
  • From: "dan hitt" <dan.hitt@xxxxxxxxx>
• Re: building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxx>
• building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• difference in int,long behavior in gcc-3.4 4.0 vs 4.1 4.2
  • From: Oleg Verych <olecom@xxxxxxxxxxxxxx>
• Re: Compilining with newlib
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Compilining with newlib
  • From: none none <menwn@xxxxxxxxxxx>
• Help building a cross-toolchain for ARM-linux
  • From: Vandra Akos <axos88@xxxxxxxxxxxx>
• -ftree-vectorizer-verbose=n
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: Setting up a cross-compile
  • From: David Daney <ddaney@xxxxxxxxxx>
• Setting up a cross-compile
  • From: Dave Williss <dwilliss@xxxxxxxxxxxxxxx>
• Re: Unexpected failure-to-warn
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• Unexpected failure-to-warn
  • From: Thomas Womack <twomack@xxxxxxxxxxxxxxxxx>
• Using special calling conventions
  • From: Tom Bachmann <e_mc_h2@xxxxxx>
• RE: How to enable mudflap with gcc-4.x
  • From: "Deepen Mantri" <Deepen.Mantri@xxxxxxxxxxxxxxx>
• Re: Pragmas in GCC
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Pragmas in GCC
  • From: ZeMan <marckhayat@xxxxxxxxx>
• Re: building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: autovectorization
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: David Daney <ddaney@xxxxxxxxxx>
• Re: building gcc-4.2.0
  • From: Bobby McNulty <snyder100@xxxxxxxxxxxxx>
• building gcc-4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: c syntax
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• c syntax
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: building gcc 4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• autovectorization
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: building gcc 4.2.0
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: building gcc 4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: building gcc 4.2.0
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• building gcc 4.2.0
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• libgcc_s.so missing copysignl
  • From: Mathew Yeates <myeates@xxxxxxxxxxxx>
• Re: Cross compiling
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: How to turn this warning off?
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: How to turn this warning off?
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: Cross compiling
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: How to turn this warning off?
  • From: Tom St Denis <tstdenis@xxxxxxxxxxxxxxxx>
• How to turn this warning off?
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: GCC porting to 64-bit architecture
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• GCC porting to 64-bit architecture
  • From: arpit jain <dreams_arpit@xxxxxxxxxxx>
• Re: Cross compiling
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Cross compiling
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Cross compiling
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: Cross compiling
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: Cross compiling
  • From: "Rupert Wood" <me@xxxxxxxxx>
• Cross compiling
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Re: query regarding LLVM
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Problem when compiling pointers with GNU
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: query regarding LLVM
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• query regarding LLVM
  • From: "manish manish" <compilerguru@xxxxxxxxx>
• Problem when compiling pointers with GNU
  • From: "Johan Larsson" <johan_larsson_82@xxxxxxxxxxx>
• RE: fprintf in passes.c
  • From: "Duft Markus" <Markus.Duft@xxxxxxxxxx>
• fprintf in passes.c
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: union issue
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: union issue
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: union issue
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: union issue
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• RE: GCC Compatibility in C++
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: GCC 3.4.6 to GCC 4.1.1 migration
  • From: Thomas Mittelstaedt <T.Mittelstaedt@xxxxxxxxxx>
• Re: GCC Compatibility in C++
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• RE: GCC Compatibility in C++
  • From: "Shlomit Morad" <Shlomit@xxxxxxxxxxxx>
• Re: How to tell which compiler was used?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help required to upgrade gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Internal Error
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: How to force 16-byte alignment with gfortran?
  • From: FX Coudert <fxcoudert@xxxxxxxxx>
• Re: Bizarrely Poor Code from Bizarre Machine-Generated C Sources
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Re: Bizarrely Poor Code from Bizarre Machine-Generated C Sources
  • From: "Barak A. Pearlmutter" <barak@xxxxxxxxxx>
• Re: Conflict between compilers
  • From: Andrew Haley <aph-gcc@xxxxxxxxxxxxxxxxxxx>
• Conflict between compilers
  • From: Sergi Blanch i Torné <sbt@xxxxxx>
• How to tell which compiler was used?
  • From: Yan Seiner <yan@xxxxxxxxxx>
• Function instrumentation
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• union issue
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• help-gcc-4.0.4 can not compiler
  • From: "" <jinlian05@xxxxxx>
• Re: cast to an enum does not throw errors even for invalid values
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxx>
• Re: cast to an enum does not throw errors even for invalid values
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• don't pack my union
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: cast to an enum does not throw errors even for invalid values
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: cast to an enum does not throw errors even for invalid values
  • From: Shriramana Sharma <samjnaa@xxxxxxxxx>
• Re: g=+ help
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: How to enable mudflap with gcc-4.x
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• g=+ help
  • From: sahar kouroshnezhad <sahar529@xxxxxxxxx>