GCC Help

• Thread Index

• compiling 32bit c program in 64 bit
  • From: flope <flope004@xxxxxxxxxxx>
• specs file make gcc 4.1.2 segfault
  • From: Benoit Sigoure <tsuna@xxxxxxxxxxxxx>
• Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
  • From: Kai Tietz <Kai.Tietz@xxxxxxxxxxxxx>
• Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
  • From: Andrew Haley <aph@xxxxxxxxxx>
• need a fix for -fdump-tree-original of g++
  • From: chellaj <rajeshchellappa@xxxxxxxxxxx>
• Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
  • From: Kai Tietz <Kai.Tietz@xxxxxxxxxxxxx>
• Re: Strange pathes for gcc for x86_64-pc-mingw32
  • From: Kai Tietz <Kai.Tietz@xxxxxxxxxxxxx>
• Re: Fw: Strange paths for gcc for x86_64-pc-mingw32
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Strange pathes for gcc for x86_64-pc-mingw32
  • From: Andrew Haley <aph@xxxxxxxxxx>
• --with-sysroot and --with-build-sysroot
  • From: Marco Trudel <mtrudel@xxxxxx>
• optimization of catch clauses in shared library
  • From: fabien.chene@xxxxxxxxx (Fabien Chêne)
• Re: gcc-4.1.2 compilation failing on ld (RHEL 3 system)
  • From: steve kirby <thin_runner@xxxxxxxxx>
• Re: problem with gcc compiler in the mac os X version 10.4.6
  • From: bjorn rohde jensen <bjensen@xxxxxxxxxxx>
• Re: static function pointers in C++ template class
  • From: "Wesley Smith" <wesley.hoke@xxxxxxxxx>
• Linking multiple resource files
  • From: Cedric Bresson <cedric.bresson@xxxxxxxxx>
• static function pointers in C++ template class
  • From: "Wesley Smith" <wesley.hoke@xxxxxxxxx>
• --with-iconv-prefix not mentioned in gcc FAQ
  • From: "Ken Takusagawa" <ken.takusagawa.2@xxxxxxxxx>
• problem with gcc compiler in the mac os X version 10.4.6
  • From: mag rat <dazzletoo@xxxxxxxxx>
• Reg : CCPPC details
  • From: "Ravi Kannan" <ravikannanv@xxxxxxxxxxxxxx>
• Instruction scheduling
  • From: "P. Pavan Kumar" <pavankumar@xxxxxxxxxxxxxx>
• Re: gcc 3.4.6 on PPC why doing function inline with -O2?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Unable to build gcc4.1.2 with MinGW/MSys
  • From: Martin Krischik <krischik@xxxxxxxxxxxxxxxxxxxxx>
• Re: Unable to build gcc4.1.2 with MinGW/MSys
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc-4.1.2 compilation failing on ld (RHEL 3 system)
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Unable to build gcc4.1.2 with MinGW/MSys
  • From: David Gressett <jdgressett@xxxxxxxxxxxxxxx>
• gcc 3.4.6 on PPC why doing function inline with -O2?
  • From: "Ming Lei" <mlei@xxxxxxxxxxx>
• gcc-4.1.2 compilation failing on ld (RHEL 3 system)
  • From: steve kirby <thin_runner@xxxxxxxxx>
• Re: intermediate representations of a C program
  • From: Andrew Haley <aph@xxxxxxxxxx>
• intermediate representations of a C program
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• RE: kernel too old
  • From: Monteaup <m_cz@xxxxxx>
• RE: error: 'comp' was not declared in this scope [RESOLVED]
  • From: "Divy Kanungo" <divyk@xxxxxxxxxxxxxx>
• Re: How can I make the following code compile under gcc-4.1.2
  • From: andre maute <andre.maute@xxxxxx>
• How can I make the following code compile under gcc-4.1.2
  • From: Stefan Schunck <Stefan.Schunck@xxxxxx>
• Re: error: 'comp' was not declared in this scope
  • From: me22 <me22.ca@xxxxxxxxx>
• Re: error: 'comp' was not declared in this scope
  • From: "Divy Kanungo" <divyk@xxxxxxxxxxxxxx>
• Re: [Fwd: How to take the member function as the function argument?]
  • From: me22 <me22.ca@xxxxxxxxx>
• [Fwd: How to take the member function as the function argument?]
  • From: benjamin <benjamin.batistic@xxxxxxxxxx>
• How to take the member function as the function argument?
  • From: benjamin <benjamin.batistic@xxxxxxxxxx>
• Re: error: 'comp' was not declared in this scope
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: error: 'comp' was not declared in this scope
  • From: "Divy Kanungo" <divyk@xxxxxxxxxxxxxx>
• RE: kernel too old
  • From: "Kaz Kylheku" <kaz@xxxxxxxxxxxxxxxxx>
• .a file can not link to .lib file???
  • From: ballofking <s2131172@xxxxxxxxxxxxxxx>
• kernel too old
  • From: Monteaup <m_cz@xxxxxx>
• Re: error: 'comp' was not declared in this scope
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: G++ structure member alignment
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• error: 'comp' was not declared in this scope
  • From: "Divy Kanungo" <divyk@xxxxxxxxxxxxxx>
• Re: G++ structure member alignment
  • From: "Baruch Lifshitz" <baruchli@xxxxxxxxx>
• Re: finding where a macro is redefined
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• finding where a macro is redefined
  • From: "Trevis Rothwell" <tjr@xxxxxxx>
• Re: G++ structure member alignment
  • From: "Baruch Lifshitz" <baruchli@xxxxxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: Pavel Saviankou <saviankou@xxxxxx>
• Re: cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: Andrew Haley <aph@xxxxxxxxxx>
• cc1plus: out of memory allocating 33554432 bytes after a total of 38465536 bytes
  • From: Pavel Saviankou <saviankou@xxxxxx>
• Re: Compilation error gcc-2.95.3
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: G++ structure member alignment
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• G++ structure member alignment
  • From: "Baruch Lifshitz" <baruchli@xxxxxxxxx>
• Compilation error gcc-2.95.3
  • From: "Pranav Kumar" <pranav.kumar@xxxxxxxxx>
• Re: inlining callbacks question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc-4.2-20061212 building error using unsafe *FLAGS
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: using programs build with gcc-4.1.1 in systems than never have gcc
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: using programs build with gcc-4.1.1 in systems than never have gcc
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• using programs build with gcc-4.1.1 in systems than never have gcc
  • From: Anatoly Kanashin <kanashin@xxxxxxxxxx>
• Re: compile problem
  • From: Grigory Zagorodnev <grigory_zagorodnev@xxxxxxxxxxxxxxx>
• Re: Data Flow
  • From: Jeffrey Holle <jeffreyholle@xxxxxxxxxxxxx>
• Re: inlining callbacks question
  • From: Christopher Layne <clayne@xxxxxxxxxxxx>
• Re: inlining callbacks question
  • From: Christopher Layne <clayne@xxxxxxxxxxxx>
• Modifying data returned by __builtin_apply_args()
  • From: "Frank Penczek" <frank.penczek@xxxxxxxxxxxxxx>
• Re: compile problem
  • From: Blake Huff <stangmechanic@xxxxxxxxx>
• compile problem
  • From: Chris Bruno <fmaanimefreak@xxxxxxxxx>
• Re: gcc-4.2-20061212 building error using unsafe *FLAGS
  • From: "Vladimir A. Pavlov" <pv4@xxxxx>
• Re: Data Flow
  • From: monica@xxxxxxxxxxx (Mônica Magalhães Pereira)
• Re: 2 questions
  • From: Andrew Haley <aph@xxxxxxxxxx>
• 2 questions
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: Compilation error gcc-2.95.3
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: inlining callbacks question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: inlining callbacks question
  • From: Christopher Layne <clayne@xxxxxxxxxxxx>
• Query regarding compilation in 64-bit mode on a 32-bit RHAS 3.0 using 32-bit g++
  • From: yashpal slathia <yashpal_ait21@xxxxxxxxx>
• Re: gcc-4.2-20061212 building error using unsafe *FLAGS
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: How to enlarge the stack size?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: inlining callbacks question
  • From: Andrew Haley <aph@xxxxxxxxxx>
• How to enlarge the stack size?
  • From: benjamin <benjamin.batistic@xxxxxxxxxx>
• gcc-4.2-20061212 building error using unsafe *FLAGS
  • From: "Vladimir A. Pavlov" <pv4@xxxxx>
• inlining callbacks question
  • From: Christopher Layne <clayne@xxxxxxxxxxxx>
• building glibc 2.5 or glibc HEAD on gcc 4.2 on linux-ppc
  • From: Arkadiusz Miskiewicz <arekm@xxxxxxxxxxxxx>
• Re: can I ask question about a bug of gettimeofday here?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: Doubt about insn-codes and 'gencodes' program
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Compilation error gcc-2.95.3
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: can I ask question about a bug of gettimeofday here?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Query regarding compilation in 64-bit mode on a 32-bit RHAS 3.0 using 32-bit g++
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Doubt about insn-codes and 'gencodes' program
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Re: can I ask question about a bug of gettimeofday here?
  • From: Lin George <george4academic@xxxxxxxxx>
• Compilation error gcc-2.95.3
  • From: "Pranav Kumar" <pranav.kumar@xxxxxxxxx>
• Re: can I ask question about a bug of gettimeofday here?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• can I ask question about a bug of gettimeofday here?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: Copy Constructor w/gcc411
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• RE: please help me about __builtin_return_address
  • From: <shin.anzai@xxxxxxxxxxxxx>
• Re: please help me about __builtin_return_address
  • From: Andrew Haley <aph@xxxxxxxxxx>
• please help me about __builtin_return_address
  • From: <shin.anzai@xxxxxxxxxxxxx>
• Re: Build fail
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Stack pointer alignment
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Build fail
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Re: Build fail
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Build fail
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Copy Constructor w/gcc411
  • From: "Phy Prabab" <phyprabab@xxxxxxxxx>
• Re: Build fail
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Build fail
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Query regarding compilation in 64-bit mode on a 32-bit RHAS 3.0 using 32-bit g++
  • From: yashpal slathia <yashpal_ait21@xxxxxxxxx>
• Stack pointer alignment
  • From: "Facundo Ciccioli" <facundofc@xxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Sven Eschenberg <eschenb@xxxxxxxxxxxxxxxxxxx>
• Re: Data Flow
  • From: "Daniel Berlin" <dberlin@xxxxxxxxxxx>
• RE: "virtual memory exhausted: Out of memory" with a large static array
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Sven Eschenberg <eschenb@xxxxxxxxxxxxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: Re: Why a specific gcc runtime is needed?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: "virtual memory exhausted: Out of memory" with a large static array
  • From: Andrew Haley <aph@xxxxxxxxxx>
• "virtual memory exhausted: Out of memory" with a large static array
  • From: Pavel Saviankou <saviankou@xxxxxx>
• Re: Re: Why a specific gcc runtime is needed?
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: Bytes alignement problem with arm-linux-gcc
  • From: Eric Botcazou <ebotcazou@xxxxxxxxxxxxxx>
• Re: Why a specific gcc runtime is needed?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: .size directive
  • From: Andrew Haley <aph@xxxxxxxxxx>
• .size directive
  • From: Rahul <rah.v.ragh@xxxxxxxxx>
• Re: Bytes alignement problem with arm-linux-gcc
  • From: "Frederic Kwiatkowski" <stagedrt@xxxxxxxxx>
• RE: Bytes alignement problem with arm-linux-gcc
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Why a specific gcc runtime is needed?
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: Bytes alignement problem with arm-linux-gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Bytes alignement problem with arm-linux-gcc
  • From: "Frederic Kwiatkowski" <stagedrt@xxxxxxxxx>
• Re: parsed as non-type error
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• parsed as non-type error
  • From: "Paul Davis" <pjdavis@xxxxxxxxxxxxxxxxxxxxx>
• Re: Is -Wall the Automatically Provided Default?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• RE: Is -Wall the Automatically Provided Default?
  • From: "Kaz Kylheku" <kaz@xxxxxxxxxxxxxxxxx>
• Re: Unused warning
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Is -Wall the Automatically Provided Default?
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Unused warning
  • From: "Eric Lemings" <lemings@xxxxxxxxxxxxx>
• Is -Wall the Automatically Provided Default?
  • From: "Carbonaro, Tony" <tony.carbonaro@xxxxxxxx>
• Re: Tidy i386 signal handler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Tidy i386 signal handler
  • From: guru <guru@xxxxxxxxxxxxxxxxx>
• Re: Tidy i386 signal handler
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Tidy i386 signal handler
  • From: guru <guru@xxxxxxxxxxxxxxxxx>
• Re: gcc exception handle
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: deprecated conversion from string constant to 'char *'
  • From: Derek Atkins <warlord@xxxxxxx>
• Re: deprecated conversion from string constant to 'char *'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: deprecated conversion from string constant to 'char *'
  • From: Derek Atkins <warlord@xxxxxxx>
• Re: does this code break the strict-aliasing rules ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• does this code break the strict-aliasing rules ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• Data Flow
  • From: "monica" <monica@xxxxxxxxxxx>
• GCJ linking problem with inherited classes in jar
  • From: "Bu Bacoo" <bubacoo@xxxxxxxxx>
• Re: what's this constant ?
  • From: Ray Hurst <rhurst2@xxxxxxx>
• Re: what's this constant ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: compiling instrinstics
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Specific register constraints on MIPS
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Windres, Pre-build
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• what's this constant ?
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: Windres, Pre-build
  • From: crtjer46 <jkalinowski@xxxxxxxxxxxxxxxxx>
• Re: Windres, Pre-build
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Windres, Pre-build
  • From: crtjer46 <jkalinowski@xxxxxxxxxxxxxxxxx>
• Re: Test suites for open-source compilers
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: compiling instrinstics
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Test suites for open-source compilers
  • From: "Kakoli Sen" <kakolis@xxxxxxxxxxxxxx>
• compiling instrinstics
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: C Preprocessor: Expected Declaration Specifiers
  • From: "Ryan Slominski" <rjslom@xxxxxxxxx>
• Problems creating cross compiler to sparc-sun-solaris2.9
  • From: "Kyle Stemen" <xt4sbzq02@xxxxxxxxxxxxxx>
• Re: C Preprocessor: Expected Declaration Specifiers
  • From: "Ryan Slominski" <rjslom@xxxxxxxxx>
• gprof issue on XSCALE
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: C Preprocessor: Expected Declaration Specifiers
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Specific register constraints on MIPS
  • From: "Aaron W. LaFramboise" <aaronavay62@xxxxxxxxxxx>
• Re: problem compiling with gcc, w32api and libiphlpapi.a
  • From: <cgraham@xxxxxxxxxxxxxxxxxx>
• Re: problem compiling with gcc, w32api and libiphlpapi.a
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• problem compiling with gcc, w32api and libiphlpapi.a
  • From: <cgraham@xxxxxxxxxxxxxxxxxx>
• Re: How to use "Dwarf2 Exception Handler"?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• How to use "Dwarf2 Exception Handler"?
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: "Bhaskar Reddy" <bhaskar@xxxxxxxxxxxxxx>
• Re: Query regarding, RTL Macros
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Check heap size / set heap for system call
  • From: "Puetz, Oliver P11M22" <Puetz.Oliver@xxxxxxxxxxx>
• Re: __builtin_setjmp/__builtin_longjmp Implementation
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: __builtin_setjmp/__builtin_longjmp Implementation
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: __builtin_setjmp/__builtin_longjmp Implementation Implementation
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: gcc errors - need help
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Query regarding, RTL Macros
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• __builtin_setjmp/__builtin_longjmp Implementation Implementation
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: gcc errors - need help
  • From: "Raman M" <m_raman_m@xxxxxxxxxxx>
• Re: PowerPc Cross Compile
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: gcc errors - need help
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Problem building GCC 4.1.1 on RHEL4
  • From: "Jon Earle" <jse@xxxxxxxxxxxxxxx>
• Re: GCC for Brew Applications!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: GCC for Brew Applications!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: GCC for Brew Applications!!!
  • From: tmike@xxxxxxxxxxxxxxxxx
• Re: GCC for Brew Applications!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• RE: libstdc++.so.6
  • From: "Rupert Wood" <me@xxxxxxxxx>
• RE: Problem building GCC 4.1.1 on RHEL4
  • From: "Rupert Wood" <me@xxxxxxxxx>
• Re: Problem building GCC 4.1.1 on RHEL4
  • From: "Jon Earle" <jse@xxxxxxxxxxxxxxx>
• Re: Problem building GCC 4.1.1 on RHEL4
  • From: "Jon Earle" <jse@xxxxxxxxxxxxxxx>
• Re: Problem building GCC 4.1.1 on RHEL4
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Problem building GCC 4.1.1 on RHEL4
  • From: "Jon Earle" <jse@xxxxxxxxxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: require for gcc and g++ compliers
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• Re: require for gcc and g++ compliers
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• PowerPc Cross Compile
  • From: none none <menwn@xxxxxxxxxxx>
• gcc errors - need help
  • From: "Raman M" <m_raman_m@xxxxxxxxxxx>
• require for gcc and g++ compliers
  • From: "EN ZHOU" <2339716@xxxxxxxxx>
• Re: AIX Cross compile on Mac OS X
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Moving long long int using inline asm
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: GCC for Brew Applications!!!
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: gcc exception handle
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Moving long long int using inline asm
  • From: "Mohamed Shafi" <shafitvm@xxxxxxxxx>
• GCC for Brew Applications!!!
  • From: aamir@xxxxxxxxxxxx
• Re: AIX Cross compile on Mac OS X
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: asm operand requires impossible reload
  • From: Lars Poeschel <larsi@xxxxxxxxxxxxxxxxx>
• AIX Cross compile on Mac OS X
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• Re: -Wunused don't warn for exit
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: asm operand requires impossible reload
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Problems compiling gcc for target alpha
  • From: "Ferad Zyulkyarov" <feradz@xxxxxxxxx>
• Re: Compiling GCC
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Compiling GCC
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Compiling GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Compiling GCC
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Compiling GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• bootstrap comparison failure
  • From: Christian Keil <c.keil@xxxxxxxxxxxxx>
• Re: Compiling GCC
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• Re: Compiling GCC
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Compiling GCC
  • From: "Paulo J. Matos" <pocm@xxxxxxxxxxx>
• -Wunused don't warn for exit
  • From: Gabriel Linder <linder@xxxxxxxxxxxxx>
• asm operand requires impossible reload
  • From: Lars Poeschel <larsi@xxxxxxxxxxxxxxxxx>
• gcc exception handle(continue)
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: typedef name question
  • From: David Fang <fang@xxxxxxxxxxxxxxx>
• C Preprocessor: Expected Declaration Specifiers
  • From: "Ryan Slominski" <ryan.slominski@xxxxxxxxx>
• help with gcc4.1.1 crosscompile and m68000 option
  • From: "Navin Anand" <anandnavin@xxxxxxxxx>
• gcc and profiling
  • From: disruptive <brettdonovan@xxxxxxxxx>
• Re: Renesas H8S
  • From: Name lastlong <brew_pt@xxxxxxxxx>
• RE: question about the -I option
  • From: maser rati <maseriyer@xxxxxxxxx>
• libstdc++.so.6
  • From: "Larry" <larrywyb@xxxxxxxxxxxxxxxxxxxx>
• Re: typedef name question
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• RE: gcc exception handle
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: gcc exception handle
  • From: Andrew Haley <aph@xxxxxxxxxx>
• RE: typedef name question
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• gcc exception handle
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: typedef name question
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: online doc on debugging formats?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: gcc 4.1.1: char *p = "str" puts "str" into rodata
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: gcc 4.1.1: char *p = "str" puts "str" into rodata
  • From: Denis Vlasenko <vda.linux@xxxxxxxxxxxxxx>
• Re: gcc 4.1.1: char *p = "str" puts "str" into rodata
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gcc 4.1.1: char *p = "str" puts "str" into rodata
  • From: Denis Vlasenko <vda.linux@xxxxxxxxxxxxxx>
• Re: gcc 4.1.1: char *p = "str" puts "str" into rodata
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: compiling xmmintrin.h
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: online doc on debugging formats?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• compiling xmmintrin.h
  • From: ranjith kumar <ranjit_kumar_b4u@xxxxxxxxxxx>
• Re: online doc on debugging formats?
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• less strict type checking within template code
  • From: andre maute <andre.maute@xxxxxx>
• online doc on debugging formats?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: warning: assignment makes pointer from integer without a cast
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• warning: assignment makes pointer from integer without a cast
  • From: "Manal Helal" <manalorama@xxxxxxxxx>
• Problems in building gcc 4.0.3
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• Re: MD file patterns and RTL templates
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• MD file patterns and RTL templates
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• RE: question about the -I option
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: question about the -I option
  • From: Dan Hipschman <dsh@xxxxxxxxxxxxxx>
• Re: question about the -I option
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• question about the -I option
  • From: maser rati <maseriyer@xxxxxxxxx>
• Re: C++ "export" keyword
  • From: Gabriel Dos Reis <gdr@xxxxxxxxxxx>
• RE: Can C and C++ object files be linked into an executable?
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: Can C and C++ object files be linked into an executable?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Can C and C++ object files be linked into an executable?
  • From: Ray Hurst <rhurst2@xxxxxxx>
• Re: Your E-Mail ID Verification
  • From: Ray Hurst <rhurst2@xxxxxxx>
• Renesas H8S
  • From: "Cucco Cristiano" <cristiano.cucco@xxxxxxxxxxxxxxxxxxxxxx>
• Re: C++ "export" keyword
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• C++ "export" keyword
  • From: "Peng Yu" <pengyu.ut@xxxxxxxxx>
• Re: define_split question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Building gcj with enable-libgcj-debug.
  • From: "R. Clayton" <clayton@xxxxxxxxxxxx>
• define_split question
  • From: Lars Poeschel <larsi@xxxxxxxxxxxxxxxxx>
• 4.0.3 warning
  • From: deanz1 <deanz1@xxxxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• Known problem with gcc 4.0.3 on sparc solaris throwing/catching exceptions in shared library?
  • From: "Glenn Serre" <serre@xxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: typedef name question
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: typedef name question
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: typedef name question
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: typedef name question
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: gcc-4.1.1 - build fail
  • From: Andrew Haley <aph@xxxxxxxxxx>
• gcc-4.1.1 - build fail
  • From: "BHASKAR G. REDDY" <bhaskar@xxxxxxxxxxxxxx>
• Fw: typedef name question
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Building gcc 2.8.1 on AIX 5.3
  • From: Chuck Noren <Chuck.Noren@xxxxxxxxx>
• Returning a reference to local function parameters
  • From: Steve Kreyer <steve.kreyer@xxxxxx>
• Re: cc1: out of memory
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• typedef name question
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• cc1: out of memory
  • From: Amine Chelghaf <amine_chelghaf@xxxxxxxx>
• bug in fr30 port
  • From: Lars Poeschel <larsi@xxxxxxxxxxxxxxxxx>
• making cross compiler soft float by default
  • From: Chris Steel <chriszaurus@xxxxxxxxxxx>
• Re: when is a double float nearest infinity ?
  • From: Christian Bruel <chrbr@xxxxxxx>
• Re: when is a double float nearest infinity ?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: when is a double float nearest infinity ?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: when is a double float nearest infinity ?
  • From: Christian Bruel <chrbr@xxxxxxx>
• when is a double float nearest infinity ?
  • From: Christian Bruel <chrbr@xxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Joezac Zachariah <joezac@xxxxxxxxxxx>
• Re: Printing heap
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Requirements for throwing C++ exceptions from one shared library to another in gcc 4.1.0 and gcc 3.2?
  • From: "Glenn Serre" <serre@xxxxxxxxx>
• Printing heap
  • From: "Kalinowski, Jeremy" <JKalinowski@xxxxxxxxxxxxxxxxx>
• RE: Calling conventions used by gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Calling conventions used by gcc
  • From: "Young, Michael" <Michael.Young@xxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: "Anders Schau Knatten" <anders@xxxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: "Anders Schau Knatten" <anders@xxxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Calling conventions used by gcc
  • From: "kanishk rastogi" <kanishk.85@xxxxxxxxx>
• Calling conventions used by gcc
  • From: "Anders Schau Knatten" <anders@xxxxxxxxxxx>
• Re: "if (i == n) ++i;" or "i += i == n;"?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• "if (i == n) ++i;" or "i += i == n;"?
  • From: Erik <sigra@xxxxxxx>
• Re: Getting a tree node for a field of a variable
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: configure gcc to build 32-bit binaries on x86_64
  • From: natasha@xxxxxxxx
• Re: GCC Cross Compilation Problem
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Re: Misalignment of local SSE variables in thread function
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: glibc version dependencies
  • From: "Michael T" <raselmsh@xxxxxxxxxxx>
• Re: gcc4.3 configuring problems with mpfr
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Re: Misalignment of local SSE variables in thread function
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• RE: Misalignment of local SSE variables in thread function
  • From: Danny Smith <dannysmith@xxxxxxxxxxxx>
• Re: Switching Compilers
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Switching Compilers
  • From: "Kalinowski, Jeremy" <JKalinowski@xxxxxxxxxxxxxxxxx>
• Re: a bug for __builtin_offsetof operator ?
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: a bug for __builtin_offsetof operator ?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• a bug for __builtin_offsetof operator ?
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Re: Re: Misalignment of local SSE variables in thread function
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: glibc version dependencies
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• glibc version dependencies
  • From: "Michael T" <raselmsh@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: gcc4.3 configuring problems with mpfr
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• GCC Cross Compilation Problem
  • From: Manish Baphna <manish_baphna@xxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• compile errors for include sys/socket.h
  • From: Franca <franca.delmastro@xxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• gcc4.3 configuring problems with mpfr
  • From: Marco Trudel <mtrudel@xxxxxx>
• Re: configure gcc to build 32-bit binaries on x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: gcj question.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: mysql-library
  • From: Artūras Moskvinas <arturas.moskvinas@xxxxxxxxx>
• Re: configure gcc to build 32-bit binaries on x86_64
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• mysql-library
  • From: "Jens Kamionka" <jkamionka@xxxxxx>
• Re: "Preprocess" dwarf info?
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• "Preprocess" dwarf info?
  • From: Fabian Cenedese <Cenedese@xxxxxxxx>
• Re: gcc 4.1.1 poor optimization
  • From: Greg Smith <gsmith@xxxxxxxxx>
• Re: gcc 4.1.1 poor optimization
  • From: Greg Smith <gsmith@xxxxxxxxx>
• configure gcc to build 32-bit binaries on x86_64
  • From: natasha@xxxxxxxx
• gcj question.
  • From: "R. Clayton" <clayton@xxxxxxxxxxxx>
• Regarding insn-attrtab.c file
  • From: "P. Pavan Kumar" <pavankumar@xxxxxxxxxxxxxx>
• pentium-DFA
  • From: "P. Pavan Kumar" <pavankumar@xxxxxxxxxxxxxx>
• Re: Misalignment of local SSE variables in thread function
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Misalignment of local SSE variables in thread function
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Cross Compilling for PowerPc from FreeBDS6.1
  • From: none none <idipous1@xxxxxxxx>
• gcc 4.1.1 --print-search-dirs questions
  • From: Paul Novak <pdnovak@xxxxxxxxxxx>
• Re: meaning of typedef ...and something more
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: meaning of typedef ...and something more
  • From: Joe Buck <Joe.Buck@xxxxxxxxxxxx>
• meaning of typedef ...and something more
  • From: "Laura Tardivo" <lauratardivo@xxxxxxxxxxxxxxxxxx>
• what defines the gcc array range notation "..."?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: #Pragma pack
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• #Pragma pack
  • From: "Kalinowski, Jeremy" <JKalinowski@xxxxxxxxxxxxxxxxx>
• Re: No Packing in GCC
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• No Packing in GCC
  • From: "Kalinowski, Jeremy" <JKalinowski@xxxxxxxxxxxxxxxxx>
• Re: g77=>gfortran ?
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: mystery linking failure
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: mystery linking failure
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• default arguments are only permitted for function parameters
  • From: Radoslaw Garbacz <rgarbacz@xxxxxxxx>
• g77=>gfortran ?
  • From: Martin Gruenewald <Martin.Grunewald@xxxxxxx>
• mystery linking failure
  • From: Nicholas Murphy <nmurphy@xxxxxxxxxxxxxxxxx>
• Re: Compilation error in gcc
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• Compilation error in gcc
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• Compilation error in gcc
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• Re: cross compiling for x86_64
  • From: "Indu Bhagat" <bhagat.indu@xxxxxxxxx>
• Re: instruction-space modification
  • From: Andrew Haley <aph@xxxxxxxxxx>
• instruction-space modification
  • From: "Gerard Visser" <visser.gerard@xxxxxxxxx>
• Re: best practices on gcc building host tool for cross arch
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• RE: best practices on gcc building host tool for cross arch
  • From: "T Michael Turney" <tmike@xxxxxxxxxxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Joezac Zachariah <joezac@xxxxxxxxxxx>
• Re: How to ignore Wall errors for a portion of code
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• RE: Objects tied in by Linker
  • From: "Lehner, Michael" <michaellehner@xxxxxxxxxxx>
• How to ignore Wall errors for a portion of code
  • From: Joezac Zachariah <joezac@xxxxxxxxxxx>
• Re: C compiler
  • From: Hugh Sasse <hgs@xxxxxxxxx>
• Re: Question about gcc -pthread option
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• Re: gcc 4.1.1 -M bug?
  • From: Hiroki Kaminaga <kaminaga@xxxxxxxxxxxxx>
• Re: best practices on gcc building host tool for cross arch
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• I want to ask a problem about libgcc.a and -fPIC
  • From: "chenyin" <chenyin@xxxxxxxxxxxxxxx>
• RE: error while preprocessing on x86 with -std
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: Errors cross compiling gcc 4.1.1 for i686-linux-pc
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Errors cross compiling gcc 4.1.1 for i686-linux-pc
  • From: Klaus Nji <makaveli_0000@xxxxxxxxx>
• Re: error while preprocessing on x86 with -std
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• C compiler
  • From: "Berg, Michelle D." <MDTRUEBLOOD@xxxxxxxxxxxx>
• RE: error while preprocessing on x86 with -std
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: gfortran for 77 codes
  • From: Toon Moene <toon@xxxxxxxxxxxxxxxxxxxx>
• RE: error while preprocessing on x86 with -std
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: error while preprocessing on x86 with -std
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• RE: error while preprocessing on x86 with -std
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• error while preprocessing on x86 with -std
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• best practices on gcc building host tool for cross arch
  • From: tmike@xxxxxxxxxxxxxxxxx
• Re: gfortran for 77 codes
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• Re: gfortran for 77 codes
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• error when porting from g++ for hp-ux to g++ for linux
  • From: "Puetz, Oliver P11M22" <Puetz.Oliver@xxxxxxxxxxx>
• Re: Objects tied in by Linker
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Objects tied in by Linker
  • From: "Lehner, Michael" <michaellehner@xxxxxxxxxxx>
• RE: pasting x amd x does not give a valid preprocessing token
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: pasting x amd x does not give a valid preprocessing token
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: TREE data structure
  • From: Andrew Haley <aph@xxxxxxxxxx>
• pasting x amd x does not give a valid preprocessing token
  • From: Divya Shresth <divya_shresth@xxxxxxxxx>
• Re: TREE data structure
  • From: "manish manish" <compilerguru@xxxxxxxxx>
• Re: gcc on 64 bits machine
  • From: Tim Prince <tprince@xxxxxxxxxxxxx>
• Re: Question about gcc -pthread option
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: gcc inline assembly for sparc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Requirements for throwning C++ exceptions from one shared library to another in gcc 4.1.0?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Question about gcc -pthread option
  • From: Paul Joselow <pjoselow@xxxxxxxxxxxxx>
• RE: proper use of __attribute__((visibility("hidden")))
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• proper use of __attribute__((visibility("hidden")))
  • From: Jeffrey Holle <jeffreyholle@xxxxxxxxxxxxx>
• Re: Requirements for throwning C++ exceptions from one shared library to another in gcc 4.1.0?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• gcc inline assembly for sparc
  • From: dave77 <zhu_dave@xxxxxxxxx>
• gcc on 64 bits machine
  • From: "ying lcs" <yinglcs@xxxxxxxxx>
• Re: Just the "compile" button
  • From: Dave Williss <dwilliss@xxxxxxxxxxxxxxx>
• Re: Cross compiler usage help
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• RE: Requirements for throwning C++ exceptions from one shared library to another in gcc 4.1.0?
  • From: "Glenn Serre" <serre@xxxxxxxxx>
• Re: Making gcc read from the standard input
  • From: Mike Stump <mrs@xxxxxxxxx>
• Re: Cross compiler usage help
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: Objects tied in by Linker
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Objects tied in by Linker
  • From: "Lehner, Michael" <michaellehner@xxxxxxxxxxx>
• Re: Just the "Compile" button!
  • From: Tony Wetmore <tony.wetmore@xxxxxxxxxxxx>
• Re: gcc 4.1.1 -M bug?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Flag to Stop Implicit Conversion
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Making gcc read from the standard input
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Requirements for throwning C++ exceptions from one shared library to another in gcc 4.1.0?
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: Just the "compile" button
  • From: John Jackson <strangetruther@xxxxxxxxx>
• Re: Just the "Compile" button!
  • From: Glen Beane <glen.beane@xxxxxxx>
• Re: Just the "Compile" button!
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Just the "Compile" button!
  • From: John Jackson <strangetruther@xxxxxxxxx>
• Re: TREE data structure
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Cross compiler usage help
  • From: "Deepak Barua" <dbbarua@xxxxxxxxx>
• Re: Making gcc read from the standard input
  • From: Paolo Bonzini <paolo.bonzini@xxxxxxxxxxx>
• gcc 4.1.1 -M bug?
  • From: Hiroki Kaminaga <kaminaga@xxxxxxxxxxxxx>
• Requirements for throwning C++ exceptions from one shared library to another in gcc 4.1.0?
  • From: "Glenn Serre" <serre@xxxxxxxxx>
• Making gcc read from the standard input
  • From: "Tathagato Rai Dastidar" <Tathagato.Rai.Dastidar@xxxxxxx>
• TREE data structure
  • From: "manish manish" <compilerguru@xxxxxxxxx>
• gcc problem for help
  • From: 王 刚伟 <gwwang10@xxxxxxxxxxx>
• Re: gcc 4.1.1 poor optimization
  • From: Greg Smith <gsmith@xxxxxxxxx>
• Re: Flag to Stop Implicit Conversion
  • From: "Roopesh Varier" <rvarier@xxxxxxxxx>
• Re: gcc 4.1.1 poor optimization
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gcc 4.1.1 poor optimization
  • From: Greg Smith <gsmith@xxxxxxxxx>
• Sparc with no windows
  • From: omer <omer.medan@xxxxxxxxx>
• Re: Solaris 9 x86 libc_name_p?
  • From: "Chayim I. Kirshen" <chayim@xxxxxxxxxxxx>
• Re: Solaris 9 x86 libc_name_p?
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: Problem building g++ 4.1.1 on Cygwin
  • From: Dave Yost <Dave@xxxxxxxx>
• Re: Problem building g++ 4.1.1 on Cygwin
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Solaris 9 x86 libc_name_p?
  • From: "Chayim I. Kirshen" <chayim@xxxxxxxxxxxx>
• Re: Problem building g++ 4.1.1 on Cygwin
  • From: Dave Yost <Dave@xxxxxxxx>
• Re: libstdc++.so: undefined reference to `___tls_get_addr'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: libstdc++.so: undefined reference to `___tls_get_addr'
  • From: "marco turchi" <marco.turchi@xxxxxxxxx>
• Re: libstdc++.so: undefined reference to `___tls_get_addr'
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Complex functions
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• libstdc++.so: undefined reference to `___tls_get_addr'
  • From: "marco turchi" <marco.turchi@xxxxxxxxx>
• Re: Undefined References to functions
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Undefined References to functions
  • From: Syam Prasad Nagabairu <snagabairu@xxxxxxxxxxxx>
• gfortran for 77 codes
  • From: Attila Kocsis <kocsisatis@xxxxxxxxx>
• Complex functions
  • From: "VijayAnand" <vijayanand@xxxxxxxxx>
• Re: Problem building g++ 4.1.1 on Cygwin
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Problem building g++ 4.1.1 on Cygwin
  • From: Dave Yost <Dave@xxxxxxxx>
• Compiler Directives for Suppressing Warnings
  • From: MSUdom5 <dom5@xxxxxxxxxxx>
• Re: "#" directive affects compilation ?
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• "#" directive affects compilation ?
  • From: "Michael Gong" <mwgong@xxxxxxxxxxxxxx>
• Since which version does gcc (ia64) support __float80?
  • From: Martin Wiechert <martin.wiechert@xxxxxx>
• Re: Problems with double arguments to varargs on MIPS
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: template instantiation problem with g++ 4.1
  • From: Egon Kocjan <egon@xxxxxxxxxxx>
• Re: gcc-4.1.1: default enabled stack-protector does not work
  • From: Alvaro Vega Garcia <avg07@xxxxxx>
• Re: bad user, or optimization bug with worked-around lvalue casts ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: bad user, or optimization bug with worked-around lvalue casts ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• Re: Problems with double arguments to varargs on MIPS
  • From: Simon Kagstrom <simon.kagstrom@xxxxxx>
• Problems with double arguments to varargs on MIPS
  • From: Simon Kagstrom <simon.kagstrom@xxxxxx>
• don't know how compiler supports IEEE math on debian alpha port
  • From: Steffen.Pelzetter@xxxxxxxxxx
• Re: bad user, or optimization bug with worked-around lvalue casts ?
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: bad user, or optimization bug with worked-around lvalue casts ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• gcc-4.1.1: default enabled stack-protector does not work
  • From: Steffen Wendzel <cdp_xe@xxxxxxx>
• template instantiation problem with g++ 4.1
  • From: Egon Kocjan <egon@xxxxxxxxxxx>
• Re: bad user, or optimization bug with worked-around lvalue casts ?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• bad user, or optimization bug with worked-around lvalue casts ?
  • From: Michael Haubenwallner <michael.haubenwallner@xxxxxxxxxx>
• Re: cross compiling for x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Default 32 bit output
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Re: How to suppress the generation of float point instructions?
  • From: Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx>
• How to suppress the generation of float point instructions?
  • From: "Ender.Dai" <ender.dai@xxxxxxxxx>
• Re: Re: cross compiling for x86_64
  • From: "Timothy C Prince" <tprince@xxxxxxxxxxxxx>
• Re: cross compiling for x86_64
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: libgcc_s
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• libgcc_s
  • From: Perry Smith <pedz@xxxxxxxxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: cross compiling for x86_64
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Paul Smith <psmith@xxxxxxxxxxx>
• cross compiling for x86_64
  • From: "Indu Bhagat" <bhagat.indu@xxxxxxxxx>
• Re: I need help building a powerpc-unknown-eabispe cross compiler
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Re: Understanding __attribute__((always_inline)) and optimization options
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Understanding __attribute__((always_inline)) and optimization options
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Understanding __attribute__((always_inline)) and optimization options
  • From: Daniel Lohmann <daniel.lohmann@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Paul Smith <psmith@xxxxxxxxxxx>
• Re: Really unoptimized ARM (and Thumb) code generated by GCC 4.1.1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Really unoptimized ARM (and Thumb) code generated by GCC 4.1.1
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Paul Smith <psmith@xxxxxxxxxxx>
• Re: Really unoptimized ARM (and Thumb) code generated by GCC 4.1.1
  • From: Mick CORNUT <mick_cornut@xxxxxxxx>
• problems with execinfo.h
  • From: suka <mbouna@xxxxxxxxxxxxxxxxx>
• Re: How to choose the right libstdc++.so with soft-float?
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: gfortran, patch for argument list functions %VAL, %LOC and %REF
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• Re: potential problems with malloc and calloc
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• potential problems with malloc and calloc
  • From: David Joseph Adrian <adriand@xxxxxxx>
• How to choose the right libstdc++.so with soft-float?
  • From: Paul Smith <psmith@xxxxxxxxxxx>
• Re: sun-sparc-solaris9 fixinclude probs.
  • From: Hugh Sasse <hgs@xxxxxxxxx>
• Re: A simple program with a large array segfaults
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: sun-sparc-solaris9 fixinclude probs.
  • From: Hugh Sasse <hgs@xxxxxxxxx>
• Re: sun-sparc-solaris9 fixinclude probs.
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• gfortran, patch for argument list functions %VAL, %LOC and %REF
  • From: "Poulsen, Karsten Bo" <KarstenBo.Poulsen@xxxxxxxxxxxx>
• sun-sparc-solaris9 fixinclude probs.
  • From: Hugh Sasse <hgs@xxxxxxxxx>
• Re: Problem building g77 configured with gnu as and ld
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• Problem building g77 configured with gnu as and ld
  • From: "Shin, John Y CONTRACTOR WRAIR-Wash DC" <John.Shin@xxxxxxxxxxxxxx>
• Re: Compiler settings of gcc 4.1.2 to achieve fast compile times as with gcc-2.95
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Compiler settings of gcc 4.1.2 to achieve fast compile times as with gcc-2.95
  • From: "M. Koehrer" <mathias_koehrer@xxxxxxxx>
• how to static link a lib
  • From: "hbeaumont hbeaumont" <ahlist@xxxxxxxxx>
• Re: I need help building a powerpc-unknown-eabispe cross compiler
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• Linking problems with gcc and AIX
  • From: David Edelsohn <dje@xxxxxxxxxxxxxx>
• I need help building a powerpc-unknown-eabispe cross compiler
  • From: Rask Ingemann Lambertsen <rask@xxxxxxxxxx>
• FW: how do I link a C function with a gfortran program
  • From: jimmie.davis@xxxxxxxxxx
• Re: GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: "John Doe" <johndoe2325@xxxxxxxxx>
• Re: Fw: How to Port 32bit source code in compatible to 64bit OS
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: Fw: How to Port 32bit source code in compatible to 64bit OS
  • From: Syam Prasad Nagabairu <snagabairu@xxxxxxxxxxxx>
• Re: Fw: How to Port 32bit source code in compatible to 64bit OS
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: FW: How do I link a C function with a gFortran program
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• How to Port 32bit source code in compatible to 64bit OS
  • From: Syam Prasad Nagabairu <snagabairu@xxxxxxxxxxxx>
• Fw: How to Port 32bit source code in compatible to 64bit OS
  • From: Syam Prasad Nagabairu <snagabairu@xxxxxxxxxxxx>
• FW: How do I link a C function with a gFortran program
  • From: "Sherman" <shermand@xxxxxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: "John Doe" <johndoe2325@xxxxxxxxx>
• Re: Default 32 bit output
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: David Mebane <david.mebane@xxxxxxxxxxxxxx>
• Re: Default 32 bit output
  • From: Artūras Moskvinas <arturas.moskvinas@xxxxxxxxx>
• Re: Default 32 bit output
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• GCC 4.1.0 vs 3.4.3 Compile Issue
  • From: "John Doe" <johndoe2325@xxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: DCH <david@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• Re: add/assign problem, part 2.
  • From: DCH <david@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• add/assign problem, part 2.
  • From: David Mebane <david.mebane@xxxxxxxxxxxxxx>
• Re: strange problem with "plus-equals"
  • From: Andrew Haley <aph@xxxxxxxxxxx>
• strange problem with "plus-equals"
  • From: David Mebane <david.mebane@xxxxxxxxxxxxxx>
• Re: help....
  • From: "Dima Sorkin" <dima.sorkin@xxxxxxxxx>
• RE: Help for shared library(Sun CC and GCC)
  • From: "Zhao Li,SCNB R&D NC(BJ)" <zhaoli@xxxxxxxxxxx>
• Re: Help for shared library(Sun CC and GCC)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: Help for shared library(Sun CC and GCC)
  • From: "Zhao Li,SCNB R&D NC(BJ)" <zhaoli@xxxxxxxxxxx>
• Re: Strange const warning
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: Strange const warning
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Help for shared library(Sun CC and GCC)
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Re: Gprof and shared libraries
  • From: Bud Davis <bdavis9659@xxxxxxxxxxxxx>
• Strange const warning
  • From: Jonathan Kinsey <jon_kinsey@xxxxxxxxxxx>
• Re: how gcc -I works?
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• how gcc -I works?
  • From: "xu zhou" <zhouxuzhu1985@xxxxxxxxx>
• Help for shared library(Sun CC and GCC)
  • From: "Zhao Li,SCNB R&D NC(BJ)" <zhaoli@xxxxxxxxxxx>
• Re: help!!
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• RE: program with various files be compiled
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• RE: Compilation error while return function pointers
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• RE: Default 32 bit output
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• Re: help....
  • From: "manish manish" <compilerguru@xxxxxxxxx>
• Re: Default 32 bit output
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Fwd: gcc IDE
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Re: gcc IDE
  • From: Erik <sigra@xxxxxxx>
• gcc IDE
  • From: Bam_Zam <bamdadzamini@xxxxxxxxx>
• Re: Default 32 bit output
  • From: Darryl Miles <darryl-mailinglists@xxxxxxxxxxxx>
• Re: Default 32 bit output
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Re: Default 32 bit output
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Re: Re: Output of (estimated) remaining compile time for huge source files
  • From: "M. Koehrer" <mathias_koehrer@xxxxxxxx>
• Re: Default 32 bit output
  • From: "kanishk rastogi" <kanishk.85@xxxxxxxxx>
• Default 32 bit output
  • From: "Domen Vrankar" <domen.vrankar@xxxxxxxxx>
• Compilation error while return function pointers
  • From: Purnendu <purnendu@xxxxxxxxx>
• program with various files be compiled
  • From: alexandre_serra <alexandre_serra@xxxxxxxxx>
• RE: Help installing GCC on to from-scratch system
  • From: "mhuffaker@xxxxxxxxxxxxxx" <mhuffaker@xxxxxxxxxxxxxx>
• help!!
  • From: "manish manish" <compilerguru@xxxxxxxxx>
• Re: GUI programming
  • From: Michael Eager <eager@xxxxxxxxxxxx>
• Re: Help installing GCC on to from-scratch system
  • From: Artūras Moskvinas <arturas.moskvinas@xxxxxxxxx>
• Help installing GCC on to from-scratch system
  • From: Jonathon Keogh <jonathon@xxxxxxxxxxxxxxxx>
• Re: info files under windows
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: Yet another aliasing question.
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: Yet another aliasing question.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Yet another aliasing question.
  • From: Sergei Organov <osv@xxxxxxxxx>
• Re: info files under windows
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• info files under windows
  • From: "Yi Tang" <yitang@xxxxxxxxxxxxxx>
• Re: Output of (estimated) remaining compile time for huge source files
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• RE: GUI programming
  • From: "John \(Eljay\) Love-Jensen" <eljay@xxxxxxxxx>
• GUI programming
  • From: "Tushar kant" <tusharkant15@xxxxxxxxx>
• Re: aligned attribute
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• ARM startup file
  • From: "Kristijan Gortan" <kristijan.gortan@xxxxxxxxx>
• Re: aligned attribute
  • From: Andrew Haley <aph@xxxxxxxxxx>
• Re: Fw: About the precision of cos() sin() and tan() function differ from glibs and fdlibm.
  • From: Andrew Haley <aph@xxxxxxxxxx>
• help....
  • From: "Manish Agarwal, Noida" <MANISH.AGRL@xxxxxx>
• Re: mingw help!!!
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Output of (estimated) remaining compile time for huge source files
  • From: "M. Koehrer" <mathias_koehrer@xxxxxxxx>
• Fw: About the precision of cos() sin() and tan() function differ from glibs and fdlibm.
  • From: "firstbt" <firstbt@xxxxxxxxx>
• Re: Initialization of zero globals
  • From: Ian Lance Taylor <iant@xxxxxxxxxx>
• Initialization of zero globals
  • From: Alexander Grobman <agrobman@xxxxxxxxx>
• Re: mingw help!!!
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: Syntax error when building gfortran in gcc-4.0.3
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: aligned attribute
  • From: Maurizio Vitale <maurizio.vitale@xxxxxxxxxxxxxxxxxxxxxx>
• Re: aligned attribute
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: aligned attribute
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: "Woodcrest" Xeon 3.0ghz optimal -march and options???
  • From: Tim Prince <timothyprince@xxxxxxxxxxxxx>
• Re: to reduce footprint
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• Re: mingw help!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: to reduce footprint
  • From: Lin George <george4academic@xxxxxxxxx>
• Re: to reduce footprint
  • From: John Love-Jensen <eljay@xxxxxxxxx>
• loop vectorization vs. sequential code vectorization
  • From: Vaclav SMILAUER <eudoxos@xxxxxxxx>
• __thread storage specifier documentation
  • From: Roger Ferrer Ibáñez <roger.ferrer@xxxxxx>
• Re: mingw help!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• Re: mingw help!!!
  • From: Kai Ruottu <karuottu@xxxxxxxx>
• mingw help!!!
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: gcc core gcc++
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• Re: abi compatibility
  • From: Brian Dessent <brian@xxxxxxxxxxx>
• gcc core gcc++
  • From: alexandre_serra <alexandre_serra@xxxxxxxxx>
• Re: abi compatibility
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Re: gcc version number from autotools
  • From: Bob Rossi <bob_rossi@xxxxxxx>
• Syntax error when building gfortran in gcc-4.0.3
  • From: "Shin, John Y CONTRACTOR WRAIR-Wash DC" <John.Shin@xxxxxxxxxxxxxx>