GCC Help

• Thread Index

• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: failing build 4.5.2: execvp: /bin/sh: Argument list too long
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• failing build 4.5.2: execvp: /bin/sh: Argument list too long
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• Re: GCC GUI???
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC GUI???
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: GCC GUI???
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• Re: GCC GUI???
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• Re: GCC GUI???
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: standard libraries are linked statically or dynamically?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC GUI???
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: GCC GUI???
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: GCC GUI???
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• Re: GCC GUI???
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• GCC GUI???
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• Compile SourceCode using OpenGL / SDL (Gravit 0.4.2) - additional info...
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• Re: compiled executable crashes with 'illegal instruction'
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: compiled executable crashes with 'illegal instruction'
  • From: Kai Ruottu <kai.ruottu@xxxxxxxxxxx>
• Re: Compile SourceCode using OpenGL / SDL (Gravit 0.4.2)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Compile SourceCode using OpenGL / SDL (Gravit 0.4.2)
  • From: emanu <emanuellarsson@xxxxxxxxxxx>
• completely unable to get Gcc 4.4.5 to build with local Gmp/Mpfr
  • From: Oliver Kullmann <O.Kullmann@xxxxxxxxxxxxx>
• compiled executable crashes with 'illegal instruction'
  • From: Vangelis Rokas <evrokas@xxxxxxxxxxx>
• Re: error in raise () from /lib/libc.so.6
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Re: incompatible implicit declaration
  • From: Bob Plantz <plantz@xxxxxxxx>
• Re: Dependency issue in gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Dependency issue in gcc
  • From: Dhanavel <espdhanavel@xxxxxxxxx>
• Re: Dependency issue in gcc
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Memory layout changed for classes with virtual functions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: error in raise () from /lib/libc.so.6
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: incompatible implicit declaration
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• error in raise () from /lib/libc.so.6
  • From: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
• Dependency issue in gcc
  • From: Dhanavel <espdhanavel@xxxxxxxxx>
• Re: Can gcc and Linux create a dynamic library?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: incompatible implicit declaration
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• RE: Checking -fPIC Failed when building the gcc 4.5.1 with --enable-plugin on cygwin
  • From: Lucky Lu <Lucky.Lu@xxxxxxxxxxxxxxxxxx>
• Re: can #line directive dynamically resolve the file path?
  • From: asmwarrior <asmwarrior@xxxxxxxxx>
• Re: why the barrier() can not take effect?
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• Re: incompatible implicit declaration
  • From: Robert Plantz <rgplantz@xxxxxxxxx>
• Re: can #line directive dynamically resolve the file path?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: incompatible implicit declaration
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Memory layout changed for classes with virtual functions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: incompatible implicit declaration
  • From: "Bill McEnaney" <bill@xxxxxxxxxxxx>
• Re: some questions about the output of gcc -v
  • From: "Andi Hellmund" <mail@xxxxxxxxxxxxxxxx>
• Re: incompatible implicit declaration
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• some questions about the output of gcc -v
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• incompatible implicit declaration
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: can #line directive dynamically resolve the file path?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: can #line directive dynamically resolve the file path?
  • From: asmwarrior <asmwarrior@xxxxxxxxx>
• Re: can #line directive dynamically resolve the file path?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• can #line directive dynamically resolve the file path?
  • From: asmwarrior <asmwarrior@xxxxxxxxx>
• Re: _start and main labels in C programs
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: Memory layout changed for classes with virtual functions
  • From: ronny meeus <ronny.meeus@xxxxxxxxx>
• Re: standard libraries are linked statically or dynamically?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: _start and main labels in C programs
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• _start and main labels in C programs
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: standard libraries are linked statically or dynamically?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: standard libraries are linked statically or dynamically?
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• standard libraries are linked statically or dynamically?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Can gcc and Linux create a dynamic library?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: why the barrier() can not take effect?
  • From: Parmenides <mobile.parmenides@xxxxxxxxx>
• Re: why the barrier() can not take effect?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: why the barrier() can not take effect?
  • From: Parmenides <mobile.parmenides@xxxxxxxxx>
• Re: Checking -fPIC Failed when building the gcc 4.5.1 with --enable-plugin on cygwin
  • From: Joel Dice <joel.dice@xxxxxxxxx>
• Re: Checking -fPIC Failed when building the gcc 4.5.1 with --enable-plugin on cygwin
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Checking -fPIC Failed when building the gcc 4.5.1 with --enable-plugin on cygwin
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Memory layout changed for classes with virtual functions
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Memory layout changed for classes with virtual functions
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Memory layout changed for classes with virtual functions
  • From: ronny meeus <ronny.meeus@xxxxxxxxx>
• Checking -fPIC Failed when building the gcc 4.5.1 with --enable-plugin on cygwin
  • From: Lucky Lu <Lucky.Lu@xxxxxxxxxxxxxxxxxx>
• Re: Can gcc and Linux create a dynamic library?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: why the barrier() can not take effect?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Can gcc and Linux create a dynamic library?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• why the barrier() can not take effect?
  • From: Parmenides <mobile.parmenides@xxxxxxxxx>
• Re: confirm unsubscribe from gcc@xxxxxxxxxxx
  • From: Konrad Eisele <konrad@xxxxxxxxxxx>
• Re: Vectorizing complex types
  • From: Ira Rosen <IRAR@xxxxxxxxxx>
• Vectorizing complex types
  • From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
• Re: GCC Initialization File?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Why the final object file of gcc can not be executed from the bourne shell?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Why the final object file of gcc can not be executed from the bourne shell?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: GCC Initialization File?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC Initialization File?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC Initialization File?
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
• Re: linking files
  • From: Robert Dell <dellr@xxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC Initialization File?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
• Re: GCC Initialization File?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC Initialization File?
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Can gcc show status of a compilation?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC Initialization File?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: GCC Initialization File?
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: GCC Initialization File?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• GCC Initialization File?
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Can gcc show status of a compilation?
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: linking files
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• linking files
  • From: Robert Dell <dellr@xxxxxxx>
• Re: max-page-size syntax
  • From: CortexFan <giancarlo.parodi@xxxxxxxxx>
• Re: relinking `libjvm.la' error when make install libjava
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Can gcc be compiled together with binutils?
  • From: Fabio Giovagnini <fabio.giovagnini@xxxxxxxxxxxxxxx>
• Re: Can gcc be compiled together with binutils?
  • From: Enrico Weigelt <weigelt@xxxxxxxx>
• fixincludes issue with gcc 4.4.2 build on centos 5.5. 32-bit /i686
  • From: Hari Kodungallur <hari.mailinglists@xxxxxxxxx>
• Re: Can gcc show status of a compilation?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Can gcc show status of a compilation?
  • From: Greatwolf <gmane.greatwolf@xxxxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: max-page-size syntax
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Inserting labels before and after my program's global variables
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• max-page-size syntax
  • From: CortexFan <giancarlo.parodi@xxxxxxxxx>
• Re: relinking `libjvm.la' error when make install libjava
  • From: majia gm <gmmajia@xxxxxxxxx>
• Re: relinking `libjvm.la' error when make install libjava
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Inserting labels before and after my program's global variables
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: relinking `libjvm.la' error when make install libjava
  • From: majia gm <gmmajia@xxxxxxxxx>
• Re: Re : Re : new gcc front end question
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: relinking `libjvm.la' error when make install libjava
  • From: Andrew Haley <aph@xxxxxxxxxx>
• relinking `libjvm.la' error when make install libjava
  • From: majia gm <gmmajia@xxxxxxxxx>
• Re: gcc search dirs
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc search dirs
  • From: frobnoid@xxxxxxxxx
• SOLVED - Re: ld: howto link a whole library or object file content to a specific section
  • From: CortexFan <giancarlo.parodi@xxxxxxxxx>
• Re: Linker question. How to change memory section for functions that comes from a ".a" library?
  • From: CortexFan <giancarlo.parodi@xxxxxxxxx>
• Fwd: GCC behave different for cv-qualifier function.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: need help for arithmetic conversion about gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: need help for arithmetic conversion about gcc
  • From: Robert Plantz <rgplantz@xxxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -ffast-math option live up to its name?
  • From: Tim Prince <n8tm@xxxxxxx>
• ld: howto link a whole library or object file content to a specific section
  • From: Gc <giancarlo.parodi@xxxxxxxxx>
• Re : Re : new gcc front end question
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: windigo84 <aberna@xxxxxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: windigo84 <aberna@xxxxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: "Yihe Chen" <yihect@xxxxxxxxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: need help for arithmetic conversion about gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: need help for arithmetic conversion about gcc
  • From: stephen <chency666@xxxxxxxxx>
• Re: need help for arithmetic conversion about gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -ffast-math option live up to its name?
  • From: Miles Bader <miles@xxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: Miles Bader <miles@xxxxxxx>
• need help for arithmetic conversion about gcc
  • From: stephen <chency666@xxxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Re : new gcc front end question
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• Re: -ffast-math option live up to its name?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: -ffast-math option live up to its name?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Quad-Core AMD Opteron(tm) Processor 2352 bugs?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• -ffast-math option live up to its name?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• gnat (ada) build for version 3.0 (to 3.0.4 via diffs)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Quad-Core AMD Opteron(tm) Processor 2352 bugs?
  • From: Nava Whiteford <new@xxxxxxxxxxxxx>
• Re: gcc standard libraries and freestanding mode
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re : new gcc front end question
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: Vector parameter loads to SSE registers
  • From: Tim Prince <n8tm@xxxxxxx>
• Re : Re : make option to recompile only changed files
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: preserving comments
  • From: Sharanbr <sharanb@xxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Vector parameter loads to SSE registers
  • From: windigo84 <aberna@xxxxxxxxxx>
• Re: How gcc links a C program with standard libraries?
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: GCC behave different for cv-qualifier function.
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• How gcc links a C program with standard libraries?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• gcc standard libraries and freestanding mode
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• GCC behave different for cv-qualifier function.
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: make install-strip
  • From: Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
• Re: Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: "Yihe Chen" <yihect@xxxxxxxxxxxxxx>
• Re: glibc test suite how to run for cross tool chain
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: compiling gnu libc (2.2.4)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: loop unrolling, flags and passes
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Can gcc be compiled together with binutils?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gnu99
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: new gcc front end question
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: Hail Marry time ...
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Hail Marry time ...
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Hail Marry time ...
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Hail Marry time ...
  • From: Dennis Clarke <dclarke@xxxxxxxxxxxxx>
• Re: Hail Marry time ...
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Why are there optimization levels (Noob question alert)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: strange warning with -Wparentheses
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• new gcc front end question
  • From: charfi asma <charfiasma@xxxxxxxx>
• glibc test suite how to run for cross tool chain
  • From: raju goruganti <raju.goruganti@xxxxxxxxx>
• Re: strange warning with -Wparentheses
  • From: andre maute <andre.maute@xxxxxx>
• compiling gnu libc (2.2.4)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• strange warning with -Wparentheses
  • From: andre maute <andre.maute@xxxxxx>
• Re: loop unrolling, flags and passes
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Why are there optimization levels (Noob question alert)
  • From: richardcavell@xxxxxxxx
• Hail Marry time ...
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: loop unrolling, flags and passes
  • From: "Kevin P. Fleming" <kpfleming@xxxxxxxxxx>
• loop unrolling, flags and passes
  • From: Abdul Wahid Memon <engrwahidmemon@xxxxxxxxx>
• Can gcc be compiled together with binutils?
  • From: "Zhang Lin" <zhanglin0714@xxxxxxx>
• gnu99
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Where can I get the defination __i686.get_pc_thunk.bx function in an objectdump a test program linked with a shared library??
  • From: "Yihe Chen" <yihect@xxxxxxxxxxxxxx>
• Re: FW: Looking for Fortran for Windows 7
  • From: NightStrike <nightstrike@xxxxxxxxx>
• Re: FW: Looking for Fortran for Windows 7
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: FW: Looking for Fortran for Windows 7
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: What loop optimizations could increase the code size significantly?
  • From: Gan <george.gan@xxxxxxxxx>
• What loop optimizations could increase the code size significantly?
  • From: "Fang, Changpeng" <Changpeng.Fang@xxxxxxx>
• FW: Looking for Fortran for Windows 7
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• -Wignored-qualifiers, a rock and a hard place
  • From: Magnus Fromreide <gcc@xxxxxxxxxxxxxx>
• FW: Looking for Fortran for Windows 7
  • From: "Stephen D. Black" <SDB7@xxxxxxxxxxxx>
• twice burned ...
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: install-strip
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Configure error with "--enable-lto" on mingw
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: install-strip
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Configure error with "--enable-lto" on mingw
  • From: "Naveen H. S" <Naveen.S@xxxxxxxxxxxxxxx>
• Re: GCC mailing lists search question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• install-strip
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• RE: Is 4 byte -1 invalid code on most/all architectures?
  • From: Joel Dice <joel.dice@xxxxxxxxx>
• RE: Is 4 byte -1 invalid code on most/all architectures?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: Is 4 byte -1 invalid code on most/all architectures?
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• RE: Is 4 byte -1 invalid code on most/all architectures?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• Re: Is 4 byte -1 invalid code on most/all architectures?
  • From: richardcavell@xxxxxxxx
• Re: Is 4 byte -1 invalid code on most/all architectures?
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• Is 4 byte -1 invalid code on most/all architectures?
  • From: Jay K <jay.krell@xxxxxxxxxxx>
• GCC mailing lists search question
  • From: Steve Ellcey <sje@xxxxxxxxxx>
• Re: Problem porting gcc to big-endian chip
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problem porting gcc to big-endian chip
  • From: Jeff Kenton <jkenton@xxxxxxxxxx>
• Re: make install-strip
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -gnatpg
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: about using GCC with PS Move
  • From: Mojmír Svoboda (2K Czech) <mojmir.svoboda@xxxxxxxxxxx>
• Re: about using GCC with PS Move
  • From: Tiago Maluta <tiago.maluta@xxxxxxxxx>
• about using GCC with PS Move
  • From: "Gene Michaelson" <g.michaelson@xxxxxxxxxxxxxxxxxxxxx>
• Re: search path for .c files!
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• search path for .c files!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• make install-strip
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: a question about -x language option
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• -gnatpg
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: a question about -x language option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: packaging generated files (autotools)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• packaging generated files (autotools)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: a question about -x language option
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• a question about -x language option
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: debug or no debug?
  • From: "Bill O'Connor" <billyoc@xxxxxxxxx>
• debug or no debug?
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: installed directory important (--prefix=)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Why --disable-libmudflap is undocumented?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Linker question. How to change memory section for functions that comes from a ".a" library?
  • From: Olof Andersson <olof.andersson@xxxxxxxxx>
• Re: .text, .data and .bbs!!
  • From: Nicolás Dato <nicolas.dato@xxxxxxxxx>
• installed directory important (--prefix=)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• profiled bootstrap
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: .text, .data and .bbs!!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• .text, .data and .bbs!!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• gnat failure with profiledbootstrap
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Why --disable-libmudflap is undocumented?
  • From: "Tadeus \"Eus\" Prastowo" <0x657573@xxxxxxxxxxxxxx>
• Re: Searching for #include files
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Searching for #include files
  • From: Edward Diener <eldlistmailingz@xxxxxxxxxxxxxx>
• Re: .text, .data and .bbs!!
  • From: Nicolás Dato <nicolas.dato@xxxxxxxxx>
• .text, .data and .bbs!!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: gcc-4.3.1 for mips linux failed to execute dynamically linked elf executables
  • From: Coder_gate <nhs_0702@xxxxxxxxx>
• gnat 3.4.6 to 4+ ???
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Linker question. How to change memory section for functions that comes from a ".a" library?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Linker question. How to change memory section for functions that comes from a ".a" library?
  • From: foolo <olof.andersson@xxxxxxxxx>
• Re: 64bits and a problem with pointers
  • From: Nicolás Dato <nicolas.dato@xxxxxxxxx>
• Re: 64bits and a problem with pointers
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: 64bits and a problem with pointers
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• 64bits and a problem with pointers
  • From: Nicolás Dato <nicolas.dato@xxxxxxxxx>
• Re: Getting GCC output of OpenMP before compilation?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: preserving comments
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Getting GCC output of OpenMP before compilation?
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: If kernel page size changed
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: If kernel page size changed
  • From: Nicolas BENOIT <nicolas.benoit@xxxxxx>
• If kernel page size changed
  • From: raju goruganti <raju.goruganti@xxxxxxxxx>
• Re: questions about cv-qualifier for function and references
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• questions about cv-qualifier for function and references
  • From: zhang qingshan <steven.zhang54373@xxxxxxxxx>
• Re: preserving comments
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Laviticus Stone <laviticus@xxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Laviticus Stone <laviticus@xxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Laviticus Stone <laviticus@xxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Laviticus Stone <laviticus@xxxxxxx>
• Re: ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• ld: fatal: file .libs/libglib-2.0.exp: unknown file type
  • From: Laviticus Stone <laviticus@xxxxxxx>
• Re: about gfortran
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: preserving comments
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: preserving comments
  • From: Sharanbr <sharanb@xxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: inline bug (?)
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: inline bug (?)
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: inline bug (?)
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: inline bug (?)
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: inline bug (?)
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: inline bug (?)
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• about gfortran
  • From: <Y.Li@xxxxxxxx>
• Re: Wherer is the Segmentation fault?
  • From: Vaibhav Kaushal <vaibhavkaushal123@xxxxxxxxx>
• Re: Wherer is the Segmentation fault?
  • From: Aubin LaBrosse <zoticus@xxxxxxxxx>
• Wherer is the Segmentation fault?
  • From: Vaibhav Kaushal <vaibhavkaushal123@xxxxxxxxx>
• Re: SPARC extended inline assembly and register constraints
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: SPARC extended inline assembly and register constraints
  • From: Josef Ahmad <josef_ahm@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: SPARC extended inline assembly and register constraints
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Dwarf debug location list
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Cross compiling gcc for ARM and dependency on libgcc_s.so.1 for pthread_cancel
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Symbol Visibility Problem in C Source File
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Change symbol visibility in library (local -> external)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Segfault when dereferencing %rax after -static compiling
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: preserving comments
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: march option for Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• several libm functions instantiations - SPARC
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: No linking occurs
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: No linking occurs
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• No linking occurs
  • From: Gunnar Sperber <gunnar.sperber@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: SSE instruction set disabled when i'm using -flto
  • From: Marcin Mirosław <marcin@xxxxxxxx>
• Library search path problem on x86_64 machines (lib64 vs lib)
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Damaged dependency files
  • From: Alex Peshkoff <peshkoff@xxxxxxx>
• Re: SSE instruction set disabled when i'm using -flto
  • From: Dmitry Gorbachev <d.g.gorbachev@xxxxxxxxx>
• Re: gcc enumeration print support
  • From: jovi zhang <bookjovi@xxxxxxxxx>
• Re: gcc451 clean build ?
  • From: David Daney <ddaney@xxxxxxxxxxxxxxxxxx>
• gcc451 clean build ?
  • From: "B.S.J.W. Stephenson" <es018r6256@xxxxxxxxxxxxxxxx>
• I have just tested my gcc4.5.1 on an oregonstate slackware64 13.1
  • From: "B.S.J.W. Stephenson" <es018r6256@xxxxxxxxxxxxxxxx>
• Re: Damaged dependency files
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Partial Static Linkage
  • From: Brian McGrew <brian@xxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: Partial Static Linkage
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Damaged dependency files
  • From: Alex Peshkoff <peshkoff@xxxxxxx>
• Re: Partial Static Linkage
  • From: Ryan Mansfield <rmansfield@xxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Partial Static Linkage
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Partial Static Linkage
  • From: Brian McGrew <brian@xxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: Questions about code generation
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Questions about code generation
  • From: richardcavell@xxxxxxxx
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: Questions about code generation
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• SPARC extended inline assembly and register constraints
  • From: Josef Ahmad <josef_ahm@xxxxxxxxx>
• Re: using static libraries
  • From: Kristoff Bonne <kristoff.bonne@xxxxxxxxx>
• Re: using static libraries
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: using static libraries
  • From: Kristoff Bonne <kristoff.bonne@xxxxxxxxx>
• Re: using static libraries
  • From: Kristoff Bonne <kristoff.bonne@xxxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Questions about code generation
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Questions about code generation
  • From: richardcavell@xxxxxxxx
• Re: using static libraries
  • From: Josef Ahmad <josef_ahm@xxxxxxxxx>
• Re: Cloog/PPL 0.15.10 build failure
  • From: Arnaud Lacombe <lacombar@xxxxxxxxx>
• Cloog/PPL 0.15.10 build failure
  • From: Arnaud Lacombe <lacombar@xxxxxxxxx>
• Re: using static libraries
  • From: Kristoff Bonne <kristoff.bonne@xxxxxxxxx>
• Re: Fail to compile Boost make_shared when -std=c++0x on
  • From: 陳韋任 <chenwj@xxxxxxxxxxxxxxxxx>
• Re: Fail to compile Boost make_shared when -std=c++0x on
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Dwarf debug location list
  • From: majia gm <gmmajia@xxxxxxxxx>
• Fail to compile Boost make_shared when -std=c++0x on
  • From: 陳韋任 <chenwj@xxxxxxxxxxxxxxxxx>
• Re: using static libraries
  • From: Josef Ahmad <josef_ahm@xxxxxxxxx>
• using static libraries
  • From: Kristoff Bonne <kristoff.bonne@xxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• SSE instruction set disabled when i'm using -flto
  • From: Marcin Mirosław <marcin@xxxxxxxx>
• Cross compiling gcc for ARM and dependency on libgcc_s.so.1 for pthread_cancel
  • From: Vincent Forbes <vwfst55@xxxxxxxxx>
• Re: Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: building gcc 4.4.5 from source on Fedora 13
  • From: Andrew Haley <aph@xxxxxxxxxx>
• building gcc 4.4.5 from source on Fedora 13
  • From: Mr Dash Four <mr.dash.four@xxxxxxxxxxxxxx>
• Re: Symbol Visibility Problem in C Source File
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Symbol Visibility Problem in C Source File
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Bob Plantz <plantz@xxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Elias Gabriel Amaral da Silva <tolkiendili@xxxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Floating point: just 20 digits of precision
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Floating point: just 20 digits of precision
  • From: Elias Gabriel Amaral da Silva <tolkiendili@xxxxxxxxx>
• Change symbol visibility in library (local -> external)
  • From: Jeffrey Walton <noloader@xxxxxxxxx>
• RE: Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Sumanth Gundapaneni <Sumanth.Gundapaneni@xxxxxxxxxxxxxxx>
• Undocumented differences between -M and -MD
  • From: jtc@xxxxxxxxxxxxxxxxxx (J.T. Conklin)
• Re: preserving comments
  • From: Sharanbr <sharanb@xxxxxxx>
• Re: Failure to recognize siginfo_t._sifields
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Robert Dell <dellr@xxxxxxx>
• Segfault when dereferencing %rax after -static compiling
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Bob Plantz <plantz@xxxxxxxx>
• Failure to recognize siginfo_t._sifields
  • From: Amittai Aviram <amittai.aviram@xxxxxxxx>
• Re: preserving comments
  • From: Philip Herron <redbrain@xxxxxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Tim Prince <n8tm@xxxxxxx>
• preserving comments
  • From: Sharanbr <sharanb@xxxxxxx>
• march option for Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
  • From: Rainer M Krug <R.M.Krug@xxxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Nikos Chantziaras <realnc@xxxxxxxx>
• Re: Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Vincent Lefevre <vincent+gcc@xxxxxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Marc Glisse <marc.glisse@xxxxxxxx>
• Re: help with g++ and strict aliasing on x86-64
  • From: Alberto Griggio <alberto.griggio@xxxxxxxxx>
• Why do floating point operations differ between -m64 -O0/-O1 and -m32 -O0?
  • From: Nikos Chantziaras <realnc@xxxxxxxx>
• RE: Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Sumanth Gundapaneni <Sumanth.Gundapaneni@xxxxxxxxxxxxxxx>
• Re: Meyers Item 4 Singleton in presence of threading
  • From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
• Re: help with g++ and strict aliasing on x86-64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: help with g++ and strict aliasing on x86-64
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: help with g++ and strict aliasing on x86-64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: help in linking standard libraries please
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: g++ 4.5.1 on OpenSolaris
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: arm -msoft-float and -lfloat question
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• Re: archive searching!!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: help with g++ and strict aliasing on x86-64
  • From: Alberto Griggio <alberto.griggio@xxxxxxxxx>
• Re: minor BUG for GCC recognizing upper-case of -T option!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• help with g++ and strict aliasing on x86-64
  • From: Alberto Griggio <alberto.griggio@xxxxxxxxx>
• Exception Handling implementation with Return Address (RA) having PC right shifted by 1
  • From: Sumanth Gundapaneni <Sumanth.Gundapaneni@xxxxxxxxxxxxxxx>
• help in linking standard libraries please
  • From: Tamamontu M <tamamontu@xxxxxxxxxxxx>
• Re: question on cmath (gcc 4.5.1)
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Meyers Item 4 Singleton in presence of threading
  • From: Paweł Sikora <pluto@xxxxxxxx>
• Re: Meyers Item 4 Singleton in presence of threading
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Meyers Item 4 Singleton in presence of threading
  • From: Miles Bader <miles@xxxxxxx>
• Re: g++ 4.5.1 on OpenSolaris
  • From: asyropoulos@xxxxxxx
• Re: Meyers Item 4 Singleton in presence of threading
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: ambiguity of ld manual regarding to -L option!!
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: -L option in GNU linker ld
  • From: Andi Hellmund <mail@xxxxxxxxxxxxxxxx>
• -L option in GNU linker ld
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• ambiguity of ld manual regarding to -L option!!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Meyers Item 4 Singleton in presence of threading
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• archive searching!!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• minor BUG for GCC recognizing upper-case of -T option!
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: g++ 4.5.1 on OpenSolaris
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: inlining memcpy
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• g++ 4.5.1 on OpenSolaris
  • From: asyropoulos@xxxxxxx
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: One-way stack support
  • From: John Tobey <john.tobey@xxxxxxxxx>
• inlining memcpy
  • From: <egada@xxxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Miles Bader <miles@xxxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• Re: question on cmath (gcc 4.5.1)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• question on cmath (gcc 4.5.1)
  • From: Neal Becker <ndbecker2@xxxxxxxxx>
• Re: One-way stack support
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: VFP unit failed
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Get "int from double" conversion warnings also with GCC 4.4.5
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• arm -msoft-float and -lfloat question
  • From: Bryan Hundven <bryanhundven@xxxxxxxxx>
• One-way stack support
  • From: John Tobey <john.tobey@xxxxxxxxx>
• test case
  • From: raju goruganti <raju.goruganti@xxxxxxxxx>
• VFP unit failed
  • From: raju goruganti <raju.goruganti@xxxxxxxxx>
• Get "int from double" conversion warnings also with GCC 4.4.5
  • From: Karl Krach <mailinglists@xxxxxxxxxxxxx>
• Re: inline bug (?)
  • From: jorge.perez@xxxxxxxx
• Re: incompatible GCC 4.4.5 and 4.5.1 libstdc++ ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: inline bug (?)
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: inline bug (?)
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxx>
• Re: incompatible GCC 4.4.5 and 4.5.1 libstdc++ ?
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• inline bug (?)
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Re: Using __cxa_atexit on Solaris
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Using __cxa_atexit on Solaris
  • From: rvyas <rishabh.a.vyas@xxxxxxxxx>
• Invoking atomic functions from a C++ shared lib (or should I force linking with -lgcc?)
  • From: Christophe Lyon <christophe.lyon@xxxxxx>
• building ada (or gnat?)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: Using __cxa_atexit on Solaris
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: output messages
  • From: ams@xxxxxxx (Alfred M. Szmidt)
• Re: output messages
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Using __cxa_atexit on Solaris
  • From: rvyas <rishabh.a.vyas@xxxxxxxxx>
• Re: output messages
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: output messages
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: c++0x tuple vs. pair
  • From: Miles Bader <miles@xxxxxxx>
• output messages
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Where are standard system directories?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: c++0x tuple vs. pair
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: problem with my @gcc.gnu.org address
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: (linker) default search path for ld
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: problem with my @gcc.gnu.org address
  • From: Fabien Chêne <fabien.chene@xxxxxxxxx>
• Where are standard system directories?
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: (linker) default search path for ld
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• c++0x tuple vs. pair
  • From: Miles Bader <miles@xxxxxxx>
• Re: (linker) default search path for ld
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• (linker) default search path for ld
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: -isystem and local includes
  • From: Zadirion <zadirion@xxxxxxxxx>
• Re: problem with my @gcc.gnu.org address
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: proper configuring & installation ???
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Are the gcc memory hooks sometimes bypassed?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: -isystem and local includes
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• problem with my @gcc.gnu.org address
  • From: Fabien Chêne <fabien.chene@xxxxxxxxx>
• Re: proper configuring & installation ???
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: double argument casting
  • From: Jorge PEREZ <jorge.perez@xxxxxxxx>
• Are the gcc memory hooks sometimes bypassed?
  • From: "Fabian van der Werf" <fabian.van.der.werf@xxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Can gcc show status of a compilation?
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: -isystem and local includes
  • From: Zadirion <zadirion@xxxxxxxxx>
• -isystem and local includes
  • From: Zadirion <zadirion@xxxxxxxxx>
• Can gcc show status of a compilation?
  • From: Greatwolf <gmane.greatwolf@xxxxxxxxxx>
• Re: proper configuring & installation ???
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• proper configuring & installation ???
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: 'lvalue required as unary ‘&’ operand' Problem
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Bad inlining because of "throw"
  • From: Luca Béla Palkovics <luca.bela.palkovics@xxxxxxxxx>
• Re: operator new catch parameter type gcc 4.3.2
  • From: "Jan M" <jan_m@xxxxxxxxxxxxxxxx>
• Re: gcc 4.4.2 : float multiplication 4097*4097 seems to be off by 1
  • From: Bob Plantz <plantz@xxxxxxxx>
• Re: gcc 4.4.2 : float multiplication 4097*4097 seems to be off by 1
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc 4.4.2 : float multiplication 4097*4097 seems to be off by 1
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Bad inlining because of "throw"
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc 4.4.2 : float multiplication 4097*4097 seems to be off by 1
  • From: 0throot <0throot@xxxxxxxxxxx>
• Re: 'lvalue required as unary ‘&’ operand' Problem
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: Bad inlining because of "throw"
  • From: John Fine <johnsfine@xxxxxxxxxxx>
• Re: operator new catch parameter type gcc 4.3.2
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: operator new catch parameter type gcc 4.3.2
  • From: Brian McGrew <brian@xxxxxxxxxxxxx>
• Re: operator new catch parameter type gcc 4.3.2
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Mutually Exclusive switches
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Mutually Exclusive switches
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• Mutually Exclusive switches
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Tim Prince <n8tm@xxxxxxx>
• operator new catch parameter type gcc 4.3.2
  • From: "Jan M" <jan_m@xxxxxxxxxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc build without debug (no -g)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "complete" gcc bootstrap
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: MIPS 32-bit ABI stack pointer
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: MIPS 32-bit ABI stack pointer
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Re: 'lvalue required as unary ‘&’ operand' Problem
  • From: Brian Budge <brian.budge@xxxxxxxxx>
• 'lvalue required as unary ‘&’ operand' Problem
  • From: Rifat Mahmud <rftmhmd@xxxxxxxxx>
• gcc build without debug (no -g)
  • From: kevin diggs <diggskevin38@xxxxxxxxx>
• "complete" gcc bootstrap
  • From: in <in@xxxxxxxxxxx>
• Re: Bad inlining because of "throw"
  • From: Luca Béla Palkovics <luca.bela.palkovics@xxxxxxxxx>
• Re: Bad inlining because of "throw"
  • From: Luca Béla Palkovics <luca.bela.palkovics@xxxxxxxxx>
• Re: Bad inlining because of "throw"
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Bad inlining because of "throw"
  • From: Luca Béla Palkovics <luca.bela.palkovics@xxxxxxxxx>
• Re: MIPS 32-bit ABI stack pointer
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: MIPS 32-bit ABI stack pointer
  • From: Mason <mpeg.blue@xxxxxxx>
• MIPS 32-bit ABI stack pointer
  • From: Mason <mpeg.blue@xxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Converting from little-endian to big-endian -- followup
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Error message "-T: command not found" building 4.5.1 on Solaris 10 SPARC
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Troubles downloading gfortran for Tiger
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Converting from little-endian to big-endian -- followup
  • From: Jeff Kenton <jeffrey.kenton@xxxxxxxxxxx>
• Re: GCC 4.5.0 - libgfortran issue
  • From: David Edelsohn <dje.gcc@xxxxxxxxx>
• Error message "-T: command not found" building 4.5.1 on Solaris 10 SPARC
  • From: "Dr. David Kirkby" <david.kirkby@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: John Boncek <jboncek@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Troubles downloading gfortran for Tiger
  • From: Mario Bernal <mbernalrod@xxxxxxxxx>
• Re: bootstrap problem?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Zdeněk Sojka <zsojka@xxxxxxxxx>
• bootstrap problem?
  • From: Salvatore Filippone <salvatore.filippone@xxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: denilsson31 <denilsson31@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: denilsson31 <denilsson31@xxxxxxxxxx>
• Re : [Generic] CALL_EXPR tree code with object ref
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Unnecessary movzx instruction?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Unnecessary movzx instruction?
  • From: Jeff Law <law@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: Axel Freyn <axel-freyn@xxxxxx>
• Re: Unnecessary movzx instruction?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: Dario Saccavino <kathoum@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: denilsson31 <denilsson31@xxxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: Dario Saccavino <kathoum@xxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: denilsson31 <denilsson31@xxxxxxxxxx>
• Unnecessary movzx instruction?
  • From: Justin Lebar <justin.lebar@xxxxxxxxx>
• Re: [C++]: Multiple inheritage/Conflicts
  • From: Axel Freyn <axel-freyn@xxxxxx>
• [C++]: Multiple inheritage/Conflicts
  • From: denilsson31 <denilsson31@xxxxxxxxxx>
• Re: Interesting void* bug
  • From: Hilton Medeiros <medeiros.hilton@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Tim Prince <n8tm@xxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
• Re: Interesting void* bug
  • From: Kalle Olavi Niemitalo <kon@xxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Jason Merrill <jason@xxxxxxxxxx>
• Re: no mails from gcc-bugzilla since I changed e-mail
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: "Segher Boessenkool" <segher@xxxxxxxxxxxxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Zdeněk Sojka <zsojka@xxxxxxxxx>
• Interesting void* bug
  • From: Hilton Medeiros <medeiros.hilton@xxxxxxxxx>
• Re: Clarification on Gcc's strict aliasing rules
  • From: Patrick Horgan <phorgan1@xxxxxxxxx>
• Clarification on Gcc's strict aliasing rules
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
• Re: no mails from gcc-bugzilla since I changed e-mail
  • From: Georg Lay <avr@xxxxxxxx>
• Re: where we can find libjpeg.a?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• where we can find libjpeg.a?
  • From: "eric lin" <fsshl@xxxxxxxxxxx>
• [C++0x] code that used to be accepted isn't accepted anymore (related to constexpr changes?)
  • From: Zdeněk Sojka <zsojka@xxxxxxxxx>
• Re: Converting from little-endian to big-endian
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Converting from little-endian to big-endian
  • From: Jeff Kenton <jeffrey.kenton@xxxxxxxxxxx>
• Re: Can insns be combined across UNSPEC_VOLATILE.?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Incorrect construction vtable on ARM in case of diamond shaped virtual inheritance
  • From: andrew wiggin <end3er@xxxxxxxxx>
• Re: Incorrect construction vtable on ARM in case of diamond shaped virtual inheritance
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• C++: how to export only RTTI, not methods symbols ?
  • From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
• Re: Incorrect construction vtable on ARM in case of diamond shaped virtual inheritance
  • From: andrew wiggin <end3er@xxxxxxxxx>
• Can insns be combined across UNSPEC_VOLATILE.?
  • From: Christian Bruel <christian.bruel@xxxxxx>
• Re: Incorrect construction vtable on ARM in case of diamond shaped virtual inheritance
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Incorrect construction vtable on ARM in case of diamond shaped virtual inheritance
  • From: andrew wiggin <end3er@xxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Generating a symbol-file for a release version.
  • From: Cedric Roux <cedric.roux@xxxxxxxxxx>
• Generating a symbol-file for a release version.
  • From: tom <tompotts@xxxxxxxxxxxxxxxxxxxxxx>
• Re: gcc (g++4.4.3) have no right to modify the name of my varialbe
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc (g++4.4.3) have no right to modify the name of my varialbe
  • From: "eric lin" <fsshl@xxxxxxxxxxx>
• Re: a question about linker and addresses
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: no mails from gcc-bugzilla since I changed e-mail
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GAS ".cfi_*" directives emitted for 64 bit but not 32 bit
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: GCC vector extensions.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: problem about __builtin_expect()
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: [Generic] CALL_EXPR tree code with object ref
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Linking GCC ELFs with IAR EWARM linker
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• no mails from gcc-bugzilla since I changed e-mail
  • From: Georg Lay <avr@xxxxxxxx>
• GAS ".cfi_*" directives emitted for 64 bit but not 32 bit
  • From: Jeremy Hall <jeremy.m0jnx@xxxxxxxxx>
• GCC vector extensions.
  • From: Hariharan Sandanagobalane <hariharans@xxxxxxxxxxxx>
• problem about __builtin_expect()
  • From: Parmenides <mobile.parmenides@xxxxxxxxx>
• [Generic] CALL_EXPR tree code with object ref
  • From: charfi asma <charfiasma@xxxxxxxx>
• Re: Linking GCC ELFs with IAR EWARM linker
  • From: Mitko <asdfgga12@xxxxxxxxx>
• Re: a question about linker and addresses
  • From: ali hagigat <hagigatali@xxxxxxxxx>
• Re: compile error of type unmatch, plz help
  • From: Axel Freyn <axel-freyn@xxxxxx>
• compile error of type unmatch, plz help
  • From: "eric lin" <fsshl@xxxxxxxxxxx>
• Re: Problem with libiconv
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>