1 Noteworthy changes in GCC for EGCS.
3 The -specs=file switch allows you to override default specs used in invoking
4 programs like cc1, as, etc.
6 Options -Wall and -Wimplicit now cause GCC to warn about implicit int
7 in declarations (e.g. `register i;'), since the C Standard committee
8 has decided to disallow this in the next revision of the standard.
10 The following new targets are supported:
12 Solaris 2.5 running on UltraSPARC's.
13 The sparclet cpu (a.out file format).
14 Solaris 2.51 running on PowerPC's.
15 Linux running on PowerPC's.
16 Embedded target m32r-elf.
18 New features for the Hitachi H8/300(H).
23 The -ms switch generates code for the Hitachi H8/S processor.
25 New features for SPARC-based systems:
29 -mimpure-text and -mno-impure-text
31 New features for all rs6000 and PowerPC systems:
42 New features for PowerPC-based systems running either System V, Linux, Solaris,
59 wchar_t is now of type long, not unsigned short as per ABI.
61 -mcpu=403 now implies -mstrict-align.
63 Options -mno-v8 and -mno-sparclite are no longer supported on SPARC
64 targets. Options -mcypress, -mv8, -msupersparc, -msparclite, -mf930,
65 and -mf934 are deprecated and will be deleted in GCC 2.9.
66 Use -mcpu=xxx instead.
68 GCC on the PA requires either gas-2.7 or the HP assembler; for best
69 results using GAS is highly recommended. GAS is required for -g
70 and exception handling support.
72 Aix 4.1 GCC targets now default to -mcpu=common so that programs compiled can
73 be moved between rs6000 and powerpc based systems. A consequence of this is
74 that -static won't work, and that some programs may be slightly slower.
76 You can select the default value to use for -mcpu=xxx on rs6000 and powerpc
77 targets by using the --with-cpu=xxx option when confiuring the compiler. In
78 addition, a new options, -mtune=xxx was added that selects the machine to
79 schedule for but does not select the architecture level.
81 Directory names used for storing the multilib libraries on System V and
82 embedded PowerPC systems have been shortened to work with commands like tar
83 that have fixed limits on pathname size.
85 Noteworthy changes in GCC version 2.7.2:
87 A few bugs have been fixed (most notably the generation of an
88 invalid assembler opcode on some RS/6000 systems).
90 Noteworthy changes in GCC version 2.7.1:
92 This release fixes numerous bugs (mostly minor) in GCC 2.7.0, but
93 also contains a few new features, mostly related to specific targets.
95 Major changes have been made in code to support Windows NT.
97 The following new targets are supported:
101 HP/UX version 10 on HP PA RISC (treated like version 9)
102 DEC Alpha running Windows NT
104 When parsing C, GCC now recognizes C++ style `//' comments unless you
105 specify `-ansi' or `-traditional'.
107 The PowerPC System V targets (powerpc-*-sysv, powerpc-*-eabi) now use the
108 calling sequence specified in the System V Application Binary Interface
109 Processor Supplement (PowerPC Processor ABI Supplement) rather than the calling
110 sequence used in GCC version 2.7.0. That calling sequence was based on the AIX
111 calling sequence without function descriptors. To compile code for that older
112 calling sequence, either configure the compiler for powerpc-*-eabiaix or use
113 the -mcall-aix switch when compiling and linking.
115 Noteworthy changes in GCC version 2.7.0:
117 GCC now works better on systems that use ".obj" and ".exe" instead of
118 ".o" and no extension. This involved changes to the driver program,
119 gcc.c, to convert ".o" names to ".obj" and to GCC's Makefile to use
120 ".obj" and ".exe" in filenames that are not targets. In order to
121 build GCC on such systems, you may need versions of GNU make and/or
122 compatible shells. At this point, this support is preliminary.
124 Object file extensions of ".obj" and executable file extensions of
125 ".exe" are allowed when using appropriate version of GNU Make.
127 Numerous enhancements were made to the __attribute__ facility including
128 more attributes and more places that support it. We now support the
129 "packed", "nocommon", "noreturn", "volatile", "const", "unused",
130 "transparent_union", "constructor", "destructor", "mode", "section",
131 "align", "format", "weak", and "alias" attributes. Each of these
132 names may also be specified with added underscores, e.g., "__packed__".
133 __attribute__ may now be applied to parameter definitions, function
134 definitions, and structure, enum, and union definitions.
136 GCC now supports returning more structures in registers, as specified by
137 many calling sequences (ABIs), such as on the HP PA RISC.
139 A new option '-fpack-struct' was added to automatically pack all structure
140 members together without holes.
142 There is a new library (cpplib) and program (cppmain) that at some
143 point will replace cpp (aka cccp). To use cppmain as cpp now, pass
144 the option CCCP=cppmain to make. The library is already used by the
145 fix-header program, which should speed up the fixproto script.
147 New options for supported targets:
150 NetBSD on MIPS, m68k, VAX, and x86.
151 LynxOS on x86, m68k, Sparc, and RS/6000.
152 VxWorks on many targets.
154 Windows/NT on x86 architecture. Initial support for Windows/NT on Alpha
157 Many embedded targets, specifically UDI on a29k, aout, coff, elf,
158 and vsta "operating systems" on m68k, m88k, mips, sparc, and x86.
160 Additional support for x86 (i386, i486, and Pentium):
162 Work with old and new linkers for Linux-based GNU systems,
163 supporting both a.out and ELF.
166 -malign-double, -mregparm=, -malign-loops= and -malign-jumps= switches.
167 On ISC systems, support -Xp like -posix.
169 Additions for RS/6000:
171 Instruction scheduling information for PowerPC 403.
173 -mstring and -mno-string.
174 -msoft-float and floating-point emulation included.
175 Preliminary support for PowerPC System V.4 with or without the GNU as.
176 Preliminary support for EABI.
177 Preliminary support for 64-bit systems.
178 Both big and little endian systems.
180 New features for MIPS-based systems:
186 Allow dollar signs in labels on SGI/Irix 5.x.
188 New support for HP PA RISC:
190 Generation of PIC (requires binutils-2.5.2.u6 or later).
191 HP-UX version 9 on HP PA RISC (dynamically links even with -g).
192 Processor variants for HP PA RISC: 700, 7100, and 7100LC.
193 Automatic generation of long calls when needed.
194 -mfast-indirect-calls for kernels and static binaries.
196 The called routine now copies arguments passed by invisible reference,
197 as required by the calling standard.
199 Other new miscellaneous target-specific support:
202 -mold-align for i960.
203 Configuration for "semi-hosted" ARM.
204 -momit-leaf-frame-pointer for M88k.
205 SH3 variant of Hitachi Super-H and support both big and little endian.
207 Changes to Objective-C:
209 Bare-bones implementation of NXConstantString has been added,
210 which is invoked by the @"string" directive.
212 Class * has been changed to Class to conform to the NextSTEP and
215 Enhancements to make dynamic loading easier.
217 The module version number has been updated to Version 7, thus existing
218 code will need to be recompiled to use the current run-time library.
220 GCC now supports the ISO Normative Addendum 1 to the C Standard.
223 The header <iso646.h> defines macros for C programs written
224 in national variants of ISO 646.
226 The following digraph tokens are supported:
228 These behave like the following, respectively:
231 Digraph tokens are supported unless you specify the `-traditional'
232 option; you do not need to specify `-ansi' or `-trigraphs'. Except
233 for contrived and unlikely examples involving preprocessor
234 stringizing, digraph interpretation doesn't change the meaning of
235 programs; this is unlike trigraph interpretation, which changes the
236 meanings of relatively common strings.
238 The macro __STDC_VERSION__ has the value 199409L.
240 As usual, for full conformance to the standard, you also need a
241 C library that conforms.
243 The following lists changes that have been made to g++. If some
244 features mentioned below sound unfamiliar, you will probably want to
245 look at the recently-released public review copy of the C++ Working
246 Paper. For PostScript and PDF (Adobe Acrobat) versions, see the
247 archive at ftp://research.att.com/dist/stdc++/WP. For HTML and ASCII
248 versions, see ftp://ftp.cygnus.com/pub/g++. On the web, see
249 http://www.cygnus.com/~mrs/wp-draft.
251 The scope of variables declared in the for-init-statement has been changed
252 to conform to http://www.cygnus.com/~mrs/wp-draft/stmt.html#stmt.for; as a
253 result, packages such as groff 1.09 will not compile unless you specify the
254 -fno-for-scope flag. PLEASE DO NOT REPORT THIS AS A BUG; this is a change
255 mandated by the C++ standardization committee.
257 Binary incompatibilities:
259 The builtin 'bool' type is now the size of a machine word on RISC targets,
260 for code efficiency; it remains one byte long on CISC targets.
262 Code that does not use #pragma interface/implementation will most
263 likely shrink dramatically, as g++ now only emits the vtable for a
264 class in the translation unit where its first non-inline, non-abstract
265 virtual function is defined.
267 Classes that do not define the copy constructor will sometimes be
268 passed and returned in registers. This may illuminate latent bugs in
271 Support for automatic template instantiation has *NOT* been added, due
272 to a disagreement over design philosophies.
274 Support for exception handling has been improved; more targets are now
275 supported, and throws will use the RTTI mechanism to match against the
276 catch parameter type. Optimization is NOT SUPPORTED with
277 -fhandle-exceptions; no need to report this as a bug.
279 Support for Run-Time Type Identification has been added with -frtti.
280 This support is still in alpha; one major restriction is that any file
281 compiled with -frtti must include <typeinfo.h>.
283 Preliminary support for namespaces has been added. This support is far
284 from complete, and probably not useful.
286 Synthesis of compiler-generated constructors, destructors and
287 assignment operators is now deferred until the functions are used.
289 The parsing of expressions such as `a ? b : c = 1' has changed from
290 `(a ? b : c) = 1' to `a : b ? (c = 1)'.
292 The code generated for testing conditions, especially those using ||
293 and &&, is now more efficient.
295 The operator keywords and, and_eq, bitand, bitor, compl, not, not_eq,
296 or, or_eq, xor and xor_eq are now supported. Use -ansi or
297 -foperator-names to enable them.
299 The 'explicit' keyword is now supported. 'explicit' is used to mark
300 constructors and type conversion operators that should not be used
303 g++ now accepts the typename keyword, though it currently has no
304 semantics; it can be a no-op in the current template implementation.
305 You may want to start using it in your code, however, since the
306 pending rewrite of the template implementation to compile STL properly
307 (perhaps for 2.8.0, perhaps not) will require you to use it as
308 indicated by the current draft.
310 Handling of user-defined type conversion has been overhauled so that
311 type conversion operators are now found and used properly in
312 expressions and function calls.
314 -fno-strict-prototype now only applies to function declarations with
317 g++ now warns about 'if (x=0)' with -Wparentheses or -Wall.
319 #pragma weak and #pragma pack are supported on System V R4 targets, as
320 are various other target-specific #pragmas supported by gcc.
322 new and delete of const types is now allowed (with no additional
325 Explicit instantiation of template methods is now supported. Also,
326 'inline template class foo<int>;' can be used to emit only the vtable
327 for a template class.
329 With -fcheck-new, g++ will check the return value of all calls to
330 operator new, and not attempt to modify a returned null pointer.
332 The template instantiation code now handles more conversions when
333 passing to a parameter that does not depend on template arguments.
334 This means that code like 'string s; cout << s;' now works.
336 Invalid jumps in a switch statement past declarations that require
337 initializations are now caught.
339 Functions declared 'extern inline' now have the same linkage semantics
340 as inline member functions. On supported targets, where previously
341 these functions (and vtables, and template instantiations) would have
342 been defined statically, they will now be defined as weak symbols so
343 that only one out-of-line definition is used.
345 collect2 now demangles linker output, and c++filt has become part of
346 the gcc distribution.
348 Noteworthy changes in GCC version 2.6.3:
350 A few more bugs have been fixed.
352 Noteworthy changes in GCC version 2.6.2:
354 A few bugs have been fixed.
356 Names of attributes can now be preceded and followed by double underscores.
358 Noteworthy changes in GCC version 2.6.1:
360 Numerous (mostly minor) bugs have been fixed.
362 The following new configurations are supported:
364 GNU on x86 (instead of treating it like MACH)
365 NetBSD on Sparc and Motorola 68k
366 AIX 4.1 on RS/6000 and PowerPC systems
367 Sequent DYNUX/ptx 1.x and 2.x.
368 Both COFF and ELF configurations on AViiON without using /bin/gcc
369 Windows/NT on x86 architecture; preliminary
370 AT&T DSP1610 digital signal processor chips
371 i960 systems on bare boards using COFF
372 PDP11; target only and not extensively tested
374 The -pg option is now supported for Alpha under OSF/1 V3.0 or later.
376 Files with an extension of ".c++" are treated as C++ code.
378 The -Xlinker and -Wl arguments are now passed to the linker in the
379 position they were specified on the command line. This makes it
380 possible, for example, to pass flags to the linker about specific
383 The use of positional arguments to the configure script is no longer
384 recommended. Use --target= to specify the target; see the GCC manual.
386 The 386 now supports two new switches: -mreg-alloc=<string> changes
387 the default register allocation order used by the compiler, and
388 -mno-wide-multiply disables the use of the mul/imul instructions that
389 produce 64 bit results in EAX:EDX from 32 bit operands to do long long
390 multiplies and 32-bit division by constants.
392 Noteworthy changes in GCC version 2.6.0:
394 Numerous bugs have been fixed, in the C and C++ front-ends, as
395 well as in the common compiler code.
397 This release includes the C, Objective-C, and C++ compilers. However,
398 we have moved the files for the C++ compiler (G++) files to a
399 subdirectory, cp. Subsequent releases of GCC will split these files
400 to a separate TAR file.
402 The G++ team has been tracking the development of the ANSI standard for C++.
403 Here are some new features added from the latest working paper:
405 * built-in boolean type 'bool', with constants 'true' and 'false'.
406 * array new and delete (operator new [] and delete []).
407 * WP-conforming lifetime of temporaries.
408 * explicit instantiation of templates (template class A<int>;),
409 along with an option (-fno-implicit-templates) to disable emission
410 of implicitly instantiated templates, obsoletes -fexternal-templates.
411 * static member constants (static const int foo = 4; within the
414 Many error messages have been improved to tell the user more about the
415 problem. Conformance checking with -pedantic-errors has been
416 improved. G++ now compiles Fresco.
418 There is now an experimental implementation of virtual functions using
419 thunks instead of Cfront-style vtables, enabled with -fvtable-thunks.
420 This option also enables a heuristic which causes the compiler to only
421 emit the vtable in the translation unit where its first non-inline
422 virtual function is defined; using this option and
423 -fno-implicit-templates, users should be able to avoid #pragma
424 interface/implementation altogether.
426 Signatures have been added as a GNU C++ extension. Using the option
427 -fhandle-signatures, users are able to turn on recognition of
428 signatures. A short introduction on signatures is in the section
429 `Extension to the C++ Language' in the manual.
431 The `g++' program is now a C program, rather than a shell script.
433 Lots and lots and lots of bugs fixes, in nested types, access control,
434 pointers to member functions, the parser, templates, overload
435 resolution, etc, etc.
437 There have been two major enhancements to the Objective-C compiler:
439 1) Added portability. It now runs on Alpha, and some problems with
440 message forwarding have been addressed on other platforms.
442 2) Selectors have been redefined to be pointers to structs like:
443 { void *sel_id, char *sel_types }, where the sel_id is the unique
444 identifier, the selector itself is no longer unique.
446 Programmers should use the new function sel_eq to test selector
449 The following major changes have been made to the base compiler and
450 machine-specific files.
452 - The MIL-STD-1750A is a new port, but still preliminary.
454 - The h8/300h is now supported; both the h8/300 and h8/300h ports come
455 with 32 bit IEEE 754 software floating point support.
457 - The 64-bit Sparc (v9) and 64-bit MIPS chips are supported.
459 - NetBSD is supported on m68k, Intel x86, and pc523 systems and FreeBSD
462 - COFF is supported on x86, m68k, and Sparc systems running LynxOS.
464 - 68K systems from Bull and Concurrent are supported and System V
465 Release 4 is supported on the Atari.
467 - GCC supports GAS on the Motorola 3300 (sysV68) and debugging
468 (assuming GAS) on the Plexus 68K system. (However, GAS does not yet
469 work on those systems).
471 - System V Release 4 is supported on MIPS (Tandem).
473 - For DG/UX, an ELF configuration is now supported, and both the ELF
474 and BCS configurations support ELF and COFF object file formats.
476 - OSF/1 V2.0 is supported on Alpha.
478 - Function profiling is also supported on Alpha.
480 - GAS and GDB is supported for Irix 5 (MIPS).
482 - "common mode" (code that will run on both POWER and PowerPC
483 architectures) is now supported for the RS/6000 family; the
484 compiler knows about more PPC chips.
486 - Both NeXTStep 2.1 and 3 are supported on 68k-based architectures.
488 - On the AMD 29k, the -msoft-float is now supported, as well as
489 -mno-sum-in-toc for RS/6000, -mapp-regs and -mflat for Sparc, and
490 -membedded-pic for MIPS.
492 - GCC can now convert division by integer constants into the equivalent
493 multiplication and shift operations when that is faster than the
496 - Two new warning options, -Wbad-function-cast and
497 -Wmissing-declarations have been added.
499 - Configurations may now add machine-specific __attribute__ options on
500 type; many machines support the `section' attribute.
502 - The -ffast-math flag permits some optimization that violate strict
503 IEEE rules, such as converting X * 0.0 to 0.0.
505 Noteworthy changes in GCC version 2.5.8:
507 This release only fixes a few serious bugs. These include fixes for a
508 bug that prevented most programs from working on the RS/6000, a bug
509 that caused invalid assembler code for programs with a `switch'
510 statement on the NS32K, a G++ problem that caused undefined names in
511 some configurations, and several less serious problems, some of which
512 can affect most configuration.
514 Noteworthy change in GCC version 2.5.7:
516 This release only fixes a few bugs, one of which was causing bootstrap
517 compare errors on some systems.
519 Noteworthy change in GCC version 2.5.6:
521 A few backend bugs have been fixed, some of which only occur on one
524 The C++ compiler in 2.5.6 includes:
526 * fixes for some common crashes
527 * correct handling of nested types that are referenced as `foo::bar'
528 * spurious warnings about friends being declared static and never
529 defined should no longer appear
530 * enums that are local to a method in a class, or a class that's
531 local to a function, are now handled correctly. For example:
532 class foo { void bar () { enum { x, y } E; x; } };
533 void bar () { class foo { enum { x, y } E; E baz; }; }
535 Noteworthy change in GCC version 2.5.5:
537 A large number of C++ bugs have been fixed.
539 The fixproto script adds prototypes conditionally on __cplusplus.
541 Noteworthy change in GCC version 2.5.4:
543 A bug fix in passing of structure arguments for the HP-PA architecture
544 makes code compiled with GCC 2.5.4 incompatible with code compiled
545 with earlier versions (if it passes struct arguments of 33 to 64 bits,
546 interspersed with other types of arguments).
548 Noteworthy change in gcc version 2.5.3:
550 The method of "mangling" C++ function names has been changed. So you
551 must recompile all C++ programs completely when you start using GCC
552 2.5. Also, GCC 2.5 requires libg++ version 2.5. Earlier libg++
553 versions won't work with GCC 2.5. (This is generally true--GCC
554 version M.N requires libg++ version M.N.)
556 Noteworthy GCC changes in version 2.5:
558 * There is now support for the IBM 370 architecture as a target.
559 Currently the only operating system supported is MVS; GCC does not run
560 on MVS, so you must produce .s files using GCC as a cross compiler,
561 then transfer them to MVS to assemble them. This port is not reliable
564 * The Power PC is now supported.
566 * The i860-based Paragon machine is now supported.
568 * The Hitachi 3050 (an HP-PA machine) is now supported.
570 * The variable __GNUC_MINOR__ holds the minor version number of GCC, as
571 an integer. For version 2.5.X, the value is 5.
573 * In C, initializers for static and global variables are now processed
574 an element at a time, so that they don't need a lot of storage.
576 * The C syntax for specifying which structure field comes next in an
577 initializer is now `.FIELDNAME='. The corresponding syntax for
578 array initializers is now `[INDEX]='. For example,
581 = { [' '] = 1, ['\t'] = 1, ['\n'] = 1 };
583 This was changed to accord with the syntax proposed by the Numerical
584 C Extensions Group (NCEG).
586 * Complex numbers are now supported in C. Use the keyword __complex__
587 to declare complex data types. See the manual for details.
589 * GCC now supports `long double' meaningfully on the Sparc (128-bit
590 floating point) and on the 386 (96-bit floating point). The Sparc
591 support is enabled on on Solaris 2.x because earlier system versions
592 (SunOS 4) have bugs in the emulation.
594 * All targets now have assertions for cpu, machine and system. So you
595 can now use assertions to distinguish among all supported targets.
597 * Nested functions in C may now be inline. Just declare them inline
600 * Packed structure members are now supported fully; it should be possible
601 to access them on any supported target, no matter how little alignment
604 * To declare that a function does not return, you must now write
605 something like this (works only in 2.5):
607 void fatal () __attribute__ ((noreturn));
609 or like this (works in older versions too):
611 typedef void voidfn ();
613 volatile voidfn fatal;
615 It used to be possible to do so by writing this:
617 volatile void fatal ();
619 but it turns out that ANSI C requires that to mean something
620 else (which is useless).
622 Likewise, to declare that a function is side-effect-free
623 so that calls may be deleted or combined, write
624 something like this (works only in 2.5):
626 int computation () __attribute__ ((const));
628 or like this (works in older versions too):
630 typedef int intfn ();
632 const intfn computation;
634 * The new option -iwithprefixbefore specifies a directory to add to
635 the search path for include files in the same position where -I would
636 put it, but uses the specified prefix just like -iwithprefix.
638 * Basic block profiling has been enhanced to record the function the
639 basic block comes from, and if the module was compiled for debugging,
640 the line number and filename. A default version of the basic block
641 support module has been added to libgcc2 that appends the basic block
642 information to a text file 'bb.out'. Machine descriptions can now
643 override the basic block support module in the target macro file.
647 * The new flag `-fansi-overloading' for C++. Use a newly implemented
648 scheme of argument matching for C++. It makes g++ more accurately
649 obey the rules set down in Chapter 13 of the Annotated C++ Reference
650 Manual (the ARM). This option will be turned on by default in a
653 * The -finline-debug flag is now gone (it was never really used by the
656 * Recognizing the syntax for pointers to members, e.g., "foo::*bar", has been
657 dramatically improved. You should not get any syntax errors or incorrect
658 runtime results while using pointers to members correctly; if you do, it's
661 * Forward declaration of an enum is now flagged as an error.
663 * Class-local typedefs are now working properly.
665 * Nested class support has been significantly improved. The compiler
666 will now (in theory) support up to 240 nested classes before hitting
667 other system limits (like memory size).
669 * There is a new C version of the `g++' driver, to replace the old
670 shell script. This should significantly improve the performance of
671 executing g++ on a system where a user's PATH environment variable
672 references many NFS-mounted filesystems. This driver also works
673 under MS-DOS and OS/2.
675 * The ANSI committee working on the C++ standard has adopted a new
676 keyword `mutable'. This will allow you to make a specific member be
677 modifiable in an otherwise const class.
679 Noteworthy GCC changes in version 2.4.4:
681 A crash building g++ on various hosts (including m68k) has been
682 fixed. Also the g++ compiler no longer reports incorrect
683 ambiguities in some situations where they do not exist, and
684 const template member functions are now being found properly.
686 Noteworthy GCC changes in version 2.4:
688 * On each target, the default is now to return short structures
689 compatibly with the "usual" compiler on that target.
691 For most targets, this means the default is to return all structures
692 in memory, like long structures, in whatever way is used on that
693 target. Use -freg-struct-return to enable returning short structures
694 (and unions) in registers.
696 This change means that newly compiled binaries are incompatible with
697 binaries compiled with previous versions of GCC.
699 On some targets, GCC is itself the usual compiler. On these targets,
700 the default way to return short structures is still in registers.
701 Use -fpcc-struct-return to tell GCC to return them in memory.
703 * There is now a floating point emulator which can imitate the way all
704 supported target machines do floating point arithmetic.
706 This makes it possible to have cross compilation to and from the VAX,
707 and between machines of different endianness. However, this works
708 only when the target machine description is updated to use the new
709 facilities, and not all have been updated.
711 This also makes possible support for longer floating point types.
712 GCC 2.4 supports extended format on the 68K if you use `long double',
713 for targets that have a 68881. (When we have run time library
714 routines for extended floating point, then `long double' will use
715 extended format on all 68K targets.)
717 We expect to support extended floating point on the i386 and Sparc in
720 * Building GCC now automatically fixes the system's header files.
721 This should require no attention.
723 * GCC now installs an unsigned data type as size_t when it fixes the
724 header files (on all but a handful of old target machines).
725 Therefore, the bug that size_t failed to be unsigned is fixed.
727 * Building and installation are now completely separate.
728 All new files are constructed during the build process;
729 installation just copies them.
731 * New targets supported: Clipper, Hitachi SH, Hitachi 8300, and Sparc
734 * A totally new and much better Objective C run time system is included.
736 * Objective C supports many new features. Alas, I can't describe them
737 since I don't use that language; however, they are the same ones
738 supported in recent versions of the NeXT operating system.
740 * The builtin functions __builtin_apply_args, __builtin_apply and
741 __builtin_return let you record the arguments and returned
742 value of a function without knowing their number or type.
744 * The builtin string variables __FUNCTION__ and __PRETTY_FUNCTION__
745 give the name of the function in the source, and a pretty-printed
746 version of the name. The two are the same in C, but differ in C++.
748 * Casts to union types do not yield lvalues.
750 * ## before an empty rest argument discards the preceding sequence
751 of non-whitespace characters from the macro definition.
752 (This feature is subject to change.)
755 New features specific to C++:
757 * The manual contains a new section ``Common Misunderstandings with
758 GNU C++'' that C++ users should read.
760 * #pragma interface and #pragma implementation let you use the same
761 C++ source file for both interface and implementation.
762 However, this mechanism is still in transition.
764 * Named returned values let you avoid an extra constructor call
765 when a function result has a class type.
767 * The C++ operators <? and >? yield min and max, respectively.
769 * C++ gotos can exit a block safely even if the block has
770 aggregates that require destructors.
772 * gcc defines the macro __GNUG__ when compiling C++ programs.
774 * GNU C++ now correctly distinguishes between the prefix and postfix
775 forms of overloaded operator ++ and --. To avoid breaking old
776 code, if a class defines only the prefix form, the compiler
777 accepts either ++obj or obj++, unless -pedantic is used.
779 * If you are using version 2.3 of libg++, you need to rebuild it with
780 `make CC=gcc' to avoid mismatches in the definition of `size_t'.
782 Newly documented compiler options:
785 Omit the standard system startup files when linking.
788 Consider memory references to extern and global data items to
792 Add DIR to the second include path.
795 Specify PREFIX for later -iwithprefix options.
798 Add PREFIX/DIR to the second include path.
801 Emit Sparc v8 code (with integer multiply and divide).
803 Emit Sparclite code (roughly v7.5).
805 -print-libgcc-file-name
806 Search for the libgcc.a file, print its absolute file name, and exit.
809 Warn when a derived class function declaration may be an error
810 in defining a C++ virtual function.
813 When using templates in a C++ program, warn if debugging is
814 not yet fully available.
817 Control how C++ virtual function definitions are used