GCC 3.4 Release SeriesChanges, New Features, and Fixes
The final release in the 3.4 release series is
The series is now closed.
GCC 3.4 has .
Before reporting a bug, please make sure it's really GCC,
and not your code, that is broken.
GNU Make is now required to build GCC.
With -nostdinc the preprocessor used to ignore
both standard include paths and include paths
contained in environment variables.
It was neither documented
nor intended that environment variable paths be ignored, so
this has been corrected.
GCC no longer accepts the options -fvolatile,
-fvolatile-global and -fvolatile-static.
It is unlikely that they worked correctly in any 3.x release.
GCC no longer ships &varargs.h&.
&stdarg.h& instead.
Support for all the systems obsoleted in
GCC 3.3 has been removed from GCC 3.4.
See below for a
GCC now requires an ISO C90 (ANSI C89) C compiler to build.
K&R C compilers will not work.
The implementation of the .
As a result, the code generated for certain MIPS
targets will not be binary compatible with earlier releases.
In previous releases, the MIPS port had a fake "hilo" register
with the user-visible name accum.
This register
has been removed.
The implementation of the .
As a result, the code generated will not be binary
compatible with earlier releases in certain cases.
The configure option --enable-threads=pthreads has
use --enable-threads=posix instead,
which should have the same effect.
Code size estimates used by inlining heuristics for C, Objective-C, C++
and Java have been redesigned significantly.
As a result the parameters
of -finline-insns,
--param max-inline-insns-single
and --param max-inline-insns-auto need to be
reconsidered.
--param max-inline-slope
and --param min-inline-insns
they are not needed for the new bottom-up inlining
heuristics.
The new unit-at-a-time compilation scheme has several compatibility
The order in which functions, variables, and top-level
asm statements are emitted may have changed.
relying on some particular ordering needs to be updated.
majority of such top-level asm statements can be replaced by section
attributes.
Unreferenced static variables and functions are removed.
This may result in undefined references when an asm
statement refers to the variable/function directly.
case either the variable/function shall be listed in asm statement
operand or in the case of top-level asm statements the attribute
used shall be used to force function/variable to be
always output and considered as a possibly used by unknown code.
For variables the attribute is accepted only by GCC 3.4 and newer,
while for earlier versions it is sufficient to use
unused to silence warnings about the variables not being
referenced.
To keep code portable across different GCC versions, you can use
appropriate preprocessor conditionals.
Static functions now can use non-standard passing conventions that may
break asm statements calling functions directly.
the attribute used shall be used to prevent this
As a temporary workaround, -fno-unit-at-a-time can be used,
but this scheme may not be supported by future releases of GCC.
GCC 3.4 automatically places zero-initialized variables in
the .bss section on some operating systems.
Versions of GNU Emacs up to (and including) 21.3 will not work
correctly when usi you can use
-fno-zero-initialized-in-bss to disable it.
If GCC 3.4 is configured with --enable-threads=posix
(the default on most targets that support pthreads) then
_REENTRANT will be defined unconditionally by
some libstdc++ headers. C++ code which relies on that macro to
detect whether multi-threaded code is being compiled might
change in meaning, possibly resulting in linker errors for
single-threaded programs.
Affected users of
compile single-threaded code with -DBOOST_DISABLE_THREADS.
See Bugzilla for
General Optimizer Improvements
Usability of the profile feedback and coverage testing has been improved.
Performance of profiled programs has been improved by faster profile
merging code.
Better use of the profile feedback for optimization (loop unrolling
and loop peeling).
File locking support allowing fork() calls and parallel
runs of profiled programs.
Coverage file format has been redesigned.
gcov coverage tool has been improved.
make profiledbootstrap available to build a faster
Experiments made on i386 hardware showed an 11% speedup on
-O0 and a 7.5% speedup on -O2 compilation of a
New value profiling pass enabled via
-fprofile-values
New value profile transformations pass enabled via -fvpt
aims to optimize some code sequences by exploiting knowledge about
value ranges or other properties of the operands.
At the moment a
conversion of expensive divisions into cheaper operations has been
implemented.
New -fprofile-generate and -fprofile-use
command-line options to simplify the use of profile feedback.
A new unit-at-a-time compilation scheme for C, Objective-C, C++ and
Java which is enabled via -funit-at-a-time (and implied by
In this scheme a whole file is parsed first and
optimized later.
The following basic inter-procedural optimizations
are implemented:
Removal of unreachable functions and variables
Discovery of local functions (functions with static linkage whose
address is never taken)
On i386, these local functions use register parameter passing
conventions.
Reordering of functions in topological order of the call graph to
enable better propagation of optimizing hints (such as the stack
alignments needed by functions) in the back end.
Call graph based out-of-order inlining heuristics which allows to
limit overall compilation unit growth (--param
inline-unit-growth).
Overall, the unit-at-a-time scheme produces a 1.3% improvement for the
SPECint2000 benchmark on the i386 architecture (AMD Athlon CPU).
More realistic code size estimates used by inlining for C, Objective-C,
C++ and Java.
The growth of large functions can now be limited via
--param large-function-insns
and --param large-function-growth.
A new cfg-level loop optimizer pass replaces the old loop unrolling
pass and adds two other loop transformations -- loop peeling and loop
unswitching -- and also uses the profile feedback to limit code growth.
(The three optimizations are enabled by -funroll-loops,
-fpeel-loops and -funswitch-loops flags,
respectively).
The old loop unroller still can be enabled by
-fold-unroll-loops and may produce better code in some
cases, especially when the webizer optimization pass is not
A new web construction pass enabled via -fweb (and implied
by -O3) improves the quality of register allocation, CSE,
first scheduling pass and some other optimization passes by avoiding
re-use of pseudo registers with non-overlapping live ranges.
almost always improves code quality but does make debugging difficult
and thus is not enabled by default by -O2
The pass is especially effective as cleanup after code duplication
passes, such as the loop unroller or the tracer.
Experimental implementations of superblock or trace scheduling in the
second scheduling pass can be enabled via
-fsched2-use-superblocks and
-fsched2-use-traces, respectively.
New Languages and Language specific improvements
The Ada front end has been updated to include numerous
bug fixes and enhancements.
These include:
Improved project file support
Additional set of warnings about potential wrong code
Improved error messages
Improved code generation
Improved cross reference information
Improved inlining
Better run-time check elimination
Better error recovery
More efficient implementation of unbounded strings
Added features in GNAT.Sockets,
GNAT.OS_Lib, GNAT.Debug_Pools, ...
New GNAT.xxxx packages (e.g. GNAT.Strings,
GNAT.Exception_Action)
New pragmas
New -gnatS switch replacing gnatpsta
Implementation of new Ada features (in particular limited with,
limited aggregates)
C/Objective-C/C++
Precompiled headers are now supported.
Precompiled headers
can dramatically speed up compilation of some projects.
are some known defects in the current precompiled header
implementation that will result in compiler crashes in
relatively rare situations.
Therefore, precompiled headers
should be considered a &technology preview& in this
Read the manual for details about how to use
precompiled headers.
File handling in the preprocessor has been rewritten.
longer gets confused by symlinks and hardlinks, and now has
a correct implementation of #import and
#pragma once.
These two directives have therefore been un-deprecated.
The undocumented extension that allowed C programs to have a
label at the end of a compound statement, which has been
deprecated since GCC 3.0, has been removed.
The cast-as-lvalue extension has been removed for C++ and
deprecated for C and Objective-C.
In particular,
code like this:
(char) i = 5;
((int *) p)++;
is no longer accepted for C++ and will not be accepted for
C and Objective-C in a future version.
The conditional-expression-as-lvalue extension has been
deprecated for C and Objective-C.
In particular, code like
(a ? b : c) = 2;
will not be accepted for C and Objective-C in a future
The compound-expression-as-lvalue extension has been
deprecated for C and Objective-C.
In particular, code like
(a, b) = 2;
will not be accepted for C and Objective-C in a future
version. A possible non-intrusive workaround is the following:
(*(a, &b)) = 2;
such as __builtin_popcount
for counting bits, finding the highest and lowest bit in a
word, and parity have been added.
The -fwritable-strings option has been deprecated
and will be removed.
Many C math library functions are now recognized as built-ins and
optimized.
The C, C++, and Objective-C compilers can now handle source files
written in any character encoding supported by the host C library.
The default input character set is taken from the current locale,
and may be overridden with the -finput-charset command
line option.
In the future we will add support for inline encoding
G++ is now much closer to full conformance to
the ISO/ANSI C++ standard. This means, among other things, that a lot
of invalid constructs which used to be accepted in previous versions
will now be rejected. It is very likely that existing C++ code will
need to be fixed. This document lists some of the most common
A hand-written recursive-descent C++ parser has replaced the
YACC-derived C++ parser from previous GCC releases.
parser contains much improved infrastructure needed for better
parsing of C++ source codes, handling of extensions, and clean
separation (where possible) between proper semantics analysis
and parsing.
The new parser fixes many bugs that were found
in the old parser.
You must now use the typename and
template keywords to disambiguate dependent names,
as required by the C++ standard.
struct K {
typedef int mytype_t;
template &class T1& struct A {
template &class T2& struct B {
void callme(void);
template &int N& void bar(void)
// Use 'typename' to tell the parser that T1::mytype_t names
a type. This is needed because the name is dependent (in
this case, on template parameter T1).
typename T1::mytype_
template &class T& void template_func(void)
// Use 'template' to prefix member templates within
dependent types (a has type A&T&, which depends on
the template parameter T).
a.template bar&0&();
// Use 'template' to tell the parser that B is a nested
template class (dependent on template parameter T), and
'typename' because the whole A&T&::B&int& is
the name of a type (again, dependent).
typename A&T&::template B&int&
b.callme();
void non_template_func(void)
// Outside of any template class or function, no names can be
dependent, so the use of the keyword 'typename' and 'template'
is not needed (and actually forbidden).
a.bar&0&();
A&K&::B&float&
b.callme();
In a template definition, unqualified names will no longer
find members of a dependent base (as specified by [temp.dep]/3
in the C++ standard). For example,
template &typename T& struct B {
template &typename T& struct C : B&T& {
m = 0; // error
n = 0; // ::n is modified
// ::g is called
You must make the names dependent, e.g. by prefixing them
with this-&. Here is the corrected definition
of C&T&::h,
template &typename T& void C&T&::h ()
this-&m = 0;
this-&f ();
this-&n = 0
this-&g ();
As an alternative solution (unfortunately not backwards
compatible with GCC 3.3), you may use using
declarations instead of this-&:
template &typename T& struct C : B&T& {
using B&T&::m;
using B&T&::f;
using B&T&::n;
using B&T&::g;
In templates, all non-dependent names are now looked up and bound
at definition time (while parsing the code), instead of later when
the template is instantiated. For instance:
void foo(int);
template &int& struct A {
static void bar(void){
void foo(char);
int main()
A&0&::bar();
// Calls foo(int), used to call foo(char).
In an explicit instantiation of a class template, you must use
class or struct before the template-id:
template &int N&
class A {};
template A&0&;
// error, not accepted anymore
template class A&0&;
The "named return value" and "implicit typename"
extensions have been removed.
Default arguments in function types have been deprecated and
will be removed.
ARM-style name-injection of friend declarations has been
deprecated and will be removed.
For example:
struct S {
friend void f();
void g() { f(); }
will not be accepted by future versions of G++; instead a
declaration of "f" will need to be present outside of the
scope of "S".
Covariant returns are implemented for all but varadic
functions that require an adjustment.
When -pedantic is used, G++ now issues errors about spurious
semicolons. For example,
namespace N {}; // Invalid semicolon.
void f() {}; // Invalid semicolon.
G++ no longer accepts attributes for a declarator after the
initializer associated with that declarator.
For example,
X x(1) __attribute__((...));
is no longer accepted.
Instead, use:
X x __attribute__((...)) (1);
Inside the scope of a template class, the name of the class
itself can be treated as either a class or a template.
GCC used to accept the class name as argument of type template,
and template template parameter.
However this is not C++ standard
compliant.
Now the name is not treated as a valid template template
argument unless you qualify the name by its scope.
For example,
the code below no longer compiles.
template &template &class& class TT& class X {};
template &class T& class Y {
X&Y& // Invalid, Y is always a type template parameter.
The valid code for the above example is
X& ::Y& // Valid.
(Notice the space between & and : to
prevent GCC to interpret this as a digraph for
Friend declarations that refer to template specializations are
rejected if the template has not already been declared. For example,
template &typename T&
friend void f&& (C&);
is rejected. You must first declare f as a
template &typename T&
void f(T);
In case of friend declarations, every name used in the friend
declaration must be accessible at the point of that declaration.
Previous versions of G++ used to be less strict about this and
allowed friend declarations for private class members,
for example.
See the ISO C++ Standard Committee's defect
report #209 for details.
Declaration of member functions of class templates as friends are
supported.
For example,
template &typename T& struct A {
template &typename T& friend void A&T&::f();
You must use template && to introduce template
specializations, as required by the standard.
For example,
template &typename T&
struct S&int& { };
is rejected. You must write,
template && struct S&int& {};
G++ used to accept code like this,
struct S {
void f(int i = g());
int g(int i = h());
This behavior is not mandated by the standard. Now G++ issues
an error about this code.
To avoid the error, you must move
the declaration of g before the declaration of
The default arguments for g must
be visible at the point where it is called.
The C++ ABI Section 3.3.3 specifications for the array
construction routines __cxa_vec_new2 and
__cxa_vec_new3 were changed to return
NULL when the allocator argument returns
These changes are incorporated into the
libstdc++ runtime library.
Using a name introduced by a typedef in a friend declaration or in an
explicit instantiation is now rejected, as specified by the ISO C++
typedef A B;
friend class B;
// error, no typedef name here
// error, friend always needs class/struct/enum
friend class A;
template &int& class Q {};
typedef Q&0& R;
template class R;
// error, no typedef name here
template class Q&0&;
When allocating an array with a new expression, GCC used to allow
parentheses around the type name. This is actually ill-formed and it is
now rejected:
int* a = new (int)[10];
// error, not accepted anymore
int* a = new int[10];
When binding an rvalue of class type to a reference, the copy
constructor of the class must be accessible. For instance, consider
the following code:
A(const A&);
// private copy ctor
A makeA(void);
void foo(const A&);
void bar(void)
// error, copy ctor is not accessible
foo(makeA());
// error, copy ctor is not accessible
// OK, a1 is a lvalue
This might be surprising at first sight, especially since most
popular compilers do not correctly implement this rule
When forming a pointer to member or a pointer to member function,
access checks for class visibility (public, protected, private)
are now performed using the qualifying scope of the name itself.
This is better explained with an example:
void pub_func();
protected:
void prot_func();
void priv_func();
class B : public A
void foo()
// OK, pub_func is accessible through A
// error, cannot access prot_func through A
// error, cannot access priv_func through A
// OK, pub_func is accessible through B
// OK, can access prot_func through B (within B)
// error, cannot access priv_func through B
Runtime Library (libstdc++)
Optimization work:
Streamlined streambuf, filebuf, separate
synched with C Standard I/O streambuf.
All formatted I/O now uses cached locale information.
STL optimizations (memory/speed for list, red-black trees as used
by sets and maps).
More use of GCC builtins.
String optimizations (avoid contention on increment/decrement-and-test
of the reference count in the empty-string object, constructor from
input_iterators speedup).
Static linkage size reductions.
Large File Support (files larger than 2 GB on 32-bit systems).
Wide character and variable encoding filebuf work
(UTF-8, Unicode).
Generic character traits.
Also support wchar_t specializations on Mac OS 10.3.x,
FreeBSD 5.x, Solaris 2.7 and above, AIX 5.x, Irix 6.5.
The allocator class is now standard-conformant, and two additional
extension allocators have been added, mt_alloc and bitmap_allocator.
PCH support: -include bits/stdc++.h (2x compile speedup).
Rewrote __cxa_demangle with support for C++ style
allocators.
New debug modes for STL containers and iterators.
Testsuite rewrite: five times as many tests, plus increasingly
sophisticated tests, including I/O, MT, multi-locale, wide and
narrow characters.
Use current versions of GNU "autotools" for build/configuration.
Objective-C
The Objective-C front end has been updated to include the numerous
bug fixes and enhancements previously available only in Apple's
version of GCC.
These include:
Structured exception (@try... @catch...
@finally, @throw) and synchronization
(@synchronized) support.
These are accessible via
the -fobjc-exceptions as of this writing,
they may only be used in conjunction with -fnext-runtime
on Mac OS X 10.3 and later. See
information.
An overhaul of @encode logic.
The C99 _Bool
and C++ bool type may now be encoded as
'B'. In addition, the back-end/codegen dependencies
have been removed.
An overhaul of message dispatch construction, ensuring that the
various receiver types (and casts thereof) are handled properly,
and that correct diagnostics are issued.
Support for "Zero-Link" (-fzero-link) and
"Fix-and-Continue" (-freplace-objc-classes) debugging
modes, currently available on Mac OS X 10.3 and later. See
information.
Access to optimized runtime entry points (-fno-nil-receivers
) on the assumption that message receivers are never
This is currently available on Mac OS X 10.3 and
later. See
information.
Compiling a .jar file will now cause non-.class entries to be
automatically compiled as resources.
libgcj has been ported to Darwin.
Jeff Sturm has adapted Jan Hubicka's call graph optimization
code to gcj.
libgcj has a new gcjlib URL this
lets URLClassLoader load code from shared
libraries.
libgcj has been much more completely merged with GNU Classpath.
Class loading is n in particular the
caller's class loader is now used when that is required.
out of the box using gij.
Parts of java.nio have been implemented.
Direct and indirect buffers work, as do fundamental file and
socket operations.
java.awt has been improved, though it is still
not ready for general use.
The HTTP protocol handler now uses HTTP/1.1 and can handle
the POST method.
The MinGW port has matured. Enhancements include socket
timeout support, thread interruption, improved
Runtime.exec() handling and support for accented
characters in filenames.
Fortran improvements are listed in the
New Targets and Target Specific Improvements
have been added such as __builtin_alpha_zap to
allow utilizing the more obscure instructions of the CPU.
Parameter passing of complex arguments has changed to match the
This change is incompatible with previous GCC versions, but
does fix compatibility with the Tru64 compiler and several corner cases
where GCC was incompatible with itself.
Nicolas Pitre has contributed his hand-coded floating-point support
code for ARM.
It is both significantly smaller and faster than the
existing C-based implementation, even when building applications for
The arm-elf configuration has been converted to use
the new code.
Support for the Intel's iWMMXt architecture, a second
generation XScale processor, has been added.
Enabled at run time with the -mcpu=iwmmxt command
line switch.
A new ARM target has been added: arm-wince-pe.
similar to the arm-pe target, but it defaults to using the
APCS32 ABI.
The existing ARM pipeline description has been converted to
the use the DFA
processor pipeline model. There is not much change in code
performance, but the description is now easier
to understand.
Support for the Cirrus EP9312 Maverick floating point
co-processor added.
Enabled at run time with the
-mcpu=ep9312 command line switch.
Note however that
the multilibs to support this chip are currently disabled in
gcc/config/arm/t-arm-elf, so if you want to enable their
production you will have to uncomment the entries in that
Support for long long has been added.
Support for saveall attribute has been added.
Pavel Pisa contributed hand-written 32-bit-by-32-bit division
code for H8/300H and H8S, which is much faster than the previous
implementation.
A lot of small performance improvements.
IA-32/AMD64 (x86-64)
Tuning for K8 (AMD Opteron/Athlon64) core is available via
-march=k8 and -mcpu=k8.
Scalar SSE code generation carefully avoids reformatting penalties,
hidden dependencies and minimizes the number of uops generated on
both Intel and AMD CPUs.
Vector MMX and SSE operands are now passed in registers to improve
performance and match the argument passing convention used by the Intel
C++ Compiler.
As a result it is not possible to call functions
accepting vector arguments compiled by older GCC version.
Conditional jump elimination is now more aggressive on modern CPUs.
The Athlon ports has been converted to use the DFA
processor pipeline description.
Optimization of indirect tail calls is now possible in a similar
fashion as direct sibcall optimization.
Further small performance improvements.
-m128bit-long-double is now less buggy.
__float128 support in 64-bit compilation.
Support for data structures exceeding 2GB in 64-bit mode.
-mcpu has been renamed to -mtune.
Tuning code for the Itanium 2 processor has been added.
generation of code tuned for Itanium 2 (option
-mtune=itanium2) is enabled by default now.
generate code tuned for Itanium 1 the option
-mtune=itanium1 should be used.
processor pipeline descriptions for the IA-64 processors
have been added.
This resulted in about 3% improvement on the
SPECInt2000 benchmark for Itanium 2.
Instruction bundling for the IA-64 processors has been
rewritten using the DFA pipeline hazard recognizer.
resulted in about 60% compiler speedup on the SPECInt2000 C
Support for the M32R/2 processor has been added by Renesas.
Support for an M32R GNU/Linux target and PIC code generation has
been added by Renesas.
Bernardo Innocenti (Develer&S.r.l.) has contributed
the m68k-uclinux target, based on former work done
by Paul Dale (SnapGear&Inc.).
Code generation for the
ColdFire processors family has been enhanced and extended
to support the MCF&53xx and MCF&54xx cores, integrating
former work done by Peter Barada (Motorola).
Processor-specific changes
Support for the RM7000 and RM9000 processors has been added.
It can be selected using the -march compiler option
and should work with any MIPS I (mips-*) or MIPS III
(mips64-*) configuration.
Support for revision 2 of the MIPS32 ISA has been added.
It can be selected with the command-line option
-march=mips32r2.
There is a new option, -mfix-sb1, to work around
certain SB-1 errata.
Configuration
It is possible to customize GCC using the following configure-time
--with-arch, which specifies the default
value of the -march option.
--with-tune, which specifies the default
value of the -mtune option.
--with-abi, which specifies the default ABI.
--with-float=soft, which tells GCC to
use software floating point by default.
--with-float=hard, which tells GCC to
use hardware floating point by default.
A 64-bit GNU/Linux port has been added.
The associated
configurations are mips64-linux-gnu and
mips64el-linux-gnu.
The 32-bit GNU/Linux port now supports Java.
The IRIX 6 configuration now supports the o32 ABI and will
build o32 multilibs by default.
This support is compatible with
both binutils and the SGI tools, but note that several features,
including debugging information and DWARF2 exception handling,
are only available when using the GNU assembler.
Use of the
GNU assembler and linker (version 2.15 or above) is strongly
recommended.
The IRIX 6 configuration now supports 128-bit long doubles.
There are two new RTEMS-specific configurations,
mips-rtems and mipsel-rtems.
There are two new *-elf configurations,
mipsisa32r2-elf and mipsisa32r2el-elf.
have been fixed.
Unfortunately, these changes will break binary compatibility
with earlier releases.
GCC can now use explicit relocation operators when generating
-mabicalls code.
This behavior is controlled by
-mexplicit-relocs and can have several performance
For example:
It allows for more optimization of GOT accesses, including
better scheduling and redundancy elimination.
It allows sibling calls to be implemented as jumps.
n32 and n64 leaf functions can use a call-clobbered
global pointer instead of $28.
The code to set up $gp can be removed from
functions that don't need it.
A new option, -mxgot, allows the GOT to be bigger
This option is equivalent to the assembler's
-xgot option and should be used instead of
-Wa,-xgot.
Frame pointer elimination is now supported when generating 64-bit
MIPS16 code.
Inline block moves have been optimized to take more account of
alignment information.
Many internal changes have been made to the MIPS port, mostly
aimed at reducing the reliance on assembler macros.
GCC 3.4 releases have a number of fixes for PowerPC and PowerPC64
regarding the way parameters are passed during functions calls.
These changes may result in incompatibility between code compiled
with GCC 3.3 and GCC 3.4.
PowerPC Darwin
Support for shared/dylib gcc libraries has been added. It is
enabled by default on powerpc-apple-darwin7.0.0
Libgcj is enabled by default. On systems older than
powerpc-apple-darwin7.0.0 you need to install dlcompat.
128-bit IBM extended precision format support added for
long double.
PowerPC64 GNU/Linux
By default, PowerPC64 GNU/Linux now uses natural alignment of
structure elements.
The old four byte alignment for
double, with special rules for a struct
starting with a double, can be chosen with
-malign-power.
This change may result in
incompatibility between code compiled with GCC 3.3 and GCC 3.4.
-mabi=altivec is now the default rather than
-mabi=no-altivec.
128-bit IBM extended precision format support added for
long double.
S/390 and zSeries
New command-line options allow to specify the intended execution
environment for generated code:
-mesa/-mzarch allows to specify
whether to generate code running in ESA/390 mode or in
z/Architecture mode (this is applicable to 31-bit code
-march allows to specify a minimum processor
architecture level (g5, g6,
z900, or z990).
-mtune allows to specify which processor to tune
It is possible to customize GCC using the following configure-time
--with-mode, which specifies whether to
default to assuming ESA/390 or z/Architecture mode.
--with-arch, which specifies the default
value of the -march option.
--with-tune, which specifies the default
value of the -mtune option.
Support for the z990 processor has been added, and can be selected
using -march=z990 or -mtune=z990.
includes instruction scheduling tuned for the superscalar instruction
pipeline of the z990 processor as well as support for all new
instructions provided by the long-displacement facility.
Support to generate 31-bit code optimized for zSeries processors
(running in ESA/390 or in z/Architecture mode) has been added.
This can be selected using -march=z900 and
-mzarch respectively.
Instruction scheduling for the z900 and z990
processors now uses the DFA pipeline hazard recognizer.
GCC no longer generates code to maintain a stack backchain,
previously used to generate stack backtraces for debugging
As replacement that does not incur runtime overhead,
DWARF-2 call frame information is provided by GCC;
this is supported by GDB 6.1.
The old behavior can
be restored using the -mbackchain option.
The stack frame size of functions may now exceed 2 GB in 64-bit
A port for the 64-bit IBM TPF operating s
the configuration is s390x-ibm-tpf.
configuration is supported as cross-compilation target only.
Various changes to improve the generated code have been implemented,
including:
GCC now uses the MULTIPLY AND ADD and
MULTIPLY AND SUBTRACT instructions to
significantly speed up many floating-point applications.
GCC now uses the ADD LOGICAL WITH CARRY and
SUBTRACT LOGICAL WITH BORROW instructions to
speed up long long arithmetic.
GCC now uses the SEARCH STRING instruction to
implement strlen().
In many cases, function call overhead for 31-bit code has
been reduced by placing the literal pool after the function
code instead of after the function prolog.
Register 14 is no longer reserved in 64-bit code.
Handling of global register variables has been improved.
The option -mflat is deprecated.
Support for large (& 2GB) frames has been added to the
64-bit port.
have been fixed.
Unfortunately, these changes will break binary compatibility with
earlier releases.
The default debugging format has been switched from STABS to
DWARF-2 for 32-bit code on Solaris 7 and later.
DWARF-2 is already
the default debugging format for 64-bit code on Solaris.
Support for the SH2E processor has been added.
Enabled at run time with the -m2e command line
switch, or at configure time by specifying sh2e as the machine
part of the target triple.
Support for the Mitsubishi V850E1 processor has been added.
This is a variant of the V850E processor with some additional
debugging instructions.
Several ABI bugs have been fixed.
Unfortunately, these changes
break binary compatibility with earlier releases.
For big-endian processors, the padding of aggregate return values
larger than a word has changed.
If the size of an aggregate return
value is not a multiple of 32 bits, previous versions of GCC inserted
padding in the most-significant bytes of the first return value
Aggregates larger than a word are now padded in the
least-significant bytes of the last return value register used.
Aggregates smaller than a word are still padded in the most-significant
The return value padding has not changed for little-endian
processors.
Function arguments with 16-byte alignment are now properly
The implementation of the va_list type has changed.
A va_list value created by va_start from a
previous release cannot be used with va_arg from this
release, or vice versa.
More processor configuration options for Xtensa processors are
supported:
the ABS instruc
the ADDX* and SUBX* instructions are
an experimental CONST16 instruction can be used to
synthesize constants instead of loading them from constant pools.
These and other Xtensa processor configuration options can no longer
be enabled or disabled by command- the processor
configuration must be specified by the xtensa-config.h
header file when building GCC.
Additionally, the
-mno-serialize-volatile option is no longer supported.
Support for a number of older systems has been declared obsolete in
Unless there is activity to revive them, the next release of
GCC will have their sources permanently removed.
All configurations of the following processor architectures have
been declared obsolete:
Mitsubishi D30V, d30v-*
AT&T DSP1600 and DSP1610, dsp16xx-*
Intel 80960, i960
Also, some individual systems have been obsoleted:
ARM Family
Support for generating code for operation in APCS/26 mode
(-mapcs-26).
IBM ESA/390
"Bigfoot" port, i370-*.
(The other port,
s390-*, is actively maintained and
supported.)
Intel 386 family
MOSS, i?86-moss-msdos and
i?86-*-moss*
NCR 3000 running System V r.4, i?86-ncr-sysv4*
FreeBSD with a.out object format, i?86-*-freebsd*aout*
and i?86-*-freebsd2*
GNU/Linux with a.out object format,
i?86-linux*aout*
GNU/Linux with libc5, a.k.a. glibc1,
i?86-linux*libc1*
Interix versions before Interix 3, i?86-*-interix
Mach microkernel, i?86-mach*
SCO UnixWare with UDK, i?86-*-udk*
Generic System V releases 1, 2, and 3,
i?86-*-sysv[123]*
VSTa microkernel, i386-*-vsta
Motorola M68000 family
HPUX, m68k-hp-hpux* and
m68000-hp-hpux*
NetBSD with a.out object format (before NetBSD 1.4),
m68k-*-*-netbsd* except
m68k-*-*-netbsdelf*
Generic System V r.4, m68k-*-sysv4*
Generic VAX, vax-*-* (This is generic VAX
we have not obsoleted any VAX triples for specific operating
Documentation improvements
Other significant improvements
The build system has undergone several significant cleanups.
Subdirectories will only be configured if they are being built,
and all subdirectory configures are run from the make
The top level has been autoconfiscated.
Building GCC no longer writes to its source directory.
should help those wishing to share a read-only source directory
over NFS or build from a CD.
The exceptions to this feature are
if you configure with either --enable-maintainer-mode
or --enable-generated-files-in-srcdir.
The -W warning option has been renamed to
-Wextra, which is more easily understood.
spelling will be retained for backwards compatibility.
Substantial improvements in compile time have been made, particularly
for non-optimizing compilations.
A vast number of bugs have been fixed in 3.4.0, too many to publish a
complete list here.
this link to query the Bugzilla database for the list of over 900 bugs
fixed in 3.4.0.
This is the list of all bugs marked as resolved and fixed
in 3.4.0 that are not flagged as 3.4 regressions.
This section lists the problem reports (PRs) from GCC's bug tracking
system that
are known to be fixed in the 3.4.1 release. This list might not be complete
(that is, it is possible that some PRs that have been fixed are not listed
Bootstrap failures
Ada bootstrap fails on PPC-Darwin - invalid assembler emitted - PIC related
[ARM] ICE in libiberty when building gcc-3.4 for arm-elf
A bug in configure.in prevents using both --program-suffix and --program-prefix
[hppa64] bootstrap fails: ICE in save_call_clobbered_regs, in caller_save.c
[alpha][Java] make bootstrap fails to configure libffi on Alpha
Solaris 9/x86 fails linking after stage 3
Multi-platform internal compiler errors (ICEs)
(preprocessor) Memory corruption in preprocessor on bad input
ICE in gcc.c-torture/compile/.c
(c++) tree check failures with invalid code involving templates
(c++) ICE on invalid code, in cp_parser_lookup_name, in cp/parser.c
(c++) ICE on syntax error, template header
(c++) Compiling of conditional value throw constructs cause a segmentation violation
(c++) typeid of template parameter gives ICE
(c++) ICE when passing a string where a char* is expected in a throw statement
ICE in rtl_verify_flow_info_1
(c++) ICE in instantiate_template
Unary minus using pointer to V4SF vector causes -fforce-mem to exhaust all memory
(c++) Runs out of memory with packed structs
(c++) Trouble with invalid function definition
(c++) instantiate_type ICE when forming pointer to template function
(c++) ICE in resolve_overloaded_unification
(c++) ICE on constructor of member template
ICE in extract_insn, in recog.c
(c++) ICE in tsubst_copy, in cp/pt.c
(c++) ICE on invalid code in arg_assoc, in cp/name-lookup.c
[unit-at-a-time] Gcc abort on valid code
(c++) ICE with bad pointer-to-member code
(c++) ICE with friends and template template parameter
ICE in do_SUBST, in combine.c
(c++) ICE on Botan-1.3.13 due to -funroll-loops
All RTEMS targets broken for gnat
C front end
missing warning about assigning to an incomplete type
atan(1.0) should not be a constant expression
[unit-at-a-time] no warning for unused paramater in static function
--pedantic-errors behaves differently from --pedantic with C-compiler on GNU/Linux
C++ compiler and library
non-const reference is incorrectly matched in a "const T" partial specialization
wcin.rdbuf()-&in_avail() return value too high
enc_filebuf doesn't work
const_cast returns lvalue but should be rvalue
num_put::do_put() undesired float/double behavior
problem with user-defined allocators in std::basic_string
libstdc++ Debug mode: failure to convert iterator to const_iterator
__gnu_cxx::stdio_sync_filebuf should expose internal FILE*
no warning anymore for reevaluation of declaration
LFS (large file support) tests missing
Duplicate namespace alias declaration should not conflict
Friend declaration ignored
cannot use offsetof to get offsets of array elements in g++ 3.4.0
[non unit-at-a-time] always_inline does not mix with templates and -O0
g++ ignores #pragma redefine_extname
Segfault on low-level write error during imbue
Linewise stream input is unusably slow (std::string slow)
compiler accepts redeclaration of template as non-template
[arm] Math functions misdetected by cross configuration
a bit test on a variable of enum type is miscompiled
g++ -lsupc++ still links against libstdc++
spurious "statement has no effect" warning
parse error with templates and pointer to const member
combination of operator[] and operator .* fails in templates
__attribute__ unused in first parameter of constructor gives error
sizeof on incomplete type diagnostic
bitset&&::_Find_next fails
_GLIBCXX_ symbols symbols defined and used in different namespaces
valid code results in incomplete type error
Incorrect member pointer offsets in anonymous structs/unions
nested template problem
compiler hangs while laying out union
operator & and template definitions
SLES9: leading + sign for unsigned int with showpos
friend defined inside a template fails to find static function
Function templates, overloads, and friend name injection
'noreturn' attribute ignored in method of template functions.
Allocator::pointer consistently ignored
Duplicate namespace alias within namespace rejected
'enum yn' fails (confict with undeclared builtin)
rejects pointer to member in template
valid code using templates and anonymous enums is rejected
Puzzling error message for wrong destructor declaration in template class
cannot copy __gnu_debug::bitset
input iterator concept too restrictive
deducing top-level consts
Java compiler is not parallel make safe
[g77] incorrect logical i/o in 64-bit mode
Objective-C
private variables cannot be shadowed in subclasses
Optimization bugs
useless copies of floating point operands
[non-unit-at-a-time] unreferenced nested inline functions not optimized away
Incorrect floating point optimization
ftrapv aborts on 0 * (-1)
Miscompiled POOMA tests
GCC generates code to write to unchanging memory
Preprocessor
Minor glitch in the source of cpp
Main driver program bugs
collect2 interprets -oldstyle_liblookup as -o ldstyle_liblookup
x86-specific (Intel/AMD)
Error: can't resolve `L0' {*ABS* section} - `xx' {*UND* section}
HPPA-specific
GCC produces an unaligned data access at -O2
FAIL: gcc.c-torture/execute/.c execution,
ICE in reload_cse_simplify_operands, in postreload.c
IA64-specific
__float80 constants incorrectly emitted
init_array sections are initialized in the wrong order
GCC segfault on duplicated asm statement
Gcc 3.4 ICE on valid code
Gcc 3.4 ICE on valid code
MIPS-specific
wrong filling of delay slot with -march=mips1 -G0 -mno-split-addresses -mno-explicit-relocs
Assembler error building gnatlib on IRIX 6.5 with GNU as 2.14.91
Bogus reference to __divdf3 when -O1
Miscompilation of unaligned data in MIPS backend
PowerPC-specific
ICE in gcc.dg/altivec-5.c
powerpc-eabispe produces bad sCOND operation
rs6000 geu/ltu patterns generate incorrect code
long double and va_arg complex args
Altivec stack layout may overlap gpr save with stack temps
(libstdc++) Stream checking functions fail when -pthread option is used.
Compiler ICE on valid code
-maltivec affects vector return with -mabi=no-altivec
vector varargs failure passing from altivec to non-altivec code for -m32
ICE in function.c:4804, assign_parms, when -mpowerpc64 & half-word operation
-maltivec -mabi=no-altivec results in mis-aligned lvx and stvx
Segmentation fault when an exception is thrown - even if try and catch are specified
s390-specific
Bad code due to overlapping stack temporaries
SPARC-specific
ICE with union assignment in 64-bit mode
GCC 3.4 emits "ld: warning: relocation error: R_SPARC_UA32"
x86-64-specific
boehm-gc hardcodes to 3DNow! prefetch for x86_64
Backported -march=nocona from mainline
__float128 failed to pass to function properly
Cygwin/Mingw32-specific
Option -mms-bitfields support on GCC 3.4 is not conformant to MS layout
-mtune=pentium4 -O2 with sjlj EH breaks stack probe worker on windows32 targets
Bugs specific to embedded processors
[m68k] -m5200 produces erroneous SImode set of short varaible on stack
[SH] Gcc code for rotation clobbers the register, but gcc continues to use the register as if it was not clobbered
[coldfire] movqi operand constraints too restrictivefor TARGET_COLDFIRE
[SH] ICE for code when using -mhitachi option in SH
[m6811hc] ICE with simple c++ source
[m6811hc] ICE on simple source
[SH] cc1plus got hang-up on libstdc++-v3/testsuite/abi_check.cc
[CRIS] Delayed branch scheduling causing invalid code on cris-*
[SH] ICE with -O2 -fPIC
[coldfire] m68k_output_mi_thunk emits wrong code for ColdFire
Testsuite problems (compiler not affected)
libstdc++ testcases 27_io/* don't work properly remotely
(libstdc++) possibly insufficient file permissions for executing test suite
(libstdc++) testsuite_files determined incorrectly
Documentation bugs
(libstdc++) no whatis info in some man pages generated by doxygen
Ada documentation out of date
(c++) Need to document method visibility changes
libstdc++-doc: Allocators.3 manpage is empty
This section lists the problem reports (PRs) from GCC's bug tracking
system that
are known to be fixed in the 3.4.2 release. This list might not be complete
(that is, it is possible that some PRs that have been fixed are not listed
Bootstrap failures and issues
[mips-sgi-irix5.3] bootstrap fails in libstdc++-v3/testsuite
[hppa-linux-gnu] libstdc++'s PCH built by profiledbootstrap does not work with the built compiler
[Solaris/x86] mkheaders can not find mkheaders.conf
Multi-platform internal compiler errors (ICEs)
(c++) ICE: expected class 't', have 'x' (error_mark) in cp_parser_class_specifier, in cp/parser.c
ICE in loc_descriptor_from_tree, in dwarf2out.c
(c++) ICE due to NRV and inlining
(c++) ICE in c_expand_expr, in c-common.c
ICE: segmentation fault in RTL optimization
(c++) ICE in write_unscoped_name (template/namespace)
ICE: in delete_insn, in cfgrtl.c
(c++) ICE for: namespace-alias shall not be declared as the name of any other entity
(c++) ICE with exceptions and declaration of __cxa_throw
(c++) ICE in finish_member_declaration, in cp/semantics.c
(c++) Legal C++ program with cast gives ICE in build_ptrmemfunc
(c++) ICE when throwing a comma expression
(c++) Boost.Spirit causes ICE in tsubst, in cp/pt.c
(c++) ICE in finish_class_member_access_expr, in cp/typeck.c
(c++) ICE (segfault) with exceptions
(c++) ICE in cp_parser_class_specifier due to redefinition
(c++) ICE: tree check: expected class 'd', have 'x' (identifier_node) in dependent_template_p, in cp/pt.c
Preprocessor bugs
Preprocessor option -remap causes memory corruption
Optimization
unreferenced nested inline functions not optimized away
Incorrect execution when compiling with -O2
Bitwise AND is lost when used within a cast to an enum of the same precision
Jump into if(0) substatement fails
Problems in generated debug information
incorrect stabs for nested local variables
C front end bugs
GCC should not warn about redundant redeclarations of built-ins
C++ compiler and library
Thread safety problems in locale::global() and locale::locale()
g++ accepts invalid pointer-to-member conversion
Excessive memory consumption
Incorrect template argument deduction
Memory exhausted when using nested classes and virtual functions
ostringstream in gcc 3.4.x very slow for big data
undefined reference to __gnu_cxx::stdio_sync_filebuf&char, std::char_traits&char& &::file()
G++ incorrectly rejects use of a null constant integral expression as a null constant pointer
offsetof fails with constant member
syntax error reported for valid input code
__attribute__((constructor)) broken in C++
compiler error in DEBUG version of range insertion std::map::insert
pointer-to-member initialization from incompatible one accepted
ambiguity is not detected
Segmentation fault in ios_base::sync_with_stdio
Java compiler and library
direct threaded interpreter not thread-safe
ServerSocket accept() leaks file descriptors
Hash synchronization deadlock with finalizers
Alpha-specific
ICE in dwarf2out_frame_debug_expr, in dwarf2out.c
could not split insn (ice in final_scan_insn, in final.c)
x86-specific
ICE in output_operand
ICE with SSE2 intrinsics
x86-64 specific
libstdc++ couldn't find 32bit libgcc_s
MIPS-specific
[mips64] No NOP after LW (with -mips1 -O0)
[mips64] value profiling clobbers gp on mips
[mipsisa64-elf] ICE copying 7 bytes between extern char[]s
[mips64] Use of uninitialised register after dbra conversion
[mips64] Unaligned access to local variables
[mips64] verify_local_live_at_start ICE after crossjumping & cfgcleanup
ARM-specific
THUMB -O2: strength-reduced iteration variable ends up off by 1
THUMB: ICE with non-commutative cbranch
THUMB: bad switch statement in md code for addsi3_cbranch_scratch
IA64-specific
ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=merced)
ICE on valid code: in bundling, in config/ia64/ia64.c (-mtune=itanium)
Gcc failed to build Linux kernel with -mtune=merced
ICE on valid code: typo in comparison of asm_noperands result
ICE on valid code: don't count ignored insns
ICE (segfault) while compiling with -fprofile-use
ia64 does not honor SUBTARGET_EXTRA_SPECS
PowerPC-specific
(ppc64): Miscompilation of GCC 3.3.x by 3.4.x
ICE on ppc64 (mozilla 1.7 compile, -O1 -fno-exceptions issue)
SPARC-specific
ICE while compiling apache 2.0.49
-m64 doesn't imply -mcpu=v9 anymore
ICE when returning non-C aggregates larger than 16 bytes
Bugs specific to embedded processors
[m32r] can't output large model function call of memcpy
[m32r] ICE with -msdata=use -O0
[m32r] ICE at switch case 0x8000
DJGPP-specific
libstdc++ in 3.4.x doesn't cross-compile for djgpp
Alpha Tru64-specific
libstdc++ gratuitously omits "long long" I/O
Testsuite, documentation issues (compiler is not affected):
(libstdc++) possibly insufficient file permissions for executing test suite
ada/doctools runs makeinfo even in release tarball
This is the list
of problem reports (PRs) from GCC's bug tracking system that are
known to be fixed in the 3.4.3 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
are not listed here).
Bootstrap failures
[ia64] Bootstrap failure with binutils-2.15.90.0.1.1
[arm-elf] bootstrap failure - libstdc++ uses strtold when undeclared
Internal compiler errors (ICEs) affecting multiple platforms
(java) GCJ segmentation fault while compiling GL4Java .class files
ICE in loc_descriptor_from_tree, in dwarf2out.c
(c++) ICE when "strong" attribute is attached to a using directive
ICE with flexible arrays
ICE with nested functions in parameter declaration
ICE with noreturn function in loop at -O2
ICE in grokdeclarator, in cp/decl.c
(c++) ICE in cp_tree_equal
C and optimization bugs
-ftrapv aborts on 0 * (-1)
#ident stopped working
quadratic behaviour in invalid_mode_change_p
Long long arithmetic fails inside a switch/case statement when compiled with -O2
-fwritable-strings doesn't work
C++ compiler and library bugs
incorrect initial ostringstream::tellp()
Unbuffered filebuf::sgetn is slow
Unrecognizing static function as a template parameter when its return value is also templated
Copy constructor optimization in aggregate initialization
Bad error message for frequently occuring error.
Rejects valid member-template-definition
empty basic_strings can't live in shared memory
std::basic_iostream is instantiated when used, even though instantiations are already contained in libstdc++
code in /ext/demangle.h appears broken
GCC fails to eliminate function template specialization when argument deduction fails
One more _S_leaf incorrectly qualified with _RopeRep:: in ropeimpl.h
use of `enumeral_type' in template type unification
"unused variable '._0'" warning with -Wall
Confusion with member templates
g++ not passing -lstdc++ to linker when all command line arguments are libraries
usage of unqualified name of static member from within class not allowed
Poor diagnostic for using "." instead of "-&"
wrong error: call of overloaded function is ambiguous
Misleading diagnostic for invalid function declarations with undeclared types
Destructor is called twice
rejects valid definition of enum value in template
bogus conflict in namespace aliasing
C++ parser bug when using && in templates
data statements with double precision constants fail
x86-specific
-O2 ICE for MMX testcase
SPARC-specific
ICE compiling gsl-1.5 statistics/lag1.c
Darwin-specific
FATAL:Symbol L_foo$stub already defined.
AIX-specific
could not catch an exception when specified -maix64
Solaris-specific
&cmath& calls acosf(), ceilf(), and other functions missing from system libraries
HP/UX specific:
/usr/ccs/bin/ld: Can't create libgcc_s.sl
ARM-specific
ICE with mode attribute on structures
MIPS-specific
No NOP after LWL with -mips1
Other embedded target specific
[arc-elf] gcc ICE on newlib's vfprintf.c
[avr-elf] -fdata-sections triggers ICE
[m68hc11-elf] gcc ICE
[powerpc-rtems] powerpc-rtems lacks __USE_INIT_FINI__
[i686-coff] Alignment error building gcc with i686-coff target
[SH] Miscompilation with -O2 -fPIC
[avr-elf] [fweb related] bug while initializing variables
Bugs relating to debugger support
missing debug info for _Complex function arguments
[big-endian targets] No DW_AT_location debug info is emitted for formal arguments to a function that uses "register" qualifiers
Testsuite issues (compiler not affected)
Testsuite in libffi overrides LD_LIBRARY_PATH
Testsuite in libstdc++ overrides LD_LIBRARY_PATH
[mips-sgi-irix6.5] libgcc_s.so.1 not found by 64-bit testsuite
Documentation
typo in gcc manual: non-existing locale example en_UK, should be en_GB
[mips-sgi-irix5.3] /bin/sh hangs during bootstrap: document broken shell
USE_LD_AS_NEEDED undocumented
This is the list
of problem reports (PRs) from GCC's bug tracking system that are
known to be fixed in the 3.4.4 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
are not listed here).
This is the list
of problem reports (PRs) from GCC's bug tracking system that are
known to be fixed in the 3.4.5 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
are not listed here).
Bootstrap issues
sco_math fixincl breaks
C compiler bugs
struct Foo { }
redefinition
wrong code for
((unsigned char)(unsigned long long)((a?a:1)&(a*b)))?0:1)
infinite warning loop on bad
array initializer
enum definition accepts
values to be overriden
find_function_data, in function.c
Failure to diagnose
violation of constraint 6.516p2
ICE on missing brace
ICE casting to long
Segfault with preprocessed source
C++ compiler and library bugs
operations on vector mode
not recognized in C++
unexpected behavior of
namespace usage directive
Strange error message with
new parser
local classes as template argument
spurious error message after
using keyword
cp_convert_to_pointer, in cp/cvt.c
ICE with invalid template
template parameter
typedef in
template declaration not rejected
const_cast for undeclared variable
C++ error message
regression
ICE when returning a copy of
a packed member
ICE on invalid usage of
template base class
ICE when returning undefined
typename not
allowed with non-dependent qualified name
rejects access to
operator() in template
uses_template_parms, in cp/pt.c
Spurious error about
variably modified type
bad error message / ICE for
invalid template parameter
ICE after friend function
definition in local class
ICE on explicit
instantiation of a non-template constructor
ICE when C++ template
function contains anonymous union
Infinite loop in diagnostic
(and ice after error message)
ICE with incomplete type in
Internal compiler error when
using custom new operators
ICE in error message due to
violation of coding conventions
constness of pointer to data
member ignored
Default argument of template
function causes a compile-time error
multiple diagnostics
New testsuite failure
g++.dg/warn/conversion-function-1.C
ICE on invalid template
specialization
Internal compiler error, seg
filebuf::xsgetn
ICE with wrong number of
template parameters
ICE after invalid
operator new
ICE with pointer to class
member & user defined conversion operator
Wrong default allocator in
ext/hash_map
char_traits
requirements/1.cc test bad math
Bad diagnostic for invalid
namespace-name
invert_truthvalue, in fold-const.c
Bad error message: not a
member of '&declaration error&'
ICE on typename
outside template
Bogus error message: no
matching function for call to 'foo(&type error&)'
&#`label_decl' not supported by
dump_expr#&expression error&
virtual base class cause
exception not to be caught
Problems in generated debug information
Bad DWARF for altivec vectors
Optimizations issues
verify_local_live_at_start
Wrong generated code for
loop with varying bound
ICE on compile-time complex
broken tail call at -O2 or
Strange optimization bug
when using -Os
Compilation failure for
real_const_1.f and real_const_2.f90
Invalid code generated for
comparison of uchar to 255
Miscompilation due to
reloading of a var that is also used in EH pad
segmentation fault in
cc1plus when compiling with -O
operand_subword_force
Precompiled headers problems
Cannot compile qt-x11-free-3.3.0
PCH largefile test fails on
various platforms
Preprocessor bugs
ICE on empty preprocessed
"gcc -E -MM -MG" reports
missing system headers in source directory
Testsuite issues
gcc.dg/.c fails
with -fpic/-fPIC on i686-pc-linux-gnu
Alpha specific
bootstrap failure with
linker relaxation enabled
ARM specific
[arm-linux]: ICE
in verify_local_live_at_start
Memory aliasing information
incorrect in inlined memcpy
ColdFile specific
Illegal move of byte into
address register causes compiler to ICE
HPPA specific
ICE while building
libgfortran
-mhp-ld/-mgnu-ld documentation
IA-64 specific
IA-64 hardware models and
configuration options documentation error
Shared libgcc not used for
linking by default
M68000 specific
reload_cse_simplify_operands, in postreload.c
MIPS specific
change_address_1, in emit-rtl.c
PowerPC and PowerPC64 specific
error on valid code:
const __attribute__((altivec(vector__))) doesn't work in
reload_cse_simplify_operands
TARGET_C99_FUNCTIONS is wrongly defined
CALL_V4_CLEAR_FP_ARGS flag not properly set
gij trashes args of
functions with more than 8 fp args
C & C++ compiler
generating misaligned references regardless of compiler flags
floatdisf2_internal2 broken
-mminimal-toc
miscompilation of __thread vars
Solaris specific
Problem with define of
HUGE_VAL in math_c99
Native Solaris assembler
cannot grok DTP-relative debug symbols
SPARC specific
PCH failures on
sparc-linux
Assembler labels have a
leading "-"
C PCH testsuite assembly
comparison failure
x86 and x86_64 specific
ICE with arrays of type
Compilation SEGFAULTs with
-O1 -fschedule-insns2 -fsched2-use-traces
reg-stack.c's swap_rtx_condition
amd64 fails
-fpeephole2
This is the list
of problem reports (PRs) from GCC's bug tracking system that are
known to be fixed in the 3.4.6 release. This list might not be
complete (that is, it is possible that some PRs that have been fixed
are not listed here).}