diff -Nrc3pad gcc-3.2.2/.brik gcc-3.2.3/.brik *** gcc-3.2.2/.brik Wed Feb 5 03:55:24 2003 --- gcc-3.2.3/.brik Tue Apr 22 09:56:16 2003 *************** *** 4,32 **** # ------ -------- 3205162104b ./.cvsignore ! 2801352305b ./BUGS 2171125041b ./COPYING 508743035b ./COPYING.LIB ! 3927827037b ./ChangeLog ! 2859733475b ./FAQ 4190923194b ./GNATS 2229468985b ./INSTALL/README ! 2594642159b ./INSTALL/binaries.html ! 1150299172b ./INSTALL/build.html ! 2138152758b ./INSTALL/configure.html ! 1908954708b ./INSTALL/download.html ! 827688179b ./INSTALL/finalinstall.html ! 2784342709b ./INSTALL/gfdl.html ! 686439052b ./INSTALL/index.html ! 798593089b ./INSTALL/old.html ! 1770994652b ./INSTALL/specific.html ! 379139745b ./INSTALL/test.html 4287295648b ./MAINTAINERS 3313742257b ./Makefile.in 3697693037b ./README 655018850b ./boehm-gc/AmigaOS.c 2411687152b ./boehm-gc/BCC_MAKEFILE ! 1277390130b ./boehm-gc/ChangeLog 3428452570b ./boehm-gc/EMX_MAKEFILE 145946109b ./boehm-gc/MacOS.c 591574792b ./boehm-gc/MacProjects.sit.hqx --- 4,32 ---- # ------ -------- 3205162104b ./.cvsignore ! 2680648595b ./BUGS 2171125041b ./COPYING 508743035b ./COPYING.LIB ! 3991841618b ./ChangeLog ! 835327280b ./FAQ 4190923194b ./GNATS 2229468985b ./INSTALL/README ! 1594371290b ./INSTALL/binaries.html ! 984517660b ./INSTALL/build.html ! 850286653b ./INSTALL/configure.html ! 3411038527b ./INSTALL/download.html ! 371279032b ./INSTALL/finalinstall.html ! 2697832096b ./INSTALL/gfdl.html ! 3334357163b ./INSTALL/index.html ! 503704929b ./INSTALL/old.html ! 4178635678b ./INSTALL/specific.html ! 2431446841b ./INSTALL/test.html 4287295648b ./MAINTAINERS 3313742257b ./Makefile.in 3697693037b ./README 655018850b ./boehm-gc/AmigaOS.c 2411687152b ./boehm-gc/BCC_MAKEFILE ! 1966835067b ./boehm-gc/ChangeLog 3428452570b ./boehm-gc/EMX_MAKEFILE 145946109b ./boehm-gc/MacOS.c 591574792b ./boehm-gc/MacProjects.sit.hqx *************** *** 183,194 **** 2467355438b ./boehm-gc/typd_mlc.c 332085760b ./boehm-gc/version.h 3326583566b ./boehm-gc/win32_threads.c ! 2509440942b ./bugs.html ! 3139906847b ./config-ml.in 3794184949b ./config.guess 1864899138b ./config.if 537897852b ./config.sub ! 3400028451b ./config/ChangeLog 3004978457b ./config/acinclude.m4 3007349820b ./config/mh-a68bsd 1442196770b ./config/mh-aix386 --- 183,194 ---- 2467355438b ./boehm-gc/typd_mlc.c 332085760b ./boehm-gc/version.h 3326583566b ./boehm-gc/win32_threads.c ! 1129492486b ./bugs.html ! 1583135805b ./config-ml.in 3794184949b ./config.guess 1864899138b ./config.if 537897852b ./config.sub ! 114139691b ./config/ChangeLog 3004978457b ./config/acinclude.m4 3007349820b ./config/mh-a68bsd 1442196770b ./config/mh-aix386 *************** *** 232,238 **** 456622165b ./config/mh-vaxult2 3265825290b ./config/mh-x86pic 198559626b ./config/mpw-mh-mpw ! 1384213553b ./config/mpw/ChangeLog 3145098931b ./config/mpw/MoveIfChange 1476422091b ./config/mpw/README 4005879853b ./config/mpw/forward-include --- 232,238 ---- 456622165b ./config/mh-vaxult2 3265825290b ./config/mh-x86pic 198559626b ./config/mpw-mh-mpw ! 108267066b ./config/mpw/ChangeLog 3145098931b ./config/mpw/MoveIfChange 1476422091b ./config/mpw/README 4005879853b ./config/mpw/forward-include *************** *** 262,268 **** 771382916b ./config/mt-x86pic 2416042097b ./configure 3230279174b ./configure.in ! 2762145970b ./contrib/ChangeLog 1948950130b ./contrib/analyze_brprob 550196746b ./contrib/compare_tests 2828387446b ./contrib/convert_to_f2c --- 262,268 ---- 771382916b ./config/mt-x86pic 2416042097b ./configure 3230279174b ./configure.in ! 3512451768b ./contrib/ChangeLog 1948950130b ./contrib/analyze_brprob 550196746b ./contrib/compare_tests 2828387446b ./contrib/convert_to_f2c *************** *** 274,280 **** 109296376b ./contrib/gennews 4256039795b ./contrib/index-prop 3683285493b ./contrib/newcvsroot ! 1731874216b ./contrib/regression/ChangeLog 1757898889b ./contrib/regression/README 1596938872b ./contrib/regression/btest-gcc.sh 4208566980b ./contrib/regression/objs-gcc.sh --- 274,280 ---- 109296376b ./contrib/gennews 4256039795b ./contrib/index-prop 3683285493b ./contrib/newcvsroot ! 2125180271b ./contrib/regression/ChangeLog 1757898889b ./contrib/regression/README 1596938872b ./contrib/regression/btest-gcc.sh 4208566980b ./contrib/regression/objs-gcc.sh *************** *** 283,293 **** 2523431553b ./contrib/test_summary 3362750683b ./contrib/texi2pod.pl 4228623080b ./contrib/warn_summary ! 3102205468b ./faq.html 1005262133b ./fastjar/AUTHORS 1745615150b ./fastjar/CHANGES 1396100520b ./fastjar/COPYING ! 1593465022b ./fastjar/ChangeLog 2770615802b ./fastjar/INSTALL 3714739366b ./fastjar/Makefile.am 39617579b ./fastjar/Makefile.in --- 283,293 ---- 2523431553b ./contrib/test_summary 3362750683b ./contrib/texi2pod.pl 4228623080b ./contrib/warn_summary ! 2887273247b ./faq.html 1005262133b ./fastjar/AUTHORS 1745615150b ./fastjar/CHANGES 1396100520b ./fastjar/COPYING ! 4056720975b ./fastjar/ChangeLog 2770615802b ./fastjar/INSTALL 3714739366b ./fastjar/Makefile.am 39617579b ./fastjar/Makefile.in *************** *** 318,324 **** 1758308615b ./gcc/ABOUT-NLS 2171125041b ./gcc/COPYING 508743035b ./gcc/COPYING.LIB ! 4098147965b ./gcc/ChangeLog 1398127668b ./gcc/ChangeLog.0 2827765101b ./gcc/ChangeLog.1 1199055802b ./gcc/ChangeLog.2 --- 318,324 ---- 1758308615b ./gcc/ABOUT-NLS 2171125041b ./gcc/COPYING 508743035b ./gcc/COPYING.LIB ! 2608914462b ./gcc/ChangeLog 1398127668b ./gcc/ChangeLog.0 2827765101b ./gcc/ChangeLog.1 1199055802b ./gcc/ChangeLog.2 *************** *** 332,338 **** 3797967515b ./gcc/FSFChangeLog.11 4134111346b ./gcc/LANGUAGES 214390302b ./gcc/Makefile.in ! 435752999b ./gcc/NEWS 538471119b ./gcc/ONEWS 2799003008b ./gcc/README-fixinc 2741038711b ./gcc/README.Portability --- 332,338 ---- 3797967515b ./gcc/FSFChangeLog.11 4134111346b ./gcc/LANGUAGES 214390302b ./gcc/Makefile.in ! 1084812157b ./gcc/NEWS 538471119b ./gcc/ONEWS 2799003008b ./gcc/README-fixinc 2741038711b ./gcc/README.Portability *************** *** 532,541 **** 1989930650b ./gcc/ada/86numaux.adb 4223067829b ./gcc/ada/86numaux.ads 176063031b ./gcc/ada/9drpc.adb ! 1702217023b ./gcc/ada/ChangeLog ! 3231195932b ./gcc/ada/Make-lang.in 82447397b ./gcc/ada/Makefile.adalib ! 3584028360b ./gcc/ada/Makefile.in 1238937539b ./gcc/ada/a-astaco.adb 4160306902b ./gcc/ada/a-astaco.ads 1228169839b ./gcc/ada/a-caldel.adb --- 532,541 ---- 1989930650b ./gcc/ada/86numaux.adb 4223067829b ./gcc/ada/86numaux.ads 176063031b ./gcc/ada/9drpc.adb ! 3541119639b ./gcc/ada/ChangeLog ! 1021041780b ./gcc/ada/Make-lang.in 82447397b ./gcc/ada/Makefile.adalib ! 3683211435b ./gcc/ada/Makefile.in 1238937539b ./gcc/ada/a-astaco.adb 4160306902b ./gcc/ada/a-astaco.ads 1228169839b ./gcc/ada/a-caldel.adb *************** *** 1008,1014 **** 2835105488b ./gcc/ada/gnatprep.ads 3865862564b ./gcc/ada/gnatpsta.adb 3829654473b ./gcc/ada/gnatpsys.adb ! 1670534955b ./gcc/ada/gnatvsn.ads 2692053620b ./gcc/ada/gnatxref.adb 577038397b ./gcc/ada/hlo.adb 991320325b ./gcc/ada/hlo.ads --- 1008,1014 ---- 2835105488b ./gcc/ada/gnatprep.ads 3865862564b ./gcc/ada/gnatpsta.adb 3829654473b ./gcc/ada/gnatpsys.adb ! 4288634473b ./gcc/ada/gnatvsn.ads 2692053620b ./gcc/ada/gnatxref.adb 577038397b ./gcc/ada/hlo.adb 991320325b ./gcc/ada/hlo.ads *************** *** 1064,1070 **** 2167962937b ./gcc/ada/lib-xref.ads 1029825782b ./gcc/ada/lib.adb 1122008701b ./gcc/ada/lib.ads ! 3576767122b ./gcc/ada/link.c 1382287720b ./gcc/ada/live.adb 241788297b ./gcc/ada/live.ads 2349274909b ./gcc/ada/machcode.ads --- 1064,1070 ---- 2167962937b ./gcc/ada/lib-xref.ads 1029825782b ./gcc/ada/lib.adb 1122008701b ./gcc/ada/lib.ads ! 3273789304b ./gcc/ada/link.c 1382287720b ./gcc/ada/live.adb 241788297b ./gcc/ada/live.ads 2349274909b ./gcc/ada/machcode.ads *************** *** 1693,1740 **** 1423262391b ./gcc/alias.c 1031959714b ./gcc/attribs.c 3996983224b ./gcc/basic-block.h ! 534677057b ./gcc/bb-reorder.c 518972076b ./gcc/bitmap.c 477755928b ./gcc/bitmap.h 540939972b ./gcc/builtin-attrs.def 1736755746b ./gcc/builtin-types.def ! 3805127813b ./gcc/builtins.c 2454689977b ./gcc/builtins.def 420541423b ./gcc/c-aux-info.c 3749632892b ./gcc/c-common.c 2096270511b ./gcc/c-common.def 17222401b ./gcc/c-common.h 1317742909b ./gcc/c-convert.c ! 2201480607b ./gcc/c-decl.c 487899684b ./gcc/c-errors.c 1391364139b ./gcc/c-format.c 1985388077b ./gcc/c-lang.c 382517507b ./gcc/c-lex.c 835686435b ./gcc/c-lex.h 1191094530b ./gcc/c-objc-common.c ! 1694666955b ./gcc/c-parse.c 4048701711b ./gcc/c-parse.in 492383053b ./gcc/c-parse.y 73956308b ./gcc/c-pragma.c 1212765089b ./gcc/c-pragma.h 3567184655b ./gcc/c-semantics.c 2780104305b ./gcc/c-tree.h ! 2926467753b ./gcc/c-typeck.c 4196427447b ./gcc/caller-save.c 3428212111b ./gcc/calls.c 2908854975b ./gcc/cfg.c 2266313517b ./gcc/cfganal.c 2306033851b ./gcc/cfgbuild.c ! 1200507286b ./gcc/cfgcleanup.c 1219429812b ./gcc/cfglayout.c 1858346793b ./gcc/cfglayout.h 3236894730b ./gcc/cfgloop.c ! 2041391494b ./gcc/cfgrtl.c ! 1806916686b ./gcc/collect2.c 653998699b ./gcc/collect2.h ! 3893532884b ./gcc/combine.c 4122382037b ./gcc/conditions.h ! 595953330b ./gcc/config.gcc 1315260558b ./gcc/config.guess 1761565476b ./gcc/config.in 3356933371b ./gcc/config/1750a/1750a-protos.h --- 1693,1740 ---- 1423262391b ./gcc/alias.c 1031959714b ./gcc/attribs.c 3996983224b ./gcc/basic-block.h ! 3664924098b ./gcc/bb-reorder.c 518972076b ./gcc/bitmap.c 477755928b ./gcc/bitmap.h 540939972b ./gcc/builtin-attrs.def 1736755746b ./gcc/builtin-types.def ! 1602117951b ./gcc/builtins.c 2454689977b ./gcc/builtins.def 420541423b ./gcc/c-aux-info.c 3749632892b ./gcc/c-common.c 2096270511b ./gcc/c-common.def 17222401b ./gcc/c-common.h 1317742909b ./gcc/c-convert.c ! 3121341096b ./gcc/c-decl.c 487899684b ./gcc/c-errors.c 1391364139b ./gcc/c-format.c 1985388077b ./gcc/c-lang.c 382517507b ./gcc/c-lex.c 835686435b ./gcc/c-lex.h 1191094530b ./gcc/c-objc-common.c ! 707725569b ./gcc/c-parse.c 4048701711b ./gcc/c-parse.in 492383053b ./gcc/c-parse.y 73956308b ./gcc/c-pragma.c 1212765089b ./gcc/c-pragma.h 3567184655b ./gcc/c-semantics.c 2780104305b ./gcc/c-tree.h ! 1842642506b ./gcc/c-typeck.c 4196427447b ./gcc/caller-save.c 3428212111b ./gcc/calls.c 2908854975b ./gcc/cfg.c 2266313517b ./gcc/cfganal.c 2306033851b ./gcc/cfgbuild.c ! 1767622119b ./gcc/cfgcleanup.c 1219429812b ./gcc/cfglayout.c 1858346793b ./gcc/cfglayout.h 3236894730b ./gcc/cfgloop.c ! 697357307b ./gcc/cfgrtl.c ! 4092688391b ./gcc/collect2.c 653998699b ./gcc/collect2.h ! 1204798801b ./gcc/combine.c 4122382037b ./gcc/conditions.h ! 1610676755b ./gcc/config.gcc 1315260558b ./gcc/config.guess 1761565476b ./gcc/config.in 3356933371b ./gcc/config/1750a/1750a-protos.h *************** *** 1756,1762 **** 4085134134b ./gcc/config/alpha/alpha-protos.h 830149807b ./gcc/config/alpha/alpha.c 2486755494b ./gcc/config/alpha/alpha.h ! 1955091231b ./gcc/config/alpha/alpha.md 3915788506b ./gcc/config/alpha/alpha32.h 1407988137b ./gcc/config/alpha/crtfastmath.c 221364934b ./gcc/config/alpha/elf.h --- 1756,1762 ---- 4085134134b ./gcc/config/alpha/alpha-protos.h 830149807b ./gcc/config/alpha/alpha.c 2486755494b ./gcc/config/alpha/alpha.h ! 1672390089b ./gcc/config/alpha/alpha.md 3915788506b ./gcc/config/alpha/alpha32.h 1407988137b ./gcc/config/alpha/crtfastmath.c 221364934b ./gcc/config/alpha/elf.h *************** *** 1767,1773 **** 3901756355b ./gcc/config/alpha/linux.h 1830150315b ./gcc/config/alpha/netbsd.h 156117508b ./gcc/config/alpha/openbsd.h ! 2313475776b ./gcc/config/alpha/osf.h 1792826440b ./gcc/config/alpha/osf12.h 3744703656b ./gcc/config/alpha/osf2or3.h 2776242025b ./gcc/config/alpha/osf5.h --- 1767,1773 ---- 3901756355b ./gcc/config/alpha/linux.h 1830150315b ./gcc/config/alpha/netbsd.h 156117508b ./gcc/config/alpha/openbsd.h ! 4018452315b ./gcc/config/alpha/osf.h 1792826440b ./gcc/config/alpha/osf12.h 3744703656b ./gcc/config/alpha/osf2or3.h 2776242025b ./gcc/config/alpha/osf5.h *************** *** 1886,1892 **** 2623962717b ./gcc/config/cris/cris-protos.h 937590356b ./gcc/config/cris/cris.c 1846933412b ./gcc/config/cris/cris.h ! 3975834409b ./gcc/config/cris/cris.md 4228128527b ./gcc/config/cris/cris_abi_symbol.c 2550031006b ./gcc/config/cris/linux.h 907689569b ./gcc/config/cris/mulsi3.asm --- 1886,1892 ---- 2623962717b ./gcc/config/cris/cris-protos.h 937590356b ./gcc/config/cris/cris.c 1846933412b ./gcc/config/cris/cris.h ! 1799638103b ./gcc/config/cris/cris.md 4228128527b ./gcc/config/cris/cris_abi_symbol.c 2550031006b ./gcc/config/cris/linux.h 907689569b ./gcc/config/cris/mulsi3.asm *************** *** 1995,2003 **** 1321445318b ./gcc/config/i386/i386-interix.h 721929446b ./gcc/config/i386/i386-interix3.h 2589129574b ./gcc/config/i386/i386-protos.h ! 2391340311b ./gcc/config/i386/i386.c ! 1737688208b ./gcc/config/i386/i386.h ! 1643637147b ./gcc/config/i386/i386.md 2017248418b ./gcc/config/i386/i386elf.h 1164740130b ./gcc/config/i386/interix.c 3908393755b ./gcc/config/i386/isc.h --- 1995,2003 ---- 1321445318b ./gcc/config/i386/i386-interix.h 721929446b ./gcc/config/i386/i386-interix3.h 2589129574b ./gcc/config/i386/i386-protos.h ! 2676101452b ./gcc/config/i386/i386.c ! 1745281973b ./gcc/config/i386/i386.h ! 1385892283b ./gcc/config/i386/i386.md 2017248418b ./gcc/config/i386/i386elf.h 1164740130b ./gcc/config/i386/interix.c 3908393755b ./gcc/config/i386/isc.h *************** *** 2006,2013 **** 877642037b ./gcc/config/i386/libgcc-x86_64-glibc.ver 2999558891b ./gcc/config/i386/linux-aout.h 2799520524b ./gcc/config/i386/linux-oldld.h ! 2801664794b ./gcc/config/i386/linux.h ! 1758822745b ./gcc/config/i386/linux64.h 83628421b ./gcc/config/i386/lynx-ng.h 372710545b ./gcc/config/i386/lynx.h 4206477894b ./gcc/config/i386/mach.h --- 2006,2013 ---- 877642037b ./gcc/config/i386/libgcc-x86_64-glibc.ver 2999558891b ./gcc/config/i386/linux-aout.h 2799520524b ./gcc/config/i386/linux-oldld.h ! 767649862b ./gcc/config/i386/linux.h ! 2975476387b ./gcc/config/i386/linux64.h 83628421b ./gcc/config/i386/lynx-ng.h 372710545b ./gcc/config/i386/lynx.h 4206477894b ./gcc/config/i386/mach.h *************** *** 2212,2218 **** 1109594909b ./gcc/config/m68k/m68k-psos.h 1870424553b ./gcc/config/m68k/m68k.c 3756685982b ./gcc/config/m68k/m68k.h ! 1833592513b ./gcc/config/m68k/m68k.md 2287927144b ./gcc/config/m68k/m68kelf.h 1120822994b ./gcc/config/m68k/m68kemb.h 947783547b ./gcc/config/m68k/m68kv4.h --- 2212,2218 ---- 1109594909b ./gcc/config/m68k/m68k-psos.h 1870424553b ./gcc/config/m68k/m68k.c 3756685982b ./gcc/config/m68k/m68k.h ! 4063689296b ./gcc/config/m68k/m68k.md 2287927144b ./gcc/config/m68k/m68kelf.h 1120822994b ./gcc/config/m68k/m68kemb.h 947783547b ./gcc/config/m68k/m68kv4.h *************** *** 2324,2330 **** 2743944992b ./gcc/config/mips/iris4loser.h 4137712676b ./gcc/config/mips/iris5.h 1342606731b ./gcc/config/mips/iris5gas.h ! 2714897906b ./gcc/config/mips/iris6.h 2290690324b ./gcc/config/mips/iris6gld.h 3658812670b ./gcc/config/mips/irix6-libc-compat.c 3645898751b ./gcc/config/mips/isa32-linux.h --- 2324,2330 ---- 2743944992b ./gcc/config/mips/iris4loser.h 4137712676b ./gcc/config/mips/iris5.h 1342606731b ./gcc/config/mips/iris5gas.h ! 1473745020b ./gcc/config/mips/iris6.h 2290690324b ./gcc/config/mips/iris6gld.h 3658812670b ./gcc/config/mips/irix6-libc-compat.c 3645898751b ./gcc/config/mips/isa32-linux.h *************** *** 2332,2341 **** 1922092548b ./gcc/config/mips/linux.h 2202363688b ./gcc/config/mips/little.h 3112223626b ./gcc/config/mips/mips-5.h ! 4191298187b ./gcc/config/mips/mips-protos.h ! 4175300921b ./gcc/config/mips/mips.c ! 1450296441b ./gcc/config/mips/mips.h ! 3326013566b ./gcc/config/mips/mips.md 2024693888b ./gcc/config/mips/mips16.S 3451330990b ./gcc/config/mips/netbsd.h 1685635385b ./gcc/config/mips/news4.h --- 2332,2341 ---- 1922092548b ./gcc/config/mips/linux.h 2202363688b ./gcc/config/mips/little.h 3112223626b ./gcc/config/mips/mips-5.h ! 3798369178b ./gcc/config/mips/mips-protos.h ! 4292919872b ./gcc/config/mips/mips.c ! 1682195442b ./gcc/config/mips/mips.h ! 218198435b ./gcc/config/mips/mips.md 2024693888b ./gcc/config/mips/mips16.S 3451330990b ./gcc/config/mips/netbsd.h 1685635385b ./gcc/config/mips/news4.h *************** *** 2431,2440 **** 3618123809b ./gcc/config/pa/pa-oldas.h 3108768032b ./gcc/config/pa/pa-osf.h 2360373262b ./gcc/config/pa/pa-pro-end.h ! 1408239843b ./gcc/config/pa/pa-protos.h ! 4191862649b ./gcc/config/pa/pa.c ! 479563046b ./gcc/config/pa/pa.h ! 3424276871b ./gcc/config/pa/pa.md 2660241824b ./gcc/config/pa/pa32-linux.h 3627454173b ./gcc/config/pa/pa32-regs.h 3477747579b ./gcc/config/pa/pa64-hpux.h --- 2431,2440 ---- 3618123809b ./gcc/config/pa/pa-oldas.h 3108768032b ./gcc/config/pa/pa-osf.h 2360373262b ./gcc/config/pa/pa-pro-end.h ! 944974079b ./gcc/config/pa/pa-protos.h ! 4228751593b ./gcc/config/pa/pa.c ! 2873633316b ./gcc/config/pa/pa.h ! 756298139b ./gcc/config/pa/pa.md 2660241824b ./gcc/config/pa/pa32-linux.h 3627454173b ./gcc/config/pa/pa32-regs.h 3477747579b ./gcc/config/pa/pa64-hpux.h *************** *** 2505,2513 **** 926081320b ./gcc/config/rs6000/netbsd.h 4127185084b ./gcc/config/rs6000/ppc-asm.h 2986503806b ./gcc/config/rs6000/rs6000-protos.h ! 3651688118b ./gcc/config/rs6000/rs6000.c ! 1882734550b ./gcc/config/rs6000/rs6000.h ! 3597268251b ./gcc/config/rs6000/rs6000.md 111710449b ./gcc/config/rs6000/rtems.h 2439652147b ./gcc/config/rs6000/softfloat.h 3703627966b ./gcc/config/rs6000/sol-ci.asm --- 2505,2513 ---- 926081320b ./gcc/config/rs6000/netbsd.h 4127185084b ./gcc/config/rs6000/ppc-asm.h 2986503806b ./gcc/config/rs6000/rs6000-protos.h ! 4042212867b ./gcc/config/rs6000/rs6000.c ! 2995718160b ./gcc/config/rs6000/rs6000.h ! 1487812065b ./gcc/config/rs6000/rs6000.md 111710449b ./gcc/config/rs6000/rtems.h 2439652147b ./gcc/config/rs6000/softfloat.h 3703627966b ./gcc/config/rs6000/sol-ci.asm *************** *** 2602,2609 **** 1221714757b ./gcc/config/sparc/sp86x-elf.h 4023359087b ./gcc/config/sparc/sparc-protos.h 2169834781b ./gcc/config/sparc/sparc.c ! 3432806460b ./gcc/config/sparc/sparc.h ! 879790849b ./gcc/config/sparc/sparc.md 842964351b ./gcc/config/sparc/splet.h 952337645b ./gcc/config/sparc/sun4gas.h 1795303911b ./gcc/config/sparc/sun4o3.h --- 2602,2609 ---- 1221714757b ./gcc/config/sparc/sp86x-elf.h 4023359087b ./gcc/config/sparc/sparc-protos.h 2169834781b ./gcc/config/sparc/sparc.c ! 679741711b ./gcc/config/sparc/sparc.h ! 707642527b ./gcc/config/sparc/sparc.md 842964351b ./gcc/config/sparc/splet.h 952337645b ./gcc/config/sparc/sun4gas.h 1795303911b ./gcc/config/sparc/sun4o3.h *************** *** 2690,2698 **** 3617796239b ./gcc/config/xtensa/t-xtensa 2796950173b ./gcc/config/xtensa/xtensa-config.h 981915907b ./gcc/config/xtensa/xtensa-protos.h ! 1944987627b ./gcc/config/xtensa/xtensa.c ! 2453353978b ./gcc/config/xtensa/xtensa.h ! 830696041b ./gcc/config/xtensa/xtensa.md 2019129276b ./gcc/configure 2239237249b ./gcc/configure.frag 862560733b ./gcc/configure.in --- 2690,2698 ---- 3617796239b ./gcc/config/xtensa/t-xtensa 2796950173b ./gcc/config/xtensa/xtensa-config.h 981915907b ./gcc/config/xtensa/xtensa-protos.h ! 62812165b ./gcc/config/xtensa/xtensa.c ! 507316486b ./gcc/config/xtensa/xtensa.h ! 1348387747b ./gcc/config/xtensa/xtensa.md 2019129276b ./gcc/configure 2239237249b ./gcc/configure.frag 862560733b ./gcc/configure.in *************** *** 2700,2727 **** 2854418854b ./gcc/convert.c 2020855935b ./gcc/convert.h 1230086821b ./gcc/cp/.cvsignore ! 1023496053b ./gcc/cp/ChangeLog 2221404065b ./gcc/cp/ChangeLog.1 2127340768b ./gcc/cp/ChangeLog.2 2546444747b ./gcc/cp/ChangeLog.egcs 2368698010b ./gcc/cp/Make-lang.in 1710026913b ./gcc/cp/NEWS ! 211407592b ./gcc/cp/call.c 4115552602b ./gcc/cp/cfns.gperf 1705070232b ./gcc/cp/cfns.h ! 3828154577b ./gcc/cp/class.c 1309293181b ./gcc/cp/config-lang.in 4084279121b ./gcc/cp/cp-lang.c 2928114977b ./gcc/cp/cp-tree.def 3545021760b ./gcc/cp/cp-tree.h 67222431b ./gcc/cp/cvt.c ! 3933539524b ./gcc/cp/decl.c 3040950596b ./gcc/cp/decl.h ! 662263475b ./gcc/cp/decl2.c 1503739344b ./gcc/cp/dump.c ! 177845186b ./gcc/cp/error.c 197247511b ./gcc/cp/except.c ! 2612079645b ./gcc/cp/expr.c 728682437b ./gcc/cp/friend.c 1574667259b ./gcc/cp/g++.1 3180385434b ./gcc/cp/g++spec.c --- 2700,2727 ---- 2854418854b ./gcc/convert.c 2020855935b ./gcc/convert.h 1230086821b ./gcc/cp/.cvsignore ! 1795683420b ./gcc/cp/ChangeLog 2221404065b ./gcc/cp/ChangeLog.1 2127340768b ./gcc/cp/ChangeLog.2 2546444747b ./gcc/cp/ChangeLog.egcs 2368698010b ./gcc/cp/Make-lang.in 1710026913b ./gcc/cp/NEWS ! 2088201374b ./gcc/cp/call.c 4115552602b ./gcc/cp/cfns.gperf 1705070232b ./gcc/cp/cfns.h ! 596844565b ./gcc/cp/class.c 1309293181b ./gcc/cp/config-lang.in 4084279121b ./gcc/cp/cp-lang.c 2928114977b ./gcc/cp/cp-tree.def 3545021760b ./gcc/cp/cp-tree.h 67222431b ./gcc/cp/cvt.c ! 3585342875b ./gcc/cp/decl.c 3040950596b ./gcc/cp/decl.h ! 952368203b ./gcc/cp/decl2.c 1503739344b ./gcc/cp/dump.c ! 3569782164b ./gcc/cp/error.c 197247511b ./gcc/cp/except.c ! 516514444b ./gcc/cp/expr.c 728682437b ./gcc/cp/friend.c 1574667259b ./gcc/cp/g++.1 3180385434b ./gcc/cp/g++spec.c *************** *** 2736,2754 **** 4041177245b ./gcc/cp/mpw-make.sed 2349927434b ./gcc/cp/operators.def 622478745b ./gcc/cp/optimize.c ! 1765484930b ./gcc/cp/parse.c ! 3428647714b ./gcc/cp/parse.h 1544139953b ./gcc/cp/parse.y ! 1612002219b ./gcc/cp/pt.c 1408553642b ./gcc/cp/ptree.c 3993964584b ./gcc/cp/repo.c 2834061289b ./gcc/cp/rtti.c ! 161492685b ./gcc/cp/search.c 4064329742b ./gcc/cp/semantics.c 2648162646b ./gcc/cp/spew.c 3384697218b ./gcc/cp/tree.c 3946434476b ./gcc/cp/typeck.c ! 1284974262b ./gcc/cp/typeck2.c 1602205564b ./gcc/cppdefault.c 733799898b ./gcc/cppdefault.h 3582099799b ./gcc/cpperror.c --- 2736,2754 ---- 4041177245b ./gcc/cp/mpw-make.sed 2349927434b ./gcc/cp/operators.def 622478745b ./gcc/cp/optimize.c ! 230679025b ./gcc/cp/parse.c ! 586236678b ./gcc/cp/parse.h 1544139953b ./gcc/cp/parse.y ! 534531070b ./gcc/cp/pt.c 1408553642b ./gcc/cp/ptree.c 3993964584b ./gcc/cp/repo.c 2834061289b ./gcc/cp/rtti.c ! 1987668761b ./gcc/cp/search.c 4064329742b ./gcc/cp/semantics.c 2648162646b ./gcc/cp/spew.c 3384697218b ./gcc/cp/tree.c 3946434476b ./gcc/cp/typeck.c ! 3217357018b ./gcc/cp/typeck2.c 1602205564b ./gcc/cppdefault.c 733799898b ./gcc/cppdefault.h 3582099799b ./gcc/cpperror.c *************** *** 2789,2816 **** 3399730921b ./gcc/doc/configterms.texi 2163122922b ./gcc/doc/contrib.texi 2272556046b ./gcc/doc/contribute.texi ! 3074111847b ./gcc/doc/cpp.1 3543132597b ./gcc/doc/cpp.texi 1838233798b ./gcc/doc/cppenv.texi 1958814700b ./gcc/doc/cppinternals.texi 685869710b ./gcc/doc/cppopts.texi ! 1477628931b ./gcc/doc/extend.texi 2634996326b ./gcc/doc/fragments.texi 600815516b ./gcc/doc/frontends.texi ! 3214630123b ./gcc/doc/fsf-funding.7 ! 2397612846b ./gcc/doc/gcc.1 2344693999b ./gcc/doc/gcc.texi 926520134b ./gcc/doc/gccint.texi ! 2862847340b ./gcc/doc/gcov.1 2529603660b ./gcc/doc/gcov.texi ! 261077961b ./gcc/doc/gfdl.7 4217859569b ./gcc/doc/gnu.texi ! 1420728298b ./gcc/doc/gpl.7 2632697239b ./gcc/doc/headerdirs.texi 1425599017b ./gcc/doc/hostconfig.texi 1232987106b ./gcc/doc/include/fdl.texi 2048065465b ./gcc/doc/include/funding.texi ! 1759928844b ./gcc/doc/include/gcc-common.texi 1416455933b ./gcc/doc/include/gpl.texi 3627483023b ./gcc/doc/include/texinfo.tex 4219640220b ./gcc/doc/install-old.texi --- 2789,2871 ---- 3399730921b ./gcc/doc/configterms.texi 2163122922b ./gcc/doc/contrib.texi 2272556046b ./gcc/doc/contribute.texi ! 1535227762b ./gcc/doc/cpp.1 ! 1544384634b ./gcc/doc/cpp.info ! 757073472b ./gcc/doc/cpp.info-1 ! 3446855226b ./gcc/doc/cpp.info-2 ! 636644590b ./gcc/doc/cpp.info-3 ! 3499936017b ./gcc/doc/cpp.info-4 ! 3675380875b ./gcc/doc/cpp.info-5 3543132597b ./gcc/doc/cpp.texi 1838233798b ./gcc/doc/cppenv.texi + 1685544580b ./gcc/doc/cppinternals.info 1958814700b ./gcc/doc/cppinternals.texi 685869710b ./gcc/doc/cppopts.texi ! 3004272717b ./gcc/doc/extend.texi 2634996326b ./gcc/doc/fragments.texi 600815516b ./gcc/doc/frontends.texi ! 3256871866b ./gcc/doc/fsf-funding.7 ! 2658060989b ./gcc/doc/gcc.1 ! 4148415874b ./gcc/doc/gcc.info ! 1053864515b ./gcc/doc/gcc.info-1 ! 4294678088b ./gcc/doc/gcc.info-10 ! 1344046739b ./gcc/doc/gcc.info-11 ! 451582535b ./gcc/doc/gcc.info-12 ! 4084131178b ./gcc/doc/gcc.info-13 ! 1824645699b ./gcc/doc/gcc.info-14 ! 1310951679b ./gcc/doc/gcc.info-15 ! 3633708433b ./gcc/doc/gcc.info-16 ! 2461331410b ./gcc/doc/gcc.info-17 ! 4272216147b ./gcc/doc/gcc.info-18 ! 3012752365b ./gcc/doc/gcc.info-19 ! 2218006986b ./gcc/doc/gcc.info-2 ! 1322735281b ./gcc/doc/gcc.info-20 ! 471346850b ./gcc/doc/gcc.info-21 ! 2053165308b ./gcc/doc/gcc.info-22 ! 3102591020b ./gcc/doc/gcc.info-23 ! 2266643536b ./gcc/doc/gcc.info-3 ! 383482857b ./gcc/doc/gcc.info-4 ! 2120276990b ./gcc/doc/gcc.info-5 ! 2474168124b ./gcc/doc/gcc.info-6 ! 521005660b ./gcc/doc/gcc.info-7 ! 686614003b ./gcc/doc/gcc.info-8 ! 396552069b ./gcc/doc/gcc.info-9 2344693999b ./gcc/doc/gcc.texi + 1868552664b ./gcc/doc/gccint.info + 1364694741b ./gcc/doc/gccint.info-1 + 618166170b ./gcc/doc/gccint.info-10 + 3363182873b ./gcc/doc/gccint.info-11 + 301752520b ./gcc/doc/gccint.info-12 + 4149939712b ./gcc/doc/gccint.info-13 + 949510653b ./gcc/doc/gccint.info-14 + 1642518230b ./gcc/doc/gccint.info-15 + 2069563881b ./gcc/doc/gccint.info-16 + 925078439b ./gcc/doc/gccint.info-17 + 3695438277b ./gcc/doc/gccint.info-18 + 2272377258b ./gcc/doc/gccint.info-19 + 561325731b ./gcc/doc/gccint.info-2 + 3982078308b ./gcc/doc/gccint.info-20 + 3867221700b ./gcc/doc/gccint.info-21 + 3280571445b ./gcc/doc/gccint.info-22 + 2008468483b ./gcc/doc/gccint.info-23 + 797617646b ./gcc/doc/gccint.info-3 + 1305326084b ./gcc/doc/gccint.info-4 + 348735569b ./gcc/doc/gccint.info-5 + 1160338029b ./gcc/doc/gccint.info-6 + 508232037b ./gcc/doc/gccint.info-7 + 3871253182b ./gcc/doc/gccint.info-8 + 976972282b ./gcc/doc/gccint.info-9 926520134b ./gcc/doc/gccint.texi ! 1397513510b ./gcc/doc/gcov.1 2529603660b ./gcc/doc/gcov.texi ! 642118932b ./gcc/doc/gfdl.7 4217859569b ./gcc/doc/gnu.texi ! 422936980b ./gcc/doc/gpl.7 2632697239b ./gcc/doc/headerdirs.texi 1425599017b ./gcc/doc/hostconfig.texi 1232987106b ./gcc/doc/include/fdl.texi 2048065465b ./gcc/doc/include/funding.texi ! 587916905b ./gcc/doc/include/gcc-common.texi 1416455933b ./gcc/doc/include/gpl.texi 3627483023b ./gcc/doc/include/texinfo.tex 4219640220b ./gcc/doc/install-old.texi *************** *** 2822,2828 **** 409601074b ./gcc/doc/makefile.texi 647485435b ./gcc/doc/md.texi 2014418726b ./gcc/doc/objc.texi ! 3181886502b ./gcc/doc/passes.texi 2247614285b ./gcc/doc/portability.texi 2576532070b ./gcc/doc/rtl.texi 3603168219b ./gcc/doc/service.texi --- 2877,2883 ---- 409601074b ./gcc/doc/makefile.texi 647485435b ./gcc/doc/md.texi 2014418726b ./gcc/doc/objc.texi ! 1074700556b ./gcc/doc/passes.texi 2247614285b ./gcc/doc/portability.texi 2576532070b ./gcc/doc/rtl.texi 3603168219b ./gcc/doc/service.texi *************** *** 2838,2844 **** 2184520814b ./gcc/dwarf2.h 31829346b ./gcc/dwarf2asm.c 2077057275b ./gcc/dwarf2asm.h ! 3548213262b ./gcc/dwarf2out.c 1010158138b ./gcc/dwarf2out.h 3359840971b ./gcc/dwarfout.c 3336789552b ./gcc/emit-rtl.c --- 2893,2899 ---- 2184520814b ./gcc/dwarf2.h 31829346b ./gcc/dwarf2asm.c 2077057275b ./gcc/dwarf2asm.h ! 1918216770b ./gcc/dwarf2out.c 1010158138b ./gcc/dwarf2out.h 3359840971b ./gcc/dwarfout.c 3336789552b ./gcc/emit-rtl.c *************** *** 2849,2862 **** 2826708782b ./gcc/except.h 908040152b ./gcc/explow.c 1156766543b ./gcc/expmed.c ! 1153850684b ./gcc/expr.c 980675150b ./gcc/expr.h 1546791101b ./gcc/f/.cvsignore ! 3780604014b ./gcc/f/BUGS ! 557093981b ./gcc/f/ChangeLog 4225493150b ./gcc/f/ChangeLog.0 2403016299b ./gcc/f/Make-lang.in ! 4068129251b ./gcc/f/NEWS 281424983b ./gcc/f/README 3295584012b ./gcc/f/RELEASE-PREP 1934744031b ./gcc/f/ansify.c --- 2904,2917 ---- 2826708782b ./gcc/except.h 908040152b ./gcc/explow.c 1156766543b ./gcc/expmed.c ! 1064280766b ./gcc/expr.c 980675150b ./gcc/expr.h 1546791101b ./gcc/f/.cvsignore ! 2016181825b ./gcc/f/BUGS ! 2146318605b ./gcc/f/ChangeLog 4225493150b ./gcc/f/ChangeLog.0 2403016299b ./gcc/f/Make-lang.in ! 3908583628b ./gcc/f/NEWS 281424983b ./gcc/f/README 3295584012b ./gcc/f/RELEASE-PREP 1934744031b ./gcc/f/ansify.c *************** *** 2882,2888 **** 417834755b ./gcc/f/expr.h 2351117682b ./gcc/f/ffe.texi 782070966b ./gcc/f/fini.c ! 2403387907b ./gcc/f/g77.1 3054392079b ./gcc/f/g77.texi 2824974536b ./gcc/f/g77spec.c 4062822261b ./gcc/f/global.c --- 2937,2965 ---- 417834755b ./gcc/f/expr.h 2351117682b ./gcc/f/ffe.texi 782070966b ./gcc/f/fini.c ! 1751461796b ./gcc/f/g77.1 ! 3841913874b ./gcc/f/g77.info ! 2480007383b ./gcc/f/g77.info-1 ! 2368693530b ./gcc/f/g77.info-10 ! 1452968741b ./gcc/f/g77.info-11 ! 4253343420b ./gcc/f/g77.info-12 ! 1335253876b ./gcc/f/g77.info-13 ! 1460006442b ./gcc/f/g77.info-14 ! 735239497b ./gcc/f/g77.info-15 ! 4083034865b ./gcc/f/g77.info-16 ! 12335273b ./gcc/f/g77.info-17 ! 2200796034b ./gcc/f/g77.info-18 ! 671514182b ./gcc/f/g77.info-19 ! 1680815922b ./gcc/f/g77.info-2 ! 2044269147b ./gcc/f/g77.info-20 ! 863778320b ./gcc/f/g77.info-21 ! 3183619273b ./gcc/f/g77.info-3 ! 79160293b ./gcc/f/g77.info-4 ! 390737386b ./gcc/f/g77.info-5 ! 1607363995b ./gcc/f/g77.info-6 ! 2946328607b ./gcc/f/g77.info-7 ! 102401303b ./gcc/f/g77.info-8 ! 4260619545b ./gcc/f/g77.info-9 3054392079b ./gcc/f/g77.texi 2824974536b ./gcc/f/g77spec.c 4062822261b ./gcc/f/global.c *************** *** 2915,2921 **** 3453379674b ./gcc/f/news0.texi 2696377463b ./gcc/f/parse.c 1067232252b ./gcc/f/proj.h ! 2334980185b ./gcc/f/root.texi 3531682397b ./gcc/f/src.c 246620254b ./gcc/f/src.h 3466162958b ./gcc/f/st.c --- 2992,2998 ---- 3453379674b ./gcc/f/news0.texi 2696377463b ./gcc/f/parse.c 1067232252b ./gcc/f/proj.h ! 2321878455b ./gcc/f/root.texi 3531682397b ./gcc/f/src.c 246620254b ./gcc/f/src.h 3466162958b ./gcc/f/st.c *************** *** 2962,2968 **** 2232338664b ./gcc/f/top.h 3443401298b ./gcc/f/type.c 2499934202b ./gcc/f/type.h ! 1209796418b ./gcc/f/version.c 1781447679b ./gcc/f/version.h 3584291506b ./gcc/f/where.c 819940437b ./gcc/f/where.h --- 3039,3045 ---- 2232338664b ./gcc/f/top.h 3443401298b ./gcc/f/type.c 2499934202b ./gcc/f/type.h ! 1303748387b ./gcc/f/version.c 1781447679b ./gcc/f/version.h 3584291506b ./gcc/f/where.c 819940437b ./gcc/f/where.h *************** *** 2973,2979 **** 2894614091b ./gcc/fixinc/check.tpl 697597425b ./gcc/fixinc/fixfixes.c 3110054233b ./gcc/fixinc/fixinc.dgux ! 15758129b ./gcc/fixinc/fixinc.interix 1474597097b ./gcc/fixinc/fixinc.ptx 1901674452b ./gcc/fixinc/fixinc.svr4 2193207840b ./gcc/fixinc/fixinc.winnt --- 3050,3056 ---- 2894614091b ./gcc/fixinc/check.tpl 697597425b ./gcc/fixinc/fixfixes.c 3110054233b ./gcc/fixinc/fixinc.dgux ! 125459277b ./gcc/fixinc/fixinc.interix 1474597097b ./gcc/fixinc/fixinc.ptx 1901674452b ./gcc/fixinc/fixinc.svr4 2193207840b ./gcc/fixinc/fixinc.winnt *************** *** 2981,2994 **** 1824978333b ./gcc/fixinc/fixincl.c 4214658264b ./gcc/fixinc/fixincl.sh 2178021789b ./gcc/fixinc/fixincl.tpl ! 3312009046b ./gcc/fixinc/fixincl.x 1372603529b ./gcc/fixinc/fixlib.c 971233728b ./gcc/fixinc/fixlib.h 4013194329b ./gcc/fixinc/fixtests.c 2003329934b ./gcc/fixinc/genfixes 605191257b ./gcc/fixinc/gnu-regex.c 1403987073b ./gcc/fixinc/gnu-regex.h ! 2194272133b ./gcc/fixinc/inclhack.def 3327140809b ./gcc/fixinc/mkfixinc.sh 1834585069b ./gcc/fixinc/procopen.c 1750379031b ./gcc/fixinc/server.c --- 3058,3071 ---- 1824978333b ./gcc/fixinc/fixincl.c 4214658264b ./gcc/fixinc/fixincl.sh 2178021789b ./gcc/fixinc/fixincl.tpl ! 2557317697b ./gcc/fixinc/fixincl.x 1372603529b ./gcc/fixinc/fixlib.c 971233728b ./gcc/fixinc/fixlib.h 4013194329b ./gcc/fixinc/fixtests.c 2003329934b ./gcc/fixinc/genfixes 605191257b ./gcc/fixinc/gnu-regex.c 1403987073b ./gcc/fixinc/gnu-regex.h ! 3231767803b ./gcc/fixinc/inclhack.def 3327140809b ./gcc/fixinc/mkfixinc.sh 1834585069b ./gcc/fixinc/procopen.c 1750379031b ./gcc/fixinc/server.c *************** *** 3006,3015 **** --- 3083,3095 ---- 3220984809b ./gcc/fixinc/tests/base/bsd/libc.h 1799847368b ./gcc/fixinc/tests/base/c_asm.h 2725396384b ./gcc/fixinc/tests/base/ctrl-quotes-def-1.h + 192637121b ./gcc/fixinc/tests/base/ctype.h 3049981119b ./gcc/fixinc/tests/base/curses.h 2909636960b ./gcc/fixinc/tests/base/fcntl.h 3901972537b ./gcc/fixinc/tests/base/fixinc-test-limits.h 4150745363b ./gcc/fixinc/tests/base/hsfs/hsfs_spec.h + 1298358958b ./gcc/fixinc/tests/base/internal/sgimacros.h + 2484816269b ./gcc/fixinc/tests/base/internal/wchar_core.h 2118846136b ./gcc/fixinc/tests/base/inttypes.h 92918392b ./gcc/fixinc/tests/base/io-quotes-def-1.h 2670651204b ./gcc/fixinc/tests/base/libgen.h *************** *** 3019,3025 **** 2373596333b ./gcc/fixinc/tests/base/netdnet/dnetdb.h 4211518276b ./gcc/fixinc/tests/base/netinet/ip.h 3107111098b ./gcc/fixinc/tests/base/pixrect/memvar.h ! 634408265b ./gcc/fixinc/tests/base/pthread.h 351364386b ./gcc/fixinc/tests/base/reg_types.h 2876721819b ./gcc/fixinc/tests/base/regex.h 2249464053b ./gcc/fixinc/tests/base/rpc/auth.h --- 3099,3105 ---- 2373596333b ./gcc/fixinc/tests/base/netdnet/dnetdb.h 4211518276b ./gcc/fixinc/tests/base/netinet/ip.h 3107111098b ./gcc/fixinc/tests/base/pixrect/memvar.h ! 372953949b ./gcc/fixinc/tests/base/pthread.h 351364386b ./gcc/fixinc/tests/base/reg_types.h 2876721819b ./gcc/fixinc/tests/base/regex.h 2249464053b ./gcc/fixinc/tests/base/rpc/auth.h *************** *** 3031,3037 **** 135186565b ./gcc/fixinc/tests/base/sparc/asm_linkage.h 1583769396b ./gcc/fixinc/tests/base/stdio.h 1529509815b ./gcc/fixinc/tests/base/stdio_tag.h ! 135522837b ./gcc/fixinc/tests/base/stdlib.h 2907849084b ./gcc/fixinc/tests/base/strings.h 482468002b ./gcc/fixinc/tests/base/sundev/vuid_event.h 1807434691b ./gcc/fixinc/tests/base/sunwindow/win_lock.h --- 3111,3117 ---- 135186565b ./gcc/fixinc/tests/base/sparc/asm_linkage.h 1583769396b ./gcc/fixinc/tests/base/stdio.h 1529509815b ./gcc/fixinc/tests/base/stdio_tag.h ! 3122205252b ./gcc/fixinc/tests/base/stdlib.h 2907849084b ./gcc/fixinc/tests/base/strings.h 482468002b ./gcc/fixinc/tests/base/sundev/vuid_event.h 1807434691b ./gcc/fixinc/tests/base/sunwindow/win_lock.h *************** *** 3046,3053 **** 1230050207b ./gcc/fixinc/tests/base/sys/mman.h 3800154687b ./gcc/fixinc/tests/base/sys/param.h 3041640682b ./gcc/fixinc/tests/base/sys/signal.h 2450632911b ./gcc/fixinc/tests/base/sys/spinlock.h ! 711604668b ./gcc/fixinc/tests/base/sys/stat.h 2422167059b ./gcc/fixinc/tests/base/sys/time.h 2994886866b ./gcc/fixinc/tests/base/sys/times.h 1174710562b ./gcc/fixinc/tests/base/sys/types.h --- 3126,3134 ---- 1230050207b ./gcc/fixinc/tests/base/sys/mman.h 3800154687b ./gcc/fixinc/tests/base/sys/param.h 3041640682b ./gcc/fixinc/tests/base/sys/signal.h + 85483121b ./gcc/fixinc/tests/base/sys/socket.h 2450632911b ./gcc/fixinc/tests/base/sys/spinlock.h ! 2880344765b ./gcc/fixinc/tests/base/sys/stat.h 2422167059b ./gcc/fixinc/tests/base/sys/time.h 2994886866b ./gcc/fixinc/tests/base/sys/times.h 1174710562b ./gcc/fixinc/tests/base/sys/types.h *************** *** 3063,3071 **** 3658835587b ./gcc/flags.h 1465737068b ./gcc/floatlib.c 959822363b ./gcc/flow.c ! 2192581144b ./gcc/fold-const.c 3820449811b ./gcc/fp-test.c ! 2059019769b ./gcc/function.c 316231375b ./gcc/function.h 3058774034b ./gcc/future.options 1214866690b ./gcc/gbl-ctors.h --- 3144,3152 ---- 3658835587b ./gcc/flags.h 1465737068b ./gcc/floatlib.c 959822363b ./gcc/flow.c ! 3465354917b ./gcc/fold-const.c 3820449811b ./gcc/fp-test.c ! 1394029795b ./gcc/function.c 316231375b ./gcc/function.h 3058774034b ./gcc/future.options 1214866690b ./gcc/gbl-ctors.h *************** *** 3076,3082 **** 3633749318b ./gcc/gccspec.c 4197147799b ./gcc/gcov-io.h 3825112355b ./gcc/gcov.c ! 1895463511b ./gcc/gcse.c 802469235b ./gcc/gdbinit.in 4293398944b ./gcc/gen-protos.c 3638083387b ./gcc/genattr.c --- 3157,3163 ---- 3633749318b ./gcc/gccspec.c 4197147799b ./gcc/gcov-io.h 3825112355b ./gcc/gcov.c ! 1524721645b ./gcc/gcse.c 802469235b ./gcc/gdbinit.in 4293398944b ./gcc/gen-protos.c 3638083387b ./gcc/genattr.c *************** *** 3136,3149 **** 3796251430b ./gcc/hooks.c 779103435b ./gcc/hooks.h 519586985b ./gcc/hwint.h ! 3563549730b ./gcc/ifcvt.c 3686080794b ./gcc/input.h 2324132584b ./gcc/insn-addr.h 3301445102b ./gcc/integrate.c 1320722832b ./gcc/integrate.h 3277280645b ./gcc/intl.c 2379664116b ./gcc/intl.h ! 3589497609b ./gcc/intl/ChangeLog 680616337b ./gcc/intl/Makefile.in 1166279255b ./gcc/intl/VERSION 3847321727b ./gcc/intl/bindtextdom.c --- 3217,3230 ---- 3796251430b ./gcc/hooks.c 779103435b ./gcc/hooks.h 519586985b ./gcc/hwint.h ! 2453090619b ./gcc/ifcvt.c 3686080794b ./gcc/input.h 2324132584b ./gcc/insn-addr.h 3301445102b ./gcc/integrate.c 1320722832b ./gcc/integrate.h 3277280645b ./gcc/intl.c 2379664116b ./gcc/intl.h ! 1081445972b ./gcc/intl/ChangeLog 680616337b ./gcc/intl/Makefile.in 1166279255b ./gcc/intl/VERSION 3847321727b ./gcc/intl/bindtextdom.c *************** *** 3175,3181 **** 1121743739b ./gcc/intl/ref-del.sin 1971238900b ./gcc/intl/textdomain.c 503022028b ./gcc/java/.cvsignore ! 94505238b ./gcc/java/ChangeLog 3840961705b ./gcc/java/Make-lang.in 1752055498b ./gcc/java/boehm.c 3814965188b ./gcc/java/buffer.c --- 3256,3262 ---- 1121743739b ./gcc/intl/ref-del.sin 1971238900b ./gcc/intl/textdomain.c 503022028b ./gcc/java/.cvsignore ! 308773326b ./gcc/java/ChangeLog 3840961705b ./gcc/java/Make-lang.in 1752055498b ./gcc/java/boehm.c 3814965188b ./gcc/java/buffer.c *************** *** 3190,3200 **** 698834578b ./gcc/java/decl.c 1301173842b ./gcc/java/except.c 1888306202b ./gcc/java/expr.c ! 1826575023b ./gcc/java/gcj.1 ! 2122686942b ./gcc/java/gcj.texi ! 919789269b ./gcc/java/gcjh.1 533046670b ./gcc/java/gen-table.pl ! 831837047b ./gcc/java/gij.1 2862690686b ./gcc/java/gjavah.c 1545050516b ./gcc/java/java-except.h 1953641142b ./gcc/java/java-opcodes.h --- 3271,3284 ---- 698834578b ./gcc/java/decl.c 1301173842b ./gcc/java/except.c 1888306202b ./gcc/java/expr.c ! 867039953b ./gcc/java/gcj.1 ! 1220042288b ./gcc/java/gcj.info ! 580198789b ./gcc/java/gcj.info-1 ! 1591575875b ./gcc/java/gcj.info-2 ! 2232106844b ./gcc/java/gcj.texi ! 2313957134b ./gcc/java/gcjh.1 533046670b ./gcc/java/gen-table.pl ! 2558615881b ./gcc/java/gij.1 2862690686b ./gcc/java/gjavah.c 1545050516b ./gcc/java/java-except.h 1953641142b ./gcc/java/java-opcodes.h *************** *** 3203,3209 **** 2538410445b ./gcc/java/javaop.def 872575611b ./gcc/java/javaop.h 1618392854b ./gcc/java/jcf-depend.c ! 2109340318b ./gcc/java/jcf-dump.1 1347786459b ./gcc/java/jcf-dump.c 370700983b ./gcc/java/jcf-io.c 981094631b ./gcc/java/jcf-parse.c --- 3287,3293 ---- 2538410445b ./gcc/java/javaop.def 872575611b ./gcc/java/javaop.h 1618392854b ./gcc/java/jcf-depend.c ! 3138781441b ./gcc/java/jcf-dump.1 1347786459b ./gcc/java/jcf-dump.c 370700983b ./gcc/java/jcf-io.c 981094631b ./gcc/java/jcf-parse.c *************** *** 3211,3218 **** 3070824570b ./gcc/java/jcf-reader.c 3086938723b ./gcc/java/jcf-write.c 921328820b ./gcc/java/jcf.h ! 453061584b ./gcc/java/jv-convert.1 ! 622445440b ./gcc/java/jv-scan.1 3491242747b ./gcc/java/jv-scan.c 3805988298b ./gcc/java/jvgenmain.c 686969605b ./gcc/java/jvspec.c --- 3295,3302 ---- 3070824570b ./gcc/java/jcf-reader.c 3086938723b ./gcc/java/jcf-write.c 921328820b ./gcc/java/jcf.h ! 1315261195b ./gcc/java/jv-convert.1 ! 2401697144b ./gcc/java/jv-scan.1 3491242747b ./gcc/java/jv-scan.c 3805988298b ./gcc/java/jvgenmain.c 686969605b ./gcc/java/jvspec.c *************** *** 3225,3244 **** 1057768549b ./gcc/java/lex.h 1290236487b ./gcc/java/mangle.c 624686086b ./gcc/java/mangle_name.c ! 1720459878b ./gcc/java/parse-scan.c 578153036b ./gcc/java/parse-scan.y ! 3319744662b ./gcc/java/parse.c 924019294b ./gcc/java/parse.h ! 2763518333b ./gcc/java/parse.y ! 3063299109b ./gcc/java/rmic.1 ! 2868759624b ./gcc/java/rmiregistry.1 2066605666b ./gcc/java/typeck.c 173829162b ./gcc/java/verify.c 3207437983b ./gcc/java/xref.c 3070080051b ./gcc/java/xref.h 2742723736b ./gcc/java/zextract.c 1459175152b ./gcc/java/zipfile.h ! 235531345b ./gcc/jump.c 1885354315b ./gcc/langhooks-def.h 4163847594b ./gcc/langhooks.c 718654791b ./gcc/langhooks.h --- 3309,3328 ---- 1057768549b ./gcc/java/lex.h 1290236487b ./gcc/java/mangle.c 624686086b ./gcc/java/mangle_name.c ! 2212453332b ./gcc/java/parse-scan.c 578153036b ./gcc/java/parse-scan.y ! 3918875946b ./gcc/java/parse.c 924019294b ./gcc/java/parse.h ! 2160466893b ./gcc/java/parse.y ! 241511114b ./gcc/java/rmic.1 ! 3124361170b ./gcc/java/rmiregistry.1 2066605666b ./gcc/java/typeck.c 173829162b ./gcc/java/verify.c 3207437983b ./gcc/java/xref.c 3070080051b ./gcc/java/xref.h 2742723736b ./gcc/java/zextract.c 1459175152b ./gcc/java/zipfile.h ! 2200195809b ./gcc/jump.c 1885354315b ./gcc/langhooks-def.h 4163847594b ./gcc/langhooks.c 718654791b ./gcc/langhooks.h *************** *** 3280,3286 **** 3712044081b ./gcc/objc/objc-act.c 2554922770b ./gcc/objc/objc-act.h 2534517289b ./gcc/objc/objc-lang.c ! 3629705469b ./gcc/objc/objc-parse.c 1805259703b ./gcc/objc/objc-parse.y 688475759b ./gcc/objc/objc-tree.def 4077044196b ./gcc/optabs.c --- 3364,3370 ---- 3712044081b ./gcc/objc/objc-act.c 2554922770b ./gcc/objc/objc-act.h 2534517289b ./gcc/objc/objc-lang.c ! 1958451116b ./gcc/objc/objc-parse.c 1805259703b ./gcc/objc/objc-parse.y 688475759b ./gcc/objc/objc-tree.def 4077044196b ./gcc/optabs.c *************** *** 3289,3295 **** 1911824904b ./gcc/params.c 2474575794b ./gcc/params.def 840880994b ./gcc/params.h ! 2082043896b ./gcc/po/ChangeLog 4281232887b ./gcc/po/EXCLUDES 275286308b ./gcc/po/da.gmo 276047898b ./gcc/po/da.po --- 3373,3379 ---- 1911824904b ./gcc/params.c 2474575794b ./gcc/params.def 840880994b ./gcc/params.h ! 3997221312b ./gcc/po/ChangeLog 4281232887b ./gcc/po/EXCLUDES 275286308b ./gcc/po/da.gmo 276047898b ./gcc/po/da.po *************** *** 3309,3315 **** 1330626989b ./gcc/po/sv.po 866561722b ./gcc/po/tr.gmo 3345738807b ./gcc/po/tr.po ! 1839892656b ./gcc/predict.c 1371462395b ./gcc/predict.def 204342296b ./gcc/predict.h 542352850b ./gcc/prefix.c --- 3393,3399 ---- 1330626989b ./gcc/po/sv.po 866561722b ./gcc/po/tr.gmo 3345738807b ./gcc/po/tr.po ! 3161983355b ./gcc/predict.c 1371462395b ./gcc/predict.def 204342296b ./gcc/predict.h 542352850b ./gcc/prefix.c *************** *** 3319,3336 **** 2666623009b ./gcc/profile.c 1610870410b ./gcc/protoize.c 2723074973b ./gcc/read-rtl.c ! 2962281463b ./gcc/real.c 2885483337b ./gcc/real.h 1758079687b ./gcc/recog.c 2056680576b ./gcc/recog.h 3611458427b ./gcc/reg-stack.c 57810796b ./gcc/regclass.c ! 3586182830b ./gcc/regmove.c 113125100b ./gcc/regrename.c 3100477763b ./gcc/regs.h ! 55889624b ./gcc/reload.c 834085082b ./gcc/reload.h ! 664936410b ./gcc/reload1.c 4167441145b ./gcc/reorg.c 2715704724b ./gcc/resource.c 2605579460b ./gcc/resource.h --- 3403,3420 ---- 2666623009b ./gcc/profile.c 1610870410b ./gcc/protoize.c 2723074973b ./gcc/read-rtl.c ! 17316212b ./gcc/real.c 2885483337b ./gcc/real.h 1758079687b ./gcc/recog.c 2056680576b ./gcc/recog.h 3611458427b ./gcc/reg-stack.c 57810796b ./gcc/regclass.c ! 2157731750b ./gcc/regmove.c 113125100b ./gcc/regrename.c 3100477763b ./gcc/regs.h ! 3794134282b ./gcc/reload.c 834085082b ./gcc/reload.h ! 1807817122b ./gcc/reload1.c 4167441145b ./gcc/reorg.c 2715704724b ./gcc/resource.c 2605579460b ./gcc/resource.h *************** *** 3353,3359 **** 3014933100b ./gcc/sdbout.c 1391855772b ./gcc/sdbout.h 2225673670b ./gcc/sibcall.c ! 63942362b ./gcc/simplify-rtx.c 3345261950b ./gcc/sort-protos 3407562807b ./gcc/ssa-ccp.c 2078369101b ./gcc/ssa-dce.c --- 3437,3443 ---- 3014933100b ./gcc/sdbout.c 1391855772b ./gcc/sdbout.h 2225673670b ./gcc/sibcall.c ! 2715461417b ./gcc/simplify-rtx.c 3345261950b ./gcc/sort-protos 3407562807b ./gcc/ssa-ccp.c 2078369101b ./gcc/ssa-dce.c *************** *** 3361,3375 **** 332547863b ./gcc/ssa.h 2395322097b ./gcc/stab.def 471587796b ./gcc/stack.h ! 958722845b ./gcc/stmt.c 2592810543b ./gcc/stor-layout.c 3515875777b ./gcc/stringpool.c 567176141b ./gcc/sys-protos.h 482558466b ./gcc/sys-types.h ! 1242992540b ./gcc/system.h 293723253b ./gcc/target-def.h 4078089769b ./gcc/target.h ! 3879441548b ./gcc/testsuite/ChangeLog 986418331b ./gcc/testsuite/README 4258789052b ./gcc/testsuite/README.g++ 174183124b ./gcc/testsuite/README.gcc --- 3445,3459 ---- 332547863b ./gcc/ssa.h 2395322097b ./gcc/stab.def 471587796b ./gcc/stack.h ! 114049826b ./gcc/stmt.c 2592810543b ./gcc/stor-layout.c 3515875777b ./gcc/stringpool.c 567176141b ./gcc/sys-protos.h 482558466b ./gcc/sys-types.h ! 524381800b ./gcc/system.h 293723253b ./gcc/target-def.h 4078089769b ./gcc/target.h ! 2721909951b ./gcc/testsuite/ChangeLog 986418331b ./gcc/testsuite/README 4258789052b ./gcc/testsuite/README.g++ 174183124b ./gcc/testsuite/README.gcc *************** *** 5101,5106 **** --- 5185,5191 ---- 3028501104b ./gcc/testsuite/g++.dg/ext/typeof1.C 2139267109b ./gcc/testsuite/g++.dg/ext/typeof2.C 4011489903b ./gcc/testsuite/g++.dg/ext/typeof3.C + 3374727940b ./gcc/testsuite/g++.dg/ext/typeof4.C 3384117993b ./gcc/testsuite/g++.dg/ext/vla1.C 4261072225b ./gcc/testsuite/g++.dg/ext/vlm1.C 546216042b ./gcc/testsuite/g++.dg/ext/vlm2.C *************** *** 5157,5162 **** --- 5242,5249 ---- 1496969096b ./gcc/testsuite/g++.dg/opt/ptrintsum1.C 571185401b ./gcc/testsuite/g++.dg/opt/reg-stack.C 1557651694b ./gcc/testsuite/g++.dg/opt/reload1.C + 2822399311b ./gcc/testsuite/g++.dg/opt/reload2.C + 2874679179b ./gcc/testsuite/g++.dg/opt/rtti1.C 1124740865b ./gcc/testsuite/g++.dg/opt/static1.C 684782459b ./gcc/testsuite/g++.dg/opt/static2.C 4154721541b ./gcc/testsuite/g++.dg/opt/thunk1.C *************** *** 5186,5192 **** 2096815409b ./gcc/testsuite/g++.dg/other/init1.C 2028368016b ./gcc/testsuite/g++.dg/other/init2.C 2143945221b ./gcc/testsuite/g++.dg/other/linkage1.C ! 2384288796b ./gcc/testsuite/g++.dg/other/pragma-ep-1.C 198088036b ./gcc/testsuite/g++.dg/other/pragma-re-1.C 1453288357b ./gcc/testsuite/g++.dg/other/ptrmem1.C 392352692b ./gcc/testsuite/g++.dg/other/ptrmem2.C --- 5273,5279 ---- 2096815409b ./gcc/testsuite/g++.dg/other/init1.C 2028368016b ./gcc/testsuite/g++.dg/other/init2.C 2143945221b ./gcc/testsuite/g++.dg/other/linkage1.C ! 1073045139b ./gcc/testsuite/g++.dg/other/pragma-ep-1.C 198088036b ./gcc/testsuite/g++.dg/other/pragma-re-1.C 1453288357b ./gcc/testsuite/g++.dg/other/ptrmem1.C 392352692b ./gcc/testsuite/g++.dg/other/ptrmem2.C *************** *** 5231,5236 **** --- 5318,5324 ---- 184359799b ./gcc/testsuite/g++.dg/template/dtor1.C 1161800603b ./gcc/testsuite/g++.dg/template/explicit-instantiation.C 3595433718b ./gcc/testsuite/g++.dg/template/friend.C + 2661209683b ./gcc/testsuite/g++.dg/template/friend16.C 3302501697b ./gcc/testsuite/g++.dg/template/friend3.C 587931705b ./gcc/testsuite/g++.dg/template/friend4.C 3560434139b ./gcc/testsuite/g++.dg/template/friend5.C *************** *** 5272,5277 **** --- 5360,5367 ---- 1028564434b ./gcc/testsuite/g++.dg/template/sizeof1.C 2914549620b ./gcc/testsuite/g++.dg/template/spec1.C 2378483146b ./gcc/testsuite/g++.dg/template/spec2.C + 177374413b ./gcc/testsuite/g++.dg/template/spec7.C + 3516934395b ./gcc/testsuite/g++.dg/template/spec8.C 3770294113b ./gcc/testsuite/g++.dg/template/static1.C 2876903140b ./gcc/testsuite/g++.dg/template/static2.C 1689207326b ./gcc/testsuite/g++.dg/template/strlen1.C *************** *** 5300,5305 **** --- 5390,5396 ---- 1455133800b ./gcc/testsuite/g++.dg/warn/format1.C 886747822b ./gcc/testsuite/g++.dg/warn/format2.C 2805519034b ./gcc/testsuite/g++.dg/warn/friend.C + 334159724b ./gcc/testsuite/g++.dg/warn/implicit-typename1.C 3402610409b ./gcc/testsuite/g++.dg/warn/oldcast1.C 2394314287b ./gcc/testsuite/g++.dg/warn/return-reference.C 3714230484b ./gcc/testsuite/g++.dg/warn/weak1.C *************** *** 7112,7118 **** 3099602163b ./gcc/testsuite/g++.old-deja/g++.ns/using7.C 396388537b ./gcc/testsuite/g++.old-deja/g++.ns/using8.C 536814910b ./gcc/testsuite/g++.old-deja/g++.ns/using9.C ! 3652230393b ./gcc/testsuite/g++.old-deja/g++.oliva/ChangeLog 3728265872b ./gcc/testsuite/g++.old-deja/g++.oliva/ctor1.C 3026414575b ./gcc/testsuite/g++.old-deja/g++.oliva/delete1.C 3639944207b ./gcc/testsuite/g++.old-deja/g++.oliva/delete2.C --- 7203,7209 ---- 3099602163b ./gcc/testsuite/g++.old-deja/g++.ns/using7.C 396388537b ./gcc/testsuite/g++.old-deja/g++.ns/using8.C 536814910b ./gcc/testsuite/g++.old-deja/g++.ns/using9.C ! 624680462b ./gcc/testsuite/g++.old-deja/g++.oliva/ChangeLog 3728265872b ./gcc/testsuite/g++.old-deja/g++.oliva/ctor1.C 3026414575b ./gcc/testsuite/g++.old-deja/g++.oliva/delete1.C 3639944207b ./gcc/testsuite/g++.old-deja/g++.oliva/delete2.C *************** *** 8915,8920 **** --- 9006,9015 ---- 953842788b ./gcc/testsuite/gcc.c-torture/compile/20021205-1.c 3765901682b ./gcc/testsuite/gcc.c-torture/compile/20021212-1.c 1694594576b ./gcc/testsuite/gcc.c-torture/compile/20030110-1.c + 3514558242b ./gcc/testsuite/gcc.c-torture/compile/20030206-1.c + 2261613922b ./gcc/testsuite/gcc.c-torture/compile/20030220-1.c + 3214532330b ./gcc/testsuite/gcc.c-torture/compile/20030305-1.c + 3074411947b ./gcc/testsuite/gcc.c-torture/compile/20030314-1.c 375311401b ./gcc/testsuite/gcc.c-torture/compile/900116-1.c 4181931788b ./gcc/testsuite/gcc.c-torture/compile/900216-1.c 426860692b ./gcc/testsuite/gcc.c-torture/compile/900313-1.c *************** *** 9366,9374 **** 1360698555b ./gcc/testsuite/gcc.c-torture/execute/20020219-1.c 1656358954b ./gcc/testsuite/gcc.c-torture/execute/20020225-1.c 127051635b ./gcc/testsuite/gcc.c-torture/execute/20020227-1.c ! 2757105756b ./gcc/testsuite/gcc.c-torture/execute/20020227-1.x 1982547595b ./gcc/testsuite/gcc.c-torture/execute/20020307-1.c 1497258578b ./gcc/testsuite/gcc.c-torture/execute/20020307-2.c 2236973257b ./gcc/testsuite/gcc.c-torture/execute/20020314-1.c 3091941732b ./gcc/testsuite/gcc.c-torture/execute/20020320-1.c 3564527352b ./gcc/testsuite/gcc.c-torture/execute/20020321-1.c --- 9461,9470 ---- 1360698555b ./gcc/testsuite/gcc.c-torture/execute/20020219-1.c 1656358954b ./gcc/testsuite/gcc.c-torture/execute/20020225-1.c 127051635b ./gcc/testsuite/gcc.c-torture/execute/20020227-1.c ! 2965337212b ./gcc/testsuite/gcc.c-torture/execute/20020227-1.x 1982547595b ./gcc/testsuite/gcc.c-torture/execute/20020307-1.c 1497258578b ./gcc/testsuite/gcc.c-torture/execute/20020307-2.c + 3970771348b ./gcc/testsuite/gcc.c-torture/execute/20020307-2.x 2236973257b ./gcc/testsuite/gcc.c-torture/execute/20020314-1.c 3091941732b ./gcc/testsuite/gcc.c-torture/execute/20020320-1.c 3564527352b ./gcc/testsuite/gcc.c-torture/execute/20020321-1.c *************** *** 9396,9401 **** --- 9492,9502 ---- 3834877290b ./gcc/testsuite/gcc.c-torture/execute/20021118-3.c 624734562b ./gcc/testsuite/gcc.c-torture/execute/20021219-1.c 2820909676b ./gcc/testsuite/gcc.c-torture/execute/20030109-1.c + 855486154b ./gcc/testsuite/gcc.c-torture/execute/20030221-1.c + 821090783b ./gcc/testsuite/gcc.c-torture/execute/20030224-2.c + 4076291177b ./gcc/testsuite/gcc.c-torture/execute/20030307-1.c + 2371585447b ./gcc/testsuite/gcc.c-torture/execute/20030313-1.c + 2637074483b ./gcc/testsuite/gcc.c-torture/execute/20030316-1.c 37158978b ./gcc/testsuite/gcc.c-torture/execute/900409-1.c 1241514475b ./gcc/testsuite/gcc.c-torture/execute/920202-1.c 651529975b ./gcc/testsuite/gcc.c-torture/execute/920302-1.c *************** *** 9829,9835 **** 1827676873b ./gcc/testsuite/gcc.c-torture/execute/scope-1.c 990025742b ./gcc/testsuite/gcc.c-torture/execute/scope-2.c 3788353048b ./gcc/testsuite/gcc.c-torture/execute/shiftdi.c ! 75800580b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-1.c 2726881848b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-2.c 2215607685b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-3.c 4127514660b ./gcc/testsuite/gcc.c-torture/execute/strct-pack-1.c --- 9930,9936 ---- 1827676873b ./gcc/testsuite/gcc.c-torture/execute/scope-1.c 990025742b ./gcc/testsuite/gcc.c-torture/execute/scope-2.c 3788353048b ./gcc/testsuite/gcc.c-torture/execute/shiftdi.c ! 1004975218b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-1.c 2726881848b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-2.c 2215607685b ./gcc/testsuite/gcc.c-torture/execute/stdio-opt-3.c 4127514660b ./gcc/testsuite/gcc.c-torture/execute/strct-pack-1.c *************** *** 10258,10271 **** 1527728757b ./gcc/testsuite/gcc.dg/20020418-2.c 2088656022b ./gcc/testsuite/gcc.dg/20020426-1.c 4234050901b ./gcc/testsuite/gcc.dg/20020426-2.c ! 464722125b ./gcc/testsuite/gcc.dg/20020430-1.c ! 1745642748b ./gcc/testsuite/gcc.dg/20020503-1.c 3667555097b ./gcc/testsuite/gcc.dg/20020517-1.c 536325431b ./gcc/testsuite/gcc.dg/20020523-1.c 1463174796b ./gcc/testsuite/gcc.dg/20020527-1.c 2086765142b ./gcc/testsuite/gcc.dg/20020530-1.c 1518490714b ./gcc/testsuite/gcc.dg/20020616-1.c 344810811b ./gcc/testsuite/gcc.dg/20021014-1.c 1577979025b ./gcc/testsuite/gcc.dg/920413-1.c 2176221389b ./gcc/testsuite/gcc.dg/940409-1.c 1567764883b ./gcc/testsuite/gcc.dg/940510-1.c --- 10359,10377 ---- 1527728757b ./gcc/testsuite/gcc.dg/20020418-2.c 2088656022b ./gcc/testsuite/gcc.dg/20020426-1.c 4234050901b ./gcc/testsuite/gcc.dg/20020426-2.c ! 3359725112b ./gcc/testsuite/gcc.dg/20020430-1.c ! 2963915296b ./gcc/testsuite/gcc.dg/20020503-1.c 3667555097b ./gcc/testsuite/gcc.dg/20020517-1.c 536325431b ./gcc/testsuite/gcc.dg/20020523-1.c 1463174796b ./gcc/testsuite/gcc.dg/20020527-1.c 2086765142b ./gcc/testsuite/gcc.dg/20020530-1.c 1518490714b ./gcc/testsuite/gcc.dg/20020616-1.c 344810811b ./gcc/testsuite/gcc.dg/20021014-1.c + 2919267b ./gcc/testsuite/gcc.dg/20030217-1.c + 1045670620b ./gcc/testsuite/gcc.dg/20030225-1.c + 11242163b ./gcc/testsuite/gcc.dg/20030309-1.c + 3937697137b ./gcc/testsuite/gcc.dg/20030323-1.c + 1058638767b ./gcc/testsuite/gcc.dg/20030414-1.c 1577979025b ./gcc/testsuite/gcc.dg/920413-1.c 2176221389b ./gcc/testsuite/gcc.dg/940409-1.c 1567764883b ./gcc/testsuite/gcc.dg/940510-1.c *************** *** 10324,10329 **** --- 10430,10436 ---- 2673255882b ./gcc/testsuite/gcc.dg/asm-5.c 2560291160b ./gcc/testsuite/gcc.dg/asm-fs-1.c 1287172903b ./gcc/testsuite/gcc.dg/asm-names.c + 1099611642b ./gcc/testsuite/gcc.dg/asmreg-1.c 2801105283b ./gcc/testsuite/gcc.dg/attr-alwaysinline.c 1514674985b ./gcc/testsuite/gcc.dg/attr-invalid.c 1915283314b ./gcc/testsuite/gcc.dg/attr-nest.c *************** *** 10652,10657 **** --- 10759,10766 ---- 3551380716b ./gcc/testsuite/gcc.dg/debug/dwarf2-2.c 1865154101b ./gcc/testsuite/gcc.dg/debug/trivial.c 2108424497b ./gcc/testsuite/gcc.dg/decl-1.c + 3489735771b ./gcc/testsuite/gcc.dg/decl-2.c + 219343109b ./gcc/testsuite/gcc.dg/decl-3.c 2106699188b ./gcc/testsuite/gcc.dg/deprecated.c 462220244b ./gcc/testsuite/gcc.dg/dg.exp 3005671194b ./gcc/testsuite/gcc.dg/divbyzero.c *************** *** 10724,10731 **** --- 10833,10845 ---- 885923224b ./gcc/testsuite/gcc.dg/i386-387-1.c 4204057333b ./gcc/testsuite/gcc.dg/i386-387-2.c 3371905361b ./gcc/testsuite/gcc.dg/i386-bitfield1.c + 3703039330b ./gcc/testsuite/gcc.dg/i386-loop-1.c + 2666972329b ./gcc/testsuite/gcc.dg/i386-loop-2.c 2049230625b ./gcc/testsuite/gcc.dg/i386-mmx-1.c 3973906625b ./gcc/testsuite/gcc.dg/i386-mmx-2.c + 811535520b ./gcc/testsuite/gcc.dg/i386-signbit-1.c + 1624192171b ./gcc/testsuite/gcc.dg/i386-signbit-2.c + 1578707081b ./gcc/testsuite/gcc.dg/i386-signbit-3.c 2923520039b ./gcc/testsuite/gcc.dg/i386-sse-1.c 1935024742b ./gcc/testsuite/gcc.dg/i386-sse-2.c 2407665653b ./gcc/testsuite/gcc.dg/i386-sse-3.c *************** *** 10785,10797 **** 2267400179b ./gcc/testsuite/gcc.dg/noreturn-2.c 1222476594b ./gcc/testsuite/gcc.dg/noreturn-3.c 4260549149b ./gcc/testsuite/gcc.dg/noreturn-4.c ! 1941766090b ./gcc/testsuite/gcc.dg/old-style-asm-1.c 1662299957b ./gcc/testsuite/gcc.dg/pack-test-1.c 2754082325b ./gcc/testsuite/gcc.dg/pack-test-1.h 2875409621b ./gcc/testsuite/gcc.dg/pack-test-2.c 3395691298b ./gcc/testsuite/gcc.dg/pragma-align.c 2976918557b ./gcc/testsuite/gcc.dg/pragma-darwin.c ! 967979463b ./gcc/testsuite/gcc.dg/pragma-ep-1.c 689657683b ./gcc/testsuite/gcc.dg/pragma-ep-2.c 375277958b ./gcc/testsuite/gcc.dg/pragma-ep-3.c 18511022b ./gcc/testsuite/gcc.dg/pragma-re-1.c --- 10899,10911 ---- 2267400179b ./gcc/testsuite/gcc.dg/noreturn-2.c 1222476594b ./gcc/testsuite/gcc.dg/noreturn-3.c 4260549149b ./gcc/testsuite/gcc.dg/noreturn-4.c ! 3873251871b ./gcc/testsuite/gcc.dg/old-style-asm-1.c 1662299957b ./gcc/testsuite/gcc.dg/pack-test-1.c 2754082325b ./gcc/testsuite/gcc.dg/pack-test-1.h 2875409621b ./gcc/testsuite/gcc.dg/pack-test-2.c 3395691298b ./gcc/testsuite/gcc.dg/pragma-align.c 2976918557b ./gcc/testsuite/gcc.dg/pragma-darwin.c ! 2313186581b ./gcc/testsuite/gcc.dg/pragma-ep-1.c 689657683b ./gcc/testsuite/gcc.dg/pragma-ep-2.c 375277958b ./gcc/testsuite/gcc.dg/pragma-ep-3.c 18511022b ./gcc/testsuite/gcc.dg/pragma-re-1.c *************** *** 10802,10807 **** --- 10916,10922 ---- 3519355790b ./gcc/testsuite/gcc.dg/return-type-2.c 3862146754b ./gcc/testsuite/gcc.dg/sequence-pt-1.c 3997091992b ./gcc/testsuite/gcc.dg/setjmp-1.c + 2828537866b ./gcc/testsuite/gcc.dg/sparc-dwarf2.c 802040009b ./gcc/testsuite/gcc.dg/sparc-ret.c 1993113484b ./gcc/testsuite/gcc.dg/special/20000419-2.c 3430419731b ./gcc/testsuite/gcc.dg/special/alias-1.c *************** *** 10833,10838 **** --- 10948,10956 ---- 789972216b ./gcc/testsuite/gcc.dg/ultrasp2.c 2708772692b ./gcc/testsuite/gcc.dg/ultrasp3.c 1890424464b ./gcc/testsuite/gcc.dg/ultrasp4.c + 783369369b ./gcc/testsuite/gcc.dg/ultrasp6.c + 2907651471b ./gcc/testsuite/gcc.dg/ultrasp7.c + 906694114b ./gcc/testsuite/gcc.dg/ultrasp8.c 2258658308b ./gcc/testsuite/gcc.dg/uninit-1.c 608086310b ./gcc/testsuite/gcc.dg/uninit-2.c 2219873069b ./gcc/testsuite/gcc.dg/uninit-3.c *************** *** 10959,10966 **** 2495249432b ./gcc/testsuite/objc.dg/local-decl-1.m 1667427564b ./gcc/testsuite/objc.dg/method-1.m 2835356210b ./gcc/testsuite/objc.dg/method-2.m ! 1830729571b ./gcc/testsuite/objc.dg/naming-1.m ! 250748297b ./gcc/testsuite/objc.dg/naming-2.m 2785734223b ./gcc/testsuite/objc.dg/proto-hier-1.m 888349193b ./gcc/testsuite/objc.dg/special/special.exp 3078900770b ./gcc/testsuite/objc.dg/special/unclaimed-category-1.h --- 11077,11084 ---- 2495249432b ./gcc/testsuite/objc.dg/local-decl-1.m 1667427564b ./gcc/testsuite/objc.dg/method-1.m 2835356210b ./gcc/testsuite/objc.dg/method-2.m ! 4046194509b ./gcc/testsuite/objc.dg/naming-1.m ! 3719205740b ./gcc/testsuite/objc.dg/naming-2.m 2785734223b ./gcc/testsuite/objc.dg/proto-hier-1.m 888349193b ./gcc/testsuite/objc.dg/special/special.exp 3078900770b ./gcc/testsuite/objc.dg/special/unclaimed-category-1.h *************** *** 11059,11080 **** 2559007517b ./gcc/timevar.def 2115869626b ./gcc/timevar.h 2335446483b ./gcc/tlink.c ! 163649448b ./gcc/toplev.c 1100253771b ./gcc/toplev.h ! 4006547771b ./gcc/tradcif.c 840149782b ./gcc/tradcif.y 325171845b ./gcc/tradcpp.c 133942480b ./gcc/tradcpp.h 1565760610b ./gcc/tree-dump.c 177026127b ./gcc/tree-dump.h ! 1491742054b ./gcc/tree-inline.c 2000795530b ./gcc/tree-inline.h ! 2992843029b ./gcc/tree.c 2149556796b ./gcc/tree.def 1200175084b ./gcc/tree.h 2106315745b ./gcc/tsystem.h 4139263293b ./gcc/typeclass.h ! 2642343552b ./gcc/unroll.c 2451297709b ./gcc/unwind-dw2-fde-glibc.c 939184029b ./gcc/unwind-dw2-fde.c 2681777274b ./gcc/unwind-dw2-fde.h --- 11177,11198 ---- 2559007517b ./gcc/timevar.def 2115869626b ./gcc/timevar.h 2335446483b ./gcc/tlink.c ! 1633125668b ./gcc/toplev.c 1100253771b ./gcc/toplev.h ! 2279698662b ./gcc/tradcif.c 840149782b ./gcc/tradcif.y 325171845b ./gcc/tradcpp.c 133942480b ./gcc/tradcpp.h 1565760610b ./gcc/tree-dump.c 177026127b ./gcc/tree-dump.h ! 4108002902b ./gcc/tree-inline.c 2000795530b ./gcc/tree-inline.h ! 1782878008b ./gcc/tree.c 2149556796b ./gcc/tree.def 1200175084b ./gcc/tree.h 2106315745b ./gcc/tsystem.h 4139263293b ./gcc/typeclass.h ! 1488638700b ./gcc/unroll.c 2451297709b ./gcc/unwind-dw2-fde-glibc.c 939184029b ./gcc/unwind-dw2-fde.c 2681777274b ./gcc/unwind-dw2-fde.h *************** *** 11086,11100 **** 1202449654b ./gcc/varasm.c 1377429075b ./gcc/varray.c 251576980b ./gcc/varray.h ! 2865840547b ./gcc/version.c 835289284b ./gcc/version.h 1602668013b ./gcc/vmsdbg.h 4159431942b ./gcc/vmsdbgout.c 3414725237b ./gcc/xcoffout.c 241048359b ./gcc/xcoffout.h ! 3804835603b ./gnats.html 2171125041b ./include/COPYING ! 1284755488b ./include/ChangeLog 218913669b ./include/ansidecl.h 3472518673b ./include/demangle.h 524172850b ./include/dyn-string.h --- 11204,11218 ---- 1202449654b ./gcc/varasm.c 1377429075b ./gcc/varray.c 251576980b ./gcc/varray.h ! 309143238b ./gcc/version.c 835289284b ./gcc/version.h 1602668013b ./gcc/vmsdbg.h 4159431942b ./gcc/vmsdbgout.c 3414725237b ./gcc/xcoffout.c 241048359b ./gcc/xcoffout.h ! 1616768675b ./gnats.html 2171125041b ./include/COPYING ! 595770831b ./include/ChangeLog 218913669b ./include/ansidecl.h 3472518673b ./include/demangle.h 524172850b ./include/dyn-string.h *************** *** 11116,11122 **** 1151436348b ./include/xregex.h 1261882580b ./include/xregex2.h 656627656b ./install-sh ! 2543423086b ./libf2c/ChangeLog 643704007b ./libf2c/Makefile.in 3111321221b ./libf2c/README 308226469b ./libf2c/TODO --- 11234,11240 ---- 1151436348b ./include/xregex.h 1261882580b ./include/xregex2.h 656627656b ./install-sh ! 884630057b ./libf2c/ChangeLog 643704007b ./libf2c/Makefile.in 3111321221b ./libf2c/README 308226469b ./libf2c/TODO *************** *** 11132,11138 **** 2048561220b ./libf2c/libF77/Makefile.in 1384146782b ./libf2c/libF77/Notice 3594711912b ./libf2c/libF77/README.netlib ! 3333503347b ./libf2c/libF77/Version.c 1304659322b ./libf2c/libF77/abort_.c 2143735092b ./libf2c/libF77/c_abs.c 4102372920b ./libf2c/libF77/c_cos.c --- 11250,11256 ---- 2048561220b ./libf2c/libF77/Makefile.in 1384146782b ./libf2c/libF77/Notice 3594711912b ./libf2c/libF77/README.netlib ! 705291937b ./libf2c/libF77/Version.c 1304659322b ./libf2c/libF77/abort_.c 2143735092b ./libf2c/libF77/c_abs.c 4102372920b ./libf2c/libF77/c_cos.c *************** *** 11264,11270 **** 81211418b ./libf2c/libI77/Makefile.in 1384146782b ./libf2c/libI77/Notice 3744878144b ./libf2c/libI77/README.netlib ! 1068556264b ./libf2c/libI77/Version.c 1606913831b ./libf2c/libI77/backspace.c 2398093876b ./libf2c/libI77/close.c 3442307107b ./libf2c/libI77/config.h.in --- 11382,11388 ---- 81211418b ./libf2c/libI77/Makefile.in 1384146782b ./libf2c/libI77/Notice 3744878144b ./libf2c/libI77/README.netlib ! 199281018b ./libf2c/libI77/Version.c 1606913831b ./libf2c/libI77/backspace.c 2398093876b ./libf2c/libI77/close.c 3442307107b ./libf2c/libI77/config.h.in *************** *** 11311,11317 **** 2717291481b ./libf2c/libU77/Makefile.in 572996563b ./libf2c/libU77/PROJECTS 2980229902b ./libf2c/libU77/README ! 3875363173b ./libf2c/libU77/Version.c 1842933802b ./libf2c/libU77/access_.c 4214861580b ./libf2c/libU77/acconfig.h 2301261828b ./libf2c/libU77/aclocal.m4 --- 11429,11435 ---- 2717291481b ./libf2c/libU77/Makefile.in 572996563b ./libf2c/libU77/PROJECTS 2980229902b ./libf2c/libU77/README ! 1494896292b ./libf2c/libU77/Version.c 1842933802b ./libf2c/libU77/access_.c 4214861580b ./libf2c/libU77/acconfig.h 2301261828b ./libf2c/libU77/aclocal.m4 *************** *** 11373,11379 **** 3987376609b ./libf2c/libU77/vxttime_.c 1384146782b ./libf2c/permission.netlib 3513813969b ./libf2c/readme.netlib ! 3047576515b ./libffi/ChangeLog 3479323424b ./libffi/ChangeLog.libgcj 1481682558b ./libffi/ChangeLog.v1 2593181117b ./libffi/LICENSE --- 11491,11497 ---- 3987376609b ./libf2c/libU77/vxttime_.c 1384146782b ./libf2c/permission.netlib 3513813969b ./libf2c/readme.netlib ! 829387645b ./libffi/ChangeLog 3479323424b ./libffi/ChangeLog.libgcj 1481682558b ./libffi/ChangeLog.v1 2593181117b ./libffi/LICENSE *************** *** 11396,11402 **** 4293371769b ./libffi/src/arm/ffi.c 591152992b ./libffi/src/arm/sysv.S 2669027491b ./libffi/src/debug.c ! 269618381b ./libffi/src/ffitest.c 2435449601b ./libffi/src/ia64/ffi.c 1956966073b ./libffi/src/ia64/ia64_flags.h 2886414800b ./libffi/src/ia64/unix.S --- 11514,11520 ---- 4293371769b ./libffi/src/arm/ffi.c 591152992b ./libffi/src/arm/sysv.S 2669027491b ./libffi/src/debug.c ! 967989305b ./libffi/src/ffitest.c 2435449601b ./libffi/src/ia64/ffi.c 1956966073b ./libffi/src/ia64/ia64_flags.h 2886414800b ./libffi/src/ia64/unix.S *************** *** 11407,11418 **** 176940890b ./libffi/src/mips/n32.S 3634355650b ./libffi/src/mips/o32.S 1342850260b ./libffi/src/powerpc/aix.S ! 2356375417b ./libffi/src/powerpc/aix_closure.S 257105690b ./libffi/src/powerpc/asm.h 91989017b ./libffi/src/powerpc/darwin.S ! 1992059182b ./libffi/src/powerpc/darwin_closure.S ! 1107349205b ./libffi/src/powerpc/ffi.c ! 342545621b ./libffi/src/powerpc/ffi_darwin.c 978519837b ./libffi/src/powerpc/ppc_closure.S 1185461672b ./libffi/src/powerpc/sysv.S 1962807490b ./libffi/src/prep_cif.c --- 11525,11536 ---- 176940890b ./libffi/src/mips/n32.S 3634355650b ./libffi/src/mips/o32.S 1342850260b ./libffi/src/powerpc/aix.S ! 1122125803b ./libffi/src/powerpc/aix_closure.S 257105690b ./libffi/src/powerpc/asm.h 91989017b ./libffi/src/powerpc/darwin.S ! 4044999467b ./libffi/src/powerpc/darwin_closure.S ! 1692071312b ./libffi/src/powerpc/ffi.c ! 2961975388b ./libffi/src/powerpc/ffi_darwin.c 978519837b ./libffi/src/powerpc/ppc_closure.S 1185461672b ./libffi/src/powerpc/sysv.S 1962807490b ./libffi/src/prep_cif.c *************** *** 11426,11435 **** 478025840b ./libffi/src/x86/win32.S 216805921b ./libffi/stamp-h.in 508743035b ./libiberty/COPYING.LIB ! 3946655929b ./libiberty/ChangeLog 1980229302b ./libiberty/Makefile.in 4016047250b ./libiberty/README 602306638b ./libiberty/_doprnt.c 640604299b ./libiberty/aclocal.m4 4169173798b ./libiberty/alloca.c 122203256b ./libiberty/argv.c --- 11544,11554 ---- 478025840b ./libffi/src/x86/win32.S 216805921b ./libffi/stamp-h.in 508743035b ./libiberty/COPYING.LIB ! 2977486001b ./libiberty/ChangeLog 1980229302b ./libiberty/Makefile.in 4016047250b ./libiberty/README 602306638b ./libiberty/_doprnt.c + 3848560079b ./libiberty/acconfig.h 640604299b ./libiberty/aclocal.m4 4169173798b ./libiberty/alloca.c 122203256b ./libiberty/argv.c *************** *** 11445,11459 **** 2557767520b ./libiberty/clock.c 3170582338b ./libiberty/concat.c 1987387424b ./libiberty/config.h-vms ! 2319815417b ./libiberty/config.in 4294237366b ./libiberty/config.table 3500529335b ./libiberty/config/mh-aix 3476234501b ./libiberty/config/mh-cxux7 1235651640b ./libiberty/config/mh-fbsd21 2904567379b ./libiberty/config/mh-openedition 2131807358b ./libiberty/config/mh-windows ! 3945236769b ./libiberty/configure ! 1116624814b ./libiberty/configure.in 2478885430b ./libiberty/copying-lib.texi 3329761531b ./libiberty/copysign.c 2979121734b ./libiberty/cp-demangle.c --- 11564,11578 ---- 2557767520b ./libiberty/clock.c 3170582338b ./libiberty/concat.c 1987387424b ./libiberty/config.h-vms ! 257229344b ./libiberty/config.in 4294237366b ./libiberty/config.table 3500529335b ./libiberty/config/mh-aix 3476234501b ./libiberty/config/mh-cxux7 1235651640b ./libiberty/config/mh-fbsd21 2904567379b ./libiberty/config/mh-openedition 2131807358b ./libiberty/config/mh-windows ! 575752138b ./libiberty/configure ! 1313961034b ./libiberty/configure.in 2478885430b ./libiberty/copying-lib.texi 3329761531b ./libiberty/copysign.c 2979121734b ./libiberty/cp-demangle.c *************** *** 11540,11546 **** 991611298b ./libiberty/xstrdup.c 387398324b ./libiberty/xstrerror.c 2171125041b ./libjava/COPYING ! 600502670b ./libjava/ChangeLog 3473562392b ./libjava/ChangeLog-1999 2385951174b ./libjava/ChangeLog-2001 1487334009b ./libjava/HACKING --- 11659,11665 ---- 991611298b ./libiberty/xstrdup.c 387398324b ./libiberty/xstrerror.c 2171125041b ./libjava/COPYING ! 520335338b ./libjava/ChangeLog 3473562392b ./libjava/ChangeLog-1999 2385951174b ./libjava/ChangeLog-2001 1487334009b ./libjava/HACKING *************** *** 12874,12880 **** 799924566b ./libjava/libgcj.spec.in 3885054737b ./libjava/libltdl/.cvsignore 1530919786b ./libjava/libltdl/COPYING.LIB ! 3714466252b ./libjava/libltdl/ChangeLog 3589765398b ./libjava/libltdl/Makefile.am 2495909158b ./libjava/libltdl/Makefile.in 1322928877b ./libjava/libltdl/README --- 12993,12999 ---- 799924566b ./libjava/libgcj.spec.in 3885054737b ./libjava/libltdl/.cvsignore 1530919786b ./libjava/libltdl/COPYING.LIB ! 3841120685b ./libjava/libltdl/ChangeLog 3589765398b ./libjava/libltdl/Makefile.am 2495909158b ./libjava/libltdl/Makefile.in 1322928877b ./libjava/libltdl/README *************** *** 12968,12974 **** 2487590179b ./libjava/sysdep/ia64/locks.h 3446737173b ./libjava/sysdep/powerpc/locks.h 2903495760b ./libjava/sysdep/sparc/locks.h ! 2964965917b ./libjava/testsuite/ChangeLog 3806425466b ./libjava/testsuite/Makefile.am 1096421437b ./libjava/testsuite/Makefile.in 1230501773b ./libjava/testsuite/config/default.exp --- 13087,13093 ---- 2487590179b ./libjava/sysdep/ia64/locks.h 3446737173b ./libjava/sysdep/powerpc/locks.h 2903495760b ./libjava/sysdep/sparc/locks.h ! 4288525704b ./libjava/testsuite/ChangeLog 3806425466b ./libjava/testsuite/Makefile.am 1096421437b ./libjava/testsuite/Makefile.in 1230501773b ./libjava/testsuite/config/default.exp *************** *** 13387,13393 **** 3417667916b ./libjava/verify.cc 3459150705b ./libjava/win32-threads.cc 916359044b ./libjava/win32.cc ! 1019359508b ./libobjc/ChangeLog 3778683951b ./libobjc/Makefile.in 638422313b ./libobjc/NXConstStr.m 3285287551b ./libobjc/Object.m --- 13506,13512 ---- 3417667916b ./libjava/verify.cc 3459150705b ./libjava/win32-threads.cc 916359044b ./libjava/win32.cc ! 3049078639b ./libobjc/ChangeLog 3778683951b ./libobjc/Makefile.in 638422313b ./libobjc/NXConstStr.m 3285287551b ./libobjc/Object.m *************** *** 13442,13448 **** 2005277748b ./libobjc/thr-vxworks.c 2963027857b ./libobjc/thr-win32.c 3239202263b ./libobjc/thr.c ! 8463637b ./libstdc++-v3/ChangeLog 1996982572b ./libstdc++-v3/ChangeLog-2000 3665233589b ./libstdc++-v3/ChangeLog-2001 3601994870b ./libstdc++-v3/Makefile.am --- 13561,13567 ---- 2005277748b ./libobjc/thr-vxworks.c 2963027857b ./libobjc/thr-win32.c 3239202263b ./libobjc/thr.c ! 3164673878b ./libstdc++-v3/ChangeLog 1996982572b ./libstdc++-v3/ChangeLog-2000 3665233589b ./libstdc++-v3/ChangeLog-2001 3601994870b ./libstdc++-v3/Makefile.am *************** *** 13450,13456 **** 201474883b ./libstdc++-v3/README 4114737556b ./libstdc++-v3/acconfig.h 1335999300b ./libstdc++-v3/acinclude.m4 ! 2806298612b ./libstdc++-v3/aclocal.m4 1280750931b ./libstdc++-v3/config.h.in 4214408479b ./libstdc++-v3/config/abi/alphaev67-unknown-linux-gnu/baseline_symbols.txt 1077465800b ./libstdc++-v3/config/abi/extract_symvers --- 13569,13575 ---- 201474883b ./libstdc++-v3/README 4114737556b ./libstdc++-v3/acconfig.h 1335999300b ./libstdc++-v3/acinclude.m4 ! 1757393875b ./libstdc++-v3/aclocal.m4 1280750931b ./libstdc++-v3/config.h.in 4214408479b ./libstdc++-v3/config/abi/alphaev67-unknown-linux-gnu/baseline_symbols.txt 1077465800b ./libstdc++-v3/config/abi/extract_symvers *************** *** 13516,13522 **** 3496359145b ./libstdc++-v3/config/locale/gnu/time_members.h 3232379868b ./libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.cc 3136594064b ./libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.h ! 3256263647b ./libstdc++-v3/config/locale/ieee_1003.1-2001/codecvt_specializations.h 3823275112b ./libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.cc 488667815b ./libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.h 4256387970b ./libstdc++-v3/config/os/aix/bits/atomicity.h --- 13635,13641 ---- 3496359145b ./libstdc++-v3/config/locale/gnu/time_members.h 3232379868b ./libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.cc 3136594064b ./libstdc++-v3/config/locale/ieee_1003.1-2001/c_locale.h ! 2429580009b ./libstdc++-v3/config/locale/ieee_1003.1-2001/codecvt_specializations.h 3823275112b ./libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.cc 488667815b ./libstdc++-v3/config/locale/ieee_1003.1-2001/messages_members.h 4256387970b ./libstdc++-v3/config/os/aix/bits/atomicity.h *************** *** 13547,13553 **** 1503897878b ./libstdc++-v3/config/os/hpux/bits/cpu_limits.h 2727448261b ./libstdc++-v3/config/os/hpux/bits/ctype_base.h 521899911b ./libstdc++-v3/config/os/hpux/bits/ctype_inline.h ! 1287488501b ./libstdc++-v3/config/os/hpux/bits/ctype_noninline.h 4256303940b ./libstdc++-v3/config/os/hpux/bits/os_defines.h 805235121b ./libstdc++-v3/config/os/irix/irix5.2/bits/atomicity.h 734403019b ./libstdc++-v3/config/os/irix/irix5.2/bits/ctype_base.h --- 13666,13672 ---- 1503897878b ./libstdc++-v3/config/os/hpux/bits/cpu_limits.h 2727448261b ./libstdc++-v3/config/os/hpux/bits/ctype_base.h 521899911b ./libstdc++-v3/config/os/hpux/bits/ctype_inline.h ! 766270739b ./libstdc++-v3/config/os/hpux/bits/ctype_noninline.h 4256303940b ./libstdc++-v3/config/os/hpux/bits/os_defines.h 805235121b ./libstdc++-v3/config/os/irix/irix5.2/bits/atomicity.h 734403019b ./libstdc++-v3/config/os/irix/irix5.2/bits/ctype_base.h *************** *** 13584,13592 **** 577770049b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/ctype_inline.h 399834321b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/ctype_noninline.h 157883947b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/os_defines.h ! 1247614208b ./libstdc++-v3/configure 3116040814b ./libstdc++-v3/configure.host ! 2627385010b ./libstdc++-v3/configure.in 282761406b ./libstdc++-v3/configure.target 1637481960b ./libstdc++-v3/docs/doxygen/Intro.3 2829674872b ./libstdc++-v3/docs/doxygen/TODO --- 13703,13711 ---- 577770049b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/ctype_inline.h 399834321b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/ctype_noninline.h 157883947b ./libstdc++-v3/config/os/solaris/solaris2.7/bits/os_defines.h ! 3647444520b ./libstdc++-v3/configure 3116040814b ./libstdc++-v3/configure.host ! 31792307b ./libstdc++-v3/configure.in 282761406b ./libstdc++-v3/configure.target 1637481960b ./libstdc++-v3/docs/doxygen/Intro.3 2829674872b ./libstdc++-v3/docs/doxygen/TODO *************** *** 13698,13710 **** 1196444434b ./libstdc++-v3/include/bits/basic_string.h 3004074520b ./libstdc++-v3/include/bits/basic_string.tcc 179433314b ./libstdc++-v3/include/bits/boost_concept_check.h ! 2325758266b ./libstdc++-v3/include/bits/c++config 3498736544b ./libstdc++-v3/include/bits/char_traits.h 3672868066b ./libstdc++-v3/include/bits/codecvt.h 2442194789b ./libstdc++-v3/include/bits/concept_check.h 329719722b ./libstdc++-v3/include/bits/cpp_type_traits.h 1176672394b ./libstdc++-v3/include/bits/fpos.h ! 2897059516b ./libstdc++-v3/include/bits/fstream.tcc 3886600201b ./libstdc++-v3/include/bits/functexcept.h 3055891139b ./libstdc++-v3/include/bits/generic_shadow.h 1117238130b ./libstdc++-v3/include/bits/gslice.h --- 13817,13829 ---- 1196444434b ./libstdc++-v3/include/bits/basic_string.h 3004074520b ./libstdc++-v3/include/bits/basic_string.tcc 179433314b ./libstdc++-v3/include/bits/boost_concept_check.h ! 1036368554b ./libstdc++-v3/include/bits/c++config 3498736544b ./libstdc++-v3/include/bits/char_traits.h 3672868066b ./libstdc++-v3/include/bits/codecvt.h 2442194789b ./libstdc++-v3/include/bits/concept_check.h 329719722b ./libstdc++-v3/include/bits/cpp_type_traits.h 1176672394b ./libstdc++-v3/include/bits/fpos.h ! 1776886078b ./libstdc++-v3/include/bits/fstream.tcc 3886600201b ./libstdc++-v3/include/bits/functexcept.h 3055891139b ./libstdc++-v3/include/bits/generic_shadow.h 1117238130b ./libstdc++-v3/include/bits/gslice.h *************** *** 13750,13756 **** 1954571679b ./libstdc++-v3/include/bits/stl_uninitialized.h 1856687262b ./libstdc++-v3/include/bits/stl_vector.h 99981565b ./libstdc++-v3/include/bits/stream_iterator.h ! 2491807253b ./libstdc++-v3/include/bits/streambuf.tcc 466836896b ./libstdc++-v3/include/bits/streambuf_iterator.h 1373192946b ./libstdc++-v3/include/bits/stringfwd.h 1571290449b ./libstdc++-v3/include/bits/type_traits.h --- 13869,13875 ---- 1954571679b ./libstdc++-v3/include/bits/stl_uninitialized.h 1856687262b ./libstdc++-v3/include/bits/stl_vector.h 99981565b ./libstdc++-v3/include/bits/stream_iterator.h ! 3082898899b ./libstdc++-v3/include/bits/streambuf.tcc 466836896b ./libstdc++-v3/include/bits/streambuf_iterator.h 1373192946b ./libstdc++-v3/include/bits/stringfwd.h 1571290449b ./libstdc++-v3/include/bits/type_traits.h *************** *** 13910,13916 **** 4158492065b ./libstdc++-v3/include/std/std_utility.h 362016596b ./libstdc++-v3/include/std/std_valarray.h 125145631b ./libstdc++-v3/include/std/std_vector.h ! 2717296741b ./libstdc++-v3/libio/ChangeLog 226381804b ./libstdc++-v3/libio/Makefile.am 4199895907b ./libstdc++-v3/libio/Makefile.in 314955067b ./libstdc++-v3/libio/_G_config.h --- 14029,14035 ---- 4158492065b ./libstdc++-v3/include/std/std_utility.h 362016596b ./libstdc++-v3/include/std/std_valarray.h 125145631b ./libstdc++-v3/include/std/std_vector.h ! 4102282136b ./libstdc++-v3/libio/ChangeLog 226381804b ./libstdc++-v3/libio/Makefile.am 4199895907b ./libstdc++-v3/libio/Makefile.in 314955067b ./libstdc++-v3/libio/_G_config.h *************** *** 14171,14182 **** 1162163080b ./libstdc++-v3/testsuite/27_io/filebuf.cc 4294967295b ./libstdc++-v3/testsuite/27_io/filebuf_members-1.tst 4294967295b ./libstdc++-v3/testsuite/27_io/filebuf_members-1.txt ! 3299934909b ./libstdc++-v3/testsuite/27_io/filebuf_members.cc 4204648704b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-1.tst 4204648704b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-1.txt 655821823b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-2.tst 1896106013b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-3.tst ! 4060177148b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals.cc 1987901042b ./libstdc++-v3/testsuite/27_io/fpos.cc 2165147103b ./libstdc++-v3/testsuite/27_io/fstream.cc 358840366b ./libstdc++-v3/testsuite/27_io/fstream_members.cc --- 14290,14301 ---- 1162163080b ./libstdc++-v3/testsuite/27_io/filebuf.cc 4294967295b ./libstdc++-v3/testsuite/27_io/filebuf_members-1.tst 4294967295b ./libstdc++-v3/testsuite/27_io/filebuf_members-1.txt ! 1936479101b ./libstdc++-v3/testsuite/27_io/filebuf_members.cc 4204648704b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-1.tst 4204648704b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-1.txt 655821823b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-2.tst 1896106013b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals-3.tst ! 3120338832b ./libstdc++-v3/testsuite/27_io/filebuf_virtuals.cc 1987901042b ./libstdc++-v3/testsuite/27_io/fpos.cc 2165147103b ./libstdc++-v3/testsuite/27_io/fstream.cc 358840366b ./libstdc++-v3/testsuite/27_io/fstream_members.cc *************** *** 14292,14298 **** 3594421631b ./ltcf-gcj.sh 30175378b ./ltconfig 2369122487b ./ltmain.sh ! 1935971162b ./maintainer-scripts/ChangeLog 3126840705b ./maintainer-scripts/README 1905552954b ./maintainer-scripts/crontab 4171969357b ./maintainer-scripts/doc_exclude --- 14411,14417 ---- 3594421631b ./ltcf-gcj.sh 30175378b ./ltconfig 2369122487b ./ltmain.sh ! 1660471952b ./maintainer-scripts/ChangeLog 3126840705b ./maintainer-scripts/README 1905552954b ./maintainer-scripts/crontab 4171969357b ./maintainer-scripts/doc_exclude *************** *** 14309,14316 **** 902556840b ./move-if-change 1077958069b ./symlink-tree 1370970362b ./ylwrap ! 1298224910b ./zlib/ChangeLog ! 4044693717b ./zlib/ChangeLog.gcj 1790959550b ./zlib/FAQ 467711448b ./zlib/INDEX 3901505907b ./zlib/Make_vms.com --- 14428,14435 ---- 902556840b ./move-if-change 1077958069b ./symlink-tree 1370970362b ./ylwrap ! 426049005b ./zlib/ChangeLog ! 356214916b ./zlib/ChangeLog.gcj 1790959550b ./zlib/FAQ 467711448b ./zlib/INDEX 3901505907b ./zlib/Make_vms.com *************** *** 14325,14332 **** 1537725969b ./zlib/amiga/Makefile.pup 3919607569b ./zlib/amiga/Makefile.sas 720988996b ./zlib/compress.c ! 449189607b ./zlib/configure ! 908419910b ./zlib/configure.in 3769239525b ./zlib/contrib/README.contrib 215845136b ./zlib/contrib/asm386/gvmat32.asm 4143184108b ./zlib/contrib/asm386/gvmat32c.c --- 14444,14451 ---- 1537725969b ./zlib/amiga/Makefile.pup 3919607569b ./zlib/amiga/Makefile.sas 720988996b ./zlib/compress.c ! 784731032b ./zlib/configure ! 3521535304b ./zlib/configure.in 3769239525b ./zlib/contrib/README.contrib 215845136b ./zlib/contrib/asm386/gvmat32.asm 4143184108b ./zlib/contrib/asm386/gvmat32c.c diff -Nrc3pad gcc-3.2.2/BUGS gcc-3.2.3/BUGS *** gcc-3.2.2/BUGS Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/BUGS Tue Apr 22 06:56:31 2003 *************** *** 2,8 **** GCC Bugs The latest version of this document is always available at ! [1]http://www.gnu.org/software/gcc/bugs.html. _________________________________________________________________ Table of Contents --- 2,8 ---- GCC Bugs The latest version of this document is always available at ! [1]http://gcc.gnu.org/bugs.html. _________________________________________________________________ Table of Contents *************** Table of Contents *** 15,39 **** + [7]Detailed bug reporting instructions for GNAT + [8]Detailed bug reporting instructions when using a precompiled header ! * [9]Managing Bugs (GNATS and the test-suite) ! * [10]Frequently Reported Bugs in GCC ! + [11]General ! + [12]Fortran ! + [13]C ! + [14]C++ ! o [15]Common problems updating from G++ 2.95 to G++ 3.0 ! o [16]Non-bugs ! o [17]Missing features ! o [18]Parse errors for "simple" code ! o [19]Optimization at -O3 takes a very long time _________________________________________________________________ Reporting Bugs ! Our preferred way of receiving bugs is via the [20]GCC GNATS bug reporting system. ! Before you report a bug, please check the [21]list of well-known bugs and, if possible in any way, try a current development snapshot. If you want to report a bug with versions of GCC before 3.1 we strongly recommend upgrading to the current release first. --- 15,38 ---- + [7]Detailed bug reporting instructions for GNAT + [8]Detailed bug reporting instructions when using a precompiled header ! * [9]Frequently Reported Bugs in GCC ! + [10]General ! + [11]Fortran ! + [12]C ! + [13]C++ ! o [14]Common problems updating from G++ 2.95 to G++ 3.0 ! o [15]Non-bugs ! o [16]Missing features ! o [17]Parse errors for "simple" code ! o [18]Optimization at -O3 takes a very long time _________________________________________________________________ Reporting Bugs ! Our preferred way of receiving bugs is via the [19]GCC GNATS bug reporting system. ! Before you report a bug, please check the [20]list of well-known bugs and, if possible in any way, try a current development snapshot. If you want to report a bug with versions of GCC before 3.1 we strongly recommend upgrading to the current release first. *************** Summarized bug reporting instructions *** 101,118 **** Where to post it ! Please submit your bug report directly to the [22]GCC GNATS bug database. Only if this is not possible, mail all information to ! [23]bug-gcc@gnu.org or [24]gcc-bugs@gcc.gnu.org. The GCC lists have message size limits (200 kbytes) and bug reports over those limits will currently be bounced. If your bug is larger ! than that, please post it using the [25]GCC GNATS bug database. Detailed bug reporting instructions ! Please refer to the [26]next section when reporting bugs in GNAT, the ! Ada compiler, or to the [27]one after that when reporting bugs that appear when using a precompiled header. In general, all the information we need can be obtained by collecting --- 100,117 ---- Where to post it ! Please submit your bug report directly to the [21]GCC GNATS bug database. Only if this is not possible, mail all information to ! [22]bug-gcc@gnu.org or [23]gcc-bugs@gcc.gnu.org. The GCC lists have message size limits (200 kbytes) and bug reports over those limits will currently be bounced. If your bug is larger ! than that, please post it using the [24]GCC GNATS bug database. Detailed bug reporting instructions ! Please refer to the [25]next section when reporting bugs in GNAT, the ! Ada compiler, or to the [26]one after that when reporting bugs that appear when using a precompiled header. In general, all the information we need can be obtained by collecting *************** Detailed bug reporting instructions *** 168,174 **** Detailed bug reporting instructions for GNAT ! See the [28]previous section for bug reporting instructions for GCC language implementations other than Ada. Bug reports have to contain at least the following information in --- 167,173 ---- Detailed bug reporting instructions for GNAT ! See the [27]previous section for bug reporting instructions for GCC language implementations other than Ada. Bug reports have to contain at least the following information in *************** Detailed bug reporting instructions for *** 200,206 **** you have to report a bug in gnatprep). When you have checked that your report meets these criteria, please ! submit it according to our [29]generic instructions. (If you use a mailing list for reporting, please include an "[Ada]" tag in the subject.) --- 199,205 ---- you have to report a bug in gnatprep). When you have checked that your report meets these criteria, please ! submit it according to our [28]generic instructions. (If you use a mailing list for reporting, please include an "[Ada]" tag in the subject.) *************** Detailed bug reporting instructions when *** 210,220 **** first thing to do is to delete the precompiled header, and try running the same GCC command again. If the bug happens again, the bug doesn't really involve precompiled headers, please report it without using ! them by following the instructions [30]above. If you've found a bug while building a precompiled header (for instance, the compiler crashes), follow the usual instructions ! [31]above. If you've found a real precompiled header bug, what we'll need to reproduce it is the sources to build the precompiled header (as a --- 209,219 ---- first thing to do is to delete the precompiled header, and try running the same GCC command again. If the bug happens again, the bug doesn't really involve precompiled headers, please report it without using ! them by following the instructions [29]above. If you've found a bug while building a precompiled header (for instance, the compiler crashes), follow the usual instructions ! [30]above. If you've found a real precompiled header bug, what we'll need to reproduce it is the sources to build the precompiled header (as a *************** Detailed bug reporting instructions when *** 224,249 **** Please don't send us the actual precompiled header. It is likely to be very large and we can't use it to reproduce the problem. - - Managing Bugs (GNATS and the test-suite) - - This section contains information mostly intended for GCC - contributors. - - If you find a bug, but you are not fixing it (yet): - 1. Create a (minimal) test-case. - 2. Add the test-case to our test-suite, marking it as XFAIL unless - the bug is a regression. - 3. Add a bug report referencing the test-case to GNATS. - - If you fix a bug for which there is already a GNATS entry: - 1. Remove the XFAIL on the test-case. - 2. Close the bug report in GNATS. - - If you find a bug, and you are fixing it right then: - 1. Create a (minimal) test-case. - 2. Add the test-case to our test-suite, marking it as PASS. - 3. Check in your fixes. _________________________________________________________________ Frequently Reported Bugs in GCC --- 223,228 ---- *************** Detailed bug reporting instructions when *** 251,257 **** Fortran Fortran bugs are documented in the G77 manual rather than explicitly ! listed here. Please see [32]Known Causes of Trouble with GNU Fortran in the G77 manual. _________________________________________________________________ --- 230,236 ---- Fortran Fortran bugs are documented in the G77 manual rather than explicitly ! listed here. Please see [31]Known Causes of Trouble with GNU Fortran in the G77 manual. _________________________________________________________________ *************** FILE *yyin = stdin; *** 283,289 **** There is a common misconception that the GCC developers are responsible for GNU libc. These are in fact two entirely ! separate projects; please check the [33]GNU libc web pages for details. Cannot use preprocessor directive in macro arguments. --- 262,268 ---- There is a common misconception that the GCC developers are responsible for GNU libc. These are in fact two entirely ! separate projects; please check the [32]GNU libc web pages for details. Cannot use preprocessor directive in macro arguments. *************** C++ *** 347,353 **** reported very often, but not yet fixed. While it is certainly better to fix bugs instead of documenting them, this document might save people the effort of writing a bug report when the bug is already ! well-known. [34]How to report bugs tells you how to report a bug. There are many reasons why reported bugs don't get fixed. It might be difficult to fix, or fixing it might break compatibility. Often, --- 326,332 ---- reported very often, but not yet fixed. While it is certainly better to fix bugs instead of documenting them, this document might save people the effort of writing a bug report when the bug is already ! well-known. [33]How to report bugs tells you how to report a bug. There are many reasons why reported bugs don't get fixed. It might be difficult to fix, or fixing it might break compatibility. Often, *************** C++ *** 365,376 **** Common problems updating from G++ 2.95 to G++ 3.0 G++ 3.0 conforms much closer to the ISO C++ standard (available at ! [35]http://www.ncits.org/cplusplus.htm). We have also implemented some of the core and library defect reports (available at ! [36]http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html & ! [37]http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html respectively). * The ABI has changed. This means that both class layout and name mangling is different. You must recompile all c++ libraries (if --- 344,355 ---- Common problems updating from G++ 2.95 to G++ 3.0 G++ 3.0 conforms much closer to the ISO C++ standard (available at ! [34]http://www.ncits.org/cplusplus.htm). We have also implemented some of the core and library defect reports (available at ! [35]http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html & ! [36]http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html respectively). * The ABI has changed. This means that both class layout and name mangling is different. You must recompile all c++ libraries (if *************** C++ *** 478,484 **** the nearest representable number. This is not a bug in the compiler, but an inherent limitation ! of the float and double types. Please study [38]this paper for more information. Templates, scoping, and digraphs. --- 457,463 ---- the nearest representable number. This is not a bug in the compiler, but an inherent limitation ! of the float and double types. Please study [37]this paper for more information. Templates, scoping, and digraphs. *************** A B::f1(bool b) *** 584,590 **** References ! 1. http://www.gnu.org/software/gcc/bugs.html 2. http://gcc.gnu.org/bugs.html#report 3. http://gcc.gnu.org/bugs.html#need 4. http://gcc.gnu.org/bugs.html#dontwant --- 563,569 ---- References ! 1. http://gcc.gnu.org/bugs.html 2. http://gcc.gnu.org/bugs.html#report 3. http://gcc.gnu.org/bugs.html#need 4. http://gcc.gnu.org/bugs.html#dontwant *************** References *** 592,624 **** 6. http://gcc.gnu.org/bugs.html#detailed 7. http://gcc.gnu.org/bugs.html#gnat 8. http://gcc.gnu.org/bugs.html#pch ! 9. http://gcc.gnu.org/bugs.html#manage ! 10. http://gcc.gnu.org/bugs.html#known ! 11. http://gcc.gnu.org/bugs.html#general ! 12. http://gcc.gnu.org/bugs.html#fortran ! 13. http://gcc.gnu.org/bugs.html#c ! 14. http://gcc.gnu.org/bugs.html#cplusplus ! 15. http://gcc.gnu.org/bugs.html#updating ! 16. http://gcc.gnu.org/bugs.html#nonbugs ! 17. http://gcc.gnu.org/bugs.html#missing ! 18. http://gcc.gnu.org/bugs.html#parsing ! 19. http://gcc.gnu.org/bugs.html#-O3 ! 20. http://gcc.gnu.org/gnats.html ! 21. http://gcc.gnu.org/bugs.html#known ! 22. http://gcc.gnu.org/gnats.html ! 23. mailto:bug-gcc@gnu.org ! 24. mailto:gcc-bugs@gcc.gnu.org ! 25. http://gcc.gnu.org/gnats.html ! 26. http://gcc.gnu.org/bugs.html#gnat ! 27. http://gcc.gnu.org/bugs.html#pch ! 28. http://gcc.gnu.org/bugs.html#detailed ! 29. http://gcc.gnu.org/bugs.html#where 30. http://gcc.gnu.org/bugs.html#detailed ! 31. http://gcc.gnu.org/bugs.html#detailed ! 32. http://gcc.gnu.org/onlinedocs/g77/Trouble.html ! 33. http://www.gnu.org/software/glibc/ ! 34. http://gcc.gnu.org/bugs.html#report ! 35. http://www.ncits.org/cplusplus.htm ! 36. http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html ! 37. http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html ! 38. http://www.validlab.com/goldberg/paper.ps --- 571,602 ---- 6. http://gcc.gnu.org/bugs.html#detailed 7. http://gcc.gnu.org/bugs.html#gnat 8. http://gcc.gnu.org/bugs.html#pch ! 9. http://gcc.gnu.org/bugs.html#known ! 10. http://gcc.gnu.org/bugs.html#general ! 11. http://gcc.gnu.org/bugs.html#fortran ! 12. http://gcc.gnu.org/bugs.html#c ! 13. http://gcc.gnu.org/bugs.html#cplusplus ! 14. http://gcc.gnu.org/bugs.html#updating ! 15. http://gcc.gnu.org/bugs.html#nonbugs ! 16. http://gcc.gnu.org/bugs.html#missing ! 17. http://gcc.gnu.org/bugs.html#parsing ! 18. http://gcc.gnu.org/bugs.html#-O3 ! 19. http://gcc.gnu.org/gnats.html ! 20. http://gcc.gnu.org/bugs.html#known ! 21. http://gcc.gnu.org/gnats.html ! 22. mailto:bug-gcc@gnu.org ! 23. mailto:gcc-bugs@gcc.gnu.org ! 24. http://gcc.gnu.org/gnats.html ! 25. http://gcc.gnu.org/bugs.html#gnat ! 26. http://gcc.gnu.org/bugs.html#pch ! 27. http://gcc.gnu.org/bugs.html#detailed ! 28. http://gcc.gnu.org/bugs.html#where ! 29. http://gcc.gnu.org/bugs.html#detailed 30. http://gcc.gnu.org/bugs.html#detailed ! 31. http://gcc.gnu.org/onlinedocs/g77/Trouble.html ! 32. http://www.gnu.org/software/glibc/ ! 33. http://gcc.gnu.org/bugs.html#report ! 34. http://www.ncits.org/cplusplus.htm ! 35. http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_defects.html ! 36. http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html ! 37. http://www.validlab.com/goldberg/paper.ps diff -Nrc3pad gcc-3.2.2/ChangeLog gcc-3.2.3/ChangeLog *** gcc-3.2.2/ChangeLog Wed Feb 5 03:02:21 2003 --- gcc-3.2.3/ChangeLog Tue Apr 22 06:14:01 2003 *************** *** 1,3 **** --- 1,11 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + + 2003-02-12 Marc Espie + + * config-ml.in: Propagate DESTDIR. + 2003-02-05 Release Manager * GCC 3.2.2 Released. diff -Nrc3pad gcc-3.2.2/FAQ gcc-3.2.3/FAQ *** gcc-3.2.2/FAQ Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/FAQ Tue Apr 22 06:56:31 2003 *************** *** 2,8 **** GCC Frequently Asked Questions The latest version of this document is always available at ! [1]http://www.gnu.org/software/gcc/faq.html. This FAQ tries to answer specific questions concerning GCC. For general information regarding C, C++, resp. Fortran please check the --- 2,8 ---- GCC Frequently Asked Questions The latest version of this document is always available at ! [1]http://gcc.gnu.org/faq.html. This FAQ tries to answer specific questions concerning GCC. For general information regarding C, C++, resp. Fortran please check the *************** What is an open development model? *** 126,138 **** the past few months. The paper which started all of this introduced two terms: A cathedral development model versus a bazaar development model. The paper is written by Eric S. Raymond, it is ! called ``[37]The Cathedral and the Bazaar''. The paper is a useful starting point for discussions. _________________________________________________________________ How do I report a bug? ! There are complete instructions [38]here. _________________________________________________________________ How do I get a bug fixed or a feature added? --- 126,138 ---- the past few months. The paper which started all of this introduced two terms: A cathedral development model versus a bazaar development model. The paper is written by Eric S. Raymond, it is ! called ``The Cathedral and the Bazaar''. The paper is a useful starting point for discussions. _________________________________________________________________ How do I report a bug? ! There are complete instructions [37]here. _________________________________________________________________ How do I get a bug fixed or a feature added? *************** How do I get a bug fixed or a feature ad *** 147,153 **** * Hire someone to fix it for you. There are various companies and individuals providing support for GCC. This alternative costs money, but is relatively likely to get results. ! * [39]Report the problem to the GCC GNATS bug tracking system and hope that someone will be kind enough to fix it for you. While this is certainly possible, and often happens, there is no guarantee that it will. You should not expect the same response --- 147,153 ---- * Hire someone to fix it for you. There are various companies and individuals providing support for GCC. This alternative costs money, but is relatively likely to get results. ! * [38]Report the problem to the GCC GNATS bug tracking system and hope that someone will be kind enough to fix it for you. While this is certainly possible, and often happens, there is no guarantee that it will. You should not expect the same response *************** How do I get a bug fixed or a feature ad *** 155,161 **** organization since the people who read GCC bug reports, if they choose to help you, will be volunteering their time. This alternative will work best if you follow the directions on ! [40]submitting bugreports. * Fix it yourself. This alternative will probably bring results, if you work hard enough, but will probably take a lot of time, and, depending on the quality of your work and the perceived benefits --- 155,161 ---- organization since the people who read GCC bug reports, if they choose to help you, will be volunteering their time. This alternative will work best if you follow the directions on ! [39]submitting bugreports. * Fix it yourself. This alternative will probably bring results, if you work hard enough, but will probably take a lot of time, and, depending on the quality of your work and the perceived benefits *************** Does GCC work on my platform? *** 168,175 **** The host/target specific installation notes for GCC include information about known problems with installing or using GCC on particular platforms. These are included in the sources for a release ! in INSTALL/specific.html, and the [41]latest version is always ! available at the GCC web site. Reports of [42]successful builds for several versions of GCC are also available at the web site. _________________________________________________________________ --- 168,175 ---- The host/target specific installation notes for GCC include information about known problems with installing or using GCC on particular platforms. These are included in the sources for a release ! in INSTALL/specific.html, and the [40]latest version is always ! available at the GCC web site. Reports of [41]successful builds for several versions of GCC are also available at the web site. _________________________________________________________________ *************** How to install multiple versions of GCC *** 216,222 **** wish to be sure about which version you are invoking. If you use --prefix, GCC may have difficulty locating a GNU assembler ! or linker on your system, [43]GCC can not find GNU as/GNU ld explains how to deal with this. Another option that may be easier is to use the --program-prefix= or --- 216,222 ---- wish to be sure about which version you are invoking. If you use --prefix, GCC may have difficulty locating a GNU assembler ! or linker on your system, [42]GCC can not find GNU as/GNU ld explains how to deal with this. Another option that may be easier is to use the --program-prefix= or *************** GCC can not find GNU as/GNU ld *** 282,288 **** versions of those programs. To ensure that GCC finds the GNU assembler (the GNU loader), which are ! required by [44]some configurations, you should configure these with the same --prefix option as you used for GCC. Then build & install GNU as (GNU ld) and proceed with building GCC. --- 282,288 ---- versions of those programs. To ensure that GCC finds the GNU assembler (the GNU loader), which are ! required by [43]some configurations, you should configure these with the same --prefix option as you used for GCC. Then build & install GNU as (GNU ld) and proceed with building GCC. *************** Unable to run the testsuite *** 336,342 **** If you get a message about unable to find "standard.exp" when trying to run the GCC testsuites, then your dejagnu is too old to run the GCC tests. You will need to get a newer version of dejagnu from ! [45]http://www.gnu.org/software/dejagnu/dejagnu.html. _________________________________________________________________ How do I pass flags like -fnew-abi to the testsuite? --- 336,342 ---- If you get a message about unable to find "standard.exp" when trying to run the GCC testsuites, then your dejagnu is too old to run the GCC tests. You will need to get a newer version of dejagnu from ! [44]http://www.gnu.org/software/dejagnu/dejagnu.html. _________________________________________________________________ How do I pass flags like -fnew-abi to the testsuite? *************** How can I run the test suite with multip *** 371,377 **** Is there a stringstream / sstream for GCC 2.95.2? Yes, it's at: ! [46]http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream. _________________________________________________________________ Miscellaneous --- 371,377 ---- Is there a stringstream / sstream for GCC 2.95.2? Yes, it's at: ! [45]http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream. _________________________________________________________________ Miscellaneous *************** dynamic_cast, throw, typeid don't work w *** 470,476 **** [basic.def.odr]. For more details about the way that GCC implements these and other C++ ! features, please read the [47]ABI specification. Note the std::typeinfo_t objects which must be resolved all begin with "_ZTS". Refer to ld's documentation for a description of the "-E" & "-Bsymbolic" flags. --- 470,476 ---- [basic.def.odr]. For more details about the way that GCC implements these and other C++ ! features, please read the [46]ABI specification. Note the std::typeinfo_t objects which must be resolved all begin with "_ZTS". Refer to ld's documentation for a description of the "-E" & "-Bsymbolic" flags. *************** Why do I need autoconf, bison, xgettext, *** 501,510 **** rebuild GCC. In general, the current versions of these tools from ! [48]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not supported, and you will need to use Autoconf 2.13; work is in progress to fix this problem. Also look at ! [49]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions of packages. _________________________________________________________________ --- 501,510 ---- rebuild GCC. In general, the current versions of these tools from ! [47]ftp://ftp.gnu.org/gnu/ will work. At present, Autoconf 2.50 is not supported, and you will need to use Autoconf 2.13; work is in progress to fix this problem. Also look at ! [48]ftp://gcc.gnu.org/pub/gcc/infrastructure/ for any special versions of packages. _________________________________________________________________ *************** Will GCC someday include an incremental *** 560,568 **** References ! 1. http://www.gnu.org/software/gcc/faq.html 2. http://www.eskimo.com/~scs/C-faq/top.html ! 3. http://www.research.att.com/~austern/csc/faq.html 4. http://www.fortran.com/fortran/info.html 5. http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html 6. http://gcc.gnu.org/java/faq.html --- 560,568 ---- References ! 1. http://gcc.gnu.org/faq.html 2. http://www.eskimo.com/~scs/C-faq/top.html ! 3. http://www.jamesd.demon.co.uk/csc/faq.html 4. http://www.fortran.com/fortran/info.html 5. http://gcc.gnu.org/onlinedocs/libstdc++/faq/index.html 6. http://gcc.gnu.org/java/faq.html *************** References *** 596,611 **** 34. http://gcc.gnu.org/steering.html 35. http://gcc.gnu.org/steering.html 36. http://gcc.gnu.org/faq.html#cathedral-vs-bazaar ! 37. http://www.tuxedo.org/~esr/writings/cathedral-bazaar/ 38. http://gcc.gnu.org/bugs.html 39. http://gcc.gnu.org/bugs.html ! 40. http://gcc.gnu.org/bugs.html ! 41. http://gcc.gnu.org/install/specific.html ! 42. http://gcc.gnu.org/buildstat.html ! 43. http://gcc.gnu.org/faq.html#gas ! 44. http://gcc.gnu.org/install/specific.html ! 45. http://www.gnu.org/software/dejagnu/dejagnu.html ! 46. http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream ! 47. http://www.codesourcery.com/cxx-abi/ ! 48. ftp://ftp.gnu.org/gnu/ ! 49. ftp://gcc.gnu.org/pub/gcc/infrastructure/ --- 596,610 ---- 34. http://gcc.gnu.org/steering.html 35. http://gcc.gnu.org/steering.html 36. http://gcc.gnu.org/faq.html#cathedral-vs-bazaar ! 37. http://gcc.gnu.org/bugs.html 38. http://gcc.gnu.org/bugs.html 39. http://gcc.gnu.org/bugs.html ! 40. http://gcc.gnu.org/install/specific.html ! 41. http://gcc.gnu.org/buildstat.html ! 42. http://gcc.gnu.org/faq.html#gas ! 43. http://gcc.gnu.org/install/specific.html ! 44. http://www.gnu.org/software/dejagnu/dejagnu.html ! 45. http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00700/sstream ! 46. http://www.codesourcery.com/cxx-abi/ ! 47. ftp://ftp.gnu.org/gnu/ ! 48. ftp://gcc.gnu.org/pub/gcc/infrastructure/ diff -Nrc3pad gcc-3.2.2/INSTALL/binaries.html gcc-3.2.3/INSTALL/binaries.html *** gcc-3.2.2/INSTALL/binaries.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/binaries.html Tue Apr 22 06:56:34 2003 *************** *** 1,59 **** ! Installing GCC: Binaries ! ! ! ! ! !

W

e are often asked about pre-compiled versions of GCC. While we cannot provide these for all platforms, below you'll find links to binaries for various platforms where creating them by yourself is not easy due to various reasons. !

Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their makers. !

!

In addition to those specific offerings, you can get a binary distribution CD-ROM from the Free Software Foundation. It contains binaries for a number of platforms, and --- 1,61 ---- ! ! Installing GCC: Binaries ! ! ! ! ! !

Installing GCC: Binaries

! We are often asked about pre-compiled versions of GCC. While we cannot provide these for all platforms, below you'll find links to binaries for various platforms where creating them by yourself is not easy due to various reasons. !

Please note that we did not create these binaries, nor do we support them. If you have any problems installing them, please contact their makers. !

!

In addition to those specific offerings, you can get a binary distribution CD-ROM from the Free Software Foundation. It contains binaries for a number of platforms, and *************** not contain the latest version of GCC, b *** 62,70 **** bootstrapping the compiler. An updated version of that disk is in the works. !

Return to the GCC Installation page ! --- 64,72 ---- bootstrapping the compiler. An updated version of that disk is in the works. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/build.html gcc-3.2.3/INSTALL/build.html *** gcc-3.2.2/INSTALL/build.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/build.html Tue Apr 22 06:56:33 2003 *************** *** 1,100 **** ! Installing GCC: Building ! ! ! ! ! !

N

ow that GCC is configured, you are ready to build the compiler and runtime libraries. !

We highly recommend that GCC be built using GNU make; other versions may work, then again they might not. GNU make is required for compiling GNAT (the Ada compiler) and the Java runtime library. !

(For example, many broken versions of make will fail if you use the recommended setup where objdir is different from srcdir. Other broken versions may recompile parts of the compiler when installing the compiler.) !

Some commands executed when making the compiler may fail (return a nonzero status) and be ignored by make. These failures, which are often due to files that were not found, are expected, and can safely be ignored. !

It is normal to have compiler warnings when compiling certain files. Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. !

On certain old systems, defining certain environment variables such as CC can interfere with the functioning of make. !

If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be because you have previously configured the compiler in the source directory. Make sure you have done all the necessary preparations. !

If you build GCC on a BSD system using a directory stored in an old System V file system, problems may occur in running fixincludes if the System V file system doesn't support symbolic links. These problems result in a failure to fix the declaration of size_t in sys/types.h. If you find that size_t is a signed type and that type mismatches occur, this could be the cause. !

The solution is not to use such a directory for building GCC. !

When building from CVS or snapshots, or if you modify parser sources, you need the Bison parser generator installed. Any version 1.25 or later should work; older versions may also work. If you do not modify parser sources, releases contain the Bison-generated files and you do not need Bison installed to build them. !

When building from CVS or snapshots, or if you modify Texinfo documentation, you need version 4.1 or later of Texinfo installed if you want Info documentation to be regenerated. Releases contain Info documentation pre-built for the unmodified documentation in the release. !

Building a native compiler

!

For a native build issue the command make bootstrap. This will build the entire GCC system, which includes the following steps: !

!

If you are short on disk space you might consider make bootstrap-lean instead. This is identical to make bootstrap except that object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. !

If you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) ! 

     make CFLAGS='-O' LIBCFLAGS='-g -O2' \
!        LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
!
!

If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set BOOT_CFLAGS on the command line when doing make bootstrap. Non-default optimization flags are less well tested here than the default of -g -O2, but should still work. --- 1,102 ---- ! ! Installing GCC: Building ! ! ! ! ! !

Installing GCC: Building

! Now that GCC is configured, you are ready to build the compiler and runtime libraries. !

We highly recommend that GCC be built using GNU make; other versions may work, then again they might not. GNU make is required for compiling GNAT (the Ada compiler) and the Java runtime library. !

(For example, many broken versions of make will fail if you use the recommended setup where objdir is different from srcdir. Other broken versions may recompile parts of the compiler when installing the compiler.) !

Some commands executed when making the compiler may fail (return a nonzero status) and be ignored by make. These failures, which are often due to files that were not found, are expected, and can safely be ignored. !

It is normal to have compiler warnings when compiling certain files. Unless you are a GCC developer, you can generally ignore these warnings unless they cause compilation to fail. !

On certain old systems, defining certain environment variables such as CC can interfere with the functioning of make. !

If you encounter seemingly strange errors when trying to build the compiler in a directory other than the source directory, it could be because you have previously configured the compiler in the source directory. Make sure you have done all the necessary preparations. !

If you build GCC on a BSD system using a directory stored in an old System V file system, problems may occur in running fixincludes if the System V file system doesn't support symbolic links. These problems result in a failure to fix the declaration of size_t in sys/types.h. If you find that size_t is a signed type and that type mismatches occur, this could be the cause. !

The solution is not to use such a directory for building GCC. !

When building from CVS or snapshots, or if you modify parser sources, you need the Bison parser generator installed. Any version 1.25 or later should work; older versions may also work. If you do not modify parser sources, releases contain the Bison-generated files and you do not need Bison installed to build them. !

When building from CVS or snapshots, or if you modify Texinfo documentation, you need version 4.1 or later of Texinfo installed if you want Info documentation to be regenerated. Releases contain Info documentation pre-built for the unmodified documentation in the release. !

Building a native compiler

!

For a native build issue the command make bootstrap. This will build the entire GCC system, which includes the following steps: !

!

If you are short on disk space you might consider make bootstrap-lean instead. This is identical to make bootstrap except that object files from the stage1 and stage2 of the 3-stage bootstrap of the compiler are deleted as soon as they are no longer needed. !

If you want to save additional space during the bootstrap and in the final installation as well, you can build the compiler binaries without debugging information as in the following example. This will save roughly 40% of disk space both for the bootstrap and the final installation. (Libraries will still contain debugging information.) ! 

          make CFLAGS='-O' LIBCFLAGS='-g -O2' \
!             LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
!
!

If you wish to use non-default GCC flags when compiling the stage2 and stage3 compilers, set BOOT_CFLAGS on the command line when doing make bootstrap. Non-default optimization flags are less well tested here than the default of -g -O2, but should still work. *************** around this, by choosing BOOT_CFLA *** 105,176 **** stage1 compiler that were miscompiled, or by using make bootstrap4 to increase the number of stages of bootstrap. !

If you used the flag --enable-languages=... to restrict the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, that re-defining LANGUAGES when calling make bootstrap does not work anymore! !

If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they always appear "different". If you encounter this problem, you will need to disable comparison in the Makefile.) !

Building a cross compiler

!

We recommend reading the crossgcc FAQ for information about building cross compilers. !

When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. !

To build a cross compiler, we first recommend building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. !

Assuming you have already installed a native copy of GCC and configured your cross compiler, issue the command make, which performs the following steps: !

!

Note that if an error occurs in any step the make process will exit. !

Building in parallel

!

If you have a multiprocessor system you can use make bootstrap MAKE="make -j 2" -j 2 or just make -j 2 bootstrap for GNU Make 3.79 and above instead of just make bootstrap when building GCC. You can use a bigger number instead of two if you like. In most cases, it won't help to use a number bigger than the number of processors in your machine. !

Building the Ada compiler

!

In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GNAT version 3.13 or later, or GCC version 3.1 or later), since the Ada front end is written in Ada (with some GNAT-specific extensions), and GNU make. !

However, you do not need a full installation of GNAT, just the GNAT binary gnat1, a copy of gnatbind, and a compiler driver which can deal with Ada input (by invoking the gnat1 binary). You can specify this compiler driver by setting the ADAC --- 107,178 ---- stage1 compiler that were miscompiled, or by using make bootstrap4 to increase the number of stages of bootstrap. !

If you used the flag --enable-languages=... to restrict the compilers to be built, only those you've actually enabled will be built. This will of course only build those runtime libraries, for which the particular compiler has been built. Please note, that re-defining LANGUAGES when calling make bootstrap does not work anymore! !

If the comparison of stage2 and stage3 fails, this normally indicates that the stage2 compiler has compiled GCC incorrectly, and is therefore a potentially serious bug which you should investigate and report. (On a few systems, meaningful comparison of object files is impossible; they always appear "different". If you encounter this problem, you will need to disable comparison in the Makefile.) !

Building a cross compiler

!

We recommend reading the crossgcc FAQ for information about building cross compilers. !

When building a cross compiler, it is not generally possible to do a 3-stage bootstrap of the compiler. This makes for an interesting problem as parts of GCC can only be built with GCC. !

To build a cross compiler, we first recommend building and installing a native compiler. You can then use the native GCC compiler to build the cross compiler. The installed native compiler needs to be GCC version 2.95 or later. !

Assuming you have already installed a native copy of GCC and configured your cross compiler, issue the command make, which performs the following steps: !

!

Note that if an error occurs in any step the make process will exit. !

Building in parallel

!

If you have a multiprocessor system you can use make bootstrap MAKE="make -j 2" -j 2 or just make -j 2 bootstrap for GNU Make 3.79 and above instead of just make bootstrap when building GCC. You can use a bigger number instead of two if you like. In most cases, it won't help to use a number bigger than the number of processors in your machine. !

Building the Ada compiler

!

In order to build GNAT, the Ada compiler, you need a working GNAT compiler (GNAT version 3.13 or later, or GCC version 3.1 or later), since the Ada front end is written in Ada (with some GNAT-specific extensions), and GNU make. !

However, you do not need a full installation of GNAT, just the GNAT binary gnat1, a copy of gnatbind, and a compiler driver which can deal with Ada input (by invoking the gnat1 binary). You can specify this compiler driver by setting the ADAC *************** and has a sufficiently recent version; i *** 183,224 **** installed, the build will fail unless --enable-languages is used to disable building the Ada front end. !

Additional build tools (such as gnatmake) or a working GNAT run-time library installation are usually not required. However, if you want to bootstrap the compiler using a minimal version of GNAT, you have to issue the following commands before invoking make bootstrap (this assumes that you start with an unmodified and consistent source distribution): ! 

    cd srcdir/gcc/ada
!     touch treeprs.ads [es]info.h nmake.ad[bs]
!
!

At the moment, the GNAT library and several tools for GNAT are not built by make bootstrap. You have to invoke ! make gnatlib_and_tools in the objdir/gcc subdirectory before proceeding with the next steps. !

For example, you can build a native Ada compiler by issuing the following commands (assuming make is GNU make): ! 

    cd objdir
!     srcdir/configure --enable-languages=c,ada
!     cd srcdir/gcc/ada
!     touch treeprs.ads [es]info.h nmake.ad[bs]
!     cd objdir
!     make bootstrap
!     cd gcc
!     make gnatlib_and_tools
!     cd ..
!
!

Currently, when compiling the Ada front end, you cannot use the parallel build feature described in the previous section. !

Return to the GCC Installation page ! --- 185,226 ---- installed, the build will fail unless --enable-languages is used to disable building the Ada front end. !

Additional build tools (such as gnatmake) or a working GNAT run-time library installation are usually not required. However, if you want to bootstrap the compiler using a minimal version of GNAT, you have to issue the following commands before invoking make bootstrap (this assumes that you start with an unmodified and consistent source distribution): ! 

         cd srcdir/gcc/ada
!          touch treeprs.ads [es]info.h nmake.ad[bs]
!
!

At the moment, the GNAT library and several tools for GNAT are not built by make bootstrap. You have to invoke ! make gnatlib_and_tools in the objdir/gcc subdirectory before proceeding with the next steps. !

For example, you can build a native Ada compiler by issuing the following commands (assuming make is GNU make): ! 

         cd objdir
!          srcdir/configure --enable-languages=c,ada
!          cd srcdir/gcc/ada
!          touch treeprs.ads [es]info.h nmake.ad[bs]
!          cd objdir
!          make bootstrap
!          cd gcc
!          make gnatlib_and_tools
!          cd ..
!
!

Currently, when compiling the Ada front end, you cannot use the parallel build feature described in the previous section. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/configure.html gcc-3.2.3/INSTALL/configure.html *** gcc-3.2.2/INSTALL/configure.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/configure.html Tue Apr 22 06:56:33 2003 *************** *** 1,30 **** ! Installing GCC: Configuration ! ! ! ! ! !

L

ike most GNU software, GCC must be configured before it can be built. This document describes the recommended configuration procedure for both native and cross targets. !

We use srcdir to refer to the toplevel source directory for GCC; we use objdir to refer to the toplevel build/object directory. !

If you obtained the sources via CVS, srcdir must refer to the top gcc directory, the one where the MAINTAINERS can be found, and not its gcc subdirectory, otherwise the build will fail. !

First, we highly recommend that GCC be built into a separate directory than the sources which does not reside within the source tree. This is how we generally build GCC; building where srcdir == objdir should still work, but doesn't get extensive testing; building where objdir is a subdirectory of srcdir is unsupported. !

If you have previously built GCC in the same directory for a different target machine, do make distclean to delete all files that might be invalid. One of the files this deletes is Makefile; if make distclean complains that Makefile --- 1,32 ---- ! ! Installing GCC: Configuration ! ! ! ! ! !

Installing GCC: Configuration

! Like most GNU software, GCC must be configured before it can be built. This document describes the recommended configuration procedure for both native and cross targets. !

We use srcdir to refer to the toplevel source directory for GCC; we use objdir to refer to the toplevel build/object directory. !

If you obtained the sources via CVS, srcdir must refer to the top gcc directory, the one where the MAINTAINERS can be found, and not its gcc subdirectory, otherwise the build will fail. !

First, we highly recommend that GCC be built into a separate directory than the sources which does not reside within the source tree. This is how we generally build GCC; building where srcdir == objdir should still work, but doesn't get extensive testing; building where objdir is a subdirectory of srcdir is unsupported. !

If you have previously built GCC in the same directory for a different target machine, do make distclean to delete all files that might be invalid. One of the files this deletes is Makefile; if make distclean complains that Makefile *************** clean. However, with the recommended me *** 33,142 **** objdir, you should simply use a different objdir for each target. !

Second, when configuring a native system, either cc or gcc must be in your path or you must set CC in your environment before running configure. Otherwise the configuration scripts may fail. !

Note that the bootstrap compiler and the resulting GCC must be link compatible, else the bootstrap will fail with linker errors about incompatible object file formats. Several multilibed targets are affected by this requirement, see host/target specific installation notes. !

To configure GCC: ! 

   % mkdir objdir
!    % cd objdir
!    % srcdir/configure [options] [target]
!
!

Target specification

!
  • GCC has code to correctly determine the correct value for target for nearly all native systems. Therefore, we highly recommend you not provide a configure target when configuring a native compiler. !
  • target must be specified as --target=target when configuring a cross compiler; examples of valid targets would be i960-rtems, m68k-coff, sh-elf, etc. !
  • Specifying just target instead of --target=target implies that the host defaults to target.
!

Options specification

!

Use options to override several configure time options for GCC. A list of supported options follows; configure --help may list other options, but those not listed below may not work and should not normally be used. !

!
--prefix=dirname !
Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to /usr/local. !

We highly recommend against dirname being the same or a subdirectory of objdir or vice versa. !

These additional options control where certain parts of the distribution are installed. Normally you should not need to use these options. !

!
--exec-prefix=dirname !
Specify the toplevel installation directory for architecture-dependent ! files. The default is prefix. !
--bindir=dirname !
Specify the installation directory for the executables called by users (such as gcc and g++). The default is ! exec-prefix/bin. !
--libdir=dirname !
Specify the installation directory for object code libraries and ! internal parts of GCC. The default is exec-prefix/lib. !
--with-slibdir=dirname !
Specify the installation directory for the shared libgcc library. The ! default is libdir. !
--infodir=dirname !
Specify the installation directory for documentation in info format. ! The default is prefix/info. !
--mandir=dirname !
Specify the installation directory for manual pages. The default is ! prefix/man. (Note that the manual pages are only extracts from the full GCC manuals, which are provided in Texinfo format. The g77 manpage is unmaintained and may be out of date; the others are derived by an automatic conversion process from parts of the full manual.) !
--with-gxx-include-dir=dirname !
Specify the installation directory for G++ header files. The default is ! prefix/include/g++-v3. !
!
--program-prefix=prefix !
GCC supports some transformations of the names of its programs when installing them. This option prepends prefix to the names of programs to install in bindir (see above). For example, specifying --program-prefix=foo- would result in gcc being installed as /usr/local/bin/foo-gcc. !
--program-suffix=suffix !
Appends suffix to the names of programs to install in bindir (see above). For example, specifying --program-suffix=-3.1 would result in gcc being installed as /usr/local/bin/gcc-3.1. !
--program-transform-name=pattern !
Applies the sed script pattern to be applied to the names of programs to install in bindir (see above). pattern has to consist of one or more basic sed editing commands, separated by semicolons. For example, if you want the gcc program name to be --- 35,144 ---- objdir, you should simply use a different objdir for each target. !

Second, when configuring a native system, either cc or gcc must be in your path or you must set CC in your environment before running configure. Otherwise the configuration scripts may fail. !

Note that the bootstrap compiler and the resulting GCC must be link compatible, else the bootstrap will fail with linker errors about incompatible object file formats. Several multilibed targets are affected by this requirement, see host/target specific installation notes. !

To configure GCC: ! 

        % mkdir objdir
!         % cd objdir
!         % srcdir/configure [options] [target]
!
!

Target specification

!
  • GCC has code to correctly determine the correct value for target for nearly all native systems. Therefore, we highly recommend you not provide a configure target when configuring a native compiler. !
  • target must be specified as --target=target when configuring a cross compiler; examples of valid targets would be i960-rtems, m68k-coff, sh-elf, etc. !
  • Specifying just target instead of --target=target implies that the host defaults to target.
!

Options specification

!

Use options to override several configure time options for GCC. A list of supported options follows; configure --help may list other options, but those not listed below may not work and should not normally be used. !

!
--prefix=dirname !
Specify the toplevel installation directory. This is the recommended way to install the tools into a directory other than the default. The toplevel installation directory defaults to /usr/local. !

We highly recommend against dirname being the same or a subdirectory of objdir or vice versa. !

These additional options control where certain parts of the distribution are installed. Normally you should not need to use these options. !

!
--exec-prefix=dirname !
Specify the toplevel installation directory for architecture-dependent ! files. The default is prefix. !
--bindir=dirname !
Specify the installation directory for the executables called by users (such as gcc and g++). The default is ! exec-prefix/bin. !
--libdir=dirname !
Specify the installation directory for object code libraries and ! internal parts of GCC. The default is exec-prefix/lib. !
--with-slibdir=dirname !
Specify the installation directory for the shared libgcc library. The ! default is libdir. !
--infodir=dirname !
Specify the installation directory for documentation in info format. ! The default is prefix/info. !
--mandir=dirname !
Specify the installation directory for manual pages. The default is ! prefix/man. (Note that the manual pages are only extracts from the full GCC manuals, which are provided in Texinfo format. The g77 manpage is unmaintained and may be out of date; the others are derived by an automatic conversion process from parts of the full manual.) !
--with-gxx-include-dir=dirname !
Specify the installation directory for G++ header files. The default is ! prefix/include/g++-v3. !
!
--program-prefix=prefix !
GCC supports some transformations of the names of its programs when installing them. This option prepends prefix to the names of programs to install in bindir (see above). For example, specifying --program-prefix=foo- would result in gcc being installed as /usr/local/bin/foo-gcc. !
--program-suffix=suffix !
Appends suffix to the names of programs to install in bindir (see above). For example, specifying --program-suffix=-3.1 would result in gcc being installed as /usr/local/bin/gcc-3.1. !
--program-transform-name=pattern !
Applies the sed script pattern to be applied to the names of programs to install in bindir (see above). pattern has to consist of one or more basic sed editing commands, separated by semicolons. For example, if you want the gcc program name to be *************** you could use the pattern *** 147,162 **** --program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/' to achieve this effect. !

All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, prefix (and suffix) are prepended (appended) before further transformations can happen with a special transformation script pattern. !

As currently implemented, these options only take effect for native builds; cross compiler binaries' names are not transformed even when a transformation is explicitly asked for by one of these options. !

For native builds, some of the installed programs are also installed with the target alias in front of their name, as in i686-pc-linux-gnu-gcc. All of the above transformations happen before the target alias is prepended to the name - so, specifying --- 149,164 ---- --program-transform-name='s/^gcc$/myowngcc/; s/^g++$/gspecial++/' to achieve this effect. !

All three options can be combined and used together, resulting in more complex conversion patterns. As a basic rule, prefix (and suffix) are prepended (appended) before further transformations can happen with a special transformation script pattern. !

As currently implemented, these options only take effect for native builds; cross compiler binaries' names are not transformed even when a transformation is explicitly asked for by one of these options. !

For native builds, some of the installed programs are also installed with the target alias in front of their name, as in i686-pc-linux-gnu-gcc. All of the above transformations happen before the target alias is prepended to the name - so, specifying *************** before the target alias is prepended to *** 164,196 **** resulting binary would be installed as /usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1. !

As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. !

--with-local-prefix=dirname !
Specify the installation directory for local include files. The default is /usr/local. Specify this option if you want the compiler to ! search directory dirname/include for locally installed header files instead of /usr/local/include. !

You should specify --with-local-prefix only if your site has a different convention (not /usr/local) for where to put site-specific files. !

The default value for --with-local-prefix is /usr/local regardless of the value of --prefix. Specifying --prefix has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. !

The purpose of --prefix is to specify where to install GCC. The local header files in /usr/local/include--if you put any in that directory--are not part of GCC. They are part of other programs--perhaps many others. (GCC installs its own header files in another directory which is based on the --prefix value.) !

Both the local-prefix include directory and the GCC-prefix include directory are part of GCC's "system include" directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The --- 166,198 ---- resulting binary would be installed as /usr/local/bin/i686-pc-linux-gnu-foo-gcc-3.1. !

As a last shortcoming, none of the installed Ada programs are transformed yet, which will be fixed in some time. !

--with-local-prefix=dirname !
Specify the installation directory for local include files. The default is /usr/local. Specify this option if you want the compiler to ! search directory dirname/include for locally installed header files instead of /usr/local/include. !

You should specify --with-local-prefix only if your site has a different convention (not /usr/local) for where to put site-specific files. !

The default value for --with-local-prefix is /usr/local regardless of the value of --prefix. Specifying --prefix has no effect on which directory GCC searches for local header files. This may seem counterintuitive, but actually it is logical. !

The purpose of --prefix is to specify where to install GCC. The local header files in /usr/local/include--if you put any in that directory--are not part of GCC. They are part of other programs--perhaps many others. (GCC installs its own header files in another directory which is based on the --prefix value.) !

Both the local-prefix include directory and the GCC-prefix include directory are part of GCC's "system include" directories. Although these two directories are not fixed, they need to be searched in the proper order for the correct processing of the include_next directive. The *************** local-prefix include directory is search *** 198,204 **** include directory. Another characteristic of system include directories is that pedantic warnings are turned off for headers in these directories. !

Some autoconf macros add -I directory options to the compiler command line, to ensure that directories containing installed packages' headers are searched. When directory is one of GCC's system include directories, GCC will ignore the option so that system --- 200,206 ---- include directory. Another characteristic of system include directories is that pedantic warnings are turned off for headers in these directories. !

Some autoconf macros add -I directory options to the compiler command line, to ensure that directories containing installed packages' headers are searched. When directory is one of GCC's system include directories, GCC will ignore the option so that system *************** directories continue to be processed in *** 206,219 **** may result in a search order different from what was specified but the directory will still be searched. !

GCC automatically searches for ordinary libraries using GCC_EXEC_PREFIX. Thus, when the same installation prefix is used for both GCC and packages, GCC will automatically search for both headers and libraries. This provides a configuration that is easy to use. GCC behaves in a manner similar to that when it is installed as a system compiler in /usr. !

Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the --program-prefix, --program-suffix and --program-transform-name options to install multiple versions --- 208,221 ---- may result in a search order different from what was specified but the directory will still be searched. !

GCC automatically searches for ordinary libraries using GCC_EXEC_PREFIX. Thus, when the same installation prefix is used for both GCC and packages, GCC will automatically search for both headers and libraries. This provides a configuration that is easy to use. GCC behaves in a manner similar to that when it is installed as a system compiler in /usr. !

Sites that need to install multiple versions of GCC may not want to use the above simple configuration. It is possible to use the --program-prefix, --program-suffix and --program-transform-name options to install multiple versions *************** site-specific files for each version. I *** 223,252 **** users to specify explicitly the location of local site libraries (e.g., with LIBRARY_PATH). !

The same value can be used for both --with-local-prefix and --prefix provided it is not /usr. This can be used to avoid the default search of /usr/local/include. !

Do not specify /usr as the --with-local-prefix! The directory you use for --with-local-prefix must not contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the header file corrections made by the fixincludes script. !

Indications are that people who use this option use it based on mistaken ideas of what it is for. People use it as if it specified where to install part of GCC. Perhaps they make this assumption because installing GCC creates the directory. !

--enable-shared[=package[,...]] !
Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries, except for libobjc which is built as a static library only by default. !

If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only static libraries will be built. Package names currently recognized in the GCC tree are libgcc (also known as gcc), libstdc++ (not --- 225,254 ---- users to specify explicitly the location of local site libraries (e.g., with LIBRARY_PATH). !

The same value can be used for both --with-local-prefix and --prefix provided it is not /usr. This can be used to avoid the default search of /usr/local/include. !

Do not specify /usr as the --with-local-prefix! The directory you use for --with-local-prefix must not contain any of the system's standard header files. If it did contain them, certain programs would be miscompiled (including GNU Emacs, on certain targets), because this would override and nullify the header file corrections made by the fixincludes script. !

Indications are that people who use this option use it based on mistaken ideas of what it is for. People use it as if it specified where to install part of GCC. Perhaps they make this assumption because installing GCC creates the directory. !

--enable-shared[=package[,...]] !
Build shared versions of libraries, if shared libraries are supported on the target platform. Unlike GCC 2.95.x and earlier, shared libraries are enabled by default on all platforms that support shared libraries, except for libobjc which is built as a static library only by default. !

If a list of packages is given as an argument, build shared libraries only for the listed packages. For other packages, only static libraries will be built. Package names currently recognized in the GCC tree are libgcc (also known as gcc), libstdc++ (not *************** any name, so, if you list package names *** 256,464 **** you will only get static Objective-C libraries. libf2c and libiberty do not support shared libraries at all. !

Use --disable-shared to build only static libraries. Note that --disable-shared does not accept a list of package names as argument, only --enable-shared does. !

--with-gnu-as !
Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify the rules to find an assembler and will result in confusion if found assembler is not actually the GNU assembler. (Confusion will also result if the compiler finds the GNU assembler but has not been configured with --with-gnu-as.) If you have more than one assembler installed on your system, you may want to use this option in ! connection with --with-as=pathname. !

The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, --with-gnu-as has no effect. !

    !
  • hppa1.0-any-any !
  • hppa1.1-any-any !
  • i386-any-sysv !
  • i386-any-isc !
  • i860-any-bsd
  • m68k-bull-sysv
  • m68k-hp-hpux
  • m68k-sony-bsd
  • m68k-altos-sysv
  • m68000-hp-hpux
  • m68000-att-sysv !
  • any-lynx-lynxos !
  • mips-any
!

On the systems listed above (except for the HP-PA, for ISC on the 386, and for mips-sgi-irix5.*), if you use the GNU assembler, you should also use the GNU linker (and specify --with-gnu-ld). !

--with-as=pathname !
Specify that the compiler should use the assembler pointed to by pathname, rather than the one found by the standard rules to find an assembler, which are: !
  • Check the ! exec_prefix/lib/gcc-lib/target/version directory, where exec_prefix defaults to prefix which defaults to /usr/local unless overridden by the ! --prefix=pathname switch described above. target is the target system triple, such as sparc-sun-solaris2.7, and version denotes the GCC version, such as 3.0.
  • Check operating system specific directories (e.g. /usr/ccs/bin on Sun Solaris 2).
! Note that these rules do not check for the value of PATH. You may want to use --with-as if no assembler is installed in the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. !
--with-gnu-ld !
Same as --with-gnu-as but for linker. !
--with-ld=pathname !
Same as --with-as, but for the linker. !
--with-stabs !
Specify that stabs debugging information should be used instead of whatever format the host normally uses. Normally GCC uses the same debug format as the host system. !

On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ECOFF debug format cannot fully handle languages other than C. BSD stabs format can handle other languages, but it only works with the GNU debugger GDB. !

Normally, GCC uses the ECOFF debugging format by default; if you prefer BSD stabs, specify --with-stabs when you configure GCC. !

No matter which default you choose when you configure GCC, the user can use the -gcoff and -gstabs+ options to specify explicitly the debug format for a particular compilation. !

--with-stabs is meaningful on the ISC system on the 386, also, if --with-gas is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. !

--with-stabs is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. !

--disable-multilib !
Specify that multiple target libraries to support different target variants, calling conventions, etc should not be built. The default is to build a predefined set of them. !

Some targets provide finer-grained control over which multilibs are built (e.g., --disable-softfloat): !

arc-*-elf* !
biendian. !
arm-*-* !
fpu, 26bit, underscore, interwork, biendian, nofmult. !
m68*-*-* !
softfloat, m68881, m68000, m68020. !
mips*-*-* !
single-float, biendian, softfloat. !
powerpc*-*-*, rs6000*-*-* !
aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. !
!
--enable-threads !
Specify that the target supports threads. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. On some systems, this is the default. !

In general, the best (and, in many cases, the only known) threading model available will be configured for use. Beware that on some systems, gcc has not been taught what threading models are generally available for the system. In this case, --enable-threads is an alias for --enable-threads=single. !

--disable-threads !
Specify that threading support should be disabled for the system. This is an alias for --enable-threads=single. !
--enable-threads=lib !
Specify that lib is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for lib are: !
aix !
AIX thread support.
dce !
DCE thread support.
mach !
Generic MACH thread support, known to work on NeXTSTEP. (Please note that the file needed to support this configuration, gthr-mach.h, is missing and thus this setting will cause a known bootstrap failure.)
no !
This is an alias for single.
posix !
Generic POSIX thread support.
pthreads !
Same as posix on arm*-*-linux*, *-*-chorusos* and *-*-freebsd* only. A future release of gcc might remove this alias or extend it to all platforms.
rtems !
RTEMS thread support.
single !
Disable thread support, should work for all platforms.
solaris !
Sun Solaris 2 thread support.
vxworks !
VxWorks thread support.
win32 !
Microsoft Win32 API thread support.
!
--with-cpu=cpu !
Specify which cpu variant the compiler should generate code for by default. This is currently only supported on the some ports, specifically arm, powerpc, and SPARC. If configure does not recognize the model name (e.g. arm700, 603e, or ultrasparc) you provide, please check the configure script for a complete list of supported models. !
--enable-altivec !
Specify that the target supports AltiVec vector enhancements. This option will adjust the ABI for AltiVec enhancements, as well as generate AltiVec code when appropriate. This option is only available for PowerPC systems. !
--enable-target-optspace !
Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. !
--disable-cpp !
Specify that a user visible cpp program should not be installed. !
--with-cpp-install-dir=dirname !
Specify that the user visible cpp program should be installed ! in prefix/dirname/cpp, in addition to bindir. !
--enable-maintainer-mode !
The build rules that regenerate the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the --- 258,466 ---- you will only get static Objective-C libraries. libf2c and libiberty do not support shared libraries at all. !

Use --disable-shared to build only static libraries. Note that --disable-shared does not accept a list of package names as argument, only --enable-shared does. !

--with-gnu-as !
Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify the rules to find an assembler and will result in confusion if found assembler is not actually the GNU assembler. (Confusion will also result if the compiler finds the GNU assembler but has not been configured with --with-gnu-as.) If you have more than one assembler installed on your system, you may want to use this option in ! connection with --with-as=pathname. !

The following systems are the only ones where it makes a difference whether you use the GNU assembler. On any other system, --with-gnu-as has no effect. !

    !
  • hppa1.0-any-any !
  • hppa1.1-any-any !
  • i386-any-sysv !
  • i386-any-isc !
  • i860-any-bsd
  • m68k-bull-sysv
  • m68k-hp-hpux
  • m68k-sony-bsd
  • m68k-altos-sysv
  • m68000-hp-hpux
  • m68000-att-sysv !
  • any-lynx-lynxos !
  • mips-any
!

On the systems listed above (except for the HP-PA, for ISC on the 386, and for mips-sgi-irix5.*), if you use the GNU assembler, you should also use the GNU linker (and specify --with-gnu-ld). !

--with-as=pathname !
Specify that the compiler should use the assembler pointed to by pathname, rather than the one found by the standard rules to find an assembler, which are: !
  • Check the ! exec_prefix/lib/gcc-lib/target/version directory, where exec_prefix defaults to prefix which defaults to /usr/local unless overridden by the ! --prefix=pathname switch described above. target is the target system triple, such as sparc-sun-solaris2.7, and version denotes the GCC version, such as 3.0.
  • Check operating system specific directories (e.g. /usr/ccs/bin on Sun Solaris 2).
! Note that these rules do not check for the value of PATH. You may want to use --with-as if no assembler is installed in the directories listed above, or if you have multiple assemblers installed and want to choose one that is not found by the above rules. !
--with-gnu-ld !
Same as --with-gnu-as but for linker. !
--with-ld=pathname !
Same as --with-as, but for the linker. !
--with-stabs !
Specify that stabs debugging information should be used instead of whatever format the host normally uses. Normally GCC uses the same debug format as the host system. !

On MIPS based systems and on Alphas, you must specify whether you want GCC to create the normal ECOFF debugging format, or to use BSD-style stabs passed through the ECOFF symbol table. The normal ECOFF debug format cannot fully handle languages other than C. BSD stabs format can handle other languages, but it only works with the GNU debugger GDB. !

Normally, GCC uses the ECOFF debugging format by default; if you prefer BSD stabs, specify --with-stabs when you configure GCC. !

No matter which default you choose when you configure GCC, the user can use the -gcoff and -gstabs+ options to specify explicitly the debug format for a particular compilation. !

--with-stabs is meaningful on the ISC system on the 386, also, if --with-gas is used. It selects use of stabs debugging information embedded in COFF output. This kind of debugging information supports C++ well; ordinary COFF debugging information does not. !

--with-stabs is also meaningful on 386 systems running SVR4. It selects use of stabs debugging information embedded in ELF output. The C++ compiler currently (2.6.0) does not support the DWARF debugging information normally used on 386 SVR4 platforms; stabs provide a workable alternative. This requires gas and gdb, as the normal SVR4 tools can not generate or interpret stabs. !

--disable-multilib !
Specify that multiple target libraries to support different target variants, calling conventions, etc should not be built. The default is to build a predefined set of them. !

Some targets provide finer-grained control over which multilibs are built (e.g., --disable-softfloat): !

arc-*-elf* !
biendian. !
arm-*-* !
fpu, 26bit, underscore, interwork, biendian, nofmult. !
m68*-*-* !
softfloat, m68881, m68000, m68020. !
mips*-*-* !
single-float, biendian, softfloat. !
powerpc*-*-*, rs6000*-*-* !
aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian, sysv, aix. !
!
--enable-threads !
Specify that the target supports threads. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. On some systems, this is the default. !

In general, the best (and, in many cases, the only known) threading model available will be configured for use. Beware that on some systems, gcc has not been taught what threading models are generally available for the system. In this case, --enable-threads is an alias for --enable-threads=single. !

--disable-threads !
Specify that threading support should be disabled for the system. This is an alias for --enable-threads=single. !
--enable-threads=lib !
Specify that lib is the thread support library. This affects the Objective-C compiler and runtime library, and exception handling for other languages like C++ and Java. The possibilities for lib are: !
aix !
AIX thread support.
dce !
DCE thread support.
mach !
Generic MACH thread support, known to work on NeXTSTEP. (Please note that the file needed to support this configuration, gthr-mach.h, is missing and thus this setting will cause a known bootstrap failure.)
no !
This is an alias for single.
posix !
Generic POSIX thread support.
pthreads !
Same as posix on arm*-*-linux*, *-*-chorusos* and *-*-freebsd* only. A future release of gcc might remove this alias or extend it to all platforms.
rtems !
RTEMS thread support.
single !
Disable thread support, should work for all platforms.
solaris !
Sun Solaris 2 thread support.
vxworks !
VxWorks thread support.
win32 !
Microsoft Win32 API thread support.
!
--with-cpu=cpu !
Specify which cpu variant the compiler should generate code for by default. This is currently only supported on the some ports, specifically arm, powerpc, and SPARC. If configure does not recognize the model name (e.g. arm700, 603e, or ultrasparc) you provide, please check the configure script for a complete list of supported models. !
--enable-altivec !
Specify that the target supports AltiVec vector enhancements. This option will adjust the ABI for AltiVec enhancements, as well as generate AltiVec code when appropriate. This option is only available for PowerPC systems. !
--enable-target-optspace !
Specify that target libraries should be optimized for code space instead of code speed. This is the default for the m32r platform. !
--disable-cpp !
Specify that a user visible cpp program should not be installed. !
--with-cpp-install-dir=dirname !
Specify that the user visible cpp program should be installed ! in prefix/dirname/cpp, in addition to bindir. !
--enable-maintainer-mode !
The build rules that regenerate the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the *************** catalog, configuring with --enable *** 466,491 **** this. Note that you need a recent version of the gettext tools to do so. !
--enable-version-specific-runtime-libs !
Specify that runtime libraries should be installed in the compiler specific ! subdirectory (libsubdir) rather than the usual places. In addition, libstdc++'s include files will be installed in ! libsubdir/include/g++ unless you overruled it by using ! --with-gxx-include-dir=dirname. Using this option is particularly useful if you intend to use several versions of GCC in parallel. This is currently supported by libf2c and libstdc++, and is the default for libobjc which cannot be changed in this case. !
--enable-languages=lang1,lang2,... !
Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for langN you can issue the following command in the gcc directory of your GCC source tree:
! 
grep language= */config-lang.in
!
! Currently, you can use any of the following: ada, c, c++, f77, java, objc. Building the Ada compiler has special requirements, see below.
If you do not pass this flag, all languages available in the gcc --- 468,493 ---- this. Note that you need a recent version of the gettext tools to do so. !
--enable-version-specific-runtime-libs !
Specify that runtime libraries should be installed in the compiler specific ! subdirectory (libsubdir) rather than the usual places. In addition, libstdc++'s include files will be installed in ! libsubdir/include/g++ unless you overruled it by using ! --with-gxx-include-dir=dirname. Using this option is particularly useful if you intend to use several versions of GCC in parallel. This is currently supported by libf2c and libstdc++, and is the default for libobjc which cannot be changed in this case. !
--enable-languages=lang1,lang2,... !
Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for langN you can issue the following command in the gcc directory of your GCC source tree:
! 
          grep language= */config-lang.in
!
! Currently, you can use any of the following: ada, c, c++, f77, java, objc. Building the Ada compiler has special requirements, see below.
If you do not pass this flag, all languages available in the gcc *************** sub-tree will be configured. Re-definin *** 493,500 **** make bootstrap does not work anymore, as those language sub-directories might not have been configured! !
--disable-libgcj !
Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular --- 495,502 ---- make bootstrap does not work anymore, as those language sub-directories might not have been configured! !
--disable-libgcj !
Specify that the run-time libraries used by GCJ should not be built. This is useful in case you intend to use GCJ with some other run-time, or you're going to install it separately, or it just happens not to build on your particular *************** may need to port it; in this case, befor *** 505,539 **** configure.in so that libgcj is enabled by default on this platform, you may use --enable-libgcj to override the default. !
--with-dwarf2 !
Specify that the compiler should use DWARF 2 debugging information as the default. !
--enable-win32-registry !
--enable-win32-registry=key !
--disable-win32-registry !
The --enable-win32-registry option enables Windows-hosted GCC to look up installations paths in the registry using the following key: ! 
HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
!
!

key defaults to GCC version number, and can be overridden by the ! --enable-win32-registry=key option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled by default, and can be disabled by --disable-win32-registry option. This option has no effect on the other hosts. !

--nfp !
Specify that the machine does not have a floating point unit. This ! option only applies to m68k-sun-sunosn and m68k-isi-bsd. On any other system, --nfp has no effect. !
--enable-checking !
--enable-checking=list !
When you specify this option, the compiler is built to perform checking of tree node types when referencing fields of that node, and some other internal consistency checks. This does not change the generated code, but adds error checking within the compiler. This will slow down the --- 507,541 ---- configure.in so that libgcj is enabled by default on this platform, you may use --enable-libgcj to override the default. !
--with-dwarf2 !
Specify that the compiler should use DWARF 2 debugging information as the default. !
--enable-win32-registry !
--enable-win32-registry=key !
--disable-win32-registry !
The --enable-win32-registry option enables Windows-hosted GCC to look up installations paths in the registry using the following key: ! 
          HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\key
!
!

key defaults to GCC version number, and can be overridden by the ! --enable-win32-registry=key option. Vendors and distributors who use custom installers are encouraged to provide a different key, perhaps one comprised of vendor name and GCC version number, to avoid conflict with existing installations. This feature is enabled by default, and can be disabled by --disable-win32-registry option. This option has no effect on the other hosts. !

--nfp !
Specify that the machine does not have a floating point unit. This ! option only applies to m68k-sun-sunosn and m68k-isi-bsd. On any other system, --nfp has no effect. !
--enable-checking !
--enable-checking=list !
When you specify this option, the compiler is built to perform checking of tree node types when referencing fields of that node, and some other internal consistency checks. This does not change the generated code, but adds error checking within the compiler. This will slow down the *************** specifying list; the categori *** 545,615 **** default when list is not specified is misc,tree,gc; the checks rtl and gcac are very expensive. !
--enable-nls !
--disable-nls !
The --enable-nls option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a canadian cross build. The --disable-nls option disables NLS. !
--with-included-gettext !
If NLS is enabled, the --with-included-gettext option causes the build procedure to prefer its copy of GNU gettext. !
--with-catgets !
If NLS is enabled, and if the host lacks gettext but has the inferior catgets interface, the GCC build procedure normally ignores catgets and instead uses GCC's copy of the GNU gettext library. The --with-catgets option causes the build procedure to use the host's catgets in this situation. !
--with-libiconv-prefix=dir !
Search for libiconv header files in dir/include and ! libiconv library files in dir/lib. !
--with-system-zlib !
Use installed zlib rather than that included with GCC. This option only applies if the Java front end is being built. !
--enable-obsolete !
Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. !

All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port.

!

Some options which only apply to building cross compilers: !

!
--with-headers=dir !
Specifies a directory which has target include files. This option is required when building a cross ! compiler, if prefix/target/sys-include doesn't pre-exist. These include files will be copied into the gcc install directory. fixincludes will be run on these files to make them compatible with GCC. !
--with-libs=``dir1 dir2 ... dirN'' !
Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the gcc install directory.
--with-newlib !
Specifies that newlib is being used as the target C library. This causes __eprintf to be omitted from libgcc.a on the assumption that it will be provided by newlib.
!

Note that each --enable option has a corresponding --disable option and that each --with option has a corresponding --without option. !

Return to the GCC Installation page ! --- 547,617 ---- default when list is not specified is misc,tree,gc; the checks rtl and gcac are very expensive. !

--enable-nls !
--disable-nls !
The --enable-nls option enables Native Language Support (NLS), which lets GCC output diagnostics in languages other than American English. Native Language Support is enabled by default if not doing a canadian cross build. The --disable-nls option disables NLS. !
--with-included-gettext !
If NLS is enabled, the --with-included-gettext option causes the build procedure to prefer its copy of GNU gettext. !
--with-catgets !
If NLS is enabled, and if the host lacks gettext but has the inferior catgets interface, the GCC build procedure normally ignores catgets and instead uses GCC's copy of the GNU gettext library. The --with-catgets option causes the build procedure to use the host's catgets in this situation. !
--with-libiconv-prefix=dir !
Search for libiconv header files in dir/include and ! libiconv library files in dir/lib. !
--with-system-zlib !
Use installed zlib rather than that included with GCC. This option only applies if the Java front end is being built. !
--enable-obsolete !
Enable configuration for an obsoleted system. If you attempt to configure GCC for a system (build, host, or target) which has been obsoleted, and you do not specify this flag, configure will halt with an error message. !

All support for systems which have been obsoleted in one release of GCC is removed entirely in the next major release, unless someone steps forward to maintain the port.

!

Some options which only apply to building cross compilers: !

!
--with-headers=dir !
Specifies a directory which has target include files. This option is required when building a cross ! compiler, if prefix/target/sys-include doesn't pre-exist. These include files will be copied into the gcc install directory. fixincludes will be run on these files to make them compatible with GCC. !
--with-libs=``dir1 dir2 ... dirN'' !
Specifies a list of directories which contain the target runtime libraries. These libraries will be copied into the gcc install directory.
--with-newlib !
Specifies that newlib is being used as the target C library. This causes __eprintf to be omitted from libgcc.a on the assumption that it will be provided by newlib.
!

Note that each --enable option has a corresponding --disable option and that each --with option has a corresponding --without option. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/download.html gcc-3.2.3/INSTALL/download.html *** gcc-3.2.2/INSTALL/download.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/download.html Tue Apr 22 06:56:33 2003 *************** *** 1,45 **** ! Downloading GCC ! ! ! ! ! !

G

CC is distributed via CVS and FTP tarballs compressed with gzip or bzip2. It is possible to download a full distribution or specific components. !

Please refer to our releases web page for information on how to obtain GCC. !

The full distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in case of GCC 3.1 and later) compilers. The full distribution also includes runtime libraries for C++, Objective-C, Fortran, and Java. In GCC 3.0 and later versions, GNU compiler testsuites are also included in the full distribution. !

If you choose to download specific components, you must download the core GCC distribution plus any language specific distributions you wish to use. The core distribution includes the C language front end as well as the shared components. Each language has a tarball which includes the language front end as well as the language runtime (when appropriate). !

Unpack the core distribution as well as any language specific distributions in the same directory. !

If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler (bfd, binutils, gas, gprof, ld, ! opcodes, ...) to the directory containing the GCC sources. !

Return to the GCC Installation page ! --- 1,47 ---- ! ! Downloading GCC ! ! ! ! ! !

Downloading GCC

! GCC is distributed via CVS and FTP tarballs compressed with gzip or bzip2. It is possible to download a full distribution or specific components. !

Please refer to our releases web page for information on how to obtain GCC. !

The full distribution includes the C, C++, Objective-C, Fortran, Java, and Ada (in case of GCC 3.1 and later) compilers. The full distribution also includes runtime libraries for C++, Objective-C, Fortran, and Java. In GCC 3.0 and later versions, GNU compiler testsuites are also included in the full distribution. !

If you choose to download specific components, you must download the core GCC distribution plus any language specific distributions you wish to use. The core distribution includes the C language front end as well as the shared components. Each language has a tarball which includes the language front end as well as the language runtime (when appropriate). !

Unpack the core distribution as well as any language specific distributions in the same directory. !

If you also intend to build binutils (either to upgrade an existing installation or for use in place of the corresponding tools of your OS), unpack the binutils distribution either in the same directory or a separate one. In the latter case, add symbolic links to any components of the binutils you intend to build alongside the compiler (bfd, binutils, gas, gprof, ld, ! opcodes, ...) to the directory containing the GCC sources. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/finalinstall.html gcc-3.2.3/INSTALL/finalinstall.html *** gcc-3.2.2/INSTALL/finalinstall.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/finalinstall.html Tue Apr 22 06:56:34 2003 *************** *** 1,57 **** ! Installing GCC: Final installation ! ! ! ! ! !

N

ow that GCC has been built (and optionally tested), you can install it with ! 

cd objdir; make install
!
!

We strongly recommend to install into a target directory where there is no previous version of GCC present. !

That step completes the installation of GCC; user level binaries can ! be found in prefix/bin where prefix is the value you specified with the --prefix to configure (or /usr/local by default). (If you specified --bindir, that directory will be used instead; otherwise, if you specified --exec-prefix, ! exec-prefix/bin will be used.) Headers for the C++ and ! Java libraries are installed in prefix/include; libraries ! in libdir (normally prefix/lib); internal ! parts of the compiler in libdir/gcc-lib; documentation in ! info format in infodir (normally prefix/info). !

When installing cross-compilers, GCC's executables ! are not only installed into bindir, that ! is, exec-prefix/bin, but additionally into ! exec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker. !

Installation into a temporary staging area or into a chroot jail can be achieved with the command ! 

make DESTDIR=path-to-rootdir install
!

where path-to-rootdir is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by DESTDIR need not exist yet; it will be created if necessary. !

There is a subtle point with tooldirs and DESTDIR: If you relocate a cross-compiler installation with ! e.g. DESTDIR=rootdir, then the directory ! rootdir/exec-prefix/target-alias/bin will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the DESTDIR feature. !

If you built a released version of GCC using make bootstrap then please quickly review the build status page for your release, available from http://gcc.gnu.org/buildstat.html. If your system is not listed for the version of GCC that you built, --- 1,59 ---- ! ! Installing GCC: Final installation ! ! ! ! ! !

Installing GCC: Final installation

! Now that GCC has been built (and optionally tested), you can install it with ! 
     cd objdir; make install
!
!

We strongly recommend to install into a target directory where there is no previous version of GCC present. !

That step completes the installation of GCC; user level binaries can ! be found in prefix/bin where prefix is the value you specified with the --prefix to configure (or /usr/local by default). (If you specified --bindir, that directory will be used instead; otherwise, if you specified --exec-prefix, ! exec-prefix/bin will be used.) Headers for the C++ and ! Java libraries are installed in prefix/include; libraries ! in libdir (normally prefix/lib); internal ! parts of the compiler in libdir/gcc-lib; documentation in ! info format in infodir (normally prefix/info). !

When installing cross-compilers, GCC's executables ! are not only installed into bindir, that ! is, exec-prefix/bin, but additionally into ! exec-prefix/target-alias/bin, if that directory exists. Typically, such tooldirs hold target-specific binutils, including assembler and linker. !

Installation into a temporary staging area or into a chroot jail can be achieved with the command ! 

     make DESTDIR=path-to-rootdir install
!

where path-to-rootdir is the absolute path of a directory relative to which all installation paths will be interpreted. Note that the directory specified by DESTDIR need not exist yet; it will be created if necessary. !

There is a subtle point with tooldirs and DESTDIR: If you relocate a cross-compiler installation with ! e.g. DESTDIR=rootdir, then the directory ! rootdir/exec-prefix/target-alias/bin will be filled with duplicated GCC executables only if it already exists, it will not be created otherwise. This is regarded as a feature, not as a bug, because it gives slightly more control to the packagers using the DESTDIR feature. !

If you built a released version of GCC using make bootstrap then please quickly review the build status page for your release, available from http://gcc.gnu.org/buildstat.html. If your system is not listed for the version of GCC that you built, *************** send a note to *** 60,119 **** that you successfully built and installed GCC. Include the following information: !

    !
  • Output from running srcdir/config.guess. Do not send us that file itself, just the one-line output from running it. !
  • The output of gcc -v for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure. !
  • Whether you enabled all languages or a subset of them. If you used a full distribution then this information is part of the configure options in the output of gcc -v, but if you downloaded the "core" compiler plus additional front ends then it isn't apparent which ones you built unless you tell us about it. !
  • If the build was for GNU/Linux, also include: !
    • The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); this information should be available from /etc/issue. !
    • The version of the Linux kernel, available from uname --version or uname -a. !
    • The version of glibc you used; for RPM-based systems like Red Hat, Mandrake, and SuSE type rpm -q glibc to get the glibc version, and on systems like Debian and Progeny use dpkg -l libc6.
    ! For other systems, you can include similar information if you think it is relevant. !
  • Any other information that you think would be useful to people building GCC on the same configuration. The new entry in the build status list will include a link to the archived copy of your message.
!

We'd also like to know if the host/target specific installation notes didn't include your host/target information or if that information is incomplete or out of date. Send a note to gcc@gcc.gnu.org telling us how the information should be changed. !

If you find a bug, please report it following our bug reporting guidelines. !

If you want to print the GCC manuals, do cd objdir; make dvi. You will need to have texi2dvi (version at least 4.1) and TeX installed. This creates a number of .dvi files in ! subdirectories of objdir; these may be converted for printing with programs such as dvips. You can also buy printed manuals from the Free Software Foundation, though such manuals may not be for the most recent version of GCC. !

Return to the GCC Installation page ! --- 62,121 ---- that you successfully built and installed GCC. Include the following information: !

    !
  • Output from running srcdir/config.guess. Do not send us that file itself, just the one-line output from running it. !
  • The output of gcc -v for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure. !
  • Whether you enabled all languages or a subset of them. If you used a full distribution then this information is part of the configure options in the output of gcc -v, but if you downloaded the "core" compiler plus additional front ends then it isn't apparent which ones you built unless you tell us about it. !
  • If the build was for GNU/Linux, also include: !
    • The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3); this information should be available from /etc/issue. !
    • The version of the Linux kernel, available from uname --version or uname -a. !
    • The version of glibc you used; for RPM-based systems like Red Hat, Mandrake, and SuSE type rpm -q glibc to get the glibc version, and on systems like Debian and Progeny use dpkg -l libc6.
    ! For other systems, you can include similar information if you think it is relevant. !
  • Any other information that you think would be useful to people building GCC on the same configuration. The new entry in the build status list will include a link to the archived copy of your message.
!

We'd also like to know if the host/target specific installation notes didn't include your host/target information or if that information is incomplete or out of date. Send a note to gcc@gcc.gnu.org telling us how the information should be changed. !

If you find a bug, please report it following our bug reporting guidelines. !

If you want to print the GCC manuals, do cd objdir; make dvi. You will need to have texi2dvi (version at least 4.1) and TeX installed. This creates a number of .dvi files in ! subdirectories of objdir; these may be converted for printing with programs such as dvips. You can also buy printed manuals from the Free Software Foundation, though such manuals may not be for the most recent version of GCC. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/gfdl.html gcc-3.2.3/INSTALL/gfdl.html *** gcc-3.2.2/INSTALL/gfdl.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/gfdl.html Tue Apr 22 06:56:35 2003 *************** *** 1,26 **** ! Installing GCC: GNU Free Documentation License ! ! ! ! !

Installing GCC: GNU Free Documentation License

!

Version 1.1, March 2000

! ! 
Copyright © 2000 Free Software Foundation, Inc.
! 59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
! 
! Everyone is permitted to copy and distribute verbatim copies
! of this license document, but changing it is not allowed.
!
!
  1. PREAMBLE !

    The purpose of this License is to make a manual, textbook, or other written document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, --- 1,27 ---- ! ! Installing GCC: GNU Free Documentation License ! ! ! ! ! !

    Installing GCC: GNU Free Documentation License

    Installing GCC: GNU Free Documentation License

    !
    Version 1.1, March 2000
    ! 
         Copyright © 2000 Free Software Foundation, Inc.
!      59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
!      
!      Everyone is permitted to copy and distribute verbatim copies
!      of this license document, but changing it is not allowed.
!
    !
    1. PREAMBLE !

      The purpose of this License is to make a manual, textbook, or other written document free in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, *************** this License preserves for the author an *** 28,39 **** credit for their work, while not being considered responsible for modifications made by others. !

      This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. !

      We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; --- 29,40 ---- credit for their work, while not being considered responsible for modifications made by others. !

      This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. !

      We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; *************** it can be used for any textual work, reg *** 41,59 **** whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. !

    2. APPLICABILITY AND DEFINITIONS !

      This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". !

      A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. !

      A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly --- 42,60 ---- whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. !

    3. APPLICABILITY AND DEFINITIONS !

      This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". !

      A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. !

      A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly *************** connection with the subject or with rela *** 64,78 **** commercial, philosophical, ethical or political position regarding them. !

      The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. !

      The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. !

      A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of --- 65,79 ---- commercial, philosophical, ethical or political position regarding them. !

      The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. !

      The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. !

      A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of *************** format whose markup has been designed to *** 84,90 **** subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque". !

      Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed --- 85,91 ---- subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque". !

      Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed *************** the DTD and/or processing *** 95,110 **** and the machine-generated HTML produced by some word processors for output purposes only. !

      The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. !

    4. VERBATIM COPYING !

      You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other --- 96,111 ---- and the machine-generated HTML produced by some word processors for output purposes only. !

      The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. !

    5. VERBATIM COPYING !

      You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other *************** copying of the copies you make or distri *** 114,125 **** compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. !

      You may also lend copies, under the same conditions stated above, and you may publicly display copies. !

    6. COPYING IN QUANTITY !

      If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on --- 115,126 ---- compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. !

      You may also lend copies, under the same conditions stated above, and you may publicly display copies. !

    7. COPYING IN QUANTITY !

      If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on *************** Copying with changes limited to the cove *** 131,142 **** the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. !

      If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. !

      If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete --- 132,143 ---- the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. !

      If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. !

      If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible computer-network location containing a complete *************** until at least one year after the last t *** 150,198 **** copy (directly or through your agents or retailers) of that edition to the public. !

      It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. !

    8. MODIFICATIONS !

      You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: !

        !

      1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. !
      2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five). !
      3. State on the Title page the name of the publisher of the Modified Version, as the publisher. !
      4. Preserve all the copyright notices of the Document. !
      5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. !
      6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. !
      7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. !
      8. Include an unaltered copy of this License. !
      9. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one --- 151,199 ---- copy (directly or through your agents or retailers) of that edition to the public. !

        It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. !

      10. MODIFICATIONS !

        You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: !

          !
        1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. !
        2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has less than five). !
        3. State on the Title page the name of the publisher of the Modified Version, as the publisher. !
        4. Preserve all the copyright notices of the Document. !
        5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. !
        6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. !
        7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. !
        8. Include an unaltered copy of this License. !
        9. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, create one *************** stating the title, year, authors, and pu *** 200,206 **** given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. !
        10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. --- 201,207 ---- given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. !
        11. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. *************** You may omit a network location for a wo *** 208,243 **** least four years before the Document itself, or if the original publisher of the version it refers to gives permission. !
        12. In any section entitled "Acknowledgments" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgments and/or dedications given therein. !
        13. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. !
        14. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version. !
        15. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section. !
        !

        If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. !

        You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. !

        You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or --- 209,244 ---- least four years before the Document itself, or if the original publisher of the version it refers to gives permission. !

      11. In any section entitled "Acknowledgments" or "Dedications", preserve the section's title, and preserve in the section all the substance and tone of each of the contributor acknowledgments and/or dedications given therein. !
      12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. !
      13. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version. !
      14. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section. !
      !

      If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. !

      You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. !

      You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or *************** by arrangement made by the same entity y *** 247,266 **** you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. !

      The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. !

    9. COMBINING DOCUMENTS !

      You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice. !

      The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by --- 248,267 ---- you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. !

      The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. !

    10. COMBINING DOCUMENTS !

      You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice. !

      The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by *************** author or publisher of that section if k *** 269,296 **** Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. !

      In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgments", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements." !

    11. COLLECTIONS OF DOCUMENTS !

      You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. !

      You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. !

    12. AGGREGATION WITH INDEPENDENT WORKS !

      A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the --- 270,297 ---- Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. !

      In the combination, you must combine any sections entitled "History" in the various original documents, forming one section entitled "History"; likewise combine any sections entitled "Acknowledgments", and any sections entitled "Dedications". You must delete all sections entitled "Endorsements." !

    13. COLLECTIONS OF DOCUMENTS !

      You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. !

      You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. !

    14. AGGREGATION WITH INDEPENDENT WORKS !

      A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no compilation copyright is claimed for the *************** License does not apply to the other self *** 299,313 **** with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document. !

      If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. !

    15. TRANSLATION !

      Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include --- 300,314 ---- with the Document, on account of their being thus compiled, if they are not themselves derivative works of the Document. !

      If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. !

    16. TRANSLATION !

      Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include *************** original English version of this License *** 318,326 **** between the translation and the original English version of this License, the original English version will prevail. !

    17. TERMINATION !

      You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, --- 319,327 ---- between the translation and the original English version of this License, the original English version will prevail. !

    18. TERMINATION !

      You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, *************** parties who have received copies, or rig *** 328,342 **** License will not have their licenses terminated so long as such parties remain in full compliance. !

    19. FUTURE REVISIONS OF THIS LICENSE !

      The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. !

      Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or --- 329,343 ---- License will not have their licenses terminated so long as such parties remain in full compliance. !

    20. FUTURE REVISIONS OF THIS LICENSE !

      The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. !

      Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or *************** of any later version that has been publi *** 344,380 **** Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. !

    !

    ADDENDUM: How to use this License for your documents

    !

    To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: ! 

      Copyright (C)  year  your name.
!   Permission is granted to copy, distribute and/or modify this document
!   under the terms of the GNU Free Documentation License, Version 1.1
!   or any later version published by the Free Software Foundation;
!   with the Invariant Sections being list their titles, with the
!   Front-Cover Texts being list, and with the Back-Cover Texts being list.
!   A copy of the license is included in the section entitled ``GNU
!   Free Documentation License''.
!
    !

    If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being list"; likewise for Back-Cover Texts. !

    If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. !

    Return to the GCC Installation page ! --- 345,381 ---- Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. !

!

ADDENDUM: How to use this License for your documents

!

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: ! 

       Copyright (C)  year  your name.
!        Permission is granted to copy, distribute and/or modify this document
!        under the terms of the GNU Free Documentation License, Version 1.1
!        or any later version published by the Free Software Foundation;
!        with the Invariant Sections being list their titles, with the
!        Front-Cover Texts being list, and with the Back-Cover Texts being list.
!        A copy of the license is included in the section entitled ``GNU
!        Free Documentation License''.
!
!

If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being list"; likewise for Back-Cover Texts. !

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/index.html gcc-3.2.3/INSTALL/index.html *** gcc-3.2.2/INSTALL/index.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/index.html Tue Apr 22 06:56:32 2003 *************** *** 1,75 **** ! Installing GCC ! ! ! ! ! !

T

he latest version of this document is always available at http://gcc.gnu.org/install/. !

This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. !

GCC includes several components that previously were separate distributions with their own installation instructions. This document supersedes all package specific installation instructions. !

Before starting the build/install procedure please check the host/target specific installation notes. We recommend you browse the entire generic installation instructions before you proceed. !

Lists of successful builds for released versions of GCC are available at http://gcc.gnu.org/buildstat.html. These lists are updated as new information becomes available. !

The installation procedure itself is broken into five steps. !

    !

  1. Downloading the source
  2. Configuration
  3. Building
  4. Testing (optional)
  5. Final install !
!

Please note that GCC does not support make uninstall and probably won't do so in the near future as this would open a can of worms. Instead, we suggest that you install GCC into a directory of its own and simply remove that directory when you do not need that specific version of GCC any longer, and, if shared libraries are installed there as well, no more binaries exist that use them. !

There are also some old installation instructions, which are mostly obsolete but still contain some information which has not yet been merged into the main part of this manual. !

Return to the GCC Installation page !

Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. -

!

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled "GNU Free Documentation License". !

(a) The FSF's Front-Cover Text is: !

A GNU Manual !

(b) The FSF's Back-Cover Text is: !

You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. ! --- 1,76 ---- ! ! Installing GCC ! ! ! ! ! !

Installing GCC

! The latest version of this document is always available at http://gcc.gnu.org/install/. !

This document describes the generic installation procedure for GCC as well as detailing some target specific installation instructions. !

GCC includes several components that previously were separate distributions with their own installation instructions. This document supersedes all package specific installation instructions. !

Before starting the build/install procedure please check the host/target specific installation notes. We recommend you browse the entire generic installation instructions before you proceed. !

Lists of successful builds for released versions of GCC are available at http://gcc.gnu.org/buildstat.html. These lists are updated as new information becomes available. !

The installation procedure itself is broken into five steps. !

    !
  1. Downloading the source
  2. Configuration
  3. Building
  4. Testing (optional)
  5. Final install !
!

Please note that GCC does not support make uninstall and probably won't do so in the near future as this would open a can of worms. Instead, we suggest that you install GCC into a directory of its own and simply remove that directory when you do not need that specific version of GCC any longer, and, if shared libraries are installed there as well, no more binaries exist that use them. !

There are also some old installation instructions, which are mostly obsolete but still contain some information which has not yet been merged into the main part of this manual. !

Return to the GCC Installation page !

Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.

!

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled "GNU Free Documentation License". !

(a) The FSF's Front-Cover Text is: !

A GNU Manual !

(b) The FSF's Back-Cover Text is: !

You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. ! diff -Nrc3pad gcc-3.2.2/INSTALL/old.html gcc-3.2.3/INSTALL/old.html *** gcc-3.2.2/INSTALL/old.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/old.html Tue Apr 22 06:56:35 2003 *************** *** 1,42 **** ! Installing GCC: Old documentation ! ! ! ! !

Old installation documentation

!

Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. !

Here is the procedure for installing GNU CC on a GNU or Unix system. See VMS Install, for VMS systems. !

    !

  1. If you have chosen a configuration for GNU CC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory under the names as, ld or whatever is appropriate. This will enable the compiler to find the proper tools for compilation of the program enquire. !

    Alternatively, you can do subsequent compilation using a value of the PATH environment variable such that the necessary GNU tools come before the standard system tools. !

  2. Specify the host, build and target machine configurations. You do this when you run the configure script. !

    The build machine is the system which you are using, the host machine is the system where you want to run the resulting compiler (normally the build machine), and the target machine is the system for which you want the compiler to generate code. !

    If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify any operands to configure; it will try to guess the type of machine you are on and use that as the build, host and target machines. So you don't need --- 1,44 ---- ! ! Installing GCC: Old documentation ! ! ! ! ! !

    Installing GCC: Old documentation

    Old installation documentation

    !

    Note most of this information is out of date and superseded by the previous chapters of this manual. It is provided for historical reference only, because of a lack of volunteers to merge it into the main manual. !

    Here is the procedure for installing GNU CC on a GNU or Unix system. See VMS Install, for VMS systems. !

      !
    1. If you have chosen a configuration for GNU CC which requires other GNU tools (such as GAS or the GNU linker) instead of the standard system tools, install the required tools in the build directory under the names as, ld or whatever is appropriate. This will enable the compiler to find the proper tools for compilation of the program enquire. !

      Alternatively, you can do subsequent compilation using a value of the PATH environment variable such that the necessary GNU tools come before the standard system tools. !

    2. Specify the host, build and target machine configurations. You do this when you run the configure script. !

      The build machine is the system which you are using, the host machine is the system where you want to run the resulting compiler (normally the build machine), and the target machine is the system for which you want the compiler to generate code. !

      If you are building a compiler to produce code for the machine it runs on (a native compiler), you normally do not need to specify any operands to configure; it will try to guess the type of machine you are on and use that as the build, host and target machines. So you don't need *************** to specify a configuration when building *** 44,87 **** configure cannot figure out what your configuration is or guesses wrong. !

      In those cases, specify the build machine's configuration name with the --host option; the host and target will default to be the same as the host machine. (If you are building a cross-compiler, see Cross-Compiler.) !

      Here is an example: ! 

      ./configure --host=sparc-sun-sunos4.1
!
      !

      A configuration name may be canonical or it may be more or less abbreviated. !

      A canonical configuration name has three parts, separated by dashes. ! It looks like this: cpu-company-system. (The three parts may themselves contain dashes; configure can figure out which dashes serve which purpose.) For example, m68k-sun-sunos4.1 specifies a Sun 3. !

      You can also replace parts of the configuration by nicknames or aliases. For example, sun3 stands for m68k-sun, so sun3-sunos4.1 is another way to specify a Sun 3. !

      You can specify a version number after any of the system types, and some of the CPU types. In most cases, the version is irrelevant, and will be ignored. So you might as well specify the version if you know it. !

      See Configurations, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GNU CC. !

    !

    Configurations Supported by GNU CC

    !

    Here are the possible CPU types: !

    1750a, a29k, alpha, arm, avr, cn, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, m32r, m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el, --- 46,89 ---- configure cannot figure out what your configuration is or guesses wrong. !

    In those cases, specify the build machine's configuration name with the --host option; the host and target will default to be the same as the host machine. (If you are building a cross-compiler, see Cross-Compiler.) !

    Here is an example: ! 

              ./configure --host=sparc-sun-sunos4.1
!
    !

    A configuration name may be canonical or it may be more or less abbreviated. !

    A canonical configuration name has three parts, separated by dashes. ! It looks like this: cpu-company-system. (The three parts may themselves contain dashes; configure can figure out which dashes serve which purpose.) For example, m68k-sun-sunos4.1 specifies a Sun 3. !

    You can also replace parts of the configuration by nicknames or aliases. For example, sun3 stands for m68k-sun, so sun3-sunos4.1 is another way to specify a Sun 3. !

    You can specify a version number after any of the system types, and some of the CPU types. In most cases, the version is irrelevant, and will be ignored. So you might as well specify the version if you know it. !

    See Configurations, for a list of supported configuration names and notes on many of the configurations. You should check the notes in that section before proceeding any further with the installation of GNU CC. !

!

Configurations Supported by GNU CC

!

Here are the possible CPU types: !

1750a, a29k, alpha, arm, avr, cn, clipper, dsp16xx, elxsi, fr30, h8300, hppa1.0, hppa1.1, i370, i386, i486, i586, i686, i786, i860, i960, m32r, m68000, m68k, m6811, m6812, m88k, mcore, mips, mipsel, mips64, mips64el, *************** mn10200, mn10300, ns32k, pdp11, powerpc, *** 89,98 **** sparclite, sparc64, v850, vax, we32k.
!

Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. !

acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, --- 91,100 ---- sparclite, sparc64, v850, vax, we32k.
!

Here are the recognized company names. As you can see, customary abbreviations are used rather than the longer official names. !

acorn, alliant, altos, apollo, apple, att, bull, cbm, convergent, convex, crds, dec, dg, dolphin, elxsi, encore, harris, hitachi, hp, ibm, intergraph, isi, *************** mips, motorola, ncr, next, ns, omron, pl *** 100,113 **** sequent, sgi, sony, sun, tti, unicom, wrs.
!

The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing ! just cpu-system, if it is not needed. For example, vax-ultrix4.2 is equivalent to vax-dec-ultrix4.2. !

Here is a list of system types: !

386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, --- 102,115 ---- sequent, sgi, sony, sun, tti, unicom, wrs.
!

The company name is meaningful only to disambiguate when the rest of the information supplied is insufficient. You can omit it, writing ! just cpu-system, if it is not needed. For example, vax-ultrix4.2 is equivalent to vax-dec-ultrix4.2. !

Here is a list of system types: !

386bsd, aix, acis, amigaos, aos, aout, aux, bosx, bsd, clix, coff, ctix, cxux, dgux, dynix, ebmon, ecoff, elf, esix, freebsd, hms, genix, gnu, linux, linux-gnu, hiux, hpux, iris, irix, isc, luna, lynxos, mach, minix, msdos, mvs, *************** vxworks, winnt, xenix. *** 119,150 ****

You can omit the system type; then configure guesses the operating system from the CPU and company. !

You can add a version number to the system type; this may or may not make a difference. For example, you can write bsd4.3 or bsd4.4 to distinguish versions of BSD. In practice, the version number is most needed for sysv3 and sysv4, which are often treated differently. !

linux-gnu is the canonical name for the GNU/Linux target; however GNU CC will also accept linux. The version of the kernel in use is not relevant on these systems. A suffix such as libc1 or aout distinguishes major versions of the C library; all of the suffixed versions are obsolete. !

If you specify an impossible combination such as i860-dg-vms, then you may get an error message from configure, or it may ignore part of the information and do the best it can with the rest. configure always prints the canonical name for the alternative that it used. GNU CC does not support all possible alternatives. !

Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine name sun3, mentioned above, is an alias for m68k-sun. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: !

3300, 3b1, 3bn, 7300, altos3068, altos, apollo68, att-7300, balance, convex-cn, crds, decstation-3100, --- 121,152 ----

You can omit the system type; then configure guesses the operating system from the CPU and company. !

You can add a version number to the system type; this may or may not make a difference. For example, you can write bsd4.3 or bsd4.4 to distinguish versions of BSD. In practice, the version number is most needed for sysv3 and sysv4, which are often treated differently. !

linux-gnu is the canonical name for the GNU/Linux target; however GNU CC will also accept linux. The version of the kernel in use is not relevant on these systems. A suffix such as libc1 or aout distinguishes major versions of the C library; all of the suffixed versions are obsolete. !

If you specify an impossible combination such as i860-dg-vms, then you may get an error message from configure, or it may ignore part of the information and do the best it can with the rest. configure always prints the canonical name for the alternative that it used. GNU CC does not support all possible alternatives. !

Often a particular model of machine has a name. Many machine names are recognized as aliases for CPU/company combinations. Thus, the machine name sun3, mentioned above, is an alias for m68k-sun. Sometimes we accept a company name as a machine name, when the name is popularly used for a particular machine. Here is a table of the known machine names: !

3300, 3b1, 3bn, 7300, altos3068, altos, apollo68, att-7300, balance, convex-cn, crds, decstation-3100, *************** sun4, symmetry, tower-32, tower. *** 163,375 **** name. If you want to install your own homemade configuration files, you can use local as the company name to access them. If you use ! configuration cpu-local, the configuration name without the cpu prefix is used to form the configuration file names. !

Thus, if you specify m68k-local, configuration uses files m68k.md, local.h, m68k.c, xm-local.h, t-local, and x-local, all in the directory config/m68k. !

Here is a list of configurations that have special treatment or special things you must know: !

vax-dec-vms !
See VMS Install, for details on how to install GNU CC on VMS.
!

Building and Installing a Cross-Compiler

!

GNU CC can function as a cross-compiler for many machines, but not all. !

  • Cross-compilers for the Mips as target using the Mips assembler currently do not work, because the auxiliary programs mips-tdump.c and mips-tfile.c can't be compiled on anything but a Mips. It does work to cross compile for a Mips if you use the GNU assembler and linker. !
  • Cross-compilers between machines with different floating point formats have not all been made to work. GNU CC now has a floating point emulator with which these can work, but each target machine description needs to be updated to take advantage of it. !
  • Cross-compilation between machines of different word sizes is somewhat problematic and sometimes does not work.
!

Since GNU CC generates assembler code, you probably need a cross-assembler that GNU CC can run, in order to produce object files. If you want to link on other than the target machine, you need a cross-linker as well. You also need header files and libraries suitable for the target machine that you can install on the host machine. !

Steps of Cross-Compilation

!

To compile and run a program using a cross-compiler involves several steps: !

  • Run the cross-compiler on the host machine to produce assembler files for the target machine. This requires header files for the target machine. !
  • Assemble the files produced by the cross-compiler. You can do this either with an assembler on the target machine, or with a cross-assembler on the host machine. !
  • Link those files to make an executable. You can do this either with a linker on the target machine, or with a cross-linker on the host machine. Whichever machine you use, you need libraries and certain ! startup files (typically crt....o) for the target machine.
!

It is most convenient to do all of these steps on the same host machine, since then you can do it all with a single invocation of GNU CC. This requires a suitable cross-assembler and cross-linker. For some targets, the GNU assembler and linker are available. !

Configuring a Cross-Compiler

!

To build GNU CC as a cross-compiler, you start out by running ! configure. Use the --target=target to specify the target type. If configure was unable to correctly identify the ! system you are running on, also specify the --build=build option. For example, here is how to configure for a cross-compiler that produces code for an HP 68030 system running BSD on a system that configure can correctly identify: ! 

./configure --target=m68k-hp-bsd4.3
!
!

Tools and Libraries for a Cross-Compiler

!

If you have a cross-assembler and cross-linker available, you should install them now. Put them in the directory ! /usr/local/target/bin. Here is a table of the tools you should put in this directory: !

as !
This should be the cross-assembler. !
ld !
This should be the cross-linker. !
ar !
This should be the cross-archiver: a program which can manipulate archive files (linker libraries) in the target machine's format. !
ranlib !
This should be a program to construct a symbol table in an archive file.
!

The installation of GNU CC will find these programs in that directory, and copy or link them to the proper place to for the cross-compiler to find them when run later. !

The easiest way to provide these files is to build the Binutils package and GAS. Configure them with the same --host and --target options that you use for configuring GNU CC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GNU CC supports. !

If you want to install libraries to use with the cross-compiler, such as a standard C library, put them in the directory ! /usr/local/target/lib; installation of GNU CC copies all the files in that subdirectory into the proper place for GNU CC to find them and link with them. Here's an example of copying some libraries from a target machine: ! 

ftp target-machine
! lcd /usr/local/target/lib
! cd /lib
! get libc.a
! cd /usr/lib
! get libg.a
! get libm.a
! quit
!

The precise set of libraries you'll need, and their locations on the target machine, vary depending on its operating system. !

Many targets require "start files" such as crt0.o and crtn.o which are linked into each executable; these too should be ! placed in /usr/local/target/lib. There may be several alternatives for crt0.o, for use with profiling or other compilation options. Check your target's definition of STARTFILE_SPEC to find out what start files it uses. Here's an example of copying these files from a target machine: ! 

ftp target-machine
! lcd /usr/local/target/lib
! prompt
! cd /lib
! mget *crt*.o
! cd /usr/lib
! mget *crt*.o
! quit
!
!

Cross-Compilers and Header Files

!

If you are cross-compiling a standalone program or a program for an embedded system, then you may not need any header files except the few that are part of GNU CC (and those of your program). However, if you intend to link your program with a standard C library such as libc.a, then you probably need to compile with the header files that go with the library you use. !

The GNU C compiler does not come with these files, because (1) they are system-specific, and (2) they belong in a C library, not in a compiler. !

If the GNU C library supports your target machine, then you can get the header files from there (assuming you actually use the GNU library when you link your program). !

If your target machine comes with a C compiler, it probably comes with suitable header files also. If you make these files accessible from the host machine, the cross-compiler can use them also. !

Otherwise, you're on your own in finding header files to use when cross-compiling. !

When you have found suitable header files, you should put them in the ! directory /usr/local/target/include, before building the cross compiler. Then installation will run fixincludes properly and install the corrected versions of the header files where the compiler will use them. !

Provide the header files before you build the cross-compiler, because the build stage actually runs the cross-compiler to produce parts of libgcc.a. (These are the parts that can be compiled with GNU CC.) Some of them need suitable header files. !

Here's an example showing how to copy the header files from a target machine. On the target machine, do this: ! 

(cd /usr/include; tar cf - .) > tarfile
!
!

Then, on the host machine, do this: ! 

ftp target-machine
! lcd /usr/local/target/include
! get tarfile
! quit
! tar xf tarfile
!
!

Actually Building the Cross-Compiler

!

Now you can proceed just as for compiling a single-machine compiler through the step of building stage 1. !

If your target is exotic, you may need to provide the header file float.h.One way to do this is to compile enquire and run it on your target machine. The job of enquire is to run on the target machine and figure out by experiment the nature of its floating --- 165,377 ---- name. If you want to install your own homemade configuration files, you can use local as the company name to access them. If you use ! configuration cpu-local, the configuration name without the cpu prefix is used to form the configuration file names. !

Thus, if you specify m68k-local, configuration uses files m68k.md, local.h, m68k.c, xm-local.h, t-local, and x-local, all in the directory config/m68k. !

Here is a list of configurations that have special treatment or special things you must know: !

vax-dec-vms !
See VMS Install, for details on how to install GNU CC on VMS.
!

Building and Installing a Cross-Compiler

!

GNU CC can function as a cross-compiler for many machines, but not all. !

  • Cross-compilers for the Mips as target using the Mips assembler currently do not work, because the auxiliary programs mips-tdump.c and mips-tfile.c can't be compiled on anything but a Mips. It does work to cross compile for a Mips if you use the GNU assembler and linker. !
  • Cross-compilers between machines with different floating point formats have not all been made to work. GNU CC now has a floating point emulator with which these can work, but each target machine description needs to be updated to take advantage of it. !
  • Cross-compilation between machines of different word sizes is somewhat problematic and sometimes does not work.
!

Since GNU CC generates assembler code, you probably need a cross-assembler that GNU CC can run, in order to produce object files. If you want to link on other than the target machine, you need a cross-linker as well. You also need header files and libraries suitable for the target machine that you can install on the host machine. !

Steps of Cross-Compilation

!

To compile and run a program using a cross-compiler involves several steps: !

  • Run the cross-compiler on the host machine to produce assembler files for the target machine. This requires header files for the target machine. !
  • Assemble the files produced by the cross-compiler. You can do this either with an assembler on the target machine, or with a cross-assembler on the host machine. !
  • Link those files to make an executable. You can do this either with a linker on the target machine, or with a cross-linker on the host machine. Whichever machine you use, you need libraries and certain ! startup files (typically crt....o) for the target machine.
!

It is most convenient to do all of these steps on the same host machine, since then you can do it all with a single invocation of GNU CC. This requires a suitable cross-assembler and cross-linker. For some targets, the GNU assembler and linker are available. !

Configuring a Cross-Compiler

!

To build GNU CC as a cross-compiler, you start out by running ! configure. Use the --target=target to specify the target type. If configure was unable to correctly identify the ! system you are running on, also specify the --build=build option. For example, here is how to configure for a cross-compiler that produces code for an HP 68030 system running BSD on a system that configure can correctly identify: ! 

     ./configure --target=m68k-hp-bsd4.3
!
!

Tools and Libraries for a Cross-Compiler

!

If you have a cross-assembler and cross-linker available, you should install them now. Put them in the directory ! /usr/local/target/bin. Here is a table of the tools you should put in this directory: !

as !
This should be the cross-assembler. !
ld !
This should be the cross-linker. !
ar !
This should be the cross-archiver: a program which can manipulate archive files (linker libraries) in the target machine's format. !
ranlib !
This should be a program to construct a symbol table in an archive file.
!

The installation of GNU CC will find these programs in that directory, and copy or link them to the proper place to for the cross-compiler to find them when run later. !

The easiest way to provide these files is to build the Binutils package and GAS. Configure them with the same --host and --target options that you use for configuring GNU CC, then build and install them. They install their executables automatically into the proper directory. Alas, they do not support all the targets that GNU CC supports. !

If you want to install libraries to use with the cross-compiler, such as a standard C library, put them in the directory ! /usr/local/target/lib; installation of GNU CC copies all the files in that subdirectory into the proper place for GNU CC to find them and link with them. Here's an example of copying some libraries from a target machine: ! 

     ftp target-machine
!      lcd /usr/local/target/lib
!      cd /lib
!      get libc.a
!      cd /usr/lib
!      get libg.a
!      get libm.a
!      quit
!

The precise set of libraries you'll need, and their locations on the target machine, vary depending on its operating system. !

Many targets require "start files" such as crt0.o and crtn.o which are linked into each executable; these too should be ! placed in /usr/local/target/lib. There may be several alternatives for crt0.o, for use with profiling or other compilation options. Check your target's definition of STARTFILE_SPEC to find out what start files it uses. Here's an example of copying these files from a target machine: ! 

     ftp target-machine
!      lcd /usr/local/target/lib
!      prompt
!      cd /lib
!      mget *crt*.o
!      cd /usr/lib
!      mget *crt*.o
!      quit
!
!

Cross-Compilers and Header Files

!

If you are cross-compiling a standalone program or a program for an embedded system, then you may not need any header files except the few that are part of GNU CC (and those of your program). However, if you intend to link your program with a standard C library such as libc.a, then you probably need to compile with the header files that go with the library you use. !

The GNU C compiler does not come with these files, because (1) they are system-specific, and (2) they belong in a C library, not in a compiler. !

If the GNU C library supports your target machine, then you can get the header files from there (assuming you actually use the GNU library when you link your program). !

If your target machine comes with a C compiler, it probably comes with suitable header files also. If you make these files accessible from the host machine, the cross-compiler can use them also. !

Otherwise, you're on your own in finding header files to use when cross-compiling. !

When you have found suitable header files, you should put them in the ! directory /usr/local/target/include, before building the cross compiler. Then installation will run fixincludes properly and install the corrected versions of the header files where the compiler will use them. !

Provide the header files before you build the cross-compiler, because the build stage actually runs the cross-compiler to produce parts of libgcc.a. (These are the parts that can be compiled with GNU CC.) Some of them need suitable header files. !

Here's an example showing how to copy the header files from a target machine. On the target machine, do this: ! 

     (cd /usr/include; tar cf - .) > tarfile
!
!

Then, on the host machine, do this: ! 

     ftp target-machine
!      lcd /usr/local/target/include
!      get tarfile
!      quit
!      tar xf tarfile
!
!

Actually Building the Cross-Compiler

!

Now you can proceed just as for compiling a single-machine compiler through the step of building stage 1. !

If your target is exotic, you may need to provide the header file float.h.One way to do this is to compile enquire and run it on your target machine. The job of enquire is to run on the target machine and figure out by experiment the nature of its floating *************** file float.h. If you can't *** 379,385 **** a suitable float.h in some other way (or else, avoid using it in your programs). !

Do not try to build stage 2 for a cross-compiler. It doesn't work to rebuild GNU CC as a cross-compiler using the cross-compiler, because that would produce a program that runs on the target machine, not on the host. For example, if you compile a 386-to-68030 cross-compiler with --- 381,387 ---- a suitable float.h in some other way (or else, avoid using it in your programs). !

Do not try to build stage 2 for a cross-compiler. It doesn't work to rebuild GNU CC as a cross-compiler using the cross-compiler, because that would produce a program that runs on the target machine, not on the host. For example, if you compile a 386-to-68030 cross-compiler with *************** for a 386 as the host). If you want to *** 389,464 **** whether you compile it on a 68030 or with a cross-compiler on a 386, you must specify a 68030 as the host when you configure it. !

To install the cross-compiler, use make install, as usual. !

Installing GNU CC on VMS

!

The VMS version of GNU CC is distributed in a backup saveset containing both source code and precompiled binaries. !

To install the gcc command so you can use the compiler easily, in the same manner as you use the VMS C compiler, you must install the VMS CLD file for GNU CC as follows: !

    !

  1. Define the VMS logical names GNU_CC and GNU_CC_INCLUDE to point to the directories where the GNU CC executables (gcc-cpp.exe, gcc-cc1.exe, etc.) and the C include files are kept respectively. This should be done with the commands: ! 
    $ assign /system /translation=concealed -
!   disk:[gcc.] gnu_cc
! $ assign /system /translation=concealed -
!   disk:[gcc.include.] gnu_cc_include
!
    !

    with the appropriate disk and directory names. These commands can be placed in your system startup file so they will be executed whenever the machine is rebooted. You may, if you choose, do this via the GCC_INSTALL.COM script in the [GCC] directory. !

  2. Install the GCC command with the command line: ! 
    $ set command /table=sys$common:[syslib]dcltables -
!   /output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc
! $ install replace sys$common:[syslib]dcltables
!
    !
  3. To install the help file, do the following: ! 
    $ library/help sys$library:helplib.hlb gcc.hlp
!
    !

    Now you can invoke the compiler with a command like gcc /verbose file.c, which is equivalent to the command gcc -v -c file.c in Unix. !

!

If you wish to use GNU C++ you must first install GNU CC, and then perform the following steps: !

    !

  1. Define the VMS logical name GNU_GXX_INCLUDE to point to the directory where the preprocessor will search for the C++ header files. This can be done with the command: ! 
    $ assign /system /translation=concealed -
!   disk:[gcc.gxx_include.] gnu_gxx_include
!
    !

    with the appropriate disk and directory name. If you are going to be using a C++ runtime library, this is where its install procedure will install its header files. !

  2. Obtain the file gcc-cc1plus.exe, and place this in the same directory that gcc-cc1.exe is kept. !

    The GNU C++ compiler can be invoked with a command like gcc /plus /verbose file.cc, which is equivalent to the command g++ -v -c file.cc in Unix. !

!

We try to put corresponding binaries and sources on the VMS distribution tape. But sometimes the binaries will be from an older version than the sources, because we don't always have time to update them. (Use the /version option to determine the version number of the binaries and --- 391,466 ---- whether you compile it on a 68030 or with a cross-compiler on a 386, you must specify a 68030 as the host when you configure it. !

To install the cross-compiler, use make install, as usual. !

Installing GNU CC on VMS

!

The VMS version of GNU CC is distributed in a backup saveset containing both source code and precompiled binaries. !

To install the gcc command so you can use the compiler easily, in the same manner as you use the VMS C compiler, you must install the VMS CLD file for GNU CC as follows: !

    !
  1. Define the VMS logical names GNU_CC and GNU_CC_INCLUDE to point to the directories where the GNU CC executables (gcc-cpp.exe, gcc-cc1.exe, etc.) and the C include files are kept respectively. This should be done with the commands: ! 
              $ assign /system /translation=concealed -
!             disk:[gcc.] gnu_cc
!           $ assign /system /translation=concealed -
!             disk:[gcc.include.] gnu_cc_include
!
    !

    with the appropriate disk and directory names. These commands can be placed in your system startup file so they will be executed whenever the machine is rebooted. You may, if you choose, do this via the GCC_INSTALL.COM script in the [GCC] directory. !

  2. Install the GCC command with the command line: ! 
              $ set command /table=sys$common:[syslib]dcltables -
!             /output=sys$common:[syslib]dcltables gnu_cc:[000000]gcc
!           $ install replace sys$common:[syslib]dcltables
!
    !
  3. To install the help file, do the following: ! 
              $ library/help sys$library:helplib.hlb gcc.hlp
!
    !

    Now you can invoke the compiler with a command like gcc /verbose file.c, which is equivalent to the command gcc -v -c file.c in Unix. !

!

If you wish to use GNU C++ you must first install GNU CC, and then perform the following steps: !

    !
  1. Define the VMS logical name GNU_GXX_INCLUDE to point to the directory where the preprocessor will search for the C++ header files. This can be done with the command: ! 
              $ assign /system /translation=concealed -
!             disk:[gcc.gxx_include.] gnu_gxx_include
!
    !

    with the appropriate disk and directory name. If you are going to be using a C++ runtime library, this is where its install procedure will install its header files. !

  2. Obtain the file gcc-cc1plus.exe, and place this in the same directory that gcc-cc1.exe is kept. !

    The GNU C++ compiler can be invoked with a command like gcc /plus /verbose file.cc, which is equivalent to the command g++ -v -c file.cc in Unix. !

!

We try to put corresponding binaries and sources on the VMS distribution tape. But sometimes the binaries will be from an older version than the sources, because we don't always have time to update them. (Use the /version option to determine the version number of the binaries and *************** compare it with the source file ve *** 466,508 **** so.) In this case, you should use the binaries you get to recompile the sources. If you must recompile, here is how: !

    !

  1. Execute the command procedure vmsconfig.com to set up the files tm.h, config.h, aux-output.c, and md., and to create files tconfig.h and hconfig.h. This procedure also creates several linker option files used by make-cc1.com and a data file used by make-l2.com. ! 
    $ @vmsconfig.com
!
    !
  2. Setup the logical names and command tables as defined above. In addition, define the VMS logical name GNU_BISON to point at the to the directories where the Bison executable is kept. This should be done with the command: ! 
    $ assign /system /translation=concealed -
!   disk:[bison.] gnu_bison
!
    !

    You may, if you choose, use the INSTALL_BISON.COM script in the [BISON] directory. !

  3. Install the BISON command with the command line: ! 
    $ set command /table=sys$common:[syslib]dcltables -
!   /output=sys$common:[syslib]dcltables -
!   gnu_bison:[000000]bison
! $ install replace sys$common:[syslib]dcltables
!
    !
  4. Type @make-gcc to recompile everything, or submit the file make-gcc.com to a batch queue. If you wish to build the GNU C++ compiler as well as the GNU CC compiler, you must first edit make-gcc.com and follow the instructions that appear in the comments. !
  5. In order to use GCC, you need a library of functions which GCC compiled code will call to perform certain tasks, and these functions are defined in the file libgcc2.c. To compile this you should use the command procedure make-l2.com, which will generate the library libgcc2.olb. --- 468,510 ---- so.) In this case, you should use the binaries you get to recompile the sources. If you must recompile, here is how: !
      !
    1. Execute the command procedure vmsconfig.com to set up the files tm.h, config.h, aux-output.c, and md., and to create files tconfig.h and hconfig.h. This procedure also creates several linker option files used by make-cc1.com and a data file used by make-l2.com. ! 
                $ @vmsconfig.com
!
      !
    2. Setup the logical names and command tables as defined above. In addition, define the VMS logical name GNU_BISON to point at the to the directories where the Bison executable is kept. This should be done with the command: ! 
                $ assign /system /translation=concealed -
!             disk:[bison.] gnu_bison
!
      !

      You may, if you choose, use the INSTALL_BISON.COM script in the [BISON] directory. !

    3. Install the BISON command with the command line: ! 
                $ set command /table=sys$common:[syslib]dcltables -
!             /output=sys$common:[syslib]dcltables -
!             gnu_bison:[000000]bison
!           $ install replace sys$common:[syslib]dcltables
!
      !
    4. Type @make-gcc to recompile everything, or submit the file make-gcc.com to a batch queue. If you wish to build the GNU C++ compiler as well as the GNU CC compiler, you must first edit make-gcc.com and follow the instructions that appear in the comments. !
    5. In order to use GCC, you need a library of functions which GCC compiled code will call to perform certain tasks, and these functions are defined in the file libgcc2.c. To compile this you should use the command procedure make-l2.com, which will generate the library libgcc2.olb. *************** file libgcc2.c. To compile *** 510,524 **** the same distribution that libgcc2.c came from, and make-gcc.com will automatically do all of this for you. !

      To install the library, use the following commands: ! 

      $ library gnu_cc:[000000]gcclib/delete=(new,eprintf)
! $ library gnu_cc:[000000]gcclib/delete=L_*
! $ library libgcc2/extract=*/output=libgcc2.obj
! $ library gnu_cc:[000000]gcclib libgcc2.obj
!
      !

      The first command simply removes old modules that will be replaced with modules from libgcc2 under different module names. The modules new and eprintf may not actually be present in your gcclib.olb--if the VMS librarian complains about those modules --- 512,526 ---- the same distribution that libgcc2.c came from, and make-gcc.com will automatically do all of this for you. !

      To install the library, use the following commands: ! 

                $ library gnu_cc:[000000]gcclib/delete=(new,eprintf)
!           $ library gnu_cc:[000000]gcclib/delete=L_*
!           $ library libgcc2/extract=*/output=libgcc2.obj
!           $ library gnu_cc:[000000]gcclib libgcc2.obj
!
      !

      The first command simply removes old modules that will be replaced with modules from libgcc2 under different module names. The modules new and eprintf may not actually be present in your gcclib.olb--if the VMS librarian complains about those modules *************** not being present, simply ignore the mes *** 526,545 **** next command. The second command removes the modules that came from the previous version of the library libgcc2.c. !

      Whenever you update the compiler on your system, you should also update the library with the above procedure. !

    6. You may wish to build GCC in such a way that no files are written to the directory where the source files reside. An example would be the when the source files are on a read-only disk. In these cases, execute the following DCL commands (substituting your actual path names): ! 
      $ assign dua0:[gcc.build_dir.]/translation=concealed, -
!          dua1:[gcc.source_dir.]/translation=concealed  gcc_build
! $ set default gcc_build:[000000]
!
      !

      where the directory dua1:[gcc.source_dir] contains the source code, and the directory dua0:[gcc.build_dir] is meant to contain all of the generated object files and executables. Once you have done this, you can proceed building GCC as described above. (Keep in mind --- 528,547 ---- next command. The second command removes the modules that came from the previous version of the library libgcc2.c. !

      Whenever you update the compiler on your system, you should also update the library with the above procedure. !

    7. You may wish to build GCC in such a way that no files are written to the directory where the source files reside. An example would be the when the source files are on a read-only disk. In these cases, execute the following DCL commands (substituting your actual path names): ! 
                $ assign dua0:[gcc.build_dir.]/translation=concealed, -
!                    dua1:[gcc.source_dir.]/translation=concealed  gcc_build
!           $ set default gcc_build:[000000]
!
      !

      where the directory dua1:[gcc.source_dir] contains the source code, and the directory dua0:[gcc.build_dir] is meant to contain all of the generated object files and executables. Once you have done this, you can proceed building GCC as described above. (Keep in mind *************** that gcc_build is a rooted *** 547,553 **** names in each element of the search list must be an actual physical device name rather than another rooted logical name). !

    8. If you are building GNU CC with a previous version of GNU CC, you also should check to see that you have the newest version of the assembler. In particular, GNU CC version 2 treats global constant variables slightly differently from GNU CC version 1, and GAS version --- 549,555 ---- names in each element of the search list must be an actual physical device name rather than another rooted logical name). !

    9. If you are building GNU CC with a previous version of GNU CC, you also should check to see that you have the newest version of the assembler. In particular, GNU CC version 2 treats global constant variables slightly differently from GNU CC version 1, and GAS version *************** the read-only bit set, and the linker wi *** 557,563 **** about mismatched psect attributes for these variables. These warning messages are merely a nuisance, and can safely be ignored. !
    10. If you want to build GNU CC with the VAX C compiler, you will need to make minor changes in make-cccp.com and make-cc1.com to choose alternate definitions of CC, CFLAGS, and LIBS. See comments in those files. However, you must --- 559,565 ---- about mismatched psect attributes for these variables. These warning messages are merely a nuisance, and can safely be ignored. !
    11. If you want to build GNU CC with the VAX C compiler, you will need to make minor changes in make-cccp.com and make-cc1.com to choose alternate definitions of CC, CFLAGS, and LIBS. See comments in those files. However, you must *************** compile libgcc2 in order to *** 568,608 **** make-l2.com expects to be able to find it operational in gnu_cc:[000000]gnu-as.exe. !

      To use GNU CC on VMS, you need the VMS driver programs gcc.exe, gcc.com, and gcc.cld. They are distributed with the VMS binaries (gcc-vms) rather than the GNU CC sources. GAS is also included in gcc-vms, as is Bison. !

      Once you have successfully built GNU CC with VAX C, you should use the resulting compiler to rebuild itself. Before doing this, be sure to restore the CC, CFLAGS, and LIBS definitions in make-cccp.com and make-cc1.com. The second generation compiler will be able to take advantage of many optimizations that must be suppressed when building with other compilers. !

    !

    Under previous versions of GNU CC, the generated code would occasionally give strange results when linked with the sharable VAXCRTL library. Now this should work. !

    Even with this version, however, GNU CC itself should not be linked with the sharable VAXCRTL. The version of qsort in VAXCRTL has a bug (known to be present in VMS versions V4.6 through V5.5) which causes the compiler to fail. !

    The executables are generated by make-cc1.com and make-cccp.com use the object library version of VAXCRTL in order to make use of the qsort routine in gcclib.olb. If you wish to link the compiler executables with the shareable image version of VAXCRTL, you should edit the file tm.h (created by vmsconfig.com) to define the macro QSORT_WORKAROUND. !

    QSORT_WORKAROUND is always defined when GNU CC is compiled with VAX C, to avoid a problem in case gcclib.olb is not yet available.

    Return to the GCC Installation page ! --- 570,610 ---- make-l2.com expects to be able to find it operational in gnu_cc:[000000]gnu-as.exe. !

    To use GNU CC on VMS, you need the VMS driver programs gcc.exe, gcc.com, and gcc.cld. They are distributed with the VMS binaries (gcc-vms) rather than the GNU CC sources. GAS is also included in gcc-vms, as is Bison. !

    Once you have successfully built GNU CC with VAX C, you should use the resulting compiler to rebuild itself. Before doing this, be sure to restore the CC, CFLAGS, and LIBS definitions in make-cccp.com and make-cc1.com. The second generation compiler will be able to take advantage of many optimizations that must be suppressed when building with other compilers. !

!

Under previous versions of GNU CC, the generated code would occasionally give strange results when linked with the sharable VAXCRTL library. Now this should work. !

Even with this version, however, GNU CC itself should not be linked with the sharable VAXCRTL. The version of qsort in VAXCRTL has a bug (known to be present in VMS versions V4.6 through V5.5) which causes the compiler to fail. !

The executables are generated by make-cc1.com and make-cccp.com use the object library version of VAXCRTL in order to make use of the qsort routine in gcclib.olb. If you wish to link the compiler executables with the shareable image version of VAXCRTL, you should edit the file tm.h (created by vmsconfig.com) to define the macro QSORT_WORKAROUND. !

QSORT_WORKAROUND is always defined when GNU CC is compiled with VAX C, to avoid a problem in case gcclib.olb is not yet available.

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/specific.html gcc-3.2.3/INSTALL/specific.html *** gcc-3.2.2/INSTALL/specific.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/specific.html Tue Apr 22 06:56:33 2003 *************** *** 1,15 **** ! Host/Target specific installation notes for GCC ! ! ! ! ! !

P

lease read this document carefully before installing the GNU Compiler Collection on your machine. !

  • 1750a-*-*
  • a29k
  • a29k-*-bsd --- 1,17 ---- ! ! Host/Target specific installation notes for GCC ! ! ! ! ! !

    Host/Target specific installation notes for GCC

    ! Please read this document carefully before installing the GNU Compiler Collection on your machine. ! ! !
    !

    1750a-*-*

    !

    MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. !

    The MIL-STD-1750A cross configuration produces output for as1750, an assembler/linker available under the GNU General Public License for the 1750A. as1750 can be obtained at ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/. A similarly licensed simulator for the 1750A is available from same address. !

    You should ignore a fatal error during the building of libgcc (libgcc is not yet implemented for the 1750A.) !

    The as1750 assembler requires the file ms1750.inc, which is found in the directory gcc/config/1750a. !

    GCC produced the same sections as the Fairchild F9450 C Compiler, namely: !

    Normal !
    The program code section. !
    Static !
    The read/write (RAM) data section. !
    Konst !
    The read-only (ROM) constants section. !
    Init !
    Initialization section (code to copy KREL to SREL).
    !

    The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This means that type char is represented with a 16-bit word per character. The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by GCC. !

    !

    a29k

    !

    AMD Am29k-family processors. These are normally used in embedded applications. This configuration corresponds to AMD's standard calling sequence and binary interface and is compatible with other 29k tools. !

    AMD has abandoned this processor. All existing a29k targets are obsoleted in GCC 3.1. !

    You may need to make a variant of the file a29k.h for your particular configuration. !

    !

    a29k-*-bsd

    !

    AMD Am29050 used in a system running a variant of BSD Unix. !

    !

    alpha*-*-*

    !

    This section contains general configuration information for all alpha-based platforms using ELF (in particular, ignore this section for DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this section, please read all other sections that match your target. !

    We require binutils 2.11.2 or newer. Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. !

    !

    alpha*-dec-osf*

    !

    Systems using processors that implement the DEC Alpha architecture and are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. !

    Support for versions before alpha*-dec-osf4 is obsoleted in GCC 3.1. (These are the versions which identify themselves as DEC OSF/1.) !

    In Digital Unix V4.0, virtual memory exhausted bootstrap failures may be fixed by configuring with --with-gc=simple, reconfiguring Kernel Virtual Memory and Swap parameters per the /usr/sbin/sys_check Tuning Suggestions, or applying the patch in http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html. !

    In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not currently (2001-06-13) work with mips-tfile. As a workaround, we need to use the old assembler, invoked via the barely documented -oldas option. To bootstrap GCC, you either need to use the Compaq C Compiler: ! 

       % CC=cc srcdir/configure [options] [target]
!
    !

    or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: ! 

       % CC=gcc -Wa,-oldas srcdir/configure [options] [target]
!
    !

    As of GNU binutils 2.11.2, neither GNU as nor GNU ld are supported on Tru64 UNIX, so you must not configure GCC with --with-gnu-as or --with-gnu-ld. !

    The --enable-threads options isn't supported yet. A patch is in preparation for a future release. !

    GCC writes a .verstamp directive to the assembler output file unless it is built as a cross-compiler. It gets the version to use from the system header file /usr/include/stamp.h. If you install a new version of DEC Unix, you should rebuild GCC to pick up the new version stamp. !

    Note that since the Alpha is a 64-bit architecture, cross-compilers from 32-bit machines will not generate code as efficient as that generated when the compiler is running on a 64-bit machine because many optimizations that depend on being able to represent a word on the --- 114,245 ----

  • Older systems
! !
!

1750a-*-*

!

MIL-STD-1750A processors. This target is obsoleted in GCC 3.1. !

The MIL-STD-1750A cross configuration produces output for as1750, an assembler/linker available under the GNU General Public License for the 1750A. as1750 can be obtained at ftp://ftp.fta-berlin.de/pub/crossgcc/1750gals/. A similarly licensed simulator for the 1750A is available from same address. !

You should ignore a fatal error during the building of libgcc (libgcc is not yet implemented for the 1750A.) !

The as1750 assembler requires the file ms1750.inc, which is found in the directory gcc/config/1750a. !

GCC produced the same sections as the Fairchild F9450 C Compiler, namely: !

Normal !
The program code section. !
Static !
The read/write (RAM) data section. !
Konst !
The read-only (ROM) constants section. !
Init !
Initialization section (code to copy KREL to SREL).
!

The smallest addressable unit is 16 bits (BITS_PER_UNIT is 16). This means that type char is represented with a 16-bit word per character. The 1750A's "Load/Store Upper/Lower Byte" instructions are not used by GCC. !

!

a29k

!

AMD Am29k-family processors. These are normally used in embedded applications. This configuration corresponds to AMD's standard calling sequence and binary interface and is compatible with other 29k tools. !

AMD has abandoned this processor. All existing a29k targets are obsoleted in GCC 3.1. !

You may need to make a variant of the file a29k.h for your particular configuration. !

!

a29k-*-bsd

!

AMD Am29050 used in a system running a variant of BSD Unix. !

!

alpha*-*-*

!

This section contains general configuration information for all alpha-based platforms using ELF (in particular, ignore this section for DEC OSF/1, Digital UNIX and Tru64 UNIX). In addition to reading this section, please read all other sections that match your target. !

We require binutils 2.11.2 or newer. Previous binutils releases had a number of problems with DWARF 2 debugging information, not the least of which is incorrect linking of shared libraries. !

!

alpha*-dec-osf*

!

Systems using processors that implement the DEC Alpha architecture and are running the DEC/Compaq Unix (DEC OSF/1, Digital UNIX, or Compaq Tru64 UNIX) operating system, for example the DEC Alpha AXP systems. !

Support for versions before alpha*-dec-osf4 is obsoleted in GCC 3.1. (These are the versions which identify themselves as DEC OSF/1.) !

In Digital Unix V4.0, virtual memory exhausted bootstrap failures may be fixed by configuring with --with-gc=simple, reconfiguring Kernel Virtual Memory and Swap parameters per the /usr/sbin/sys_check Tuning Suggestions, or applying the patch in http://gcc.gnu.org/ml/gcc/2002-08/msg00822.html. !

In Tru64 UNIX V5.1, Compaq introduced a new assembler that does not currently (2001-06-13) work with mips-tfile. As a workaround, we need to use the old assembler, invoked via the barely documented -oldas option. To bootstrap GCC, you either need to use the Compaq C Compiler: ! 

        % CC=cc srcdir/configure [options] [target]
!
!

or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0: ! 

        % CC=gcc -Wa,-oldas srcdir/configure [options] [target]
!
!

As of GNU binutils 2.11.2, neither GNU as nor GNU ld are supported on Tru64 UNIX, so you must not configure GCC with --with-gnu-as or --with-gnu-ld. !

The --enable-threads options isn't supported yet. A patch is in preparation for a future release. !

GCC writes a .verstamp directive to the assembler output file unless it is built as a cross-compiler. It gets the version to use from the system header file /usr/include/stamp.h. If you install a new version of DEC Unix, you should rebuild GCC to pick up the new version stamp. !

Note that since the Alpha is a 64-bit architecture, cross-compilers from 32-bit machines will not generate code as efficient as that generated when the compiler is running on a 64-bit machine because many optimizations that depend on being able to represent a word on the *************** target in an integral value on the host *** 245,251 **** cross-compilers on the Alpha for 32-bit machines has only been tested in a few cases and may not work properly. !

make compare may fail on old versions of DEC Unix unless you add -save-temps to CFLAGS. On these systems, the name of the assembler input file is stored in the object file, and that makes comparison fail if it differs between the stage1 and --- 247,253 ---- cross-compilers on the Alpha for 32-bit machines has only been tested in a few cases and may not work properly. !

make compare may fail on old versions of DEC Unix unless you add -save-temps to CFLAGS. On these systems, the name of the assembler input file is stored in the object file, and that makes comparison fail if it differs between the stage1 and *************** unless the comparisons fail without that *** 256,267 **** -save-temps, you will have to manually delete the .i and .s files after each series of compilations. !

GCC now supports both the native (ECOFF) debugging format used by DBX and GDB and an encapsulated STABS format for use only with GDB. See the discussion of the --with-stabs option of configure above for more information on these formats and how to select them. !

There is a bug in DEC's assembler that produces incorrect line numbers for ECOFF format when the .align directive is used. To work around this problem, GCC will not emit such alignment directives while writing ECOFF format debugging information even if optimization is --- 258,269 ---- -save-temps, you will have to manually delete the .i and .s files after each series of compilations. !

GCC now supports both the native (ECOFF) debugging format used by DBX and GDB and an encapsulated STABS format for use only with GDB. See the discussion of the --with-stabs option of configure above for more information on these formats and how to select them. !

There is a bug in DEC's assembler that produces incorrect line numbers for ECOFF format when the .align directive is used. To work around this problem, GCC will not emit such alignment directives while writing ECOFF format debugging information even if optimization is *************** being performed. Unfortunately, this ha *** 269,343 **** side-effect that code addresses when -O is specified are different depending on whether or not -g is also specified. !

To avoid this behavior, specify -gstabs+ and use GDB instead of DBX. DEC is now aware of this problem with the assembler and hopes to provide a fix shortly. !

!

alphaev5-cray-unicosmk*

!

Cray T3E systems running Unicos/Mk. !

This port is incomplete and has many known bugs. We hope to improve the support for this target soon. Currently, only the C front end is supported, and it is not possible to build parallel applications. Cray modules are not supported; in particular, Craylibs are assumed to be in /opt/ctl/craylibs/craylibs. !

You absolutely must use GNU make on this platform. Also, you need to tell GCC where to find the assembler and the linker. The simplest way to do so is by providing --with-as and --with-ld to configure, e.g. ! 

    configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
!       --enable-languages=c
!
!

The comparison test during make bootstrap fails on Unicos/Mk because the assembler inserts timestamps into object files. You should be able to work around this by doing make all after getting this failure. !

!

arc-*-elf

!

Argonaut ARC processor. This configuration is intended for embedded systems. !

!

arm-*-aout

!

Advanced RISC Machines ARM-family processors. These are often used in embedded applications. There are no standard Unix configurations. This configuration corresponds to the basic instruction sequences and will produce a.out format object modules. !

You may need to make a variant of the file arm.h for your particular configuration. !

!

arm-*-elf

!

This configuration is intended for embedded systems. !

!

arm*-*-linux-gnu

!

We require GNU binutils 2.10 or newer. !

!

arm-*-riscix

!

The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix. This configuration is obsoleted in GCC 3.1. !

If you are running a version of RISC iX prior to 1.2 then you must specify the version number during configuration. Note that the assembler shipped with RISC iX does not support stabs debugging information; a new version of the assembler, with stabs support --- 271,345 ---- side-effect that code addresses when -O is specified are different depending on whether or not -g is also specified. !

To avoid this behavior, specify -gstabs+ and use GDB instead of DBX. DEC is now aware of this problem with the assembler and hopes to provide a fix shortly. !

!

alphaev5-cray-unicosmk*

!

Cray T3E systems running Unicos/Mk. !

This port is incomplete and has many known bugs. We hope to improve the support for this target soon. Currently, only the C front end is supported, and it is not possible to build parallel applications. Cray modules are not supported; in particular, Craylibs are assumed to be in /opt/ctl/craylibs/craylibs. !

You absolutely must use GNU make on this platform. Also, you need to tell GCC where to find the assembler and the linker. The simplest way to do so is by providing --with-as and --with-ld to configure, e.g. ! 

         configure --with-as=/opt/ctl/bin/cam --with-ld=/opt/ctl/bin/cld \
!            --enable-languages=c
!
!

The comparison test during make bootstrap fails on Unicos/Mk because the assembler inserts timestamps into object files. You should be able to work around this by doing make all after getting this failure. !

!

arc-*-elf

!

Argonaut ARC processor. This configuration is intended for embedded systems. !

!

arm-*-aout

!

Advanced RISC Machines ARM-family processors. These are often used in embedded applications. There are no standard Unix configurations. This configuration corresponds to the basic instruction sequences and will produce a.out format object modules. !

You may need to make a variant of the file arm.h for your particular configuration. !

!

arm-*-elf

!

This configuration is intended for embedded systems. !

!

arm*-*-linux-gnu

!

We require GNU binutils 2.10 or newer. !

!

arm-*-riscix

!

The ARM2 or ARM3 processor running RISC iX, Acorn's port of BSD Unix. This configuration is obsoleted in GCC 3.1. !

If you are running a version of RISC iX prior to 1.2 then you must specify the version number during configuration. Note that the assembler shipped with RISC iX does not support stabs debugging information; a new version of the assembler, with stabs support *************** included, is now available from Acorn an *** 345,465 **** ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z. To enable stabs debugging, pass --with-gnu-as to configure. !

You will need to install GNU sed before you can run configure. !

!

avr

!

ATMEL AVR-family micro controllers. These are used in embedded applications. There are no standard Unix configurations. See "AVR Options" in the main manual for the list of supported MCU types. !

Use configure --target=avr --enable-languages="c" to configure GCC. !

Further installation notes and other useful information about AVR tools can also be obtained from: !

!

We strongly recommend using binutils 2.11 or newer. !

The following error: ! 

  Error: register required
!
!

indicates that you should upgrade to a newer version of the binutils. !

!

c4x

!

Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal Processors. These are used in embedded applications. There are no standard Unix configurations. See "TMS320C3x/C4x Options" in the main manual for the list of supported MCU types. !

GCC can be configured as a cross compiler for both the C3x and C4x architectures on the same system. Use configure --target=c4x --enable-languages="c,c++" to configure. !

Further installation notes and other useful information about C4x tools can also be obtained from: !

!
!

CRIS

!

CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. !

See "CRIS Options" in the main manual for a list of CRIS-specific options. !

There are a few different CRIS targets: !

cris-axis-aout !
Old target. Includes a multilib for the elinux a.out-based target. No multilibs for newer architecture variants.
cris-axis-elf !
Mainly for monolithic embedded systems. Includes a multilib for the v10 core used in ETRAX 100 LX.
cris-axis-linux-gnu !
A GNU/Linux port for the CRIS architecture, currently targeting ETRAX 100 LX by default.
!

For cris-axis-aout and cris-axis-elf you need binutils 2.11 or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer. !

Pre-packaged tools can be obtained from ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More information about this platform is available at http://developer.axis.com/. !

!

DOS

!

Please have a look at our binaries page. !

You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. !

!

dsp16xx

!

A port to the AT&T DSP1610 family of processors. !

!

*-*-freebsd*

!

The version of binutils installed in /usr/bin is known to work unless otherwise specified in any per-architecture notes. However, binutils 2.12.1 or greater is known to improve overall testsuite results. !

For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All configuration support and files as shipped with GCC 2.95 are still in place. FreeBSD 2.2.7 has been known to bootstrap completely; however, it is unknown which version of binutils was used (it is assumed that it was the system copy in /usr/bin) and C++ EH failures were noted. !

Support for FreeBSD 1 is obsoleted in GCC 3.1. !

For FreeBSD using the ELF file format: DWARF 2 debugging is now the default for all CPU architectures. It had been the default on FreeBSD/alpha since its inception. You may use -gstabs instead of -g, if you really want the old debugging format. There are --- 347,467 ---- ftp://ftp.acorn.com/pub/riscix/as+xterm.tar.Z. To enable stabs debugging, pass --with-gnu-as to configure. !

You will need to install GNU sed before you can run configure. !

!

avr

!

ATMEL AVR-family micro controllers. These are used in embedded applications. There are no standard Unix configurations. See "AVR Options" in the main manual for the list of supported MCU types. !

Use configure --target=avr --enable-languages="c" to configure GCC. !

Further installation notes and other useful information about AVR tools can also be obtained from: !

!

We strongly recommend using binutils 2.11 or newer. !

The following error: ! 

       Error: register required
!
!

indicates that you should upgrade to a newer version of the binutils. !

!

c4x

!

Texas Instruments TMS320C3x and TMS320C4x Floating Point Digital Signal Processors. These are used in embedded applications. There are no standard Unix configurations. See "TMS320C3x/C4x Options" in the main manual for the list of supported MCU types. !

GCC can be configured as a cross compiler for both the C3x and C4x architectures on the same system. Use configure --target=c4x --enable-languages="c,c++" to configure. !

Further installation notes and other useful information about C4x tools can also be obtained from: !

!
!

CRIS

!

CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip series. These are used in embedded applications. !

See "CRIS Options" in the main manual for a list of CRIS-specific options. !

There are a few different CRIS targets: !

cris-axis-aout !
Old target. Includes a multilib for the elinux a.out-based target. No multilibs for newer architecture variants.
cris-axis-elf !
Mainly for monolithic embedded systems. Includes a multilib for the v10 core used in ETRAX 100 LX.
cris-axis-linux-gnu !
A GNU/Linux port for the CRIS architecture, currently targeting ETRAX 100 LX by default.
!

For cris-axis-aout and cris-axis-elf you need binutils 2.11 or newer. For cris-axis-linux-gnu you need binutils 2.12 or newer. !

Pre-packaged tools can be obtained from ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/. More information about this platform is available at http://developer.axis.com/. !

!

DOS

!

Please have a look at our binaries page. !

You cannot install GCC by itself on MSDOS; it will not compile under any MSDOS compiler except itself. You need to get the complete compilation package DJGPP, which includes binaries as well as sources, and includes all the necessary compilation tools and libraries. !

!

dsp16xx

!

A port to the AT&T DSP1610 family of processors. !

!

*-*-freebsd*

!

The version of binutils installed in /usr/bin is known to work unless otherwise specified in any per-architecture notes. However, binutils 2.12.1 or greater is known to improve overall testsuite results. !

For FreeBSD 1, FreeBSD 2 or any mutant a.out versions of FreeBSD 3: All configuration support and files as shipped with GCC 2.95 are still in place. FreeBSD 2.2.7 has been known to bootstrap completely; however, it is unknown which version of binutils was used (it is assumed that it was the system copy in /usr/bin) and C++ EH failures were noted. !

Support for FreeBSD 1 is obsoleted in GCC 3.1. !

For FreeBSD using the ELF file format: DWARF 2 debugging is now the default for all CPU architectures. It had been the default on FreeBSD/alpha since its inception. You may use -gstabs instead of -g, if you really want the old debugging format. There are *************** However, as a general user, do not attem *** 471,477 **** compiler with this release. Known to bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT. !

In principle, --enable-threads is now compatible with --enable-libgcj on FreeBSD. However, it has only been built and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0. The static --- 473,479 ---- compiler with this release. Known to bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2, 4.3, 4.4, 4.5-STABLE and 5-CURRENT. !

In principle, --enable-threads is now compatible with --enable-libgcj on FreeBSD. However, it has only been built and tested on i386-*-freebsd4.5 and alpha-*-freebsd5.0. The static *************** should properly complete the bootstrap). *** 488,578 **** supported by FreeBSD will require additional configuration tuning in, at the very least, both boehm-gc and libffi. !

Shared libgcc_s.so is now built and installed by default. !

!

elxsi-elxsi-bsd

!

The Elxsi's C compiler has known limitations that prevent it from compiling GCC. Please contact mrs@wrs.com for more details. !

Support for this processor is obsoleted in GCC 3.1. !

!

h8300-hms

!

Hitachi H8/300 series of processors. !

Please have a look at our binaries page. !

The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. !

!

hppa*-hp-hpux*

!

We highly recommend using gas/binutils 2.8 or newer on all hppa platforms; you may encounter a variety of problems when using the HP assembler. The HP assembler does not work with the hppa64-hp-hpux11* port. !

Specifically, -g does not work on HP-UX (since that system uses a peculiar debugging format which GCC does not know about), unless you use GAS and GDB and configure GCC with the --with-gnu-as and ! --with-as=... options. !

If you wish to use the pa-risc 2.0 architecture support with a 32-bit runtime, you must use either the HP assembler, gas/binutils 2.11 or newer, or a recent snapshot of gas. !

More specific information to hppa*-hp-hpux* targets follows. !

!

hppa*-hp-hpux9

!

The HP assembler has major problems on this platform. We've tried to work around the worst of the problems. However, those workarounds may be causing linker crashes in some circumstances; the workarounds also probably prevent shared libraries from working. Use the GNU assembler to avoid these problems. !

The configuration scripts for GCC will also trigger a bug in the hpux9 shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to /bin/ksh in your environment. !

!

hppa*-hp-hpux10

!

For hpux10.20, we highly recommend you pick up the latest sed patch PHCO_19798 from HP. HP has two sites which provide patches free of charge: !

!

The HP assembler on these systems is much better than the hpux9 assembler, but still has some problems. Most notably the assembler inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a make bootstrap. You should be able to continue by saying make all after getting the failure from make bootstrap. !

!

hppa*-hp-hpux11

!

GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there are two distinct ports. The hppa2.0w-hp-hpux11* port generates code for the 32-bit pa-risc runtime architecture. It uses the HP linker and is currently the default selected by config.guess. The --- 490,580 ---- supported by FreeBSD will require additional configuration tuning in, at the very least, both boehm-gc and libffi. !

Shared libgcc_s.so is now built and installed by default. !

!

elxsi-elxsi-bsd

!

The Elxsi's C compiler has known limitations that prevent it from compiling GCC. Please contact mrs@wrs.com for more details. !

Support for this processor is obsoleted in GCC 3.1. !

!

h8300-hms

!

Hitachi H8/300 series of processors. !

Please have a look at our binaries page. !

The calling convention and structure layout has changed in release 2.6. All code must be recompiled. The calling convention now passes the first three arguments in function calls in registers. Structures are no longer a multiple of 2 bytes. !

!

hppa*-hp-hpux*

!

We highly recommend using gas/binutils 2.8 or newer on all hppa platforms; you may encounter a variety of problems when using the HP assembler. The HP assembler does not work with the hppa64-hp-hpux11* port. !

Specifically, -g does not work on HP-UX (since that system uses a peculiar debugging format which GCC does not know about), unless you use GAS and GDB and configure GCC with the --with-gnu-as and ! --with-as=... options. !

If you wish to use the pa-risc 2.0 architecture support with a 32-bit runtime, you must use either the HP assembler, gas/binutils 2.11 or newer, or a recent snapshot of gas. !

More specific information to hppa*-hp-hpux* targets follows. !

!

hppa*-hp-hpux9

!

The HP assembler has major problems on this platform. We've tried to work around the worst of the problems. However, those workarounds may be causing linker crashes in some circumstances; the workarounds also probably prevent shared libraries from working. Use the GNU assembler to avoid these problems. !

The configuration scripts for GCC will also trigger a bug in the hpux9 shell. To avoid this problem set CONFIG_SHELL to /bin/ksh and SHELL to /bin/ksh in your environment. !

!

hppa*-hp-hpux10

!

For hpux10.20, we highly recommend you pick up the latest sed patch PHCO_19798 from HP. HP has two sites which provide patches free of charge: !

!

The HP assembler on these systems is much better than the hpux9 assembler, but still has some problems. Most notably the assembler inserts timestamps into each object file it creates, causing the 3-stage comparison test to fail during a make bootstrap. You should be able to continue by saying make all after getting the failure from make bootstrap. !

!

hppa*-hp-hpux11

!

GCC 3.0 and up support HP-UX 11. On 64-bit capable systems, there are two distinct ports. The hppa2.0w-hp-hpux11* port generates code for the 32-bit pa-risc runtime architecture. It uses the HP linker and is currently the default selected by config.guess. The *************** pa-risc 2.0 architecture. It must be ex *** 581,600 **** --host=hppa64-hp-hpux11* configure option. Different prefixes must be used if both ports are to be installed on the same system. !

You must use GNU binutils 2.11 or above with the 32-bit port. Thread support is not currently implemented, so --enable-threads does not work. See: !

!

GCC 2.95.x is not supported under HP-UX 11 and cannot be used to compile GCC 3.0 and up. Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. !

GNU binutils 2.13 or later is recommended with the 64-bit port. The HP assembler is not supported. It is highly recommended that the GNU linker be used as well. Either binutils must be built prior to gcc, or a binary distribution of gcc or binutils must be --- 583,602 ---- --host=hppa64-hp-hpux11* configure option. Different prefixes must be used if both ports are to be installed on the same system. !

You must use GNU binutils 2.11 or above with the 32-bit port. Thread support is not currently implemented, so --enable-threads does not work. See: !

!

GCC 2.95.x is not supported under HP-UX 11 and cannot be used to compile GCC 3.0 and up. Refer to binaries for information about obtaining precompiled GCC binaries for HP-UX. !

GNU binutils 2.13 or later is recommended with the 64-bit port. The HP assembler is not supported. It is highly recommended that the GNU linker be used as well. Either binutils must be built prior to gcc, or a binary distribution of gcc or binutils must be *************** differences in semantics between traditi *** 606,630 **** have been problems reported with various binary distributions. This port still is undergoing significant development. !

!

i370-*-*

!

This port is very preliminary and has many known bugs. We hope to have a higher-quality port for this machine soon. !

!

*-*-linux-gnu

!

If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install out-of-the-box. You'll get compile errors while building libstdc++. The patch glibc-2.2.patch, that is to be applied in the GCC source tree, fixes the compatibility problems. !

!

Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync since the latest exception handling changes for GCC. Compiling glibc with GCC 3.0 will give a binary incompatible glibc and therefore cause lots of problems and might make your system completly unusable. This --- 608,632 ---- have been problems reported with various binary distributions. This port still is undergoing significant development. !

!

i370-*-*

!

This port is very preliminary and has many known bugs. We hope to have a higher-quality port for this machine soon. !

!

*-*-linux-gnu

!

If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install out-of-the-box. You'll get compile errors while building libstdc++. The patch glibc-2.2.patch, that is to be applied in the GCC source tree, fixes the compatibility problems. !

!

Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync since the latest exception handling changes for GCC. Compiling glibc with GCC 3.0 will give a binary incompatible glibc and therefore cause lots of problems and might make your system completly unusable. This *************** strongly advise to wait for glibc 2.2.4 *** 633,711 **** glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc 2.2.3 with GCC 3.0, just do not try to recompile it. !

!

i?86-*-linux*oldld

!

Use this configuration to generate a.out binaries on Linux-based GNU systems if you do not have gas/binutils version 2.5.2 or later installed. !

This configuration is obsoleted in GCC 3.1. !

!

i?86-*-linux*aout

!

Use this configuration to generate a.out binaries on Linux-based GNU systems. This configuration is being superseded. You must use gas/binutils version 2.5.2 or later. !

!

i?86-*-linux*

!

You will need binutils 2.9.1.0.15 or newer for exception handling to work. !

If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl. !

!

i?86-*-sco

!

Compilation with RCC is recommended. Also, it may be a good idea to link with GNU malloc instead of the malloc that comes with the system. !

!

i?86-*-sco3.2v4

!

Use this configuration for SCO release 3.2 version 4. !

!

i?86-*-sco3.2v5*

!

Use this for the SCO OpenServer Release 5 family of operating systems. !

Unlike earlier versions of GCC, the ability to generate COFF with this target is no longer provided. !

Earlier versions of GCC emitted DWARF 1 when generating ELF to allow the system debugger to be used. That support was too burdensome to maintain. GCC now emits only DWARF 2 for this target. This means you may use either the UDK debugger or GDB to debug programs built by this version of GCC. !

Use of the -march=pentiumpro flag can result in unrecognized opcodes when using the native assembler on OS versions before 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in that version.) While it's rather rare to see these emitted by GCC yet, errors of the basic form: ! 

  /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
!   /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
!
!

are symptoms of this problem. You may work around this by not building affected files with that flag, by using the GNU assembler, or by using the assembler provided with the current version of the OS. Users of GNU assembler should see the note below for hazards on doing so. !

The native SCO assembler that is provided with the OS at no charge is normally required. If, however, you must be able to use the GNU assembler (perhaps you're compiling code with asms that require GAS syntax) you may configure this package using the flags --- 635,713 ---- glibc 2.2.4 whether patches for GCC 3.0 are needed. You can use glibc 2.2.3 with GCC 3.0, just do not try to recompile it. !

!

i?86-*-linux*oldld

!

Use this configuration to generate a.out binaries on Linux-based GNU systems if you do not have gas/binutils version 2.5.2 or later installed. !

This configuration is obsoleted in GCC 3.1. !

!

i?86-*-linux*aout

!

Use this configuration to generate a.out binaries on Linux-based GNU systems. This configuration is being superseded. You must use gas/binutils version 2.5.2 or later. !

!

i?86-*-linux*

!

You will need binutils 2.9.1.0.15 or newer for exception handling to work. !

If you receive Signal 11 errors when building on GNU/Linux, then it is possible you have a hardware problem. Further information on this can be found on www.bitwizard.nl. !

!

i?86-*-sco

!

Compilation with RCC is recommended. Also, it may be a good idea to link with GNU malloc instead of the malloc that comes with the system. !

!

i?86-*-sco3.2v4

!

Use this configuration for SCO release 3.2 version 4. !

!

i?86-*-sco3.2v5*

!

Use this for the SCO OpenServer Release 5 family of operating systems. !

Unlike earlier versions of GCC, the ability to generate COFF with this target is no longer provided. !

Earlier versions of GCC emitted DWARF 1 when generating ELF to allow the system debugger to be used. That support was too burdensome to maintain. GCC now emits only DWARF 2 for this target. This means you may use either the UDK debugger or GDB to debug programs built by this version of GCC. !

Use of the -march=pentiumpro flag can result in unrecognized opcodes when using the native assembler on OS versions before 5.0.6. (Support for P6 opcodes was added to the native ELF assembler in that version.) While it's rather rare to see these emitted by GCC yet, errors of the basic form: ! 

       /usr/tmp/ccaNlqBc.s:22:unknown instruction: fcomip
!        /usr/tmp/ccaNlqBc.s:50:unknown instruction: fucomip
!
!

are symptoms of this problem. You may work around this by not building affected files with that flag, by using the GNU assembler, or by using the assembler provided with the current version of the OS. Users of GNU assembler should see the note below for hazards on doing so. !

The native SCO assembler that is provided with the OS at no charge is normally required. If, however, you must be able to use the GNU assembler (perhaps you're compiling code with asms that require GAS syntax) you may configure this package using the flags *************** require GAS syntax) you may configure th *** 713,730 **** use a recent version of GNU binutils; versions past 2.9.1 seem to work well. !

In general, the --with-gnu-as option isn't as well tested as the native assembler. !

Look in gcc/config/i386/sco5.h (search for "messy") for additional OpenServer-specific flags. !

Systems based on OpenServer before 5.0.4 (uname -X will tell you what you're running) require TLS597 from ftp://ftp.sco.com/TLS/ for C++ constructors and destructors to work right. !

The system linker in (at least) 5.0.4 and 5.0.5 will sometimes do the wrong thing for a construct that GCC will emit for PIC code. This can be seen as execution testsuite failures when using -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c. --- 715,732 ---- use a recent version of GNU binutils; versions past 2.9.1 seem to work well. !

In general, the --with-gnu-as option isn't as well tested as the native assembler. !

Look in gcc/config/i386/sco5.h (search for "messy") for additional OpenServer-specific flags. !

Systems based on OpenServer before 5.0.4 (uname -X will tell you what you're running) require TLS597 from ftp://ftp.sco.com/TLS/ for C++ constructors and destructors to work right. !

The system linker in (at least) 5.0.4 and 5.0.5 will sometimes do the wrong thing for a construct that GCC will emit for PIC code. This can be seen as execution testsuite failures when using -fPIC on 921215-1.c, 931002-1.c, nestfunc-1.c, and gcov-1.c. *************** available. You must install both *** 733,739 **** ftp://ftp.sco.com/Supplements/rs505a/ and OSS499A. !

The dynamic linker in OpenServer 5.0.5 (earlier versions may show the same problem) aborts on certain G77-compiled programs. It's particularly likely to be triggered by building Fortran code with the -fPIC flag. Although it's conceivable that the error could be triggered by other --- 735,741 ---- ftp://ftp.sco.com/Supplements/rs505a/ and OSS499A. !

The dynamic linker in OpenServer 5.0.5 (earlier versions may show the same problem) aborts on certain G77-compiled programs. It's particularly likely to be triggered by building Fortran code with the -fPIC flag. Although it's conceivable that the error could be triggered by other *************** backtrace with a fault occurring in /usr/lib/ld.so.1. This problem has been reported to SCO engineering and will hopefully be addressed in later releases. !

!

i?86-*-udk

!

This target emulates the SCO Universal Development Kit and requires that package be installed. (If it is installed, you will have a /udk/usr/ccs/bin/cc file present.) It's very much like the i?86-*-unixware7* target --- 749,759 ---- running as /usr/lib/ld.so.1. This problem has been reported to SCO engineering and will hopefully be addressed in later releases. !

!

i?86-*-udk

!

This target emulates the SCO Universal Development Kit and requires that package be installed. (If it is installed, you will have a /udk/usr/ccs/bin/cc file present.) It's very much like the i?86-*-unixware7* target *************** default compiler such as OpenServer 5 or *** 760,877 **** generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, with the same warnings and caveats as the SCO UDK. !

This target is a little tricky to build because we have to distinguish it from the native tools (so it gets headers, startups, and libraries from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this: ! 

    CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure \
!       --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
!
!

You should substitute i686 in the above command with the appropriate processor for your host. !

After the usual make bootstrap and make install, you can then access the UDK-targeted GCC tools by adding udk- before the commonly known name. For example, to invoke the C compiler, you would use udk-gcc. They will coexist peacefully with any native-target GCC tools you may have installed. !

!

i?86-*-isc

!

This configuration is obsoleted in GCC 3.1. !

It may be a good idea to link with GNU malloc instead of the malloc that comes with the system. !

In ISC version 4.1, sed core dumps when building deduced.h. Use the version of sed from version 4.0. !

!

i?86-ibm-aix

!

This configuration is obsoleted in GCC 3.1. !

You need to use GAS version 2.1 or later, and LD from GNU binutils version 2.2 or later. !

!

i?86-sequent-bsd

!

This configuration is obsoleted in GCC 3.1. !

Go to the Berkeley universe before compiling. !

!

i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*

!

This configuration is obsoleted in GCC 3.1. !

You must install GNU sed before running configure. !

The fixproto shell script may trigger a bug in the system shell. If you encounter this problem, upgrade your operating system or use bash (the GNU shell) to run fixproto. !

!

i860-intel-osf*

!

All support for the i860 processor is obsoleted in GCC 3.1. !

On the Intel Paragon (an i860 machine), if you are using operating system version 1.0, you will get warnings or errors about redefinition of va_arg when you build GCC. !

If this happens, then you need to link most programs with the library iclib.a. You must also modify stdio.h as follows: before the lines ! 

#if     defined(__i860__) && !defined(_VA_LIST)
! #include <va_list.h>
!

insert the line ! 

#if __PGC__
!

and after the lines ! 

extern int  vprintf(const char *, va_list );
! extern int  vsprintf(char *, const char *, va_list );
! #endif
!

insert the line ! 

#endif /* __PGC__ */
!
!

These problems don't exist in operating system version 1.1. !

!

ia64-*-linux

!

IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. !

The toolchain is not completely finished, so requirements will continue to change. GCC 3.0.1 and later require glibc 2.2.4. GCC 3.0.2 requires binutils from 2001-09-05 or later. GCC 3.0.1 requires binutils 2.11.1 or later. !

None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. --- 762,879 ---- generate binaries that will run on OpenServer, Unixware 2, or Unixware 7, with the same warnings and caveats as the SCO UDK. !

This target is a little tricky to build because we have to distinguish it from the native tools (so it gets headers, startups, and libraries from the right place) while making the tools not think we're actually building a cross compiler. The easiest way to do this is with a configure command like this: ! 

         CC=/udk/usr/ccs/bin/cc /your/path/to/gcc/configure \
!            --host=i686-pc-udk --target=i686-pc-udk --program-prefix=udk-
!
!

You should substitute i686 in the above command with the appropriate processor for your host. !

After the usual make bootstrap and make install, you can then access the UDK-targeted GCC tools by adding udk- before the commonly known name. For example, to invoke the C compiler, you would use udk-gcc. They will coexist peacefully with any native-target GCC tools you may have installed. !

!

i?86-*-isc

!

This configuration is obsoleted in GCC 3.1. !

It may be a good idea to link with GNU malloc instead of the malloc that comes with the system. !

In ISC version 4.1, sed core dumps when building deduced.h. Use the version of sed from version 4.0. !

!

i?86-ibm-aix

!

This configuration is obsoleted in GCC 3.1. !

You need to use GAS version 2.1 or later, and LD from GNU binutils version 2.2 or later. !

!

i?86-sequent-bsd

!

This configuration is obsoleted in GCC 3.1. !

Go to the Berkeley universe before compiling. !

!

i?86-sequent-ptx1*, i?86-sequent-ptx2*, i?86-sequent-sysv3*

!

This configuration is obsoleted in GCC 3.1. !

You must install GNU sed before running configure. !

The fixproto shell script may trigger a bug in the system shell. If you encounter this problem, upgrade your operating system or use bash (the GNU shell) to run fixproto. !

!

i860-intel-osf*

!

All support for the i860 processor is obsoleted in GCC 3.1. !

On the Intel Paragon (an i860 machine), if you are using operating system version 1.0, you will get warnings or errors about redefinition of va_arg when you build GCC. !

If this happens, then you need to link most programs with the library iclib.a. You must also modify stdio.h as follows: before the lines ! 

     #if     defined(__i860__) && !defined(_VA_LIST)
!      #include <va_list.h>
!

insert the line ! 

     #if __PGC__
!

and after the lines ! 

     extern int  vprintf(const char *, va_list );
!      extern int  vsprintf(char *, const char *, va_list );
!      #endif
!

insert the line ! 

     #endif /* __PGC__ */
!
!

These problems don't exist in operating system version 1.1. !

!

ia64-*-linux

!

IA-64 processor (also known as IPF, or Itanium Processor Family) running GNU/Linux. !

The toolchain is not completely finished, so requirements will continue to change. GCC 3.0.1 and later require glibc 2.2.4. GCC 3.0.2 requires binutils from 2001-09-05 or later. GCC 3.0.1 requires binutils 2.11.1 or later. !

None of the following versions of GCC has an ABI that is compatible with any of the other versions in this list, with the exception that Red Hat 2.96 and Trillian 000171 are compatible with each other: 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717. *************** GCC 3.0.2 is recommended for compiling l *** 882,907 **** GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major ABI changes are expected. !

!

*-lynx-lynxos

!

LynxOS 2.2 and earlier comes with GCC 1.x already installed as /bin/gcc. You should compile with this instead of /bin/cc. You can tell GCC to use the GNU assembler and linker, by specifying --with-gnu-as --with-gnu-ld when configuring. These will produce COFF format object files and executables; otherwise GCC will use the installed tools, which produce a.out format executables. !

!

*-ibm-aix*

!

AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or newer is recommended to build on this platform. !

Errors involving alloca when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the build, the native AIX compiler must be invoked as cc --- 884,909 ---- GCC 3.0.2 is believed to be fully ABI compliant, and hence no more major ABI changes are expected. !

!

*-lynx-lynxos

!

LynxOS 2.2 and earlier comes with GCC 1.x already installed as /bin/gcc. You should compile with this instead of /bin/cc. You can tell GCC to use the GNU assembler and linker, by specifying --with-gnu-as --with-gnu-ld when configuring. These will produce COFF format object files and executables; otherwise GCC will use the installed tools, which produce a.out format executables. !

!

*-ibm-aix*

!

AIX Make frequently has problems with GCC makefiles. GNU Make 3.76 or newer is recommended to build on this platform. !

Errors involving alloca when building GCC generally are due to an incorrect definition of CC in the Makefile or mixing files compiled with the native C compiler and GCC. During the stage1 phase of the build, the native AIX compiler must be invoked as cc *************** does not provide a definition that will *** 912,927 **** If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). !

The GNU Assembler incorrectly reports that it supports WEAK symbols on AIX which causes GCC to try to utilize weak symbol functionality which is not really supported on the platform. The native as and ld still are recommended. The native AIX tools do interoperate with GCC. !

Building libstdc++.a requires a fix for a AIX Assembler bug APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). !

libstdc++ in GCC 3.2 increments the major version number of the shared object and GCC installation places the libstdc++.a shared library in a common location which will overwrite the GCC 3.1 version of the shared library. Applications either need to be --- 914,929 ---- If this error occurs during stage2 or later, then the problem most likely is the version of Make (see above). !

The GNU Assembler incorrectly reports that it supports WEAK symbols on AIX which causes GCC to try to utilize weak symbol functionality which is not really supported on the platform. The native as and ld still are recommended. The native AIX tools do interoperate with GCC. !

Building libstdc++.a requires a fix for a AIX Assembler bug APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). !

libstdc++ in GCC 3.2 increments the major version number of the shared object and GCC installation places the libstdc++.a shared library in a common location which will overwrite the GCC 3.1 version of the shared library. Applications either need to be *************** be installed for runtime dynamic loading *** 932,960 **** set the F_LOADONLY flag in the shared object for each multilib libstdc++.a installed: !

Extract the shared object from each the GCC 3.1 libstdc++.a archive: ! 

   % ar -x libstdc++.a libstdc++.so.4
!
!

Enable the F_LOADONLY flag so that the shared object will be available for runtime dynamic loading, but not linking: ! 

   % strip -e libstdc++.so.4
!
!

Archive the runtime-only shared object in the GCC 3.2 libstdc++.a archive: ! 

   % ar -q libstdc++.a libstdc++.so.4
!
!

Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. !

AIX 4.3 utilizes a "large format" archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during --- 934,962 ---- set the F_LOADONLY flag in the shared object for each multilib libstdc++.a installed: !

Extract the shared object from each the GCC 3.1 libstdc++.a archive: ! 

        % ar -x libstdc++.a libstdc++.so.4
!
!

Enable the F_LOADONLY flag so that the shared object will be available for runtime dynamic loading, but not linking: ! 

        % strip -e libstdc++.so.4
!
!

Archive the runtime-only shared object in the GCC 3.2 libstdc++.a archive: ! 

        % ar -q libstdc++.a libstdc++.so.4
!
!

Linking executables and shared libraries may produce warnings of duplicate symbols. The assembly files generated by GCC for AIX always have included multiple symbol definitions for certain global variable and function declarations in the original program. The warnings should not prevent the linker from producing a correct library or runnable executable. !

AIX 4.3 utilizes a "large format" archive to support both 32-bit and 64-bit object modules. The routines provided in AIX 4.3.0 and AIX 4.3.1 to parse archive libraries did not handle the new format correctly. These routines are used by GCC and result in error messages during *************** option of the archive command may be use *** 964,970 **** objects using the original "small format". A correct version of the routines is shipped with AIX 4.3.2 and above. !

Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is --- 966,972 ---- objects using the original "small format". A correct version of the routines is shipped with AIX 4.3.2 and above. !

Some versions of the AIX binder (linker) can fail with a relocation overflow severe error when the -bbigtoc option is used to link GCC-produced object files into an executable that overflows the TOC. A fix for APAR IX75823 (OVERFLOW DURING LINK WHEN USING GCC AND -BBIGTOC) is *************** available from IBM Customer Support and *** 972,990 **** techsupport.services.ibm.com website as PTF U455193. !

The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. !

The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. !

AIX provides National Language Support (NLS). Compilers and assemblers use NLS to support locale-specific representations of various data formats including floating-point numbers (e.g., . vs , for separating decimal fractions). There have been problems reported where --- 974,992 ---- techsupport.services.ibm.com website as PTF U455193. !

The AIX 4.3.2.1 linker (bos.rte.bind_cmds Level 4.3.2.1) will dump core with a segmentation fault when invoked by any version of GCC. A fix for APAR IX87327 is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U461879. This fix is incorporated in AIX 4.3.3 and above. !

The initial assembler shipped with AIX 4.3.0 generates incorrect object files. A fix for APAR IX74254 (64BIT DISASSEMBLED OUTPUT FROM COMPILER FAILS TO ASSEMBLE/BIND) is available from IBM Customer Support and from its techsupport.services.ibm.com website as PTF U453956. This fix is incorporated in AIX 4.3.1 and above. !

AIX provides National Language Support (NLS). Compilers and assemblers use NLS to support locale-specific representations of various data formats including floating-point numbers (e.g., . vs , for separating decimal fractions). There have been problems reported where *************** GCC does not produce the same floating-p *** 992,1078 **** expects. If one encounters this problem, set the LANG environment variable to C or En_US. !

By default, GCC for AIX 4.1 and above produces code that can be used on both Power or PowerPC processors. !

A default can be specified with the -mcpu=cpu_type ! switch and using the configure option --with-cpu-cpu_type. !

!

m32r-*-elf

!

Mitsubishi M32R processor. This configuration is intended for embedded systems. !

!

m68000-hp-bsd

!

HP 9000 series 200 running BSD. Note that the C compiler that comes with this system cannot compile GCC; contact law@cygnus.com to get binaries of GCC for bootstrapping. !

!

m6811-elf

!

Motorola 68HC11 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. !

!

m6812-elf

!

Motorola 68HC12 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. !

!

m68k-altos

!

Altos 3068. This configuration is obsoleted in GCC 3.1. !

You must use the GNU assembler, linker and debugger. Also, you must fix a kernel bug. !

!

m68k-apple-aux

!

Apple Macintosh running A/UX. This configuration is obsoleted in GCC 3.1. !

You may configure GCC to use either the system assembler and linker or the GNU assembler and linker. You should use the GNU configuration if you can, especially if you also want to use G++. You enable that configuration with the --with-gnu-as and --with-gnu-ld options to configure. !

Note the C compiler that comes with this system cannot compile GCC. You can find binaries of GCC for bootstrapping on jagubox.gsfc.nasa.gov. You will also a patched version of /bin/ld there that raises some of the arbitrary limits found in the original. !

!

m68k-att-sysv

!

AT&T 3b1, a.k.a. 7300 PC. This version of GCC cannot be compiled with the system C compiler, which is too buggy. You will need to get a previous version of GCC and use it to bootstrap. Binaries are available from the OSU-CIS archive, at ftp://archive.cis.ohio-state.edu/pub/att7300/. !

!

m68k-bull-sysv

!

Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. This configuration is obsoleted in GCC 3.1. !

GCC works either with native assembler or GNU assembler. You can use GNU assembler with native COFF generation by providing --with-gnu-as to the configure script or use GNU assembler with stabs-in-COFF encapsulation --- 994,1080 ---- expects. If one encounters this problem, set the LANG environment variable to C or En_US. !

By default, GCC for AIX 4.1 and above produces code that can be used on both Power or PowerPC processors. !

A default can be specified with the -mcpu=cpu_type ! switch and using the configure option --with-cpu-cpu_type. !

!

m32r-*-elf

!

Mitsubishi M32R processor. This configuration is intended for embedded systems. !

!

m68000-hp-bsd

!

HP 9000 series 200 running BSD. Note that the C compiler that comes with this system cannot compile GCC; contact law@cygnus.com to get binaries of GCC for bootstrapping. !

!

m6811-elf

!

Motorola 68HC11 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. !

!

m6812-elf

!

Motorola 68HC12 family micro controllers. These are used in embedded applications. There are no standard Unix configurations. !

!

m68k-altos

!

Altos 3068. This configuration is obsoleted in GCC 3.1. !

You must use the GNU assembler, linker and debugger. Also, you must fix a kernel bug. !

!

m68k-apple-aux

!

Apple Macintosh running A/UX. This configuration is obsoleted in GCC 3.1. !

You may configure GCC to use either the system assembler and linker or the GNU assembler and linker. You should use the GNU configuration if you can, especially if you also want to use G++. You enable that configuration with the --with-gnu-as and --with-gnu-ld options to configure. !

Note the C compiler that comes with this system cannot compile GCC. You can find binaries of GCC for bootstrapping on jagubox.gsfc.nasa.gov. You will also a patched version of /bin/ld there that raises some of the arbitrary limits found in the original. !

!

m68k-att-sysv

!

AT&T 3b1, a.k.a. 7300 PC. This version of GCC cannot be compiled with the system C compiler, which is too buggy. You will need to get a previous version of GCC and use it to bootstrap. Binaries are available from the OSU-CIS archive, at ftp://archive.cis.ohio-state.edu/pub/att7300/. !

!

m68k-bull-sysv

!

Bull DPX/2 series 200 and 300 with BOS-2.00.45 up to BOS-2.01. This configuration is obsoleted in GCC 3.1. !

GCC works either with native assembler or GNU assembler. You can use GNU assembler with native COFF generation by providing --with-gnu-as to the configure script or use GNU assembler with stabs-in-COFF encapsulation *************** by providing --with-gnu-as --stabs *** 1080,1259 **** assembler or for availability of the DPX/2 port of GAS, contact F.Pierresteguy@frcl.bull.fr. !

!

m68k-crds-unos

!

Use configure unos for building on Unos. !

The Unos assembler is named casm instead of as. For some strange reason linking /bin/as to /bin/casm changes the behavior, and does not work. So, when installing GCC, you should install the following script as as in the subdirectory where the passes of GCC are installed: ! 

#!/bin/sh
! casm $*
!
!

The default Unos library is named libunos.a instead of libc.a. To allow GCC to function, either change all references to -lc in gcc.c to -lunos or link /lib/libc.a to /lib/libunos.a. !

When compiling GCC with the standard compiler, to overcome bugs in the support of alloca, do not use -O when making stage 2. Then use the stage 2 compiler with -O to make the stage 3 compiler. This compiler will have the same characteristics as the usual stage 2 compiler on other systems. Use it to make a stage 4 compiler and compare that with stage 3 to verify proper compilation. !

(Perhaps simply defining ALLOCA in x-crds as described in the comments there will make the above paragraph superfluous. Please inform us of whether this works.) !

Unos uses memory segmentation instead of demand paging, so you will need a lot of memory. 5 Mb is barely enough if no other tasks are running. If linking cc1 fails, try putting the object files into a library and linking from that library. !

!

m68k-hp-hpux

!

HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in the assembler that prevents compilation of GCC. This bug manifests itself during the first stage of compilation, while building libgcc2.a: ! 

_floatdisf
! cc1: warning: `-g' option not supported on this version of GCC
! cc1: warning: `-g1' option not supported on this version of GCC
! ./xgcc: Internal compiler error: program as got fatal signal 11
!
!

A patched version of the assembler is available as the file ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler. If you have HP software support, the patch can also be obtained directly from HP, as described in the following note: !

This is the patched assembler, to patch SR#1653-010439, where the assembler aborts on floating point constants. !

The bug is not really in the assembler, but in the shared library version of the function "cvtnum(3c)". The bug on "cvtnum(3c)" is SR#4701-078451. Anyway, the attached assembler uses the archive library version of "cvtnum(3c)" and thus does not exhibit the bug.

!

This patch is also known as PHCO_4484. !

In addition, if you wish to use gas, you must use gas version 2.1 or later, and you must use the GNU linker version 2.1 or later. Earlier versions of gas relied upon a program which converted the gas output into the native HP-UX format, but that program has not been kept up to date. gdb does not understand that native HP-UX format, so you must use gas if you wish to use gdb. !

On HP-UX version 8.05, but not on 8.07 or more recent versions, the fixproto shell script triggers a bug in the system shell. If you encounter this problem, upgrade your operating system or use BASH (the GNU shell) to run fixproto. This bug will cause the fixproto program to report an error of the form: ! 

./fixproto: sh internal 1K buffer overflow
!
!

To fix this, you can also change the first line of the fixproto script to look like: ! 

#!/bin/ksh
!
!
!

m68k-*-nextstep*

!

These configurations are obsoleted in GCC 3.1. !

Current GCC versions probably do not work on version 2 of the NeXT operating system. !

On NeXTStep 3.0, the Objective-C compiler does not work, due, apparently, to a kernel bug that it happens to trigger. This problem does not happen on 3.1. !

You absolutely must use GNU sed and GNU make on this platform. !

On NeXTSTEP 3.x where x < 3 the build of GCC will abort during stage1 with an error message like this: ! 

  _eh
!   /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
!   /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
!   valued 95 (_).
!
!

The reason for this is the fact that NeXT's assembler for these versions of the operating system does not support the .section pseudo op that's needed for full C++ exception functionality. !

As NeXT's assembler is a derived work from GNU as, a free replacement that does can be obtained at ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz. !

If you try to build the integrated C++ & C++ runtime libraries on this system you will run into trouble with include files. The way to get around this is to use the following sequence. Note you must have write permission to the directory prefix you specified in the configuration process of GCC for this sequence to work. ! 

  cd bld-gcc
!   make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
!   cd gcc
!   make bootstrap
!   make install-headers-tar
!   cd ..
!   make bootstrap3
!
!
!

m68k-ncr-*

!

On the Tower models 4n0 and 6n0, by default a process is not allowed to have more than one megabyte of memory. GCC cannot compile itself (or many other programs) with -O in that much memory. !

To solve this problem, reconfigure the kernel adding the following line to the configuration file: ! 

MAXUMEM = 4096
!
!
!

m68k-sun

!

Sun 3. We do not provide a configuration file to use the Sun FPA by default, because programs that establish signal handlers for floating point traps inherently cannot work with the FPA. !

!

m68k-sun-sunos4.1.1

!

It is reported that you may need the GNU assembler on this platform. !

!

m88k-*-svr3

!

Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port. These configurations are obsoleted in GCC 3.1. !

These systems tend to use the Green Hills C, revision 1.8.5, as the standard C compiler. There are apparently bugs in this compiler that result in object files differences between stage 2 and stage 3. If this happens, make the stage 4 compiler and compare it to the stage 3 --- 1082,1261 ---- assembler or for availability of the DPX/2 port of GAS, contact F.Pierresteguy@frcl.bull.fr. !

!

m68k-crds-unos

!

Use configure unos for building on Unos. !

The Unos assembler is named casm instead of as. For some strange reason linking /bin/as to /bin/casm changes the behavior, and does not work. So, when installing GCC, you should install the following script as as in the subdirectory where the passes of GCC are installed: ! 

     #!/bin/sh
!      casm $*
!
!

The default Unos library is named libunos.a instead of libc.a. To allow GCC to function, either change all references to -lc in gcc.c to -lunos or link /lib/libc.a to /lib/libunos.a. !

When compiling GCC with the standard compiler, to overcome bugs in the support of alloca, do not use -O when making stage 2. Then use the stage 2 compiler with -O to make the stage 3 compiler. This compiler will have the same characteristics as the usual stage 2 compiler on other systems. Use it to make a stage 4 compiler and compare that with stage 3 to verify proper compilation. !

(Perhaps simply defining ALLOCA in x-crds as described in the comments there will make the above paragraph superfluous. Please inform us of whether this works.) !

Unos uses memory segmentation instead of demand paging, so you will need a lot of memory. 5 Mb is barely enough if no other tasks are running. If linking cc1 fails, try putting the object files into a library and linking from that library. !

!

m68k-hp-hpux

!

HP 9000 series 300 or 400 running HP-UX. HP-UX version 8.0 has a bug in the assembler that prevents compilation of GCC. This bug manifests itself during the first stage of compilation, while building libgcc2.a: ! 

     _floatdisf
!      cc1: warning: `-g' option not supported on this version of GCC
!      cc1: warning: `-g1' option not supported on this version of GCC
!      ./xgcc: Internal compiler error: program as got fatal signal 11
!
!

A patched version of the assembler is available as the file ftp://altdorf.ai.mit.edu/archive/cph/hpux-8.0-assembler. If you have HP software support, the patch can also be obtained directly from HP, as described in the following note: !

This is the patched assembler, to patch SR#1653-010439, where the assembler aborts on floating point constants. !

The bug is not really in the assembler, but in the shared library version of the function "cvtnum(3c)". The bug on "cvtnum(3c)" is SR#4701-078451. Anyway, the attached assembler uses the archive library version of "cvtnum(3c)" and thus does not exhibit the bug.

!

This patch is also known as PHCO_4484. !

In addition, if you wish to use gas, you must use gas version 2.1 or later, and you must use the GNU linker version 2.1 or later. Earlier versions of gas relied upon a program which converted the gas output into the native HP-UX format, but that program has not been kept up to date. gdb does not understand that native HP-UX format, so you must use gas if you wish to use gdb. !

On HP-UX version 8.05, but not on 8.07 or more recent versions, the fixproto shell script triggers a bug in the system shell. If you encounter this problem, upgrade your operating system or use BASH (the GNU shell) to run fixproto. This bug will cause the fixproto program to report an error of the form: ! 

     ./fixproto: sh internal 1K buffer overflow
!
!

To fix this, you can also change the first line of the fixproto script to look like: ! 

     #!/bin/ksh
!
!
!

m68k-*-nextstep*

!

These configurations are obsoleted in GCC 3.1. !

Current GCC versions probably do not work on version 2 of the NeXT operating system. !

On NeXTStep 3.0, the Objective-C compiler does not work, due, apparently, to a kernel bug that it happens to trigger. This problem does not happen on 3.1. !

You absolutely must use GNU sed and GNU make on this platform. !

On NeXTSTEP 3.x where x < 3 the build of GCC will abort during stage1 with an error message like this: ! 

       _eh
!        /usr/tmp/ccbbsZ0U.s:987:Unknown pseudo-op: .section
!        /usr/tmp/ccbbsZ0U.s:987:Rest of line ignored. 1st junk character
!        valued 95 (_).
!
!

The reason for this is the fact that NeXT's assembler for these versions of the operating system does not support the .section pseudo op that's needed for full C++ exception functionality. !

As NeXT's assembler is a derived work from GNU as, a free replacement that does can be obtained at ftp://ftp.next.peak.org:/next-ftp/next/apps/devtools/as.3.3.NIHS.s.tar.gz. !

If you try to build the integrated C++ & C++ runtime libraries on this system you will run into trouble with include files. The way to get around this is to use the following sequence. Note you must have write permission to the directory prefix you specified in the configuration process of GCC for this sequence to work. ! 

       cd bld-gcc
!        make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
!        cd gcc
!        make bootstrap
!        make install-headers-tar
!        cd ..
!        make bootstrap3
!
!
!

m68k-ncr-*

!

On the Tower models 4n0 and 6n0, by default a process is not allowed to have more than one megabyte of memory. GCC cannot compile itself (or many other programs) with -O in that much memory. !

To solve this problem, reconfigure the kernel adding the following line to the configuration file: ! 

     MAXUMEM = 4096
!
!
!

m68k-sun

!

Sun 3. We do not provide a configuration file to use the Sun FPA by default, because programs that establish signal handlers for floating point traps inherently cannot work with the FPA. !

!

m68k-sun-sunos4.1.1

!

It is reported that you may need the GNU assembler on this platform. !

!

m88k-*-svr3

!

Motorola m88k running the AT&T/Unisoft/Motorola V.3 reference port. These configurations are obsoleted in GCC 3.1. !

These systems tend to use the Green Hills C, revision 1.8.5, as the standard C compiler. There are apparently bugs in this compiler that result in object files differences between stage 2 and stage 3. If this happens, make the stage 4 compiler and compare it to the stage 3 *************** compiler. If the stage 3 and stage 4 ob *** 1261,1277 **** suggests you encountered a problem with the standard C compiler; the stage 3 and 4 compilers may be usable. !

It is best, however, to use an older version of GCC for bootstrapping if you have one. !

!

m88k-*-dgux

!

Motorola m88k running DG/UX. These configurations are obsoleted in GCC 3.1. !

To build 88open BCS native or cross compilers on DG/UX, specify the configuration name as m88k-*-dguxbcs and build in the 88open BCS software development environment. To build ELF native or cross compilers on DG/UX, specify --- 1263,1279 ---- suggests you encountered a problem with the standard C compiler; the stage 3 and 4 compilers may be usable. !

It is best, however, to use an older version of GCC for bootstrapping if you have one. !

!

m88k-*-dgux

!

Motorola m88k running DG/UX. These configurations are obsoleted in GCC 3.1. !

To build 88open BCS native or cross compilers on DG/UX, specify the configuration name as m88k-*-dguxbcs and build in the 88open BCS software development environment. To build ELF native or cross compilers on DG/UX, specify *************** You set the software development environ *** 1280,1296 **** sde-target command and specifying either m88kbcs or m88kdguxelf as the operand. !

If you do not specify a configuration name, configure guesses the configuration based on the current software development environment. !

!

m88k-tektronix-sysv3

!

Tektronix XD88 running UTekV 3.2e. These configurations are obsoleted in GCC 3.1. !

Do not turn on optimization while building stage1 if you bootstrap with the buggy Green Hills compiler. Also, the bundled LAI System V NFS is buggy so if you build in an NFS mounted --- 1282,1298 ---- sde-target command and specifying either m88kbcs or m88kdguxelf as the operand. !

If you do not specify a configuration name, configure guesses the configuration based on the current software development environment. !

!

m88k-tektronix-sysv3

!

Tektronix XD88 running UTekV 3.2e. These configurations are obsoleted in GCC 3.1. !

Do not turn on optimization while building stage1 if you bootstrap with the buggy Green Hills compiler. Also, the bundled LAI System V NFS is buggy so if you build in an NFS mounted *************** directory, start from a fresh reboot, or *** 1298,1331 **** Otherwise you may have trouble getting clean comparisons between stages. !

!

mips-*-*

!

If you use the 1.31 version of the MIPS assembler (such as was shipped with Ultrix 3.1), you will need to use the -fno-delayed-branch switch when optimizing floating point code. Otherwise, the assembler will complain when the GCC compiler fills a branch delay slot with a floating point instruction, such as add.d. !

If on a MIPS system you get an error message saying "does not have gp sections for all it's [sic] sectons [sic]", don't worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. !

It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. !

Users have reported some problems with version 2.0 of the MIPS compiler tools that were shipped with Ultrix 4.1. Version 2.10 which came with Ultrix 4.2 seems to work fine. !

Users have also reported some problems with version 2.20 of the MIPS compiler tools that were shipped with RISC/os 4.x. The earlier version 2.11 seems to work fine. !

Some versions of the MIPS linker will issue an assertion failure when linking code that uses alloca against shared libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug in the linker, that is supposed to be fixed in future revisions. --- 1300,1333 ---- Otherwise you may have trouble getting clean comparisons between stages. !

!

mips-*-*

!

If you use the 1.31 version of the MIPS assembler (such as was shipped with Ultrix 3.1), you will need to use the -fno-delayed-branch switch when optimizing floating point code. Otherwise, the assembler will complain when the GCC compiler fills a branch delay slot with a floating point instruction, such as add.d. !

If on a MIPS system you get an error message saying "does not have gp sections for all it's [sic] sectons [sic]", don't worry about it. This happens whenever you use GAS with the MIPS linker, but there is not really anything wrong, and it is okay to use the output file. You can stop such warnings by installing the GNU linker. !

It would be nice to extend GAS to produce the gp tables, but they are optional, and there should not be a warning about their absence. !

Users have reported some problems with version 2.0 of the MIPS compiler tools that were shipped with Ultrix 4.1. Version 2.10 which came with Ultrix 4.2 seems to work fine. !

Users have also reported some problems with version 2.20 of the MIPS compiler tools that were shipped with RISC/os 4.x. The earlier version 2.11 seems to work fine. !

Some versions of the MIPS linker will issue an assertion failure when linking code that uses alloca against shared libraries on RISC-OS 5.0, and DEC's OSF/1 systems. This is a bug in the linker, that is supposed to be fixed in future revisions. *************** To protect against this, GCC passes -shared or -call_shared switch. !

mips-mips-bsd

!

MIPS machines running the MIPS operating system in BSD mode. These configurations are obsoleted in GCC 3.1. !

It's possible that some old versions of the system lack the functions memcpy, memmove, memcmp, and memset. If your system lacks these, you must remove or undo the definition of TARGET_MEM_FUNCTIONS in mips-bsd.h. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. --- 1335,1351 ---- linker unless you pass an explicit -shared or -call_shared switch. !

mips-mips-bsd

!

MIPS machines running the MIPS operating system in BSD mode. These configurations are obsoleted in GCC 3.1. !

It's possible that some old versions of the system lack the functions memcpy, memmove, memcmp, and memset. If your system lacks these, you must remove or undo the definition of TARGET_MEM_FUNCTIONS in mips-bsd.h. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. *************** Both of these options are automatically *** 1352,1382 **** If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

!

mips-dec-*

!

These configurations are obsoleted in GCC 3.1. !

MIPS-based DECstations can support three different personalities: Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have a configuration name beginning with alpha*-dec.) To configure GCC for these platforms use the following configurations: !

mips-dec-ultrix !
Ultrix configuration. !
mips-dec-osf1 !
DEC's version of OSF/1. !
mips-dec-osfrose !
Open Software Foundation reference port of OSF/1 which uses the OSF/rose object file format instead of ECOFF. Normally, you would not select this configuration.
!

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. --- 1354,1384 ---- If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

!

mips-dec-*

!

These configurations are obsoleted in GCC 3.1. !

MIPS-based DECstations can support three different personalities: Ultrix, DEC OSF/1, and OSF/rose. (Alpha-based DECstation products have a configuration name beginning with alpha*-dec.) To configure GCC for these platforms use the following configurations: !

mips-dec-ultrix !
Ultrix configuration. !
mips-dec-osf1 !
DEC's version of OSF/1. !
mips-dec-osfrose !
Open Software Foundation reference port of OSF/1 which uses the OSF/rose object file format instead of ECOFF. Normally, you would not select this configuration.
!

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. *************** Both of these options are automatically *** 1385,1397 **** If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

!

mips-mips-riscos*

!

These configurations are obsoleted in GCC 3.1. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. --- 1387,1399 ---- If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

!

mips-mips-riscos*

!

These configurations are obsoleted in GCC 3.1. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. *************** Both of these options are automatically *** 1400,1474 **** If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

MIPS computers running RISC-OS can support four different personalities: default, BSD 4.3, System V.3, and System V.4 (older versions of RISC-OS don't support V.4). To configure GCC for these platforms use the following configurations: !

!
mips-mips-riscosrev !
Default configuration for RISC-OS, revision rev. !
mips-mips-riscosrevbsd !
BSD 4.3 configuration for RISC-OS, revision rev. !
mips-mips-riscosrevsysv4 !
System V.4 configuration for RISC-OS, revision rev. !
!
mips-mips-riscosrevsysv !
System V.3 configuration for RISC-OS, revision rev.
!

The revision rev mentioned above is the revision of RISC-OS to use. You must reconfigure GCC when going from a RISC-OS revision 4 to RISC-OS revision 5. This has the effect of avoiding a linker bug. !

!

mips-sgi-irix4

!

This configuration is obsoleted in GCC 3.1. !

In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib" option must be installed from the CD-ROM supplied from Silicon Graphics. This is found on the 2nd CD in release 4.0.1. !

On IRIX version 4.0.5F, and perhaps on some other versions as well, there is an assembler bug that reorders instructions incorrectly. To work around it, specify the target configuration mips-sgi-irix4loser. This configuration inhibits assembler optimization. !

In a compiler configured with target mips-sgi-irix4, you can turn off assembler optimization by using the -noasmopt option. This compiler option passes the option -O0 to the assembler, to inhibit reordering. !

The -noasmopt option can be useful for testing whether a problem is due to erroneous assembler reordering. Even if a problem does not go away with -noasmopt, it may still be due to assembler reordering--perhaps GCC itself was miscompiled as a result. !

You may get the following warning on IRIX 4 platforms, it can be safely ignored. ! 

  warning: foo.o does not have gp tables for all its sections.
!
!
!

mips-sgi-irix5

!

This configuration has considerable problems, which will be fixed in a future release. !

In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr" subsystem must be installed from the IDO CD-ROM supplied by Silicon Graphics. It is also available for download from http://www.sgi.com/developers/devtools/apis/ido.html. !

make compare may fail on version 5 of IRIX unless you add -save-temps to CFLAGS. On these systems, the name of the assembler input file is stored in the object file, and that makes comparison fail if it differs between the stage1 and --- 1402,1476 ---- If you override the CC make variable and use the MIPS compilers, you may need to add -Wf,-XNg1500 -Olimit 3000. !

MIPS computers running RISC-OS can support four different personalities: default, BSD 4.3, System V.3, and System V.4 (older versions of RISC-OS don't support V.4). To configure GCC for these platforms use the following configurations: !

!
mips-mips-riscosrev !
Default configuration for RISC-OS, revision rev. !
mips-mips-riscosrevbsd !
BSD 4.3 configuration for RISC-OS, revision rev. !
mips-mips-riscosrevsysv4 !
System V.4 configuration for RISC-OS, revision rev. !
!
mips-mips-riscosrevsysv !
System V.3 configuration for RISC-OS, revision rev.
!

The revision rev mentioned above is the revision of RISC-OS to use. You must reconfigure GCC when going from a RISC-OS revision 4 to RISC-OS revision 5. This has the effect of avoiding a linker bug. !

!

mips-sgi-irix4

!

This configuration is obsoleted in GCC 3.1. !

In order to compile GCC on an SGI running IRIX 4, the "c.hdr.lib" option must be installed from the CD-ROM supplied from Silicon Graphics. This is found on the 2nd CD in release 4.0.1. !

On IRIX version 4.0.5F, and perhaps on some other versions as well, there is an assembler bug that reorders instructions incorrectly. To work around it, specify the target configuration mips-sgi-irix4loser. This configuration inhibits assembler optimization. !

In a compiler configured with target mips-sgi-irix4, you can turn off assembler optimization by using the -noasmopt option. This compiler option passes the option -O0 to the assembler, to inhibit reordering. !

The -noasmopt option can be useful for testing whether a problem is due to erroneous assembler reordering. Even if a problem does not go away with -noasmopt, it may still be due to assembler reordering--perhaps GCC itself was miscompiled as a result. !

You may get the following warning on IRIX 4 platforms, it can be safely ignored. ! 

       warning: foo.o does not have gp tables for all its sections.
!
!
!

mips-sgi-irix5

!

This configuration has considerable problems, which will be fixed in a future release. !

In order to compile GCC on an SGI running IRIX 5, the "compiler_dev.hdr" subsystem must be installed from the IDO CD-ROM supplied by Silicon Graphics. It is also available for download from http://www.sgi.com/developers/devtools/apis/ido.html. !

make compare may fail on version 5 of IRIX unless you add -save-temps to CFLAGS. On these systems, the name of the assembler input file is stored in the object file, and that makes comparison fail if it differs between the stage1 and *************** unless the comparisons fail without that *** 1479,1490 **** -save-temps, you will have to manually delete the .i and .s files after each series of compilations. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. !

To enable debugging under IRIX 5, you must use GNU as 2.11.2 or later, and use the --with-gnu-as configure option when configuring GCC. GNU as is distributed as part of the binutils package. --- 1481,1492 ---- -save-temps, you will have to manually delete the .i and .s files after each series of compilations. !

If you use the MIPS C compiler to bootstrap, it may be necessary to increase its table size for switch statements with the -Wf,-XNg1500 option. If you use the -O2 optimization option, you also need to use -Olimit 3000. !

To enable debugging under IRIX 5, you must use GNU as 2.11.2 or later, and use the --with-gnu-as configure option when configuring GCC. GNU as is distributed as part of the binutils package. *************** When using release 2.11.2, you need to a *** 1492,1498 **** http://sources.redhat.com/ml/binutils/2001-07/msg00352.html which will be included in the next release of binutils. !

When building GCC, the build process loops rebuilding cc1 over and over again. This happens on mips-sgi-irix5.2, and possibly other platforms. It has been reported that this is a known bug in the make shipped with IRIX 5.2. We recommend you use GNU --- 1494,1500 ---- http://sources.redhat.com/ml/binutils/2001-07/msg00352.html which will be included in the next release of binutils. !

When building GCC, the build process loops rebuilding cc1 over and over again. This happens on mips-sgi-irix5.2, and possibly other platforms. It has been reported that this is a known bug in the make shipped with IRIX 5.2. We recommend you use GNU *************** other platforms. It has been reported t *** 1500,1532 **** however, you may have success with smake on IRIX 5.2 if you do not have GNU make available. !

!

mips-sgi-irix6

!

If you are using IRIX cc as your bootstrap compiler, you must ensure that the N32 ABI is in use. To test this, compile a simple C file with cc and then run file on the resulting object file. The output should look like: ! 

test.o: ELF N32 MSB ...
!
!

If you see: ! 

test.o: ELF 32-bit MSB ...
!
!

or ! 

test.o: ELF 64-bit MSB ...
!
!

then your version of cc uses the O32 or N64 ABI by default. You should set the environment variable CC to cc -n32 before configuring GCC. !

If you want the resulting gcc to run on old 32-bit systems with the MIPS R4400 CPU, you need to ensure that only code for the mips3 instruction set architecture (ISA) is generated. While GCC 3.x does this correctly, both GCC 2.95 and SGI's MIPSpro cc may change --- 1502,1534 ---- however, you may have success with smake on IRIX 5.2 if you do not have GNU make available. !

!

mips-sgi-irix6

!

If you are using IRIX cc as your bootstrap compiler, you must ensure that the N32 ABI is in use. To test this, compile a simple C file with cc and then run file on the resulting object file. The output should look like: ! 

     test.o: ELF N32 MSB ...
!
!

If you see: ! 

     test.o: ELF 32-bit MSB ...
!
!

or ! 

     test.o: ELF 64-bit MSB ...
!
!

then your version of cc uses the O32 or N64 ABI by default. You should set the environment variable CC to cc -n32 before configuring GCC. !

If you want the resulting gcc to run on old 32-bit systems with the MIPS R4400 CPU, you need to ensure that only code for the mips3 instruction set architecture (ISA) is generated. While GCC 3.x does this correctly, both GCC 2.95 and SGI's MIPSpro cc may change *************** the ISA depending on the machine where G *** 1534,1560 **** as the bootstrap compiler may result in mips4 code, which won't run at all on mips3-only systems. For the test program above, you should see: ! 

test.o: ELF N32 MSB mips-3 ...
!
!

If you get: ! 

test.o: ELF N32 MSB mips-4 ...
!
!

instead, you should set the environment variable CC to cc -n32 -mips3 or gcc -mips3 respectively before configuring GCC. !

GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If you build GCC on a system that doesn't have the N64 libraries installed, you need to configure with --disable-multilib so GCC doesn't try to use them. Look for /usr/lib64/libc.so.1 to see if you have the 64-bit libraries installed. !

You must not use GNU as (which isn't built anyway as of binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems. !

GCC does not currently support generating O32 ABI binaries in the mips-sgi-irix6 configurations. It is possible to create a GCC with O32 ABI only support by configuring it for the mips-sgi-irix5 target and using a patched GNU as 2.11.2 as documented in the --- 1536,1562 ---- as the bootstrap compiler may result in mips4 code, which won't run at all on mips3-only systems. For the test program above, you should see: ! 

     test.o: ELF N32 MSB mips-3 ...
!
!

If you get: ! 

     test.o: ELF N32 MSB mips-4 ...
!
!

instead, you should set the environment variable CC to cc -n32 -mips3 or gcc -mips3 respectively before configuring GCC. !

GCC on IRIX 6 is usually built to support both the N32 and N64 ABIs. If you build GCC on a system that doesn't have the N64 libraries installed, you need to configure with --disable-multilib so GCC doesn't try to use them. Look for /usr/lib64/libc.so.1 to see if you have the 64-bit libraries installed. !

You must not use GNU as (which isn't built anyway as of binutils 2.11.2) on IRIX 6 platforms; doing so will only cause problems. !

GCC does not currently support generating O32 ABI binaries in the mips-sgi-irix6 configurations. It is possible to create a GCC with O32 ABI only support by configuring it for the mips-sgi-irix5 target and using a patched GNU as 2.11.2 as documented in the *************** native assembler requires patches to GCC *** 1563,1569 **** future release. It is expected that O32 ABI support will be available again in a future release. !

The --enable-threads option doesn't currently work, a patch is in preparation for a future release. The --enable-libgcj option is disabled by default: IRIX 6 uses a very low default limit (20480) for the command line length. Although libtool contains a --- 1565,1571 ---- future release. It is expected that O32 ABI support will be available again in a future release. !

The --enable-threads option doesn't currently work, a patch is in preparation for a future release. The --enable-libgcj option is disabled by default: IRIX 6 uses a very low default limit (20480) for the command line length. Although libtool contains a *************** to build despite this, running into an i *** 1573,1579 **** its maximum of 262144 bytes. If you have root access, you can use the systune command to do this. !

GCC does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte --- 1575,1581 ---- its maximum of 262144 bytes. If you have root access, you can use the systune command to do this. !

GCC does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but IRIX 6 is affected the most, because it is a 64-bit target, and 4 byte *************** at the wrong end, e.g. a 4 byte structur *** 1582,1588 **** of the register when it should be loaded into the upper 4 bytes of the register. !

GCC is consistent with itself, but not consistent with the SGI C compiler (and the SGI supplied runtime libraries), so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. Currently this --- 1584,1590 ---- of the register when it should be loaded into the upper 4 bytes of the register. !

GCC is consistent with itself, but not consistent with the SGI C compiler (and the SGI supplied runtime libraries), so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. Currently this *************** is known to affect inet_ntoainet_netof, inet_makeaddr, and semctl. Until the bug is fixed, GCC contains workarounds for the known affected functions. !

See http://freeware.sgi.com/ for more information about using GCC on IRIX platforms. !

!

mips-sony-sysv

!

Sony MIPS NEWS. This configuration is obsoleted in GCC 3.1. !

This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of COFF). In particular, the linker does not like the code generated by GCC when shared libraries are linked in. !

!

ns32k-encore

!

This configuration is obsoleted in GCC 3.1. !

Encore ns32000 system. Encore systems are supported only under BSD. !

!

ns32k-*-genix

!

National Semiconductor ns32000 system. This configuration is obsoleted in GCC 3.1. !

Genix has bugs in alloca and malloc; you must get the compiled versions of these from GNU Emacs. !

!

ns32k-sequent

!

This configuration is obsoleted in GCC 3.1. !

Go to the Berkeley universe before compiling. !

!

ns32k-utek

!

UTEK ns32000 system ("merlin"). This configuration is obsoleted in GCC 3.1. !

The C compiler that comes with this system cannot compile GCC; contact tektronix!reed!mason to get binaries of GCC for bootstrapping. !

!

powerpc-*-*

!

You can specify a default version for the -mcpu=cpu_type ! switch by using the configure option --with-cpu-cpu_type. !

!

powerpc-*-darwin*

!

PowerPC running Darwin (Mac OS X kernel). !

GCC 3.0 does not support Darwin, but 3.1 and later releases will work. !

Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at http://www.opensource.apple.com/projects/darwin (free registration required). !

Versions of the assembler prior to "cctools-364" cannot handle the 4-argument form of rlwinm and related mask-using instructions. Darwin 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364, check out cctools with tag Apple-364, build it, and install the assembler as usr/bin/as. See http://www.opensource.apple.com/tools/cvs/docs.html for details. !

Also, the default stack limit of 512K is too small, and a bootstrap will typically fail when self-compiling expr.c. Set the stack to 800K or more, for instance by doing limit stack 800. It's also convenient to use the GNU preprocessor instead of Apple's during the --- 1592,1675 ---- inet_netof, inet_makeaddr, and semctl. Until the bug is fixed, GCC contains workarounds for the known affected functions. !

See http://freeware.sgi.com/ for more information about using GCC on IRIX platforms. !

!

mips-sony-sysv

!

Sony MIPS NEWS. This configuration is obsoleted in GCC 3.1. !

This works in NEWSOS 5.0.1, but not in 5.0.2 (which uses ELF instead of COFF). In particular, the linker does not like the code generated by GCC when shared libraries are linked in. !

!

ns32k-encore

!

This configuration is obsoleted in GCC 3.1. !

Encore ns32000 system. Encore systems are supported only under BSD. !

!

ns32k-*-genix

!

National Semiconductor ns32000 system. This configuration is obsoleted in GCC 3.1. !

Genix has bugs in alloca and malloc; you must get the compiled versions of these from GNU Emacs. !

!

ns32k-sequent

!

This configuration is obsoleted in GCC 3.1. !

Go to the Berkeley universe before compiling. !

!

ns32k-utek

!

UTEK ns32000 system ("merlin"). This configuration is obsoleted in GCC 3.1. !

The C compiler that comes with this system cannot compile GCC; contact tektronix!reed!mason to get binaries of GCC for bootstrapping. !

!

powerpc-*-*

!

You can specify a default version for the -mcpu=cpu_type ! switch by using the configure option --with-cpu-cpu_type. !

!

powerpc-*-darwin*

!

PowerPC running Darwin (Mac OS X kernel). !

GCC 3.0 does not support Darwin, but 3.1 and later releases will work. !

Pre-installed versions of Mac OS X may not include any developer tools, meaning that you will not be able to build GCC from source. Tool binaries are available at http://www.opensource.apple.com/projects/darwin (free registration required). !

Versions of the assembler prior to "cctools-364" cannot handle the 4-argument form of rlwinm and related mask-using instructions. Darwin 1.3 (Mac OS X 10.0) uses cctools-353 for instance. To get cctools-364, check out cctools with tag Apple-364, build it, and install the assembler as usr/bin/as. See http://www.opensource.apple.com/tools/cvs/docs.html for details. !

Also, the default stack limit of 512K is too small, and a bootstrap will typically fail when self-compiling expr.c. Set the stack to 800K or more, for instance by doing limit stack 800. It's also convenient to use the GNU preprocessor instead of Apple's during the *************** first stage of bootstrapping; this is au *** 1675,1845 **** bootstrap, but to do it from the toplevel objdir you will need to say make CC='cc -no-cpp-precomp' bootstrap. !

Note that the version of GCC shipped by Apple typically includes a number of extensions not available in a standard GCC release. These extensions are generally specific to Mac programming. !

!

powerpc-*-elf, powerpc-*-sysv4

!

PowerPC system in big endian mode, running System V.4. !

!

powerpc-*-linux-gnu*

!

You will need binutils 2.13.90.0.10 or newer for a working GCC. !

!

powerpc-*-netbsd*

!

PowerPC system in big endian mode running NetBSD. To build the documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included Texinfo version 3.12). !

!

powerpc-*-eabiaix

!

Embedded PowerPC system in big endian mode with -mcall-aix selected as the default. !

!

powerpc-*-eabisim

!

Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. !

!

powerpc-*-eabi

!

Embedded PowerPC system in big endian mode. !

!

powerpcle-*-elf, powerpcle-*-sysv4

!

PowerPC system in little endian mode, running System V.4. !

!

powerpcle-*-eabisim

!

Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. !

!

powerpcle-*-eabi

!

Embedded PowerPC system in little endian mode. !

!

powerpcle-*-winnt, powerpcle-*-pe

!

PowerPC system in little endian mode running Windows NT. !

!

romp-*-aos, romp-*-mach

!

These configurations are obsoleted in GCC 3.1. !

We recommend you compile GCC with an earlier version of itself; if you compile GCC with hc, the Metaware compiler, it will work, but you will get mismatches between the stage 2 and stage 3 compilers in various files. These errors are minor differences in some floating-point constants and can be safely ignored; the stage 3 compiler is correct. !

!

s390-*-linux*

!

S/390 system running Linux for S/390. !

!

s390x-*-linux*

!

zSeries system (64-bit) running Linux for zSeries. !

!

*-*-solaris2*

!

Sun does not ship a C compiler with Solaris 2. To bootstrap and install GCC you first have to install a pre-built compiler, see our binaries page for details. !

The Solaris 2 /bin/sh will often fail to configure libstdc++-v3, boehm-gc or libjava. If you encounter this problem, set CONFIG_SHELL to /bin/ksh in your environment before running configure. !

Solaris 2 comes with a number of optional OS packages. Some of these packages are needed to use GCC fully, namely SUNWarc, SUNWbtool, SUNWesu, SUNWhea, SUNWlibm, SUNWsprot, and SUNWtoo. If you did not install all optional packages when installing Solaris 2, you will need to verify that the packages that GCC needs are installed. !

To check whether an optional package is installed, use the pkginfo command. To add an optional package, use the pkgadd command. For further details, see the Solaris 2 documentation. !

Trying to use the linker and other tools in /usr/ucb to install GCC has been observed to cause trouble. For example, the linker may hang indefinitely. The fix is to remove /usr/ucb from your PATH. !

All releases of GNU binutils prior to 2.11.2 have known bugs on this platform. We recommend the use of GNU binutils 2.11.2 or the vendor tools (Sun as, Sun ld). !

Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or newer: g++ will complain that types are missing. These headers assume that omitting the type means int; this assumption worked for C89 but is wrong for C++, and is now wrong for C99 also. !

g++ accepts such (invalid) constructs with the option -fpermissive; it will assume that any missing type is int (as defined by C89). !

There are patches for Solaris 2.6 (105633-56 or newer for SPARC, 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC, 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, 108653-22 for Intel) that fix this bug. !

!

sparc-sun-solaris2*

!

When GCC is configured to use binutils 2.11.2 or later the binaries produced are smaller than the ones produced using Sun's native tools; this difference is quite significant for binaries containing debugging information. !

Sun as 4.x is broken in that it cannot cope with long symbol names. A typical error message might look similar to the following: ! 

/usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
!   can't compute value of an expression involving an external symbol.
!
!

This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris 2.6 and has been fixed in later (5.x) versions of the assembler, starting with Solaris 7. !

Starting with Solaris 7, the operating system is capable of executing 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this; the -m64 option enables 64-bit code generation. However, if all you want is code tuned for the UltraSPARC CPU, you --- 1677,1847 ---- bootstrap, but to do it from the toplevel objdir you will need to say make CC='cc -no-cpp-precomp' bootstrap. !

Note that the version of GCC shipped by Apple typically includes a number of extensions not available in a standard GCC release. These extensions are generally specific to Mac programming. !

!

powerpc-*-elf, powerpc-*-sysv4

!

PowerPC system in big endian mode, running System V.4. !

!

powerpc-*-linux-gnu*

!

You will need binutils 2.13.90.0.10 or newer for a working GCC. !

!

powerpc-*-netbsd*

!

PowerPC system in big endian mode running NetBSD. To build the documentation you will need Texinfo version 4.1 (NetBSD 1.5.1 included Texinfo version 3.12). !

!

powerpc-*-eabiaix

!

Embedded PowerPC system in big endian mode with -mcall-aix selected as the default. !

!

powerpc-*-eabisim

!

Embedded PowerPC system in big endian mode for use in running under the PSIM simulator. !

!

powerpc-*-eabi

!

Embedded PowerPC system in big endian mode. !

!

powerpcle-*-elf, powerpcle-*-sysv4

!

PowerPC system in little endian mode, running System V.4. !

!

powerpcle-*-eabisim

!

Embedded PowerPC system in little endian mode for use in running under the PSIM simulator. !

!

powerpcle-*-eabi

!

Embedded PowerPC system in little endian mode. !

!

powerpcle-*-winnt, powerpcle-*-pe

!

PowerPC system in little endian mode running Windows NT. !

!

romp-*-aos, romp-*-mach

!

These configurations are obsoleted in GCC 3.1. !

We recommend you compile GCC with an earlier version of itself; if you compile GCC with hc, the Metaware compiler, it will work, but you will get mismatches between the stage 2 and stage 3 compilers in various files. These errors are minor differences in some floating-point constants and can be safely ignored; the stage 3 compiler is correct. !

!

s390-*-linux*

!

S/390 system running Linux for S/390. !

!

s390x-*-linux*

!

zSeries system (64-bit) running Linux for zSeries. !

!

*-*-solaris2*

!

Sun does not ship a C compiler with Solaris 2. To bootstrap and install GCC you first have to install a pre-built compiler, see our binaries page for details. !

The Solaris 2 /bin/sh will often fail to configure libstdc++-v3, boehm-gc or libjava. If you encounter this problem, set CONFIG_SHELL to /bin/ksh in your environment before running configure. !

Solaris 2 comes with a number of optional OS packages. Some of these packages are needed to use GCC fully, namely SUNWarc, SUNWbtool, SUNWesu, SUNWhea, SUNWlibm, SUNWsprot, and SUNWtoo. If you did not install all optional packages when installing Solaris 2, you will need to verify that the packages that GCC needs are installed. !

To check whether an optional package is installed, use the pkginfo command. To add an optional package, use the pkgadd command. For further details, see the Solaris 2 documentation. !

Trying to use the linker and other tools in /usr/ucb to install GCC has been observed to cause trouble. For example, the linker may hang indefinitely. The fix is to remove /usr/ucb from your PATH. !

All releases of GNU binutils prior to 2.11.2 have known bugs on this platform. We recommend the use of GNU binutils 2.11.2 or the vendor tools (Sun as, Sun ld). !

Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or newer: g++ will complain that types are missing. These headers assume that omitting the type means int; this assumption worked for C89 but is wrong for C++, and is now wrong for C99 also. !

g++ accepts such (invalid) constructs with the option -fpermissive; it will assume that any missing type is int (as defined by C89). !

There are patches for Solaris 2.6 (105633-56 or newer for SPARC, 106248-42 or newer for Intel), Solaris 7 (108376-21 or newer for SPARC, 108377-20 for Intel), and Solaris 8 (108652-24 or newer for SPARC, 108653-22 for Intel) that fix this bug. !

!

sparc-sun-solaris2*

!

When GCC is configured to use binutils 2.11.2 or later the binaries produced are smaller than the ones produced using Sun's native tools; this difference is quite significant for binaries containing debugging information. !

Sun as 4.x is broken in that it cannot cope with long symbol names. A typical error message might look similar to the following: ! 

     /usr/ccs/bin/as: "/var/tmp/ccMsw135.s", line 11041: error:
!        can't compute value of an expression involving an external symbol.
!
!

This is Sun bug 4237974. This is fixed with patch 108908-02 for Solaris 2.6 and has been fixed in later (5.x) versions of the assembler, starting with Solaris 7. !

Starting with Solaris 7, the operating system is capable of executing 64-bit SPARC V9 binaries. GCC 3.1 and later properly supports this; the -m64 option enables 64-bit code generation. However, if all you want is code tuned for the UltraSPARC CPU, you *************** should try the -mtune=ultrasparcWhen configuring on a Solaris 7 or later system that is running a kernel that supports only 32-bit binaries, one must configure with --disable-multilib, since we will not be able to build the 64-bit target libraries. !

!

sparc-sun-solaris2.7

!

Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 and later, including all EGCS releases. Sun formerly recommended 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to recommend it only for people who use Sun's compilers. !

Here are some workarounds to this problem: !

  • Do not install Sun patch 107058-01 until after Sun releases a complete patch for bug 4210064. This is the simplest course to take, unless you must also use Sun's C compiler. Unfortunately 107058-01 is preinstalled on some new Solaris 7-based hosts, so you may have to back it out. !
  • Copy the original, unpatched Solaris 7 /usr/ccs/bin/as into /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as, adjusting the latter name to fit your local conventions and software version numbers. !
  • Install Sun patch 106950-03 (1999-05-25) or later. Nobody with both 107058-01 and 106950-03 installed has reported the bug with GCC and Sun's dynamic linker. This last course of action is riskiest, for two reasons. First, you must install 106950 on all hosts that --- 1849,1884 ---- code that, unlike full 64-bit code, can still run on non-UltraSPARC machines. !

    When configuring on a Solaris 7 or later system that is running a kernel that supports only 32-bit binaries, one must configure with --disable-multilib, since we will not be able to build the 64-bit target libraries. !

    !

    sparc-sun-solaris2.7

    !

    Sun patch 107058-01 (1999-01-13) for Solaris 7/SPARC triggers a bug in the dynamic linker. This problem (Sun bug 4210064) affects GCC 2.8 and later, including all EGCS releases. Sun formerly recommended 107058-01 for all Solaris 7 users, but around 1999-09-01 it started to recommend it only for people who use Sun's compilers. !

    Here are some workarounds to this problem: !

    • Do not install Sun patch 107058-01 until after Sun releases a complete patch for bug 4210064. This is the simplest course to take, unless you must also use Sun's C compiler. Unfortunately 107058-01 is preinstalled on some new Solaris 7-based hosts, so you may have to back it out. !
    • Copy the original, unpatched Solaris 7 /usr/ccs/bin/as into /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.1/as, adjusting the latter name to fit your local conventions and software version numbers. !
    • Install Sun patch 106950-03 (1999-05-25) or later. Nobody with both 107058-01 and 106950-03 installed has reported the bug with GCC and Sun's dynamic linker. This last course of action is riskiest, for two reasons. First, you must install 106950 on all hosts that *************** the bug. The current (as of 2001-09-24) *** 1888,2079 **** the Solaris 7 Recommended Patch Cluster.
    !

    !

    sparc-sun-sunos4*

    !

    A bug in the SunOS 4 linker will cause it to crash when linking -fPIC compiled objects (and will therefore not allow you to build shared libraries). !

    To fix this problem you can either use the most recent version of binutils or get the latest SunOS 4 linker patch (patch ID 100170-10) from Sun's patch site. !

    Sometimes on a Sun 4 you may observe a crash in the program genflags or genoutput while building GCC. This is said to be due to a bug in sh. You can probably get around it by running genflags or genoutput manually and then retrying the make. !

    !

    sparc-unknown-linux-gnulibc1

    !

    It has been reported that you might need binutils 2.8.1.0.23 for this platform, too. !

    !

    sparc-*-linux*

    !

    GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases mishandled unaligned relocations on sparc-*-* targets. !

    !

    sparc64-*-*

    !

    GCC version 2.95 is not able to compile code correctly for sparc64 targets. Users of the Linux kernel, at least, can use the sparc32 program to start up a new shell invocation with an environment that causes configure to recognize (via uname -a) the system as sparc-*-* instead. !

    !

    sparcv9-*-solaris2*

    !

    The following compiler flags must be specified in the configure step in order to bootstrap this target with the Sun compiler: ! 

       % CC="cc -xildoff -xarch=v9" srcdir/configure [options] [target]
!
    !

    -xildoff turns off the incremental linker, and -xarch=v9 specifies the v9 architecture to the Sun linker and assembler. !

    !

    *-*-sysv*

    !

    On System V release 3, you may get this error message while linking: ! 

    ld fatal: failed to write symbol name something
!  in strings table for file whatever
!
    !

    This probably indicates that the disk is full or your ulimit won't allow the file to be as large as it needs to be. !

    This problem can also result because the kernel parameter MAXUMEM is too small. If so, you must regenerate the kernel and make the value much larger. The default value is reported to be 1024; a value of 32768 is said to work. Smaller values may also work. !

    On System V, if you get an error like this, ! 

    /usr/local/lib/bison.simple: In function `yyparse':
! /usr/local/lib/bison.simple:625: virtual memory exhausted
!

    that too indicates a problem with disk space, ulimit, or MAXUMEM. !

    On a System V release 4 system, make sure /usr/bin precedes /usr/ucb in PATH. The cc command in /usr/ucb uses libraries which have bugs. !

    !

    vax-dec-ultrix

    !

    Don't try compiling with VAX C (vcc). It produces incorrect code in some cases (for example, when alloca is used). !

    !

    we32k-*-*

    !

    These computers are also known as the 3b2, 3b5, 3b20 and other similar names. (However, the 3b1 is actually a 68000.) These configurations are obsoleted in GCC 3.1. !

    Don't use -g when compiling with the system's compiler. The system's linker seems to be unable to handle such a large program with debugging information. !

    The system's compiler runs out of capacity when compiling stmt.c in GCC. You can work around this by building cpp in GCC first, then use that instead of the system's preprocessor with the system's C compiler to compile stmt.c. Here is how: ! 

    mv /lib/cpp /lib/cpp.att
! cp cpp /lib/cpp.gnu
! echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
! chmod +x /lib/cpp
!
    !

    The system's compiler produces bad code for some of the GCC optimization files. So you must build the stage 2 compiler without optimization. Then build a stage 3 compiler with optimization. That executable should work. Here are the necessary commands: ! 

    make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
! make stage2
! make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
!
    !

    You may need to raise the ULIMIT setting to build a C++ compiler, as the file cc1plus is larger than one megabyte. !

    !

    xtensa-*-elf

    !

    This target is intended for embedded Xtensa systems using the newlib C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. !

    The Xtensa configuration information must be specified prior to building GCC. The gcc/config/xtensa/xtensa-config.h header file contains the configuration information. If you created your own Xtensa configuration with the Xtensa Processor Generator, the downloaded files include a customized copy of this header file, which you can use to replace the default header file. !

    !

    xtensa-*-linux*

    !

    This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates position-independent code (PIC) regardless of whether the -fpic or -fPIC options are used. In other respects, this target is the same as the xtensa-*-elf target. !

    !

    Microsoft Windows (32-bit)

    !

    A port of GCC 2.95.x is included with the Cygwin environment. !

    Current (as of early 2001) snapshots of GCC will build under Cygwin without modification. !

    !

    OS/2

    !

    GCC does not currently support OS/2. However, Andrew Zabolotny has been working on a generic OS/2 port with pgcc. The current code can be found at http://www.goof.com/pcg/os2/. !

    An older copy of GCC 2.8.1 is included with the EMX tools available at ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/. !

    !

    Older systems

    !

    GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for several years and may suffer from bitrot. Support from some systems --- 1890,2081 ---- the Solaris 7 Recommended Patch Cluster.

!

!

sparc-sun-sunos4*

!

A bug in the SunOS 4 linker will cause it to crash when linking -fPIC compiled objects (and will therefore not allow you to build shared libraries). !

To fix this problem you can either use the most recent version of binutils or get the latest SunOS 4 linker patch (patch ID 100170-10) from Sun's patch site. !

Sometimes on a Sun 4 you may observe a crash in the program genflags or genoutput while building GCC. This is said to be due to a bug in sh. You can probably get around it by running genflags or genoutput manually and then retrying the make. !

!

sparc-unknown-linux-gnulibc1

!

It has been reported that you might need binutils 2.8.1.0.23 for this platform, too. !

!

sparc-*-linux*

!

GCC versions 3.0 and higher require binutils 2.11.2 and glibc 2.2.4 or newer on this platform. All earlier binutils and glibc releases mishandled unaligned relocations on sparc-*-* targets. !

!

sparc64-*-*

!

GCC version 2.95 is not able to compile code correctly for sparc64 targets. Users of the Linux kernel, at least, can use the sparc32 program to start up a new shell invocation with an environment that causes configure to recognize (via uname -a) the system as sparc-*-* instead. !

!

sparcv9-*-solaris2*

!

The following compiler flags must be specified in the configure step in order to bootstrap this target with the Sun compiler: ! 

        % CC="cc -xildoff -xarch=v9" srcdir/configure [options] [target]
!
!

-xildoff turns off the incremental linker, and -xarch=v9 specifies the v9 architecture to the Sun linker and assembler. !

!

*-*-sysv*

!

On System V release 3, you may get this error message while linking: ! 

     ld fatal: failed to write symbol name something
!       in strings table for file whatever
!
!

This probably indicates that the disk is full or your ulimit won't allow the file to be as large as it needs to be. !

This problem can also result because the kernel parameter MAXUMEM is too small. If so, you must regenerate the kernel and make the value much larger. The default value is reported to be 1024; a value of 32768 is said to work. Smaller values may also work. !

On System V, if you get an error like this, ! 

     /usr/local/lib/bison.simple: In function `yyparse':
!      /usr/local/lib/bison.simple:625: virtual memory exhausted
!

that too indicates a problem with disk space, ulimit, or MAXUMEM. !

On a System V release 4 system, make sure /usr/bin precedes /usr/ucb in PATH. The cc command in /usr/ucb uses libraries which have bugs. !

!

vax-dec-ultrix

!

Don't try compiling with VAX C (vcc). It produces incorrect code in some cases (for example, when alloca is used). !

!

we32k-*-*

!

These computers are also known as the 3b2, 3b5, 3b20 and other similar names. (However, the 3b1 is actually a 68000.) These configurations are obsoleted in GCC 3.1. !

Don't use -g when compiling with the system's compiler. The system's linker seems to be unable to handle such a large program with debugging information. !

The system's compiler runs out of capacity when compiling stmt.c in GCC. You can work around this by building cpp in GCC first, then use that instead of the system's preprocessor with the system's C compiler to compile stmt.c. Here is how: ! 

     mv /lib/cpp /lib/cpp.att
!      cp cpp /lib/cpp.gnu
!      echo '/lib/cpp.gnu -traditional ${1+"$@"}' > /lib/cpp
!      chmod +x /lib/cpp
!
!

The system's compiler produces bad code for some of the GCC optimization files. So you must build the stage 2 compiler without optimization. Then build a stage 3 compiler with optimization. That executable should work. Here are the necessary commands: ! 

     make LANGUAGES=c CC=stage1/xgcc CFLAGS="-Bstage1/ -g"
!      make stage2
!      make CC=stage2/xgcc CFLAGS="-Bstage2/ -g -O"
!
!

You may need to raise the ULIMIT setting to build a C++ compiler, as the file cc1plus is larger than one megabyte. !

!

xtensa-*-elf

!

This target is intended for embedded Xtensa systems using the newlib C library. It uses ELF but does not support shared objects. Designed-defined instructions specified via the Tensilica Instruction Extension (TIE) language are only supported through inline assembly. !

The Xtensa configuration information must be specified prior to building GCC. The gcc/config/xtensa/xtensa-config.h header file contains the configuration information. If you created your own Xtensa configuration with the Xtensa Processor Generator, the downloaded files include a customized copy of this header file, which you can use to replace the default header file. !

!

xtensa-*-linux*

!

This target is for Xtensa systems running GNU/Linux. It supports ELF shared objects and the GNU C library (glibc). It also generates position-independent code (PIC) regardless of whether the -fpic or -fPIC options are used. In other respects, this target is the same as the xtensa-*-elf target. !

!

Microsoft Windows (32-bit)

!

A port of GCC 2.95.x is included with the Cygwin environment. !

Current (as of early 2001) snapshots of GCC will build under Cygwin without modification. !

!

OS/2

!

GCC does not currently support OS/2. However, Andrew Zabolotny has been working on a generic OS/2 port with pgcc. The current code can be found at http://www.goof.com/pcg/os2/. !

An older copy of GCC 2.8.1 is included with the EMX tools available at ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/emx+gcc/. !

!

Older systems

!

GCC contains support files for many older (1980s and early 1990s) Unix variants. For the most part, support for these systems has not been deliberately removed, but it has not been maintained for several years and may suffer from bitrot. Support from some systems *************** has been removed from GCC 3: fx80, ns32- *** 2081,2094 **** gmicro, spur; most of these targets had not been updated since GCC version 1. !

We are planning to remove support for more older systems, starting in GCC 3.1. Each release will have a list of "obsoleted" systems. Support for these systems is still present in that release, but configure will fail unless the --enable-obsolete option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. !

Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of the targets that never worked with GCC 2, starting from the last --- 2083,2096 ---- gmicro, spur; most of these targets had not been updated since GCC version 1. !

We are planning to remove support for more older systems, starting in GCC 3.1. Each release will have a list of "obsoleted" systems. Support for these systems is still present in that release, but configure will fail unless the --enable-obsolete option is given. Unless a maintainer steps forward, support for these systems will be removed from the next release of GCC. !

Support for older systems as targets for cross-compilation is less problematic than support for them as hosts for GCC; if an enthusiast wishes to make such a target work again (including resurrecting any of the targets that never worked with GCC 2, starting from the last *************** CVS version before they were removed), p *** 2097,2103 **** would be likely to be accepted, since they should not affect the support for more modern targets. !

Support for old systems as hosts for GCC can cause problems if the workarounds for compiler, library and operating system bugs affect the cleanliness or maintainability of the rest of GCC. In some cases, to bring GCC up on such a system, if still possible with current GCC, may --- 2099,2105 ---- would be likely to be accepted, since they should not affect the support for more modern targets. !

Support for old systems as hosts for GCC can cause problems if the workarounds for compiler, library and operating system bugs affect the cleanliness or maintainability of the rest of GCC. In some cases, to bring GCC up on such a system, if still possible with current GCC, may *************** the old-releases directory *** 2109,2135 **** be avoided using fixincludes, but bugs or deficiencies in libraries and the operating system may still cause problems. !

For some systems, old versions of GNU binutils may also be useful, and are available from pub/binutils/old-releases on sources.redhat.com mirror sites. !

Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. !

!

all ELF targets (SVR4, Solaris 2, etc.)

!

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. !

Return to the GCC Installation page ! --- 2111,2137 ---- be avoided using fixincludes, but bugs or deficiencies in libraries and the operating system may still cause problems. !

For some systems, old versions of GNU binutils may also be useful, and are available from pub/binutils/old-releases on sources.redhat.com mirror sites. !

Some of the information on specific systems above relates to such older systems, but much of the information about GCC on such systems (which may no longer be applicable to current GCC) is to be found in the GCC texinfo manual. !

!

all ELF targets (SVR4, Solaris 2, etc.)

!

C++ support is significantly better on ELF targets if you use the GNU linker; duplicate copies of inlines, vtables and template instantiations will be discarded automatically. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/INSTALL/test.html gcc-3.2.3/INSTALL/test.html *** gcc-3.2.2/INSTALL/test.html Wed Feb 5 03:09:30 2003 --- gcc-3.2.3/INSTALL/test.html Tue Apr 22 06:56:34 2003 *************** *** 1,12 **** ! Installing GCC: Testing ! ! ! ! ! !

B

efore you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the gcc-testresults mailing list. --- 1,14 ---- ! ! Installing GCC: Testing ! ! ! ! ! !

Installing GCC: Testing

! Before you install GCC, we encourage you to run the testsuites and to compare your results with results from a similar configuration that have been submitted to the gcc-testresults mailing list. *************** This step is optional and may require yo *** 14,109 **** but it can give you confidence in your new GCC installation or point out problems before you install and start using your new GCC. !

First, you must have downloaded the testsuites. These are part of the full distribution, but if you downloaded the "core" compiler plus any front ends, you must download the testsuites separately. !

Second, you must have the testing tools installed. This includes a current version of DejaGnu; dejagnu 1.3 is not sufficient. It also includes Tcl and Expect; the DejaGnu site has links to these. !

Now you may need specific preparations: !

    !
  • The following environment variables may need to be set appropriately, as in the following example (which assumes that DejaGnu has been installed under /usr/local): ! 
         TCL_LIBRARY = /usr/local/share/tcl8.0
!      DEJAGNULIBS = /usr/local/share/dejagnu
!
    !

    On systems such as Cygwin, these paths are required to be actual paths, not mounts or links; presumably this is due to some lack of portability in the DejaGnu code. !

    If the directories where runtest and expect were installed are in the PATH, it should not be necessary to set these environment variables. !

!

Finally, you can run the testsuite (which may take a long time): ! 

     cd objdir; make -k check
!
!

The testing process will try to test as many components in the GCC distribution as possible, including the C, C++, Objective-C and Fortran compilers as well as the C++ and Java runtime libraries. !

While running the testsuite, DejaGnu might emit messages resembling WARNING: Couldn't find the global config file. or WARNING: Couldn't find tool init file. These messages are harmless and do not affect the validity of the tests. !

How can I run the test suite on selected tests?

!

As a first possibility to cut down the number of tests that are run it is possible to use make check-gcc or make check-g++ in the gcc subdirectory of the object directory. To further cut down the tests the following is possible: ! 

    make check-gcc RUNTESTFLAGS="execute.exp other-options"
!
!

This will run all gcc execute tests in the testsuite. ! 

    make check-g++ RUNTESTFLAGS="old-deja.exp=9805* other-options"
!
!

This will run the g++ "old-deja" tests in the testsuite where the filename matches 9805*. !

The *.exp files are located in the testsuite directories of the GCC source, the most important ones being compile.exp, execute.exp, dg.exp and old-deja.exp. To get a list of the possible *.exp files, pipe the output of make check into a file and look at the ! Running ... .exp lines. !

To run only the tests for a library, run make check from the the library's testsuite in a subdirectory of the object directory: libstdc++-v3/testsuite or libcgj/testsuite. !

Additional testing for Java Class Libraries

!

The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by specifying the location of the Mauve tree when invoking make, as in make MAUVEDIR=~/mauve check. !

How to interpret test results

!

After the testsuite has run you'll find various *.sum and *.log files in the testsuite subdirectories. The *.log files contain a detailed log of the compiler invocations and the corresponding results, the *.sum files summarize the results. These summaries list all the tests that have been run with a corresponding status code: !

!

It is normal for some tests to report unexpected failures. At the current time our testing harness does not allow fine grained control over whether or not a test is expected to fail. We expect to fix this problem in future releases. !

Submitting test results

!

If you want to report the results to the GCC project, use the contrib/test_summary shell script. Start it in the objdir with ! 

         srcdir/contrib/test_summary -p your_commentary.txt \
!              -m gcc-testresults@gcc.gnu.org |sh
!
!

This script uses the Mail program to send the results, so make sure it is in your PATH. The file your_commentary.txt is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please *************** behave on different platforms and compar *** 139,147 **** few failing testcases are possible even on released versions and you should look here first if you think your results are unreasonable. !

Return to the GCC Installation page ! --- 141,149 ---- few failing testcases are possible even on released versions and you should look here first if you think your results are unreasonable. !

Return to the GCC Installation page ! diff -Nrc3pad gcc-3.2.2/bugs.html gcc-3.2.3/bugs.html *** gcc-3.2.2/bugs.html Wed Feb 5 03:09:23 2003 --- gcc-3.2.3/bugs.html Tue Apr 22 06:56:23 2003 *************** *** 8,14 ****

GCC Bugs

The latest version of this document is always available at ! http://www.gnu.org/software/gcc/bugs.html.

--- 8,14 ----

GCC Bugs

The latest version of this document is always available at ! http://gcc.gnu.org/bugs.html.

*************** *** 24,30 ****
  • Detailed bug reporting instructions when using a precompiled header
    • -
  • Managing Bugs (GNATS and the test-suite)
  • Frequently Reported Bugs in GCC
    • General
      • --- 24,29 ---- *************** use it.

      *** 275,306 ****

      Please don't send us the actual precompiled header. It is likely to be very large and we can't use it to reproduce the problem.

      - -

      Managing Bugs (GNATS and the test-suite)

      - -

      This section contains information mostly intended for GCC - contributors.

      - -

      If you find a bug, but you are not fixing it (yet):

      -
        -
      1. Create a (minimal) test-case.
        2. -
      2. Add the test-case to our test-suite, marking it as XFAIL unless - the bug is a regression.
        3. -
      3. Add a bug report referencing the test-case to GNATS.
        4. -
      - -

      If you fix a bug for which there is already a GNATS entry:

      -
        -
      1. Remove the XFAIL on the test-case.
        2. -
      2. Close the bug report in GNATS.
        3. -
      - -

      If you find a bug, and you are fixing it right then:

      -
        -
      1. Create a (minimal) test-case.
        2. -
      2. Add the test-case to our test-suite, marking it as PASS.
        3. -
      3. Check in your fixes.
        4. -
      --- 274,279 ---- diff -Nrc3pad gcc-3.2.2/config/ChangeLog gcc-3.2.3/config/ChangeLog *** gcc-3.2.2/config/ChangeLog Wed Feb 5 03:02:08 2003 --- gcc-3.2.3/config/ChangeLog Tue Apr 22 06:14:11 2003 *************** *** 1,3 **** --- 1,7 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + 2003-02-05 Release Manager * GCC 3.2.2 Released. diff -Nrc3pad gcc-3.2.2/config/mpw/ChangeLog gcc-3.2.3/config/mpw/ChangeLog *** gcc-3.2.2/config/mpw/ChangeLog Wed Feb 5 03:02:05 2003 --- gcc-3.2.3/config/mpw/ChangeLog Tue Apr 22 06:14:08 2003 *************** *** 1,3 **** --- 1,7 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + 2003-02-05 Release Manager * GCC 3.2.2 Released. diff -Nrc3pad gcc-3.2.2/config-ml.in gcc-3.2.3/config-ml.in *** gcc-3.2.2/config-ml.in Wed Jun 13 02:12:07 2001 --- gcc-3.2.3/config-ml.in Wed Feb 12 17:44:49 2003 *************** multi-do: *** 553,558 **** --- 553,559 ---- LIBCFLAGS="$(LIBCFLAGS) $${flags}" \ LIBCXXFLAGS="$(LIBCXXFLAGS) $${flags}" \ LDFLAGS="$(LDFLAGS) $${flags}" \ + DESTDIR="$(DESTDIR)" \ $(DO)); then \ true; \ else \ diff -Nrc3pad gcc-3.2.2/contrib/ChangeLog gcc-3.2.3/contrib/ChangeLog *** gcc-3.2.2/contrib/ChangeLog Wed Feb 5 03:01:37 2003 --- gcc-3.2.3/contrib/ChangeLog Tue Apr 22 06:14:14 2003 *************** *** 1,3 **** --- 1,7 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + 2003-02-05 Release Manager * GCC 3.2.2 Released. diff -Nrc3pad gcc-3.2.2/contrib/regression/ChangeLog gcc-3.2.3/contrib/regression/ChangeLog *** gcc-3.2.2/contrib/regression/ChangeLog Wed Feb 5 03:01:34 2003 --- gcc-3.2.3/contrib/regression/ChangeLog Tue Apr 22 06:14:17 2003 *************** *** 1,3 **** --- 1,7 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + 2003-02-05 Release Manager * GCC 3.2.2 Released. diff -Nrc3pad gcc-3.2.2/faq.html gcc-3.2.3/faq.html *** gcc-3.2.2/faq.html Wed Feb 5 03:09:29 2003 --- gcc-3.2.3/faq.html Tue Apr 22 06:56:29 2003 *************** *** 9,20 ****

      GCC Frequently Asked Questions

      The latest version of this document is always available at ! http://www.gnu.org/software/gcc/faq.html.

      This FAQ tries to answer specific questions concerning GCC. For general information regarding C, C++, resp. Fortran please check the comp.lang.c FAQ, ! comp.std.c++ FAQ, and the Fortran Information page.

      --- 9,20 ----

      GCC Frequently Asked Questions

      The latest version of this document is always available at ! http://gcc.gnu.org/faq.html.

      This FAQ tries to answer specific questions concerning GCC. For general information regarding C, C++, resp. Fortran please check the comp.lang.c FAQ, ! comp.std.c++ FAQ, and the Fortran Information page.

      *************** than we've had before.

      *** 159,168 **** past few months. The paper which started all of this introduced two terms: A cathedral development model versus a bazaar development model. The paper is written by Eric S. Raymond, it is ! called ``The ! Cathedral and the Bazaar''. The paper is a useful starting point ! for discussions.
    • --- 159,166 ---- past few months. The paper which started all of this introduced two terms: A cathedral development model versus a bazaar development model. The paper is written by Eric S. Raymond, it is ! called ``The Cathedral and the Bazaar''. ! The paper is a useful starting point for discussions.
    diff -Nrc3pad gcc-3.2.2/gcc/ChangeLog gcc-3.2.3/gcc/ChangeLog *** gcc-3.2.2/gcc/ChangeLog Wed Feb 5 03:01:09 2003 --- gcc-3.2.3/gcc/ChangeLog Tue Apr 22 06:14:38 2003 *************** *** 1,3 **** --- 1,622 ---- + 2003-04-22 Release Manager + + * GCC 3.2.3 Released. + + 2003-04-16 John David Anglin + + PR/10271 + * pa-protos.h (function_arg): Remove last argument. + * pa.c (function_arg): Likewise. Use CUMULATIVE_ARGS struct instead. + * pa.h (struct hppa_args): Add member incoming. + (INIT_CUMULATIVE_ARGS, INIT_CUMULATIVE_INCOMING_ARGS): Initialize + member incoming. + (FUNCTION_ARG): Revise call to function_arg. + (FUNCTION_INCOMING_ARG): Delete. + + 2003-04-15 Jason Merrill + + PR middle-end/10336, c++/10401 + * jump.c (never_reached_warning): Also stop looking if we reach the + beginning of the function. + + 2003-04-14 Hans-Peter Nilsson + + PR target/10377 + * config/cris/cris.md ("*mov_sideqi", "*mov_sidehi") + ("*mov_sidesi", "*mov_sideqi_mem", "*mov_sidehi_mem") + ("*mov_sidesi_mem", "*clear_sidesi", "*clear_sidehi") + ("*clear_sideqi", "*ext_sideqihi", "*ext_sideqisi") + ("*ext_sidehisi", "*op_sideqi", "*op_sidehi", "*op_sidesi") + ("*op_swap_sideqi", "*op_swap_sidehi", "*op_swap_sidesi") + ("*extopqihi_side", "*extopqisi_side", "*extophisi_side") + ("*extopqihi_swap_side", "*extopqisi_swap_side") + ("*extophisi_swap_side", 8th, 9th, 10th, 11th, 14th peepholes): + When next to constraint R, replace constraint i with n. + + 2003-04-10 Bob Wilson + + * config/xtensa/xtensa.h (MAX_INT_TYPE_SIZE, IMPLICIT_FIX_EXPR, + EASY_DIV_EXPR): Delete poisoned macro definitions. + + 2003-04-09 Richard Henderson + + PR opt/10352 + Tue Jul 23 21:49:24 2002 J"orn Rennecke + * simplify-rtx.c (simplify_subreg): When converting to a non-int + mode, try to convert to an integer mode of matching size first. + + 2003-04-09 Alan Modra + + * config/rs6000/rs6000.c (rs6000_emit_prologue): Use correct mode to + set frame pointer. + + 2003-04-03 Jason Merrill + + PR c/10175 + * jump.c (never_reached_warning): Look backwards for a line note. + + 2003-04-02 Richard Henderson + + * dwarf2out.c (output_call_frame_info): Ignore fde->nothrow as an + optimization when flag_exceptions not enabled. + + 2003-03-30 Kaveh R. Ghazi + + PR other/6955 + * collect2.c (collect_wait): Use WCOREDUMP and fix output message. + * system.h (WCOREDUMP, WCOREFLG): Define if necessary. + + 2003-03-29 Arpad Beszedes + + PR middle-end/9967 + * builtins.c (expand_builtin_fputs): When optimizing for size, + don't transform fputs into fwrite. + + 2003-03-29 Albert Chin-A-Young + DJ Delorie , + Bruce Korb + + * fixinc/inclhack.def (solaris_mutex_init_1): New; Fix + buggy Solaris mutex/cond initializers. + (solaris_mutex_init): Rename to solaris_mutex_init_2. + * fixinc/fixincl.x: Regenerate. + * fixinc/tests/base/pthread.h: Update. + + 2003-03-29 Nathanael Nerode + + * fixinc/fixinc.interix: Remove completely dead code + + 2003-03-29 Ulrich Weigand + + PR target/7784 + * reload.c (maybe_memory_address_p): New function. + (find_reloads_address): Use it instead of memory_address_p. + + 2003-03-29 Alan Modra + + * config/rs6000/rs6000.h (FUNCTION_VALUE_REGNO_P): Respect + TARGET_HARD_FLOAT. Reformat. + (FUNCTION_ARG_REGNO_P): Likewise, and remove unneeded casts. + + 2003-03-29 Glen Nakamura + + PR c/8224 + * fold-const.c (extract_muldiv_1): Don't pass through type conversions + when signedness changes for division or modulus. + + 2003-03-29 Alan Modra + + * reload1.c (reload_as_needed): Allow a USE in asm reloads. + + 2003-03-28 Olivier Hainque + + PR ada/9953 + * ada/Makefile.in (gnatlib configuration for HPUX): Split + the general section for HPUX into specific sections for + HPUX 10 and HPUX 11. + + 2003-03-28 Eric Botcazou + + PR target/10067 + * config/sparc/sparc.md (jump pattern): Correct order + when issuing the annuling marker. + + 2003-03-28 Eric Botcazou + + PR c/8281 + * config/sparc/sparc.md (movdi_insn_sp32_v9): Remove 'f-f' alternative. + (movdi reg/reg split): Match only on sparc32, and v9 when int regs. + + 2003-03-28 Eric Botcazou + Richard Henderson + + PR target/10114 and PR target/10084 + * dwarf2out.c (mem_loc_descriptor): Handle LO_SUM. + + 2003-03-27 Janis Johnson + + PR sw-bug/10234 + * system.h (GCCBUGURL): Reference GCC web site. + + 2003-03-26 Richard Henderson + + * cfgrtl.c (try_redirect_by_replacing_jump): Disable removing + tablejumps with no optimization. + + 2003-03-27 Rainer Orth + + * config/mips/iris6.h (CPLUSPLUS_CPP_SPEC): Define __c99. + + * fixinc/inclhack.def (irix___restrict): Don't change __restrict + for C++ on IRIX 6.5.1[89]. + * fixinc/tests/base/internal/sgimacros.h: New file. + + * fixinc/inclhack.def (irix_wcsftime): Use XPG5 variant for C99. + * fixinc/fixincl.x: Regenerate. + * fixinc/tests/base/internal/wchar_core.h: New file. + + 2003-03-26 Eric Botcazou + + PR target/7784 + * reload.c (find_reloads_address): Handle + (PLUS (PLUS (REG) (REG)) (CONST_INT)) form for + all base registers. + + 2003-03-25 Jason Merrill + + PR optimization/10171 + * unroll.c (unroll_loop): Don't delete the jump at the end unless + we also delete a jump at the beginning. + + 2003-03-25 Gerald Pfeifer + + * doc/passes.texi (Passes): Properly document that we do not + perform jump2 any longer; remove command-line option -dJ. + + 2003-03-25 Eric Botcazou + + PR optimization/8746 + * config/i386/i386.md (and promoting splitters): Disable HImode to + SImode promoting when the sign bit matters and is not preserved. + Disable promoting when optimizing for size. + + 2003-03-23 Eric Botcazou + + PR optimization/9414 + * config/sparc/sparc.md (widening peepholes): Use + widen_memory_access instead of change_address. + + 2003-03-23 Daniel Jacobowitz + + Fix PR target/9797. + * stmt.c (expand_decl_init): Call push_temp_slots () and + pop_temp_slots (). + + 2003-03-23 Richard Henderson + + * cfgcleanup.c (try_optimize_cfg): Allow merging of tablejumps + before flow2. + * cfgrtl.c (try_redirect_by_replacing_jump): Similarly. + + 2003-03-23 Richard Henderson + + PR opt/10116 + * ifcvt.c (find_if_block): Disallow tablejump insns outgoing + from then_bb or else_bb after flow2. + + 2003-03-22 John David Anglin + + * pa.c (output_cbranch, output_bb, output_bvb): Output nop for + conditional branch to the following instruction. + + 2003-03-21 Volker Reichelt + + PR doc-bug/9813 + * doc/extend.texi: Move misplaced paragraph about underscores in + variables in macros. + + 2003-03-21 Eric Botcazou + Richard Henderson + + PR optimization/8366 + * config/sparc/sparc.h: (SYMBOLIC_CONST): New macro. + (GO_IF_LEGITIMATE_ADDRESS): Use it. Reject the form + PIC+SYMBOLIC_CONST in other modes than Pmode. + (GO_IF_MODE_DEPENDENT_ADDRESS): Use it. Mark + the form PIC+SYMBOLIC_CONST as mode dependent. + + 2003-03-20 Richard Henderson + + * fold-const.c (extract_muldiv_1): Revert changing order of + operands in case MULT_EXPR of 2003-02-16 patch. + + 2003-03-19 Eric Botcazou + + PR optimization/8746 + Backport from mainline: + + Thu Jun 6 23:14:46 CEST 2002 Jan Hubicka + + * i386.md (and promoting splitters): Disable QI to SImode promoting + when doing so changes immediate to be 32bit. + + 2003-03-19 Jakub Jelinek + + * stmt.c (expand_start_case): Call emit_queue (). + + 2003-03-19 Jakub Jelinek + + * ifcvt.c (dead_or_predicable): Fail if there are any references + to tablejump in merge_bb other than the final JUMP_INSN. + + 2003-03-19 Alan Modra + + PR target/10073 + * combine.c (force_to_mode ): Use gen_int_mode. + + 2003-03-17 Dave Love + Rainer Orth + + * config/alpha/osf.h (CPP_PREDEFINES): Define __digital__, + __arch64__ to match Compaq cc. + + 2003-03-17 Andreas Schwab + + PR target/7248 + * config/m68k/m68k.md (iordi3): Fix setting low half to -1. From + martin@blom.org. + + 2003-03-16 Richard Henderson + + * config/i386/i386.md (movstrictqi, movstrictqi_1): Check + optimize_size as well. + + 2003-03-16 Falk Hueffner + + PR target/9164 + * tree.c (get_narrower): For extensions with unchanged bit number, + return the unsignedness of the outer mode. + + 2003-03-14 Jakub Jelinek + + * config/rs6000/rs6000.c (rs6000_emit_load_toc_table): Don't call + rs6000_maybe_dead if !fromprolog. + + 2003-03-14 Eric Botcazou + + PR optimization/8396 + * tree-inline.c (initialize_inlined_parameters): Make sure the value + of read-only constant arguments is passed with the right type. + + 2003-03-14 Andreas Jaeger + + * config/i386/linux64.h (CPP_SPEC): Define __LP64__ and _LP64 for + 64-bit. + + 2003-03-12 Richard Henderson + + PR opt/8178 + * config/i386/i386.md (ffssi2): Tighten op1 predicate to + the requirements of the output insns. + + 2003-03-12 Andrew Lewycky + + PR c++/7050 + * expr.c (store_expr): Don't attempt to store void-typed trees, + just evaluate them for side effects. + + 2003-03-12 Bob Wilson + + Backport from mainline: + 2003-03-12 Bob Wilson + + * config/xtensa/xtensa.md (adddi3): Don't clobber source operand used + to detect carry. + (subdi3): Reorder emitted instructions. + + 2003-03-12 Eric Botcazou + + PR c/9928 + * c-decl.c (duplicate_decls): Discard the initializer of the new decl + only if it is a VAR_DECL. + + 2003-03-12 Eric Botcazou + + PR optimization/9888 + * config/i386/i386.md (jcc_1): Fix range. + (jcc_2): Likewise. + (jump): LIkewise. + (doloop_end_internal): Likewise. + + 2003-03-12 Eric Botcazou + + PR optimization/9888 + Backport patch from mainline: + + Tue Nov 19 23:50:56 CET 2002 Jan Hubicka + + * i386.md (length_immediate): Do not refer to insn address. + (jcc*, jmp patterns): Compute length explicitly. + (doloop_end_internal pattern): Unconditionally set the type to "ibr". + + 2003-03-12 Eric Botcazou + + PR optimization/9888 + * config/i386/i386.md (movsi_1): Remove special alternatives + for %eax register. + (movhi_1): Likewise. + * config/i386/i386.c (memory_address_length): Do not use + short displacement when there is no base. + (ix86_attr_length_address_default): Handle LEA instructions. + + 2003-03-09 Eric Botcazou + + PR optimization/9888 + Backport patch from mainline: + + 2002-07-03 Eric Botcazou + Jeff Law + + * i386.md (length_immediate attribute): Fix typo. + (length_address attribute): Likewise. + (modrm attribute): Set it to 0 for immediate call instructions. + (jcc_1 pattern): Set modrm attribute to 0. + (jcc_2 pattern ): Likewise. + (jump pattern): Likewise. + (doloop_end_internal pattern): Explicitly set length. + (leave pattern): Fix typo. + (leave_rex64 pattern): Likewise. + + 2003-03-08 Eric Botcazou + + PR middle-end/7796 + * unroll.c (calculate_giv_inc): Handle constants being + loaded with LSHIFTRT. + + 2003-03-07 Eric Botcazou + + PR optimization/8726 + Backport patch from mainline: + + 2003-01-08 Dale Johannesen + + * function.c (assign_parms): Don't set pretend_args_size if + REG_PARM_STACK_SPACE. + + 2003-03-06 Reinhard Jessich + + PR 9954/other + * config/i386/linux.h (MD_FALLBACK_FRAME_STATE_FOR): Since this uses + it should be wrapped in an inhibit_libc conditional + like the same code in config/i386/linux64.h. + + 2003-03-05 Eric Botcazou + + PR c/9799 + * c-typeck.c (push_init_level): Add sanity check. + + 2003-02-28 Bob Wilson + + Backport following patch: + + 2003-02-28 Bob Wilson + * config.gcc (xtensa-*-linux*): Add t-slibgcc-elf-ver to tmake_file. + + 2003-02-28 Joel Sherrill + + PR 9638/other + * config/i386/i386.c (DEFAULT_PCC_STRUCT_RETURN): Ensure the + this constant defaults to 1. + + 2003-02-27 Alan Modra + + * config/rs6000/rs6000.md: Add TI constant splitter. + + 2003-02-26 Jan Hubicka + + PR target/8343 + * m68k.md (umulsidi, mulsidi expanders): Use register operand. + + 2003-02-26 David Billinghurst + + * fixinc/fixincl.x: Regenerate + + 2003-02-25 Richard Henderson + + * config/i386/i386.c (function_arg): Pass variable sized + structures correctly on the stack. + + 2003-02-25 Franz Sirl + + PR target/9732 + * config/rs6000/rs6000.c (first_reg_to_save): Handle + PIC_OFFSET_TABLE_REGNUM for -fPIC too. + (rs6000_emit_prologue): Likewise. + (rs6000_emit_epilogue): Likewise. + * config/rs6000/rs6000.h (CONDITIONAL_REGISTER_USAGE): Make + PIC_OFFSET_TABLE_REGNUM a fixed register for -fPIC. + + 2003-02-25 Matthias Klose + + 2003-02-07 Richard Henderson + PR 9226 + * gcse.c (local_cprop_find_used_regs): New. + (local_cprop_pass): Use it. + + 2003-02-25 Matthias Klose + + * config.gcc (m68k-*-linux*): Add crtbeginT.o to extra_parts. + + 2003-02-24 Rainer Orth + + * config/alpha/osf.h (CPP_SUBTARGET_SPEC): Rename + __EXTERN_PREFIX to __PRAGMA_EXTERN_PREFIX. + * doc/extend.texi (Tru64 Pragmas): Reflect this. + + * fixinc/inclhack.def (alpha___extern_prefix): Indicate #pragma + extern_prefix support for Tru64 UNIX V5 . + * fixinc/fixincl.x: Regenerate. + * fixinc/tests/base/sys/stat.h [ALPHA___EXTERN_PREFIX_CHECK]: New + testcase. + Fixes PR c/5059, c/6126, other/9671. + + 2003-02-24 David Billinghurst + + Fixes PR libgcj/9652. + Backport patch from mainline: + 2003-02-12 Rainer Orth + + * fixinc/inclhack.def (irix_socklen_t): Fix broken IRIX 6.5.1[78] + socklen_t definition. + * fixinc/fixincl.x: Regenerate. + * fixinc/tests/base/sys/socket.h: New file. + + 2003-02-23 Hans-Peter Nilsson + + * regmove.c (optimize_reg_copy_1): Do not replace a hard register + in an asm. + + 2003-02-22 Steven Bosscher + + PR other/3782 + * toplev.c (process_options): If flag_detailed_statistics is set, + then set time_report as well. + + PR c/8828 + * jump.c (never_reached_warning): Don't fall through BARRRIER + insns. Update comments to reflect what the function really does. + + 2003-02-21 Richard Henderson + + 2003-01-06 Richard Henderson + * config/alpha/alpha.md (movdi_er_high_g): Allow all symbols. + + 2003-02-21 Glen Nakamura + + PR optimization/8613 + * builtins.c (expand_builtin): Emit postincrements before expanding + builtin functions. + + 2003-02-20 Randolph Chung + Eric Botcazou + + PR optimization/9768 + Backport patch from mainline: + + 2002-03-21 DJ Delorie + + * bb-reorder.c (make_reorder_chain_1): Protect against + when redundant edges are omitted. + * predict.c (dump_prediction): Likewise. + + 2003-02-20 BAN Nobuhiro + + PR c/9678 + * config/i386/i386.h (CPP_CPUCOMMON_SPEC): Fix typo. + + 2003-02-18 Jakub Jelinek + + * real.c (asctoeg): Handle denormals in hexadecimal notation. + + 2003-02-16 Arend Bayer + Richard Henderson + + PR c/8068 + * fold-const.c (extract_muldiv_1): Rename from extract_muldiv; + rearrange mult arguments for less recursion. + (extract_muldiv): New. Prevent runaway recursion. + + 2003-02-14 Falk Hueffner + + PR optimization/7702 + * reload1.c (reload_cse_simplify_set): Honor + CLASS_CANNOT_CHANGE_MODE_P. + + 2003-02-13 John David Anglin + + * inclhack.def (hpux_long_double): Tighten select and add bypass + regexp. + * fixincl.x: Rebuilt. + + 2003-02-13 Josef Zlomek + + * cfgcleanup.c (outgoing_edges_match): When there is single outgoing + edge and block ends with a jump insn it must be simple jump. + + 2003-02-12 John David Anglin + + PR9275 and PR8694 + * inclhack.def (hpux_long_double, hpux10_ctype_declarations1, + hpux10_ctype_declarations2, hpux_ctype_macros): New hacks. + * fixincl.x: Rebuilt. + * tests/base/stdlib.h: Update. + * tests/base/ctype.h: New file. + + 2003-02-12 Kaveh R. Ghazi + + * mips.h (FP_INC): Define. + + Backport fix for PR6362: + 2002-10-01 Richard Sandiford + + * config/mips/mips-protos.h (mips_emit_fcc_reload): Declare. + * config/mips/mips.h (PREDICATE_CODES): Add fcc_register_operand. + * config/mips/mips.c (fcc_register_operand): New function. + (mips_emit_fcc_reload): New function, extracted from reload_incc. + * cnfig/mips/mips.md (reload_incc): Change destination prediate + to fcc_register_operand. Remove misleading source constraint. + Use mips_emit_fcc_reload. + (reload_outcc): Duplicate reload_incc. + + 2003-02-11 Bob Wilson + + Backport following patch: + + 2003-02-11 Bob Wilson + + * config/xtensa/xtensa.md (set_frame_ptr): Change rtl to set reg a7. + * config/xtensa/xtensa.c (xtensa_reorg): Search for UNSPECV_SET_FP + as a SET pattern. + + 2003-02-10 Eric Botcazou + Christian Ehrhardt + + PR c/7741 + * c-decl.c (duplicate_decls): Discard the initializer of the + new decl when the types are conflicting. + + 2003-02-01 Daniel Jacobowitz + + * dwarf2out.c (gen_type_die): Check for typedefs before calling + for TYPE_MAIN_VARIANT. + + 2003-02-07 John David Anglin + + * pa.c (output_millicode_call): Use $PIC_pcrel$0 for long PIC + millicode calls when !TARGET_SOM and TARGET_GAS is true. + * pa.md (jump): Likewise. + + 2003-02-06 Eric Botcazou + Richard Henderson + + PR c/9530 + * config/i386/i386.h (FUNCTION_OK_FOR_SIBCALL): Forbid sibcalls + from functions that return a float to functions that don't. + + 2003-02-03 Bob Wilson + + * config/xtensa/xtensa.c (order_regs_for_local_alloc): Order the + coprocessor registers before floating-point registers. + * config/xtensa/xtensa.h (REG_ALLOC_ORDER): Adjust register numbers + to account for a previously removed register. + (SPEC_REG_FIRST, SPEC_REG_LAST, SPEC_REG_NUM, COUNT_REGISTER_REGNUM): + Delete unused macros. + + 2003-02-05 Gabriel Dos Reis + + * doc/include/gcc-common.texi: Bump version. + * version.c(version_string): Update. + 2003-02-05 Release Manager * GCC 3.2.2 Released. *************** *** 31,73 **** 2002-09-16 Richard Henderson ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Adjust SIZE ! as well as OFFSET for BITPOS. 2002-09-08 Jan Hubicka ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Fix array_ref ! handling. 2002-07-29 Richard Henderson ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Rename from ! set_mem_attributes and add BITPOS argument. Subtract it from ! OFFSET when same is adjusted. ! (set_mem_attributes): New wrapper function. ! * expr.c (expand_assignment): Use set_mem_attributes_minus_bitpos; ! remove offset adjustment hack. ! * expr.h (set_mem_attributes_minus_bitpos): Declare. 2002-07-25 Richard Henderson ! * emit-rtl.c (set_mem_attributes): Fix size and alignment thinkos ! in ARRAY_REF of DECL_P case. 2002-07-21 Richard Henderson ! * emit-rtl.c (set_mem_attributes): Preserve indirection of PARM_DECL ! when flag_argument_noalias == 2. ! * alias.c (nonoverlapping_memrefs_p): Handle that. ! * print-rtl.c (print_mem_expr): Likewise. 2002-06-03 Dan Nicolaescu ! * alias.c (nonoverlapping_memrefs_p): Fix off by one error. 2003-02-03 Steve Ellcey ! * config/pa/pa64-hpux.h (INIT_ENVIRONMENT): New. 2003-02-01 Jakub Jelinek --- 650,692 ---- 2002-09-16 Richard Henderson ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Adjust SIZE ! as well as OFFSET for BITPOS. 2002-09-08 Jan Hubicka ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Fix array_ref ! handling. 2002-07-29 Richard Henderson ! * emit-rtl.c (set_mem_attributes_minus_bitpos): Rename from ! set_mem_attributes and add BITPOS argument. Subtract it from ! OFFSET when same is adjusted. ! (set_mem_attributes): New wrapper function. ! * expr.c (expand_assignment): Use set_mem_attributes_minus_bitpos; ! remove offset adjustment hack. ! * expr.h (set_mem_attributes_minus_bitpos): Declare. 2002-07-25 Richard Henderson ! * emit-rtl.c (set_mem_attributes): Fix size and alignment thinkos ! in ARRAY_REF of DECL_P case. 2002-07-21 Richard Henderson ! * emit-rtl.c (set_mem_attributes): Preserve indirection of PARM_DECL ! when flag_argument_noalias == 2. ! * alias.c (nonoverlapping_memrefs_p): Handle that. ! * print-rtl.c (print_mem_expr): Likewise. 2002-06-03 Dan Nicolaescu ! * alias.c (nonoverlapping_memrefs_p): Fix off by one error. 2003-02-03 Steve Ellcey ! * config/pa/pa64-hpux.h (INIT_ENVIRONMENT): New. 2003-02-01 Jakub Jelinek *************** *** 89,101 **** * config/m68k/m68k.md (tablejump+2): Don't sign extend an address register. ! * config/m68k/apollo68.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/coff.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/linux.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/m68kelf.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/mot3300.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/netbsd-elf.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/pbb.h (ASM_RETURN_CASE_JUMP): Likewise. 2003-01-30 Ralf Corsepius --- 708,720 ---- * config/m68k/m68k.md (tablejump+2): Don't sign extend an address register. ! * config/m68k/apollo68.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/coff.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/linux.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/m68kelf.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/mot3300.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/netbsd-elf.h (ASM_RETURN_CASE_JUMP): Likewise. ! * config/m68k/pbb.h (ASM_RETURN_CASE_JUMP): Likewise. 2003-01-30 Ralf Corsepius *************** *** 182,189 **** 2003-01-27 Richard Earnshaw ! * function.c (purge_addressof_1): After pushing anaddressed register ! onto the stack, simplify the result. 2003-01-25 Eric Botcazou --- 801,808 ---- 2003-01-27 Richard Earnshaw ! * function.c (purge_addressof_1): After pushing anaddressed register ! onto the stack, simplify the result. 2003-01-25 Eric Botcazou *************** *** 200,206 **** of *both* the file name and the fix name. 2003-01-25 Eric Botcazou ! Christian Ehrhardt PR optimization/9279 --- 819,825 ---- of *both* the file name and the fix name. 2003-01-25 Eric Botcazou ! Christian Ehrhardt PR optimization/9279 *************** *** 327,333 **** binary compatibility. 2003-01-07 Benjamin Kosnik ! Sunil Davasam PR libstdc++/9076 * unwind-dw2.c (execute_cfa_program): DW_CFA_undefined, --- 946,952 ---- binary compatibility. 2003-01-07 Benjamin Kosnik ! Sunil Davasam PR libstdc++/9076 * unwind-dw2.c (execute_cfa_program): DW_CFA_undefined, *************** Sat Nov 16 02:54:29 CET 2002 Jan Hubick *** 647,658 **** 2002-11-04 Aldy Hernandez ! Backport patch to fix PR c/8451. ! 2002-04-25 Richard Henderson ! * expmed.c (extract_bit_field): Fall through to generic code rather ! than aborting on subreg special case. 2002-11-01 Mark Mitchell --- 1266,1277 ---- 2002-11-04 Aldy Hernandez ! Backport patch to fix PR c/8451. ! 2002-04-25 Richard Henderson ! * expmed.c (extract_bit_field): Fall through to generic code rather ! than aborting on subreg special case. 2002-11-01 Mark Mitchell diff -Nrc3pad gcc-3.2.2/gcc/NEWS gcc-3.2.3/gcc/NEWS *** gcc-3.2.2/gcc/NEWS Wed Feb 5 03:09:41 2003 --- gcc-3.2.3/gcc/NEWS Tue Apr 22 06:56:45 2003 *************** see ONEWS. *** 7,55 **** ====================================================================== http://gcc.gnu.org/gcc-3.2/index.html ! GCC 3.2 ! November 19, 2002 The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 3.2.1. ! The links below still apply to GCC 3.2.1. ! August 14, 2002 ! The [2]GNU project and the GCC developers are pleased to announce the ! release of GCC 3.2. GCC used to stand for the GNU C Compiler, but since the compiler supports several other languages aside from C, it now stands for the GNU Compiler Collection. ! A list of [3]successful builds is updated as new information becomes available. The GCC developers would like to thank the numerous people that have ! contributed [4]new features, improvements, bug fixes, and other ! changes as well as test results to GCC. This [5]amazing group of ! volunteers is what makes GCC successful. ! For additional information about GCC please refer to the [6]GCC ! project web site or contact the [7]GCC development mailing list. ! To obtain GCC please use [8]our mirror sites, one of the [9]GNU mirror ! sites, or [10]our CVS server. ! _________________________________________________________________ _________________________________________________________________ ! Please send FSF & GNU inquiries & questions to [11]gnu@gnu.org. There ! are also [12]other ways to contact the FSF. ! These pages are maintained by [13]The GCC team. Please send comments on these web pages and GCC to our public ! mailing list at [14]gcc@gnu.org or [15]gcc@gcc.gnu.org, send other ! questions to [16]gnu@gnu.org. Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. --- 7,72 ---- ====================================================================== http://gcc.gnu.org/gcc-3.2/index.html ! GCC 3.2 Release Series ! February 5, 2003 The [1]GNU project and the GCC developers are pleased to announce the ! release of GCC 3.2.2. ! The purpose of the GCC 3.2 release series is to provide a stable ! platform for OS distributors to use building their next releases. A ! primary objective was to stabilize the C++ ABI; we believe that the ! interface to the compiler and the C++ standard library are now ! relatively stable. ! Be aware that C++ code compiled by GCC 3.2.x will (in general) not ! interoperate with code compiled by GCC 3.1.1 or earlier. ! Please refer to our [2]detailed list of news, caveats, and bug-fixes ! for further information. ! ! Release History ! ! GCC 3.2.2 ! February 5, 2003 ([3]changes) ! ! GCC 3.2.1 ! November 19, 2002 ([4]changes) ! ! GCC 3.2 ! August 14, 2002 ([5]changes) ! ! References and Acknowledgements GCC used to stand for the GNU C Compiler, but since the compiler supports several other languages aside from C, it now stands for the GNU Compiler Collection. ! A list of [6]successful builds is updated as new information becomes available. The GCC developers would like to thank the numerous people that have ! contributed new features, improvements, bug fixes, and other changes ! as well as test results to GCC. This [7]amazing group of volunteers is ! what makes GCC successful. ! For additional information about GCC please refer to the [8]GCC ! project web site or contact the [9]GCC development mailing list. ! To obtain GCC please use [10]our mirror sites, one of the [11]GNU ! mirror sites, or [12]our CVS server. _________________________________________________________________ ! Please send FSF & GNU inquiries & questions to [13]gnu@gnu.org. There ! are also [14]other ways to contact the FSF. ! These pages are maintained by [15]The GCC team. Please send comments on these web pages and GCC to our public ! mailing list at [16]gcc@gnu.org or [17]gcc@gcc.gnu.org, send other ! questions to [18]gnu@gnu.org. Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. *************** http://gcc.gnu.org/gcc-3.2/index.html *** 57,142 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-18 [17]Valid XHTML 1.0 References 1. http://www.gnu.org/ ! 2. http://www.gnu.org/ ! 3. http://gcc.gnu.org/gcc-3.2/buildstat.html ! 4. http://gcc.gnu.org/gcc-3.2/changes.html ! 5. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html ! 6. http://gcc.gnu.org/index.html ! 7. mailto:gcc@gcc.gnu.org ! 8. http://gcc.gnu.org/mirrors.html ! 9. http://www.gnu.org/order/ftp.html ! 10. http://gcc.gnu.org/cvs.html ! 11. mailto:gnu@gnu.org ! 12. http://www.gnu.org/home.html#ContactInfo ! 13. http://gcc.gnu.org/about.html ! 14. mailto:gcc@gnu.org ! 15. mailto:gcc@gcc.gnu.org ! 16. mailto:gnu@gnu.org ! 17. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.2/changes.html ! GCC 3.2 Release Series -- Changes, New Features, and Fixes ! ! The purpose of this release series is to provide a stable platform for ! OS distributors to use building their next releases. A primary ! objective was to stabilize the C++ ABI; we believe that the interface ! to the compiler and the C++ standard library are now stable. ! ! Be aware that C++ code compiled by GCC 3.2.x will not interoperate ! with code compiled by GCC 3.1.1 or earlier. ! ! Frontend Enhancements ! ! * C/C++/Objective-C ! + The method of constructing the list of directories to be ! searched for header files has been revised. If a directory ! named by a -I option is a standard system include directory, ! the option is ignored to ensure that the default search order ! for system directories and the special treatment of system ! header files are not defeated. ! + The C and Objective-C compilers no longer accept the "Naming ! Types" extension (typedef foo = bar); it was already ! unavailable in C++. Code which uses it will need to be ! changed to use the "typeof" extension instead: typedef ! typeof(bar) foo. (We have removed this extension without a ! period of deprecation because it has caused the compiler to ! crash since version 3.0 and no one noticed until very ! recently. Thus we conclude it is not in widespread use.) ! * C++ ! + There are now no known differences between the C++ ABI ! implemented in GCC and the multi-vendor standard. We believe ! that the ABI for the C++ standard library is now stable and ! will not change in future versions of the compiler. However, ! hard experience has taught us to be cautious; it is possible ! that more problems will be found. It is our intention to make ! changes to the ABI only if they are necessary for correct ! compilation of C++, as opposed to conformance to the ABI ! documents. ! + For details on how to build an ABI compliant compiler for ! GNU/Linux systems, check the [1]common C++ ABI page. ! ! New Targets and Target Specific Improvements ! * IA-32 ! + Fixed a number of bugs in SSE and MMX intrinsics. ! + Fixed common compiler crashes with SSE instruction set ! enabled (implied by -march=pentium3, pentium4, athlon-xp) ! + __m128 and __m128i is not 128bit aligned when used in ! structures. ! * x86-64 ! + A bug whereby the compiler could generate bad code for bzero ! has been fixed. ! + ABI fixes (implying ABI incompatibilities with previous ! version in some corner cases) ! + Fixed prefetch code generation ! Caveats * The C++ compiler does not correctly zero-initialize pointers-to-data members. You must explicitly initialize them. For --- 74,111 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [19]Valid XHTML 1.0 References 1. http://www.gnu.org/ ! 2. http://gcc.gnu.org/gcc-3.2/changes.html ! 3. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.2 ! 4. http://gcc.gnu.org/gcc-3.2/changes.html#3.2.1 ! 5. http://gcc.gnu.org/gcc-3.2/changes.html#3.2 ! 6. http://gcc.gnu.org/gcc-3.2/buildstat.html ! 7. http://gcc.gnu.org/onlinedocs/gcc/Contributors.html ! 8. http://gcc.gnu.org/index.html ! 9. mailto:gcc@gcc.gnu.org ! 10. http://gcc.gnu.org/mirrors.html ! 11. http://www.gnu.org/order/ftp.html ! 12. http://gcc.gnu.org/cvs.html ! 13. mailto:gnu@gnu.org ! 14. http://www.gnu.org/home.html#ContactInfo ! 15. http://gcc.gnu.org/about.html ! 16. mailto:gcc@gnu.org ! 17. mailto:gcc@gcc.gnu.org ! 18. mailto:gnu@gnu.org ! 19. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.2/changes.html ! GCC 3.2 Release Series ! Changes, New Features, and Fixes ! Caveats and New Features ! Caveats * The C++ compiler does not correctly zero-initialize pointers-to-data members. You must explicitly initialize them. For *************** Caveats *** 145,163 **** fixed in GCC 3.2 without inducing unacceptable risks. It will be fixed in GCC 3.3. * This GCC release is based on the GCC 3.1 sourcebase, and thus has ! all the [2]changes in the GCC 3.1 series. In addition, GCC 3.2 has a number of C++ ABI fixes which make its C++ compiler generate binary code which is incompatible with the C++ compilers found in earlier GCC releases, including GCC 3.1 and GCC 3.1.1. ! GCC 3.2.2 ! Miscellaneous Improvements ! * As of 3.2.2, the Makefile suite supports redirection of make ! install by means of the DESTDIR variable. ! GCC 3.2.1 3.2.1 adds a new warning, -Wabi. This option warns when GNU C++ generates code that is known not to be binary-compatible with the --- 114,321 ---- fixed in GCC 3.2 without inducing unacceptable risks. It will be fixed in GCC 3.3. * This GCC release is based on the GCC 3.1 sourcebase, and thus has ! all the [1]changes in the GCC 3.1 series. In addition, GCC 3.2 has a number of C++ ABI fixes which make its C++ compiler generate binary code which is incompatible with the C++ compilers found in earlier GCC releases, including GCC 3.1 and GCC 3.1.1. ! Frontend Enhancements ! C/C++/Objective-C ! * The method of constructing the list of directories to be searched ! for header files has been revised. If a directory named by a -I ! option is a standard system include directory, the option is ! ignored to ensure that the default search order for system ! directories and the special treatment of system header files are ! not defeated. ! * The C and Objective-C compilers no longer accept the "Naming ! Types" extension (typedef foo = bar); it was already unavailable ! in C++. Code which uses it will need to be changed to use the ! "typeof" extension instead: typedef typeof(bar) foo. (We have ! removed this extension without a period of deprecation because it ! has caused the compiler to crash since version 3.0 and no one ! noticed until very recently. Thus we conclude it is not in ! widespread use.) ! C++ ! ! * There are now no known differences between the C++ ABI implemented ! in GCC and the multi-vendor standard. We believe that the ABI for ! the C++ standard library is now stable and will not change in ! future versions of the compiler. However, hard experience has ! taught us to be cautious; it is possible that more problems will ! be found. It is our intention to make changes to the ABI only if ! they are necessary for correct compilation of C++, as opposed to ! conformance to the ABI documents. ! * For details on how to build an ABI compliant compiler for ! GNU/Linux systems, check the [2]common C++ ABI page. ! ! New Targets and Target Specific Improvements ! ! IA-32 ! ! * Fixed a number of bugs in SSE and MMX intrinsics. ! * Fixed common compiler crashes with SSE instruction set enabled ! (implied by -march=pentium3, pentium4, athlon-xp) ! * __m128 and __m128i is not 128bit aligned when used in structures. ! ! x86-64 ! ! * A bug whereby the compiler could generate bad code for bzero has ! been fixed. ! * ABI fixes (implying ABI incompatibilities with previous version in ! some corner cases) ! * Fixed prefetch code generation ! _________________________________________________________________ ! ! GCC 3.2.2 ! ! Beginning with 3.2.2, GCC's Makefile suite supports redirection of ! make install by means of the DESTDIR variable. Parts of the GCC tree ! have featured that support long before, but now it is available even ! from the top level. ! ! Other than that, GCC 3.2.2 is a bug fix release only; there are no new ! features that were not present in GCC 3.2.1. ! ! Bug Fixes ! ! On the following i386-based systems GCC 3.2.1 broke the C ABI wrt. ! functions returning structures: Cygwin, FreeBSD (GCC 3.2.1 as shipped ! with FreeBSD 5.0 does not have this problem), Interix, a.out-based ! Linux and NetBSD, OpenBSD, and Darwin. GCC 3.2.2 reverts this ABI ! change, and thus restores ABI-compatibility with previous releases ! (except GCC 3.2.1) on these platforms. ! ! This section lists the problem reports (PRs) from GCC's bug tracking ! system (GNATS) that are known to be fixed in the 3.2.2 release. This ! list might not be complete (that is, it is possible that some PRs that ! have been fixed are not listed here). ! ! The sorting is slightly different from the GNATS categories, and some ! of the titles have been changed to make them more clear. ! ! Internal Compiler Errors (multi-platform) ! ! * [3]5919: (c++) ICE when passing variable array to template ! function ! * [4]7129: (c++) ICE with min/max assignment operators (?=) ! * [5]7507: ICE with -O2 when address of called function is a ! complicated expression ! * [6]7622: ICE with nested inline functions if function's address is ! taken ! * [7]7681: (fortran) ICE in compensate_edge, in reg-stack.c (also PR ! [8]9258) ! * [9]8031: (c++) ICE in code comparing typeids and casting from ! virtual base ! * [10]8275: ICE in simplify_subreg ! * [11]8332: (c++) builtin strlen/template interaction causes ICE ! * [12]8372: (c++) ICE on explicit call of destructor ! * [13]8439: (c, not c++) empty struct causes ICE ! * [14]8442: (c++) ICE with nested template classes ! * [15]8518: ICE when compiling mplayer ("extern inline" issue) ! * [16]8615: (c++) ICE with out-of-range character constant template ! argument ! * [17]8663: (c++) ICE in cp_expr_size, at cp-lang.c:307 ! * [18]8799: (c++) ICE: error reporting routines re-entered ! * [19]9328: (c++) ICE with typeof(X) for overloaded X ! * [20]9465: (preprocessor) cpp -traditional ICE on null bytes ! ! C++ (compiler and library) bugs ! ! * [21]47: scoping in nested classes is broken ! * [22]6745: problems with iostream rdbuf() member function ! * [23]8214: conversion from const char* const to char* sometimes ! accepted illegally ! * [24]8493: builtin strlen and overload resolution (same bug as ! [25]8332) ! * [26]8503: strange behaviour of function types ! * [27]8727: compiler confused by inheritance from an anonymous ! struct ! * [28]7445: poor performance of std::locale::classic() in ! multi-threaded applications ! * [29]8230: mishandling of overflow in vector::resize ! * [30]8399: sync_with_stdio(false) breaks unformatted input ! * [31]8662: illegal access of private member of unnamed class is ! accepted ! * [32]8707: "make distclean" fails in libstdc++-v3 directory ! * [33]8708: __USE_MALLOC doesn't work ! * [34]8790: Use of non-thread-safe strtok in src/localename.cc ! * [35]8887: Bug in date formats with --enable-clocale=generic ! * [36]9076: Call Frame Instructions are not handled correctly during ! unwind operation ! * [37]9151: std::setprecision limited to 16 digits when outputting a ! double to a stream ! * [38]9168: codecvt overwrites output buffers ! * [39]9269: libstdc++ headers: explicit specialization of function ! must precede its first use ! * [40]9322: return value of basic_streambuf<>::getloc affected by ! locale::global ! * [41]9433: segfault in runtime support for dynamic_cast ! ! C and optimizer bugs ! ! * [42]8032: GCC incorrectly initializes static structs that have ! flexible arrays ! * [43]8639: simple arithmetic expression broken ! * [44]8794: optimization improperly eliminates certain expressions ! * [45]8832: traditional "asm volatile" code is illegally optimized ! * [46]8988: loop optimizer bug: with -O2, code is generated that ! segfaults (found on i386, bug present for all platforms) ! * [47]9492: structure copy clobbers subsequent stores to structure ! ! Objective-C bugs ! ! * [48]9267: Objective-C parser won't build with newer bison versions ! (e.g. 1.875) ! ! Ada bugs ! ! * [49]8344: Ada build problem due to conflict between gcc/final.o, ! gcc/ada/final.o ! ! Preprocessor bugs ! ! * [50]8524: _Pragma within macros is improperly expanded ! * [51]8880: __WCHAR_TYPE__ macro incorrectly set to "long int" with ! -fshort-wchar ! ! ARM-specific ! ! * [52]9090: arm ICE with >= -O2; regression from gcc-2.95 ! ! x86-specific (Intel/AMD) ! ! * [53]8588: ICE in extract_insn, at recog.c:NNNN (shift instruction) ! * [54]8599: loop unroll bug with -march=k6-3 ! * [55]9506: ABI breakage in structure return (affects BSD and ! Cygwin, but not GNU/Linux) ! ! FreeBSD 5.0 specific ! ! * [56]9484: GCC 3.2.1 Bootstrap failure on FreeBSD 5.0 ! ! RTEMS-specific ! ! * [57]9292: hppa1.1-rtems configurery problems ! * [58]9293: [m68k-elf/rtems] config/m68k/t-crtstuff bug ! * [59]9295: [mips-rtems] config/mips/rtems.h init/fini issue ! * [60]9296: gthr-rtems regression ! * [61]9316: powerpc-rtems: extending multilibs ! ! HP-PA specific ! ! * [62]9493: ICE with -O2 when building a simple function ! ! Documentation ! ! * [63]7341: hyperlink to gcov in GCC documentation doesn't work ! * [64]8947: Please add a warning about "-malign-double" in docs ! * [65]7448, [66]8882: typo cleanups ! _________________________________________________________________ ! ! GCC 3.2.1 3.2.1 adds a new warning, -Wabi. This option warns when GNU C++ generates code that is known not to be binary-compatible with the *************** Miscellaneous Improvements *** 173,347 **** the new warning there are no new features that were not present in GCC 3.2. ! In addition, the previous fix for [3]PR 7445 (poor performance of std::locale::classic() in multi-threaded applications) was reverted ("unfixed"), because the "fix" was not thread-safe. ! Bug Fixes ! This document lists the problem reports (PRs) from GCC's bug tracking ! system ([4]GNATS) that are known to be fixed in the 3.2.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). As you can see, the number of bug fixes is quite large, so it is strongly recommended that users of earlier gcc 3.x releases upgrade to GCC 3.2.1. - * Internal Compiler Errors (multi-platform) - + [5]2521: (c++) ICE in build_ptrmemfunc, in cp/typeck.c - + [6]5661: (c++) ICE instantiating template on array of unknown - size (bad code) - + [7]6419: (c++) ICE in make_decl_rtl for "longest" attribute - on 64-bit platforms - + [8]6994: (c++) ICE in find_function_data - + [9]7150: preprocessor: GCC -dM -E gives an ICE - + [10]7160: ICE when optimizing branches without a return value - + [11]7228: (c++) ICE when using member template and template - function - + [12]7266: (c++) ICE with -pedantic on missing typename - + [13]7353: ICE from use of "Naming Types" extension, see above - + [14]7411: ICE in instantiate_virtual_regs_1, in function.c - + [15]7478: (c++) ICE on static_cast inside template - + [16]7526: preprocessor core dump when _Pragma implies #pragma - dependency - + [17]7721: (c++) ICE on simple (but incorrect) template - ([18]7803 is a duplicate) - + [19]7754: (c++) ICE on union with template parameter - + [20]7788: (c++) redeclaring a definition as an incomplete - class causes ICE - + [21]8031: (c++) ICE in comptypes, in cp/typeck.c - + [22]8055: preprocessor dies with SIG11 when building FreeBSD - kernel - + [23]8067: (c++) ICE due to mishandling of __FUNCTION__ and - related variables - + [24]8134: (c++) ICE in force_store_init_value on legal code - + [25]8149: (c++) ICE on incomplete type - + [26]8160: (c++) ICE in build_modify_expr, in cp/typeck.c: - array initialization - * C++ (compiler and library) bugs - + [27]5607: No pointer adjustment in covariant return types - + [28]6579: Infinite loop with statement expressions in member - initialization - + [29]6803: Default copy constructor bug in GCC 3.1 - + [30]7176: g++ confused by friend and static member with same - name - + [31]7188: Segfault with template class and recursive - (incorrect) initializer list - + [32]7306: Regression: GCC 3.x fails to compile code with - virtual inheritance if a method has a variable number of - arguments - + [33]7461: ctype::classic_table() returns offset array - on Cygwin - + [34]7524: f(const float arg[3]) fails - + [35]7584: Erroneous ambiguous base error on using declaration - + [36]7676: Member template overloading problem - + [37]7679: infinite loop when a right parenthesis is missing - + [38]7811: default locale not taken from environment - + [39]7961: compare( char *) implemented incorrectly in - basic_string<> - + [40]8071: basic_ostream::operator<<(streambuf*) loops forever - if streambuf::underflow() leaves gptr() NULL (dups: [41]8127, - [42]6745) - + [43]8096: deque::at() throws std::range_error instead of - std::out_of_range - + [44]8127: cout << cin.rdbuf() infinite loop - + [45]8218: Excessively large memory consumed for classes with - large array members - + [46]8287: GCC 3.2: Destructor called for non-constructed - local object - + [47]8347: empty vector range used in string construction - causes core dump - + [48]8348: fail() flag is set in istringstream when eof() flag - is set - + [49]8391: regression: infinite loop in - cp/decl2.c(finish_file) - * C and optimizer bugs - + [50]6627: -fno-align-functions doesn't seem to disable - function alignment - + [51]6631: life_analysis misoptimizes code to initialize - fields of a structure - + [52]7102: unsigned char division results in floating - exception - + [53]7120: Run once loop should *always* be unrolled - (pessimization) - + [54]7209: Bug involving array referencing and ?: operator - + [55]7515: invalid inlining of global function with -O3 - + [56]7814: incorrect scheduling for glibc-2.2.92 strcpy test - + [57]8467: bug in sibling call optimization - * Preprocessor bugs - + [58]4890: incorrect line markers from the traditional - preprocessor - + [59]7357: -M option omits system headers files (making it the - same as -MM) - + [60]7358: Changes to Sun's make Dependencies - + [61]7602: C++ header files found in CPLUS_INCLUDE_PATH - treated as C headers - + [62]7862: Interrupting GCC -MD removes .d file but not .o - + [63]8190: Failed compilation deletes -MD dependency file - + [64]8524: _Pragma within macro is improperly expanded - * x86 specific (Intel/AMD) - + [65]5351: (i686-only) function pass-by-value structure copy - corrupts stack ([66]7591 is a duplicate) - + [67]6845, [68]7034, [69]7124, [70]7174: ICE's with - -march=pentium3/pentium2/athlon (these are all the same - underlying bug, in MMX register use) - + [71]7134, [72]7375, [73]7390: ICE with -march=athlon (maybe - same as above?) - + [74]6890: xmmintrin.h, _MM_TRANSPOSE4_PS is broken - + [75]6981: wrong code in 64-bit manipulation on x86 - + [76]7242: GCC -mcpu=pentium[23] doesn't define - __tune_pentiumpro__ macro - + [77]7396: ix86: cmpgt_ss, cmpge_ss, cmpngt_ss, and cmpnge_ss - SSE intrinsics are broken - + [78]7630: GCC 3.2 breaks on Mozilla 1.0's JS sources with - -march=pentium4 - + [79]7693: Typo in i386 mmintrin.h header - + [80]7723: ICE - Pentium3 sse - GCC 3.2 - + [81]7951: ICE on -march=pentium4 -O2 -mfpmath=sse - + [82]8146: (i686 only) gcc 3.2 miscompiles gcc 2.95.3 - * PowerPC specific - + [83]5967: GCC bug when profiling nested functions on powerpc - + [84]6984: wrong code generated with -O2, -O3, -Os for - do-while loop on PowerPC - + [85]7114: PowerPC: ICE building strcoll.op from glibc-2.2.5 - + [86]7130: miscompiled code for GCC-3.1 in powerpc linux with - -funroll-all-loops - + [87]7133: PowerPC ICE: unrecognizable insn - + [88]7380: ICE in extract_insn, at recog.c:2148 - + [89]8252: ICE on Altivec code with optimization turned on - + [90]8451: Altivec ICE in GCC 3.2 - * HP/PA specific - + [91]7250: __ashrdi3 returns wrong value on 32 bit hppa - * SPARC specific - + [92]6668: when using --disable-multilib, libgcc_s.so is - installed in the wrong place on sparc-solaris - + [93]7151: ICE when compiling for UltraSPARC - + [94]7335: SPARC: ICE in verify_wide_reg (flow.c:557) with - long double and -O1 - + [95]7842: [REGRESSION] SPARC code gen bug - * ARM specific - + [96]7856: [arm] invalid offset in constant pool reference - + [97]7967: optimization produces wrong code (ARM) - * Alpha specific - + [98]7374: __builtin_fabsl broken on alpha - * IBM s390 specific - + [99]7370: ICE in fixup_var_refs_1 on s390x - + [100]7409: loop optimization bug on s390x-linux-gnu - + [101]8232: s390x: ICE when using bcmp with int length - argument - * SCO specific - + [102]7623: SCO OpenServer build fails with machmode.def: - undefined symbol: BITS_PER_UNIT - * m68k/Coldfire specific - + [103]8314: crtbegin, crtend need to be multilib'ed for this - platform - * Documentation - + [104]761: Document some undocumented options - + [105]5610: Fix documentation about invoking SSE instructions - (-mfpmath=sse) - + [106]7484: List -Wmissing-declarations as C-only option - + [107]7531: -mcmodel not documented for x86-64 - + [108]8120: Update documentation of bad use of ## ! GCC 3.2 3.2 is a small bug fix release, but there is a change to the application binary interface (ABI), hence the change to the second --- 331,529 ---- the new warning there are no new features that were not present in GCC 3.2. ! In addition, the previous fix for [67]PR 7445 (poor performance of std::locale::classic() in multi-threaded applications) was reverted ("unfixed"), because the "fix" was not thread-safe. ! Bug Fixes ! This section lists the problem reports (PRs) from GCC's bug tracking ! system ([68]GNATS) that are known to be fixed in the 3.2.1 release. This list might not be complete (that is, it is possible that some PRs that have been fixed are not listed here). As you can see, the number of bug fixes is quite large, so it is strongly recommended that users of earlier gcc 3.x releases upgrade to GCC 3.2.1. ! Internal Compiler Errors (multi-platform) ! ! * [69]2521: (c++) ICE in build_ptrmemfunc, in cp/typeck.c ! * [70]5661: (c++) ICE instantiating template on array of unknown ! size (bad code) ! * [71]6419: (c++) ICE in make_decl_rtl for "longest" attribute on ! 64-bit platforms ! * [72]6994: (c++) ICE in find_function_data ! * [73]7150: preprocessor: GCC -dM -E gives an ICE ! * [74]7160: ICE when optimizing branches without a return value ! * [75]7228: (c++) ICE when using member template and template ! function ! * [76]7266: (c++) ICE with -pedantic on missing typename ! * [77]7353: ICE from use of "Naming Types" extension, see above ! * [78]7411: ICE in instantiate_virtual_regs_1, in function.c ! * [79]7478: (c++) ICE on static_cast inside template ! * [80]7526: preprocessor core dump when _Pragma implies #pragma ! dependency ! * [81]7721: (c++) ICE on simple (but incorrect) template ([82]7803 ! is a duplicate) ! * [83]7754: (c++) ICE on union with template parameter ! * [84]7788: (c++) redeclaring a definition as an incomplete class ! causes ICE ! * [85]8031: (c++) ICE in comptypes, in cp/typeck.c ! * [86]8055: preprocessor dies with SIG11 when building FreeBSD ! kernel ! * [87]8067: (c++) ICE due to mishandling of __FUNCTION__ and related ! variables ! * [88]8134: (c++) ICE in force_store_init_value on legal code ! * [89]8149: (c++) ICE on incomplete type ! * [90]8160: (c++) ICE in build_modify_expr, in cp/typeck.c: array ! initialization ! ! C++ (compiler and library) bugs ! ! * [91]5607: No pointer adjustment in covariant return types ! * [92]6579: Infinite loop with statement expressions in member ! initialization ! * [93]6803: Default copy constructor bug in GCC 3.1 ! * [94]7176: g++ confused by friend and static member with same name ! * [95]7188: Segfault with template class and recursive (incorrect) ! initializer list ! * [96]7306: Regression: GCC 3.x fails to compile code with virtual ! inheritance if a method has a variable number of arguments ! * [97]7461: ctype::classic_table() returns offset array on ! Cygwin ! * [98]7524: f(const float arg[3]) fails ! * [99]7584: Erroneous ambiguous base error on using declaration ! * [100]7676: Member template overloading problem ! * [101]7679: infinite loop when a right parenthesis is missing ! * [102]7811: default locale not taken from environment ! * [103]7961: compare( char *) implemented incorrectly in ! basic_string<> ! * [104]8071: basic_ostream::operator<<(streambuf*) loops forever if ! streambuf::underflow() leaves gptr() NULL (dups: [105]8127, ! [106]6745) ! * [107]8096: deque::at() throws std::range_error instead of ! std::out_of_range ! * [108]8127: cout << cin.rdbuf() infinite loop ! * [109]8218: Excessively large memory consumed for classes with ! large array members ! * [110]8287: GCC 3.2: Destructor called for non-constructed local ! object ! * [111]8347: empty vector range used in string construction causes ! core dump ! * [112]8348: fail() flag is set in istringstream when eof() flag is ! set ! * [113]8391: regression: infinite loop in cp/decl2.c(finish_file) ! ! C and optimizer bugs ! ! * [114]6627: -fno-align-functions doesn't seem to disable function ! alignment ! * [115]6631: life_analysis misoptimizes code to initialize fields of ! a structure ! * [116]7102: unsigned char division results in floating exception ! * [117]7120: Run once loop should *always* be unrolled ! (pessimization) ! * [118]7209: Bug involving array referencing and ?: operator ! * [119]7515: invalid inlining of global function with -O3 ! * [120]7814: incorrect scheduling for glibc-2.2.92 strcpy test ! * [121]8467: bug in sibling call optimization ! ! Preprocessor bugs ! ! * [122]4890: incorrect line markers from the traditional ! preprocessor ! * [123]7357: -M option omits system headers files (making it the ! same as -MM) ! * [124]7358: Changes to Sun's make Dependencies ! * [125]7602: C++ header files found in CPLUS_INCLUDE_PATH treated as ! C headers ! * [126]7862: Interrupting GCC -MD removes .d file but not .o ! * [127]8190: Failed compilation deletes -MD dependency file ! * [128]8524: _Pragma within macro is improperly expanded ! ! x86 specific (Intel/AMD) ! ! * [129]5351: (i686-only) function pass-by-value structure copy ! corrupts stack ([130]7591 is a duplicate) ! * [131]6845, [132]7034, [133]7124, [134]7174: ICE's with ! -march=pentium3/pentium2/athlon (these are all the same underlying ! bug, in MMX register use) ! * [135]7134, [136]7375, [137]7390: ICE with -march=athlon (maybe ! same as above?) ! * [138]6890: xmmintrin.h, _MM_TRANSPOSE4_PS is broken ! * [139]6981: wrong code in 64-bit manipulation on x86 ! * [140]7242: GCC -mcpu=pentium[23] doesn't define ! __tune_pentiumpro__ macro ! * [141]7396: ix86: cmpgt_ss, cmpge_ss, cmpngt_ss, and cmpnge_ss SSE ! intrinsics are broken ! * [142]7630: GCC 3.2 breaks on Mozilla 1.0's JS sources with ! -march=pentium4 ! * [143]7693: Typo in i386 mmintrin.h header ! * [144]7723: ICE - Pentium3 sse - GCC 3.2 ! * [145]7951: ICE on -march=pentium4 -O2 -mfpmath=sse ! * [146]8146: (i686 only) gcc 3.2 miscompiles gcc 2.95.3 ! ! PowerPC specific ! ! * [147]5967: GCC bug when profiling nested functions on powerpc ! * [148]6984: wrong code generated with -O2, -O3, -Os for do-while ! loop on PowerPC ! * [149]7114: PowerPC: ICE building strcoll.op from glibc-2.2.5 ! * [150]7130: miscompiled code for GCC-3.1 in powerpc linux with ! -funroll-all-loops ! * [151]7133: PowerPC ICE: unrecognizable insn ! * [152]7380: ICE in extract_insn, at recog.c:2148 ! * [153]8252: ICE on Altivec code with optimization turned on ! * [154]8451: Altivec ICE in GCC 3.2 ! ! HP/PA specific ! ! * [155]7250: __ashrdi3 returns wrong value on 32 bit hppa ! ! SPARC specific ! ! * [156]6668: when using --disable-multilib, libgcc_s.so is installed ! in the wrong place on sparc-solaris ! * [157]7151: ICE when compiling for UltraSPARC ! * [158]7335: SPARC: ICE in verify_wide_reg (flow.c:557) with long ! double and -O1 ! * [159]7842: [REGRESSION] SPARC code gen bug ! ! ARM specific ! ! * [160]7856: [arm] invalid offset in constant pool reference ! * [161]7967: optimization produces wrong code (ARM) ! ! Alpha specific ! ! * [162]7374: __builtin_fabsl broken on alpha ! ! IBM s390 specific ! ! * [163]7370: ICE in fixup_var_refs_1 on s390x ! * [164]7409: loop optimization bug on s390x-linux-gnu ! * [165]8232: s390x: ICE when using bcmp with int length argument ! ! SCO specific ! ! * [166]7623: SCO OpenServer build fails with machmode.def: undefined ! symbol: BITS_PER_UNIT ! ! m68k/Coldfire specific ! ! * [167]8314: crtbegin, crtend need to be multilib'ed for this ! platform ! ! Documentation ! ! * [168]761: Document some undocumented options ! * [169]5610: Fix documentation about invoking SSE instructions ! (-mfpmath=sse) ! * [170]7484: List -Wmissing-declarations as C-only option ! * [171]7531: -mcmodel not documented for x86-64 ! * [172]8120: Update documentation of bad use of ## ! _________________________________________________________________ ! ! GCC 3.2 3.2 is a small bug fix release, but there is a change to the application binary interface (ABI), hence the change to the second *************** Bug Fixes *** 351,389 **** in the C++ ABI, with the intention of providing a stable interface going forward. Accordingly, 3.2 is only a small change to 3.1.1. ! Bug Fixes ! * C++ ! + [109]7320: g++ 3.2 relocation problem ! + [110]7470: vtable: virtual function pointers not in ! declaration order ! * libstdc++ ! + [111]6410: Trouble with non-ASCII monetary symbols and ! wchar_t ! + [112]6503, [113]6642, [114]7186: Problems with comparing or ! subtracting various types of const and non-const iterators ! + [115]7216: ambiguity with basic_iostream::traits_type ! + [116]7220: problem with basic_istream::ignore(0,delimiter) ! + [117]7222: locale::operator==() doesn't work on ! std::locale("") ! + [118]7286: placement operator delete issue ! + [119]7442: cxxabi.h does not match the C++ ABI ! + [120]7445: poor performance of std::locale::classic() in ! multi-threaded applications ! * x86-64 specific ! + [121]7291: off-by-one in generated inline bzero code for ! x86-64 _________________________________________________________________ ! Please send FSF & GNU inquiries & questions to [122]gnu@gnu.org. There ! are also [123]other ways to contact the FSF. ! These pages are maintained by [124]The GCC team. Please send comments on these web pages and GCC to our public ! mailing list at [125]gcc@gnu.org or [126]gcc@gcc.gnu.org, send other ! questions to [127]gnu@gnu.org. Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. --- 533,573 ---- in the C++ ABI, with the intention of providing a stable interface going forward. Accordingly, 3.2 is only a small change to 3.1.1. ! Bug Fixes ! C++ ! ! * [173]7320: g++ 3.2 relocation problem ! * [174]7470: vtable: virtual function pointers not in declaration ! order ! ! libstdc++ ! ! * [175]6410: Trouble with non-ASCII monetary symbols and wchar_t ! * [176]6503, [177]6642, [178]7186: Problems with comparing or ! subtracting various types of const and non-const iterators ! * [179]7216: ambiguity with basic_iostream::traits_type ! * [180]7220: problem with basic_istream::ignore(0,delimiter) ! * [181]7222: locale::operator==() doesn't work on std::locale("") ! * [182]7286: placement operator delete issue ! * [183]7442: cxxabi.h does not match the C++ ABI ! * [184]7445: poor performance of std::locale::classic() in ! multi-threaded applications ! ! x86-64 specific ! ! * [185]7291: off-by-one in generated inline bzero code for x86-64 _________________________________________________________________ ! Please send FSF & GNU inquiries & questions to [186]gnu@gnu.org. There ! are also [187]other ways to contact the FSF. ! These pages are maintained by [188]The GCC team. Please send comments on these web pages and GCC to our public ! mailing list at [189]gcc@gnu.org or [190]gcc@gcc.gnu.org, send other ! questions to [191]gnu@gnu.org. Copyright (C) Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. *************** Bug Fixes *** 391,528 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-01-28 [128]Valid XHTML 1.0 References ! 1. http://gcc.gnu.org/gcc-3.2/c++-abi.html ! 2. http://gcc.gnu.org/gcc-3.1/changes.html ! 3. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7445 ! 4. http://gcc.gnu.org/cgi-bin/gnatsweb.pl ! 5. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=2521 ! 6. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5661 ! 7. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6419 ! 8. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6994 ! 9. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7150 ! 10. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7160 ! 11. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7228 ! 12. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7266 ! 13. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7353 ! 14. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7411 ! 15. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7478 ! 16. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7526 ! 17. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7721 ! 18. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7803 ! 19. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7754 ! 20. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7788 ! 21. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8031 ! 22. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8055 ! 23. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8067 ! 24. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8134 ! 25. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8149 ! 26. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8160 ! 27. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5607 ! 28. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6579 ! 29. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6803 ! 30. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7176 ! 31. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7188 ! 32. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7306 ! 33. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7461 ! 34. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7524 ! 35. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7584 ! 36. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7676 ! 37. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7679 ! 38. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7811 ! 39. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7961 ! 40. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8071 ! 41. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8127 ! 42. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6745 ! 43. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8096 ! 44. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8127 ! 45. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8218 ! 46. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8287 ! 47. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8347 ! 48. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8348 ! 49. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8391 ! 50. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6627 ! 51. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6631 ! 52. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7102 ! 53. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7120 ! 54. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7209 ! 55. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7515 ! 56. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7814 ! 57. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8467 ! 58. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4890 ! 59. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7357 ! 60. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7358 ! 61. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7602 ! 62. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7862 ! 63. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8190 ! 64. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8524 ! 65. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5351 ! 66. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7591 ! 67. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6845 ! 68. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7034 ! 69. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7124 ! 70. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7174 ! 71. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7134 ! 72. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7375 ! 73. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7390 ! 74. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6890 ! 75. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6981 ! 76. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7242 ! 77. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7396 ! 78. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7630 ! 79. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7693 ! 80. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7723 ! 81. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7951 ! 82. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8146 ! 83. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5967 ! 84. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6984 ! 85. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7114 ! 86. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7130 ! 87. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7133 ! 88. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7380 ! 89. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8252 ! 90. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8451 ! 91. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7250 ! 92. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6668 ! 93. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7151 ! 94. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7335 ! 95. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7842 ! 96. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7856 ! 97. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7967 ! 98. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7374 ! 99. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7370 ! 100. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7409 ! 101. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8232 ! 102. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7623 ! 103. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8314 ! 104. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=761 ! 105. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5610 ! 106. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7484 ! 107. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7531 ! 108. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8120 ! 109. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7320 ! 110. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7470 ! 111. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6410 ! 112. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6503 ! 113. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6642 ! 114. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7186 ! 115. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7216 ! 116. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7220 ! 117. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7222 ! 118. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7286 ! 119. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7442 ! 120. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7445 ! 121. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7291 ! 122. mailto:gnu@gnu.org ! 123. http://www.gnu.org/home.html#ContactInfo ! 124. http://gcc.gnu.org/about.html ! 125. mailto:gcc@gnu.org ! 126. mailto:gcc@gcc.gnu.org ! 127. mailto:gnu@gnu.org ! 128. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.1/index.html --- 575,776 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-03-21 [192]Valid XHTML 1.0 References ! 1. http://gcc.gnu.org/gcc-3.1/changes.html ! 2. http://gcc.gnu.org/gcc-3.2/c++-abi.html ! 3. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5919 ! 4. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7129 ! 5. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7507 ! 6. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7622 ! 7. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7681 ! 8. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9528 ! 9. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8031 ! 10. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8275 ! 11. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8332 ! 12. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8372 ! 13. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8439 ! 14. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8442 ! 15. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8518 ! 16. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8615 ! 17. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8663 ! 18. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8799 ! 19. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9328 ! 20. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9465 ! 21. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=47 ! 22. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6745 ! 23. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8214 ! 24. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8493 ! 25. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8332 ! 26. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8503 ! 27. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8727 ! 28. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7445 ! 29. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8230 ! 30. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8399 ! 31. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8662 ! 32. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8707 ! 33. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8708 ! 34. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8790 ! 35. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8887 ! 36. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9076 ! 37. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9151 ! 38. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9168 ! 39. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9269 ! 40. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9322 ! 41. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9433 ! 42. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8032 ! 43. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8639 ! 44. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8794 ! 45. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8832 ! 46. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8988 ! 47. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9492 ! 48. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9267 ! 49. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8344 ! 50. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8524 ! 51. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8880 ! 52. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9090 ! 53. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8588 ! 54. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8599 ! 55. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9506 ! 56. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9484 ! 57. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9292 ! 58. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9293 ! 59. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9295 ! 60. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9296 ! 61. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9316 ! 62. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=9493 ! 63. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7341 ! 64. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8947 ! 65. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7448 ! 66. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8882 ! 67. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7445 ! 68. http://gcc.gnu.org/cgi-bin/gnatsweb.pl ! 69. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=2521 ! 70. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5661 ! 71. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6419 ! 72. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6994 ! 73. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7150 ! 74. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7160 ! 75. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7228 ! 76. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7266 ! 77. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7353 ! 78. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7411 ! 79. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7478 ! 80. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7526 ! 81. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7721 ! 82. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7803 ! 83. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7754 ! 84. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7788 ! 85. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8031 ! 86. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8055 ! 87. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8067 ! 88. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8134 ! 89. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8149 ! 90. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8160 ! 91. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5607 ! 92. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6579 ! 93. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6803 ! 94. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7176 ! 95. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7188 ! 96. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7306 ! 97. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7461 ! 98. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7524 ! 99. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7584 ! 100. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7676 ! 101. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7679 ! 102. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7811 ! 103. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7961 ! 104. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8071 ! 105. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8127 ! 106. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6745 ! 107. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8096 ! 108. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8127 ! 109. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8218 ! 110. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8287 ! 111. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8347 ! 112. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8348 ! 113. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8391 ! 114. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6627 ! 115. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6631 ! 116. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7102 ! 117. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7120 ! 118. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7209 ! 119. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7515 ! 120. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7814 ! 121. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8467 ! 122. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4890 ! 123. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7357 ! 124. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7358 ! 125. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7602 ! 126. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7862 ! 127. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8190 ! 128. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8524 ! 129. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5351 ! 130. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7591 ! 131. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6845 ! 132. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7034 ! 133. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7124 ! 134. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7174 ! 135. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7134 ! 136. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7375 ! 137. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7390 ! 138. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6890 ! 139. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6981 ! 140. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7242 ! 141. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7396 ! 142. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7630 ! 143. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7693 ! 144. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7723 ! 145. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7951 ! 146. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8146 ! 147. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5967 ! 148. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6984 ! 149. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7114 ! 150. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7130 ! 151. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7133 ! 152. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7380 ! 153. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8252 ! 154. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8451 ! 155. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7250 ! 156. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6668 ! 157. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7151 ! 158. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7335 ! 159. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7842 ! 160. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7856 ! 161. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7967 ! 162. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7374 ! 163. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7370 ! 164. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7409 ! 165. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8232 ! 166. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7623 ! 167. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8314 ! 168. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=761 ! 169. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5610 ! 170. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7484 ! 171. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7531 ! 172. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=8120 ! 173. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7320 ! 174. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7470 ! 175. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6410 ! 176. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6503 ! 177. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=6642 ! 178. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7186 ! 179. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7216 ! 180. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7220 ! 181. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7222 ! 182. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7286 ! 183. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7442 ! 184. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7445 ! 185. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=7291 ! 186. mailto:gnu@gnu.org ! 187. http://www.gnu.org/home.html#ContactInfo ! 188. http://gcc.gnu.org/about.html ! 189. mailto:gcc@gnu.org ! 190. mailto:gcc@gcc.gnu.org ! 191. mailto:gnu@gnu.org ! 192. http://validator.w3.org/check/referer ====================================================================== http://gcc.gnu.org/gcc-3.1/index.html *************** http://gcc.gnu.org/gcc-3.1/index.html *** 576,582 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [17]Valid XHTML 1.0 References --- 824,830 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [17]Valid XHTML 1.0 References *************** References *** 600,606 **** ====================================================================== http://gcc.gnu.org/gcc-3.1/changes.html ! GCC 3.1 Release Series -- Changes, New Features, and Fixes Additional changes in GCC 3.1.1 --- 848,855 ---- ====================================================================== http://gcc.gnu.org/gcc-3.1/changes.html ! GCC 3.1 Release Series ! Changes, New Features, and Fixes Additional changes in GCC 3.1.1 *************** Documentation improvements *** 939,945 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-01-28 [25]Valid XHTML 1.0 References --- 1188,1194 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-03-21 [25]Valid XHTML 1.0 References *************** Previous 3.0.x Releases *** 1028,1034 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [17]Valid XHTML 1.0 References --- 1277,1283 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [17]Valid XHTML 1.0 References *************** Other significant improvements *** 1229,1235 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-01-04 [20]Valid XHTML 1.0 References --- 1478,1484 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [20]Valid XHTML 1.0 References *************** http://gcc.gnu.org/gcc-3.0/caveats.html *** 1308,1314 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [10]Valid XHTML 1.0 References --- 1557,1563 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [10]Valid XHTML 1.0 References *************** http://gcc.gnu.org/gcc-2.95/index.html *** 1387,1393 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [19]Valid XHTML 1.0 References --- 1636,1642 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [19]Valid XHTML 1.0 References *************** Additional Changes in GCC 2.95.3 *** 1662,1668 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-12-30 [23]Valid XHTML 1.0 References --- 1911,1917 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [23]Valid XHTML 1.0 References *************** http://gcc.gnu.org/gcc-2.95/caveats.html *** 1751,1757 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-12-30 [8]Valid XHTML 1.0 References --- 2000,2006 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [8]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.1/index.html *** 1978,1984 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-01-04 [17]Valid XHTML 1.0 References --- 2227,2233 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [17]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.1/features.htm *** 2053,2067 **** + Alpha port has been tuned for the EV6 processor and has an optimized expansion of memcpy/bzero. The Alpha port now uses the Haifa scheduler. ! + RS6000/PowerPC: EGCS 1.1 includes support for the Power64 ! architecture and aix4.3 support. The RS6000/PowerPC port now ! uses the Haifa scheduler. + x86: Alignment of static store data and jump targets is per Intel recommendations now. Various improvements throughout ! the x86 port to improve performance on Pentium processors. ! Conditional move support has been fixed and enabled for PPro ! processors. The x86 port also better supports 64bit ! operations now. + MIPS has improved multiply/multiply-add support and now includes mips16 ISA support. + M68k has many micro-optimizations and Coldfire fixes. --- 2302,2319 ---- + Alpha port has been tuned for the EV6 processor and has an optimized expansion of memcpy/bzero. The Alpha port now uses the Haifa scheduler. ! + RS6000/PowerPC: support for the Power64 architecture and AIX ! 4.3. The RS6000/PowerPC port now uses the Haifa scheduler. + x86: Alignment of static store data and jump targets is per Intel recommendations now. Various improvements throughout ! the x86 port to improve performance on Pentium processors ! (including improved epilogue sequences for Pentium chips and ! backend improvements which should help register allocation on ! all x86 variants. Conditional move support has been fixed and ! enabled for PPro processors. The x86 port also better ! supports 64bit operations now. Unixware 7, a System V Release ! 5 target, is now supported and SCO OpenServer targets can ! support GAS. + MIPS has improved multiply/multiply-add support and now includes mips16 ISA support. + M68k has many micro-optimizations and Coldfire fixes. *************** http://gcc.gnu.org/egcs-1.1/features.htm *** 2085,2091 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [12]Valid XHTML 1.0 References --- 2337,2343 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-03-29 [12]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.1/caveats.html *** 2146,2152 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-12-30 [7]Valid XHTML 1.0 References --- 2398,2404 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [7]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/egcs-1.0.3.h *** 2250,2256 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [12]Valid XHTML 1.0 References --- 2502,2508 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [12]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/egcs-1.0.2.h *** 2390,2396 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-01-04 [12]Valid XHTML 1.0 References --- 2642,2648 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [12]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/egcs-1.0.1.h *** 2530,2536 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [12]Valid XHTML 1.0 References --- 2782,2788 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [12]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/egcs-1.0.htm *** 2627,2633 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [12]Valid XHTML 1.0 References --- 2879,2885 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [12]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/features.htm *** 2701,2707 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-11-11 [9]Valid XHTML 1.0 References --- 2953,2959 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [9]Valid XHTML 1.0 References *************** http://gcc.gnu.org/egcs-1.0/caveats.html *** 2761,2767 **** Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2002-12-30 [7]Valid XHTML 1.0 References --- 3013,3019 ---- Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. ! Last modified 2003-02-21 [7]Valid XHTML 1.0 References diff -Nrc3pad gcc-3.2.2/gcc/bb-reorder.c gcc-3.2.3/gcc/bb-reorder.c *** gcc-3.2.2/gcc/bb-reorder.c Mon Jul 15 16:19:38 2002 --- gcc-3.2.3/gcc/bb-reorder.c Thu Feb 20 20:10:57 2003 *************** make_reorder_chain_1 (bb, prev) *** 205,211 **** e_taken = e; } ! next = (taken ? e_taken : e_fall)->dest; } /* In the absence of a prediction, disturb things as little as possible --- 205,211 ---- e_taken = e; } ! next = ((taken && e_taken) ? e_taken : e_fall)->dest; } /* In the absence of a prediction, disturb things as little as possible diff -Nrc3pad gcc-3.2.2/gcc/builtins.c gcc-3.2.3/gcc/builtins.c *** gcc-3.2.2/gcc/builtins.c Sun Dec 1 18:19:08 2002 --- gcc-3.2.3/gcc/builtins.c Sun Mar 30 04:42:16 2003 *************** expand_builtin_fputs (arglist, ignore, u *** 3385,3392 **** /* FALLTHROUGH */ case 1: /* length is greater than 1, call fwrite. */ { ! tree string_arg = TREE_VALUE (arglist); /* New argument list transforming fputs(string, stream) to fwrite(string, 1, len, stream). */ arglist = build_tree_list (NULL_TREE, TREE_VALUE (TREE_CHAIN (arglist))); --- 3385,3396 ---- /* FALLTHROUGH */ case 1: /* length is greater than 1, call fwrite. */ { ! tree string_arg; + /* If optimizing for size keep fputs. */ + if (optimize_size) + return 0; + string_arg = TREE_VALUE (arglist); /* New argument list transforming fputs(string, stream) to fwrite(string, 1, len, stream). */ arglist = build_tree_list (NULL_TREE, TREE_VALUE (TREE_CHAIN (arglist))); *************** expand_builtin (exp, target, subtarget, *** 3599,3604 **** --- 3603,3611 ---- tree fndecl = TREE_OPERAND (TREE_OPERAND (exp, 0), 0); tree arglist = TREE_OPERAND (exp, 1); enum built_in_function fcode = DECL_FUNCTION_CODE (fndecl); + + /* Perform postincrements before expanding builtin functions.  */ + emit_queue (); if (DECL_BUILT_IN_CLASS (fndecl) == BUILT_IN_MD) return (*targetm.expand_builtin) (exp, target, subtarget, mode, ignore); diff -Nrc3pad gcc-3.2.2/gcc/c-decl.c gcc-3.2.3/gcc/c-decl.c *** gcc-3.2.2/gcc/c-decl.c Sat Nov 23 08:20:02 2002 --- gcc-3.2.3/gcc/c-decl.c Wed Mar 12 10:04:51 2003 *************** duplicate_decls (newdecl, olddecl, diffe *** 1665,1670 **** --- 1665,1677 ---- } } error_with_decl (olddecl, "previous declaration of `%s'"); + + /* This is safer because the initializer might contain references + to variables that were declared between olddecl and newdecl. This + will make the initializer invalid for olddecl in case it gets + assigned to olddecl below. */ + if (TREE_CODE (newdecl) == VAR_DECL) + DECL_INITIAL (newdecl) = 0; } else { diff -Nrc3pad gcc-3.2.2/gcc/c-parse.c gcc-3.2.3/gcc/c-parse.c *** gcc-3.2.2/gcc/c-parse.c Wed Feb 5 03:10:41 2003 --- gcc-3.2.3/gcc/c-parse.c Tue Apr 22 07:00:33 2003 *************** *** 1,75 **** ! /* A Bison parser, made from c-parse.y ! by GNU bison 1.33. */ ! #define YYBISON 1 /* Identify Bison output. */ ! # define IDENTIFIER 257 ! # define TYPENAME 258 ! # define SCSPEC 259 ! # define TYPESPEC 260 ! # define TYPE_QUAL 261 ! # define CONSTANT 262 ! # define STRING 263 ! # define ELLIPSIS 264 ! # define SIZEOF 265 ! # define ENUM 266 ! # define STRUCT 267 ! # define UNION 268 ! # define IF 269 ! # define ELSE 270 ! # define WHILE 271 ! # define DO 272 ! # define FOR 273 ! # define SWITCH 274 ! # define CASE 275 ! # define DEFAULT 276 ! # define BREAK 277 ! # define CONTINUE 278 ! # define RETURN 279 ! # define GOTO 280 ! # define ASM_KEYWORD 281 ! # define TYPEOF 282 ! # define ALIGNOF 283 ! # define ATTRIBUTE 284 ! # define EXTENSION 285 ! # define LABEL 286 ! # define REALPART 287 ! # define IMAGPART 288 ! # define VA_ARG 289 ! # define CHOOSE_EXPR 290 ! # define TYPES_COMPATIBLE_P 291 ! # define PTR_VALUE 292 ! # define PTR_BASE 293 ! # define PTR_EXTENT 294 ! # define STRING_FUNC_NAME 295 ! # define VAR_FUNC_NAME 296 ! # define ASSIGN 297 ! # define OROR 298 ! # define ANDAND 299 ! # define EQCOMPARE 300 ! # define ARITHCOMPARE 301 ! # define LSHIFT 302 ! # define RSHIFT 303 ! # define UNARY 304 ! # define PLUSPLUS 305 ! # define MINUSMINUS 306 ! # define HYPERUNARY 307 ! # define POINTSAT 308 ! # define INTERFACE 309 ! # define IMPLEMENTATION 310 ! # define END 311 ! # define SELECTOR 312 ! # define DEFS 313 ! # define ENCODE 314 ! # define CLASSNAME 315 ! # define PUBLIC 316 ! # define PRIVATE 317 ! # define PROTECTED 318 ! # define PROTOCOL 319 ! # define OBJECTNAME 320 ! # define CLASS 321 ! # define ALIAS 322 #line 34 "c-parse.y" #include "config.h" --- 1,197 ---- ! /* A Bison parser, made by GNU Bison 1.875. */ ! /* Skeleton parser for Yacc-like parsing with Bison, ! Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002 Free Software Foundation, Inc. ! This program is free software; you can redistribute it and/or modify ! it under the terms of the GNU General Public License as published by ! the Free Software Foundation; either version 2, or (at your option) ! any later version. ! ! This program is distributed in the hope that it will be useful, ! but WITHOUT ANY WARRANTY; without even the implied warranty of ! MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ! GNU General Public License for more details. ! ! You should have received a copy of the GNU General Public License ! along with this program; if not, write to the Free Software ! Foundation, Inc., 59 Temple Place - Suite 330, ! Boston, MA 02111-1307, USA. */ ! ! /* As a special exception, when this file is copied by Bison into a ! Bison output file, you may use that output file without restriction. ! This special exception was added by the Free Software Foundation ! in version 1.24 of Bison. */ ! ! /* Written by Richard Stallman by simplifying the original so called ! ``semantic'' parser. */ ! ! /* All symbols defined below should begin with yy or YY, to avoid ! infringing on user name space. This should be done even for local ! variables, as they might otherwise be expanded by user macros. ! There are some unavoidable exceptions within include files to ! define necessary library symbols; they are noted "INFRINGES ON ! USER NAME SPACE" below. */ ! ! /* Identify Bison output. */ ! #define YYBISON 1 ! ! /* Skeleton name. */ ! #define YYSKELETON_NAME "yacc.c" ! ! /* Pure parsers. */ ! #define YYPURE 0 ! ! /* Using locations. */ ! #define YYLSP_NEEDED 0 ! ! ! ! /* Tokens. */ ! #ifndef YYTOKENTYPE ! # define YYTOKENTYPE ! /* Put the tokens into the symbol table, so that GDB and other debuggers ! know about them. */ ! enum yytokentype { ! IDENTIFIER = 258, ! TYPENAME = 259, ! SCSPEC = 260, ! TYPESPEC = 261, ! TYPE_QUAL = 262, ! CONSTANT = 263, ! STRING = 264, ! ELLIPSIS = 265, ! SIZEOF = 266, ! ENUM = 267, ! STRUCT = 268, ! UNION = 269, ! IF = 270, ! ELSE = 271, ! WHILE = 272, ! DO = 273, ! FOR = 274, ! SWITCH = 275, ! CASE = 276, ! DEFAULT = 277, ! BREAK = 278, ! CONTINUE = 279, ! RETURN = 280, ! GOTO = 281, ! ASM_KEYWORD = 282, ! TYPEOF = 283, ! ALIGNOF = 284, ! ATTRIBUTE = 285, ! EXTENSION = 286, ! LABEL = 287, ! REALPART = 288, ! IMAGPART = 289, ! VA_ARG = 290, ! CHOOSE_EXPR = 291, ! TYPES_COMPATIBLE_P = 292, ! PTR_VALUE = 293, ! PTR_BASE = 294, ! PTR_EXTENT = 295, ! STRING_FUNC_NAME = 296, ! VAR_FUNC_NAME = 297, ! ASSIGN = 298, ! OROR = 299, ! ANDAND = 300, ! EQCOMPARE = 301, ! ARITHCOMPARE = 302, ! RSHIFT = 303, ! LSHIFT = 304, ! MINUSMINUS = 305, ! PLUSPLUS = 306, ! UNARY = 307, ! HYPERUNARY = 308, ! POINTSAT = 309, ! INTERFACE = 310, ! IMPLEMENTATION = 311, ! END = 312, ! SELECTOR = 313, ! DEFS = 314, ! ENCODE = 315, ! CLASSNAME = 316, ! PUBLIC = 317, ! PRIVATE = 318, ! PROTECTED = 319, ! PROTOCOL = 320, ! OBJECTNAME = 321, ! CLASS = 322, ! ALIAS = 323 ! }; ! #endif ! #define IDENTIFIER 258 ! #define TYPENAME 259 ! #define SCSPEC 260 ! #define TYPESPEC 261 ! #define TYPE_QUAL 262 ! #define CONSTANT 263 ! #define STRING 264 ! #define ELLIPSIS 265 ! #define SIZEOF 266 ! #define ENUM 267 ! #define STRUCT 268 ! #define UNION 269 ! #define IF 270 ! #define ELSE 271 ! #define WHILE 272 ! #define DO 273 ! #define FOR 274 ! #define SWITCH 275 ! #define CASE 276 ! #define DEFAULT 277 ! #define BREAK 278 ! #define CONTINUE 279 ! #define RETURN 280 ! #define GOTO 281 ! #define ASM_KEYWORD 282 ! #define TYPEOF 283 ! #define ALIGNOF 284 ! #define ATTRIBUTE 285 ! #define EXTENSION 286 ! #define LABEL 287 ! #define REALPART 288 ! #define IMAGPART 289 ! #define VA_ARG 290 ! #define CHOOSE_EXPR 291 ! #define TYPES_COMPATIBLE_P 292 ! #define PTR_VALUE 293 ! #define PTR_BASE 294 ! #define PTR_EXTENT 295 ! #define STRING_FUNC_NAME 296 ! #define VAR_FUNC_NAME 297 ! #define ASSIGN 298 ! #define OROR 299 ! #define ANDAND 300 ! #define EQCOMPARE 301 ! #define ARITHCOMPARE 302 ! #define RSHIFT 303 ! #define LSHIFT 304 ! #define MINUSMINUS 305 ! #define PLUSPLUS 306 ! #define UNARY 307 ! #define HYPERUNARY 308 ! #define POINTSAT 309 ! #define INTERFACE 310 ! #define IMPLEMENTATION 311 ! #define END 312 ! #define SELECTOR 313 ! #define DEFS 314 ! #define ENCODE 315 ! #define CLASSNAME 316 ! #define PUBLIC 317 ! #define PRIVATE 318 ! #define PROTECTED 319 ! #define PROTOCOL 320 ! #define OBJECTNAME 321 ! #define CLASS 322 ! #define ALIAS 323 + + + + /* Copy the first part of user declarations. */ #line 34 "c-parse.y" #include "config.h" *************** *** 101,112 **** /* Rename the "yyparse" function so that we can override it elsewhere. */ #define yyparse yyparse_1 #line 67 "c-parse.y" ! #ifndef YYSTYPE ! typedef union {long itype; tree ttype; enum tree_code code; ! const char *filename; int lineno; } yystype; ! # define YYSTYPE yystype #endif #line 200 "c-parse.y" /* Number of statements (loosely speaking) and compound statements --- 223,256 ---- /* Rename the "yyparse" function so that we can override it elsewhere. */ #define yyparse yyparse_1 + + /* Enabling traces. */ + #ifndef YYDEBUG + # define YYDEBUG 0 + #endif + + /* Enabling verbose error messages. */ + #ifdef YYERROR_VERBOSE + # undef YYERROR_VERBOSE + # define YYERROR_VERBOSE 1 + #else + # define YYERROR_VERBOSE 0 + #endif + + #if ! defined (YYSTYPE) && ! defined (YYSTYPE_IS_DECLARED) #line 67 "c-parse.y" ! typedef union YYSTYPE {long itype; tree ttype; enum tree_code code; ! const char *filename; int lineno; } YYSTYPE; ! /* Line 191 of yacc.c. */ ! #line 245 "c-p10602.c" ! # define yystype YYSTYPE /* obsolescent; will be withdrawn */ ! # define YYSTYPE_IS_DECLARED 1 ! # define YYSTYPE_IS_TRIVIAL 1 #endif + + + + /* Copy the second part of user declarations. */ #line 200 "c-parse.y" /* Number of statements (loosely speaking) and compound statements *************** c_parse_init () *** 191,222 **** ggc_add_tree_root (&all_prefix_attributes, 1); } ! #ifndef YYDEBUG ! # define YYDEBUG 0 #endif ! #define YYFINAL 901 ! #define YYFLAG -32768 ! #define YYNTBASE 91 ! /* YYTRANSLATE(YYLEX) -- Bison token number corresponding to YYLEX. */ ! #define YYTRANSLATE(x) ((unsigned)(x) <= 322 ? yytranslate[x] : 290) ! /* YYTRANSLATE[YYLEX] -- Bison token number corresponding to YYLEX. */ ! static const char yytranslate[] = { 0, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 87, 2, 2, 2, 60, 51, 2, ! 67, 83, 58, 56, 88, 57, 66, 59, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 46, 84, ! 2, 44, 2, 45, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 68, 2, 90, 50, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 89, 49, 85, 86, 2, 2, 2, --- 335,473 ---- ggc_add_tree_root (&all_prefix_attributes, 1); } ! ! ! /* Line 214 of yacc.c. */ ! #line 341 "c-p10602.c" ! ! #if ! defined (yyoverflow) || YYERROR_VERBOSE ! ! /* The parser invokes alloca or malloc; define the necessary symbols. */ ! ! # if YYSTACK_USE_ALLOCA ! # define YYSTACK_ALLOC alloca ! # else ! # ifndef YYSTACK_USE_ALLOCA ! # if defined (alloca) || defined (_ALLOCA_H) ! # define YYSTACK_ALLOC alloca ! # else ! # ifdef __GNUC__ ! # define YYSTACK_ALLOC __builtin_alloca ! # endif ! # endif ! # endif ! # endif ! ! # ifdef YYSTACK_ALLOC ! /* Pacify GCC's `empty if-body' warning. */ ! # define YYSTACK_FREE(Ptr) do { /* empty */; } while (0) ! # else ! # if defined (__STDC__) || defined (__cplusplus) ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T size_t ! # endif ! # define YYSTACK_ALLOC malloc ! # define YYSTACK_FREE free ! # endif ! #endif /* ! defined (yyoverflow) || YYERROR_VERBOSE */ ! ! ! #if (! defined (yyoverflow) \ ! && (! defined (__cplusplus) \ ! || (YYSTYPE_IS_TRIVIAL))) ! ! /* A type that is properly aligned for any stack member. */ ! union yyalloc ! { ! short yyss; ! YYSTYPE yyvs; ! }; ! ! /* The size of the maximum gap between one aligned stack and the next. */ ! # define YYSTACK_GAP_MAXIMUM (sizeof (union yyalloc) - 1) ! ! /* The size of an array large to enough to hold all stacks, each with ! N elements. */ ! # define YYSTACK_BYTES(N) \ ! ((N) * (sizeof (short) + sizeof (YYSTYPE)) \ ! + YYSTACK_GAP_MAXIMUM) ! ! /* Copy COUNT objects from FROM to TO. The source and destination do ! not overlap. */ ! # ifndef YYCOPY ! # if 1 < __GNUC__ ! # define YYCOPY(To, From, Count) \ ! __builtin_memcpy (To, From, (Count) * sizeof (*(From))) ! # else ! # define YYCOPY(To, From, Count) \ ! do \ ! { \ ! register YYSIZE_T yyi; \ ! for (yyi = 0; yyi < (Count); yyi++) \ ! (To)[yyi] = (From)[yyi]; \ ! } \ ! while (0) ! # endif ! # endif ! ! /* Relocate STACK from its old location to the new one. The ! local variables YYSIZE and YYSTACKSIZE give the old and new number of ! elements in the stack, and YYPTR gives the new location of the ! stack. Advance YYPTR to a properly aligned location for the next ! stack. */ ! # define YYSTACK_RELOCATE(Stack) \ ! do \ ! { \ ! YYSIZE_T yynewbytes; \ ! YYCOPY (&yyptr->Stack, Stack, yysize); \ ! Stack = &yyptr->Stack; \ ! yynewbytes = yystacksize * sizeof (*Stack) + YYSTACK_GAP_MAXIMUM; \ ! yyptr += yynewbytes / sizeof (*yyptr); \ ! } \ ! while (0) ! #endif + #if defined (__STDC__) || defined (__cplusplus) + typedef signed char yysigned_char; + #else + typedef short yysigned_char; + #endif + /* YYFINAL -- State number of the termination state. */ + #define YYFINAL 4 + /* YYLAST -- Last index in YYTABLE. */ + #define YYLAST 3173 ! /* YYNTOKENS -- Number of terminals. */ ! #define YYNTOKENS 91 ! /* YYNNTS -- Number of nonterminals. */ ! #define YYNNTS 200 ! /* YYNRULES -- Number of rules. */ ! #define YYNRULES 561 ! /* YYNRULES -- Number of states. */ ! #define YYNSTATES 901 ! /* YYTRANSLATE(YYLEX) -- Bison symbol number corresponding to YYLEX. */ ! #define YYUNDEFTOK 2 ! #define YYMAXUTOK 323 ! #define YYTRANSLATE(YYX) \ ! ((unsigned int) (YYX) <= YYMAXUTOK ? yytranslate[YYX] : YYUNDEFTOK) ! ! /* YYTRANSLATE[YYLEX] -- Bison symbol number corresponding to YYLEX. */ ! static const unsigned char yytranslate[] = { 0, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 87, 2, 2, 2, 60, 51, 2, ! 66, 83, 58, 56, 88, 57, 65, 59, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 46, 84, ! 2, 43, 2, 45, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 67, 2, 90, 50, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 89, 49, 85, 86, 2, 2, 2, *************** static const char yytranslate[] = *** 232,590 **** 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 2, 2, 2, 1, 3, 4, 5, ! 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, ! 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, ! 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, ! 36, 37, 38, 39, 40, 41, 42, 43, 47, 48, ! 52, 53, 54, 55, 61, 62, 63, 64, 65, 69, ! 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, ! 80, 81, 82 }; #if YYDEBUG ! static const short yyprhs[] = { ! 0, 0, 1, 3, 4, 7, 8, 12, 14, 16, ! 22, 25, 29, 34, 39, 42, 45, 48, 50, 51, ! 52, 62, 67, 68, 69, 79, 84, 85, 86, 95, ! 99, 101, 103, 105, 107, 109, 111, 113, 115, 117, ! 119, 120, 122, 124, 128, 130, 133, 136, 139, 142, ! 145, 150, 153, 158, 161, 164, 166, 168, 170, 172, ! 177, 179, 183, 187, 191, 195, 199, 203, 207, 211, ! 215, 219, 223, 227, 228, 233, 234, 239, 240, 241, ! 249, 250, 256, 260, 264, 266, 268, 270, 272, 273, ! 281, 285, 289, 293, 297, 302, 309, 318, 325, 330, ! 334, 338, 341, 344, 346, 349, 350, 352, 355, 359, ! 361, 363, 366, 369, 374, 379, 382, 385, 389, 390, ! 392, 397, 402, 406, 410, 413, 416, 418, 421, 424, ! 427, 430, 433, 435, 438, 440, 443, 446, 449, 452, ! 455, 458, 460, 463, 466, 469, 472, 475, 478, 481, ! 484, 487, 490, 493, 496, 499, 502, 505, 508, 510, 513, 516, 519, 522, 525, 528, 531, 534, 537, 540, 543, 546, 549, 552, 555, 558, 561, 564, 567, 570, 573, 576, 579, 582, 585, 588, 591, 594, 597, 600, 603, 606, 609, 612, 615, 618, 621, 624, 627, 630, ! 633, 636, 639, 642, 644, 646, 648, 650, 652, 654, ! 656, 658, 660, 662, 664, 666, 668, 670, 672, 674, ! 676, 678, 680, 682, 684, 686, 688, 690, 692, 694, ! 696, 698, 700, 702, 704, 706, 708, 710, 712, 714, ! 716, 718, 720, 722, 724, 726, 728, 730, 732, 734, ! 736, 738, 740, 742, 744, 746, 748, 750, 752, 754, ! 755, 757, 759, 761, 763, 765, 767, 769, 771, 776, ! 781, 783, 788, 790, 795, 796, 801, 802, 809, 813, ! 814, 821, 825, 826, 828, 830, 833, 840, 842, 846, ! 847, 849, 854, 861, 866, 868, 870, 872, 874, 876, ! 877, 882, 884, 885, 888, 890, 894, 898, 901, 902, ! 907, 909, 910, 915, 917, 919, 921, 924, 927, 933, ! 937, 938, 939, 947, 948, 949, 957, 959, 961, 966, ! 970, 973, 977, 979, 981, 983, 987, 990, 992, 996, ! 999, 1003, 1007, 1012, 1016, 1021, 1025, 1028, 1030, 1032, ! 1035, 1037, 1040, 1042, 1045, 1046, 1054, 1060, 1061, 1069, ! 1075, 1076, 1085, 1086, 1094, 1097, 1100, 1103, 1104, 1106, ! 1107, 1109, 1111, 1114, 1115, 1119, 1122, 1126, 1131, 1135, ! 1137, 1139, 1142, 1144, 1149, 1151, 1156, 1161, 1168, 1174, ! 1179, 1186, 1192, 1194, 1198, 1200, 1202, 1206, 1207, 1211, ! 1212, 1214, 1215, 1217, 1220, 1222, 1224, 1226, 1230, 1233, ! 1237, 1242, 1246, 1249, 1252, 1254, 1258, 1263, 1266, 1270, ! 1274, 1279, 1284, 1290, 1296, 1298, 1300, 1302, 1304, 1306, ! 1309, 1312, 1315, 1318, 1320, 1323, 1326, 1329, 1331, 1334, ! 1337, 1340, 1343, 1345, 1348, 1350, 1352, 1354, 1356, 1359, ! 1360, 1361, 1362, 1363, 1364, 1366, 1368, 1371, 1375, 1377, ! 1380, 1382, 1384, 1390, 1392, 1394, 1397, 1400, 1403, 1406, ! 1407, 1413, 1414, 1419, 1420, 1421, 1423, 1426, 1430, 1434, ! 1438, 1439, 1444, 1446, 1450, 1451, 1452, 1460, 1466, 1469, ! 1470, 1471, 1472, 1473, 1486, 1487, 1494, 1497, 1499, 1501, ! 1504, 1508, 1511, 1514, 1517, 1521, 1528, 1537, 1548, 1561, ! 1565, 1570, 1572, 1576, 1582, 1585, 1591, 1592, 1594, 1595, ! 1597, 1598, 1600, 1602, 1606, 1611, 1619, 1621, 1625, 1626, ! 1630, 1633, 1634, 1635, 1642, 1645, 1646, 1648, 1650, 1654, ! 1656, 1660, 1665, 1670, 1674, 1679, 1683, 1688, 1693, 1697, ! 1702, 1706, 1708, 1709, 1713, 1715, 1718, 1720, 1724, 1726, ! 1730 }; static const short yyrhs[] = { ! -1, 92, 0, 0, 93, 95, 0, 0, 92, 94, ! 95, 0, 97, 0, 96, 0, 27, 67, 106, 83, ! 84, 0, 289, 95, 0, 128, 162, 84, 0, 148, ! 128, 162, 84, 0, 147, 128, 161, 84, 0, 154, ! 84, 0, 1, 84, 0, 1, 85, 0, 84, 0, ! 0, 0, 147, 128, 190, 98, 123, 99, 250, 251, ! 239, 0, 147, 128, 190, 1, 0, 0, 0, 148, ! 128, 195, 100, 123, 101, 250, 251, 239, 0, 148, ! 128, 195, 1, 0, 0, 0, 128, 195, 102, 123, ! 103, 250, 251, 239, 0, 128, 195, 1, 0, 3, ! 0, 4, 0, 51, 0, 57, 0, 56, 0, 62, ! 0, 63, 0, 86, 0, 87, 0, 108, 0, 0, ! 108, 0, 114, 0, 108, 88, 114, 0, 120, 0, ! 58, 113, 0, 289, 113, 0, 105, 113, 0, 48, ! 104, 0, 110, 109, 0, 110, 67, 216, 83, 0, ! 111, 109, 0, 111, 67, 216, 83, 0, 33, 113, ! 0, 34, 113, 0, 11, 0, 29, 0, 28, 0, ! 109, 0, 67, 216, 83, 113, 0, 113, 0, 114, ! 56, 114, 0, 114, 57, 114, 0, 114, 58, 114, ! 0, 114, 59, 114, 0, 114, 60, 114, 0, 114, ! 54, 114, 0, 114, 55, 114, 0, 114, 53, 114, ! 0, 114, 52, 114, 0, 114, 51, 114, 0, 114, ! 49, 114, 0, 114, 50, 114, 0, 0, 114, 48, ! 115, 114, 0, 0, 114, 47, 116, 114, 0, 0, ! 0, 114, 45, 117, 106, 46, 118, 114, 0, 0, ! 114, 45, 119, 46, 114, 0, 114, 44, 114, 0, ! 114, 43, 114, 0, 3, 0, 8, 0, 122, 0, ! 42, 0, 0, 67, 216, 83, 89, 121, 176, 85, ! 0, 67, 106, 83, 0, 67, 1, 83, 0, 243, ! 241, 83, 0, 243, 1, 83, 0, 120, 67, 107, ! 83, 0, 35, 67, 114, 88, 216, 83, 0, 36, ! 67, 114, 88, 114, 88, 114, 83, 0, 37, 67, ! 216, 88, 216, 83, 0, 120, 68, 106, 90, 0, ! 120, 66, 104, 0, 120, 65, 104, 0, 120, 62, ! 0, 120, 63, 0, 9, 0, 122, 9, 0, 0, ! 125, 0, 125, 10, 0, 250, 251, 126, 0, 124, ! 0, 231, 0, 125, 124, 0, 124, 231, 0, 149, ! 128, 161, 84, 0, 150, 128, 162, 84, 0, 149, ! 84, 0, 150, 84, 0, 250, 251, 130, 0, 0, ! 168, 0, 147, 128, 161, 84, 0, 148, 128, 162, ! 84, 0, 147, 128, 184, 0, 148, 128, 187, 0, ! 154, 84, 0, 289, 130, 0, 7, 0, 131, 7, ! 0, 132, 7, 0, 131, 169, 0, 133, 7, 0, ! 134, 7, 0, 169, 0, 133, 169, 0, 156, 0, ! 135, 7, 0, 136, 7, 0, 135, 158, 0, 136, ! 158, 0, 131, 156, 0, 132, 156, 0, 157, 0, ! 135, 169, 0, 135, 159, 0, 136, 159, 0, 131, ! 157, 0, 132, 157, 0, 137, 7, 0, 138, 7, ! 0, 137, 158, 0, 138, 158, 0, 133, 156, 0, ! 134, 156, 0, 137, 169, 0, 137, 159, 0, 138, ! 159, 0, 133, 157, 0, 134, 157, 0, 5, 0, ! 139, 7, 0, 140, 7, 0, 131, 5, 0, 132, ! 5, 0, 139, 5, 0, 140, 5, 0, 139, 169, ! 0, 141, 7, 0, 142, 7, 0, 133, 5, 0, ! 134, 5, 0, 141, 5, 0, 142, 5, 0, 141, ! 169, 0, 143, 7, 0, 144, 7, 0, 143, 158, ! 0, 144, 158, 0, 139, 156, 0, 140, 156, 0, ! 135, 5, 0, 136, 5, 0, 143, 5, 0, 144, ! 5, 0, 143, 169, 0, 143, 159, 0, 144, 159, ! 0, 139, 157, 0, 140, 157, 0, 145, 7, 0, ! 146, 7, 0, 145, 158, 0, 146, 158, 0, 141, ! 156, 0, 142, 156, 0, 137, 5, 0, 138, 5, ! 0, 145, 5, 0, 146, 5, 0, 145, 169, 0, ! 145, 159, 0, 146, 159, 0, 141, 157, 0, 142, ! 157, 0, 135, 0, 136, 0, 137, 0, 138, 0, ! 143, 0, 144, 0, 145, 0, 146, 0, 131, 0, ! 132, 0, 133, 0, 134, 0, 139, 0, 140, 0, ! 141, 0, 142, 0, 135, 0, 136, 0, 143, 0, ! 144, 0, 131, 0, 132, 0, 139, 0, 140, 0, ! 135, 0, 136, 0, 137, 0, 138, 0, 131, 0, ! 132, 0, 133, 0, 134, 0, 135, 0, 136, 0, ! 137, 0, 138, 0, 131, 0, 132, 0, 133, 0, ! 134, 0, 131, 0, 132, 0, 133, 0, 134, 0, ! 135, 0, 136, 0, 137, 0, 138, 0, 139, 0, ! 140, 0, 141, 0, 142, 0, 143, 0, 144, 0, ! 145, 0, 146, 0, 0, 152, 0, 158, 0, 160, ! 0, 159, 0, 6, 0, 204, 0, 199, 0, 4, ! 0, 112, 67, 106, 83, 0, 112, 67, 216, 83, ! 0, 164, 0, 161, 88, 129, 164, 0, 166, 0, ! 162, 88, 129, 166, 0, 0, 27, 67, 122, 83, ! 0, 0, 190, 163, 168, 44, 165, 174, 0, 190, ! 163, 168, 0, 0, 195, 163, 168, 44, 167, 174, ! 0, 195, 163, 168, 0, 0, 169, 0, 170, 0, ! 169, 170, 0, 30, 67, 67, 171, 83, 83, 0, ! 172, 0, 171, 88, 172, 0, 0, 173, 0, 173, ! 67, 3, 83, 0, 173, 67, 3, 88, 108, 83, ! 0, 173, 67, 107, 83, 0, 104, 0, 5, 0, ! 6, 0, 7, 0, 114, 0, 0, 89, 175, 176, ! 85, 0, 1, 0, 0, 177, 205, 0, 178, 0, ! 177, 88, 178, 0, 182, 44, 180, 0, 183, 180, ! 0, 0, 104, 46, 179, 180, 0, 180, 0, 0, ! 89, 181, 176, 85, 0, 114, 0, 1, 0, 183, ! 0, 182, 183, 0, 66, 104, 0, 68, 114, 10, ! 114, 90, 0, 68, 114, 90, 0, 0, 0, 190, ! 185, 123, 186, 250, 251, 244, 0, 0, 0, 195, ! 188, 123, 189, 250, 251, 244, 0, 191, 0, 195, ! 0, 67, 168, 191, 83, 0, 191, 67, 284, 0, ! 191, 224, 0, 58, 155, 191, 0, 4, 0, 193, ! 0, 194, 0, 193, 67, 284, 0, 193, 224, 0, ! 4, 0, 194, 67, 284, 0, 194, 224, 0, 58, ! 155, 193, 0, 58, 155, 194, 0, 67, 168, 194, ! 83, 0, 195, 67, 284, 0, 67, 168, 195, 83, ! 0, 58, 155, 195, 0, 195, 224, 0, 3, 0, ! 13, 0, 13, 169, 0, 14, 0, 14, 169, 0, ! 12, 0, 12, 169, 0, 0, 196, 104, 89, 200, ! 207, 85, 168, 0, 196, 89, 207, 85, 168, 0, ! 0, 197, 104, 89, 201, 207, 85, 168, 0, 197, ! 89, 207, 85, 168, 0, 0, 198, 104, 89, 202, ! 214, 206, 85, 168, 0, 0, 198, 89, 203, 214, ! 206, 85, 168, 0, 196, 104, 0, 197, 104, 0, ! 198, 104, 0, 0, 88, 0, 0, 88, 0, 208, ! 0, 208, 209, 0, 0, 208, 209, 84, 0, 208, ! 84, 0, 151, 128, 210, 0, 151, 128, 250, 251, ! 0, 152, 128, 211, 0, 152, 0, 1, 0, 289, ! 209, 0, 212, 0, 210, 88, 129, 212, 0, 213, ! 0, 211, 88, 129, 213, 0, 250, 251, 190, 168, ! 0, 250, 251, 190, 46, 114, 168, 0, 250, 251, ! 46, 114, 168, 0, 250, 251, 195, 168, 0, 250, ! 251, 195, 46, 114, 168, 0, 250, 251, 46, 114, ! 168, 0, 215, 0, 214, 88, 215, 0, 1, 0, ! 104, 0, 104, 44, 114, 0, 0, 153, 217, 218, ! 0, 0, 220, 0, 0, 220, 0, 221, 169, 0, ! 222, 0, 221, 0, 223, 0, 58, 155, 221, 0, ! 58, 155, 0, 58, 155, 222, 0, 67, 168, 220, ! 83, 0, 223, 67, 274, 0, 223, 224, 0, 67, ! 274, 0, 224, 0, 68, 106, 90, 0, 68, 153, ! 106, 90, 0, 68, 90, 0, 68, 153, 90, 0, ! 68, 58, 90, 0, 68, 153, 58, 90, 0, 68, ! 5, 106, 90, 0, 68, 5, 153, 106, 90, 0, ! 68, 153, 5, 106, 90, 0, 226, 0, 227, 0, ! 228, 0, 229, 0, 254, 0, 226, 254, 0, 227, ! 254, 0, 228, 254, 0, 229, 254, 0, 127, 0, ! 226, 127, 0, 227, 127, 0, 229, 127, 0, 255, ! 0, 226, 255, 0, 227, 255, 0, 228, 255, 0, ! 229, 255, 0, 231, 0, 230, 231, 0, 226, 0, ! 227, 0, 228, 0, 229, 0, 1, 84, 0, 0, ! 0, 0, 0, 0, 237, 0, 238, 0, 237, 238, ! 0, 32, 288, 84, 0, 244, 0, 1, 244, 0, ! 89, 0, 85, 0, 232, 236, 242, 85, 233, 0, ! 225, 0, 1, 0, 67, 89, 0, 240, 241, 0, ! 246, 253, 0, 246, 1, 0, 0, 15, 247, 67, ! 106, 83, 0, 0, 18, 249, 253, 17, 0, 0, ! 0, 254, 0, 255, 252, 0, 234, 252, 235, 0, ! 250, 251, 266, 0, 250, 251, 267, 0, 0, 245, ! 16, 257, 253, 0, 245, 0, 245, 16, 1, 0, ! 0, 0, 17, 258, 67, 106, 83, 259, 253, 0, ! 248, 67, 106, 83, 84, 0, 248, 1, 0, 0, ! 0, 0, 0, 19, 260, 67, 265, 261, 269, 84, ! 262, 269, 83, 263, 253, 0, 0, 20, 67, 106, ! 83, 264, 253, 0, 269, 84, 0, 130, 0, 244, ! 0, 106, 84, 0, 234, 256, 235, 0, 23, 84, ! 0, 24, 84, 0, 25, 84, 0, 25, 106, 84, ! 0, 27, 268, 67, 106, 83, 84, 0, 27, 268, ! 67, 106, 46, 270, 83, 84, 0, 27, 268, 67, ! 106, 46, 270, 46, 270, 83, 84, 0, 27, 268, ! 67, 106, 46, 270, 46, 270, 46, 273, 83, 84, ! 0, 26, 104, 84, 0, 26, 58, 106, 84, 0, ! 84, 0, 21, 114, 46, 0, 21, 114, 10, 114, ! 46, 0, 22, 46, 0, 104, 250, 251, 46, 168, ! 0, 0, 7, 0, 0, 106, 0, 0, 271, 0, ! 272, 0, 271, 88, 272, 0, 9, 67, 106, 83, ! 0, 68, 104, 90, 9, 67, 106, 83, 0, 122, ! 0, 273, 88, 122, 0, 0, 168, 275, 276, 0, ! 279, 83, 0, 0, 0, 280, 84, 277, 168, 278, ! 276, 0, 1, 83, 0, 0, 10, 0, 280, 0, ! 280, 88, 10, 0, 282, 0, 280, 88, 281, 0, ! 147, 128, 192, 168, 0, 147, 128, 195, 168, 0, ! 147, 128, 219, 0, 148, 128, 195, 168, 0, 148, ! 128, 219, 0, 149, 283, 192, 168, 0, 149, 283, ! 195, 168, 0, 149, 283, 219, 0, 150, 283, 195, ! 168, 0, 150, 283, 219, 0, 128, 0, 0, 168, ! 285, 286, 0, 276, 0, 287, 83, 0, 3, 0, ! 287, 88, 3, 0, 104, 0, 288, 88, 104, 0, ! 31, 0 }; ! #endif ! ! #if YYDEBUG ! /* YYRLINE[YYN] -- source line where rule number YYN was defined. */ ! static const short yyrline[] = { ! 0, 286, 291, 306, 306, 308, 308, 311, 313, 314, ! 322, 326, 334, 336, 338, 340, 341, 342, 347, 347, ! 347, 360, 362, 362, 362, 374, 376, 376, 376, 388, ! 392, 394, 397, 399, 401, 406, 408, 410, 412, 416, ! 420, 423, 426, 429, 433, 435, 438, 441, 445, 462, ! 468, 471, 474, 477, 479, 483, 487, 491, 495, 497, ! 501, 503, 505, 507, 509, 511, 513, 515, 517, 519, ! 521, 523, 525, 527, 527, 533, 533, 539, 539, 539, ! 548, 548, 558, 565, 575, 582, 583, 585, 587, 587, ! 600, 605, 607, 623, 630, 632, 635, 645, 655, 657, ! 661, 667, 669, 674, 676, 693, 695, 696, 706, 711, ! 713, 714, 715, 722, 725, 727, 730, 738, 747, 757, ! 762, 765, 767, 769, 771, 773, 829, 833, 836, 841, ! 847, 851, 856, 860, 865, 869, 872, 875, 878, 881, ! 884, 889, 893, 896, 899, 902, 905, 910, 914, 917, ! 920, 923, 926, 931, 935, 938, 941, 944, 949, 953, ! 956, 959, 965, 971, 977, 985, 991, 995, 998, 1004, ! 1010, 1016, 1024, 1030, 1034, 1037, 1040, 1043, 1046, 1049, ! 1055, 1061, 1067, 1075, 1079, 1082, 1085, 1088, 1093, 1097, ! 1100, 1103, 1106, 1109, 1112, 1118, 1124, 1130, 1138, 1142, ! 1145, 1148, 1151, 1157, 1159, 1160, 1161, 1162, 1163, 1164, ! 1165, 1168, 1170, 1171, 1172, 1173, 1174, 1175, 1176, 1179, ! 1181, 1182, 1183, 1186, 1188, 1189, 1190, 1193, 1195, 1196, ! 1197, 1200, 1202, 1203, 1204, 1207, 1209, 1210, 1211, 1212, ! 1213, 1214, 1215, 1218, 1220, 1221, 1222, 1223, 1224, 1225, ! 1226, 1227, 1228, 1229, 1230, 1231, 1232, 1233, 1234, 1238, ! 1241, 1266, 1268, 1271, 1275, 1278, 1281, 1285, 1290, 1292, ! 1298, 1300, 1303, 1305, 1308, 1311, 1317, 1317, 1326, 1333, ! 1333, 1342, 1349, 1352, 1356, 1359, 1363, 1368, 1371, 1375, ! 1378, 1380, 1382, 1384, 1391, 1393, 1394, 1395, 1400, 1402, ! 1402, 1406, 1411, 1415, 1418, 1420, 1425, 1429, 1432, 1432, ! 1438, 1441, 1441, 1446, 1448, 1451, 1453, 1456, 1462, 1466, ! 1470, 1470, 1470, 1500, 1500, 1500, 1533, 1535, 1540, 1543, ! 1548, 1550, 1552, 1559, 1561, 1564, 1570, 1572, 1575, 1581, ! 1583, 1585, 1587, 1594, 1600, 1602, 1604, 1606, 1609, 1612, ! 1616, 1619, 1623, 1626, 1636, 1636, 1643, 1647, 1647, 1651, ! 1655, 1655, 1660, 1660, 1667, 1670, 1672, 1680, 1682, 1685, ! 1687, 1692, 1695, 1700, 1702, 1704, 1709, 1713, 1723, 1726, ! 1731, 1733, 1738, 1740, 1744, 1746, 1750, 1754, 1758, 1763, ! 1767, 1771, 1781, 1783, 1788, 1793, 1796, 1800, 1800, 1808, ! 1811, 1814, 1819, 1823, 1829, 1831, 1834, 1836, 1840, 1843, ! 1847, 1850, 1852, 1854, 1856, 1862, 1865, 1867, 1869, 1871, ! 1873, 1875, 1879, 1883, 1895, 1897, 1898, 1902, 1905, 1907, ! 1908, 1909, 1910, 1913, 1915, 1918, 1919, 1922, 1924, 1925, ! 1926, 1927, 1930, 1932, 1935, 1937, 1938, 1939, 1942, 1945, ! 1952, 1957, 1973, 1988, 1990, 1995, 1997, 2000, 2014, 2017, ! 2020, 2024, 2026, 2033, 2035, 2038, 2056, 2063, 2069, 2072, ! 2072, 2094, 2094, 2114, 2120, 2126, 2128, 2132, 2138, 2152, ! 2161, 2161, 2170, 2182, 2192, 2192, 2192, 2202, 2205, 2207, ! 2207, 2207, 2207, 2207, 2221, 2221, 2228, 2231, 2236, 2239, ! 2242, 2246, 2249, 2252, 2255, 2258, 2262, 2266, 2271, 2275, ! 2287, 2293, 2301, 2304, 2307, 2310, 2325, 2329, 2333, 2336, ! 2341, 2343, 2346, 2348, 2352, 2355, 2359, 2362, 2371, 2371, ! 2382, 2384, 2384, 2384, 2397, 2403, 2405, 2415, 2417, 2421, ! 2424, 2430, 2436, 2441, 2444, 2450, 2457, 2463, 2468, 2471, ! 2477, 2482, 2491, 2491, 2502, 2504, 2521, 2524, 2529, 2532, ! 2536 }; #endif ! ! #if (YYDEBUG) || defined YYERROR_VERBOSE ! ! /* YYTNAME[TOKEN_NUM] -- String name of the token TOKEN_NUM. */ static const char *const yytname[] = { ! "$", "error", "$undefined.", "IDENTIFIER", "TYPENAME", "SCSPEC", "TYPESPEC", "TYPE_QUAL", "CONSTANT", "STRING", "ELLIPSIS", "SIZEOF", "ENUM", "STRUCT", "UNION", "IF", "ELSE", "WHILE", "DO", "FOR", "SWITCH", "CASE", "DEFAULT", "BREAK", "CONTINUE", "RETURN", "GOTO", "ASM_KEYWORD", "TYPEOF", "ALIGNOF", "ATTRIBUTE", "EXTENSION", "LABEL", "REALPART", "IMAGPART", "VA_ARG", "CHOOSE_EXPR", "TYPES_COMPATIBLE_P", "PTR_VALUE", ! "PTR_BASE", "PTR_EXTENT", "STRING_FUNC_NAME", "VAR_FUNC_NAME", "ASSIGN", ! "'='", "'?'", "':'", "OROR", "ANDAND", "'|'", "'^'", "'&'", "EQCOMPARE", ! "ARITHCOMPARE", "LSHIFT", "RSHIFT", "'+'", "'-'", "'*'", "'/'", "'%'", ! "UNARY", "PLUSPLUS", "MINUSMINUS", "HYPERUNARY", "POINTSAT", "'.'", ! "'('", "'['", "INTERFACE", "IMPLEMENTATION", "END", "SELECTOR", "DEFS", ! "ENCODE", "CLASSNAME", "PUBLIC", "PRIVATE", "PROTECTED", "PROTOCOL", ! "OBJECTNAME", "CLASS", "ALIAS", "')'", "';'", "'}'", "'~'", "'!'", ! "','", "'{'", "']'", "program", "extdefs", "@1", "@2", "extdef", ! "datadef", "fndef", "@3", "@4", "@5", "@6", "@7", "@8", "identifier", ! "unop", "expr", "exprlist", "nonnull_exprlist", "unary_expr", "sizeof", ! "alignof", "typeof", "cast_expr", "expr_no_commas", "@9", "@10", "@11", ! "@12", "@13", "primary", "@14", "string", "old_style_parm_decls", ! "lineno_datadecl", "datadecls", "datadecl", "lineno_decl", "setspecs", ! "maybe_resetattrs", "decl", "declspecs_nosc_nots_nosa_noea", ! "declspecs_nosc_nots_nosa_ea", "declspecs_nosc_nots_sa_noea", ! "declspecs_nosc_nots_sa_ea", "declspecs_nosc_ts_nosa_noea", ! "declspecs_nosc_ts_nosa_ea", "declspecs_nosc_ts_sa_noea", ! "declspecs_nosc_ts_sa_ea", "declspecs_sc_nots_nosa_noea", ! "declspecs_sc_nots_nosa_ea", "declspecs_sc_nots_sa_noea", ! "declspecs_sc_nots_sa_ea", "declspecs_sc_ts_nosa_noea", ! "declspecs_sc_ts_nosa_ea", "declspecs_sc_ts_sa_noea", ! "declspecs_sc_ts_sa_ea", "declspecs_ts", "declspecs_nots", ! "declspecs_ts_nosa", "declspecs_nots_nosa", "declspecs_nosc_ts", ! "declspecs_nosc_nots", "declspecs_nosc", "declspecs", ! "maybe_type_quals_attrs", "typespec_nonattr", "typespec_attr", ! "typespec_reserved_nonattr", "typespec_reserved_attr", "typespec_nonreserved_nonattr", "initdecls", "notype_initdecls", "maybeasm", "initdcl", "@15", "notype_initdcl", "@16", "maybe_attribute", "attributes", "attribute", "attribute_list", --- 483,841 ---- 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 2, 2, 2, 1, 2, 3, 4, ! 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, ! 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, ! 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, ! 35, 36, 37, 38, 39, 40, 41, 42, 44, 47, ! 48, 52, 53, 54, 55, 61, 62, 63, 64, 68, ! 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, ! 79, 80, 81, 82 }; #if YYDEBUG ! /* YYPRHS[YYN] -- Index of the first RHS symbol of rule number YYN in ! YYRHS. */ ! static const unsigned short yyprhs[] = { ! 0, 0, 3, 4, 6, 7, 10, 11, 15, 17, ! 19, 25, 28, 32, 37, 42, 45, 48, 51, 53, ! 54, 55, 65, 70, 71, 72, 82, 87, 88, 89, ! 98, 102, 104, 106, 108, 110, 112, 114, 116, 118, ! 120, 122, 123, 125, 127, 131, 133, 136, 139, 142, ! 145, 148, 153, 156, 161, 164, 167, 169, 171, 173, ! 175, 180, 182, 186, 190, 194, 198, 202, 206, 210, ! 214, 218, 222, 226, 230, 231, 236, 237, 242, 243, ! 244, 252, 253, 259, 263, 267, 269, 271, 273, 275, ! 276, 284, 288, 292, 296, 300, 305, 312, 321, 328, ! 333, 337, 341, 344, 347, 349, 352, 353, 355, 358, ! 362, 364, 366, 369, 372, 377, 382, 385, 388, 392, ! 393, 395, 400, 405, 409, 413, 416, 419, 421, 424, ! 427, 430, 433, 436, 438, 441, 443, 446, 449, 452, ! 455, 458, 461, 463, 466, 469, 472, 475, 478, 481, ! 484, 487, 490, 493, 496, 499, 502, 505, 508, 511, 513, 516, 519, 522, 525, 528, 531, 534, 537, 540, 543, 546, 549, 552, 555, 558, 561, 564, 567, 570, 573, 576, 579, 582, 585, 588, 591, 594, 597, 600, 603, 606, 609, 612, 615, 618, 621, 624, 627, 630, ! 633, 636, 639, 642, 645, 647, 649, 651, 653, 655, ! 657, 659, 661, 663, 665, 667, 669, 671, 673, 675, ! 677, 679, 681, 683, 685, 687, 689, 691, 693, 695, ! 697, 699, 701, 703, 705, 707, 709, 711, 713, 715, ! 717, 719, 721, 723, 725, 727, 729, 731, 733, 735, ! 737, 739, 741, 743, 745, 747, 749, 751, 753, 755, ! 757, 758, 760, 762, 764, 766, 768, 770, 772, 774, ! 779, 784, 786, 791, 793, 798, 799, 804, 805, 812, ! 816, 817, 824, 828, 829, 831, 833, 836, 843, 845, ! 849, 850, 852, 857, 864, 869, 871, 873, 875, 877, ! 879, 880, 885, 887, 888, 891, 893, 897, 901, 904, ! 905, 910, 912, 913, 918, 920, 922, 924, 927, 930, ! 936, 940, 941, 942, 950, 951, 952, 960, 962, 964, ! 969, 973, 976, 980, 982, 984, 986, 990, 993, 995, ! 999, 1002, 1006, 1010, 1015, 1019, 1024, 1028, 1031, 1033, ! 1035, 1038, 1040, 1043, 1045, 1048, 1049, 1057, 1063, 1064, ! 1072, 1078, 1079, 1088, 1089, 1097, 1100, 1103, 1106, 1107, ! 1109, 1110, 1112, 1114, 1117, 1118, 1122, 1125, 1129, 1134, ! 1138, 1140, 1142, 1145, 1147, 1152, 1154, 1159, 1164, 1171, ! 1177, 1182, 1189, 1195, 1197, 1201, 1203, 1205, 1209, 1210, ! 1214, 1215, 1217, 1218, 1220, 1223, 1225, 1227, 1229, 1233, ! 1236, 1240, 1245, 1249, 1252, 1255, 1257, 1261, 1266, 1269, ! 1273, 1277, 1282, 1287, 1293, 1299, 1301, 1303, 1305, 1307, ! 1309, 1312, 1315, 1318, 1321, 1323, 1326, 1329, 1332, 1334, ! 1337, 1340, 1343, 1346, 1348, 1351, 1353, 1355, 1357, 1359, ! 1362, 1363, 1364, 1365, 1366, 1367, 1369, 1371, 1374, 1378, ! 1380, 1383, 1385, 1387, 1393, 1395, 1397, 1400, 1403, 1406, ! 1409, 1410, 1416, 1417, 1422, 1423, 1424, 1426, 1429, 1433, ! 1437, 1441, 1442, 1447, 1449, 1453, 1454, 1455, 1463, 1469, ! 1472, 1473, 1474, 1475, 1476, 1489, 1490, 1497, 1500, 1502, ! 1504, 1507, 1511, 1514, 1517, 1520, 1524, 1531, 1540, 1551, ! 1564, 1568, 1573, 1575, 1579, 1585, 1588, 1594, 1595, 1597, ! 1598, 1600, 1601, 1603, 1605, 1609, 1614, 1622, 1624, 1628, ! 1629, 1633, 1636, 1637, 1638, 1645, 1648, 1649, 1651, 1653, ! 1657, 1659, 1663, 1668, 1673, 1677, 1682, 1686, 1691, 1696, ! 1700, 1705, 1709, 1711, 1712, 1716, 1718, 1721, 1723, 1727, ! 1729, 1733 }; + + /* YYRHS -- A `-1'-separated list of the rules' RHS. */ static const short yyrhs[] = { ! 92, 0, -1, -1, 93, -1, -1, 94, 96, -1, ! -1, 93, 95, 96, -1, 98, -1, 97, -1, 27, ! 66, 107, 83, 84, -1, 290, 96, -1, 129, 163, ! 84, -1, 149, 129, 163, 84, -1, 148, 129, 162, ! 84, -1, 155, 84, -1, 1, 84, -1, 1, 85, ! -1, 84, -1, -1, -1, 148, 129, 191, 99, 124, ! 100, 251, 252, 240, -1, 148, 129, 191, 1, -1, ! -1, -1, 149, 129, 196, 101, 124, 102, 251, 252, ! 240, -1, 149, 129, 196, 1, -1, -1, -1, 129, ! 196, 103, 124, 104, 251, 252, 240, -1, 129, 196, ! 1, -1, 3, -1, 4, -1, 51, -1, 57, -1, ! 56, -1, 62, -1, 61, -1, 86, -1, 87, -1, ! 109, -1, -1, 109, -1, 115, -1, 109, 88, 115, ! -1, 121, -1, 58, 114, -1, 290, 114, -1, 106, ! 114, -1, 48, 105, -1, 111, 110, -1, 111, 66, ! 217, 83, -1, 112, 110, -1, 112, 66, 217, 83, ! -1, 33, 114, -1, 34, 114, -1, 11, -1, 29, ! -1, 28, -1, 110, -1, 66, 217, 83, 114, -1, ! 114, -1, 115, 56, 115, -1, 115, 57, 115, -1, ! 115, 58, 115, -1, 115, 59, 115, -1, 115, 60, ! 115, -1, 115, 55, 115, -1, 115, 54, 115, -1, ! 115, 53, 115, -1, 115, 52, 115, -1, 115, 51, ! 115, -1, 115, 49, 115, -1, 115, 50, 115, -1, ! -1, 115, 48, 116, 115, -1, -1, 115, 47, 117, ! 115, -1, -1, -1, 115, 45, 118, 107, 46, 119, ! 115, -1, -1, 115, 45, 120, 46, 115, -1, 115, ! 43, 115, -1, 115, 44, 115, -1, 3, -1, 8, ! -1, 123, -1, 42, -1, -1, 66, 217, 83, 89, ! 122, 177, 85, -1, 66, 107, 83, -1, 66, 1, ! 83, -1, 244, 242, 83, -1, 244, 1, 83, -1, ! 121, 66, 108, 83, -1, 35, 66, 115, 88, 217, ! 83, -1, 36, 66, 115, 88, 115, 88, 115, 83, ! -1, 37, 66, 217, 88, 217, 83, -1, 121, 67, ! 107, 90, -1, 121, 65, 105, -1, 121, 68, 105, ! -1, 121, 62, -1, 121, 61, -1, 9, -1, 123, ! 9, -1, -1, 126, -1, 126, 10, -1, 251, 252, ! 127, -1, 125, -1, 232, -1, 126, 125, -1, 125, ! 232, -1, 150, 129, 162, 84, -1, 151, 129, 163, ! 84, -1, 150, 84, -1, 151, 84, -1, 251, 252, ! 131, -1, -1, 169, -1, 148, 129, 162, 84, -1, ! 149, 129, 163, 84, -1, 148, 129, 185, -1, 149, ! 129, 188, -1, 155, 84, -1, 290, 131, -1, 7, ! -1, 132, 7, -1, 133, 7, -1, 132, 170, -1, ! 134, 7, -1, 135, 7, -1, 170, -1, 134, 170, ! -1, 157, -1, 136, 7, -1, 137, 7, -1, 136, ! 159, -1, 137, 159, -1, 132, 157, -1, 133, 157, ! -1, 158, -1, 136, 170, -1, 136, 160, -1, 137, ! 160, -1, 132, 158, -1, 133, 158, -1, 138, 7, ! -1, 139, 7, -1, 138, 159, -1, 139, 159, -1, ! 134, 157, -1, 135, 157, -1, 138, 170, -1, 138, ! 160, -1, 139, 160, -1, 134, 158, -1, 135, 158, ! -1, 5, -1, 140, 7, -1, 141, 7, -1, 132, ! 5, -1, 133, 5, -1, 140, 5, -1, 141, 5, ! -1, 140, 170, -1, 142, 7, -1, 143, 7, -1, ! 134, 5, -1, 135, 5, -1, 142, 5, -1, 143, ! 5, -1, 142, 170, -1, 144, 7, -1, 145, 7, ! -1, 144, 159, -1, 145, 159, -1, 140, 157, -1, ! 141, 157, -1, 136, 5, -1, 137, 5, -1, 144, ! 5, -1, 145, 5, -1, 144, 170, -1, 144, 160, ! -1, 145, 160, -1, 140, 158, -1, 141, 158, -1, ! 146, 7, -1, 147, 7, -1, 146, 159, -1, 147, ! 159, -1, 142, 157, -1, 143, 157, -1, 138, 5, ! -1, 139, 5, -1, 146, 5, -1, 147, 5, -1, ! 146, 170, -1, 146, 160, -1, 147, 160, -1, 142, ! 158, -1, 143, 158, -1, 136, -1, 137, -1, 138, ! -1, 139, -1, 144, -1, 145, -1, 146, -1, 147, ! -1, 132, -1, 133, -1, 134, -1, 135, -1, 140, ! -1, 141, -1, 142, -1, 143, -1, 136, -1, 137, ! -1, 144, -1, 145, -1, 132, -1, 133, -1, 140, ! -1, 141, -1, 136, -1, 137, -1, 138, -1, 139, ! -1, 132, -1, 133, -1, 134, -1, 135, -1, 136, ! -1, 137, -1, 138, -1, 139, -1, 132, -1, 133, ! -1, 134, -1, 135, -1, 132, -1, 133, -1, 134, ! -1, 135, -1, 136, -1, 137, -1, 138, -1, 139, ! -1, 140, -1, 141, -1, 142, -1, 143, -1, 144, ! -1, 145, -1, 146, -1, 147, -1, -1, 153, -1, ! 159, -1, 161, -1, 160, -1, 6, -1, 205, -1, ! 200, -1, 4, -1, 113, 66, 107, 83, -1, 113, ! 66, 217, 83, -1, 165, -1, 162, 88, 130, 165, ! -1, 167, -1, 163, 88, 130, 167, -1, -1, 27, ! 66, 123, 83, -1, -1, 191, 164, 169, 43, 166, ! 175, -1, 191, 164, 169, -1, -1, 196, 164, 169, ! 43, 168, 175, -1, 196, 164, 169, -1, -1, 170, ! -1, 171, -1, 170, 171, -1, 30, 66, 66, 172, ! 83, 83, -1, 173, -1, 172, 88, 173, -1, -1, ! 174, -1, 174, 66, 3, 83, -1, 174, 66, 3, ! 88, 109, 83, -1, 174, 66, 108, 83, -1, 105, ! -1, 5, -1, 6, -1, 7, -1, 115, -1, -1, ! 89, 176, 177, 85, -1, 1, -1, -1, 178, 206, ! -1, 179, -1, 178, 88, 179, -1, 183, 43, 181, ! -1, 184, 181, -1, -1, 105, 46, 180, 181, -1, ! 181, -1, -1, 89, 182, 177, 85, -1, 115, -1, ! 1, -1, 184, -1, 183, 184, -1, 65, 105, -1, ! 67, 115, 10, 115, 90, -1, 67, 115, 90, -1, ! -1, -1, 191, 186, 124, 187, 251, 252, 245, -1, ! -1, -1, 196, 189, 124, 190, 251, 252, 245, -1, ! 192, -1, 196, -1, 66, 169, 192, 83, -1, 192, ! 66, 285, -1, 192, 225, -1, 58, 156, 192, -1, ! 4, -1, 194, -1, 195, -1, 194, 66, 285, -1, ! 194, 225, -1, 4, -1, 195, 66, 285, -1, 195, ! 225, -1, 58, 156, 194, -1, 58, 156, 195, -1, ! 66, 169, 195, 83, -1, 196, 66, 285, -1, 66, ! 169, 196, 83, -1, 58, 156, 196, -1, 196, 225, ! -1, 3, -1, 13, -1, 13, 170, -1, 14, -1, ! 14, 170, -1, 12, -1, 12, 170, -1, -1, 197, ! 105, 89, 201, 208, 85, 169, -1, 197, 89, 208, ! 85, 169, -1, -1, 198, 105, 89, 202, 208, 85, ! 169, -1, 198, 89, 208, 85, 169, -1, -1, 199, ! 105, 89, 203, 215, 207, 85, 169, -1, -1, 199, ! 89, 204, 215, 207, 85, 169, -1, 197, 105, -1, ! 198, 105, -1, 199, 105, -1, -1, 88, -1, -1, ! 88, -1, 209, -1, 209, 210, -1, -1, 209, 210, ! 84, -1, 209, 84, -1, 152, 129, 211, -1, 152, ! 129, 251, 252, -1, 153, 129, 212, -1, 153, -1, ! 1, -1, 290, 210, -1, 213, -1, 211, 88, 130, ! 213, -1, 214, -1, 212, 88, 130, 214, -1, 251, ! 252, 191, 169, -1, 251, 252, 191, 46, 115, 169, ! -1, 251, 252, 46, 115, 169, -1, 251, 252, 196, ! 169, -1, 251, 252, 196, 46, 115, 169, -1, 251, ! 252, 46, 115, 169, -1, 216, -1, 215, 88, 216, ! -1, 1, -1, 105, -1, 105, 43, 115, -1, -1, ! 154, 218, 219, -1, -1, 221, -1, -1, 221, -1, ! 222, 170, -1, 223, -1, 222, -1, 224, -1, 58, ! 156, 222, -1, 58, 156, -1, 58, 156, 223, -1, ! 66, 169, 221, 83, -1, 224, 66, 275, -1, 224, ! 225, -1, 66, 275, -1, 225, -1, 67, 107, 90, ! -1, 67, 154, 107, 90, -1, 67, 90, -1, 67, ! 154, 90, -1, 67, 58, 90, -1, 67, 154, 58, ! 90, -1, 67, 5, 107, 90, -1, 67, 5, 154, ! 107, 90, -1, 67, 154, 5, 107, 90, -1, 227, ! -1, 228, -1, 229, -1, 230, -1, 255, -1, 227, ! 255, -1, 228, 255, -1, 229, 255, -1, 230, 255, ! -1, 128, -1, 227, 128, -1, 228, 128, -1, 230, ! 128, -1, 256, -1, 227, 256, -1, 228, 256, -1, ! 229, 256, -1, 230, 256, -1, 232, -1, 231, 232, ! -1, 227, -1, 228, -1, 229, -1, 230, -1, 1, ! 84, -1, -1, -1, -1, -1, -1, 238, -1, 239, ! -1, 238, 239, -1, 32, 289, 84, -1, 245, -1, ! 1, 245, -1, 89, -1, 85, -1, 233, 237, 243, ! 85, 234, -1, 226, -1, 1, -1, 66, 89, -1, ! 241, 242, -1, 247, 254, -1, 247, 1, -1, -1, ! 15, 248, 66, 107, 83, -1, -1, 18, 250, 254, ! 17, -1, -1, -1, 255, -1, 256, 253, -1, 235, ! 253, 236, -1, 251, 252, 267, -1, 251, 252, 268, ! -1, -1, 246, 16, 258, 254, -1, 246, -1, 246, ! 16, 1, -1, -1, -1, 17, 259, 66, 107, 83, ! 260, 254, -1, 249, 66, 107, 83, 84, -1, 249, ! 1, -1, -1, -1, -1, -1, 19, 261, 66, 266, ! 262, 270, 84, 263, 270, 83, 264, 254, -1, -1, ! 20, 66, 107, 83, 265, 254, -1, 270, 84, -1, ! 131, -1, 245, -1, 107, 84, -1, 235, 257, 236, ! -1, 23, 84, -1, 24, 84, -1, 25, 84, -1, ! 25, 107, 84, -1, 27, 269, 66, 107, 83, 84, ! -1, 27, 269, 66, 107, 46, 271, 83, 84, -1, ! 27, 269, 66, 107, 46, 271, 46, 271, 83, 84, ! -1, 27, 269, 66, 107, 46, 271, 46, 271, 46, ! 274, 83, 84, -1, 26, 105, 84, -1, 26, 58, ! 107, 84, -1, 84, -1, 21, 115, 46, -1, 21, ! 115, 10, 115, 46, -1, 22, 46, -1, 105, 251, ! 252, 46, 169, -1, -1, 7, -1, -1, 107, -1, ! -1, 272, -1, 273, -1, 272, 88, 273, -1, 9, ! 66, 107, 83, -1, 67, 105, 90, 9, 66, 107, ! 83, -1, 123, -1, 274, 88, 123, -1, -1, 169, ! 276, 277, -1, 280, 83, -1, -1, -1, 281, 84, ! 278, 169, 279, 277, -1, 1, 83, -1, -1, 10, ! -1, 281, -1, 281, 88, 10, -1, 283, -1, 281, ! 88, 282, -1, 148, 129, 193, 169, -1, 148, 129, ! 196, 169, -1, 148, 129, 220, -1, 149, 129, 196, ! 169, -1, 149, 129, 220, -1, 150, 284, 193, 169, ! -1, 150, 284, 196, 169, -1, 150, 284, 220, -1, ! 151, 284, 196, 169, -1, 151, 284, 220, -1, 129, ! -1, -1, 169, 286, 287, -1, 277, -1, 288, 83, ! -1, 3, -1, 288, 88, 3, -1, 105, -1, 289, ! 88, 105, -1, 31, -1 }; ! /* YYRLINE[YYN] -- source line where rule number YYN was defined. */ ! static const unsigned short yyrline[] = { ! 0, 287, 287, 291, 307, 307, 308, 308, 312, 313, ! 314, 322, 327, 334, 336, 338, 340, 341, 342, 349, ! 354, 348, 360, 363, 368, 362, 374, 377, 382, 376, ! 388, 393, 394, 397, 399, 401, 406, 408, 410, 412, ! 416, 422, 423, 427, 429, 434, 435, 438, 441, 445, ! 462, 468, 471, 474, 477, 479, 484, 488, 492, 496, ! 497, 502, 503, 505, 507, 509, 511, 513, 515, 517, ! 519, 521, 523, 525, 528, 527, 534, 533, 540, 543, ! 539, 549, 548, 558, 565, 576, 582, 583, 585, 588, ! 587, 600, 605, 607, 623, 630, 632, 635, 645, 655, ! 657, 661, 667, 669, 675, 676, 693, 695, 696, 707, ! 712, 713, 714, 715, 723, 725, 727, 730, 739, 748, ! 758, 763, 765, 767, 769, 771, 773, 830, 833, 836, ! 842, 848, 851, 857, 860, 866, 869, 872, 875, 878, ! 881, 884, 890, 893, 896, 899, 902, 905, 911, 914, ! 917, 920, 923, 926, 932, 935, 938, 941, 944, 950, ! 953, 956, 959, 965, 971, 977, 986, 992, 995, 998, ! 1004, 1010, 1016, 1025, 1031, 1034, 1037, 1040, 1043, 1046, ! 1049, 1055, 1061, 1067, 1076, 1079, 1082, 1085, 1088, 1094, ! 1097, 1100, 1103, 1106, 1109, 1112, 1118, 1124, 1130, 1139, ! 1142, 1145, 1148, 1151, 1158, 1159, 1160, 1161, 1162, 1163, ! 1164, 1165, 1169, 1170, 1171, 1172, 1173, 1174, 1175, 1176, ! 1180, 1181, 1182, 1183, 1187, 1188, 1189, 1190, 1194, 1195, ! 1196, 1197, 1201, 1202, 1203, 1204, 1208, 1209, 1210, 1211, ! 1212, 1213, 1214, 1215, 1219, 1220, 1221, 1222, 1223, 1224, ! 1225, 1226, 1227, 1228, 1229, 1230, 1231, 1232, 1233, 1234, ! 1240, 1241, 1267, 1268, 1272, 1276, 1278, 1282, 1286, 1290, ! 1292, 1299, 1300, 1304, 1305, 1310, 1311, 1319, 1318, 1326, ! 1335, 1334, 1342, 1351, 1352, 1357, 1359, 1364, 1369, 1371, ! 1377, 1378, 1380, 1382, 1384, 1392, 1393, 1394, 1395, 1401, ! 1403, 1402, 1406, 1413, 1415, 1419, 1420, 1426, 1429, 1433, ! 1432, 1438, 1443, 1442, 1446, 1448, 1452, 1453, 1457, 1462, ! 1466, 1472, 1484, 1471, 1502, 1514, 1501, 1534, 1535, 1541, ! 1543, 1548, 1550, 1552, 1560, 1561, 1565, 1570, 1572, 1576, ! 1581, 1583, 1585, 1587, 1595, 1600, 1602, 1604, 1606, 1610, ! 1612, 1617, 1619, 1624, 1626, 1638, 1637, 1643, 1648, 1647, ! 1651, 1656, 1655, 1661, 1660, 1668, 1670, 1672, 1680, 1682, ! 1685, 1687, 1693, 1695, 1701, 1702, 1704, 1710, 1713, 1723, ! 1726, 1731, 1733, 1739, 1740, 1745, 1746, 1751, 1754, 1758, ! 1764, 1767, 1771, 1782, 1783, 1788, 1794, 1796, 1802, 1801, ! 1810, 1811, 1816, 1819, 1823, 1830, 1831, 1835, 1836, 1841, ! 1843, 1848, 1850, 1852, 1854, 1856, 1863, 1865, 1867, 1869, ! 1871, 1873, 1875, 1879, 1883, 1896, 1897, 1898, 1902, 1906, ! 1907, 1908, 1909, 1910, 1914, 1915, 1918, 1919, 1923, 1924, ! 1925, 1926, 1927, 1931, 1932, 1936, 1937, 1938, 1939, 1942, ! 1946, 1953, 1958, 1974, 1988, 1990, 1996, 1997, 2001, 2015, ! 2017, 2020, 2024, 2026, 2034, 2035, 2039, 2056, 2064, 2069, ! 2082, 2081, 2096, 2095, 2115, 2121, 2127, 2128, 2133, 2139, ! 2153, 2163, 2162, 2170, 2182, 2193, 2196, 2192, 2202, 2205, ! 2208, 2212, 2215, 2218, 2207, 2222, 2221, 2229, 2231, 2237, ! 2239, 2242, 2246, 2249, 2252, 2255, 2258, 2262, 2266, 2271, ! 2275, 2287, 2293, 2301, 2304, 2307, 2310, 2327, 2329, 2335, ! 2336, 2342, 2343, 2347, 2348, 2353, 2355, 2360, 2362, 2373, ! 2372, 2383, 2385, 2393, 2384, 2397, 2404, 2405, 2415, 2417, ! 2422, 2424, 2431, 2436, 2441, 2444, 2450, 2458, 2463, 2468, ! 2471, 2477, 2483, 2493, 2492, 2503, 2504, 2522, 2524, 2530, ! 2532, 2537 }; #endif ! #if YYDEBUG || YYERROR_VERBOSE ! /* YYTNME[SYMBOL-NUM] -- String name of the symbol SYMBOL-NUM. ! First, the terminals, then, starting at YYNTOKENS, nonterminals. */ static const char *const yytname[] = { ! "$end", "error", "$undefined", "IDENTIFIER", "TYPENAME", "SCSPEC", "TYPESPEC", "TYPE_QUAL", "CONSTANT", "STRING", "ELLIPSIS", "SIZEOF", "ENUM", "STRUCT", "UNION", "IF", "ELSE", "WHILE", "DO", "FOR", "SWITCH", "CASE", "DEFAULT", "BREAK", "CONTINUE", "RETURN", "GOTO", "ASM_KEYWORD", "TYPEOF", "ALIGNOF", "ATTRIBUTE", "EXTENSION", "LABEL", "REALPART", "IMAGPART", "VA_ARG", "CHOOSE_EXPR", "TYPES_COMPATIBLE_P", "PTR_VALUE", ! "PTR_BASE", "PTR_EXTENT", "STRING_FUNC_NAME", "VAR_FUNC_NAME", "'='", ! "ASSIGN", "'?'", "':'", "OROR", "ANDAND", "'|'", "'^'", "'&'", ! "EQCOMPARE", "ARITHCOMPARE", "RSHIFT", "LSHIFT", "'+'", "'-'", "'*'", ! "'/'", "'%'", "MINUSMINUS", "PLUSPLUS", "UNARY", "HYPERUNARY", "'.'", ! "'('", "'['", "POINTSAT", "INTERFACE", "IMPLEMENTATION", "END", ! "SELECTOR", "DEFS", "ENCODE", "CLASSNAME", "PUBLIC", "PRIVATE", ! "PROTECTED", "PROTOCOL", "OBJECTNAME", "CLASS", "ALIAS", "')'", "';'", ! "'}'", "'~'", "'!'", "','", "'{'", "']'", "$accept", "program", ! "extdefs", "@1", "@2", "extdef", "datadef", "fndef", "@3", "@4", "@5", ! "@6", "@7", "@8", "identifier", "unop", "expr", "exprlist", ! "nonnull_exprlist", "unary_expr", "sizeof", "alignof", "typeof", ! "cast_expr", "expr_no_commas", "@9", "@10", "@11", "@12", "@13", ! "primary", "@14", "string", "old_style_parm_decls", "lineno_datadecl", ! "datadecls", "datadecl", "lineno_decl", "setspecs", "maybe_resetattrs", ! "decl", "declspecs_nosc_nots_nosa_noea", "declspecs_nosc_nots_nosa_ea", ! "declspecs_nosc_nots_sa_noea", "declspecs_nosc_nots_sa_ea", ! "declspecs_nosc_ts_nosa_noea", "declspecs_nosc_ts_nosa_ea", ! "declspecs_nosc_ts_sa_noea", "declspecs_nosc_ts_sa_ea", ! "declspecs_sc_nots_nosa_noea", "declspecs_sc_nots_nosa_ea", ! "declspecs_sc_nots_sa_noea", "declspecs_sc_nots_sa_ea", ! "declspecs_sc_ts_nosa_noea", "declspecs_sc_ts_nosa_ea", ! "declspecs_sc_ts_sa_noea", "declspecs_sc_ts_sa_ea", "declspecs_ts", ! "declspecs_nots", "declspecs_ts_nosa", "declspecs_nots_nosa", ! "declspecs_nosc_ts", "declspecs_nosc_nots", "declspecs_nosc", ! "declspecs", "maybe_type_quals_attrs", "typespec_nonattr", ! "typespec_attr", "typespec_reserved_nonattr", "typespec_reserved_attr", "typespec_nonreserved_nonattr", "initdecls", "notype_initdecls", "maybeasm", "initdcl", "@15", "notype_initdcl", "@16", "maybe_attribute", "attributes", "attribute", "attribute_list", *************** static const char *const yytname[] = *** 621,1770 **** }; #endif ! /* YYR1[YYN] -- Symbol number of symbol that rule YYN derives. */ ! static const short yyr1[] = { ! 0, 91, 91, 93, 92, 94, 92, 95, 95, 95, ! 95, 96, 96, 96, 96, 96, 96, 96, 98, 99, ! 97, 97, 100, 101, 97, 97, 102, 103, 97, 97, ! 104, 104, 105, 105, 105, 105, 105, 105, 105, 106, ! 107, 107, 108, 108, 109, 109, 109, 109, 109, 109, ! 109, 109, 109, 109, 109, 110, 111, 112, 113, 113, ! 114, 114, 114, 114, 114, 114, 114, 114, 114, 114, ! 114, 114, 114, 115, 114, 116, 114, 117, 118, 114, ! 119, 114, 114, 114, 120, 120, 120, 120, 121, 120, ! 120, 120, 120, 120, 120, 120, 120, 120, 120, 120, ! 120, 120, 120, 122, 122, 123, 123, 123, 124, 125, ! 125, 125, 125, 126, 126, 126, 126, 127, 128, 129, ! 130, 130, 130, 130, 130, 130, 131, 131, 131, 132, ! 133, 133, 134, 134, 135, 135, 135, 135, 135, 135, ! 135, 136, 136, 136, 136, 136, 136, 137, 137, 137, ! 137, 137, 137, 138, 138, 138, 138, 138, 139, 139, ! 139, 139, 139, 139, 139, 140, 141, 141, 141, 141, ! 141, 141, 142, 143, 143, 143, 143, 143, 143, 143, ! 143, 143, 143, 144, 144, 144, 144, 144, 145, 145, ! 145, 145, 145, 145, 145, 145, 145, 145, 146, 146, ! 146, 146, 146, 147, 147, 147, 147, 147, 147, 147, ! 147, 148, 148, 148, 148, 148, 148, 148, 148, 149, ! 149, 149, 149, 150, 150, 150, 150, 151, 151, 151, ! 151, 152, 152, 152, 152, 153, 153, 153, 153, 153, ! 153, 153, 153, 154, 154, 154, 154, 154, 154, 154, ! 154, 154, 154, 154, 154, 154, 154, 154, 154, 155, ! 155, 156, 156, 157, 158, 158, 159, 160, 160, 160, ! 161, 161, 162, 162, 163, 163, 165, 164, 164, 167, ! 166, 166, 168, 168, 169, 169, 170, 171, 171, 172, ! 172, 172, 172, 172, 173, 173, 173, 173, 174, 175, ! 174, 174, 176, 176, 177, 177, 178, 178, 179, 178, ! 178, 181, 180, 180, 180, 182, 182, 183, 183, 183, ! 185, 186, 184, 188, 189, 187, 190, 190, 191, 191, ! 191, 191, 191, 192, 192, 193, 193, 193, 194, 194, ! 194, 194, 194, 195, 195, 195, 195, 195, 196, 196, ! 197, 197, 198, 198, 200, 199, 199, 201, 199, 199, ! 202, 199, 203, 199, 204, 204, 204, 205, 205, 206, ! 206, 207, 207, 208, 208, 208, 209, 209, 209, 209, ! 209, 209, 210, 210, 211, 211, 212, 212, 212, 213, ! 213, 213, 214, 214, 214, 215, 215, 217, 216, 218, ! 218, 219, 219, 219, 220, 220, 221, 221, 222, 222, ! 223, 223, 223, 223, 223, 224, 224, 224, 224, 224, ! 224, 224, 224, 224, 225, 225, 225, 225, 226, 226, ! 226, 226, 226, 227, 227, 227, 227, 228, 228, 228, ! 228, 228, 229, 229, 230, 230, 230, 230, 231, 232, ! 233, 234, 235, 236, 236, 237, 237, 238, 239, 239, ! 240, 241, 241, 242, 242, 243, 244, 245, 245, 247, ! 246, 249, 248, 250, 251, 252, 252, 253, 254, 255, ! 257, 256, 256, 256, 258, 259, 256, 256, 256, 260, ! 261, 262, 263, 256, 264, 256, 265, 265, 266, 266, ! 266, 266, 266, 266, 266, 266, 266, 266, 266, 266, ! 266, 266, 267, 267, 267, 267, 268, 268, 269, 269, ! 270, 270, 271, 271, 272, 272, 273, 273, 275, 274, ! 276, 277, 278, 276, 276, 279, 279, 279, 279, 280, ! 280, 281, 281, 281, 281, 281, 282, 282, 282, 282, ! 282, 283, 285, 284, 286, 286, 287, 287, 288, 288, ! 289 }; ! /* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN. */ ! static const short yyr2[] = { ! 0, 0, 1, 0, 2, 0, 3, 1, 1, 5, ! 2, 3, 4, 4, 2, 2, 2, 1, 0, 0, ! 9, 4, 0, 0, 9, 4, 0, 0, 8, 3, ! 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, ! 0, 1, 1, 3, 1, 2, 2, 2, 2, 2, ! 4, 2, 4, 2, 2, 1, 1, 1, 1, 4, ! 1, 3, 3, 3, 3, 3, 3, 3, 3, 3, ! 3, 3, 3, 0, 4, 0, 4, 0, 0, 7, ! 0, 5, 3, 3, 1, 1, 1, 1, 0, 7, ! 3, 3, 3, 3, 4, 6, 8, 6, 4, 3, ! 3, 2, 2, 1, 2, 0, 1, 2, 3, 1, ! 1, 2, 2, 4, 4, 2, 2, 3, 0, 1, ! 4, 4, 3, 3, 2, 2, 1, 2, 2, 2, ! 2, 2, 1, 2, 1, 2, 2, 2, 2, 2, ! 2, 1, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 2, 2, 2, 2, 2, 1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, ! 1, 1, 1, 1, 1, 1, 1, 1, 1, 0, ! 1, 1, 1, 1, 1, 1, 1, 1, 4, 4, ! 1, 4, 1, 4, 0, 4, 0, 6, 3, 0, ! 6, 3, 0, 1, 1, 2, 6, 1, 3, 0, ! 1, 4, 6, 4, 1, 1, 1, 1, 1, 0, ! 4, 1, 0, 2, 1, 3, 3, 2, 0, 4, ! 1, 0, 4, 1, 1, 1, 2, 2, 5, 3, ! 0, 0, 7, 0, 0, 7, 1, 1, 4, 3, ! 2, 3, 1, 1, 1, 3, 2, 1, 3, 2, ! 3, 3, 4, 3, 4, 3, 2, 1, 1, 2, ! 1, 2, 1, 2, 0, 7, 5, 0, 7, 5, ! 0, 8, 0, 7, 2, 2, 2, 0, 1, 0, ! 1, 1, 2, 0, 3, 2, 3, 4, 3, 1, ! 1, 2, 1, 4, 1, 4, 4, 6, 5, 4, ! 6, 5, 1, 3, 1, 1, 3, 0, 3, 0, ! 1, 0, 1, 2, 1, 1, 1, 3, 2, 3, ! 4, 3, 2, 2, 1, 3, 4, 2, 3, 3, ! 4, 4, 5, 5, 1, 1, 1, 1, 1, 2, ! 2, 2, 2, 1, 2, 2, 2, 1, 2, 2, ! 2, 2, 1, 2, 1, 1, 1, 1, 2, 0, ! 0, 0, 0, 0, 1, 1, 2, 3, 1, 2, ! 1, 1, 5, 1, 1, 2, 2, 2, 2, 0, ! 5, 0, 4, 0, 0, 1, 2, 3, 3, 3, ! 0, 4, 1, 3, 0, 0, 7, 5, 2, 0, ! 0, 0, 0, 12, 0, 6, 2, 1, 1, 2, ! 3, 2, 2, 2, 3, 6, 8, 10, 12, 3, ! 4, 1, 3, 5, 2, 5, 0, 1, 0, 1, ! 0, 1, 1, 3, 4, 7, 1, 3, 0, 3, ! 2, 0, 0, 6, 2, 0, 1, 1, 3, 1, ! 3, 4, 4, 3, 4, 3, 4, 4, 3, 4, ! 3, 1, 0, 3, 1, 2, 1, 3, 1, 3, ! 1 }; ! /* YYDEFACT[S] -- default rule to reduce with in state S when YYTABLE ! doesn't specify something else to do. Zero means the default is an ! error. */ ! static const short yydefact[] = { ! 3, 5, 0, 0, 0, 267, 158, 264, 126, 352, ! 348, 350, 0, 57, 0, 560, 17, 4, 8, 7, ! 0, 0, 211, 212, 213, 214, 203, 204, 205, 206, ! 215, 216, 217, 218, 207, 208, 209, 210, 118, 118, ! 0, 134, 141, 261, 263, 262, 132, 284, 0, 0, ! 0, 266, 265, 0, 6, 15, 16, 353, 349, 351, ! 0, 0, 0, 347, 259, 282, 0, 272, 0, 161, ! 127, 139, 145, 129, 162, 128, 140, 146, 168, 130, ! 151, 156, 133, 169, 131, 152, 157, 179, 135, 137, ! 143, 142, 180, 136, 138, 144, 194, 147, 149, 154, ! 153, 195, 148, 150, 155, 163, 159, 177, 186, 165, ! 164, 160, 178, 187, 170, 166, 192, 201, 172, 171, ! 167, 193, 202, 181, 173, 175, 184, 183, 182, 174, ! 176, 185, 196, 188, 190, 199, 198, 197, 189, 191, ! 200, 0, 0, 14, 285, 30, 31, 373, 364, 373, ! 365, 362, 366, 10, 84, 85, 103, 55, 56, 0, ! 0, 0, 0, 0, 87, 0, 32, 34, 33, 0, ! 35, 36, 0, 37, 38, 0, 0, 39, 58, 0, ! 0, 60, 42, 44, 86, 0, 0, 289, 0, 239, ! 240, 241, 242, 235, 236, 237, 238, 397, 0, 231, ! 232, 233, 234, 260, 0, 0, 283, 11, 282, 29, ! 0, 282, 0, 0, 282, 346, 332, 259, 282, 0, ! 270, 0, 326, 327, 0, 0, 0, 0, 354, 0, ! 357, 0, 360, 53, 54, 0, 0, 0, 48, 45, ! 0, 465, 0, 0, 47, 0, 0, 0, 49, 0, ! 51, 0, 0, 77, 75, 73, 0, 0, 0, 0, ! 0, 0, 0, 0, 0, 0, 0, 0, 101, 102, ! 0, 0, 40, 0, 104, 0, 461, 453, 0, 46, ! 295, 296, 297, 294, 0, 287, 290, 268, 399, 269, ! 345, 0, 0, 119, 0, 552, 343, 0, 0, 417, ! 0, 0, 0, 27, 0, 473, 110, 474, 281, 0, ! 0, 13, 282, 21, 0, 282, 282, 330, 12, 25, ! 0, 282, 380, 375, 231, 232, 233, 234, 227, 228, ! 229, 230, 118, 118, 372, 0, 373, 282, 373, 394, ! 395, 369, 392, 0, 0, 0, 0, 91, 90, 0, ! 9, 43, 0, 0, 83, 82, 0, 0, 0, 0, ! 71, 72, 70, 69, 68, 66, 67, 61, 62, 63, ! 64, 65, 100, 99, 0, 41, 0, 93, 0, 0, ! 454, 455, 92, 0, 289, 40, 259, 282, 398, 400, ! 405, 404, 406, 414, 344, 273, 274, 0, 0, 0, ! 0, 419, 415, 0, 0, 418, 0, 448, 473, 112, ! 107, 111, 0, 279, 331, 0, 0, 19, 278, 329, ! 23, 356, 473, 473, 374, 381, 0, 359, 0, 0, ! 370, 0, 369, 0, 0, 0, 88, 59, 50, 52, ! 0, 0, 76, 74, 94, 98, 558, 0, 464, 433, ! 463, 473, 473, 473, 473, 0, 442, 0, 474, 428, ! 437, 456, 286, 288, 84, 0, 408, 528, 413, 282, ! 412, 275, 0, 556, 536, 223, 224, 219, 220, 225, ! 226, 221, 222, 118, 118, 554, 0, 537, 539, 553, ! 0, 421, 0, 0, 420, 416, 474, 108, 118, 118, ! 0, 328, 271, 274, 473, 276, 473, 376, 382, 474, ! 378, 384, 474, 282, 282, 396, 393, 282, 0, 0, ! 0, 0, 0, 78, 81, 457, 0, 434, 429, 438, ! 435, 430, 439, 474, 431, 440, 436, 432, 441, 443, ! 450, 451, 291, 0, 293, 407, 409, 0, 0, 528, ! 411, 534, 551, 401, 401, 530, 531, 0, 555, 0, ! 422, 423, 0, 115, 0, 116, 0, 301, 299, 298, ! 280, 474, 0, 474, 282, 377, 282, 0, 355, 358, ! 363, 282, 95, 0, 97, 314, 84, 0, 0, 311, ! 0, 313, 0, 367, 304, 310, 0, 0, 0, 559, ! 451, 462, 267, 0, 0, 0, 0, 0, 0, 516, ! 511, 460, 473, 0, 117, 118, 118, 0, 0, 449, ! 498, 478, 479, 0, 0, 410, 529, 337, 259, 282, ! 282, 333, 334, 282, 548, 402, 405, 259, 282, 282, ! 550, 282, 538, 211, 212, 213, 214, 203, 204, 205, ! 206, 215, 216, 217, 218, 207, 208, 209, 210, 118, ! 118, 540, 557, 0, 28, 458, 0, 0, 0, 0, ! 277, 0, 473, 0, 282, 473, 0, 282, 361, 0, ! 317, 0, 0, 308, 89, 0, 303, 0, 316, 307, ! 79, 0, 514, 501, 502, 503, 0, 0, 0, 517, ! 0, 474, 499, 0, 0, 124, 469, 484, 471, 489, ! 0, 482, 0, 0, 452, 466, 125, 292, 408, 528, ! 546, 282, 336, 282, 339, 547, 403, 408, 528, 549, ! 532, 401, 401, 459, 113, 114, 0, 20, 24, 383, ! 474, 282, 0, 386, 385, 282, 0, 389, 96, 0, ! 319, 0, 0, 305, 306, 0, 512, 504, 0, 509, ! 0, 0, 0, 122, 320, 0, 123, 323, 0, 0, ! 451, 0, 0, 0, 468, 473, 467, 488, 0, 500, ! 340, 341, 0, 335, 338, 0, 282, 282, 543, 282, ! 545, 300, 0, 388, 282, 391, 282, 0, 312, 309, ! 0, 510, 0, 282, 120, 0, 121, 0, 0, 0, ! 0, 518, 0, 483, 451, 452, 475, 473, 0, 342, ! 533, 541, 542, 544, 387, 390, 318, 513, 520, 0, ! 515, 321, 324, 0, 0, 472, 519, 497, 490, 0, ! 494, 481, 477, 476, 0, 0, 0, 0, 521, 522, ! 505, 473, 473, 470, 485, 518, 496, 451, 487, 0, ! 0, 520, 0, 0, 474, 474, 451, 0, 495, 0, ! 0, 0, 506, 523, 0, 0, 486, 491, 524, 0, ! 0, 0, 322, 325, 518, 0, 526, 0, 507, 0, ! 0, 0, 0, 492, 525, 508, 527, 451, 493, 0, ! 0, 0 }; static const short yydefgoto[] = { ! 899, 1, 2, 3, 17, 18, 19, 314, 504, 320, ! 506, 213, 408, 590, 175, 242, 374, 177, 178, 179, ! 180, 20, 181, 182, 359, 358, 356, 598, 357, 183, ! 522, 184, 303, 304, 305, 497, 449, 21, 292, 614, ! 189, 190, 191, 192, 193, 194, 195, 196, 30, 31, ! 32, 33, 34, 35, 36, 37, 38, 39, 483, 484, ! 332, 203, 197, 40, 204, 41, 42, 43, 44, 45, ! 219, 66, 214, 220, 572, 67, 500, 293, 206, 47, ! 284, 285, 286, 570, 668, 592, 593, 594, 752, 595, ! 682, 596, 597, 763, 805, 851, 766, 807, 852, 503, ! 222, 630, 631, 632, 223, 48, 49, 50, 51, 336, ! 338, 343, 231, 52, 686, 431, 226, 227, 334, 507, ! 510, 508, 511, 341, 342, 198, 288, 388, 634, 635, ! 390, 391, 392, 215, 450, 451, 452, 453, 454, 455, ! 306, 277, 601, 775, 779, 379, 380, 381, 664, 619, ! 278, 457, 185, 665, 711, 712, 768, 713, 770, 307, ! 412, 815, 776, 816, 817, 714, 814, 769, 866, 771, ! 855, 884, 897, 857, 838, 621, 622, 700, 839, 847, ! 848, 849, 887, 468, 548, 485, 641, 785, 486, 487, ! 661, 488, 553, 296, 398, 489, 490, 447, 186 }; static const short yypact[] = { ! 57, 92, 986, 986, 379,-32768,-32768,-32768,-32768, 109, ! 109, 109, 105,-32768, 123,-32768,-32768,-32768,-32768,-32768, ! 165, 316, 509, 1138, 1295, 1166, 311, 1055, 833, 1206, ! 1326, 1453, 1379, 1540, 1605, 1298, 1625, 1591,-32768,-32768, ! 63,-32768,-32768,-32768,-32768,-32768, 109,-32768, 71, 80, ! 125,-32768,-32768, 986,-32768,-32768,-32768, 109, 109, 109, ! 2684, 176, 2602,-32768, 129, 109, 203,-32768, 896,-32768, ! -32768,-32768,-32768, 109,-32768,-32768,-32768,-32768,-32768,-32768, ! -32768,-32768, 109,-32768,-32768,-32768,-32768,-32768,-32768,-32768, ! -32768, 109,-32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, ! 109,-32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, 109, ! -32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, 109,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768,-32768, 109,-32768,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768, 109,-32768,-32768,-32768, ! -32768, 206, 316,-32768,-32768,-32768,-32768,-32768, 42,-32768, ! 162,-32768, 189,-32768,-32768,-32768,-32768,-32768,-32768, 2684, ! 2684, 230, 238, 246,-32768, 483,-32768,-32768,-32768, 2684, ! -32768,-32768, 1797,-32768,-32768, 2684, 254, 270,-32768, 2725, ! 2766,-32768, 3099, 1053, 355, 1471, 2684, 908, 284, 2385, ! 3084, 2553, 3095, 690, 485, 732, 605,-32768, 295, 242, ! 373, 279, 409,-32768, 316, 316, 109,-32768, 109,-32768, ! 323, 109, 2131, 461, 109,-32768,-32768, 129, 109, 293, ! -32768, 1080, 504, 513, 304, 1045, 349, 489,-32768, 358, ! -32768, 542,-32768,-32768,-32768, 2684, 2684, 3026,-32768,-32768, ! 363,-32768, 369, 371,-32768, 387, 2684, 1797,-32768, 1797, ! -32768, 2684, 2684, 464,-32768,-32768, 2684, 2684, 2684, 2684, ! 2684, 2684, 2684, 2684, 2684, 2684, 2684, 2684,-32768,-32768, ! 483, 483, 2684, 2684,-32768, 405,-32768, 486, 424,-32768, ! -32768,-32768,-32768,-32768, 201,-32768, 457,-32768, 390,-32768, ! 513, 186, 316,-32768, 529,-32768,-32768, 2602, 2234,-32768, ! 466, 2172, 478,-32768, 356, 114,-32768,-32768, 532, 206, ! 206,-32768, 109,-32768, 461, 109, 109,-32768,-32768,-32768, ! 461, 109,-32768,-32768, 2385, 3084, 2553, 3095, 690, 485, ! 732, 605,-32768, 499, 502, 1413,-32768, 109,-32768,-32768, ! 546, 506,-32768, 542, 2872, 2890, 508,-32768,-32768, 2475, ! -32768, 3099, 517, 525, 3099, 3099, 2684, 568, 2684, 2684, ! 2437, 3062, 1208, 2564, 983, 879, 879, 288, 288,-32768, ! -32768,-32768,-32768,-32768, 555, 270, 551,-32768, 483, 1558, ! 486,-32768,-32768, 562, 908, 2807, 129, 109,-32768,-32768, ! -32768,-32768, 535,-32768,-32768,-32768, 99, 33, 1230, 557, ! 2684,-32768,-32768, 2684, 2275,-32768, 559,-32768,-32768,-32768, ! -32768,-32768, 2454,-32768, 504, 192, 206,-32768, 581,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768, 566,-32768, 570, 2684, ! 483, 572, 506, 3026, 2684, 3026,-32768,-32768, 564, 564, ! 616, 2684, 3128, 2197,-32768,-32768,-32768, 314, 478,-32768, ! -32768, 94, 98, 112, 132, 662,-32768, 580,-32768,-32768, ! -32768,-32768,-32768,-32768, 326, 585, 390, 390,-32768, 109, ! -32768,-32768, 588,-32768,-32768, 1709, 3030, 1194, 864, 1875, ! 3055, 1712, 989,-32768,-32768,-32768, 591, 338,-32768,-32768, ! 327,-32768, 586, 590,-32768,-32768,-32768,-32768, 598, 601, ! 1313,-32768,-32768, 659,-32768,-32768,-32768, 602,-32768,-32768, ! 603,-32768,-32768, 109, 109, 3099,-32768, 109, 604, 615, ! 2914, 627, 1862,-32768, 3115,-32768, 483,-32768,-32768,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, ! -32768, 2345,-32768, 2684,-32768,-32768,-32768, 628, 753,-32768, ! -32768,-32768,-32768, 383, 178,-32768,-32768, 945,-32768, 696, ! -32768,-32768, 69,-32768, 206,-32768, 316,-32768,-32768, 3099, ! -32768,-32768, 1313,-32768, 109, 253, 109, 362,-32768,-32768, ! -32768, 109,-32768, 2684,-32768,-32768, 671, 483, 2684,-32768, ! 684, 3099, 646, 644,-32768,-32768, 167, 1998, 2684,-32768, ! 2414,-32768, 687, 2684, 694, 652, 657, 2643, 141, 735, ! -32768,-32768,-32768, 663,-32768,-32768,-32768, 666, 704, 658, ! -32768,-32768,-32768, 2540, 352,-32768,-32768,-32768, 129, 109, ! 109, 538, 553, 158,-32768,-32768, 109, 129, 109, 158, ! -32768, 109,-32768, 1709, 3030, 2076, 3059, 1194, 864, 1772, ! 1536, 1875, 3055, 2144, 3072, 1712, 989, 1837, 1678,-32768, ! -32768,-32768,-32768, 672,-32768,-32768, 416, 421, 1862, 69, ! -32768, 69,-32768, 2684, 88,-32768, 2684, 329,-32768, 2932, ! -32768, 1228, 1862,-32768,-32768, 1930,-32768, 2066,-32768,-32768, ! 3115, 2852,-32768,-32768,-32768,-32768, 668, 2684, 680,-32768, ! 702,-32768,-32768, 206, 316,-32768,-32768,-32768,-32768,-32768, ! 705, 755, 1645, 118,-32768,-32768,-32768,-32768, 383, 336, ! -32768, 109,-32768, 109,-32768,-32768, 109, 178, 178,-32768, ! -32768, 383, 178,-32768,-32768,-32768, 693,-32768,-32768,-32768, ! -32768, 2969, 2684,-32768,-32768, 2969, 2684,-32768,-32768, 2684, ! -32768, 695, 2066,-32768,-32768, 2684,-32768,-32768, 703,-32768, ! 2684, 742, 469,-32768, 268, 475,-32768, 548, 722, 724, ! -32768, 726, 2684, 1732,-32768,-32768,-32768,-32768, 2684,-32768, ! 538, 553, 393,-32768,-32768, 753, 109, 158,-32768, 158, ! -32768,-32768, 253,-32768, 2969,-32768, 2969, 2828,-32768,-32768, ! 3081,-32768, 52, 109,-32768, 461,-32768, 461, 2684, 2684, ! 777, 2540, 713,-32768,-32768,-32768,-32768,-32768, 714,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, 121, 720, ! -32768,-32768,-32768, 715, 723,-32768,-32768,-32768,-32768, 729, ! -32768,-32768,-32768,-32768, 731, 740, 483, 97, 728,-32768, ! -32768,-32768,-32768,-32768,-32768, 2684,-32768,-32768,-32768, 2684, ! 730, 121, 738, 121,-32768,-32768,-32768, 739,-32768, 749, ! 824, 155,-32768,-32768, 672, 672,-32768,-32768,-32768, 767, ! 529, 751,-32768,-32768, 2684, 2684, 355, 389,-32768, 759, ! 760, 764, 529,-32768,-32768,-32768, 355,-32768,-32768, 844, ! 851,-32768 }; static const short yypgoto[] = { ! -32768,-32768,-32768,-32768, 87,-32768,-32768,-32768,-32768,-32768, ! -32768,-32768,-32768, 101,-32768, -60, 468, -253, 443,-32768, ! -32768,-32768, -82, 769,-32768,-32768,-32768,-32768,-32768,-32768, ! -32768, -293, -299, 549,-32768,-32768, 78, 68, -282, -572, ! 7, 41, 38, 44, 1, 20, 47, 50, -364, -336, ! 299, 302, -330, -326, 303, 305, -496, -461, 454, 456, ! -32768, -161, -127, -503, -200, 503, 683, 748, 774,-32768, ! -532, -135, -210, 470,-32768, 589,-32768, 96, 3, 64, ! -32768, 500,-32768, 315,-32768, -420,-32768, 204,-32768, -533, ! -32768,-32768, 292,-32768,-32768,-32768,-32768,-32768,-32768, -133, ! 319, 160, 180, -85, 202,-32768,-32768,-32768,-32768,-32768, ! -32768,-32768,-32768,-32768,-32768, 472, -94,-32768, 583,-32768, ! -32768, 233, 232, 573, 492, -84,-32768,-32768, -526, -272, ! -397, -442,-32768, 465,-32768,-32768,-32768,-32768,-32768,-32768, ! -268,-32768,-32768, -452, 104,-32768,-32768, 545, -343,-32768, ! 308,-32768,-32768, -521,-32768,-32768,-32768,-32768,-32768, 442, ! -395, 111, -689, -172, -150,-32768,-32768,-32768,-32768,-32768, ! -32768,-32768,-32768,-32768,-32768,-32768,-32768,-32768, -743, 84, ! -32768, 90,-32768, 487,-32768, -522,-32768,-32768,-32768,-32768, ! -32768,-32768, 476, -298,-32768,-32768,-32768,-32768, 56 }; ! ! #define YYLAST 3188 ! ! static const short yytable[] = { ! 176, 397, 188, 26, 26, 46, 46, 224, 221, 22, ! 22, 315, 57, 58, 59, 417, 389, 309, 419, 375, ! 620, 420, 27, 27, 546, 73, 626, 82, 640, 91, ! 416, 100, 666, 109, 479, 118, 409, 127, 617, 136, ! 24, 24, 274, 23, 23, 615, 25, 25, 479, 28, ! 28, 716, 29, 29, 26, 229, 46, -1, 53, 53, ! 22, 659, 480, 541, 689, 46, 333, 46, 481, 545, ! 663, 199, 482, 27, 145, 146, 480, 233, 234, 620, ! 616, 810, 481, 145, 146, 301, 482, 239, 243, 618, ! 54, 24, -2, 244, 23, -444, 660, 25, 828, -445, ! 28, 562, 201, 29, 279, 200, 141, 142, 202, 53, ! 144, 456, 867, -446, 575, -106, 471, 577, 14, 777, ! 617, 144, 144, 144, 410, 841, 210, 615, 145, 146, ! 845, 228, 375, -447, 742, 829, 8, 144, 600, 14, ! 153, 889, 733, 861, 145, 146, 144, 143, 618, 148, ! 150, 152, 300, 346, 754, 144, 636, 636, 611, 14, ! 147, 205, 616, 352, 144, 353, 211, 212, 868, 149, ! 400, 762, 60, 144, 333, 46, 669, 876, 671, -424, ! 862, 63, 144, -425, 479, 778, 466, 539, 14, 846, ! 61, 144, 73, 651, 82, 547, 91, -426, 100, 697, ! 144, 880, 73, -106, 82, 788, 790, 459, 898, 63, ! 216, 687, 480, 376, 151, 46, 239, -427, 481, 799, ! 46, 652, 482, 68, 199, 211, 212, 655, 328, 460, ! 46, 656, 62, 587, 324, 588, 637, 399, 881, 837, ! 46, 406, 426, 187, 428, 638, 212, 329, 736, 70, ! 46, 230, 46, 211, 212, 201, 63, 216, 200, 316, ! 212, 202, 751, 820, 217, 326, 238, 437, 325, 394, ! 144, 327, 14, 218, 330, 501, 546, 331, 232, 528, ! 531, 534, 537, 335, 383, 546, 79, 207, 283, 384, ! 624, 208, 672, 315, 675, 210, 440, 235, -274, 673, ! 46, 529, 532, 535, 538, 236, 761, 295, 617, 14, ! 308, 217, -274, 237, 310, 615, 87, 7, 88, 63, ! 218, 545, 239, 9, 10, 11, 737, 73, 738, 82, ! 545, 91, 340, 100, 636, 636, 328, 245, 46, 63, ! 492, 14, 324, 493, 225, 792, 265, 266, 267, 519, ! 616, 521, -274, 882, 883, 329, -274, 302, 246, 14, ! -109, -109, -109, -109, 274, 63, -109, 287, -109, -109, ! -109, 372, 373, 326, 64, 746, 325, 311, 289, 327, ! 75, 312, 330, 65, -109, 331, 63, 627, 318, 46, ! 294, 335, 208, 199, 628, -247, 211, 212, 525, 477, ! 422, 423, 526, 629, 212, 475, 290, 291, 676, 542, ! 558, 418, 295, 477, 543, 559, 84, 421, 478, 475, ! 64, 479, 556, 783, 201, 784, 557, 200, 718, 65, ! 202, 667, 478, 427, 321, 717, 46, 727, 46, 476, ! 246, 628, 674, 337, 340, -109, 347, 547, 386, 480, ! 629, 212, 348, 476, 349, 481, 547, 387, 212, 482, ! 723, 212, 302, 55, 56, -473, -473, -473, -473, 874, ! 875, 350, 891, -473, -473, -473, 819, 892, 73, 446, ! 91, 613, 109, 467, 127, 283, 145, 146, 377, -473, ! 322, 7, 93, 5, 396, 7, 8, 9, 10, 11, ! 734, 9, 10, 11, 312, 735, 831, 382, 832, 208, ! -80, 290, 291, 5, 69, 7, 70, 13, 378, 14, ! 15, 9, 10, 11, 385, 71, 76, 80, 85, 527, ! 530, 340, 536, 107, 112, 116, 121, 13, 156, 14, ! 613, 279, 26, 339, 46, 145, 146, 696, 22, 477, ! -105, 552, 552, 804, 315, 475, 402, 312, 647, 806, ! 46, 27, 407, 208, 643, 549, 564, 566, 478, 765, ! 764, 316, 212, 323, -371, 210, 413, 648, -274, 24, ! 211, 212, 23, -379, -379, 25, 424, 886, 28, 476, ! 429, 29, -274, -243, 430, 645, 435, 623, 644, 896, ! 438, 646, 469, 212, 649, 721, 212, 650, 439, 578, ! 579, 7, 102, 580, 441, 211, 212, 9, 10, 11, ! 723, 212, 248, 250, 26, 505, 46, 599, 414, 415, ! 22, 46, -274, 781, 782, 199, -274, 758, 444, 726, ! 46, 445, 612, 27, 199, 462, 73, 491, 82, 495, ! 91, 513, 100, 436, 109, 514, 118, 517, 127, 674, ! 136, 24, 523, 302, 23, 540, 201, 25, 544, 200, ! 28, 551, 202, 29, 555, 201, 560, 678, 200, 623, ! 561, 202, 563, 703, 704, 565, 210, 317, 680, 581, ! 574, 576, 71, 76, 80, 85, 7, 88, 582, 662, ! 802, 612, 9, 10, 11, 72, 77, 81, 86, 698, ! 584, 625, 812, 108, 113, 117, 122, -30, 818, 706, ! 14, 707, 708, 709, 710, 719, 720, 731, 732, 725, ! 683, 684, 685, -31, 728, 729, 693, 730, 7, 97, ! 692, 694, 699, 276, 9, 10, 11, 702, 833, 834, ! 705, 836, 757, 393, 472, 633, 639, 5, 6, 7, ! 8, 611, 14, 474, 759, 9, 10, 11, 396, 760, ! 743, 773, 772, 747, 89, 94, 98, 103, 791, 677, ! 798, 13, 125, 130, 134, 139, 477, 801, 803, 808, ! 144, 809, 475, 811, 835, 836, 840, 844, 853, 869, ! 90, 95, 99, 104, 850, 478, 854, 859, 126, 131, ! 135, 140, 26, 856, 46, 858, 863, 295, 22, 295, ! 870, 458, 872, 877, 836, 890, 476, 71, 76, 80, ! 85, 27, 878, 879, 885, 888, -535, 793, 96, 7, ! 97, 795, 893, 894, 900, 9, 10, 11, 895, 24, ! 496, 901, 23, 465, 411, 25, 653, 470, 28, 654, ! 657, 29, 658, 14, 509, 512, 498, 623, 499, 92, ! 7, 93, 72, 77, 81, 86, 9, 10, 11, 317, ! 317, 395, 821, 822, 463, 823, 502, 670, 688, 753, ! 824, 786, 825, 458, 458, 533, 458, 209, 780, 830, ! -26, -26, -26, -26, 518, 739, 767, 744, -26, -26, ! -26, 145, 146, 280, 281, 282, 432, -249, 425, 842, ! 290, 291, 516, 210, -26, 461, -274, 715, 843, 290, ! 291, 393, 393, 787, 789, 263, 264, 265, 266, 267, ! -274, 89, 94, 98, 103, 871, 571, 860, 573, 5, ! 6, 7, 8, 873, 0, 642, 550, 9, 10, 11, ! 554, 0, 0, 211, 212, 0, 0, 90, 95, 99, ! 104, 0, 0, 13, 0, 14, 0, 0, 71, 76, ! -274, 0, 107, 112, -274, -26, 0, 4, 0, -118, ! 5, 6, 7, 8, 128, 7, 129, 0, 9, 10, ! 11, 9, 10, 11, 344, 345, 0, 72, 77, 81, ! 86, 0, 0, 12, 13, 351, 14, 15, 393, 393, ! 354, 355, 0, 0, 0, 360, 361, 362, 363, 364, ! 365, 366, 367, 368, 369, 370, 371, 261, 262, 263, ! 264, 265, 266, 267, -118, 0, 319, 0, 0, -22, ! -22, -22, -22, -118, 701, 0, 0, -22, -22, -22, ! 92, 7, 93, 0, 0, 0, 0, 9, 10, 11, ! 16, 0, 210, -22, 0, -274, 89, 94, 98, 103, ! 0, 313, 0, 0, -18, -18, -18, -18, 0, -274, ! 0, 0, -18, -18, -18, 0, 722, 724, 0, 0, ! 0, 0, 90, 95, 99, 104, 0, 210, -18, 0, ! -274, 0, 211, 212, 740, 268, 269, 512, 270, 271, ! 272, 273, 0, 0, -274, 0, 0, 442, 443, -274, ! 0, 0, 0, -274, -22, 0, 0, 0, 0, -248, ! 0, 0, 5, 74, 7, 75, 71, 76, 80, 85, ! 9, 10, 11, 0, 107, 112, 116, 121, 72, 77, ! 0, 0, 108, 113, -274, 0, 13, 0, -274, -18, ! 5, 83, 7, 84, 0, 0, 0, 0, 9, 10, ! 11, 0, 0, 393, 393, 0, 0, 0, 0, 0, ! 0, 0, 393, 393, 13, 0, 393, 393, 515, 87, ! 7, 88, 0, 520, 0, 0, 9, 10, 11, 0, ! 524, 101, 7, 102, 0, 0, 0, 533, 9, 10, ! 11, 0, -244, 0, 14, 89, 94, 0, 0, 125, ! 130, 472, 0, 473, 5, 6, 7, 8, 749, 0, ! 474, 0, 9, 10, 11, 722, 724, 724, 0, 0, ! -246, 90, 95, 0, 0, 126, 131, 0, 13, 533, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 569, ! 0, 251, 252, 253, 0, 254, 255, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 0, ! -250, 591, 0, 864, 865, 0, 0, 0, 0, 5, ! 78, 7, 79, 128, 7, 129, 0, 9, 10, 11, ! 9, 10, 11, -535, 567, 0, 154, 0, 750, 0, ! 0, 155, 156, 13, 157, 14, 72, 77, 81, 86, ! 5, 105, 7, 106, 108, 113, 117, 122, 9, 10, ! 11, 569, 158, 0, 15, 0, 159, 160, 161, 162, ! 163, 0, 679, 0, 13, 164, 14, 681, 0, 0, ! 0, 165, 0, 0, 166, 0, 591, 690, 0, 167, ! 168, 169, 691, 0, 0, 170, 171, 0, 0, -245, ! 172, 0, -256, 5, 114, 7, 115, 0, 0, 0, ! 0, 9, 10, 11, 0, 89, 94, 98, 103, 173, ! 174, 0, 568, 125, 130, 134, 139, 13, 0, 14, ! -251, 0, 0, 0, 322, 0, 0, 5, 0, 7, ! 8, 90, 95, 99, 104, 9, 10, 11, 0, 126, ! 131, 135, 140, 0, 0, 0, 0, 591, 0, 0, ! 0, 13, 741, 14, 15, 745, 0, 0, 0, 0, ! 0, 591, 0, 0, 591, 0, 591, 5, 110, 7, ! 111, 0, 0, -253, 0, 9, 10, 11, 0, 0, ! 0, 0, 275, 0, -449, -449, -449, -449, -449, -449, ! -449, 13, -449, -449, -449, -449, -449, 0, -449, -449, ! -449, -449, -449, -449, -449, -449, -449, -449, -449, -449, ! -449, -449, -449, -449, -449, -449, -449, -449, -449, 0, ! 0, 794, 0, -449, 0, 796, 0, 0, 797, -449, ! 0, 591, -449, 0, 800, 0, 0, -449, -449, -449, ! 0, 0, 0, -449, -449, 0, 0, -252, -449, 0, ! 0, 101, 7, 102, 5, 119, 7, 120, 9, 10, ! 11, 0, 9, 10, 11, -449, 276, -449, -449, 448, ! -449, -473, -473, -473, -473, -473, -473, -473, 13, -473, ! -473, -473, -473, -473, 0, -473, -473, -473, -473, -473, ! -473, -473, -473, -473, -473, -473, -473, -473, -473, -473, ! 0, -473, -473, -473, -473, -473, 137, 7, 138, 0, ! -473, 0, 0, 9, 10, 11, -473, 0, 0, -473, ! 123, 7, 124, 0, -473, -473, -473, 9, 10, 11, ! -473, -473, 0, 0, -254, -473, 0, 0, 0, 0, ! 132, 7, 133, 0, 0, 14, 0, 9, 10, 11, ! 0, 0, -473, 0, -473, -473, 774, -473, -451, -451, ! 0, 0, 0, -451, -451, 14, -451, 0, 0, 0, ! -451, 0, -451, -451, -451, -451, -451, -451, -451, -451, ! -451, -451, -451, 0, -451, -258, -451, 0, -451, -451, ! -451, -451, -451, 137, 7, 138, 0, -451, 0, -255, ! 9, 10, 11, -451, 0, 0, -451, 0, 0, 0, ! 0, -451, -451, -451, 0, 0, 0, -451, -451, -257, ! 0, 0, -451, 5, 69, 7, 70, 123, 7, 124, ! 0, 9, 10, 11, 9, 10, 11, 0, 0, -451, ! 0, -451, -451, 813, -451, -480, -480, 13, 0, 14, ! -480, -480, 14, -480, 0, 0, 0, -480, 0, -480, ! -480, -480, -480, -480, -480, -480, -480, -480, -480, -480, ! 0, -480, 0, -480, 0, -480, -480, -480, -480, -480, ! 0, 0, 0, 0, -480, 0, 0, 96, 7, 97, ! -480, 0, 0, -480, 9, 10, 11, 0, -480, -480, ! -480, 0, 0, 0, -480, -480, 0, 0, 240, -480, ! 154, 5, 14, 7, 8, 155, 156, 0, 157, 9, ! 10, 11, 0, 0, 0, 0, -480, 0, -480, -480, ! 0, -480, 0, 0, 0, 13, 158, 14, 15, 0, ! 159, 160, 161, 162, 163, 0, 0, 0, 0, 164, ! 0, 0, 132, 7, 133, 165, 0, 0, 166, 9, ! 10, 11, 0, 167, 168, 169, 0, 0, 0, 170, ! 171, 0, 0, 585, 172, 586, 146, 14, 0, 0, ! 155, 156, 0, 157, 0, 0, 0, 0, 0, 5, ! 105, 7, 106, 173, 174, 0, 241, 9, 10, 11, ! 0, 158, 0, 15, 0, 159, 160, 161, 162, 163, ! 0, 0, 0, 13, 164, 14, 0, 0, 0, 0, ! 165, 0, 0, 166, 0, 0, 0, 0, 167, 168, ! 169, 0, 0, 0, 170, 171, 0, 0, 587, 172, ! 588, 585, 0, 586, 146, 0, 0, 0, 155, 156, ! 0, 157, 0, 0, 0, 0, 0, -302, 173, 174, ! 0, 589, 0, 0, 0, 0, 0, 0, 0, 158, ! 0, 15, 0, 159, 160, 161, 162, 163, 0, 0, ! 0, 0, 164, 0, 0, 0, 0, 0, 165, 0, ! 0, 166, 0, 0, 0, 0, 167, 168, 169, 0, ! 0, 0, 170, 171, 0, 0, 587, 172, 588, 585, ! 0, 154, 0, 0, 0, 0, 155, 156, 0, 157, ! 0, 0, 0, 0, 0, -368, 173, 174, 0, 589, ! 0, 0, 0, 0, 0, 0, 0, 158, 0, 15, ! 0, 159, 160, 161, 162, 163, 0, 0, 0, 0, ! 164, 0, -315, 0, 0, 0, 165, 0, 0, 166, ! 0, 0, 0, 0, 167, 168, 169, 0, 0, 0, ! 170, 171, 0, 0, -315, 172, -315, 585, 0, 154, ! 0, 0, 0, 0, 155, 156, 0, 157, 0, 0, ! 5, 78, 7, 79, 173, 174, 0, 589, 9, 10, ! 11, 0, 0, 0, 0, 158, 0, 15, 0, 159, ! 160, 161, 162, 163, 13, 0, 14, 0, 164, 0, ! 0, 0, 0, 0, 165, 0, 0, 166, 0, 0, ! 0, 0, 167, 168, 169, 0, 0, 0, 170, 171, ! 0, 0, 0, 172, 154, 5, 297, 7, 8, 155, ! 156, 0, 157, 9, 10, 11, 0, 0, 5, 114, ! 7, 115, 173, 174, 0, 589, 9, 10, 11, 13, ! 158, 14, 15, 0, 159, 160, 161, 162, 163, 0, ! 0, 0, 13, 164, 14, 154, 0, 403, 0, 165, ! 155, 156, 166, 157, 0, 0, 0, 167, 168, 298, ! 0, 0, 0, 170, 171, 0, 0, 0, 172, 0, ! 0, 158, 0, 15, 0, 159, 160, 161, 162, 163, ! 0, 0, 0, 0, 164, 0, 0, 173, 174, 0, ! 165, 299, 0, 166, 0, 0, 0, 0, 167, 168, ! 404, 0, 0, 0, 170, 171, 0, 154, 0, 172, ! 0, 0, 155, 156, 0, 157, 256, 257, 258, 259, ! 260, 261, 262, 263, 264, 265, 266, 267, 173, 174, ! 0, 0, 405, 158, 0, 15, 0, 159, 160, 161, ! 162, 163, 0, 0, 0, 0, 164, 0, 154, 0, ! 0, 0, 165, 155, 156, 166, 157, 0, 0, 0, ! 167, 168, 169, 0, 0, 0, 170, 171, 0, 0, ! 0, 172, 0, 0, 158, 0, 15, 0, 159, 160, ! 161, 162, 163, 0, 0, 0, 0, 164, 0, 0, ! 173, 174, 0, 165, 401, 0, 166, 0, 0, 0, ! 0, 167, 168, 169, 0, 0, 0, 170, 171, 0, ! 0, 0, 172, 0, 0, 0, 0, 0, 586, 602, ! 6, 7, 8, 155, 156, 0, 157, 9, 10, 11, ! 0, 173, 174, 0, 0, 494, 603, 604, 605, 606, ! 607, 608, 609, 13, 158, 14, 15, 0, 159, 160, ! 161, 162, 163, 0, 0, 0, 0, 164, 0, 5, ! 0, 7, 70, 165, 0, 0, 166, 9, 10, 11, ! 0, 167, 168, 169, 0, 0, 0, 170, 171, 0, ! 0, 0, 172, 13, 0, 14, 0, 586, 146, 0, ! 0, 0, 155, 156, 0, 157, 0, 0, 0, 610, ! 0, 173, 174, 0, 611, 603, 604, 605, 606, 607, ! 608, 609, 0, 158, 0, 15, 0, 159, 160, 161, ! 162, 163, 0, 0, 0, 0, 164, 0, 5, 6, ! 7, 8, 165, 0, 0, 166, 9, 10, 11, 0, ! 167, 168, 169, 0, 0, 0, 170, 171, 154, 0, ! 0, 172, 13, 155, 156, 0, 157, 257, 258, 259, ! 260, 261, 262, 263, 264, 265, 266, 267, 610, 0, ! 173, 174, 0, 611, 158, 0, 15, 0, 159, 160, ! 161, 162, 163, 0, 0, 0, 0, 164, 0, 0, ! 0, 0, 0, 165, 0, 0, 166, 0, 0, 0, ! 0, 167, 168, 169, 0, 0, 0, 170, 171, 0, ! 0, 0, 172, 154, 5, 6, 7, 8, 155, 156, ! 0, 157, 9, 10, 11, 0, 0, 5, 0, 7, ! 79, 173, 174, 0, 436, 9, 10, 11, 13, 158, ! 14, 15, 0, 159, 160, 161, 162, 163, 0, 0, ! 0, 13, 164, 14, 0, 0, 0, 0, 165, 0, ! 0, 166, 0, 0, 0, 0, 167, 168, 169, 0, ! 0, 0, 170, 171, 0, 154, 5, 172, 7, 8, ! 155, 156, 0, 157, 9, 10, 11, 260, 261, 262, ! 263, 264, 265, 266, 267, 0, 173, 174, 0, 0, ! 13, 158, 14, 15, 0, 159, 160, 161, 162, 163, ! 0, 0, 0, 0, 164, 0, 154, 0, 0, 0, ! 165, 155, 156, 166, 157, 0, 0, 0, 167, 168, ! 169, 0, 0, 0, 170, 171, 0, 0, 0, 172, ! 0, 0, 158, 0, 15, 0, 159, 160, 161, 162, ! 163, 0, 0, 0, 0, 164, 0, 154, 173, 174, ! 0, 165, 155, 156, 166, 157, 0, 0, 0, 167, ! 168, 169, 0, 0, 0, 170, 171, 0, 0, 0, ! 172, 0, 0, 158, 0, 15, 0, 159, 160, 161, ! 162, 163, 0, 0, 0, 0, 164, 695, 154, 173, ! 174, 0, 165, 155, 156, 166, 157, 0, 0, 0, ! 167, 168, 169, 0, 0, 0, 170, 171, 0, 0, ! 0, 172, 0, 0, 158, 0, 15, 0, 159, 160, ! 161, 162, 163, 0, 0, 0, 0, 164, 0, 154, ! 173, 174, 0, 165, 155, 156, 166, 157, 0, 0, ! 0, 167, 168, 169, 0, 0, 0, 170, 171, 0, ! 0, 0, 247, 0, 0, 158, 0, 15, 0, 159, ! 160, 161, 162, 163, 0, 0, 0, 0, 164, 0, ! 464, 173, 174, 0, 165, 155, 156, 166, 157, 0, ! 0, 0, 167, 168, 169, 0, 0, 0, 170, 171, ! 0, 0, 0, 249, 0, 0, 158, 0, 15, 0, ! 159, 160, 161, 162, 163, 0, 0, 0, 0, 164, ! 0, 0, 173, 174, 0, 165, 0, 0, 166, 0, ! 0, 0, 755, 167, 168, 169, 0, 0, 0, 170, ! 171, 251, 252, 253, 172, 254, 255, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 0, ! 0, 0, 0, 173, 174, 251, 252, 253, 756, 254, ! 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 0, 0, 251, 252, 253, 826, 254, ! 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 251, 252, 253, 0, 254, 255, 256, ! 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, ! 267, 0, 0, 0, 0, 0, 0, 251, 252, 253, ! 433, 254, 255, 256, 257, 258, 259, 260, 261, 262, ! 263, 264, 265, 266, 267, 251, 252, 253, 434, 254, ! 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 0, 0, 0, 0, 0, 0, 14, ! 0, 0, 583, 0, 0, 0, 0, 0, 0, 0, ! 0, 0, 251, 252, 253, 748, 254, 255, 256, 257, ! 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, ! 5, 0, 7, 8, 5, 74, 7, 75, 9, 10, ! 11, 0, 9, 10, 11, 0, 0, 0, 0, 0, ! 0, 0, 0, 0, 13, 0, 14, 0, 13, 5, ! 110, 7, 111, 5, 83, 7, 84, 9, 10, 11, ! 0, 9, 10, 11, 0, 0, 5, 119, 7, 120, ! 0, 0, 0, 13, 9, 10, 11, 13, 5, 0, ! 7, 75, 0, 0, 0, 0, 9, 10, 11, 5, ! 13, 7, 84, 0, 0, 0, 0, 9, 10, 11, ! 0, 0, 13, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 13, 251, 252, 253, 827, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, ! 266, 267, 251, 252, 253, 0, 254, 255, 256, 257, ! 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, ! 253, 0, 254, 255, 256, 257, 258, 259, 260, 261, ! 262, 263, 264, 265, 266, 267, 255, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267 }; static const short yycheck[] = { ! 60, 294, 62, 2, 3, 2, 3, 142, 141, 2, ! 3, 221, 9, 10, 11, 314, 288, 217, 316, 272, ! 541, 320, 2, 3, 466, 22, 548, 24, 554, 26, ! 312, 28, 564, 30, 398, 32, 304, 34, 541, 36, ! 2, 3, 9, 2, 3, 541, 2, 3, 412, 2, ! 3, 623, 2, 3, 53, 149, 53, 0, 2, 3, ! 53, 557, 398, 458, 597, 62, 227, 64, 398, 466, ! 1, 64, 398, 53, 3, 4, 412, 159, 160, 600, ! 541, 770, 412, 3, 4, 212, 412, 169, 172, 541, ! 3, 53, 0, 175, 53, 1, 557, 53, 46, 1, ! 53, 496, 64, 53, 186, 64, 38, 39, 64, 53, ! 46, 379, 855, 1, 509, 1, 83, 512, 30, 1, ! 623, 57, 58, 59, 10, 814, 27, 623, 3, 4, ! 9, 89, 385, 1, 46, 83, 7, 73, 533, 30, ! 53, 884, 663, 46, 3, 4, 82, 84, 600, 48, ! 49, 50, 212, 237, 687, 91, 553, 554, 89, 30, ! 89, 65, 623, 247, 100, 249, 67, 68, 857, 89, ! 297, 703, 67, 109, 335, 172, 571, 866, 573, 85, ! 83, 3, 118, 85, 548, 67, 386, 455, 30, 68, ! 67, 127, 189, 557, 191, 467, 193, 85, 195, 58, ! 136, 46, 199, 89, 201, 731, 732, 379, 897, 3, ! 4, 44, 548, 273, 89, 212, 298, 85, 548, 752, ! 217, 557, 548, 21, 217, 67, 68, 557, 227, 379, ! 227, 557, 67, 66, 227, 68, 58, 297, 83, 811, ! 237, 301, 336, 67, 338, 67, 68, 227, 668, 7, ! 247, 89, 249, 67, 68, 217, 3, 4, 217, 67, ! 68, 217, 682, 785, 58, 227, 165, 349, 227, 83, ! 206, 227, 30, 67, 227, 83, 718, 227, 89, 451, ! 452, 453, 454, 227, 83, 727, 7, 84, 187, 88, ! 543, 88, 574, 503, 576, 27, 356, 67, 30, 46, ! 297, 451, 452, 453, 454, 67, 701, 211, 811, 30, ! 214, 58, 44, 67, 218, 811, 5, 6, 7, 3, ! 67, 718, 404, 12, 13, 14, 669, 324, 671, 326, ! 727, 328, 231, 330, 731, 732, 335, 83, 335, 3, ! 400, 30, 335, 403, 142, 740, 58, 59, 60, 433, ! 811, 435, 84, 874, 875, 335, 88, 1, 88, 30, ! 4, 5, 6, 7, 9, 3, 10, 83, 12, 13, ! 14, 270, 271, 335, 58, 46, 335, 84, 83, 335, ! 7, 88, 335, 67, 28, 335, 3, 4, 84, 386, ! 67, 335, 88, 386, 58, 84, 67, 68, 84, 398, ! 332, 333, 88, 67, 68, 398, 204, 205, 46, 83, ! 83, 315, 316, 412, 88, 88, 7, 321, 398, 412, ! 58, 785, 84, 721, 386, 723, 88, 386, 628, 67, ! 386, 566, 412, 337, 85, 83, 433, 637, 435, 398, ! 88, 58, 575, 85, 343, 89, 83, 719, 58, 785, ! 67, 68, 83, 412, 83, 785, 728, 67, 68, 785, ! 67, 68, 1, 84, 85, 4, 5, 6, 7, 864, ! 865, 84, 83, 12, 13, 14, 83, 88, 475, 378, ! 477, 541, 479, 387, 481, 384, 3, 4, 83, 28, ! 1, 6, 7, 4, 292, 6, 7, 12, 13, 14, ! 84, 12, 13, 14, 88, 84, 805, 83, 807, 88, ! 46, 309, 310, 4, 5, 6, 7, 28, 32, 30, ! 31, 12, 13, 14, 67, 22, 23, 24, 25, 451, ! 452, 430, 454, 30, 31, 32, 33, 28, 9, 30, ! 600, 623, 541, 1, 541, 3, 4, 607, 541, 548, ! 89, 483, 484, 84, 764, 548, 90, 88, 557, 84, ! 557, 541, 84, 88, 557, 469, 498, 499, 548, 704, ! 703, 67, 68, 84, 85, 27, 44, 557, 30, 541, ! 67, 68, 541, 84, 85, 541, 84, 880, 541, 548, ! 44, 541, 44, 84, 88, 557, 88, 541, 557, 892, ! 83, 557, 67, 68, 557, 67, 68, 557, 83, 513, ! 514, 6, 7, 517, 46, 67, 68, 12, 13, 14, ! 67, 68, 179, 180, 623, 44, 623, 526, 309, 310, ! 623, 628, 84, 718, 719, 628, 88, 697, 83, 636, ! 637, 90, 541, 623, 637, 83, 643, 90, 645, 90, ! 647, 85, 649, 89, 651, 85, 653, 85, 655, 792, ! 657, 623, 46, 1, 623, 85, 628, 623, 83, 628, ! 623, 83, 628, 623, 83, 637, 90, 581, 637, 623, ! 90, 637, 84, 615, 616, 84, 27, 222, 587, 85, ! 88, 88, 189, 190, 191, 192, 6, 7, 83, 3, ! 760, 600, 12, 13, 14, 22, 23, 24, 25, 608, ! 83, 83, 772, 30, 31, 32, 33, 46, 778, 15, ! 30, 17, 18, 19, 20, 629, 630, 659, 660, 633, ! 46, 85, 88, 46, 638, 639, 84, 641, 6, 7, ! 46, 84, 7, 85, 12, 13, 14, 84, 808, 809, ! 84, 811, 84, 288, 1, 553, 554, 4, 5, 6, ! 7, 89, 30, 10, 84, 12, 13, 14, 566, 67, ! 674, 16, 67, 677, 26, 27, 28, 29, 85, 577, ! 85, 28, 34, 35, 36, 37, 785, 84, 46, 67, ! 726, 67, 785, 67, 17, 855, 83, 83, 83, 859, ! 26, 27, 28, 29, 84, 785, 83, 67, 34, 35, ! 36, 37, 811, 84, 811, 84, 88, 721, 811, 723, ! 90, 379, 84, 84, 884, 885, 785, 324, 325, 326, ! 327, 811, 83, 9, 67, 84, 83, 741, 5, 6, ! 7, 745, 83, 83, 0, 12, 13, 14, 84, 811, ! 408, 0, 811, 385, 305, 811, 557, 392, 811, 557, ! 557, 811, 557, 30, 422, 423, 412, 811, 412, 5, ! 6, 7, 189, 190, 191, 192, 12, 13, 14, 414, ! 415, 292, 786, 787, 384, 789, 416, 572, 596, 685, ! 794, 731, 796, 451, 452, 453, 454, 1, 718, 803, ! 4, 5, 6, 7, 432, 672, 704, 675, 12, 13, ! 14, 3, 4, 5, 6, 7, 343, 84, 335, 815, ! 718, 719, 430, 27, 28, 380, 30, 619, 817, 727, ! 728, 466, 467, 731, 732, 56, 57, 58, 59, 60, ! 44, 193, 194, 195, 196, 861, 504, 846, 506, 4, ! 5, 6, 7, 863, -1, 10, 469, 12, 13, 14, ! 484, -1, -1, 67, 68, -1, -1, 193, 194, 195, ! 196, -1, -1, 28, -1, 30, -1, -1, 475, 476, ! 84, -1, 479, 480, 88, 89, -1, 1, -1, 3, ! 4, 5, 6, 7, 5, 6, 7, -1, 12, 13, ! 14, 12, 13, 14, 235, 236, -1, 324, 325, 326, ! 327, -1, -1, 27, 28, 246, 30, 31, 553, 554, ! 251, 252, -1, -1, -1, 256, 257, 258, 259, 260, ! 261, 262, 263, 264, 265, 266, 267, 54, 55, 56, ! 57, 58, 59, 60, 58, -1, 1, -1, -1, 4, ! 5, 6, 7, 67, 612, -1, -1, 12, 13, 14, ! 5, 6, 7, -1, -1, -1, -1, 12, 13, 14, ! 84, -1, 27, 28, -1, 30, 328, 329, 330, 331, ! -1, 1, -1, -1, 4, 5, 6, 7, -1, 44, ! -1, -1, 12, 13, 14, -1, 631, 632, -1, -1, ! -1, -1, 328, 329, 330, 331, -1, 27, 28, -1, ! 30, -1, 67, 68, 672, 62, 63, 675, 65, 66, ! 67, 68, -1, -1, 44, -1, -1, 358, 359, 84, ! -1, -1, -1, 88, 89, -1, -1, -1, -1, 84, ! -1, -1, 4, 5, 6, 7, 643, 644, 645, 646, ! 12, 13, 14, -1, 651, 652, 653, 654, 475, 476, ! -1, -1, 479, 480, 84, -1, 28, -1, 88, 89, ! 4, 5, 6, 7, -1, -1, -1, -1, 12, 13, ! 14, -1, -1, 718, 719, -1, -1, -1, -1, -1, ! -1, -1, 727, 728, 28, -1, 731, 732, 429, 5, ! 6, 7, -1, 434, -1, -1, 12, 13, 14, -1, ! 441, 5, 6, 7, -1, -1, -1, 775, 12, 13, ! 14, -1, 84, -1, 30, 477, 478, -1, -1, 481, ! 482, 1, -1, 3, 4, 5, 6, 7, 10, -1, ! 10, -1, 12, 13, 14, 780, 781, 782, -1, -1, ! 84, 477, 478, -1, -1, 481, 482, -1, 28, 817, ! 52, 53, 54, 55, 56, 57, 58, 59, 60, 500, ! -1, 43, 44, 45, -1, 47, 48, 49, 50, 51, ! 52, 53, 54, 55, 56, 57, 58, 59, 60, -1, ! 84, 522, -1, 851, 852, -1, -1, -1, -1, 4, ! 5, 6, 7, 5, 6, 7, -1, 12, 13, 14, ! 12, 13, 14, 83, 1, -1, 3, -1, 90, -1, ! -1, 8, 9, 28, 11, 30, 643, 644, 645, 646, ! 4, 5, 6, 7, 651, 652, 653, 654, 12, 13, ! 14, 572, 29, -1, 31, -1, 33, 34, 35, 36, ! 37, -1, 583, -1, 28, 42, 30, 588, -1, -1, ! -1, 48, -1, -1, 51, -1, 597, 598, -1, 56, ! 57, 58, 603, -1, -1, 62, 63, -1, -1, 84, ! 67, -1, 84, 4, 5, 6, 7, -1, -1, -1, ! -1, 12, 13, 14, -1, 647, 648, 649, 650, 86, ! 87, -1, 89, 655, 656, 657, 658, 28, -1, 30, ! 84, -1, -1, -1, 1, -1, -1, 4, -1, 6, ! 7, 647, 648, 649, 650, 12, 13, 14, -1, 655, ! 656, 657, 658, -1, -1, -1, -1, 668, -1, -1, ! -1, 28, 673, 30, 31, 676, -1, -1, -1, -1, ! -1, 682, -1, -1, 685, -1, 687, 4, 5, 6, ! 7, -1, -1, 84, -1, 12, 13, 14, -1, -1, ! -1, -1, 1, -1, 3, 4, 5, 6, 7, 8, ! 9, 28, 11, 12, 13, 14, 15, -1, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, ! 29, 30, 31, 32, 33, 34, 35, 36, 37, -1, ! -1, 742, -1, 42, -1, 746, -1, -1, 749, 48, ! -1, 752, 51, -1, 755, -1, -1, 56, 57, 58, ! -1, -1, -1, 62, 63, -1, -1, 84, 67, -1, ! -1, 5, 6, 7, 4, 5, 6, 7, 12, 13, ! 14, -1, 12, 13, 14, 84, 85, 86, 87, 1, ! 89, 3, 4, 5, 6, 7, 8, 9, 28, 11, ! 12, 13, 14, 15, -1, 17, 18, 19, 20, 21, ! 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, ! -1, 33, 34, 35, 36, 37, 5, 6, 7, -1, ! 42, -1, -1, 12, 13, 14, 48, -1, -1, 51, ! 5, 6, 7, -1, 56, 57, 58, 12, 13, 14, ! 62, 63, -1, -1, 84, 67, -1, -1, -1, -1, ! 5, 6, 7, -1, -1, 30, -1, 12, 13, 14, ! -1, -1, 84, -1, 86, 87, 1, 89, 3, 4, ! -1, -1, -1, 8, 9, 30, 11, -1, -1, -1, ! 15, -1, 17, 18, 19, 20, 21, 22, 23, 24, ! 25, 26, 27, -1, 29, 84, 31, -1, 33, 34, ! 35, 36, 37, 5, 6, 7, -1, 42, -1, 84, ! 12, 13, 14, 48, -1, -1, 51, -1, -1, -1, ! -1, 56, 57, 58, -1, -1, -1, 62, 63, 84, ! -1, -1, 67, 4, 5, 6, 7, 5, 6, 7, ! -1, 12, 13, 14, 12, 13, 14, -1, -1, 84, ! -1, 86, 87, 1, 89, 3, 4, 28, -1, 30, ! 8, 9, 30, 11, -1, -1, -1, 15, -1, 17, ! 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, ! -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, -1, 42, -1, -1, 5, 6, 7, ! 48, -1, -1, 51, 12, 13, 14, -1, 56, 57, ! 58, -1, -1, -1, 62, 63, -1, -1, 1, 67, ! 3, 4, 30, 6, 7, 8, 9, -1, 11, 12, ! 13, 14, -1, -1, -1, -1, 84, -1, 86, 87, ! -1, 89, -1, -1, -1, 28, 29, 30, 31, -1, ! 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, ! -1, -1, 5, 6, 7, 48, -1, -1, 51, 12, ! 13, 14, -1, 56, 57, 58, -1, -1, -1, 62, ! 63, -1, -1, 1, 67, 3, 4, 30, -1, -1, ! 8, 9, -1, 11, -1, -1, -1, -1, -1, 4, ! 5, 6, 7, 86, 87, -1, 89, 12, 13, 14, ! -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, 28, 42, 30, -1, -1, -1, -1, ! 48, -1, -1, 51, -1, -1, -1, -1, 56, 57, ! 58, -1, -1, -1, 62, 63, -1, -1, 66, 67, ! 68, 1, -1, 3, 4, -1, -1, -1, 8, 9, ! -1, 11, -1, -1, -1, -1, -1, 85, 86, 87, ! -1, 89, -1, -1, -1, -1, -1, -1, -1, 29, ! -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, ! -1, -1, 42, -1, -1, -1, -1, -1, 48, -1, -1, 51, -1, -1, -1, -1, 56, 57, 58, -1, ! -1, -1, 62, 63, -1, -1, 66, 67, 68, 1, ! -1, 3, -1, -1, -1, -1, 8, 9, -1, 11, ! -1, -1, -1, -1, -1, 85, 86, 87, -1, 89, ! -1, -1, -1, -1, -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, 44, -1, -1, -1, 48, -1, -1, 51, ! -1, -1, -1, -1, 56, 57, 58, -1, -1, -1, ! 62, 63, -1, -1, 66, 67, 68, 1, -1, 3, ! -1, -1, -1, -1, 8, 9, -1, 11, -1, -1, ! 4, 5, 6, 7, 86, 87, -1, 89, 12, 13, ! 14, -1, -1, -1, -1, 29, -1, 31, -1, 33, ! 34, 35, 36, 37, 28, -1, 30, -1, 42, -1, ! -1, -1, -1, -1, 48, -1, -1, 51, -1, -1, ! -1, -1, 56, 57, 58, -1, -1, -1, 62, 63, ! -1, -1, -1, 67, 3, 4, 5, 6, 7, 8, ! 9, -1, 11, 12, 13, 14, -1, -1, 4, 5, ! 6, 7, 86, 87, -1, 89, 12, 13, 14, 28, ! 29, 30, 31, -1, 33, 34, 35, 36, 37, -1, ! -1, -1, 28, 42, 30, 3, -1, 5, -1, 48, ! 8, 9, 51, 11, -1, -1, -1, 56, 57, 58, ! -1, -1, -1, 62, 63, -1, -1, -1, 67, -1, ! -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, -1, 42, -1, -1, 86, 87, -1, ! 48, 90, -1, 51, -1, -1, -1, -1, 56, 57, ! 58, -1, -1, -1, 62, 63, -1, 3, -1, 67, ! -1, -1, 8, 9, -1, 11, 49, 50, 51, 52, ! 53, 54, 55, 56, 57, 58, 59, 60, 86, 87, ! -1, -1, 90, 29, -1, 31, -1, 33, 34, 35, ! 36, 37, -1, -1, -1, -1, 42, -1, 3, -1, ! -1, -1, 48, 8, 9, 51, 11, -1, -1, -1, ! 56, 57, 58, -1, -1, -1, 62, 63, -1, -1, ! -1, 67, -1, -1, 29, -1, 31, -1, 33, 34, ! 35, 36, 37, -1, -1, -1, -1, 42, -1, -1, ! 86, 87, -1, 48, 90, -1, 51, -1, -1, -1, ! -1, 56, 57, 58, -1, -1, -1, 62, 63, -1, ! -1, -1, 67, -1, -1, -1, -1, -1, 3, 4, ! 5, 6, 7, 8, 9, -1, 11, 12, 13, 14, ! -1, 86, 87, -1, -1, 90, 21, 22, 23, 24, ! 25, 26, 27, 28, 29, 30, 31, -1, 33, 34, ! 35, 36, 37, -1, -1, -1, -1, 42, -1, 4, ! -1, 6, 7, 48, -1, -1, 51, 12, 13, 14, ! -1, 56, 57, 58, -1, -1, -1, 62, 63, -1, ! -1, -1, 67, 28, -1, 30, -1, 3, 4, -1, ! -1, -1, 8, 9, -1, 11, -1, -1, -1, 84, ! -1, 86, 87, -1, 89, 21, 22, 23, 24, 25, ! 26, 27, -1, 29, -1, 31, -1, 33, 34, 35, ! 36, 37, -1, -1, -1, -1, 42, -1, 4, 5, ! 6, 7, 48, -1, -1, 51, 12, 13, 14, -1, ! 56, 57, 58, -1, -1, -1, 62, 63, 3, -1, ! -1, 67, 28, 8, 9, -1, 11, 50, 51, 52, ! 53, 54, 55, 56, 57, 58, 59, 60, 84, -1, ! 86, 87, -1, 89, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, -1, -1, -1, -1, -1, 48, -1, -1, 51, -1, -1, -1, ! -1, 56, 57, 58, -1, -1, -1, 62, 63, -1, ! -1, -1, 67, 3, 4, 5, 6, 7, 8, 9, ! -1, 11, 12, 13, 14, -1, -1, 4, -1, 6, ! 7, 86, 87, -1, 89, 12, 13, 14, 28, 29, ! 30, 31, -1, 33, 34, 35, 36, 37, -1, -1, ! -1, 28, 42, 30, -1, -1, -1, -1, 48, -1, ! -1, 51, -1, -1, -1, -1, 56, 57, 58, -1, ! -1, -1, 62, 63, -1, 3, 4, 67, 6, 7, ! 8, 9, -1, 11, 12, 13, 14, 53, 54, 55, ! 56, 57, 58, 59, 60, -1, 86, 87, -1, -1, 28, 29, 30, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, -1, 42, -1, 3, -1, -1, -1, ! 48, 8, 9, 51, 11, -1, -1, -1, 56, 57, ! 58, -1, -1, -1, 62, 63, -1, -1, -1, 67, ! -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, ! 37, -1, -1, -1, -1, 42, -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, -1, -1, 56, ! 57, 58, -1, -1, -1, 62, 63, -1, -1, -1, ! 67, -1, -1, 29, -1, 31, -1, 33, 34, 35, ! 36, 37, -1, -1, -1, -1, 42, 84, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, -1, -1, ! 56, 57, 58, -1, -1, -1, 62, 63, -1, -1, ! -1, 67, -1, -1, 29, -1, 31, -1, 33, 34, ! 35, 36, 37, -1, -1, -1, -1, 42, -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, -1, ! -1, 56, 57, 58, -1, -1, -1, 62, 63, -1, ! -1, -1, 67, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, ! -1, -1, 56, 57, 58, -1, -1, -1, 62, 63, ! -1, -1, -1, 67, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, ! -1, -1, 86, 87, -1, 48, -1, -1, 51, -1, ! -1, -1, 10, 56, 57, 58, -1, -1, -1, 62, ! 63, 43, 44, 45, 67, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, -1, ! -1, -1, -1, 86, 87, 43, 44, 45, 46, 47, ! 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, ! 58, 59, 60, -1, -1, 43, 44, 45, 90, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 43, 44, 45, -1, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, -1, -1, -1, -1, -1, -1, 43, 44, 45, 88, 47, 48, 49, 50, 51, 52, 53, 54, 55, ! 56, 57, 58, 59, 60, 43, 44, 45, 88, 47, ! 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, ! 58, 59, 60, -1, -1, -1, -1, -1, -1, 30, ! -1, -1, 88, -1, -1, -1, -1, -1, -1, -1, ! -1, -1, 43, 44, 45, 83, 47, 48, 49, 50, ! 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, ! 4, -1, 6, 7, 4, 5, 6, 7, 12, 13, 14, -1, 12, 13, 14, -1, -1, -1, -1, -1, ! -1, -1, -1, -1, 28, -1, 30, -1, 28, 4, ! 5, 6, 7, 4, 5, 6, 7, 12, 13, 14, ! -1, 12, 13, 14, -1, -1, 4, 5, 6, 7, ! -1, -1, -1, 28, 12, 13, 14, 28, 4, -1, ! 6, 7, -1, -1, -1, -1, 12, 13, 14, 4, ! 28, 6, 7, -1, -1, -1, -1, 12, 13, 14, ! -1, -1, 28, 51, 52, 53, 54, 55, 56, 57, ! 58, 59, 60, 28, 43, 44, 45, 46, 47, 48, ! 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, ! 59, 60, 43, 44, 45, -1, 47, 48, 49, 50, ! 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, ! 45, -1, 47, 48, 49, 50, 51, 52, 53, 54, ! 55, 56, 57, 58, 59, 60, 48, 49, 50, 51, ! 52, 53, 54, 55, 56, 57, 58, 59, 60 }; - /* -*-C-*- Note some compilers choke on comments on `#line' lines. */ - #line 3 "/usr/share/bison/bison.simple" - - /* Skeleton output parser for bison, - - Copyright (C) 1984, 1989, 1990, 2000, 2001, 2002 Free Software - Foundation, Inc. - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2, or (at your option) - any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 59 Temple Place - Suite 330, - Boston, MA 02111-1307, USA. */ - - /* As a special exception, when this file is copied by Bison into a - Bison output file, you may use that output file without restriction. - This special exception was added by the Free Software Foundation - in version 1.24 of Bison. */ - - /* This is the parser code that is written into each bison parser when - the %semantic_parser declaration is not specified in the grammar. - It was written by Richard Stallman by simplifying the hairy parser - used when %semantic_parser is specified. */ - - /* All symbols defined below should begin with yy or YY, to avoid - infringing on user name space. This should be done even for local - variables, as they might otherwise be expanded by user macros. - There are some unavoidable exceptions within include files to - define necessary library symbols; they are noted "INFRINGES ON - USER NAME SPACE" below. */ - - #ifdef __cplusplus - # define YYSTD(x) std::x - #else - # define YYSTD(x) x - #endif ! #ifndef YYPARSE_RETURN_TYPE ! #define YYPARSE_RETURN_TYPE int ! #endif ! ! #if ! defined (yyoverflow) || defined (YYERROR_VERBOSE) ! ! /* The parser invokes alloca or malloc; define the necessary symbols. */ ! ! # if YYSTACK_USE_ALLOCA ! # define YYSTACK_ALLOC alloca ! # else ! # ifndef YYSTACK_USE_ALLOCA ! # if defined (alloca) || defined (_ALLOCA_H) ! # define YYSTACK_ALLOC alloca ! # else ! # ifdef __GNUC__ ! # define YYSTACK_ALLOC __builtin_alloca ! # endif ! # endif ! # endif ! # endif ! ! # ifdef YYSTACK_ALLOC ! /* Pacify GCC's `empty if-body' warning. */ ! # define YYSTACK_FREE(Ptr) do { /* empty */; } while (0) ! # else ! # ifdef __cplusplus ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T std::size_t ! # else ! # ifdef __STDC__ ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T size_t ! # endif ! # endif ! # define YYSTACK_ALLOC YYSTD (malloc) ! # define YYSTACK_FREE YYSTD (free) ! # endif ! ! /* A type that is properly aligned for any stack member. */ ! union yyalloc { ! short yyss; ! YYSTYPE yyvs; ! # if YYLSP_NEEDED ! YYLTYPE yyls; ! # endif }; - /* The size of the maximum gap between one aligned stack and the next. */ - # define YYSTACK_GAP_MAX (sizeof (union yyalloc) - 1) - - /* The size of an array large to enough to hold all stacks, each with - N elements. */ - # if YYLSP_NEEDED - # define YYSTACK_BYTES(N) \ - ((N) * (sizeof (short) + sizeof (YYSTYPE) + sizeof (YYLTYPE)) \ - + 2 * YYSTACK_GAP_MAX) - # else - # define YYSTACK_BYTES(N) \ - ((N) * (sizeof (short) + sizeof (YYSTYPE)) \ - + YYSTACK_GAP_MAX) - # endif - - /* Relocate the TYPE STACK from its old location to the new one. The - local variables YYSIZE and YYSTACKSIZE give the old and new number of - elements in the stack, and YYPTR gives the new location of the - stack. Advance YYPTR to a properly aligned location for the next - stack. */ - # define YYSTACK_RELOCATE(Type, Stack) \ - do \ - { \ - YYSIZE_T yynewbytes; \ - yymemcpy ((char *) yyptr, (char *) (Stack), \ - yysize * (YYSIZE_T) sizeof (Type)); \ - Stack = &yyptr->Stack; \ - yynewbytes = yystacksize * sizeof (Type) + YYSTACK_GAP_MAX; \ - yyptr += yynewbytes / sizeof (*yyptr); \ - } \ - while (0) - - #endif /* ! defined (yyoverflow) || defined (YYERROR_VERBOSE) */ - - #if ! defined (YYSIZE_T) && defined (__SIZE_TYPE__) # define YYSIZE_T __SIZE_TYPE__ #endif --- 872,2011 ---- }; #endif ! # ifdef YYPRINT ! /* YYTOKNUM[YYLEX-NUM] -- Internal token number corresponding to ! token YYLEX-NUM. */ ! static const unsigned short yytoknum[] = { ! 0, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, ! 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, ! 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, ! 295, 296, 297, 61, 298, 63, 58, 299, 300, 124, ! 94, 38, 301, 302, 303, 304, 43, 45, 42, 47, ! 37, 305, 306, 307, 308, 46, 40, 91, 309, 310, ! 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, ! 321, 322, 323, 41, 59, 125, 126, 33, 44, 123, ! 93 }; + # endif ! /* YYR1[YYN] -- Symbol number of symbol that rule YYN derives. */ ! static const unsigned short yyr1[] = { ! 0, 91, 92, 92, 94, 93, 95, 93, 96, 96, ! 96, 96, 97, 97, 97, 97, 97, 97, 97, 99, ! 100, 98, 98, 101, 102, 98, 98, 103, 104, 98, ! 98, 105, 105, 106, 106, 106, 106, 106, 106, 106, ! 107, 108, 108, 109, 109, 110, 110, 110, 110, 110, ! 110, 110, 110, 110, 110, 110, 111, 112, 113, 114, ! 114, 115, 115, 115, 115, 115, 115, 115, 115, 115, ! 115, 115, 115, 115, 116, 115, 117, 115, 118, 119, ! 115, 120, 115, 115, 115, 121, 121, 121, 121, 122, ! 121, 121, 121, 121, 121, 121, 121, 121, 121, 121, ! 121, 121, 121, 121, 123, 123, 124, 124, 124, 125, ! 126, 126, 126, 126, 127, 127, 127, 127, 128, 129, ! 130, 131, 131, 131, 131, 131, 131, 132, 132, 132, ! 133, 134, 134, 135, 135, 136, 136, 136, 136, 136, ! 136, 136, 137, 137, 137, 137, 137, 137, 138, 138, ! 138, 138, 138, 138, 139, 139, 139, 139, 139, 140, ! 140, 140, 140, 140, 140, 140, 141, 142, 142, 142, ! 142, 142, 142, 143, 144, 144, 144, 144, 144, 144, ! 144, 144, 144, 144, 145, 145, 145, 145, 145, 146, ! 146, 146, 146, 146, 146, 146, 146, 146, 146, 147, ! 147, 147, 147, 147, 148, 148, 148, 148, 148, 148, ! 148, 148, 149, 149, 149, 149, 149, 149, 149, 149, ! 150, 150, 150, 150, 151, 151, 151, 151, 152, 152, ! 152, 152, 153, 153, 153, 153, 154, 154, 154, 154, ! 154, 154, 154, 154, 155, 155, 155, 155, 155, 155, ! 155, 155, 155, 155, 155, 155, 155, 155, 155, 155, ! 156, 156, 157, 157, 158, 159, 159, 160, 161, 161, ! 161, 162, 162, 163, 163, 164, 164, 166, 165, 165, ! 168, 167, 167, 169, 169, 170, 170, 171, 172, 172, ! 173, 173, 173, 173, 173, 174, 174, 174, 174, 175, ! 176, 175, 175, 177, 177, 178, 178, 179, 179, 180, ! 179, 179, 182, 181, 181, 181, 183, 183, 184, 184, ! 184, 186, 187, 185, 189, 190, 188, 191, 191, 192, ! 192, 192, 192, 192, 193, 193, 194, 194, 194, 195, ! 195, 195, 195, 195, 196, 196, 196, 196, 196, 197, ! 197, 198, 198, 199, 199, 201, 200, 200, 202, 200, ! 200, 203, 200, 204, 200, 205, 205, 205, 206, 206, ! 207, 207, 208, 208, 209, 209, 209, 210, 210, 210, ! 210, 210, 210, 211, 211, 212, 212, 213, 213, 213, ! 214, 214, 214, 215, 215, 215, 216, 216, 218, 217, ! 219, 219, 220, 220, 220, 221, 221, 222, 222, 223, ! 223, 224, 224, 224, 224, 224, 225, 225, 225, 225, ! 225, 225, 225, 225, 225, 226, 226, 226, 226, 227, ! 227, 227, 227, 227, 228, 228, 228, 228, 229, 229, ! 229, 229, 229, 230, 230, 231, 231, 231, 231, 232, ! 233, 234, 235, 236, 237, 237, 238, 238, 239, 240, ! 240, 241, 242, 242, 243, 243, 244, 245, 246, 246, ! 248, 247, 250, 249, 251, 252, 253, 253, 254, 255, ! 256, 258, 257, 257, 257, 259, 260, 257, 257, 257, ! 261, 262, 263, 264, 257, 265, 257, 266, 266, 267, ! 267, 267, 267, 267, 267, 267, 267, 267, 267, 267, ! 267, 267, 267, 268, 268, 268, 268, 269, 269, 270, ! 270, 271, 271, 272, 272, 273, 273, 274, 274, 276, ! 275, 277, 278, 279, 277, 277, 280, 280, 280, 280, ! 281, 281, 282, 282, 282, 282, 282, 283, 283, 283, ! 283, 283, 284, 286, 285, 287, 287, 288, 288, 289, ! 289, 290 ! }; ! ! /* YYR2[YYN] -- Number of symbols composing right hand side of rule YYN. */ ! static const unsigned char yyr2[] = ! { ! 0, 2, 0, 1, 0, 2, 0, 3, 1, 1, ! 5, 2, 3, 4, 4, 2, 2, 2, 1, 0, ! 0, 9, 4, 0, 0, 9, 4, 0, 0, 8, ! 3, 1, 1, 1, 1, 1, 1, 1, 1, 1, ! 1, 0, 1, 1, 3, 1, 2, 2, 2, 2, ! 2, 4, 2, 4, 2, 2, 1, 1, 1, 1, ! 4, 1, 3, 3, 3, 3, 3, 3, 3, 3, ! 3, 3, 3, 3, 0, 4, 0, 4, 0, 0, ! 7, 0, 5, 3, 3, 1, 1, 1, 1, 0, ! 7, 3, 3, 3, 3, 4, 6, 8, 6, 4, ! 3, 3, 2, 2, 1, 2, 0, 1, 2, 3, ! 1, 1, 2, 2, 4, 4, 2, 2, 3, 0, ! 1, 4, 4, 3, 3, 2, 2, 1, 2, 2, ! 2, 2, 2, 1, 2, 1, 2, 2, 2, 2, ! 2, 2, 1, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 2, 2, 2, 2, 2, 2, 1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, ! 2, 2, 2, 2, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, ! 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, ! 0, 1, 1, 1, 1, 1, 1, 1, 1, 4, ! 4, 1, 4, 1, 4, 0, 4, 0, 6, 3, ! 0, 6, 3, 0, 1, 1, 2, 6, 1, 3, ! 0, 1, 4, 6, 4, 1, 1, 1, 1, 1, ! 0, 4, 1, 0, 2, 1, 3, 3, 2, 0, ! 4, 1, 0, 4, 1, 1, 1, 2, 2, 5, ! 3, 0, 0, 7, 0, 0, 7, 1, 1, 4, ! 3, 2, 3, 1, 1, 1, 3, 2, 1, 3, ! 2, 3, 3, 4, 3, 4, 3, 2, 1, 1, ! 2, 1, 2, 1, 2, 0, 7, 5, 0, 7, ! 5, 0, 8, 0, 7, 2, 2, 2, 0, 1, ! 0, 1, 1, 2, 0, 3, 2, 3, 4, 3, ! 1, 1, 2, 1, 4, 1, 4, 4, 6, 5, ! 4, 6, 5, 1, 3, 1, 1, 3, 0, 3, ! 0, 1, 0, 1, 2, 1, 1, 1, 3, 2, ! 3, 4, 3, 2, 2, 1, 3, 4, 2, 3, ! 3, 4, 4, 5, 5, 1, 1, 1, 1, 1, ! 2, 2, 2, 2, 1, 2, 2, 2, 1, 2, ! 2, 2, 2, 1, 2, 1, 1, 1, 1, 2, ! 0, 0, 0, 0, 0, 1, 1, 2, 3, 1, ! 2, 1, 1, 5, 1, 1, 2, 2, 2, 2, ! 0, 5, 0, 4, 0, 0, 1, 2, 3, 3, ! 3, 0, 4, 1, 3, 0, 0, 7, 5, 2, ! 0, 0, 0, 0, 12, 0, 6, 2, 1, 1, ! 2, 3, 2, 2, 2, 3, 6, 8, 10, 12, ! 3, 4, 1, 3, 5, 2, 5, 0, 1, 0, ! 1, 0, 1, 1, 3, 4, 7, 1, 3, 0, ! 3, 2, 0, 0, 6, 2, 0, 1, 1, 3, ! 1, 3, 4, 4, 3, 4, 3, 4, 4, 3, ! 4, 3, 1, 0, 3, 1, 2, 1, 3, 1, ! 3, 1 }; ! /* YYDEFACT[STATE-NAME] -- Default rule to reduce with in state ! STATE-NUM when YYTABLE doesn't specify something else to do. Zero ! means the default is an error. */ ! static const unsigned short yydefact[] = { ! 4, 0, 6, 0, 1, 0, 0, 268, 159, 265, ! 127, 353, 349, 351, 0, 58, 0, 561, 18, 5, ! 9, 8, 0, 0, 212, 213, 214, 215, 204, 205, ! 206, 207, 216, 217, 218, 219, 208, 209, 210, 211, ! 119, 119, 0, 135, 142, 262, 264, 263, 133, 285, ! 0, 0, 0, 267, 266, 0, 7, 16, 17, 354, ! 350, 352, 0, 0, 0, 348, 260, 283, 0, 273, ! 0, 162, 128, 140, 146, 130, 163, 129, 141, 147, ! 169, 131, 152, 157, 134, 170, 132, 153, 158, 180, ! 136, 138, 144, 143, 181, 137, 139, 145, 195, 148, ! 150, 155, 154, 196, 149, 151, 156, 164, 160, 178, ! 187, 166, 165, 161, 179, 188, 171, 167, 193, 202, ! 173, 172, 168, 194, 203, 182, 174, 176, 185, 184, ! 183, 175, 177, 186, 197, 189, 191, 200, 199, 198, ! 190, 192, 201, 0, 0, 15, 286, 31, 32, 374, ! 365, 374, 366, 363, 367, 11, 85, 86, 104, 56, ! 57, 0, 0, 0, 0, 0, 88, 0, 33, 35, ! 34, 0, 37, 36, 0, 38, 39, 0, 0, 40, ! 59, 0, 0, 61, 43, 45, 87, 0, 0, 290, ! 0, 240, 241, 242, 243, 236, 237, 238, 239, 398, ! 0, 232, 233, 234, 235, 261, 0, 0, 284, 12, ! 283, 30, 0, 283, 0, 0, 283, 347, 333, 260, ! 283, 0, 271, 0, 327, 328, 0, 0, 0, 0, ! 355, 0, 358, 0, 361, 54, 55, 0, 0, 0, ! 49, 46, 0, 466, 0, 0, 48, 0, 0, 0, ! 50, 0, 52, 0, 0, 78, 76, 74, 0, 0, ! 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ! 103, 102, 0, 41, 0, 0, 105, 0, 462, 454, ! 0, 47, 296, 297, 298, 295, 0, 288, 291, 269, ! 400, 270, 346, 0, 0, 120, 0, 553, 344, 0, ! 0, 418, 0, 0, 0, 28, 0, 474, 111, 475, ! 282, 0, 0, 14, 283, 22, 0, 283, 283, 331, ! 13, 26, 0, 283, 381, 376, 232, 233, 234, 235, ! 228, 229, 230, 231, 119, 119, 373, 0, 374, 283, ! 374, 395, 396, 370, 393, 0, 0, 0, 0, 92, ! 91, 0, 10, 44, 0, 0, 83, 84, 0, 0, ! 0, 0, 72, 73, 71, 70, 69, 68, 67, 62, ! 63, 64, 65, 66, 100, 0, 42, 0, 101, 94, ! 0, 0, 455, 456, 93, 0, 290, 41, 260, 283, ! 399, 401, 406, 405, 407, 415, 345, 274, 275, 0, ! 0, 0, 0, 420, 416, 0, 0, 419, 0, 449, ! 474, 113, 108, 112, 0, 280, 332, 0, 0, 20, ! 279, 330, 24, 357, 474, 474, 375, 382, 0, 360, ! 0, 0, 371, 0, 370, 0, 0, 0, 89, 60, ! 51, 53, 0, 0, 77, 75, 95, 99, 559, 0, ! 465, 434, 464, 474, 474, 474, 474, 0, 443, 0, ! 475, 429, 438, 457, 287, 289, 85, 0, 409, 529, ! 414, 283, 413, 276, 0, 557, 537, 224, 225, 220, ! 221, 226, 227, 222, 223, 119, 119, 555, 0, 538, ! 540, 554, 0, 422, 0, 0, 421, 417, 475, 109, ! 119, 119, 0, 329, 272, 275, 474, 277, 474, 377, ! 383, 475, 379, 385, 475, 283, 283, 397, 394, 283, ! 0, 0, 0, 0, 0, 79, 82, 458, 0, 435, ! 430, 439, 436, 431, 440, 475, 432, 441, 437, 433, ! 442, 444, 451, 452, 292, 0, 294, 408, 410, 0, ! 0, 529, 412, 535, 552, 402, 402, 531, 532, 0, ! 556, 0, 423, 424, 0, 116, 0, 117, 0, 302, ! 300, 299, 281, 475, 0, 475, 283, 378, 283, 0, ! 356, 359, 364, 283, 96, 0, 98, 315, 85, 0, ! 0, 312, 0, 314, 0, 368, 305, 311, 0, 0, ! 0, 560, 452, 463, 268, 0, 0, 0, 0, 0, ! 0, 517, 512, 461, 474, 0, 118, 119, 119, 0, ! 0, 450, 499, 479, 480, 0, 0, 411, 530, 338, ! 260, 283, 283, 334, 335, 283, 549, 403, 406, 260, ! 283, 283, 551, 283, 539, 212, 213, 214, 215, 204, ! 205, 206, 207, 216, 217, 218, 219, 208, 209, 210, ! 211, 119, 119, 541, 558, 0, 29, 459, 0, 0, ! 0, 0, 278, 0, 474, 0, 283, 474, 0, 283, ! 362, 0, 318, 0, 0, 309, 90, 0, 304, 0, ! 317, 308, 80, 0, 515, 502, 503, 504, 0, 0, ! 0, 518, 0, 475, 500, 0, 0, 125, 470, 485, ! 472, 490, 0, 483, 0, 0, 453, 467, 126, 293, ! 409, 529, 547, 283, 337, 283, 340, 548, 404, 409, ! 529, 550, 533, 402, 402, 460, 114, 115, 0, 21, ! 25, 384, 475, 283, 0, 387, 386, 283, 0, 390, ! 97, 0, 320, 0, 0, 306, 307, 0, 513, 505, ! 0, 510, 0, 0, 0, 123, 321, 0, 124, 324, ! 0, 0, 452, 0, 0, 0, 469, 474, 468, 489, ! 0, 501, 341, 342, 0, 336, 339, 0, 283, 283, ! 544, 283, 546, 301, 0, 389, 283, 392, 283, 0, ! 313, 310, 0, 511, 0, 283, 121, 0, 122, 0, ! 0, 0, 0, 519, 0, 484, 452, 453, 476, 474, ! 0, 343, 534, 542, 543, 545, 388, 391, 319, 514, ! 521, 0, 516, 322, 325, 0, 0, 473, 520, 498, ! 491, 0, 495, 482, 478, 477, 0, 0, 0, 0, ! 522, 523, 506, 474, 474, 471, 486, 519, 497, 452, ! 488, 0, 0, 521, 0, 0, 475, 475, 452, 0, ! 496, 0, 0, 0, 507, 524, 0, 0, 487, 492, ! 525, 0, 0, 0, 323, 326, 519, 0, 527, 0, ! 508, 0, 0, 0, 0, 493, 526, 509, 528, 452, ! 494 }; + /* YYDEFGOTO[NTERM-NUM]. */ static const short yydefgoto[] = { ! -1, 1, 2, 3, 5, 19, 20, 21, 316, 506, ! 322, 508, 215, 410, 592, 177, 244, 375, 179, 180, ! 181, 182, 22, 183, 184, 361, 360, 358, 600, 359, ! 185, 524, 186, 305, 306, 307, 499, 451, 23, 294, ! 616, 191, 192, 193, 194, 195, 196, 197, 198, 32, ! 33, 34, 35, 36, 37, 38, 39, 40, 41, 485, ! 486, 334, 205, 199, 42, 206, 43, 44, 45, 46, ! 47, 221, 68, 216, 222, 574, 69, 502, 295, 208, ! 49, 286, 287, 288, 572, 670, 594, 595, 596, 754, ! 597, 684, 598, 599, 765, 807, 853, 768, 809, 854, ! 505, 224, 632, 633, 634, 225, 50, 51, 52, 53, ! 338, 340, 345, 233, 54, 688, 433, 228, 229, 336, ! 509, 512, 510, 513, 343, 344, 200, 290, 390, 636, ! 637, 392, 393, 394, 217, 452, 453, 454, 455, 456, ! 457, 308, 279, 603, 777, 781, 381, 382, 383, 666, ! 621, 280, 459, 187, 667, 713, 714, 770, 715, 772, ! 309, 414, 817, 778, 818, 819, 716, 816, 771, 868, ! 773, 857, 886, 899, 859, 840, 623, 624, 702, 841, ! 849, 850, 851, 889, 470, 550, 487, 643, 787, 488, ! 489, 663, 490, 555, 298, 400, 491, 492, 449, 188 }; + /* YYPACT[STATE-NUM] -- Index in YYTABLE of the portion describing + STATE-NUM. */ + #define YYPACT_NINF -713 static const short yypact[] = { ! 159, 169, 177, 961, -713, 961, 441, -713, -713, -713, ! -713, 196, 196, 196, 166, -713, 192, -713, -713, -713, ! -713, -713, 213, 345, 300, 515, 1115, 1018, 458, 408, ! 796, 488, 1236, 1269, 1240, 1454, 1309, 751, 1501, 885, ! -713, -713, 208, -713, -713, -713, -713, -713, 196, -713, ! 127, 133, 150, -713, -713, 961, -713, -713, -713, 196, ! 196, 196, 2755, 229, 2673, -713, 120, 196, 163, -713, ! 1167, -713, -713, -713, -713, 196, -713, -713, -713, -713, ! -713, -713, -713, -713, 196, -713, -713, -713, -713, -713, ! -713, -713, -713, 196, -713, -713, -713, -713, -713, -713, ! -713, -713, 196, -713, -713, -713, -713, -713, -713, -713, ! -713, 196, -713, -713, -713, -713, -713, -713, -713, -713, ! 196, -713, -713, -713, -713, -713, -713, -713, -713, 196, ! -713, -713, -713, -713, -713, -713, -713, -713, 196, -713, ! -713, -713, -713, 501, 345, -713, -713, -713, -713, -713, ! 245, -713, 248, -713, 255, -713, -713, -713, -713, -713, ! -713, 2755, 2755, 330, 343, 357, -713, 534, -713, -713, ! -713, 2755, -713, -713, 1774, -713, -713, 2755, 275, 342, ! -713, 2796, 2837, -713, 3084, 755, 424, 1536, 2755, 615, ! 359, 1022, 784, 1163, 3080, 1077, 719, 1743, 1102, -713, ! 367, 258, 460, 287, 469, -713, 345, 345, 196, -713, ! 196, -713, 413, 196, 2206, 358, 196, -713, -713, 120, ! 196, 238, -713, 447, 499, 502, 289, 2141, 421, 930, ! -713, 425, -713, 482, -713, -713, -713, 2755, 2755, 3049, ! -713, -713, 430, -713, 451, 456, -713, 446, 2755, 1774, ! -713, 1774, -713, 2755, 2755, 462, -713, -713, 2755, 2755, ! 2755, 2755, 2755, 2755, 2755, 2755, 2755, 2755, 2755, 2755, ! -713, -713, 534, 2755, 2755, 534, -713, 463, -713, 542, ! 496, -713, -713, -713, -713, -713, 122, -713, 524, -713, ! 224, -713, 502, 351, 345, -713, 586, -713, -713, 2673, ! 2307, -713, 508, 2247, 518, -713, 111, 79, -713, -713, ! 568, 501, 501, -713, 196, -713, 358, 196, 196, -713, ! -713, -713, 358, 196, -713, -713, 1022, 784, 1163, 3080, ! 1077, 719, 1743, 1102, -713, 493, 550, 2169, -713, 196, ! -713, -713, 595, 555, -713, 482, 2942, 2960, 557, -713, ! -713, 2548, -713, 3084, 564, 570, 3084, 3084, 2755, 605, ! 2755, 2755, 2510, 1799, 1464, 2635, 783, 997, 997, 308, ! 308, -713, -713, -713, -713, 574, 342, 569, -713, -713, ! 534, 1391, 542, -713, -713, 578, 615, 2878, 120, 196, ! -713, -713, -713, -713, 516, -713, -713, -713, 179, 89, ! 1211, 585, 2755, -713, -713, 2755, 2348, -713, 601, -713, ! -713, -713, -713, -713, 1373, -713, 499, 432, 501, -713, ! 650, -713, -713, -713, -713, -713, -713, -713, 614, -713, ! 616, 2755, 534, 620, 555, 3049, 2755, 3049, -713, -713, ! 630, 630, 677, 2755, 3113, 2064, -713, -713, -713, 292, ! 518, -713, -713, 78, 93, 96, 118, 737, -713, 659, ! -713, -713, -713, -713, -713, -713, 155, 667, 224, 224, ! -713, 196, -713, -713, 679, -713, -713, 2050, 1458, 690, ! 772, 2317, 2079, 740, 1299, -713, -713, -713, 683, 310, ! -713, -713, 189, -713, 652, 681, -713, -713, -713, -713, ! 696, 699, 2039, -713, -713, 760, -713, -713, -713, 705, ! -713, -713, 706, -713, -713, 196, 196, 3084, -713, 196, ! 682, 717, 2984, 721, 1838, -713, 3100, -713, 534, -713, ! -713, -713, -713, -713, -713, -713, -713, -713, -713, -713, ! -713, -713, -713, 2418, -713, 2755, -713, -713, -713, 722, ! 855, -713, -713, -713, -713, 321, 283, -713, -713, 1336, ! -713, 803, -713, -713, 73, -713, 501, -713, 345, -713, ! -713, 3084, -713, -713, 2039, -713, 196, 547, 196, 366, ! -713, -713, -713, 196, -713, 2755, -713, -713, 761, 534, ! 2755, -713, 767, 3084, 734, 739, -713, -713, 211, 1972, ! 2755, -713, 2487, -713, 786, 2755, 798, 745, 746, 2714, ! 265, 842, -713, -713, -713, 768, -713, -713, -713, 769, ! 986, 770, -713, -713, -713, 2612, 215, -713, -713, -713, ! 120, 196, 196, 598, 644, 218, -713, -713, 196, 120, ! 196, 218, -713, 196, -713, 2050, 1458, 2458, 2527, 690, ! 772, 1063, 1569, 2317, 2079, 3045, 3076, 740, 1299, 1377, ! 1656, -713, -713, -713, -713, 774, -713, -713, 313, 320, ! 1838, 73, -713, 73, -713, 2755, 130, -713, 2755, 457, ! -713, 1556, -713, 1440, 1838, -713, -713, 1905, -713, 2101, ! -713, -713, 3100, 2923, -713, -713, -713, -713, 780, 2755, ! 782, -713, 804, -713, -713, 501, 345, -713, -713, -713, ! -713, -713, 806, 861, 1623, 107, -713, -713, -713, -713, ! 321, 333, -713, 196, -713, 196, -713, -713, 196, 283, ! 283, -713, -713, 321, 283, -713, -713, -713, 793, -713, ! -713, -713, -713, 1643, 2755, -713, -713, 1643, 2755, -713, ! -713, 2755, -713, 794, 2101, -713, -713, 2755, -713, -713, ! 797, -713, 2755, 836, 322, -713, 606, 355, -713, 655, ! 820, 821, -713, 823, 2755, 1710, -713, -713, -713, -713, ! 2755, -713, 598, 644, 466, -713, -713, 855, 196, 218, ! -713, 218, -713, -713, 547, -713, 1643, -713, 1643, 2898, ! -713, -713, 3066, -713, 60, 196, -713, 358, -713, 358, ! 2755, 2755, 878, 2612, 817, -713, -713, -713, -713, -713, ! 818, -713, -713, -713, -713, -713, -713, -713, -713, -713, ! 140, 819, -713, -713, -713, 833, 834, -713, -713, -713, ! -713, 835, -713, -713, -713, -713, 838, 852, 534, 63, ! 814, -713, -713, -713, -713, -713, -713, 2755, -713, -713, ! -713, 2755, 837, 140, 839, 140, -713, -713, -713, 844, ! -713, 843, 924, 112, -713, -713, 774, 774, -713, -713, ! -713, 873, 586, 875, -713, -713, 2755, 2755, 424, 233, ! -713, 874, 880, 886, 586, -713, -713, -713, 424, -713, ! -713 }; + /* YYPGOTO[NTERM-NUM]. */ static const short yypgoto[] = { ! -713, -713, -713, -713, -713, 102, -713, -713, -713, -713, ! -713, -713, -713, -713, 82, -713, -62, 584, -252, 548, ! -713, -713, -713, -107, 687, -713, -713, -713, -713, -713, ! -713, -713, -270, -300, 665, -713, -713, 100, 11, -295, ! -580, 2, 5, 37, 38, 41, 44, -2, 45, -380, ! -342, 418, 420, -341, -331, 426, 427, -481, -458, 573, ! 576, -713, -153, -109, -511, -202, 582, 654, 678, 876, ! -713, -476, -133, -208, 566, -713, 700, -713, 253, 1, ! 27, -713, 607, -713, 428, -713, -529, -713, 325, -713, ! -563, -713, -713, 397, -713, -713, -713, -713, -713, -713, ! -120, 423, 264, 293, 40, 7, -713, -713, -713, -713, ! -713, -713, -713, -713, -713, -713, 583, -85, -713, 670, ! -713, -713, 344, 339, 675, 589, -52, -713, -713, -474, ! -281, -373, -440, -713, 365, -713, -713, -713, -713, -713, ! -713, -215, -713, -713, -401, 216, -713, -713, 658, -182, ! -713, 416, -713, -713, -525, -713, -713, -713, -713, -713, ! 657, -350, 220, -688, -192, -145, -713, -713, -713, -713, ! -713, -713, -713, -713, -713, -713, -713, -713, -713, -712, ! 180, -713, 197, -713, 590, -713, -512, -713, -713, -713, ! -713, -713, -713, 579, -294, -713, -713, -713, -713, 58 }; ! /* YYTABLE[YYPACT[STATE-NUM]]. What to do in state STATE-NUM. If ! positive, shift that token. If negative, reduce the rule which ! number is the opposite. If zero, do what YYDEFACT says. ! If YYTABLE_NINF, syntax error. */ ! #define YYTABLE_NINF -537 static const short yytable[] = { ! 178, 30, 190, 30, 48, 24, 48, 24, 25, 391, ! 25, 226, 59, 60, 61, 317, 419, 311, 622, 418, ! 481, 376, 422, 223, 421, 75, 399, 84, 548, 93, ! 70, 102, 619, 111, 481, 120, 691, 129, 628, 138, ! 26, 27, 26, 27, 28, 718, 28, 29, 31, 29, ! 31, 143, 144, 30, 235, 236, 48, 24, 482, 483, ! 25, 55, 617, 55, 241, 48, 231, 48, 201, 484, ! 246, 202, 482, 483, 665, 146, 335, 622, 661, -445, ! -107, 281, 642, 484, 812, 618, 146, 146, 146, 412, ! 668, 411, 26, 27, -446, 547, 28, -447, 276, 29, ! 31, 662, 146, 203, 204, 303, 830, 56, 779, 863, ! 543, 146, 304, 55, 619, -110, -110, -110, -110, -448, ! 146, -110, 245, -110, -110, -110, 756, 10, 843, 146, ! 147, 148, 150, 152, 154, 376, 147, 148, 146, -110, ! 735, 738, 620, 831, 617, 869, 864, 146, 564, 847, ! 16, 227, 302, 147, 148, 753, 146, 155, 882, -2, ! 16, 577, 613, -425, 579, 146, 458, 618, -107, 4, ! 481, 870, 473, 780, 891, 48, 744, -3, -426, 653, ! 878, -427, 638, 638, 335, 602, 468, 348, 549, 461, ! 402, 801, 75, 241, 84, 883, 93, 354, 102, 355, ! -110, 620, 75, -428, 84, 385, 212, 848, 482, 483, ! 386, 900, 377, 292, 293, 48, 149, 654, 657, 484, ! 48, 201, 151, 671, 202, 673, 16, 332, 658, 764, ! 48, 326, 62, 839, 327, 146, 462, 401, 544, 153, ! 48, 408, 541, 545, 439, 213, 214, 209, 16, 240, ! 48, 210, 48, 428, 689, 430, 203, 204, 63, 790, ! 792, 530, 533, 536, 539, 72, 328, 329, 147, 148, ! 330, 285, 560, 331, 333, 822, 589, 561, 590, 64, ! 548, 674, 388, 677, 213, 214, 65, 337, 16, 548, ! 389, 214, 145, 626, 81, 189, 442, 317, 719, 241, ! 48, 398, 619, 248, 7, 71, 9, 72, 531, 534, ! 537, 540, 11, 12, 13, 342, 893, 16, 292, 293, ! 207, 894, 313, 699, 65, 629, 314, 75, 15, 84, ! 16, 93, 617, 102, 230, 332, 65, 232, 48, 326, ! 494, 639, 327, 495, 234, 424, 425, 547, 65, 640, ! 214, 884, 885, 763, 374, 618, 547, 378, 247, 304, ! 638, 638, -474, -474, -474, -474, 267, 268, 269, 65, ! -474, -474, -474, 320, 328, 329, 527, 210, 330, 630, ! 528, 331, 333, 521, -244, 523, -474, 631, 214, 48, ! 201, 630, 794, 202, 558, 337, 237, 736, 559, 631, ! 214, 314, 477, 66, 737, 478, 806, 481, 210, 238, ! 314, 67, 678, 94, 9, 95, 477, 213, 214, 478, ! 11, 12, 13, 239, 66, 203, 204, 342, 720, 785, ! 248, 786, 67, 276, 396, 669, 48, 729, 48, 808, ! 549, 479, 289, 210, 480, 482, 483, -106, 315, 549, ! 291, -19, -19, -19, -19, 479, 484, 676, 480, -19, ! -19, -19, 448, 89, 9, 90, 297, 77, 285, 310, ! 11, 12, 13, 312, 212, -19, 86, -275, 75, 296, ! 93, 615, 111, 341, 129, 147, 148, 16, 16, 739, ! -275, 740, -249, 103, 9, 104, 554, 554, 318, 214, ! 11, 12, 13, 748, 65, 218, 323, 833, -81, 834, ! 339, 566, 568, 349, 342, 503, 876, 877, 281, 7, ! 76, 9, 77, 213, 214, 57, 58, 11, 12, 13, ! 352, -275, 725, 214, 350, -275, -19, 147, 148, 351, ! 615, 30, -248, 15, 48, 24, 379, 698, 25, 821, ! 65, 218, 477, 529, 532, 478, 538, 651, 317, 219, ! 48, 645, 635, 641, 646, 318, 214, 220, 213, 214, ! 420, 297, -251, 767, 380, 398, 423, -380, -380, 384, ! 26, 27, 471, 214, 28, 766, 679, 29, 31, 319, ! 387, 479, 429, 675, 480, 158, 647, 648, 404, -245, ! 649, 625, 409, 650, 652, 219, 73, 78, 82, 87, ! 601, 415, 888, 220, 109, 114, 118, 123, 147, 148, ! 282, 283, 284, 30, 898, 614, 48, 24, 705, 706, ! 25, 48, 201, 212, 426, 202, -275, 760, 431, 728, ! 48, 201, 469, 432, 202, 437, 75, 440, 84, -275, ! 93, 443, 102, 441, 111, 395, 120, 446, 129, 447, ! 138, 464, 26, 27, 723, 214, 28, 203, 204, 29, ! 31, 682, 733, 734, 676, 493, 203, 204, 74, 79, ! 83, 88, 212, 625, 614, -275, 110, 115, 119, 124, ! -275, 497, 700, 507, -275, 89, 9, 90, -275, 515, ! 804, 516, 11, 12, 13, 519, 91, 96, 100, 105, ! 725, 214, 814, 769, 127, 132, 136, 141, 820, 438, ! 16, 213, 214, 525, 551, 9, 95, 292, 293, 250, ! 252, 11, 12, 13, 416, 417, 292, 293, 304, -275, ! 789, 791, 562, -275, 542, 125, 9, 126, 835, 836, ! 546, 838, 11, 12, 13, 146, 130, 9, 131, 472, ! 783, 784, 553, 11, 12, 13, 557, 583, 580, 581, ! 16, 563, 582, 73, 78, 82, 87, 94, 9, 95, ! 565, 319, 319, 567, 11, 12, 13, 212, 7, 477, ! 9, 77, 478, 576, 578, 838, 11, 12, 13, 871, ! 584, 98, 9, 99, 586, 627, 664, -31, 11, 12, ! 13, 30, 15, 685, 48, 24, 270, 271, 25, 686, ! 272, 273, 274, 275, 838, 892, 16, 687, 479, 695, ! 696, 480, -32, 395, 395, -257, 680, 263, 264, 265, ! 266, 267, 268, 269, 694, 74, 79, 83, 88, 701, ! 26, 27, 704, 707, 28, 278, 474, 29, 31, 7, ! 8, 9, 10, 613, 759, 476, 761, 11, 12, 13, ! 762, 625, 774, 91, 96, 100, 105, 775, 793, 800, ! -250, 803, 805, 15, 721, 722, 810, 811, 727, 813, ! 139, 9, 140, 730, 731, 837, 732, 11, 12, 13, ! 842, 846, 865, 852, 92, 97, 101, 106, 73, 78, ! 82, 87, 128, 133, 137, 142, 855, 856, 861, 858, ! 395, 395, 860, 874, 346, 347, 880, 872, 879, 745, ! 862, 324, 749, 881, 7, 353, 9, 10, -536, 887, ! 356, 357, 11, 12, 13, 362, 363, 364, 365, 366, ! 367, 368, 369, 370, 371, 372, 373, 895, 15, 890, ! 16, 17, 6, 896, -119, 7, 8, 9, 10, -259, ! 897, 467, 413, 11, 12, 13, 297, 655, 297, 656, ! 74, 79, 83, 88, 504, 659, 660, 500, 14, 15, ! 501, 16, 17, 465, 397, 690, 795, 788, 724, 726, ! 797, 708, 672, 709, 710, 711, 712, 427, 91, 96, ! 100, 105, 755, 782, 325, -372, 746, 520, 741, -119, ! 434, 518, 7, 85, 9, 86, 7, -119, 9, 72, ! 11, 12, 13, 844, 11, 12, 13, 717, 460, 845, ! 463, 823, 824, 873, 825, 18, 15, 444, 445, 826, ! 15, 827, 16, 265, 266, 267, 268, 269, 832, 73, ! 78, 552, 875, 109, 114, 556, 0, 498, 98, 9, ! 99, 92, 97, 101, 106, 11, 12, 13, 0, 0, ! 0, 511, 514, 9, 90, 395, 395, 0, 0, 11, ! 12, 13, 0, 16, 395, 395, 0, 0, 395, 395, ! 0, 0, -247, 0, 0, 0, 0, 16, 9, 104, ! 460, 460, 535, 460, 11, 12, 13, 0, 517, 7, ! 80, 9, 81, 522, 0, 0, 0, 11, 12, 13, ! 526, 74, 79, 0, 0, 110, 115, 0, 0, 0, ! 0, 0, 0, 15, 0, 16, 0, 724, 726, 726, ! 0, 0, 0, 0, 0, 0, 0, 91, 96, 0, ! 0, 127, 132, 573, 0, 575, 0, 7, 211, 9, ! 81, -27, -27, -27, -27, 11, 12, 13, 0, -27, ! -27, -27, 0, 0, 0, 0, 0, 0, 0, 571, ! 0, 15, 0, 16, 212, -27, 0, -275, 0, -246, ! 0, 0, 0, 0, 0, 0, 92, 97, 101, 106, ! -275, 593, 474, 0, 475, 7, 8, 9, 10, 0, ! 0, 476, 0, 11, 12, 13, 0, 73, 78, 82, ! 87, 0, 0, 213, 214, 109, 114, 118, 123, 15, ! 7, 107, 9, 108, 7, 116, 9, 117, 11, 12, ! 13, -275, 11, 12, 13, -275, -27, 0, 0, 0, ! 0, 571, 0, 0, 15, 0, 16, 0, 15, 0, ! 16, 703, 681, 7, 112, 9, 113, 683, 0, 0, ! 0, 11, 12, 13, 0, 0, 593, 692, 0, 0, ! 0, 0, 693, 0, -536, 0, 0, 15, 0, 74, ! 79, 83, 88, 0, 130, 9, 131, 110, 115, 119, ! 124, 11, 12, 13, 125, 9, 126, 0, 0, 0, ! -252, 11, 12, 13, -254, 0, 0, 91, 96, 100, ! 105, 742, 0, 0, 514, 127, 132, 136, 141, 16, ! 7, 8, 9, 10, 0, 0, 644, 0, 11, 12, ! 13, 0, 0, -253, 0, 92, 97, 593, 0, 128, ! 133, 0, 743, 0, 15, 747, 16, 0, 0, 0, ! 0, 593, 0, 0, 593, 0, 593, 7, 8, 9, ! 10, 0, 134, 9, 135, 11, 12, 13, 0, 11, ! 12, 13, 450, -256, -474, -474, -474, -474, -474, -474, ! -474, 15, -474, -474, -474, -474, -474, 16, -474, -474, ! -474, -474, -474, -474, -474, -474, -474, -474, -474, -474, ! -474, -474, -474, 0, -474, -474, -474, -474, -474, 0, ! 0, 796, 0, -474, 535, 798, 0, 0, 799, -474, ! 0, 593, -474, 0, 802, 0, 0, -474, -474, -474, ! 751, 0, -474, -474, 0, 0, 0, -474, 7, 121, ! 9, 122, 7, 76, 9, 77, 11, 12, 13, 0, ! 11, 12, 13, 0, 0, -474, 535, -474, -474, 0, ! -474, 0, 15, 253, 254, 255, 15, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, ! 269, 0, 0, 0, 0, 0, 134, 9, 135, 0, ! 866, 867, 0, 11, 12, 13, 261, 262, 263, 264, ! 265, 266, 267, 268, 269, 92, 97, 101, 106, 0, ! 752, 16, 0, 128, 133, 137, 142, 277, -255, -450, ! -450, -450, -450, -450, -450, -450, 0, -450, -450, -450, ! -450, -450, 0, -450, -450, -450, -450, -450, -450, -450, ! -450, -450, -450, -450, -450, -450, -450, -450, -450, -450, ! -450, -450, -450, -450, 103, 9, 104, 0, -450, 0, ! 0, 11, 12, 13, -450, -258, 0, -450, 0, 0, ! 0, 0, -450, -450, -450, 0, 0, -450, -450, 253, ! 254, 255, -450, 256, 257, 258, 259, 260, 261, 262, ! 263, 264, 265, 266, 267, 268, 269, 0, 0, 0, ! -450, 278, -450, -450, 776, -450, -452, -452, 0, 0, ! 0, -452, -452, 0, -452, 0, 0, 0, -452, 750, ! -452, -452, -452, -452, -452, -452, -452, -452, -452, -452, ! -452, 0, -452, 0, -452, 0, -452, -452, -452, -452, ! -452, 139, 9, 140, 0, -452, 0, 0, 11, 12, ! 13, -452, 0, 16, -452, 0, 0, 0, 0, -452, ! -452, -452, 0, 0, -452, -452, 253, 254, 255, -452, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, ! 266, 267, 268, 269, 0, 0, 0, -452, 0, -452, ! -452, 815, -452, -481, -481, 0, 0, 0, -481, -481, ! 0, -481, 0, 0, 0, -481, 0, -481, -481, -481, ! -481, -481, -481, -481, -481, -481, -481, -481, 0, -481, ! 0, -481, 0, -481, -481, -481, -481, -481, 0, 9, ! 99, 0, -481, 0, 0, 11, 12, 13, -481, 0, ! 0, -481, 0, 0, 0, 0, -481, -481, -481, 0, ! 0, -481, -481, 16, 0, 242, -481, 156, 7, 0, ! 9, 10, 157, 158, 0, 159, 11, 12, 13, 0, ! 0, 0, 0, 0, -481, 0, -481, -481, 0, -481, ! 0, 0, 15, 160, 16, 17, 0, 161, 162, 163, ! 164, 165, 0, 0, 0, 0, 166, 0, 0, 0, ! 0, 0, 167, 0, 0, 168, 0, 0, 0, 0, ! 169, 170, 171, 0, 0, 172, 173, 0, 0, 587, ! 174, 588, 148, 0, 0, 0, 157, 158, 0, 159, ! 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, ! 175, 176, 0, 243, 0, 0, 0, 160, 0, 17, ! 0, 161, 162, 163, 164, 165, 0, 0, 0, 0, ! 166, 0, 0, 0, 0, 0, 167, 0, 0, 168, ! 0, 0, 0, 0, 169, 170, 171, 0, 0, 172, ! 173, 0, 0, 589, 174, 590, 587, 0, 588, 148, ! 0, 0, 0, 157, 158, 0, 159, 0, 0, 0, ! 0, 0, 0, -303, 175, 176, 0, 591, 0, 0, ! 0, 0, 0, 0, 160, 0, 17, 0, 161, 162, ! 163, 164, 165, 0, 0, 0, 0, 166, 0, 0, ! 0, 0, 0, 167, 0, 0, 168, 0, 0, 0, ! 0, 169, 170, 171, 0, 0, 172, 173, 0, 0, ! 589, 174, 590, 587, 0, 156, 0, 0, 0, 0, ! 157, 158, 0, 159, 0, 0, 0, 0, 0, 0, ! -369, 175, 176, 0, 591, 0, 0, 0, 0, 0, ! 0, 160, 0, 17, 0, 161, 162, 163, 164, 165, ! 0, 0, 0, 0, 166, -316, 0, 0, 0, 0, ! 167, 0, 0, 168, 0, 0, 0, 0, 169, 170, ! 171, 0, 0, 172, 173, 0, 0, -316, 174, -316, ! 569, 0, 156, 0, 0, 0, 0, 157, 158, 0, ! 159, 0, 0, 0, 7, 71, 9, 72, 175, 176, ! 0, 591, 11, 12, 13, 0, 0, 0, 160, 0, ! 17, 0, 161, 162, 163, 164, 165, 0, 15, 0, ! 16, 166, 0, 7, 112, 9, 113, 167, 0, 0, ! 168, 11, 12, 13, 0, 169, 170, 171, 0, 0, ! 172, 173, 587, 0, 156, 174, 0, 15, 0, 157, ! 158, 0, 159, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 268, 269, 175, 176, 0, 570, 0, ! 160, 0, 17, 0, 161, 162, 163, 164, 165, 0, ! 0, 0, 321, 166, 0, -23, -23, -23, -23, 167, ! 0, 0, 168, -23, -23, -23, 0, 169, 170, 171, ! 0, 0, 172, 173, 0, 0, 0, 174, 212, -23, ! 324, -275, 0, 7, 0, 9, 10, 0, 0, 0, ! 0, 11, 12, 13, -275, 0, 0, 175, 176, 0, ! 591, 0, 0, 0, 0, 0, 0, 15, 0, 16, ! 17, 0, 0, 0, 0, 0, 0, 213, 214, 156, ! 7, 299, 9, 10, 157, 158, 0, 159, 11, 12, ! 13, 0, 0, 0, 0, -275, 0, 0, 0, -275, ! -23, 0, 0, 0, 15, 160, 16, 17, 0, 161, ! 162, 163, 164, 165, 0, 0, 0, 0, 166, 0, ! 156, 0, 405, 0, 167, 157, 158, 168, 159, 0, ! 0, 0, 169, 170, 300, 0, 0, 172, 173, 0, ! 0, 0, 174, 0, 0, 0, 160, 0, 17, 0, ! 161, 162, 163, 164, 165, 0, 0, 0, 0, 166, ! 0, 0, 175, 176, 0, 167, 301, 0, 168, 0, ! 0, 0, 0, 169, 170, 406, 0, 0, 172, 173, ! 156, 0, 0, 174, 0, 157, 158, 0, 159, 0, ! 0, 7, 107, 9, 108, 0, 0, 0, 0, 11, ! 12, 13, 0, 175, 176, 0, 160, 407, 17, 0, ! 161, 162, 163, 164, 165, 15, 0, 16, 0, 166, ! 0, 156, 0, 0, 0, 167, 157, 158, 168, 159, ! 0, 0, 0, 169, 170, 171, 0, 0, 172, 173, ! 0, 0, 0, 174, 0, 0, 0, 160, 0, 17, ! 0, 161, 162, 163, 164, 165, 0, 0, 0, 0, ! 166, 0, 0, 175, 176, 0, 167, 403, 0, 168, ! 0, 0, 0, 0, 169, 170, 171, 0, 0, 172, ! 173, 0, 0, 0, 174, 0, 0, 0, 0, 0, ! 0, 588, 604, 8, 9, 10, 157, 158, 0, 159, ! 11, 12, 13, 0, 175, 176, 0, 0, 496, 605, ! 606, 607, 608, 609, 610, 611, 15, 160, 16, 17, ! 0, 161, 162, 163, 164, 165, 0, 0, 0, 0, ! 166, 0, 7, 80, 9, 81, 167, 0, 0, 168, ! 11, 12, 13, 0, 169, 170, 171, 0, 0, 172, ! 173, 0, 0, 0, 174, 0, 15, 0, 16, 0, ! 588, 148, 0, 0, 0, 157, 158, 0, 159, 0, ! 0, 0, 612, 0, 175, 176, 0, 613, 605, 606, ! 607, 608, 609, 610, 611, 0, 160, 0, 17, 0, ! 161, 162, 163, 164, 165, 0, 0, 0, 0, 166, ! 0, 7, 85, 9, 86, 167, 0, 0, 168, 11, ! 12, 13, 0, 169, 170, 171, 0, 0, 172, 173, ! 0, 156, 0, 174, 0, 15, 157, 158, 0, 159, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, ! 269, 612, 0, 175, 176, 0, 613, 160, 0, 17, ! 0, 161, 162, 163, 164, 165, 0, 0, 0, 0, ! 166, 0, 0, 0, 0, 0, 167, 0, 0, 168, ! 0, 0, 0, 0, 169, 170, 171, 0, 0, 172, ! 173, 0, 0, 0, 174, 156, 7, 8, 9, 10, ! 157, 158, 0, 159, 11, 12, 13, 0, 0, 0, ! 0, 0, 0, 0, 175, 176, 0, 438, 0, 0, ! 15, 160, 16, 17, 0, 161, 162, 163, 164, 165, ! 0, 0, 0, 0, 166, 0, 0, 0, 0, 0, ! 167, 0, 0, 168, 0, 0, 0, 0, 169, 170, ! 171, 0, 0, 172, 173, 0, 156, 7, 174, 9, ! 10, 157, 158, 0, 159, 11, 12, 13, 262, 263, ! 264, 265, 266, 267, 268, 269, 0, 0, 175, 176, ! 0, 15, 160, 16, 17, 0, 161, 162, 163, 164, ! 165, 0, 0, 0, 0, 166, 0, 156, 0, 0, ! 0, 167, 157, 158, 168, 159, 0, 0, 0, 169, ! 170, 171, 0, 0, 172, 173, 0, 0, 0, 174, ! 0, 0, 0, 160, 0, 17, 0, 161, 162, 163, ! 164, 165, 0, 0, 0, 0, 166, 0, 156, 175, ! 176, 0, 167, 157, 158, 168, 159, 0, 0, 0, ! 169, 170, 171, 0, 0, 172, 173, 0, 0, 0, ! 174, 0, 0, 0, 160, 0, 17, 0, 161, 162, ! 163, 164, 165, 0, 0, 0, 0, 166, 697, 156, ! 175, 176, 0, 167, 157, 158, 168, 159, 0, 0, ! 0, 169, 170, 171, 0, 0, 172, 173, 0, 0, ! 0, 174, 0, 0, 0, 160, 0, 17, 0, 161, ! 162, 163, 164, 165, 0, 0, 0, 0, 166, 0, ! 156, 175, 176, 0, 167, 157, 158, 168, 159, 0, ! 0, 0, 169, 170, 171, 0, 0, 172, 173, 0, ! 0, 0, 249, 0, 0, 0, 160, 0, 17, 0, ! 161, 162, 163, 164, 165, 0, 0, 0, 0, 166, ! 0, 466, 175, 176, 0, 167, 157, 158, 168, 159, ! 0, 0, 0, 169, 170, 171, 0, 0, 172, 173, ! 0, 0, 0, 251, 0, 0, 0, 160, 0, 17, ! 0, 161, 162, 163, 164, 165, 0, 0, 0, 0, ! 166, 0, 0, 175, 176, 0, 167, 0, 0, 168, ! 0, 0, 0, 757, 169, 170, 171, 0, 0, 172, ! 173, 253, 254, 255, 174, 256, 257, 258, 259, 260, ! 261, 262, 263, 264, 265, 266, 267, 268, 269, 0, ! 0, 0, 0, 0, 175, 176, 253, 254, 255, 758, ! 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, ! 266, 267, 268, 269, 0, 253, 254, 255, 828, 256, ! 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, ! 267, 268, 269, 253, 254, 255, 0, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, ! 269, 0, 0, 0, 0, 0, 0, 253, 254, 255, ! 435, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 268, 269, 0, 0, 0, 436, 7, ! 116, 9, 117, 7, 0, 9, 10, 11, 12, 13, ! 0, 11, 12, 13, 0, 0, 0, 0, 0, 0, ! 0, 0, 585, 15, 0, 16, 0, 15, 0, 16, ! 7, 121, 9, 122, 7, 0, 9, 86, 11, 12, ! 13, 0, 11, 12, 13, 0, 0, 0, 0, 0, ! 0, 0, 0, 0, 15, 0, 0, 0, 15, 253, ! 254, 255, 829, 256, 257, 258, 259, 260, 261, 262, ! 263, 264, 265, 266, 267, 268, 269, 253, 254, 255, ! 0, 256, 257, 258, 259, 260, 261, 262, 263, 264, ! 265, 266, 267, 268, 269, 255, 0, 256, 257, 258, ! 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, ! 269, 257, 258, 259, 260, 261, 262, 263, 264, 265, ! 266, 267, 268, 269 }; static const short yycheck[] = { ! 62, 3, 64, 5, 3, 3, 5, 5, 3, 290, ! 5, 144, 11, 12, 13, 223, 316, 219, 543, 314, ! 400, 273, 322, 143, 318, 24, 296, 26, 468, 28, ! 23, 30, 543, 32, 414, 34, 599, 36, 550, 38, ! 3, 3, 5, 5, 3, 625, 5, 3, 3, 5, ! 5, 40, 41, 55, 161, 162, 55, 55, 400, 400, ! 55, 3, 543, 5, 171, 64, 151, 66, 66, 400, ! 177, 66, 414, 414, 1, 48, 229, 602, 559, 1, ! 1, 188, 556, 414, 772, 543, 59, 60, 61, 10, ! 566, 306, 55, 55, 1, 468, 55, 1, 9, 55, ! 55, 559, 75, 66, 66, 214, 46, 5, 1, 46, ! 460, 84, 1, 55, 625, 4, 5, 6, 7, 1, ! 93, 10, 174, 12, 13, 14, 689, 7, 816, 102, ! 3, 4, 50, 51, 52, 387, 3, 4, 111, 28, ! 665, 670, 543, 83, 625, 857, 83, 120, 498, 9, ! 30, 144, 214, 3, 4, 684, 129, 55, 46, 0, ! 30, 511, 89, 85, 514, 138, 381, 625, 89, 0, ! 550, 859, 83, 66, 886, 174, 46, 0, 85, 559, ! 868, 85, 555, 556, 337, 535, 388, 239, 469, 381, ! 299, 754, 191, 300, 193, 83, 195, 249, 197, 251, ! 89, 602, 201, 85, 203, 83, 27, 67, 550, 550, ! 88, 899, 274, 206, 207, 214, 89, 559, 559, 550, ! 219, 219, 89, 573, 219, 575, 30, 229, 559, 705, ! 229, 229, 66, 813, 229, 208, 381, 299, 83, 89, ! 239, 303, 457, 88, 351, 66, 67, 84, 30, 167, ! 249, 88, 251, 338, 43, 340, 219, 219, 66, 733, ! 734, 453, 454, 455, 456, 7, 229, 229, 3, 4, ! 229, 189, 83, 229, 229, 787, 65, 88, 67, 66, ! 720, 576, 58, 578, 66, 67, 3, 229, 30, 729, ! 66, 67, 84, 545, 7, 66, 358, 505, 83, 406, ! 299, 294, 813, 88, 4, 5, 6, 7, 453, 454, ! 455, 456, 12, 13, 14, 233, 83, 30, 311, 312, ! 67, 88, 84, 58, 3, 4, 88, 326, 28, 328, ! 30, 330, 813, 332, 89, 337, 3, 89, 337, 337, ! 402, 58, 337, 405, 89, 334, 335, 720, 3, 66, ! 67, 876, 877, 703, 272, 813, 729, 275, 83, 1, ! 733, 734, 4, 5, 6, 7, 58, 59, 60, 3, ! 12, 13, 14, 84, 337, 337, 84, 88, 337, 58, ! 88, 337, 337, 435, 84, 437, 28, 66, 67, 388, ! 388, 58, 742, 388, 84, 337, 66, 84, 88, 66, ! 67, 88, 400, 58, 84, 400, 84, 787, 88, 66, ! 88, 66, 46, 5, 6, 7, 414, 66, 67, 414, ! 12, 13, 14, 66, 58, 388, 388, 345, 630, 723, ! 88, 725, 66, 9, 83, 568, 435, 639, 437, 84, ! 721, 400, 83, 88, 400, 787, 787, 89, 1, 730, ! 83, 4, 5, 6, 7, 414, 787, 577, 414, 12, ! 13, 14, 380, 5, 6, 7, 213, 7, 386, 216, ! 12, 13, 14, 220, 27, 28, 7, 30, 477, 66, ! 479, 543, 481, 1, 483, 3, 4, 30, 30, 671, ! 43, 673, 84, 5, 6, 7, 485, 486, 66, 67, ! 12, 13, 14, 46, 3, 4, 85, 807, 46, 809, ! 85, 500, 501, 83, 432, 83, 866, 867, 625, 4, ! 5, 6, 7, 66, 67, 84, 85, 12, 13, 14, ! 84, 84, 66, 67, 83, 88, 89, 3, 4, 83, ! 602, 543, 84, 28, 543, 543, 83, 609, 543, 83, ! 3, 4, 550, 453, 454, 550, 456, 559, 766, 58, ! 559, 559, 555, 556, 559, 66, 67, 66, 66, 67, ! 317, 318, 84, 706, 32, 568, 323, 84, 85, 83, ! 543, 543, 66, 67, 543, 705, 579, 543, 543, 224, ! 66, 550, 339, 46, 550, 9, 559, 559, 90, 84, ! 559, 543, 84, 559, 559, 58, 24, 25, 26, 27, ! 528, 43, 882, 66, 32, 33, 34, 35, 3, 4, ! 5, 6, 7, 625, 894, 543, 625, 625, 617, 618, ! 625, 630, 630, 27, 84, 630, 30, 699, 43, 638, ! 639, 639, 389, 88, 639, 88, 645, 83, 647, 43, ! 649, 46, 651, 83, 653, 290, 655, 83, 657, 90, ! 659, 83, 625, 625, 66, 67, 625, 630, 630, 625, ! 625, 589, 661, 662, 794, 90, 639, 639, 24, 25, ! 26, 27, 27, 625, 602, 30, 32, 33, 34, 35, ! 84, 90, 610, 43, 88, 5, 6, 7, 43, 85, ! 762, 85, 12, 13, 14, 85, 28, 29, 30, 31, ! 66, 67, 774, 706, 36, 37, 38, 39, 780, 89, ! 30, 66, 67, 46, 471, 6, 7, 720, 721, 181, ! 182, 12, 13, 14, 311, 312, 729, 730, 1, 84, ! 733, 734, 90, 88, 85, 5, 6, 7, 810, 811, ! 83, 813, 12, 13, 14, 728, 5, 6, 7, 394, ! 720, 721, 83, 12, 13, 14, 83, 85, 515, 516, ! 30, 90, 519, 191, 192, 193, 194, 5, 6, 7, ! 84, 416, 417, 84, 12, 13, 14, 27, 4, 787, ! 6, 7, 787, 88, 88, 857, 12, 13, 14, 861, ! 83, 5, 6, 7, 83, 83, 3, 46, 12, 13, ! 14, 813, 28, 46, 813, 813, 61, 62, 813, 85, ! 65, 66, 67, 68, 886, 887, 30, 88, 787, 84, ! 84, 787, 46, 468, 469, 84, 583, 54, 55, 56, ! 57, 58, 59, 60, 46, 191, 192, 193, 194, 7, ! 813, 813, 84, 84, 813, 85, 1, 813, 813, 4, ! 5, 6, 7, 89, 84, 10, 84, 12, 13, 14, ! 66, 813, 66, 195, 196, 197, 198, 16, 85, 85, ! 84, 84, 46, 28, 631, 632, 66, 66, 635, 66, ! 5, 6, 7, 640, 641, 17, 643, 12, 13, 14, ! 83, 83, 88, 84, 28, 29, 30, 31, 326, 327, ! 328, 329, 36, 37, 38, 39, 83, 83, 66, 84, ! 555, 556, 84, 84, 237, 238, 83, 90, 84, 676, ! 848, 1, 679, 9, 4, 248, 6, 7, 83, 66, ! 253, 254, 12, 13, 14, 258, 259, 260, 261, 262, ! 263, 264, 265, 266, 267, 268, 269, 83, 28, 84, ! 30, 31, 1, 83, 3, 4, 5, 6, 7, 84, ! 84, 387, 307, 12, 13, 14, 723, 559, 725, 559, ! 326, 327, 328, 329, 418, 559, 559, 414, 27, 28, ! 414, 30, 31, 386, 294, 598, 743, 733, 633, 634, ! 747, 15, 574, 17, 18, 19, 20, 337, 330, 331, ! 332, 333, 687, 720, 84, 85, 677, 434, 674, 58, ! 345, 432, 4, 5, 6, 7, 4, 66, 6, 7, ! 12, 13, 14, 817, 12, 13, 14, 621, 381, 819, ! 382, 788, 789, 863, 791, 84, 28, 360, 361, 796, ! 28, 798, 30, 56, 57, 58, 59, 60, 805, 477, ! 478, 471, 865, 481, 482, 486, -1, 410, 5, 6, ! 7, 195, 196, 197, 198, 12, 13, 14, -1, -1, ! -1, 424, 425, 6, 7, 720, 721, -1, -1, 12, ! 13, 14, -1, 30, 729, 730, -1, -1, 733, 734, ! -1, -1, 84, -1, -1, -1, -1, 30, 6, 7, ! 453, 454, 455, 456, 12, 13, 14, -1, 431, 4, ! 5, 6, 7, 436, -1, -1, -1, 12, 13, 14, ! 443, 477, 478, -1, -1, 481, 482, -1, -1, -1, ! -1, -1, -1, 28, -1, 30, -1, 782, 783, 784, ! -1, -1, -1, -1, -1, -1, -1, 479, 480, -1, ! -1, 483, 484, 506, -1, 508, -1, 4, 1, 6, ! 7, 4, 5, 6, 7, 12, 13, 14, -1, 12, ! 13, 14, -1, -1, -1, -1, -1, -1, -1, 502, ! -1, 28, -1, 30, 27, 28, -1, 30, -1, 84, ! -1, -1, -1, -1, -1, -1, 330, 331, 332, 333, ! 43, 524, 1, -1, 3, 4, 5, 6, 7, -1, ! -1, 10, -1, 12, 13, 14, -1, 645, 646, 647, ! 648, -1, -1, 66, 67, 653, 654, 655, 656, 28, ! 4, 5, 6, 7, 4, 5, 6, 7, 12, 13, ! 14, 84, 12, 13, 14, 88, 89, -1, -1, -1, ! -1, 574, -1, -1, 28, -1, 30, -1, 28, -1, ! 30, 614, 585, 4, 5, 6, 7, 590, -1, -1, ! -1, 12, 13, 14, -1, -1, 599, 600, -1, -1, ! -1, -1, 605, -1, 83, -1, -1, 28, -1, 645, ! 646, 647, 648, -1, 5, 6, 7, 653, 654, 655, ! 656, 12, 13, 14, 5, 6, 7, -1, -1, -1, ! 84, 12, 13, 14, 84, -1, -1, 649, 650, 651, ! 652, 674, -1, -1, 677, 657, 658, 659, 660, 30, ! 4, 5, 6, 7, -1, -1, 10, -1, 12, 13, ! 14, -1, -1, 84, -1, 479, 480, 670, -1, 483, ! 484, -1, 675, -1, 28, 678, 30, -1, -1, -1, ! -1, 684, -1, -1, 687, -1, 689, 4, 5, 6, ! 7, -1, 5, 6, 7, 12, 13, 14, -1, 12, ! 13, 14, 1, 84, 3, 4, 5, 6, 7, 8, ! 9, 28, 11, 12, 13, 14, 15, 30, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, ! 29, 30, 31, -1, 33, 34, 35, 36, 37, -1, ! -1, 744, -1, 42, 777, 748, -1, -1, 751, 48, ! -1, 754, 51, -1, 757, -1, -1, 56, 57, 58, ! 10, -1, 61, 62, -1, -1, -1, 66, 4, 5, ! 6, 7, 4, 5, 6, 7, 12, 13, 14, -1, ! 12, 13, 14, -1, -1, 84, 819, 86, 87, -1, ! 89, -1, 28, 43, 44, 45, 28, 47, 48, 49, ! 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, ! 60, -1, -1, -1, -1, -1, 5, 6, 7, -1, ! 853, 854, -1, 12, 13, 14, 52, 53, 54, 55, ! 56, 57, 58, 59, 60, 649, 650, 651, 652, -1, ! 90, 30, -1, 657, 658, 659, 660, 1, 84, 3, ! 4, 5, 6, 7, 8, 9, -1, 11, 12, 13, ! 14, 15, -1, 17, 18, 19, 20, 21, 22, 23, ! 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, ! 34, 35, 36, 37, 5, 6, 7, -1, 42, -1, ! -1, 12, 13, 14, 48, 84, -1, 51, -1, -1, ! -1, -1, 56, 57, 58, -1, -1, 61, 62, 43, ! 44, 45, 66, 47, 48, 49, 50, 51, 52, 53, ! 54, 55, 56, 57, 58, 59, 60, -1, -1, -1, ! 84, 85, 86, 87, 1, 89, 3, 4, -1, -1, ! -1, 8, 9, -1, 11, -1, -1, -1, 15, 83, ! 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, ! 27, -1, 29, -1, 31, -1, 33, 34, 35, 36, ! 37, 5, 6, 7, -1, 42, -1, -1, 12, 13, ! 14, 48, -1, 30, 51, -1, -1, -1, -1, 56, ! 57, 58, -1, -1, 61, 62, 43, 44, 45, 66, ! 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, ! 57, 58, 59, 60, -1, -1, -1, 84, -1, 86, ! 87, 1, 89, 3, 4, -1, -1, -1, 8, 9, ! -1, 11, -1, -1, -1, 15, -1, 17, 18, 19, ! 20, 21, 22, 23, 24, 25, 26, 27, -1, 29, ! -1, 31, -1, 33, 34, 35, 36, 37, -1, 6, ! 7, -1, 42, -1, -1, 12, 13, 14, 48, -1, -1, 51, -1, -1, -1, -1, 56, 57, 58, -1, ! -1, 61, 62, 30, -1, 1, 66, 3, 4, -1, ! 6, 7, 8, 9, -1, 11, 12, 13, 14, -1, ! -1, -1, -1, -1, 84, -1, 86, 87, -1, 89, ! -1, -1, 28, 29, 30, 31, -1, 33, 34, 35, ! 36, 37, -1, -1, -1, -1, 42, -1, -1, -1, ! -1, -1, 48, -1, -1, 51, -1, -1, -1, -1, ! 56, 57, 58, -1, -1, 61, 62, -1, -1, 1, ! 66, 3, 4, -1, -1, -1, 8, 9, -1, 11, ! 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, ! 86, 87, -1, 89, -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, -1, -1, -1, -1, 48, -1, -1, 51, ! -1, -1, -1, -1, 56, 57, 58, -1, -1, 61, ! 62, -1, -1, 65, 66, 67, 1, -1, 3, 4, ! -1, -1, -1, 8, 9, -1, 11, -1, -1, -1, ! -1, -1, -1, 85, 86, 87, -1, 89, -1, -1, ! -1, -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, -1, -1, -1, -1, -1, 48, -1, -1, 51, -1, -1, -1, ! -1, 56, 57, 58, -1, -1, 61, 62, -1, -1, ! 65, 66, 67, 1, -1, 3, -1, -1, -1, -1, ! 8, 9, -1, 11, -1, -1, -1, -1, -1, -1, ! 85, 86, 87, -1, 89, -1, -1, -1, -1, -1, ! -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, -1, 42, 43, -1, -1, -1, -1, ! 48, -1, -1, 51, -1, -1, -1, -1, 56, 57, ! 58, -1, -1, 61, 62, -1, -1, 65, 66, 67, ! 1, -1, 3, -1, -1, -1, -1, 8, 9, -1, ! 11, -1, -1, -1, 4, 5, 6, 7, 86, 87, ! -1, 89, 12, 13, 14, -1, -1, -1, 29, -1, ! 31, -1, 33, 34, 35, 36, 37, -1, 28, -1, ! 30, 42, -1, 4, 5, 6, 7, 48, -1, -1, ! 51, 12, 13, 14, -1, 56, 57, 58, -1, -1, ! 61, 62, 1, -1, 3, 66, -1, 28, -1, 8, ! 9, -1, 11, 49, 50, 51, 52, 53, 54, 55, ! 56, 57, 58, 59, 60, 86, 87, -1, 89, -1, ! 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, ! -1, -1, 1, 42, -1, 4, 5, 6, 7, 48, ! -1, -1, 51, 12, 13, 14, -1, 56, 57, 58, ! -1, -1, 61, 62, -1, -1, -1, 66, 27, 28, ! 1, 30, -1, 4, -1, 6, 7, -1, -1, -1, ! -1, 12, 13, 14, 43, -1, -1, 86, 87, -1, ! 89, -1, -1, -1, -1, -1, -1, 28, -1, 30, ! 31, -1, -1, -1, -1, -1, -1, 66, 67, 3, ! 4, 5, 6, 7, 8, 9, -1, 11, 12, 13, ! 14, -1, -1, -1, -1, 84, -1, -1, -1, 88, ! 89, -1, -1, -1, 28, 29, 30, 31, -1, 33, ! 34, 35, 36, 37, -1, -1, -1, -1, 42, -1, ! 3, -1, 5, -1, 48, 8, 9, 51, 11, -1, ! -1, -1, 56, 57, 58, -1, -1, 61, 62, -1, ! -1, -1, 66, -1, -1, -1, 29, -1, 31, -1, ! 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, ! -1, -1, 86, 87, -1, 48, 90, -1, 51, -1, ! -1, -1, -1, 56, 57, 58, -1, -1, 61, 62, ! 3, -1, -1, 66, -1, 8, 9, -1, 11, -1, ! -1, 4, 5, 6, 7, -1, -1, -1, -1, 12, ! 13, 14, -1, 86, 87, -1, 29, 90, 31, -1, ! 33, 34, 35, 36, 37, 28, -1, 30, -1, 42, ! -1, 3, -1, -1, -1, 48, 8, 9, 51, 11, ! -1, -1, -1, 56, 57, 58, -1, -1, 61, 62, ! -1, -1, -1, 66, -1, -1, -1, 29, -1, 31, ! -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, -1, 86, 87, -1, 48, 90, -1, 51, ! -1, -1, -1, -1, 56, 57, 58, -1, -1, 61, ! 62, -1, -1, -1, 66, -1, -1, -1, -1, -1, ! -1, 3, 4, 5, 6, 7, 8, 9, -1, 11, ! 12, 13, 14, -1, 86, 87, -1, -1, 90, 21, ! 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, ! -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, 4, 5, 6, 7, 48, -1, -1, 51, ! 12, 13, 14, -1, 56, 57, 58, -1, -1, 61, ! 62, -1, -1, -1, 66, -1, 28, -1, 30, -1, ! 3, 4, -1, -1, -1, 8, 9, -1, 11, -1, ! -1, -1, 84, -1, 86, 87, -1, 89, 21, 22, ! 23, 24, 25, 26, 27, -1, 29, -1, 31, -1, ! 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, ! -1, 4, 5, 6, 7, 48, -1, -1, 51, 12, ! 13, 14, -1, 56, 57, 58, -1, -1, 61, 62, ! -1, 3, -1, 66, -1, 28, 8, 9, -1, 11, ! 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, ! 60, 84, -1, 86, 87, -1, 89, 29, -1, 31, ! -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, -1, -1, -1, -1, 48, -1, -1, 51, ! -1, -1, -1, -1, 56, 57, 58, -1, -1, 61, ! 62, -1, -1, -1, 66, 3, 4, 5, 6, 7, ! 8, 9, -1, 11, 12, 13, 14, -1, -1, -1, ! -1, -1, -1, -1, 86, 87, -1, 89, -1, -1, 28, 29, 30, 31, -1, 33, 34, 35, 36, 37, ! -1, -1, -1, -1, 42, -1, -1, -1, -1, -1, ! 48, -1, -1, 51, -1, -1, -1, -1, 56, 57, ! 58, -1, -1, 61, 62, -1, 3, 4, 66, 6, ! 7, 8, 9, -1, 11, 12, 13, 14, 53, 54, ! 55, 56, 57, 58, 59, 60, -1, -1, 86, 87, ! -1, 28, 29, 30, 31, -1, 33, 34, 35, 36, ! 37, -1, -1, -1, -1, 42, -1, 3, -1, -1, -1, 48, 8, 9, 51, 11, -1, -1, -1, 56, ! 57, 58, -1, -1, 61, 62, -1, -1, -1, 66, ! -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, ! 36, 37, -1, -1, -1, -1, 42, -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, -1, -1, ! 56, 57, 58, -1, -1, 61, 62, -1, -1, -1, ! 66, -1, -1, -1, 29, -1, 31, -1, 33, 34, ! 35, 36, 37, -1, -1, -1, -1, 42, 84, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, -1, ! -1, 56, 57, 58, -1, -1, 61, 62, -1, -1, ! -1, 66, -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, -1, ! -1, -1, 56, 57, 58, -1, -1, 61, 62, -1, ! -1, -1, 66, -1, -1, -1, 29, -1, 31, -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, 42, ! -1, 3, 86, 87, -1, 48, 8, 9, 51, 11, ! -1, -1, -1, 56, 57, 58, -1, -1, 61, 62, ! -1, -1, -1, 66, -1, -1, -1, 29, -1, 31, ! -1, 33, 34, 35, 36, 37, -1, -1, -1, -1, ! 42, -1, -1, 86, 87, -1, 48, -1, -1, 51, ! -1, -1, -1, 10, 56, 57, 58, -1, -1, 61, ! 62, 43, 44, 45, 66, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, -1, ! -1, -1, -1, -1, 86, 87, 43, 44, 45, 46, ! 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, ! 57, 58, 59, 60, -1, 43, 44, 45, 90, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 43, 44, 45, -1, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, -1, -1, -1, -1, -1, -1, 43, 44, 45, 88, 47, 48, 49, 50, 51, 52, 53, 54, 55, ! 56, 57, 58, 59, 60, -1, -1, -1, 88, 4, ! 5, 6, 7, 4, -1, 6, 7, 12, 13, 14, ! -1, 12, 13, 14, -1, -1, -1, -1, -1, -1, ! -1, -1, 88, 28, -1, 30, -1, 28, -1, 30, ! 4, 5, 6, 7, 4, -1, 6, 7, 12, 13, 14, -1, 12, 13, 14, -1, -1, -1, -1, -1, ! -1, -1, -1, -1, 28, -1, -1, -1, 28, 43, ! 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, ! 54, 55, 56, 57, 58, 59, 60, 43, 44, 45, ! -1, 47, 48, 49, 50, 51, 52, 53, 54, 55, ! 56, 57, 58, 59, 60, 45, -1, 47, 48, 49, ! 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, ! 60, 48, 49, 50, 51, 52, 53, 54, 55, 56, ! 57, 58, 59, 60 }; ! /* YYSTOS[STATE-NUM] -- The (internal number of the) accessing ! symbol of state STATE-NUM. */ ! static const unsigned short yystos[] = { ! 0, 92, 93, 94, 0, 95, 1, 4, 5, 6, ! 7, 12, 13, 14, 27, 28, 30, 31, 84, 96, ! 97, 98, 113, 129, 132, 133, 134, 135, 136, 137, ! 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, ! 148, 149, 155, 157, 158, 159, 160, 161, 170, 171, ! 197, 198, 199, 200, 205, 290, 96, 84, 85, 170, ! 170, 170, 66, 66, 66, 3, 58, 66, 163, 167, ! 196, 5, 7, 157, 158, 170, 5, 7, 157, 158, ! 5, 7, 157, 158, 170, 5, 7, 157, 158, 5, ! 7, 159, 160, 170, 5, 7, 159, 160, 5, 7, ! 159, 160, 170, 5, 7, 159, 160, 5, 7, 157, ! 158, 170, 5, 7, 157, 158, 5, 7, 157, 158, ! 170, 5, 7, 157, 158, 5, 7, 159, 160, 170, ! 5, 7, 159, 160, 5, 7, 159, 160, 170, 5, ! 7, 159, 160, 129, 129, 84, 171, 3, 4, 89, ! 105, 89, 105, 89, 105, 96, 3, 8, 9, 11, ! 29, 33, 34, 35, 36, 37, 42, 48, 51, 56, ! 57, 58, 61, 62, 66, 86, 87, 106, 107, 109, ! 110, 111, 112, 114, 115, 121, 123, 244, 290, 66, ! 107, 132, 133, 134, 135, 136, 137, 138, 139, 154, ! 217, 132, 133, 134, 135, 153, 156, 169, 170, 84, ! 88, 1, 27, 66, 67, 103, 164, 225, 4, 58, ! 66, 162, 165, 191, 192, 196, 163, 196, 208, 209, ! 89, 208, 89, 204, 89, 114, 114, 66, 66, 66, ! 105, 114, 1, 89, 107, 217, 114, 83, 88, 66, ! 110, 66, 110, 43, 44, 45, 47, 48, 49, 50, ! 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, ! 61, 62, 65, 66, 67, 68, 9, 1, 85, 233, ! 242, 114, 5, 6, 7, 105, 172, 173, 174, 83, ! 218, 83, 196, 196, 130, 169, 66, 169, 285, 5, ! 58, 90, 107, 154, 1, 124, 125, 126, 232, 251, ! 169, 156, 169, 84, 88, 1, 99, 164, 66, 225, ! 84, 1, 101, 85, 1, 84, 132, 133, 134, 135, ! 136, 137, 138, 139, 152, 153, 210, 290, 201, 85, ! 202, 1, 105, 215, 216, 203, 115, 115, 217, 83, ! 83, 83, 84, 115, 217, 217, 115, 115, 118, 120, ! 117, 116, 115, 115, 115, 115, 115, 115, 115, 115, ! 115, 115, 115, 115, 105, 108, 109, 107, 105, 83, ! 32, 237, 238, 239, 83, 83, 88, 66, 58, 66, ! 219, 221, 222, 223, 224, 225, 83, 167, 196, 123, ! 286, 107, 154, 90, 90, 5, 58, 90, 107, 84, ! 104, 232, 10, 125, 252, 43, 192, 192, 130, 124, ! 169, 285, 124, 169, 129, 129, 84, 210, 208, 169, ! 208, 43, 88, 207, 215, 88, 88, 88, 89, 114, ! 83, 83, 107, 46, 115, 115, 83, 90, 105, 289, ! 1, 128, 226, 227, 228, 229, 230, 231, 232, 243, ! 251, 255, 256, 239, 83, 173, 3, 108, 156, 169, ! 275, 66, 225, 83, 1, 3, 10, 132, 133, 136, ! 137, 140, 141, 144, 145, 150, 151, 277, 280, 281, ! 283, 287, 288, 90, 107, 107, 90, 90, 251, 127, ! 150, 151, 168, 83, 165, 191, 100, 43, 102, 211, ! 213, 251, 212, 214, 251, 85, 85, 115, 216, 85, ! 207, 217, 115, 217, 122, 46, 115, 84, 88, 128, ! 255, 256, 128, 255, 256, 251, 255, 256, 128, 255, ! 256, 232, 85, 252, 83, 88, 83, 222, 223, 221, ! 276, 169, 275, 83, 129, 284, 284, 83, 84, 88, ! 83, 88, 90, 90, 252, 84, 129, 84, 129, 1, ! 89, 115, 175, 251, 166, 251, 88, 252, 88, 252, ! 169, 169, 169, 85, 83, 88, 83, 1, 3, 65, ! 67, 89, 105, 115, 177, 178, 179, 181, 183, 184, ! 119, 105, 252, 234, 4, 21, 22, 23, 24, 25, ! 26, 27, 84, 89, 105, 107, 131, 148, 149, 155, ! 235, 241, 245, 267, 268, 290, 109, 83, 277, 4, ! 58, 66, 193, 194, 195, 196, 220, 221, 222, 58, ! 66, 196, 220, 278, 10, 132, 133, 134, 135, 136, ! 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, ! 147, 148, 149, 282, 3, 1, 240, 245, 162, 163, ! 176, 252, 175, 252, 130, 46, 191, 130, 46, 196, ! 169, 115, 105, 115, 182, 46, 85, 88, 206, 43, ! 184, 181, 115, 115, 46, 84, 84, 84, 107, 58, ! 105, 7, 269, 251, 84, 129, 129, 84, 15, 17, ! 18, 19, 20, 246, 247, 249, 257, 242, 131, 83, ! 156, 169, 169, 66, 225, 66, 225, 169, 170, 156, ! 169, 169, 169, 129, 129, 245, 84, 84, 177, 240, ! 240, 213, 251, 115, 46, 169, 214, 115, 46, 169, ! 83, 10, 90, 177, 180, 179, 181, 10, 46, 84, ! 107, 84, 66, 252, 162, 185, 191, 163, 188, 196, ! 248, 259, 250, 261, 66, 16, 1, 235, 254, 1, ! 66, 236, 194, 195, 195, 285, 285, 279, 193, 196, ! 220, 196, 220, 85, 252, 169, 115, 169, 115, 115, ! 85, 181, 115, 84, 107, 46, 84, 186, 84, 189, ! 66, 66, 254, 66, 107, 1, 258, 253, 255, 256, ! 107, 83, 277, 169, 169, 169, 169, 169, 90, 46, ! 46, 83, 169, 124, 124, 107, 107, 17, 107, 131, ! 266, 270, 83, 254, 236, 253, 83, 9, 67, 271, ! 272, 273, 84, 187, 190, 83, 83, 262, 84, 265, ! 84, 66, 105, 46, 83, 88, 251, 251, 260, 270, ! 254, 107, 90, 271, 84, 273, 252, 252, 254, 84, ! 83, 9, 46, 83, 245, 245, 263, 66, 123, 274, ! 84, 270, 107, 83, 88, 83, 83, 84, 123, 264, ! 254 }; #if ! defined (YYSIZE_T) && defined (__SIZE_TYPE__) # define YYSIZE_T __SIZE_TYPE__ #endif *************** union yyalloc *** 1772,1785 **** # define YYSIZE_T size_t #endif #if ! defined (YYSIZE_T) ! # ifdef __cplusplus ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T std::size_t ! # else ! # ifdef __STDC__ ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T size_t ! # endif # endif #endif #if ! defined (YYSIZE_T) --- 2013,2021 ---- # define YYSIZE_T size_t #endif #if ! defined (YYSIZE_T) ! # if defined (__STDC__) || defined (__cplusplus) ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYSIZE_T size_t # endif #endif #if ! defined (YYSIZE_T) *************** union yyalloc *** 1788,1816 **** #define yyerrok (yyerrstatus = 0) #define yyclearin (yychar = YYEMPTY) ! #define YYEMPTY -2 #define YYEOF 0 #define YYACCEPT goto yyacceptlab ! #define YYABORT goto yyabortlab #define YYERROR goto yyerrlab1 /* Like YYERROR except do call yyerror. This remains here temporarily to ease the transition to the new meaning of YYERROR, for GCC. Once GCC version 2 has supplanted version 1, this can go. */ #define YYFAIL goto yyerrlab #define YYRECOVERING() (!!yyerrstatus) #define YYBACKUP(Token, Value) \ do \ if (yychar == YYEMPTY && yylen == 1) \ { \ yychar = (Token); \ yylval = (Value); \ ! yychar1 = YYTRANSLATE (yychar); \ YYPOPSTACK; \ goto yybackup; \ } \ else \ { \ ! yyerror ("syntax error: cannot back up"); \ YYERROR; \ } \ while (0) --- 2024,2057 ---- #define yyerrok (yyerrstatus = 0) #define yyclearin (yychar = YYEMPTY) ! #define YYEMPTY (-2) #define YYEOF 0 + #define YYACCEPT goto yyacceptlab ! #define YYABORT goto yyabortlab #define YYERROR goto yyerrlab1 + /* Like YYERROR except do call yyerror. This remains here temporarily to ease the transition to the new meaning of YYERROR, for GCC. Once GCC version 2 has supplanted version 1, this can go. */ + #define YYFAIL goto yyerrlab + #define YYRECOVERING() (!!yyerrstatus) + #define YYBACKUP(Token, Value) \ do \ if (yychar == YYEMPTY && yylen == 1) \ { \ yychar = (Token); \ yylval = (Value); \ ! yytoken = YYTRANSLATE (yychar); \ YYPOPSTACK; \ goto yybackup; \ } \ else \ { \ ! yyerror ("syntax error: cannot back up");\ YYERROR; \ } \ while (0) *************** while (0) *** 1818,1869 **** #define YYTERROR 1 #define YYERRCODE 256 - /* YYLLOC_DEFAULT -- Compute the default location (before the actions ! are run). ! ! When YYLLOC_DEFAULT is run, CURRENT is set the location of the ! first token. By default, to implement support for ranges, extend ! its range to the last symbol. */ #ifndef YYLLOC_DEFAULT ! # define YYLLOC_DEFAULT(Current, Rhs, N) \ ! Current.last_line = Rhs[N].last_line; \ ! Current.last_column = Rhs[N].last_column; #endif - /* YYLEX -- calling `yylex' with the right arguments. */ ! #if YYPURE ! # if YYLSP_NEEDED ! # ifdef YYLEX_PARAM ! # define YYLEX yylex (&yylval, &yylloc, YYLEX_PARAM) ! # else ! # define YYLEX yylex (&yylval, &yylloc) ! # endif ! # else /* !YYLSP_NEEDED */ ! # ifdef YYLEX_PARAM ! # define YYLEX yylex (&yylval, YYLEX_PARAM) ! # else ! # define YYLEX yylex (&yylval) ! # endif ! # endif /* !YYLSP_NEEDED */ ! #else /* !YYPURE */ ! # define YYLEX yylex () ! #endif /* !YYPURE */ ! /* Enable debugging if requested. */ #if YYDEBUG # ifndef YYFPRINTF ! # ifdef __cplusplus ! # include /* INFRINGES ON USER NAME SPACE */ ! # else ! # include /* INFRINGES ON USER NAME SPACE */ ! # endif ! # define YYFPRINTF YYSTD (fprintf) # endif # define YYDPRINTF(Args) \ --- 2059,2089 ---- #define YYTERROR 1 #define YYERRCODE 256 /* YYLLOC_DEFAULT -- Compute the default location (before the actions ! are run). */ #ifndef YYLLOC_DEFAULT ! # define YYLLOC_DEFAULT(Current, Rhs, N) \ ! Current.first_line = Rhs[1].first_line; \ ! Current.first_column = Rhs[1].first_column; \ ! Current.last_line = Rhs[N].last_line; \ ! Current.last_column = Rhs[N].last_column; #endif /* YYLEX -- calling `yylex' with the right arguments. */ ! #ifdef YYLEX_PARAM ! # define YYLEX yylex (YYLEX_PARAM) ! #else ! # define YYLEX yylex () ! #endif /* Enable debugging if requested. */ #if YYDEBUG # ifndef YYFPRINTF ! # include /* INFRINGES ON USER NAME SPACE */ ! # define YYFPRINTF fprintf # endif # define YYDPRINTF(Args) \ *************** do { \ *** 1871,1885 **** if (yydebug) \ YYFPRINTF Args; \ } while (0) ! /* Nonzero means print parse trace. [The following comment makes no ! sense to me. Could someone clarify it? --akim] Since this is ! uninitialized, it does not stop multiple parsers from coexisting. ! */ int yydebug; #else /* !YYDEBUG */ # define YYDPRINTF(Args) #endif /* !YYDEBUG */ /* YYINITDEPTH -- initial size of the parser's stacks. */ #ifndef YYINITDEPTH # define YYINITDEPTH 200 --- 2091,2183 ---- if (yydebug) \ YYFPRINTF Args; \ } while (0) ! ! # define YYDSYMPRINT(Args) \ ! do { \ ! if (yydebug) \ ! yysymprint Args; \ ! } while (0) ! ! # define YYDSYMPRINTF(Title, Token, Value, Location) \ ! do { \ ! if (yydebug) \ ! { \ ! YYFPRINTF (stderr, "%s ", Title); \ ! yysymprint (stderr, \ ! Token, Value); \ ! YYFPRINTF (stderr, "\n"); \ ! } \ ! } while (0) ! ! /*------------------------------------------------------------------. ! | yy_stack_print -- Print the state stack from its BOTTOM up to its | ! | TOP (cinluded). | ! `------------------------------------------------------------------*/ ! ! #if defined (__STDC__) || defined (__cplusplus) ! static void ! yy_stack_print (short *bottom, short *top) ! #else ! static void ! yy_stack_print (bottom, top) ! short *bottom; ! short *top; ! #endif ! { ! YYFPRINTF (stderr, "Stack now"); ! for (/* Nothing. */; bottom <= top; ++bottom) ! YYFPRINTF (stderr, " %d", *bottom); ! YYFPRINTF (stderr, "\n"); ! } ! ! # define YY_STACK_PRINT(Bottom, Top) \ ! do { \ ! if (yydebug) \ ! yy_stack_print ((Bottom), (Top)); \ ! } while (0) ! ! ! /*------------------------------------------------. ! | Report that the YYRULE is going to be reduced. | ! `------------------------------------------------*/ ! ! #if defined (__STDC__) || defined (__cplusplus) ! static void ! yy_reduce_print (int yyrule) ! #else ! static void ! yy_reduce_print (yyrule) ! int yyrule; ! #endif ! { ! int yyi; ! unsigned int yylineno = yyrline[yyrule]; ! YYFPRINTF (stderr, "Reducing stack by rule %d (line %u), ", ! yyrule - 1, yylineno); ! /* Print the symbols being reduced, and their result. */ ! for (yyi = yyprhs[yyrule]; 0 <= yyrhs[yyi]; yyi++) ! YYFPRINTF (stderr, "%s ", yytname [yyrhs[yyi]]); ! YYFPRINTF (stderr, "-> %s\n", yytname [yyr1[yyrule]]); ! } ! ! # define YY_REDUCE_PRINT(Rule) \ ! do { \ ! if (yydebug) \ ! yy_reduce_print (Rule); \ ! } while (0) ! ! /* Nonzero means print parse trace. It is left uninitialized so that ! multiple parsers can coexist. */ int yydebug; #else /* !YYDEBUG */ # define YYDPRINTF(Args) + # define YYDSYMPRINT(Args) + # define YYDSYMPRINTF(Title, Token, Value, Location) + # define YY_STACK_PRINT(Bottom, Top) + # define YY_REDUCE_PRINT(Rule) #endif /* !YYDEBUG */ + /* YYINITDEPTH -- initial size of the parser's stacks. */ #ifndef YYINITDEPTH # define YYINITDEPTH 200 *************** int yydebug; *** 1899,1933 **** #ifndef YYMAXDEPTH # define YYMAXDEPTH 10000 #endif - - #if ! defined (yyoverflow) && ! defined (yymemcpy) - # if __GNUC__ > 1 /* GNU C and GNU C++ define this. */ - # define yymemcpy __builtin_memcpy - # else /* not GNU C or C++ */ ! /* This is the most reliable way to avoid incompatibilities ! in available built-in functions on various systems. */ ! static void ! # if defined (__STDC__) || defined (__cplusplus) ! yymemcpy (char *yyto, const char *yyfrom, YYSIZE_T yycount) ! # else ! yymemcpy (yyto, yyfrom, yycount) ! char *yyto; ! const char *yyfrom; ! YYSIZE_T yycount; ! # endif ! { ! register const char *yyf = yyfrom; ! register char *yyt = yyto; ! register YYSIZE_T yyi = yycount; ! ! while (yyi-- != 0) ! *yyt++ = *yyf++; ! } ! # endif ! #endif ! #ifdef YYERROR_VERBOSE # ifndef yystrlen # if defined (__GLIBC__) && defined (_STRING_H) --- 2197,2206 ---- #ifndef YYMAXDEPTH # define YYMAXDEPTH 10000 #endif ! ! #if YYERROR_VERBOSE # ifndef yystrlen # if defined (__GLIBC__) && defined (_STRING_H) *************** yystpcpy (yydest, yysrc) *** 1977,2062 **** } # endif # endif ! #endif - #line 345 "/usr/share/bison/bison.simple" ! /* The user can define YYPARSE_PARAM as the name of an argument to be passed ! into yyparse. The argument should have type void *. ! It should actually point to an object. ! Grammar actions can access the variable by casting it ! to the proper pointer type. */ ! #ifdef YYPARSE_PARAM ! # ifdef __cplusplus ! # define YYPARSE_PARAM_ARG void *YYPARSE_PARAM ! # define YYPARSE_PARAM_DECL ! # else /* !__cplusplus */ ! # define YYPARSE_PARAM_ARG YYPARSE_PARAM ! # define YYPARSE_PARAM_DECL void *YYPARSE_PARAM; ! # endif /* !__cplusplus */ ! #else /* !YYPARSE_PARAM */ ! # define YYPARSE_PARAM_ARG ! # define YYPARSE_PARAM_DECL ! #endif /* !YYPARSE_PARAM */ ! /* Prevent warning if -Wstrict-prototypes. */ ! #ifdef __GNUC__ ! # ifdef YYPARSE_PARAM ! YYPARSE_RETURN_TYPE yyparse (void *); # else ! YYPARSE_RETURN_TYPE yyparse (void); # endif #endif - /* YY_DECL_VARIABLES -- depending whether we use a pure parser, - variables are global, or local to YYPARSE. */ ! #define YY_DECL_NON_LSP_VARIABLES \ ! /* The lookahead symbol. */ \ ! int yychar; \ ! \ ! /* The semantic value of the lookahead symbol. */ \ ! YYSTYPE yylval; \ ! \ ! /* Number of parse errors so far. */ \ int yynerrs; - #if YYLSP_NEEDED - # define YY_DECL_VARIABLES \ - YY_DECL_NON_LSP_VARIABLES \ - \ - /* Location data for the lookahead symbol. */ \ - YYLTYPE yylloc; - #else - # define YY_DECL_VARIABLES \ - YY_DECL_NON_LSP_VARIABLES - #endif ! /* If nonreentrant, generate the variables here. */ ! #if !YYPURE ! YY_DECL_VARIABLES ! #endif /* !YYPURE */ ! YYPARSE_RETURN_TYPE ! yyparse (YYPARSE_PARAM_ARG) ! YYPARSE_PARAM_DECL { ! /* If reentrant, generate the variables here. */ ! #if YYPURE ! YY_DECL_VARIABLES ! #endif /* !YYPURE */ ! register int yystate; register int yyn; int yyresult; /* Number of tokens to shift before error messages enabled. */ int yyerrstatus; /* Lookahead token as an internal (translated) token number. */ ! int yychar1 = 0; /* Three stacks and their tools: `yyss': related to states, --- 2250,2383 ---- } # endif # endif ! ! #endif /* !YYERROR_VERBOSE */ ! + #if YYDEBUG + /*--------------------------------. + | Print this symbol on YYOUTPUT. | + `--------------------------------*/ ! #if defined (__STDC__) || defined (__cplusplus) ! static void ! yysymprint (FILE *yyoutput, int yytype, YYSTYPE *yyvaluep) ! #else ! static void ! yysymprint (yyoutput, yytype, yyvaluep) ! FILE *yyoutput; ! int yytype; ! YYSTYPE *yyvaluep; ! #endif ! { ! /* Pacify ``unused variable'' warnings. */ ! (void) yyvaluep; ! if (yytype < YYNTOKENS) ! { ! YYFPRINTF (yyoutput, "token %s (", yytname[yytype]); ! # ifdef YYPRINT ! YYPRINT (yyoutput, yytoknum[yytype], *yyvaluep); ! # endif ! } ! else ! YYFPRINTF (yyoutput, "nterm %s (", yytname[yytype]); ! switch (yytype) ! { ! default: ! break; ! } ! YYFPRINTF (yyoutput, ")"); ! } ! ! #endif /* ! YYDEBUG */ ! /*-----------------------------------------------. ! | Release the memory associated to this symbol. | ! `-----------------------------------------------*/ ! ! #if defined (__STDC__) || defined (__cplusplus) ! static void ! yydestruct (int yytype, YYSTYPE *yyvaluep) ! #else ! static void ! yydestruct (yytype, yyvaluep) ! int yytype; ! YYSTYPE *yyvaluep; ! #endif ! { ! /* Pacify ``unused variable'' warnings. */ ! (void) yyvaluep; ! ! switch (yytype) ! { ! ! default: ! break; ! } ! } ! ! ! /* Prevent warnings from -Wmissing-prototypes. */ ! ! #ifdef YYPARSE_PARAM ! # if defined (__STDC__) || defined (__cplusplus) ! int yyparse (void *YYPARSE_PARAM); # else ! int yyparse (); # endif + #else /* ! YYPARSE_PARAM */ + #if defined (__STDC__) || defined (__cplusplus) + int yyparse (void); + #else + int yyparse (); #endif + #endif /* ! YYPARSE_PARAM */ ! ! /* The lookahead symbol. */ ! int yychar; ! ! /* The semantic value of the lookahead symbol. */ ! YYSTYPE yylval; ! ! /* Number of syntax errors so far. */ int yynerrs; ! /*----------. ! | yyparse. | ! `----------*/ ! #ifdef YYPARSE_PARAM ! # if defined (__STDC__) || defined (__cplusplus) ! int yyparse (void *YYPARSE_PARAM) ! # else ! int yyparse (YYPARSE_PARAM) ! void *YYPARSE_PARAM; ! # endif ! #else /* ! YYPARSE_PARAM */ ! #if defined (__STDC__) || defined (__cplusplus) ! int ! yyparse (void) ! #else ! int ! yyparse () ! #endif ! #endif { ! register int yystate; register int yyn; int yyresult; /* Number of tokens to shift before error messages enabled. */ int yyerrstatus; /* Lookahead token as an internal (translated) token number. */ ! int yytoken = 0; /* Three stacks and their tools: `yyss': related to states, *************** yyparse (YYPARSE_PARAM_ARG) *** 2066,2072 **** Refer to the stacks thru separate pointers, to allow yyoverflow to reallocate them elsewhere. */ ! /* The state stack. */ short yyssa[YYINITDEPTH]; short *yyss = yyssa; register short *yyssp; --- 2387,2393 ---- Refer to the stacks thru separate pointers, to allow yyoverflow to reallocate them elsewhere. */ ! /* The state stack. */ short yyssa[YYINITDEPTH]; short *yyss = yyssa; register short *yyssp; *************** yyparse (YYPARSE_PARAM_ARG) *** 2076,2106 **** YYSTYPE *yyvs = yyvsa; register YYSTYPE *yyvsp; - #if YYLSP_NEEDED - /* The location stack. */ - YYLTYPE yylsa[YYINITDEPTH]; - YYLTYPE *yyls = yylsa; - YYLTYPE *yylsp; - #endif - #if YYLSP_NEEDED - # define YYPOPSTACK (yyvsp--, yyssp--, yylsp--) - #else - # define YYPOPSTACK (yyvsp--, yyssp--) - #endif ! YYSIZE_T yystacksize = YYINITDEPTH; /* The variables used to return semantic value and location from the action routines. */ YYSTYPE yyval; ! #if YYLSP_NEEDED ! YYLTYPE yyloc; ! #endif /* When reducing, the number of symbols on the RHS of the reduced ! rule. */ int yylen; YYDPRINTF ((stderr, "Starting parse\n")); --- 2397,2415 ---- YYSTYPE *yyvs = yyvsa; register YYSTYPE *yyvsp; ! #define YYPOPSTACK (yyvsp--, yyssp--) + YYSIZE_T yystacksize = YYINITDEPTH; /* The variables used to return semantic value and location from the action routines. */ YYSTYPE yyval; ! /* When reducing, the number of symbols on the RHS of the reduced ! rule. */ int yylen; YYDPRINTF ((stderr, "Starting parse\n")); *************** yyparse (YYPARSE_PARAM_ARG) *** 2117,2125 **** yyssp = yyss; yyvsp = yyvs; ! #if YYLSP_NEEDED ! yylsp = yyls; ! #endif goto yysetstate; /*------------------------------------------------------------. --- 2426,2432 ---- yyssp = yyss; yyvsp = yyvs; ! goto yysetstate; /*------------------------------------------------------------. *************** yyparse (YYPARSE_PARAM_ARG) *** 2134,2140 **** yysetstate: *yyssp = yystate; ! if (yyssp >= yyss + yystacksize - 1) { /* Get the current used size of the three stacks, in elements. */ YYSIZE_T yysize = yyssp - yyss + 1; --- 2441,2447 ---- yysetstate: *yyssp = yystate; ! if (yyss + yystacksize - 1 <= yyssp) { /* Get the current used size of the three stacks, in elements. */ YYSIZE_T yysize = yyssp - yyss + 1; *************** yyparse (YYPARSE_PARAM_ARG) *** 2147,2179 **** YYSTYPE *yyvs1 = yyvs; short *yyss1 = yyss; /* Each stack pointer address is followed by the size of the ! data in use in that stack, in bytes. */ ! # if YYLSP_NEEDED ! YYLTYPE *yyls1 = yyls; ! /* This used to be a conditional around just the two extra args, ! but that might be undefined if yyoverflow is a macro. */ ! yyoverflow ("parser stack overflow", ! &yyss1, yysize * sizeof (*yyssp), ! &yyvs1, yysize * sizeof (*yyvsp), ! &yyls1, yysize * sizeof (*yylsp), ! &yystacksize); ! yyls = yyls1; ! # else yyoverflow ("parser stack overflow", &yyss1, yysize * sizeof (*yyssp), &yyvs1, yysize * sizeof (*yyvsp), &yystacksize); ! # endif yyss = yyss1; yyvs = yyvs1; } #else /* no yyoverflow */ /* Extend the stack our own way. */ ! if (yystacksize >= YYMAXDEPTH) goto yyoverflowlab; yystacksize *= 2; ! if (yystacksize > YYMAXDEPTH) yystacksize = YYMAXDEPTH; { --- 2454,2482 ---- YYSTYPE *yyvs1 = yyvs; short *yyss1 = yyss; + /* Each stack pointer address is followed by the size of the ! data in use in that stack, in bytes. This used to be a ! conditional around just the two extra args, but that might ! be undefined if yyoverflow is a macro. */ yyoverflow ("parser stack overflow", &yyss1, yysize * sizeof (*yyssp), &yyvs1, yysize * sizeof (*yyvsp), + &yystacksize); ! yyss = yyss1; yyvs = yyvs1; } #else /* no yyoverflow */ + # ifndef YYSTACK_RELOCATE + goto yyoverflowlab; + # else /* Extend the stack our own way. */ ! if (YYMAXDEPTH <= yystacksize) goto yyoverflowlab; yystacksize *= 2; ! if (YYMAXDEPTH < yystacksize) yystacksize = YYMAXDEPTH; { *************** yyparse (YYPARSE_PARAM_ARG) *** 2182,2208 **** (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize)); if (! yyptr) goto yyoverflowlab; ! YYSTACK_RELOCATE (short, yyss); ! YYSTACK_RELOCATE (YYSTYPE, yyvs); ! # if YYLSP_NEEDED ! YYSTACK_RELOCATE (YYLTYPE, yyls); ! # endif ! # undef YYSTACK_RELOCATE if (yyss1 != yyssa) YYSTACK_FREE (yyss1); } #endif /* no yyoverflow */ yyssp = yyss + yysize - 1; yyvsp = yyvs + yysize - 1; ! #if YYLSP_NEEDED ! yylsp = yyls + yysize - 1; ! #endif YYDPRINTF ((stderr, "Stack size increased to %lu\n", (unsigned long int) yystacksize)); ! if (yyssp >= yyss + yystacksize - 1) YYABORT; } --- 2485,2508 ---- (union yyalloc *) YYSTACK_ALLOC (YYSTACK_BYTES (yystacksize)); if (! yyptr) goto yyoverflowlab; ! YYSTACK_RELOCATE (yyss); ! YYSTACK_RELOCATE (yyvs); ! ! # undef YYSTACK_RELOCATE if (yyss1 != yyssa) YYSTACK_FREE (yyss1); } + # endif #endif /* no yyoverflow */ yyssp = yyss + yysize - 1; yyvsp = yyvs + yysize - 1; ! YYDPRINTF ((stderr, "Stack size increased to %lu\n", (unsigned long int) yystacksize)); ! if (yyss + yystacksize - 1 <= yyssp) YYABORT; } *************** yyparse (YYPARSE_PARAM_ARG) *** 2210,2216 **** goto yybackup; - /*-----------. | yybackup. | `-----------*/ --- 2510,2515 ---- *************** yybackup: *** 2223,2310 **** /* First try to decide what to do without reference to lookahead token. */ yyn = yypact[yystate]; ! if (yyn == YYFLAG) goto yydefault; /* Not known => get a lookahead token if don't already have one. */ ! /* yychar is either YYEMPTY or YYEOF ! or a valid token in external form. */ ! if (yychar == YYEMPTY) { YYDPRINTF ((stderr, "Reading a token: ")); yychar = YYLEX; } ! /* Convert token to internal form (in yychar1) for indexing tables with */ ! ! if (yychar <= 0) /* This means end of input. */ { ! yychar1 = 0; ! yychar = YYEOF; /* Don't call YYLEX any more */ ! YYDPRINTF ((stderr, "Now at end of input.\n")); } else { ! yychar1 = YYTRANSLATE (yychar); ! ! #if YYDEBUG ! /* We have to keep this `#if YYDEBUG', since we use variables ! which are defined only if `YYDEBUG' is set. */ ! if (yydebug) ! { ! YYFPRINTF (stderr, "Next token is %d (%s", ! yychar, yytname[yychar1]); ! /* Give the individual parser a way to print the precise ! meaning of a token, for further debugging info. */ ! # ifdef YYPRINT ! YYPRINT (stderr, yychar, yylval); ! # endif ! YYFPRINTF (stderr, ")\n"); ! } ! #endif } ! yyn += yychar1; ! if (yyn < 0 || yyn > YYLAST || yycheck[yyn] != yychar1) goto yydefault; - yyn = yytable[yyn]; ! ! /* yyn is what to do for this token type in this state. ! Negative => reduce, -yyn is rule number. ! Positive => shift, yyn is new state. ! New state is final state => don't bother to shift, ! just return success. ! 0, or most negative number => error. */ ! ! if (yyn < 0) { ! if (yyn == YYFLAG) goto yyerrlab; yyn = -yyn; goto yyreduce; } - else if (yyn == 0) - goto yyerrlab; if (yyn == YYFINAL) YYACCEPT; /* Shift the lookahead token. */ ! YYDPRINTF ((stderr, "Shifting token %d (%s), ", ! yychar, yytname[yychar1])); /* Discard the token being shifted unless it is eof. */ if (yychar != YYEOF) yychar = YYEMPTY; *++yyvsp = yylval; ! #if YYLSP_NEEDED ! *++yylsp = yylloc; ! #endif /* Count tokens shifted since error; after three, turn off error status. */ --- 2522,2576 ---- /* First try to decide what to do without reference to lookahead token. */ yyn = yypact[yystate]; ! if (yyn == YYPACT_NINF) goto yydefault; /* Not known => get a lookahead token if don't already have one. */ ! /* YYCHAR is either YYEMPTY or YYEOF or a valid lookahead symbol. */ if (yychar == YYEMPTY) { YYDPRINTF ((stderr, "Reading a token: ")); yychar = YYLEX; } ! if (yychar <= YYEOF) { ! yychar = yytoken = YYEOF; YYDPRINTF ((stderr, "Now at end of input.\n")); } else { ! yytoken = YYTRANSLATE (yychar); ! YYDSYMPRINTF ("Next token is", yytoken, &yylval, &yylloc); } ! /* If the proper action on seeing token YYTOKEN is to reduce or to ! detect an error, take that action. */ ! yyn += yytoken; ! if (yyn < 0 || YYLAST < yyn || yycheck[yyn] != yytoken) goto yydefault; yyn = yytable[yyn]; ! if (yyn <= 0) { ! if (yyn == 0 || yyn == YYTABLE_NINF) goto yyerrlab; yyn = -yyn; goto yyreduce; } if (yyn == YYFINAL) YYACCEPT; /* Shift the lookahead token. */ ! YYDPRINTF ((stderr, "Shifting token %s, ", yytname[yytoken])); /* Discard the token being shifted unless it is eof. */ if (yychar != YYEOF) yychar = YYEMPTY; *++yyvsp = yylval; ! /* Count tokens shifted since error; after three, turn off error status. */ *************** yyreduce: *** 2335,2780 **** /* If YYLEN is nonzero, implement the default value of the action: `$$ = $1'. ! Otherwise, the following line sets YYVAL to the semantic value of ! the lookahead token. This behavior is undocumented and Bison users should not rely upon it. Assigning to YYVAL unconditionally makes the parser a bit smaller, and it avoids a GCC warning that YYVAL may be used uninitialized. */ yyval = yyvsp[1-yylen]; - #if YYLSP_NEEDED - /* Similarly for the default location. Let the user run additional - commands if for instance locations are ranges. */ - yyloc = yylsp[1-yylen]; - YYLLOC_DEFAULT (yyloc, (yylsp - yylen), yylen); - #endif ! #if YYDEBUG ! /* We have to keep this `#if YYDEBUG', since we use variables which ! are defined only if `YYDEBUG' is set. */ ! if (yydebug) { ! int yyi; ! ! YYFPRINTF (stderr, "Reducing via rule %d (line %d), ", ! yyn, yyrline[yyn]); ! ! /* Print the symbols being reduced, and their result. */ ! for (yyi = yyprhs[yyn]; yyrhs[yyi] > 0; yyi++) ! YYFPRINTF (stderr, "%s ", yytname[yyrhs[yyi]]); ! YYFPRINTF (stderr, " -> %s\n", yytname[yyr1[yyn]]); ! } ! #endif ! ! switch (yyn) { ! ! case 1: #line 287 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids an empty source file"); finish_file (); ! ; ! break;} ! case 2: #line 292 "c-parse.y" ! { /* In case there were missing closebraces, get us back to the global binding level. */ while (! global_bindings_p ()) poplevel (0, 0, 0); finish_fname_decls (); finish_file (); ! ; ! break;} ! case 3: #line 307 "c-parse.y" ! {yyval.ttype = NULL_TREE; ; ! break;} ! case 5: #line 308 "c-parse.y" ! {yyval.ttype = NULL_TREE; ggc_collect(); ; ! break;} ! case 9: #line 315 "c-parse.y" ! { STRIP_NOPS (yyvsp[-2].ttype); if ((TREE_CODE (yyvsp[-2].ttype) == ADDR_EXPR && TREE_CODE (TREE_OPERAND (yyvsp[-2].ttype, 0)) == STRING_CST) || TREE_CODE (yyvsp[-2].ttype) == STRING_CST) assemble_asm (yyvsp[-2].ttype); else ! error ("argument of `asm' is not a constant string"); ; ! break;} ! case 10: #line 323 "c-parse.y" ! { RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ; ! break;} ! case 11: #line 328 "c-parse.y" ! { if (pedantic) error ("ISO C forbids data definition with no type or storage class"); else if (!flag_traditional) warning ("data definition has no type or storage class"); ! POP_DECLSPEC_STACK; ; ! break;} ! case 12: #line 335 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 13: #line 337 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 14: #line 339 "c-parse.y" ! { shadow_tag (yyvsp[-1].ttype); ; ! break;} ! case 17: #line 343 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C does not allow extra `;' outside of a function"); ; ! break;} ! case 18: #line 349 "c-parse.y" ! { if (! start_function (current_declspecs, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ; ! break;} ! case 19: #line 354 "c-parse.y" ! { store_parm_decls (); ; ! break;} ! case 20: #line 356 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ; ! break;} ! case 21: #line 361 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 22: #line 363 "c-parse.y" ! { if (! start_function (current_declspecs, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ; ! break;} ! case 23: #line 368 "c-parse.y" ! { store_parm_decls (); ; ! break;} ! case 24: #line 370 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ; ! break;} ! case 25: #line 375 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 26: #line 377 "c-parse.y" ! { if (! start_function (NULL_TREE, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ; ! break;} ! case 27: #line 382 "c-parse.y" ! { store_parm_decls (); ; ! break;} ! case 28: #line 384 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ; ! break;} ! case 29: #line 389 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 32: #line 398 "c-parse.y" ! { yyval.code = ADDR_EXPR; ; ! break;} ! case 33: #line 400 "c-parse.y" ! { yyval.code = NEGATE_EXPR; ; ! break;} ! case 34: #line 402 "c-parse.y" ! { yyval.code = CONVERT_EXPR; if (warn_traditional && !in_system_header) warning ("traditional C rejects the unary plus operator"); ! ; ! break;} ! case 35: #line 407 "c-parse.y" ! { yyval.code = PREINCREMENT_EXPR; ; ! break;} ! case 36: #line 409 "c-parse.y" ! { yyval.code = PREDECREMENT_EXPR; ; ! break;} ! case 37: #line 411 "c-parse.y" ! { yyval.code = BIT_NOT_EXPR; ; ! break;} ! case 38: #line 413 "c-parse.y" ! { yyval.code = TRUTH_NOT_EXPR; ; ! break;} ! case 39: #line 417 "c-parse.y" ! { yyval.ttype = build_compound_expr (yyvsp[0].ttype); ; ! break;} ! case 40: #line 422 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 42: #line 428 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ; ! break;} ! case 43: #line 430 "c-parse.y" ! { chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ; ! break;} ! case 45: #line 436 "c-parse.y" ! { yyval.ttype = build_indirect_ref (yyvsp[0].ttype, "unary *"); ; ! break;} ! case 46: #line 439 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ; ! break;} ! case 47: #line 442 "c-parse.y" ! { yyval.ttype = build_unary_op (yyvsp[-1].code, yyvsp[0].ttype, 0); ! overflow_warning (yyval.ttype); ; ! break;} ! case 48: #line 446 "c-parse.y" ! { yyval.ttype = finish_label_address_expr (yyvsp[0].ttype); ; ! break;} ! case 49: #line 463 "c-parse.y" ! { skip_evaluation--; if (TREE_CODE (yyvsp[0].ttype) == COMPONENT_REF && DECL_C_BIT_FIELD (TREE_OPERAND (yyvsp[0].ttype, 1))) error ("`sizeof' applied to a bit-field"); ! yyval.ttype = c_sizeof (TREE_TYPE (yyvsp[0].ttype)); ; ! break;} ! case 50: #line 469 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_sizeof (groktypename (yyvsp[-1].ttype)); ; ! break;} ! case 51: #line 472 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_alignof_expr (yyvsp[0].ttype); ; ! break;} ! case 52: #line 475 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_alignof (groktypename (yyvsp[-1].ttype)); ; ! break;} ! case 53: #line 478 "c-parse.y" ! { yyval.ttype = build_unary_op (REALPART_EXPR, yyvsp[0].ttype, 0); ; ! break;} ! case 54: #line 480 "c-parse.y" ! { yyval.ttype = build_unary_op (IMAGPART_EXPR, yyvsp[0].ttype, 0); ; ! break;} ! case 55: #line 484 "c-parse.y" ! { skip_evaluation++; ; ! break;} ! case 56: #line 488 "c-parse.y" ! { skip_evaluation++; ; ! break;} ! case 57: #line 492 "c-parse.y" ! { skip_evaluation++; ; ! break;} ! case 59: #line 498 "c-parse.y" ! { yyval.ttype = c_cast_expr (yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 61: #line 504 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 62: #line 506 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 63: #line 508 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 64: #line 510 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 65: #line 512 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 66: #line 514 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 67: #line 516 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 68: #line 518 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 69: #line 520 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 70: #line 522 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 71: #line 524 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 72: #line 526 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 73: #line 528 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_false_node; ; ! break;} ! case 74: #line 531 "c-parse.y" ! { skip_evaluation -= yyvsp[-3].ttype == boolean_false_node; ! yyval.ttype = parser_build_binary_op (TRUTH_ANDIF_EXPR, yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 75: #line 534 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_true_node; ; ! break;} ! case 76: #line 537 "c-parse.y" ! { skip_evaluation -= yyvsp[-3].ttype == boolean_true_node; ! yyval.ttype = parser_build_binary_op (TRUTH_ORIF_EXPR, yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 77: #line 540 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_false_node; ; ! break;} ! case 78: #line 543 "c-parse.y" ! { skip_evaluation += ((yyvsp[-4].ttype == boolean_true_node) ! - (yyvsp[-4].ttype == boolean_false_node)); ; ! break;} ! case 79: #line 546 "c-parse.y" ! { skip_evaluation -= yyvsp[-6].ttype == boolean_true_node; ! yyval.ttype = build_conditional_expr (yyvsp[-6].ttype, yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 80: #line 549 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids omitting the middle term of a ?: expression"); /* Make sure first operand is calculated only once. */ yyvsp[0].ttype = save_expr (yyvsp[-1].ttype); yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[0].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_true_node; ; ! break;} ! case 81: #line 556 "c-parse.y" ! { skip_evaluation -= yyvsp[-4].ttype == boolean_true_node; ! yyval.ttype = build_conditional_expr (yyvsp[-4].ttype, yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 82: #line 559 "c-parse.y" ! { char class; yyval.ttype = build_modify_expr (yyvsp[-2].ttype, NOP_EXPR, yyvsp[0].ttype); class = TREE_CODE_CLASS (TREE_CODE (yyval.ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyval.ttype, MODIFY_EXPR); ! ; ! break;} ! case 83: #line 566 "c-parse.y" ! { char class; yyval.ttype = build_modify_expr (yyvsp[-2].ttype, yyvsp[-1].code, yyvsp[0].ttype); /* This inhibits warnings in truthvalue_conversion. */ class = TREE_CODE_CLASS (TREE_CODE (yyval.ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyval.ttype, ERROR_MARK); ! ; ! break;} ! case 84: #line 577 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; yyval.ttype = build_external_ref (yyvsp[0].ttype, yychar == '('); ! ; ! break;} ! case 86: #line 584 "c-parse.y" ! { yyval.ttype = combine_strings (yyvsp[0].ttype); ; ! break;} ! case 87: #line 586 "c-parse.y" ! { yyval.ttype = fname_decl (C_RID_CODE (yyval.ttype), yyval.ttype); ; ! break;} ! case 88: #line 588 "c-parse.y" ! { start_init (NULL_TREE, NULL, 0); yyvsp[-2].ttype = groktypename (yyvsp[-2].ttype); ! really_start_incremental_init (yyvsp[-2].ttype); ; ! break;} ! case 89: #line 592 "c-parse.y" ! { tree constructor = pop_init_level (0); tree type = yyvsp[-5].ttype; finish_init (); if (pedantic && ! flag_isoc99) pedwarn ("ISO C89 forbids compound literals"); yyval.ttype = build_compound_literal (type, constructor); ! ; ! break;} ! case 90: #line 601 "c-parse.y" ! { char class = TREE_CODE_CLASS (TREE_CODE (yyvsp[-1].ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyvsp[-1].ttype, ERROR_MARK); ! yyval.ttype = yyvsp[-1].ttype; ; ! break;} ! case 91: #line 606 "c-parse.y" ! { yyval.ttype = error_mark_node; ; ! break;} ! case 92: #line 608 "c-parse.y" ! { tree saved_last_tree; if (pedantic) pedwarn ("ISO C forbids braced-groups within expressions"); --- 2601,3102 ---- /* If YYLEN is nonzero, implement the default value of the action: `$$ = $1'. ! Otherwise, the following line sets YYVAL to garbage. ! This behavior is undocumented and Bison users should not rely upon it. Assigning to YYVAL unconditionally makes the parser a bit smaller, and it avoids a GCC warning that YYVAL may be used uninitialized. */ yyval = yyvsp[1-yylen]; ! YY_REDUCE_PRINT (yyn); ! switch (yyn) { ! case 2: #line 287 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids an empty source file"); finish_file (); ! ;} ! break; ! ! case 3: #line 292 "c-parse.y" ! { /* In case there were missing closebraces, get us back to the global binding level. */ while (! global_bindings_p ()) poplevel (0, 0, 0); finish_fname_decls (); finish_file (); ! ;} ! break; ! ! case 4: #line 307 "c-parse.y" ! {yyval.ttype = NULL_TREE; ;} ! break; ! ! case 6: #line 308 "c-parse.y" ! {yyval.ttype = NULL_TREE; ggc_collect(); ;} ! break; ! ! case 10: #line 315 "c-parse.y" ! { STRIP_NOPS (yyvsp[-2].ttype); if ((TREE_CODE (yyvsp[-2].ttype) == ADDR_EXPR && TREE_CODE (TREE_OPERAND (yyvsp[-2].ttype, 0)) == STRING_CST) || TREE_CODE (yyvsp[-2].ttype) == STRING_CST) assemble_asm (yyvsp[-2].ttype); else ! error ("argument of `asm' is not a constant string"); ;} ! break; ! ! case 11: #line 323 "c-parse.y" ! { RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ;} ! break; ! ! case 12: #line 328 "c-parse.y" ! { if (pedantic) error ("ISO C forbids data definition with no type or storage class"); else if (!flag_traditional) warning ("data definition has no type or storage class"); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 13: #line 335 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 14: #line 337 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 15: #line 339 "c-parse.y" ! { shadow_tag (yyvsp[-1].ttype); ;} ! break; ! ! case 18: #line 343 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C does not allow extra `;' outside of a function"); ;} ! break; ! ! case 19: #line 349 "c-parse.y" ! { if (! start_function (current_declspecs, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ;} ! break; ! ! case 20: #line 354 "c-parse.y" ! { store_parm_decls (); ;} ! break; ! ! case 21: #line 356 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 22: #line 361 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 23: #line 363 "c-parse.y" ! { if (! start_function (current_declspecs, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ;} ! break; ! ! case 24: #line 368 "c-parse.y" ! { store_parm_decls (); ;} ! break; ! ! case 25: #line 370 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 26: #line 375 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 27: #line 377 "c-parse.y" ! { if (! start_function (NULL_TREE, yyvsp[0].ttype, all_prefix_attributes)) YYERROR1; ! ;} ! break; ! ! case 28: #line 382 "c-parse.y" ! { store_parm_decls (); ;} ! break; ! ! case 29: #line 384 "c-parse.y" ! { DECL_SOURCE_FILE (current_function_decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (current_function_decl) = yyvsp[-1].lineno; finish_function (0, 1); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 30: #line 389 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 33: #line 398 "c-parse.y" ! { yyval.code = ADDR_EXPR; ;} ! break; ! ! case 34: #line 400 "c-parse.y" ! { yyval.code = NEGATE_EXPR; ;} ! break; ! ! case 35: #line 402 "c-parse.y" ! { yyval.code = CONVERT_EXPR; if (warn_traditional && !in_system_header) warning ("traditional C rejects the unary plus operator"); ! ;} ! break; ! ! case 36: #line 407 "c-parse.y" ! { yyval.code = PREINCREMENT_EXPR; ;} ! break; ! ! case 37: #line 409 "c-parse.y" ! { yyval.code = PREDECREMENT_EXPR; ;} ! break; ! ! case 38: #line 411 "c-parse.y" ! { yyval.code = BIT_NOT_EXPR; ;} ! break; ! ! case 39: #line 413 "c-parse.y" ! { yyval.code = TRUTH_NOT_EXPR; ;} ! break; ! ! case 40: #line 417 "c-parse.y" ! { yyval.ttype = build_compound_expr (yyvsp[0].ttype); ;} ! break; ! ! case 41: #line 422 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 43: #line 428 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ;} ! break; ! ! case 44: #line 430 "c-parse.y" ! { chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ;} ! break; ! ! case 46: #line 436 "c-parse.y" ! { yyval.ttype = build_indirect_ref (yyvsp[0].ttype, "unary *"); ;} ! break; ! ! case 47: #line 439 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ;} ! break; ! ! case 48: #line 442 "c-parse.y" ! { yyval.ttype = build_unary_op (yyvsp[-1].code, yyvsp[0].ttype, 0); ! overflow_warning (yyval.ttype); ;} ! break; ! ! case 49: #line 446 "c-parse.y" ! { yyval.ttype = finish_label_address_expr (yyvsp[0].ttype); ;} ! break; ! ! case 50: #line 463 "c-parse.y" ! { skip_evaluation--; if (TREE_CODE (yyvsp[0].ttype) == COMPONENT_REF && DECL_C_BIT_FIELD (TREE_OPERAND (yyvsp[0].ttype, 1))) error ("`sizeof' applied to a bit-field"); ! yyval.ttype = c_sizeof (TREE_TYPE (yyvsp[0].ttype)); ;} ! break; ! ! case 51: #line 469 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_sizeof (groktypename (yyvsp[-1].ttype)); ;} ! break; ! ! case 52: #line 472 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_alignof_expr (yyvsp[0].ttype); ;} ! break; ! ! case 53: #line 475 "c-parse.y" ! { skip_evaluation--; ! yyval.ttype = c_alignof (groktypename (yyvsp[-1].ttype)); ;} ! break; ! ! case 54: #line 478 "c-parse.y" ! { yyval.ttype = build_unary_op (REALPART_EXPR, yyvsp[0].ttype, 0); ;} ! break; ! ! case 55: #line 480 "c-parse.y" ! { yyval.ttype = build_unary_op (IMAGPART_EXPR, yyvsp[0].ttype, 0); ;} ! break; ! ! case 56: #line 484 "c-parse.y" ! { skip_evaluation++; ;} ! break; ! ! case 57: #line 488 "c-parse.y" ! { skip_evaluation++; ;} ! break; ! ! case 58: #line 492 "c-parse.y" ! { skip_evaluation++; ;} ! break; ! ! case 60: #line 498 "c-parse.y" ! { yyval.ttype = c_cast_expr (yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 62: #line 504 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 63: #line 506 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 64: #line 508 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 65: #line 510 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 66: #line 512 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 67: #line 514 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 68: #line 516 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 69: #line 518 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 70: #line 520 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 71: #line 522 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 72: #line 524 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 73: #line 526 "c-parse.y" ! { yyval.ttype = parser_build_binary_op (yyvsp[-1].code, yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 74: #line 528 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_false_node; ;} ! break; ! ! case 75: #line 531 "c-parse.y" ! { skip_evaluation -= yyvsp[-3].ttype == boolean_false_node; ! yyval.ttype = parser_build_binary_op (TRUTH_ANDIF_EXPR, yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 76: #line 534 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_true_node; ;} ! break; ! ! case 77: #line 537 "c-parse.y" ! { skip_evaluation -= yyvsp[-3].ttype == boolean_true_node; ! yyval.ttype = parser_build_binary_op (TRUTH_ORIF_EXPR, yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 78: #line 540 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[-1].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_false_node; ;} ! break; ! ! case 79: #line 543 "c-parse.y" ! { skip_evaluation += ((yyvsp[-4].ttype == boolean_true_node) ! - (yyvsp[-4].ttype == boolean_false_node)); ;} ! break; ! ! case 80: #line 546 "c-parse.y" ! { skip_evaluation -= yyvsp[-6].ttype == boolean_true_node; ! yyval.ttype = build_conditional_expr (yyvsp[-6].ttype, yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 81: #line 549 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids omitting the middle term of a ?: expression"); /* Make sure first operand is calculated only once. */ yyvsp[0].ttype = save_expr (yyvsp[-1].ttype); yyvsp[-1].ttype = truthvalue_conversion (default_conversion (yyvsp[0].ttype)); ! skip_evaluation += yyvsp[-1].ttype == boolean_true_node; ;} ! break; ! ! case 82: #line 556 "c-parse.y" ! { skip_evaluation -= yyvsp[-4].ttype == boolean_true_node; ! yyval.ttype = build_conditional_expr (yyvsp[-4].ttype, yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 83: #line 559 "c-parse.y" ! { char class; yyval.ttype = build_modify_expr (yyvsp[-2].ttype, NOP_EXPR, yyvsp[0].ttype); class = TREE_CODE_CLASS (TREE_CODE (yyval.ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyval.ttype, MODIFY_EXPR); ! ;} ! break; ! ! case 84: #line 566 "c-parse.y" ! { char class; yyval.ttype = build_modify_expr (yyvsp[-2].ttype, yyvsp[-1].code, yyvsp[0].ttype); /* This inhibits warnings in truthvalue_conversion. */ class = TREE_CODE_CLASS (TREE_CODE (yyval.ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyval.ttype, ERROR_MARK); ! ;} ! break; ! ! case 85: #line 577 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; yyval.ttype = build_external_ref (yyvsp[0].ttype, yychar == '('); ! ;} ! break; ! ! case 87: #line 584 "c-parse.y" ! { yyval.ttype = combine_strings (yyvsp[0].ttype); ;} ! break; ! ! case 88: #line 586 "c-parse.y" ! { yyval.ttype = fname_decl (C_RID_CODE (yyval.ttype), yyval.ttype); ;} ! break; ! ! case 89: #line 588 "c-parse.y" ! { start_init (NULL_TREE, NULL, 0); yyvsp[-2].ttype = groktypename (yyvsp[-2].ttype); ! really_start_incremental_init (yyvsp[-2].ttype); ;} ! break; ! ! case 90: #line 592 "c-parse.y" ! { tree constructor = pop_init_level (0); tree type = yyvsp[-5].ttype; finish_init (); if (pedantic && ! flag_isoc99) pedwarn ("ISO C89 forbids compound literals"); yyval.ttype = build_compound_literal (type, constructor); ! ;} ! break; ! ! case 91: #line 601 "c-parse.y" ! { char class = TREE_CODE_CLASS (TREE_CODE (yyvsp[-1].ttype)); if (IS_EXPR_CODE_CLASS (class)) C_SET_EXP_ORIGINAL_CODE (yyvsp[-1].ttype, ERROR_MARK); ! yyval.ttype = yyvsp[-1].ttype; ;} ! break; ! ! case 92: #line 606 "c-parse.y" ! { yyval.ttype = error_mark_node; ;} ! break; ! ! case 93: #line 608 "c-parse.y" ! { tree saved_last_tree; if (pedantic) pedwarn ("ISO C forbids braced-groups within expressions"); *************** case 92: *** 2788,2815 **** last_expr_type = void_type_node; yyval.ttype = build1 (STMT_EXPR, last_expr_type, yyvsp[-2].ttype); TREE_SIDE_EFFECTS (yyval.ttype) = 1; ! ; ! break;} ! case 93: #line 624 "c-parse.y" ! { pop_label_level (); last_tree = COMPOUND_BODY (yyvsp[-2].ttype); TREE_CHAIN (last_tree) = NULL_TREE; yyval.ttype = error_mark_node; ! ; ! break;} ! case 94: #line 631 "c-parse.y" ! { yyval.ttype = build_function_call (yyvsp[-3].ttype, yyvsp[-1].ttype); ; ! break;} ! case 95: #line 633 "c-parse.y" ! { yyval.ttype = build_va_arg (yyvsp[-3].ttype, groktypename (yyvsp[-1].ttype)); ; ! break;} ! case 96: #line 636 "c-parse.y" ! { tree c; c = fold (yyvsp[-5].ttype); --- 3110,3141 ---- last_expr_type = void_type_node; yyval.ttype = build1 (STMT_EXPR, last_expr_type, yyvsp[-2].ttype); TREE_SIDE_EFFECTS (yyval.ttype) = 1; ! ;} ! break; ! ! case 94: #line 624 "c-parse.y" ! { pop_label_level (); last_tree = COMPOUND_BODY (yyvsp[-2].ttype); TREE_CHAIN (last_tree) = NULL_TREE; yyval.ttype = error_mark_node; ! ;} ! break; ! ! case 95: #line 631 "c-parse.y" ! { yyval.ttype = build_function_call (yyvsp[-3].ttype, yyvsp[-1].ttype); ;} ! break; ! ! case 96: #line 633 "c-parse.y" ! { yyval.ttype = build_va_arg (yyvsp[-3].ttype, groktypename (yyvsp[-1].ttype)); ;} ! break; ! ! case 97: #line 636 "c-parse.y" ! { tree c; c = fold (yyvsp[-5].ttype); *************** case 96: *** 2817,2827 **** if (TREE_CODE (c) != INTEGER_CST) error ("first argument to __builtin_choose_expr not a constant"); yyval.ttype = integer_zerop (c) ? yyvsp[-1].ttype : yyvsp[-3].ttype; ! ; ! break;} ! case 97: #line 646 "c-parse.y" ! { tree e1, e2; e1 = TYPE_MAIN_VARIANT (groktypename (yyvsp[-3].ttype)); --- 3143,3154 ---- if (TREE_CODE (c) != INTEGER_CST) error ("first argument to __builtin_choose_expr not a constant"); yyval.ttype = integer_zerop (c) ? yyvsp[-1].ttype : yyvsp[-3].ttype; ! ;} ! break; ! ! case 98: #line 646 "c-parse.y" ! { tree e1, e2; e1 = TYPE_MAIN_VARIANT (groktypename (yyvsp[-3].ttype)); *************** case 97: *** 2829,2865 **** yyval.ttype = comptypes (e1, e2) ? build_int_2 (1, 0) : build_int_2 (0, 0); ! ; ! break;} ! case 98: #line 656 "c-parse.y" ! { yyval.ttype = build_array_ref (yyvsp[-3].ttype, yyvsp[-1].ttype); ; ! break;} ! case 99: #line 658 "c-parse.y" ! { yyval.ttype = build_component_ref (yyvsp[-2].ttype, yyvsp[0].ttype); ! ; ! break;} ! case 100: #line 662 "c-parse.y" ! { tree expr = build_indirect_ref (yyvsp[-2].ttype, "->"); yyval.ttype = build_component_ref (expr, yyvsp[0].ttype); ! ; ! break;} ! case 101: #line 668 "c-parse.y" ! { yyval.ttype = build_unary_op (POSTINCREMENT_EXPR, yyvsp[-1].ttype, 0); ; ! break;} ! case 102: #line 670 "c-parse.y" ! { yyval.ttype = build_unary_op (POSTDECREMENT_EXPR, yyvsp[-1].ttype, 0); ; ! break;} ! case 104: #line 677 "c-parse.y" ! { static int last_lineno = 0; static const char *last_input_filename = 0; yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); --- 3156,3198 ---- yyval.ttype = comptypes (e1, e2) ? build_int_2 (1, 0) : build_int_2 (0, 0); ! ;} ! break; ! ! case 99: #line 656 "c-parse.y" ! { yyval.ttype = build_array_ref (yyvsp[-3].ttype, yyvsp[-1].ttype); ;} ! break; ! ! case 100: #line 658 "c-parse.y" ! { yyval.ttype = build_component_ref (yyvsp[-2].ttype, yyvsp[0].ttype); ! ;} ! break; ! ! case 101: #line 662 "c-parse.y" ! { tree expr = build_indirect_ref (yyvsp[-2].ttype, "->"); yyval.ttype = build_component_ref (expr, yyvsp[0].ttype); ! ;} ! break; ! ! case 102: #line 668 "c-parse.y" ! { yyval.ttype = build_unary_op (POSTINCREMENT_EXPR, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 103: #line 670 "c-parse.y" ! { yyval.ttype = build_unary_op (POSTDECREMENT_EXPR, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 105: #line 677 "c-parse.y" ! { static int last_lineno = 0; static const char *last_input_filename = 0; yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); *************** case 104: *** 2871,3563 **** last_lineno = lineno; last_input_filename = input_filename; } ! ; ! break;} ! case 107: #line 698 "c-parse.y" ! { c_mark_varargs (); if (pedantic) ! pedwarn ("ISO C does not permit use of `varargs.h'"); ; ! break;} ! case 108: #line 708 "c-parse.y" ! { ; ! break;} ! case 113: #line 724 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 114: #line 726 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 115: #line 728 "c-parse.y" ! { shadow_tag_warned (yyvsp[-1].ttype, 1); ! pedwarn ("empty declaration"); ; ! break;} ! case 116: #line 731 "c-parse.y" ! { pedwarn ("empty declaration"); ; ! break;} ! case 117: #line 740 "c-parse.y" ! { ; ! break;} ! case 118: #line 748 "c-parse.y" ! { pending_xref_error (); PUSH_DECLSPEC_STACK; split_specs_attrs (yyvsp[0].ttype, ¤t_declspecs, &prefix_attributes); ! all_prefix_attributes = prefix_attributes; ; ! break;} ! case 119: #line 759 "c-parse.y" ! { all_prefix_attributes = chainon (yyvsp[0].ttype, prefix_attributes); ; ! break;} ! case 120: #line 764 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 121: #line 766 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 122: #line 768 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 123: #line 770 "c-parse.y" ! { POP_DECLSPEC_STACK; ; ! break;} ! case 124: #line 772 "c-parse.y" ! { shadow_tag (yyvsp[-1].ttype); ; ! break;} ! case 125: #line 774 "c-parse.y" ! { RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ; ! break;} ! case 126: #line 831 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 127: #line 834 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 128: #line 837 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 129: #line 843 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 130: #line 849 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 131: #line 852 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 132: #line 858 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 0; ; ! break;} ! case 133: #line 861 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 134: #line 867 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 135: #line 870 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 136: #line 873 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 137: #line 876 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 138: #line 879 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 139: #line 882 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 140: #line 885 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 141: #line 891 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 142: #line 894 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 143: #line 897 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 144: #line 900 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 145: #line 903 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 146: #line 906 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 147: #line 912 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 148: #line 915 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 149: #line 918 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 150: #line 921 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 151: #line 924 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 152: #line 927 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 153: #line 933 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 154: #line 936 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 155: #line 939 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 156: #line 942 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 157: #line 945 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 158: #line 951 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 0; ; ! break;} ! case 159: #line 954 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 160: #line 957 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 161: #line 960 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 162: #line 966 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 163: #line 972 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 164: #line 978 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 165: #line 987 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 166: #line 993 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 167: #line 996 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 168: #line 999 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 169: #line 1005 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 170: #line 1011 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 171: #line 1017 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 172: #line 1026 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 173: #line 1032 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 174: #line 1035 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 175: #line 1038 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 176: #line 1041 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 177: #line 1044 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 178: #line 1047 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 179: #line 1050 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 180: #line 1056 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 181: #line 1062 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 182: #line 1068 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 183: #line 1077 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 184: #line 1080 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 185: #line 1083 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 186: #line 1086 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 187: #line 1089 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 188: #line 1095 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 189: #line 1098 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 190: #line 1101 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 191: #line 1104 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 192: #line 1107 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 193: #line 1110 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 194: #line 1113 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 195: #line 1119 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 196: #line 1125 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 197: #line 1131 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 198: #line 1140 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ; ! break;} ! case 199: #line 1143 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 200: #line 1146 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 201: #line 1149 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 202: #line 1152 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ; ! break;} ! case 259: #line 1240 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 260: #line 1242 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 264: #line 1277 "c-parse.y" ! { OBJC_NEED_RAW_IDENTIFIER (1); ; ! break;} ! case 267: #line 1287 "c-parse.y" ! { /* For a typedef name, record the meaning, not the name. In case of `foo foo, bar;'. */ ! yyval.ttype = lookup_name (yyvsp[0].ttype); ; ! break;} ! case 268: #line 1291 "c-parse.y" ! { skip_evaluation--; yyval.ttype = TREE_TYPE (yyvsp[-1].ttype); ; ! break;} ! case 269: #line 1293 "c-parse.y" ! { skip_evaluation--; yyval.ttype = groktypename (yyvsp[-1].ttype); ; ! break;} ! case 274: #line 1310 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 275: #line 1312 "c-parse.y" ! { if (TREE_CHAIN (yyvsp[-1].ttype)) yyvsp[-1].ttype = combine_strings (yyvsp[-1].ttype); yyval.ttype = yyvsp[-1].ttype; ! ; ! break;} ! case 276: #line 1319 "c-parse.y" ! { yyval.ttype = start_decl (yyvsp[-3].ttype, current_declspecs, 1, chainon (yyvsp[-1].ttype, all_prefix_attributes)); ! start_init (yyval.ttype, yyvsp[-2].ttype, global_bindings_p ()); ; ! break;} ! case 277: #line 1324 "c-parse.y" ! { finish_init (); ! finish_decl (yyvsp[-1].ttype, yyvsp[0].ttype, yyvsp[-4].ttype); ; ! break;} ! case 278: #line 1327 "c-parse.y" ! { tree d = start_decl (yyvsp[-2].ttype, current_declspecs, 0, chainon (yyvsp[0].ttype, all_prefix_attributes)); finish_decl (d, NULL_TREE, yyvsp[-1].ttype); ! ; ! break;} ! case 279: #line 1335 "c-parse.y" ! { yyval.ttype = start_decl (yyvsp[-3].ttype, current_declspecs, 1, chainon (yyvsp[-1].ttype, all_prefix_attributes)); ! start_init (yyval.ttype, yyvsp[-2].ttype, global_bindings_p ()); ; ! break;} ! case 280: #line 1340 "c-parse.y" ! { finish_init (); ! finish_decl (yyvsp[-1].ttype, yyvsp[0].ttype, yyvsp[-4].ttype); ; ! break;} ! case 281: #line 1343 "c-parse.y" ! { tree d = start_decl (yyvsp[-2].ttype, current_declspecs, 0, chainon (yyvsp[0].ttype, all_prefix_attributes)); ! finish_decl (d, NULL_TREE, yyvsp[-1].ttype); ; ! break;} ! case 282: #line 1351 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 283: #line 1353 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 284: #line 1358 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 285: #line 1360 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 286: #line 1365 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype; ; ! break;} ! case 287: #line 1370 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 288: #line 1372 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 289: #line 1377 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 290: #line 1379 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 291: #line 1381 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-3].ttype, build_tree_list (NULL_TREE, yyvsp[-1].ttype)); ; ! break;} ! case 292: #line 1383 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-5].ttype, tree_cons (NULL_TREE, yyvsp[-3].ttype, yyvsp[-1].ttype)); ; ! break;} ! case 293: #line 1385 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-3].ttype, yyvsp[-1].ttype); ; ! break;} ! case 299: #line 1403 "c-parse.y" ! { really_start_incremental_init (NULL_TREE); ; ! break;} ! case 300: #line 1405 "c-parse.y" ! { yyval.ttype = pop_init_level (0); ; ! break;} ! case 301: #line 1407 "c-parse.y" ! { yyval.ttype = error_mark_node; ; ! break;} ! case 302: #line 1413 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C forbids empty initializer braces"); ; ! break;} ! case 306: #line 1427 "c-parse.y" ! { if (pedantic && ! flag_isoc99) ! pedwarn ("ISO C89 forbids specifying subobject to initialize"); ; ! break;} ! case 307: #line 1430 "c-parse.y" ! { if (pedantic) ! pedwarn ("obsolete use of designated initializer without `='"); ; ! break;} ! case 308: #line 1433 "c-parse.y" ! { set_init_label (yyvsp[-1].ttype); if (pedantic) ! pedwarn ("obsolete use of designated initializer with `:'"); ; ! break;} ! case 309: #line 1437 "c-parse.y" ! {; ! break;} ! case 311: #line 1443 "c-parse.y" ! { push_init_level (0); ; ! break;} ! case 312: #line 1445 "c-parse.y" ! { process_init_element (pop_init_level (0)); ; ! break;} ! case 313: #line 1447 "c-parse.y" ! { process_init_element (yyvsp[0].ttype); ; ! break;} ! case 317: #line 1458 "c-parse.y" ! { set_init_label (yyvsp[0].ttype); ; ! break;} ! case 318: #line 1463 "c-parse.y" ! { set_init_index (yyvsp[-3].ttype, yyvsp[-1].ttype); if (pedantic) ! pedwarn ("ISO C forbids specifying range of elements to initialize"); ; ! break;} ! case 319: #line 1467 "c-parse.y" ! { set_init_index (yyvsp[-1].ttype, NULL_TREE); ; ! break;} ! case 320: #line 1472 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids nested functions"); push_function_context (); --- 3204,4029 ---- last_lineno = lineno; last_input_filename = input_filename; } ! ;} ! break; ! ! case 108: #line 698 "c-parse.y" ! { c_mark_varargs (); if (pedantic) ! pedwarn ("ISO C does not permit use of `varargs.h'"); ;} ! break; ! ! case 109: #line 708 "c-parse.y" ! { ;} ! break; ! ! case 114: #line 724 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 115: #line 726 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 116: #line 728 "c-parse.y" ! { shadow_tag_warned (yyvsp[-1].ttype, 1); ! pedwarn ("empty declaration"); ;} ! break; ! ! case 117: #line 731 "c-parse.y" ! { pedwarn ("empty declaration"); ;} ! break; ! ! case 118: #line 740 "c-parse.y" ! { ;} ! break; ! ! case 119: #line 748 "c-parse.y" ! { pending_xref_error (); PUSH_DECLSPEC_STACK; split_specs_attrs (yyvsp[0].ttype, ¤t_declspecs, &prefix_attributes); ! all_prefix_attributes = prefix_attributes; ;} ! break; ! ! case 120: #line 759 "c-parse.y" ! { all_prefix_attributes = chainon (yyvsp[0].ttype, prefix_attributes); ;} ! break; ! ! case 121: #line 764 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 122: #line 766 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 123: #line 768 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 124: #line 770 "c-parse.y" ! { POP_DECLSPEC_STACK; ;} ! break; ! ! case 125: #line 772 "c-parse.y" ! { shadow_tag (yyvsp[-1].ttype); ;} ! break; ! ! case 126: #line 774 "c-parse.y" ! { RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ;} ! break; ! ! case 127: #line 831 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 128: #line 834 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 129: #line 837 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 130: #line 843 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 131: #line 849 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 132: #line 852 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 133: #line 858 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 0; ;} ! break; ! ! case 134: #line 861 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 135: #line 867 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 136: #line 870 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 137: #line 873 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 138: #line 876 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 139: #line 879 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 140: #line 882 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 141: #line 885 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 142: #line 891 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 143: #line 894 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 144: #line 897 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 145: #line 900 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 146: #line 903 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 147: #line 906 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 148: #line 912 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 149: #line 915 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 150: #line 918 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 151: #line 921 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 152: #line 924 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 153: #line 927 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 154: #line 933 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 155: #line 936 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 156: #line 939 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 157: #line 942 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 158: #line 945 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 159: #line 951 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, NULL_TREE); ! TREE_STATIC (yyval.ttype) = 0; ;} ! break; ! ! case 160: #line 954 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 161: #line 957 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 162: #line 960 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 163: #line 966 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 164: #line 972 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 165: #line 978 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 166: #line 987 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 167: #line 993 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 168: #line 996 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 169: #line 999 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 170: #line 1005 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 171: #line 1011 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 172: #line 1017 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 173: #line 1026 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 174: #line 1032 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 175: #line 1035 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 176: #line 1038 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 177: #line 1041 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 178: #line 1044 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 179: #line 1047 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 180: #line 1050 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 181: #line 1056 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 182: #line 1062 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 183: #line 1068 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 184: #line 1077 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 185: #line 1080 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 186: #line 1083 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 187: #line 1086 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 188: #line 1089 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 189: #line 1095 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 190: #line 1098 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 191: #line 1101 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 192: #line 1104 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 193: #line 1107 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 194: #line 1110 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 195: #line 1113 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 196: #line 1119 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 197: #line 1125 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 198: #line 1131 "c-parse.y" ! { if (extra_warnings && TREE_STATIC (yyvsp[-1].ttype)) warning ("`%s' is not at beginning of declaration", IDENTIFIER_POINTER (yyvsp[0].ttype)); yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 199: #line 1140 "c-parse.y" ! { yyval.ttype = tree_cons (yyvsp[0].ttype, NULL_TREE, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = TREE_STATIC (yyvsp[-1].ttype); ;} ! break; ! ! case 200: #line 1143 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 201: #line 1146 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 202: #line 1149 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 203: #line 1152 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, yyvsp[0].ttype, yyvsp[-1].ttype); ! TREE_STATIC (yyval.ttype) = 1; ;} ! break; ! ! case 260: #line 1240 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 261: #line 1242 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 265: #line 1277 "c-parse.y" ! { OBJC_NEED_RAW_IDENTIFIER (1); ;} ! break; ! ! case 268: #line 1287 "c-parse.y" ! { /* For a typedef name, record the meaning, not the name. In case of `foo foo, bar;'. */ ! yyval.ttype = lookup_name (yyvsp[0].ttype); ;} ! break; ! ! case 269: #line 1291 "c-parse.y" ! { skip_evaluation--; yyval.ttype = TREE_TYPE (yyvsp[-1].ttype); ;} ! break; ! ! case 270: #line 1293 "c-parse.y" ! { skip_evaluation--; yyval.ttype = groktypename (yyvsp[-1].ttype); ;} ! break; ! ! case 275: #line 1310 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 276: #line 1312 "c-parse.y" ! { if (TREE_CHAIN (yyvsp[-1].ttype)) yyvsp[-1].ttype = combine_strings (yyvsp[-1].ttype); yyval.ttype = yyvsp[-1].ttype; ! ;} ! break; ! ! case 277: #line 1319 "c-parse.y" ! { yyval.ttype = start_decl (yyvsp[-3].ttype, current_declspecs, 1, chainon (yyvsp[-1].ttype, all_prefix_attributes)); ! start_init (yyval.ttype, yyvsp[-2].ttype, global_bindings_p ()); ;} ! break; ! ! case 278: #line 1324 "c-parse.y" ! { finish_init (); ! finish_decl (yyvsp[-1].ttype, yyvsp[0].ttype, yyvsp[-4].ttype); ;} ! break; ! ! case 279: #line 1327 "c-parse.y" ! { tree d = start_decl (yyvsp[-2].ttype, current_declspecs, 0, chainon (yyvsp[0].ttype, all_prefix_attributes)); finish_decl (d, NULL_TREE, yyvsp[-1].ttype); ! ;} ! break; ! ! case 280: #line 1335 "c-parse.y" ! { yyval.ttype = start_decl (yyvsp[-3].ttype, current_declspecs, 1, chainon (yyvsp[-1].ttype, all_prefix_attributes)); ! start_init (yyval.ttype, yyvsp[-2].ttype, global_bindings_p ()); ;} ! break; ! ! case 281: #line 1340 "c-parse.y" ! { finish_init (); ! finish_decl (yyvsp[-1].ttype, yyvsp[0].ttype, yyvsp[-4].ttype); ;} ! break; ! ! case 282: #line 1343 "c-parse.y" ! { tree d = start_decl (yyvsp[-2].ttype, current_declspecs, 0, chainon (yyvsp[0].ttype, all_prefix_attributes)); ! finish_decl (d, NULL_TREE, yyvsp[-1].ttype); ;} ! break; ! ! case 283: #line 1351 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 284: #line 1353 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 285: #line 1358 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 286: #line 1360 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 287: #line 1365 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype; ;} ! break; ! ! case 288: #line 1370 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 289: #line 1372 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 290: #line 1377 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 291: #line 1379 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 292: #line 1381 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-3].ttype, build_tree_list (NULL_TREE, yyvsp[-1].ttype)); ;} ! break; ! ! case 293: #line 1383 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-5].ttype, tree_cons (NULL_TREE, yyvsp[-3].ttype, yyvsp[-1].ttype)); ;} ! break; ! ! case 294: #line 1385 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-3].ttype, yyvsp[-1].ttype); ;} ! break; ! ! case 300: #line 1403 "c-parse.y" ! { really_start_incremental_init (NULL_TREE); ;} ! break; ! ! case 301: #line 1405 "c-parse.y" ! { yyval.ttype = pop_init_level (0); ;} ! break; ! ! case 302: #line 1407 "c-parse.y" ! { yyval.ttype = error_mark_node; ;} ! break; ! ! case 303: #line 1413 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C forbids empty initializer braces"); ;} ! break; ! ! case 307: #line 1427 "c-parse.y" ! { if (pedantic && ! flag_isoc99) ! pedwarn ("ISO C89 forbids specifying subobject to initialize"); ;} ! break; ! ! case 308: #line 1430 "c-parse.y" ! { if (pedantic) ! pedwarn ("obsolete use of designated initializer without `='"); ;} ! break; ! ! case 309: #line 1433 "c-parse.y" ! { set_init_label (yyvsp[-1].ttype); if (pedantic) ! pedwarn ("obsolete use of designated initializer with `:'"); ;} ! break; ! ! case 310: #line 1437 "c-parse.y" ! {;} ! break; ! ! case 312: #line 1443 "c-parse.y" ! { push_init_level (0); ;} ! break; ! ! case 313: #line 1445 "c-parse.y" ! { process_init_element (pop_init_level (0)); ;} ! break; ! ! case 314: #line 1447 "c-parse.y" ! { process_init_element (yyvsp[0].ttype); ;} ! break; ! ! case 318: #line 1458 "c-parse.y" ! { set_init_label (yyvsp[0].ttype); ;} ! break; ! ! case 319: #line 1463 "c-parse.y" ! { set_init_index (yyvsp[-3].ttype, yyvsp[-1].ttype); if (pedantic) ! pedwarn ("ISO C forbids specifying range of elements to initialize"); ;} ! break; ! ! case 320: #line 1467 "c-parse.y" ! { set_init_index (yyvsp[-1].ttype, NULL_TREE); ;} ! break; ! ! case 321: #line 1472 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids nested functions"); push_function_context (); *************** case 320: *** 3567,3590 **** pop_function_context (); YYERROR1; } ! ; ! break;} ! case 321: #line 1484 "c-parse.y" ! { store_parm_decls (); ; ! break;} ! case 322: #line 1492 "c-parse.y" ! { tree decl = current_function_decl; DECL_SOURCE_FILE (decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (decl) = yyvsp[-1].lineno; finish_function (1, 1); pop_function_context (); ! add_decl_stmt (decl); ; ! break;} ! case 323: #line 1502 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids nested functions"); push_function_context (); --- 4033,4059 ---- pop_function_context (); YYERROR1; } ! ;} ! break; ! ! case 322: #line 1484 "c-parse.y" ! { store_parm_decls (); ;} ! break; ! ! case 323: #line 1492 "c-parse.y" ! { tree decl = current_function_decl; DECL_SOURCE_FILE (decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (decl) = yyvsp[-1].lineno; finish_function (1, 1); pop_function_context (); ! add_decl_stmt (decl); ;} ! break; ! ! case 324: #line 1502 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids nested functions"); push_function_context (); *************** case 323: *** 3594,3797 **** pop_function_context (); YYERROR1; } ! ; ! break;} ! case 324: #line 1514 "c-parse.y" ! { store_parm_decls (); ; ! break;} ! case 325: #line 1522 "c-parse.y" ! { tree decl = current_function_decl; DECL_SOURCE_FILE (decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (decl) = yyvsp[-1].lineno; finish_function (1, 1); pop_function_context (); ! add_decl_stmt (decl); ; ! break;} ! case 328: #line 1542 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ; ! break;} ! case 329: #line 1544 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 330: #line 1549 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ; ! break;} ! case 331: #line 1551 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 335: #line 1566 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 336: #line 1571 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ; ! break;} ! case 338: #line 1577 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 339: #line 1582 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ; ! break;} ! case 340: #line 1584 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 341: #line 1586 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 342: #line 1588 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ; ! break;} ! case 343: #line 1596 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 344: #line 1601 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ; ! break;} ! case 345: #line 1603 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 346: #line 1605 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ; ! break;} ! case 348: #line 1611 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 349: #line 1613 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 350: #line 1618 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 351: #line 1620 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 352: #line 1625 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 353: #line 1627 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 354: #line 1638 "c-parse.y" ! { yyval.ttype = start_struct (RECORD_TYPE, yyvsp[-1].ttype); /* Start scope of tag before parsing components. */ ! ; ! break;} ! case 355: #line 1642 "c-parse.y" ! { yyval.ttype = finish_struct (yyvsp[-3].ttype, yyvsp[-2].ttype, chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ; ! break;} ! case 356: #line 1644 "c-parse.y" ! { yyval.ttype = finish_struct (start_struct (RECORD_TYPE, NULL_TREE), yyvsp[-2].ttype, chainon (yyvsp[-4].ttype, yyvsp[0].ttype)); ! ; ! break;} ! case 357: #line 1648 "c-parse.y" ! { yyval.ttype = start_struct (UNION_TYPE, yyvsp[-1].ttype); ; ! break;} ! case 358: #line 1650 "c-parse.y" ! { yyval.ttype = finish_struct (yyvsp[-3].ttype, yyvsp[-2].ttype, chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ; ! break;} ! case 359: #line 1652 "c-parse.y" ! { yyval.ttype = finish_struct (start_struct (UNION_TYPE, NULL_TREE), yyvsp[-2].ttype, chainon (yyvsp[-4].ttype, yyvsp[0].ttype)); ! ; ! break;} ! case 360: #line 1656 "c-parse.y" ! { yyval.ttype = start_enum (yyvsp[-1].ttype); ; ! break;} ! case 361: #line 1658 "c-parse.y" ! { yyval.ttype = finish_enum (yyvsp[-4].ttype, nreverse (yyvsp[-3].ttype), ! chainon (yyvsp[-7].ttype, yyvsp[0].ttype)); ; ! break;} ! case 362: #line 1661 "c-parse.y" ! { yyval.ttype = start_enum (NULL_TREE); ; ! break;} ! case 363: #line 1663 "c-parse.y" ! { yyval.ttype = finish_enum (yyvsp[-4].ttype, nreverse (yyvsp[-3].ttype), ! chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ; ! break;} ! case 364: #line 1669 "c-parse.y" ! { yyval.ttype = xref_tag (RECORD_TYPE, yyvsp[0].ttype); ; ! break;} ! case 365: #line 1671 "c-parse.y" ! { yyval.ttype = xref_tag (UNION_TYPE, yyvsp[0].ttype); ; ! break;} ! case 366: #line 1673 "c-parse.y" ! { yyval.ttype = xref_tag (ENUMERAL_TYPE, yyvsp[0].ttype); /* In ISO C, enumerated types can be referred to only if already defined. */ if (pedantic && !COMPLETE_TYPE_P (yyval.ttype)) ! pedwarn ("ISO C forbids forward references to `enum' types"); ; ! break;} ! case 370: #line 1688 "c-parse.y" ! { if (pedantic && ! flag_isoc99) ! pedwarn ("comma at end of enumerator list"); ; ! break;} ! case 371: #line 1694 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 372: #line 1696 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); ! pedwarn ("no semicolon at end of struct or union"); ; ! break;} ! case 373: #line 1701 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 374: #line 1703 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[-1].ttype); ; ! break;} ! case 375: #line 1705 "c-parse.y" ! { if (pedantic) ! pedwarn ("extra semicolon in struct or union specified"); ; ! break;} ! case 376: #line 1711 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 377: #line 1714 "c-parse.y" ! { /* Support for unnamed structs or unions as members of structs or unions (which is [a] useful and [b] supports MS P-SDK). */ --- 4063,4310 ---- pop_function_context (); YYERROR1; } ! ;} ! break; ! ! case 325: #line 1514 "c-parse.y" ! { store_parm_decls (); ;} ! break; ! ! case 326: #line 1522 "c-parse.y" ! { tree decl = current_function_decl; DECL_SOURCE_FILE (decl) = yyvsp[-2].filename; DECL_SOURCE_LINE (decl) = yyvsp[-1].lineno; finish_function (1, 1); pop_function_context (); ! add_decl_stmt (decl); ;} ! break; ! ! case 329: #line 1542 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ;} ! break; ! ! case 330: #line 1544 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 331: #line 1549 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 332: #line 1551 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 336: #line 1566 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 337: #line 1571 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 339: #line 1577 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 340: #line 1582 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 341: #line 1584 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 342: #line 1586 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 343: #line 1588 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ;} ! break; ! ! case 344: #line 1596 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 345: #line 1601 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ;} ! break; ! ! case 346: #line 1603 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 347: #line 1605 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 0); ;} ! break; ! ! case 349: #line 1611 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 350: #line 1613 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 351: #line 1618 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 352: #line 1620 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 353: #line 1625 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 354: #line 1627 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 355: #line 1638 "c-parse.y" ! { yyval.ttype = start_struct (RECORD_TYPE, yyvsp[-1].ttype); /* Start scope of tag before parsing components. */ ! ;} ! break; ! ! case 356: #line 1642 "c-parse.y" ! { yyval.ttype = finish_struct (yyvsp[-3].ttype, yyvsp[-2].ttype, chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ;} ! break; ! ! case 357: #line 1644 "c-parse.y" ! { yyval.ttype = finish_struct (start_struct (RECORD_TYPE, NULL_TREE), yyvsp[-2].ttype, chainon (yyvsp[-4].ttype, yyvsp[0].ttype)); ! ;} ! break; ! ! case 358: #line 1648 "c-parse.y" ! { yyval.ttype = start_struct (UNION_TYPE, yyvsp[-1].ttype); ;} ! break; ! ! case 359: #line 1650 "c-parse.y" ! { yyval.ttype = finish_struct (yyvsp[-3].ttype, yyvsp[-2].ttype, chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ;} ! break; ! ! case 360: #line 1652 "c-parse.y" ! { yyval.ttype = finish_struct (start_struct (UNION_TYPE, NULL_TREE), yyvsp[-2].ttype, chainon (yyvsp[-4].ttype, yyvsp[0].ttype)); ! ;} ! break; ! ! case 361: #line 1656 "c-parse.y" ! { yyval.ttype = start_enum (yyvsp[-1].ttype); ;} ! break; ! ! case 362: #line 1658 "c-parse.y" ! { yyval.ttype = finish_enum (yyvsp[-4].ttype, nreverse (yyvsp[-3].ttype), ! chainon (yyvsp[-7].ttype, yyvsp[0].ttype)); ;} ! break; ! ! case 363: #line 1661 "c-parse.y" ! { yyval.ttype = start_enum (NULL_TREE); ;} ! break; ! ! case 364: #line 1663 "c-parse.y" ! { yyval.ttype = finish_enum (yyvsp[-4].ttype, nreverse (yyvsp[-3].ttype), ! chainon (yyvsp[-6].ttype, yyvsp[0].ttype)); ;} ! break; ! ! case 365: #line 1669 "c-parse.y" ! { yyval.ttype = xref_tag (RECORD_TYPE, yyvsp[0].ttype); ;} ! break; ! ! case 366: #line 1671 "c-parse.y" ! { yyval.ttype = xref_tag (UNION_TYPE, yyvsp[0].ttype); ;} ! break; ! ! case 367: #line 1673 "c-parse.y" ! { yyval.ttype = xref_tag (ENUMERAL_TYPE, yyvsp[0].ttype); /* In ISO C, enumerated types can be referred to only if already defined. */ if (pedantic && !COMPLETE_TYPE_P (yyval.ttype)) ! pedwarn ("ISO C forbids forward references to `enum' types"); ;} ! break; ! ! case 371: #line 1688 "c-parse.y" ! { if (pedantic && ! flag_isoc99) ! pedwarn ("comma at end of enumerator list"); ;} ! break; ! ! case 372: #line 1694 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 373: #line 1696 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-1].ttype, yyvsp[0].ttype); ! pedwarn ("no semicolon at end of struct or union"); ;} ! break; ! ! case 374: #line 1701 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 375: #line 1703 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[-1].ttype); ;} ! break; ! ! case 376: #line 1705 "c-parse.y" ! { if (pedantic) ! pedwarn ("extra semicolon in struct or union specified"); ;} ! break; ! ! case 377: #line 1711 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 378: #line 1714 "c-parse.y" ! { /* Support for unnamed structs or unions as members of structs or unions (which is [a] useful and [b] supports MS P-SDK). */ *************** case 377: *** 3799,4014 **** pedwarn ("ISO C doesn't support unnamed structs/unions"); yyval.ttype = grokfield(yyvsp[-1].filename, yyvsp[0].lineno, NULL, current_declspecs, NULL_TREE); ! POP_DECLSPEC_STACK; ; ! break;} ! case 378: #line 1724 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 379: #line 1727 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids member declarations with no members"); shadow_tag(yyvsp[0].ttype); ! yyval.ttype = NULL_TREE; ; ! break;} ! case 380: #line 1732 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 381: #line 1734 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ; ! break;} ! case 383: #line 1741 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 385: #line 1747 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-3].ttype, yyvsp[0].ttype); ; ! break;} ! case 386: #line 1752 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-1].ttype, current_declspecs, NULL_TREE); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 387: #line 1756 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-5].filename, yyvsp[-4].lineno, yyvsp[-3].ttype, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 388: #line 1759 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-4].filename, yyvsp[-3].lineno, NULL_TREE, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 389: #line 1765 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-1].ttype, current_declspecs, NULL_TREE); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 390: #line 1769 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-5].filename, yyvsp[-4].lineno, yyvsp[-3].ttype, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 391: #line 1772 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-4].filename, yyvsp[-3].lineno, NULL_TREE, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ; ! break;} ! case 393: #line 1784 "c-parse.y" ! { if (yyvsp[-2].ttype == error_mark_node) yyval.ttype = yyvsp[-2].ttype; else ! yyval.ttype = chainon (yyvsp[0].ttype, yyvsp[-2].ttype); ; ! break;} ! case 394: #line 1789 "c-parse.y" ! { yyval.ttype = error_mark_node; ; ! break;} ! case 395: #line 1795 "c-parse.y" ! { yyval.ttype = build_enumerator (yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 396: #line 1797 "c-parse.y" ! { yyval.ttype = build_enumerator (yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 397: #line 1802 "c-parse.y" ! { pending_xref_error (); ! yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 398: #line 1805 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 399: #line 1810 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 401: #line 1816 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, NULL_TREE), ! all_prefix_attributes); ; ! break;} ! case 402: #line 1820 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[0].ttype), ! all_prefix_attributes); ; ! break;} ! case 403: #line 1824 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), ! chainon (yyvsp[0].ttype, all_prefix_attributes)); ; ! break;} ! case 407: #line 1837 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 408: #line 1842 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 409: #line 1844 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ; ! break;} ! case 410: #line 1849 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ; ! break;} ! case 411: #line 1851 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 412: #line 1853 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 1); ; ! break;} ! case 413: #line 1855 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, NULL_TREE, yyvsp[0].ttype, NULL_TREE); ; ! break;} ! case 414: #line 1857 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, NULL_TREE, 1); ; ! break;} ! case 415: #line 1864 "c-parse.y" ! { yyval.ttype = build_array_declarator (yyvsp[-1].ttype, NULL_TREE, 0, 0); ; ! break;} ! case 416: #line 1866 "c-parse.y" ! { yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-2].ttype, 0, 0); ; ! break;} ! case 417: #line 1868 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, NULL_TREE, 0, 0); ; ! break;} ! case 418: #line 1870 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, yyvsp[-1].ttype, 0, 0); ; ! break;} ! case 419: #line 1872 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, NULL_TREE, 0, 1); ; ! break;} ! case 420: #line 1874 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, yyvsp[-2].ttype, 0, 1); ; ! break;} ! case 421: #line 1876 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-2].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, NULL_TREE, 1, 0); ; ! break;} ! case 422: #line 1880 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-3].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-2].ttype, 1, 0); ; ! break;} ! case 423: #line 1884 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-2].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-3].ttype, 1, 0); ; ! break;} ! case 426: #line 1899 "c-parse.y" ! { pedwarn ("deprecated use of label at end of compound statement"); ! ; ! break;} ! case 434: #line 1916 "c-parse.y" ! { if (pedantic && !flag_isoc99) ! pedwarn ("ISO C89 forbids mixed declarations and code"); ; ! break;} ! case 449: #line 1946 "c-parse.y" ! { pushlevel (0); clear_last_expr (); add_scope_stmt (/*begin_p=*/1, /*partial_p=*/0); ! ; ! break;} ! case 450: #line 1953 "c-parse.y" ! { yyval.ttype = add_scope_stmt (/*begin_p=*/0, /*partial_p=*/0); ; ! break;} ! case 451: #line 1958 "c-parse.y" ! { if (flag_isoc99) { yyval.ttype = c_begin_compound_stmt (); pushlevel (0); --- 4312,4571 ---- pedwarn ("ISO C doesn't support unnamed structs/unions"); yyval.ttype = grokfield(yyvsp[-1].filename, yyvsp[0].lineno, NULL, current_declspecs, NULL_TREE); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 379: #line 1724 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 380: #line 1727 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids member declarations with no members"); shadow_tag(yyvsp[0].ttype); ! yyval.ttype = NULL_TREE; ;} ! break; ! ! case 381: #line 1732 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 382: #line 1734 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! RESTORE_WARN_FLAGS (yyvsp[-1].ttype); ;} ! break; ! ! case 384: #line 1741 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 386: #line 1747 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-3].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 387: #line 1752 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-1].ttype, current_declspecs, NULL_TREE); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 388: #line 1756 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-5].filename, yyvsp[-4].lineno, yyvsp[-3].ttype, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 389: #line 1759 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-4].filename, yyvsp[-3].lineno, NULL_TREE, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 390: #line 1765 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-1].ttype, current_declspecs, NULL_TREE); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 391: #line 1769 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-5].filename, yyvsp[-4].lineno, yyvsp[-3].ttype, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 392: #line 1772 "c-parse.y" ! { yyval.ttype = grokfield (yyvsp[-4].filename, yyvsp[-3].lineno, NULL_TREE, current_declspecs, yyvsp[-1].ttype); ! decl_attributes (&yyval.ttype, chainon (yyvsp[0].ttype, all_prefix_attributes), 0); ;} ! break; ! ! case 394: #line 1784 "c-parse.y" ! { if (yyvsp[-2].ttype == error_mark_node) yyval.ttype = yyvsp[-2].ttype; else ! yyval.ttype = chainon (yyvsp[0].ttype, yyvsp[-2].ttype); ;} ! break; ! ! case 395: #line 1789 "c-parse.y" ! { yyval.ttype = error_mark_node; ;} ! break; ! ! case 396: #line 1795 "c-parse.y" ! { yyval.ttype = build_enumerator (yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 397: #line 1797 "c-parse.y" ! { yyval.ttype = build_enumerator (yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 398: #line 1802 "c-parse.y" ! { pending_xref_error (); ! yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 399: #line 1805 "c-parse.y" ! { yyval.ttype = build_tree_list (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 400: #line 1810 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 402: #line 1816 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, NULL_TREE), ! all_prefix_attributes); ;} ! break; ! ! case 403: #line 1820 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[0].ttype), ! all_prefix_attributes); ;} ! break; ! ! case 404: #line 1824 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), ! chainon (yyvsp[0].ttype, all_prefix_attributes)); ;} ! break; ! ! case 408: #line 1837 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 409: #line 1842 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 410: #line 1844 "c-parse.y" ! { yyval.ttype = make_pointer_declarator (yyvsp[-1].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 411: #line 1849 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype ? tree_cons (yyvsp[-2].ttype, yyvsp[-1].ttype, NULL_TREE) : yyvsp[-1].ttype; ;} ! break; ! ! case 412: #line 1851 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, yyvsp[-2].ttype, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 413: #line 1853 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, yyvsp[-1].ttype, 1); ;} ! break; ! ! case 414: #line 1855 "c-parse.y" ! { yyval.ttype = build_nt (CALL_EXPR, NULL_TREE, yyvsp[0].ttype, NULL_TREE); ;} ! break; ! ! case 415: #line 1857 "c-parse.y" ! { yyval.ttype = set_array_declarator_type (yyvsp[0].ttype, NULL_TREE, 1); ;} ! break; ! ! case 416: #line 1864 "c-parse.y" ! { yyval.ttype = build_array_declarator (yyvsp[-1].ttype, NULL_TREE, 0, 0); ;} ! break; ! ! case 417: #line 1866 "c-parse.y" ! { yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-2].ttype, 0, 0); ;} ! break; ! ! case 418: #line 1868 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, NULL_TREE, 0, 0); ;} ! break; ! ! case 419: #line 1870 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, yyvsp[-1].ttype, 0, 0); ;} ! break; ! ! case 420: #line 1872 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, NULL_TREE, 0, 1); ;} ! break; ! ! case 421: #line 1874 "c-parse.y" ! { yyval.ttype = build_array_declarator (NULL_TREE, yyvsp[-2].ttype, 0, 1); ;} ! break; ! ! case 422: #line 1876 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-2].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, NULL_TREE, 1, 0); ;} ! break; ! ! case 423: #line 1880 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-3].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-2].ttype, 1, 0); ;} ! break; ! ! case 424: #line 1884 "c-parse.y" ! { if (C_RID_CODE (yyvsp[-2].ttype) != RID_STATIC) error ("storage class specifier in array declarator"); ! yyval.ttype = build_array_declarator (yyvsp[-1].ttype, yyvsp[-3].ttype, 1, 0); ;} ! break; ! ! case 427: #line 1899 "c-parse.y" ! { pedwarn ("deprecated use of label at end of compound statement"); ! ;} ! break; ! ! case 435: #line 1916 "c-parse.y" ! { if (pedantic && !flag_isoc99) ! pedwarn ("ISO C89 forbids mixed declarations and code"); ;} ! break; ! ! case 450: #line 1946 "c-parse.y" ! { pushlevel (0); clear_last_expr (); add_scope_stmt (/*begin_p=*/1, /*partial_p=*/0); ! ;} ! break; ! ! case 451: #line 1953 "c-parse.y" ! { yyval.ttype = add_scope_stmt (/*begin_p=*/0, /*partial_p=*/0); ;} ! break; ! ! case 452: #line 1958 "c-parse.y" ! { if (flag_isoc99) { yyval.ttype = c_begin_compound_stmt (); pushlevel (0); *************** case 451: *** 4017,4027 **** } else yyval.ttype = NULL_TREE; ! ; ! break;} ! case 452: #line 1974 "c-parse.y" ! { if (flag_isoc99) { tree scope_stmt = add_scope_stmt (/*begin_p=*/0, /*partial_p=*/0); yyval.ttype = poplevel (kept_level_p (), 0, 0); --- 4574,4585 ---- } else yyval.ttype = NULL_TREE; ! ;} ! break; ! ! case 453: #line 1974 "c-parse.y" ! { if (flag_isoc99) { tree scope_stmt = add_scope_stmt (/*begin_p=*/0, /*partial_p=*/0); yyval.ttype = poplevel (kept_level_p (), 0, 0); *************** case 452: *** 4030,4076 **** = yyval.ttype; } else ! yyval.ttype = NULL_TREE; ; ! break;} ! case 454: #line 1991 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C forbids label declarations"); ; ! break;} ! case 457: #line 2002 "c-parse.y" ! { tree link; for (link = yyvsp[-1].ttype; link; link = TREE_CHAIN (link)) { tree label = shadow_label (TREE_VALUE (link)); C_DECLARED_LABEL_FLAG (label) = 1; add_decl_stmt (label); } ! ; ! break;} ! case 458: #line 2016 "c-parse.y" ! {; ! break;} ! case 460: #line 2020 "c-parse.y" ! { compstmt_count++; ! yyval.ttype = c_begin_compound_stmt (); ; ! break;} ! case 461: #line 2025 "c-parse.y" ! { yyval.ttype = convert (void_type_node, integer_zero_node); ; ! break;} ! case 462: #line 2027 "c-parse.y" ! { yyval.ttype = poplevel (kept_level_p (), 1, 0); SCOPE_STMT_BLOCK (TREE_PURPOSE (yyvsp[0].ttype)) = SCOPE_STMT_BLOCK (TREE_VALUE (yyvsp[0].ttype)) ! = yyval.ttype; ; ! break;} ! case 465: #line 2040 "c-parse.y" ! { if (current_function_decl == 0) { error ("braced-group within expression allowed only inside a function"); YYERROR; --- 4588,4641 ---- = yyval.ttype; } else ! yyval.ttype = NULL_TREE; ;} ! break; ! ! case 455: #line 1991 "c-parse.y" ! { if (pedantic) ! pedwarn ("ISO C forbids label declarations"); ;} ! break; ! ! case 458: #line 2002 "c-parse.y" ! { tree link; for (link = yyvsp[-1].ttype; link; link = TREE_CHAIN (link)) { tree label = shadow_label (TREE_VALUE (link)); C_DECLARED_LABEL_FLAG (label) = 1; add_decl_stmt (label); } ! ;} ! break; ! ! case 459: #line 2016 "c-parse.y" ! {;} ! break; ! ! case 461: #line 2020 "c-parse.y" ! { compstmt_count++; ! yyval.ttype = c_begin_compound_stmt (); ;} ! break; ! ! case 462: #line 2025 "c-parse.y" ! { yyval.ttype = convert (void_type_node, integer_zero_node); ;} ! break; ! ! case 463: #line 2027 "c-parse.y" ! { yyval.ttype = poplevel (kept_level_p (), 1, 0); SCOPE_STMT_BLOCK (TREE_PURPOSE (yyvsp[0].ttype)) = SCOPE_STMT_BLOCK (TREE_VALUE (yyvsp[0].ttype)) ! = yyval.ttype; ;} ! break; ! ! case 466: #line 2040 "c-parse.y" ! { if (current_function_decl == 0) { error ("braced-group within expression allowed only inside a function"); YYERROR; *************** case 465: *** 4083,4115 **** push_label_level (); compstmt_count++; yyval.ttype = add_stmt (build_stmt (COMPOUND_STMT, last_tree)); ! ; ! break;} ! case 466: #line 2057 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-1].ttype, COMPOUND_BODY (yyvsp[-1].ttype)); last_expr_type = NULL_TREE; ! yyval.ttype = yyvsp[-1].ttype; ; ! break;} ! case 467: #line 2065 "c-parse.y" ! { c_finish_then (); ; ! break;} ! case 469: #line 2082 "c-parse.y" ! { yyval.ttype = c_begin_if_stmt (); ; ! break;} ! case 470: #line 2084 "c-parse.y" ! { c_expand_start_cond (truthvalue_conversion (yyvsp[-1].ttype), compstmt_count,yyvsp[-3].ttype); yyval.itype = stmt_count; if_stmt_file = yyvsp[-7].filename; ! if_stmt_line = yyvsp[-6].lineno; ; ! break;} ! case 471: #line 2096 "c-parse.y" ! { stmt_count++; compstmt_count++; yyval.ttype = add_stmt (build_stmt (DO_STMT, NULL_TREE, --- 4648,4685 ---- push_label_level (); compstmt_count++; yyval.ttype = add_stmt (build_stmt (COMPOUND_STMT, last_tree)); ! ;} ! break; ! ! case 467: #line 2057 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-1].ttype, COMPOUND_BODY (yyvsp[-1].ttype)); last_expr_type = NULL_TREE; ! yyval.ttype = yyvsp[-1].ttype; ;} ! break; ! ! case 468: #line 2065 "c-parse.y" ! { c_finish_then (); ;} ! break; ! ! case 470: #line 2082 "c-parse.y" ! { yyval.ttype = c_begin_if_stmt (); ;} ! break; ! ! case 471: #line 2084 "c-parse.y" ! { c_expand_start_cond (truthvalue_conversion (yyvsp[-1].ttype), compstmt_count,yyvsp[-3].ttype); yyval.itype = stmt_count; if_stmt_file = yyvsp[-7].filename; ! if_stmt_line = yyvsp[-6].lineno; ;} ! break; ! ! case 472: #line 2096 "c-parse.y" ! { stmt_count++; compstmt_count++; yyval.ttype = add_stmt (build_stmt (DO_STMT, NULL_TREE, *************** case 471: *** 4118,4150 **** parsing the complete do-statement, set the condition now. Otherwise, we can get crashes at RTL-generation time. */ ! DO_COND (yyval.ttype) = error_mark_node; ; ! break;} ! case 472: #line 2107 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype; ! RECHAIN_STMTS (yyval.ttype, DO_BODY (yyval.ttype)); ; ! break;} ! case 473: #line 2115 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; ! yyval.filename = input_filename; ; ! break;} ! case 474: #line 2121 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; ! yyval.lineno = lineno; ; ! break;} ! case 477: #line 2134 "c-parse.y" ! { if (flag_isoc99) ! RECHAIN_STMTS (yyvsp[-2].ttype, COMPOUND_BODY (yyvsp[-2].ttype)); ; ! break;} ! case 478: #line 2140 "c-parse.y" ! { if (yyvsp[0].ttype) { STMT_LINENO (yyvsp[0].ttype) = yyvsp[-1].lineno; /* ??? We currently have no way of recording --- 4688,4725 ---- parsing the complete do-statement, set the condition now. Otherwise, we can get crashes at RTL-generation time. */ ! DO_COND (yyval.ttype) = error_mark_node; ;} ! break; ! ! case 473: #line 2107 "c-parse.y" ! { yyval.ttype = yyvsp[-2].ttype; ! RECHAIN_STMTS (yyval.ttype, DO_BODY (yyval.ttype)); ;} ! break; ! ! case 474: #line 2115 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; ! yyval.filename = input_filename; ;} ! break; ! ! case 475: #line 2121 "c-parse.y" ! { if (yychar == YYEMPTY) yychar = YYLEX; ! yyval.lineno = lineno; ;} ! break; ! ! case 478: #line 2134 "c-parse.y" ! { if (flag_isoc99) ! RECHAIN_STMTS (yyvsp[-2].ttype, COMPOUND_BODY (yyvsp[-2].ttype)); ;} ! break; ! ! case 479: #line 2140 "c-parse.y" ! { if (yyvsp[0].ttype) { STMT_LINENO (yyvsp[0].ttype) = yyvsp[-1].lineno; /* ??? We currently have no way of recording *************** case 478: *** 4153,4318 **** but I suspect that problems will occur when doing inlining at the tree level. */ } ! ; ! break;} ! case 479: #line 2154 "c-parse.y" ! { if (yyvsp[0].ttype) { STMT_LINENO (yyvsp[0].ttype) = yyvsp[-1].lineno; } ! ; ! break;} ! case 480: #line 2163 "c-parse.y" ! { c_expand_start_else (); ! yyvsp[-1].itype = stmt_count; ; ! break;} ! case 481: #line 2166 "c-parse.y" ! { c_finish_else (); c_expand_end_cond (); if (extra_warnings && stmt_count == yyvsp[-3].itype) ! warning ("empty body in an else-statement"); ; ! break;} ! case 482: #line 2171 "c-parse.y" ! { c_expand_end_cond (); /* This warning is here instead of in simple_if, because we do not want a warning if an empty if is followed by an else statement. Increment stmt_count so we don't give a second error if this is a nested `if'. */ if (extra_warnings && stmt_count++ == yyvsp[0].itype) warning_with_file_and_line (if_stmt_file, if_stmt_line, ! "empty body in an if-statement"); ; ! break;} ! case 483: #line 2183 "c-parse.y" ! { c_expand_end_cond (); ; ! break;} ! case 484: #line 2193 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_begin_while_stmt (); ; ! break;} ! case 485: #line 2196 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (yyvsp[-1].ttype); c_finish_while_stmt_cond (truthvalue_conversion (yyvsp[-1].ttype), yyvsp[-3].ttype); ! yyval.ttype = add_stmt (yyvsp[-3].ttype); ; ! break;} ! case 486: #line 2201 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-1].ttype, WHILE_BODY (yyvsp[-1].ttype)); ; ! break;} ! case 487: #line 2204 "c-parse.y" ! { DO_COND (yyvsp[-4].ttype) = truthvalue_conversion (yyvsp[-2].ttype); ; ! break;} ! case 488: #line 2206 "c-parse.y" ! { ; ! break;} ! case 489: #line 2208 "c-parse.y" ! { yyval.ttype = build_stmt (FOR_STMT, NULL_TREE, NULL_TREE, NULL_TREE, NULL_TREE); ! add_stmt (yyval.ttype); ; ! break;} ! case 490: #line 2212 "c-parse.y" ! { stmt_count++; ! RECHAIN_STMTS (yyvsp[-2].ttype, FOR_INIT_STMT (yyvsp[-2].ttype)); ; ! break;} ! case 491: #line 2215 "c-parse.y" ! { if (yyvsp[-1].ttype) ! FOR_COND (yyvsp[-5].ttype) = truthvalue_conversion (yyvsp[-1].ttype); ; ! break;} ! case 492: #line 2218 "c-parse.y" ! { FOR_EXPR (yyvsp[-8].ttype) = yyvsp[-1].ttype; ; ! break;} ! case 493: #line 2220 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-10].ttype, FOR_BODY (yyvsp[-10].ttype)); ; ! break;} ! case 494: #line 2222 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_start_case (yyvsp[-1].ttype); ; ! break;} ! case 495: #line 2225 "c-parse.y" ! { c_finish_case (); ; ! break;} ! case 496: #line 2230 "c-parse.y" ! { add_stmt (build_stmt (EXPR_STMT, yyvsp[-1].ttype)); ; ! break;} ! case 497: #line 2232 "c-parse.y" ! { check_for_loop_decls (); ; ! break;} ! case 498: #line 2238 "c-parse.y" ! { stmt_count++; yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 499: #line 2240 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_expr_stmt (yyvsp[-1].ttype); ; ! break;} ! case 500: #line 2243 "c-parse.y" ! { if (flag_isoc99) RECHAIN_STMTS (yyvsp[-2].ttype, COMPOUND_BODY (yyvsp[-2].ttype)); ! yyval.ttype = NULL_TREE; ; ! break;} ! case 501: #line 2247 "c-parse.y" ! { stmt_count++; ! yyval.ttype = add_stmt (build_break_stmt ()); ; ! break;} ! case 502: #line 2250 "c-parse.y" ! { stmt_count++; ! yyval.ttype = add_stmt (build_continue_stmt ()); ; ! break;} ! case 503: #line 2253 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_return (NULL_TREE); ; ! break;} ! case 504: #line 2256 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_return (yyvsp[-1].ttype); ; ! break;} ! case 505: #line 2259 "c-parse.y" ! { stmt_count++; ! yyval.ttype = simple_asm_stmt (yyvsp[-2].ttype); ; ! break;} ! case 506: #line 2263 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype, NULL_TREE, NULL_TREE); ; ! break;} ! case 507: #line 2268 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-8].ttype, yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype, NULL_TREE); ; ! break;} ! case 508: #line 2273 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-10].ttype, yyvsp[-8].ttype, yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype); ; ! break;} ! case 509: #line 2276 "c-parse.y" ! { tree decl; stmt_count++; decl = lookup_label (yyvsp[-1].ttype); if (decl != 0) --- 4728,4924 ---- but I suspect that problems will occur when doing inlining at the tree level. */ } ! ;} ! break; ! ! case 480: #line 2154 "c-parse.y" ! { if (yyvsp[0].ttype) { STMT_LINENO (yyvsp[0].ttype) = yyvsp[-1].lineno; } ! ;} ! break; ! ! case 481: #line 2163 "c-parse.y" ! { c_expand_start_else (); ! yyvsp[-1].itype = stmt_count; ;} ! break; ! ! case 482: #line 2166 "c-parse.y" ! { c_finish_else (); c_expand_end_cond (); if (extra_warnings && stmt_count == yyvsp[-3].itype) ! warning ("empty body in an else-statement"); ;} ! break; ! ! case 483: #line 2171 "c-parse.y" ! { c_expand_end_cond (); /* This warning is here instead of in simple_if, because we do not want a warning if an empty if is followed by an else statement. Increment stmt_count so we don't give a second error if this is a nested `if'. */ if (extra_warnings && stmt_count++ == yyvsp[0].itype) warning_with_file_and_line (if_stmt_file, if_stmt_line, ! "empty body in an if-statement"); ;} ! break; ! ! case 484: #line 2183 "c-parse.y" ! { c_expand_end_cond (); ;} ! break; ! ! case 485: #line 2193 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_begin_while_stmt (); ;} ! break; ! ! case 486: #line 2196 "c-parse.y" ! { yyvsp[-1].ttype = truthvalue_conversion (yyvsp[-1].ttype); c_finish_while_stmt_cond (truthvalue_conversion (yyvsp[-1].ttype), yyvsp[-3].ttype); ! yyval.ttype = add_stmt (yyvsp[-3].ttype); ;} ! break; ! ! case 487: #line 2201 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-1].ttype, WHILE_BODY (yyvsp[-1].ttype)); ;} ! break; ! ! case 488: #line 2204 "c-parse.y" ! { DO_COND (yyvsp[-4].ttype) = truthvalue_conversion (yyvsp[-2].ttype); ;} ! break; ! ! case 489: #line 2206 "c-parse.y" ! { ;} ! break; ! ! case 490: #line 2208 "c-parse.y" ! { yyval.ttype = build_stmt (FOR_STMT, NULL_TREE, NULL_TREE, NULL_TREE, NULL_TREE); ! add_stmt (yyval.ttype); ;} ! break; ! ! case 491: #line 2212 "c-parse.y" ! { stmt_count++; ! RECHAIN_STMTS (yyvsp[-2].ttype, FOR_INIT_STMT (yyvsp[-2].ttype)); ;} ! break; ! ! case 492: #line 2215 "c-parse.y" ! { if (yyvsp[-1].ttype) ! FOR_COND (yyvsp[-5].ttype) = truthvalue_conversion (yyvsp[-1].ttype); ;} ! break; ! ! case 493: #line 2218 "c-parse.y" ! { FOR_EXPR (yyvsp[-8].ttype) = yyvsp[-1].ttype; ;} ! break; ! ! case 494: #line 2220 "c-parse.y" ! { RECHAIN_STMTS (yyvsp[-10].ttype, FOR_BODY (yyvsp[-10].ttype)); ;} ! break; ! ! case 495: #line 2222 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_start_case (yyvsp[-1].ttype); ;} ! break; ! ! case 496: #line 2225 "c-parse.y" ! { c_finish_case (); ;} ! break; ! ! case 497: #line 2230 "c-parse.y" ! { add_stmt (build_stmt (EXPR_STMT, yyvsp[-1].ttype)); ;} ! break; ! ! case 498: #line 2232 "c-parse.y" ! { check_for_loop_decls (); ;} ! break; ! ! case 499: #line 2238 "c-parse.y" ! { stmt_count++; yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 500: #line 2240 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_expr_stmt (yyvsp[-1].ttype); ;} ! break; ! ! case 501: #line 2243 "c-parse.y" ! { if (flag_isoc99) RECHAIN_STMTS (yyvsp[-2].ttype, COMPOUND_BODY (yyvsp[-2].ttype)); ! yyval.ttype = NULL_TREE; ;} ! break; ! ! case 502: #line 2247 "c-parse.y" ! { stmt_count++; ! yyval.ttype = add_stmt (build_break_stmt ()); ;} ! break; ! ! case 503: #line 2250 "c-parse.y" ! { stmt_count++; ! yyval.ttype = add_stmt (build_continue_stmt ()); ;} ! break; ! ! case 504: #line 2253 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_return (NULL_TREE); ;} ! break; ! ! case 505: #line 2256 "c-parse.y" ! { stmt_count++; ! yyval.ttype = c_expand_return (yyvsp[-1].ttype); ;} ! break; ! ! case 506: #line 2259 "c-parse.y" ! { stmt_count++; ! yyval.ttype = simple_asm_stmt (yyvsp[-2].ttype); ;} ! break; ! ! case 507: #line 2263 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype, NULL_TREE, NULL_TREE); ;} ! break; ! ! case 508: #line 2268 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-8].ttype, yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype, NULL_TREE); ;} ! break; ! ! case 509: #line 2273 "c-parse.y" ! { stmt_count++; ! yyval.ttype = build_asm_stmt (yyvsp[-10].ttype, yyvsp[-8].ttype, yyvsp[-6].ttype, yyvsp[-4].ttype, yyvsp[-2].ttype); ;} ! break; ! ! case 510: #line 2276 "c-parse.y" ! { tree decl; stmt_count++; decl = lookup_label (yyvsp[-1].ttype); if (decl != 0) *************** case 509: *** 4322,4359 **** } else yyval.ttype = NULL_TREE; ! ; ! break;} ! case 510: #line 2288 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids `goto *expr;'"); stmt_count++; yyvsp[-1].ttype = convert (ptr_type_node, yyvsp[-1].ttype); ! yyval.ttype = add_stmt (build_stmt (GOTO_STMT, yyvsp[-1].ttype)); ; ! break;} ! case 511: #line 2294 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 512: #line 2302 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (yyvsp[-1].ttype, NULL_TREE); ; ! break;} ! case 513: #line 2305 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (yyvsp[-3].ttype, yyvsp[-1].ttype); ; ! break;} ! case 514: #line 2308 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (NULL_TREE, NULL_TREE); ; ! break;} ! case 515: #line 2311 "c-parse.y" ! { tree label = define_label (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-4].ttype); stmt_count++; if (label) { --- 4928,4971 ---- } else yyval.ttype = NULL_TREE; ! ;} ! break; ! ! case 511: #line 2288 "c-parse.y" ! { if (pedantic) pedwarn ("ISO C forbids `goto *expr;'"); stmt_count++; yyvsp[-1].ttype = convert (ptr_type_node, yyvsp[-1].ttype); ! yyval.ttype = add_stmt (build_stmt (GOTO_STMT, yyvsp[-1].ttype)); ;} ! break; ! ! case 512: #line 2294 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 513: #line 2302 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (yyvsp[-1].ttype, NULL_TREE); ;} ! break; ! ! case 514: #line 2305 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (yyvsp[-3].ttype, yyvsp[-1].ttype); ;} ! break; ! ! case 515: #line 2308 "c-parse.y" ! { stmt_count++; ! yyval.ttype = do_case (NULL_TREE, NULL_TREE); ;} ! break; ! ! case 516: #line 2311 "c-parse.y" ! { tree label = define_label (yyvsp[-3].filename, yyvsp[-2].lineno, yyvsp[-4].ttype); stmt_count++; if (label) { *************** case 515: *** 4362,4448 **** } else yyval.ttype = NULL_TREE; ! ; ! break;} ! case 516: #line 2327 "c-parse.y" ! { emit_line_note (input_filename, lineno); ! yyval.ttype = NULL_TREE; ; ! break;} ! case 517: #line 2330 "c-parse.y" ! { emit_line_note (input_filename, lineno); ; ! break;} ! case 518: #line 2335 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 520: #line 2342 "c-parse.y" ! { yyval.ttype = NULL_TREE; ; ! break;} ! case 523: #line 2349 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[0].ttype); ; ! break;} ! case 524: #line 2354 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (NULL_TREE, yyvsp[-3].ttype), yyvsp[-1].ttype); ; ! break;} ! case 525: #line 2356 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (yyvsp[-5].ttype, yyvsp[-3].ttype), yyvsp[-1].ttype); ; ! break;} ! case 526: #line 2361 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, combine_strings (yyvsp[0].ttype), NULL_TREE); ; ! break;} ! case 527: #line 2363 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, combine_strings (yyvsp[0].ttype), yyvsp[-2].ttype); ; ! break;} ! case 528: #line 2373 "c-parse.y" ! { pushlevel (0); clear_parm_order (); ! declare_parm_level (0); ; ! break;} ! case 529: #line 2377 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; parmlist_tags_warning (); ! poplevel (0, 0, 0); ; ! break;} ! case 531: #line 2385 "c-parse.y" ! { tree parm; if (pedantic) pedwarn ("ISO C forbids forward parameter declarations"); /* Mark the forward decls as such. */ for (parm = getdecls (); parm; parm = TREE_CHAIN (parm)) TREE_ASM_WRITTEN (parm) = 1; ! clear_parm_order (); ; ! break;} ! case 532: #line 2393 "c-parse.y" ! { /* Dummy action so attributes are in known place ! on parser stack. */ ; ! break;} ! case 533: #line 2396 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ; ! break;} ! case 534: #line 2398 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, NULL_TREE, NULL_TREE); ; ! break;} ! case 535: #line 2404 "c-parse.y" ! { yyval.ttype = get_parm_info (0); ; ! break;} ! case 536: #line 2406 "c-parse.y" ! { yyval.ttype = get_parm_info (0); /* Gcc used to allow this as an extension. However, it does not work for all targets, and thus has been disabled. Also, since func (...) and func () are indistinguishable, --- 4974,5077 ---- } else yyval.ttype = NULL_TREE; ! ;} ! break; ! ! case 517: #line 2327 "c-parse.y" ! { emit_line_note (input_filename, lineno); ! yyval.ttype = NULL_TREE; ;} ! break; ! ! case 518: #line 2330 "c-parse.y" ! { emit_line_note (input_filename, lineno); ;} ! break; ! ! case 519: #line 2335 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 521: #line 2342 "c-parse.y" ! { yyval.ttype = NULL_TREE; ;} ! break; ! ! case 524: #line 2349 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, yyvsp[0].ttype); ;} ! break; ! ! case 525: #line 2354 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (NULL_TREE, yyvsp[-3].ttype), yyvsp[-1].ttype); ;} ! break; ! ! case 526: #line 2356 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (yyvsp[-5].ttype, yyvsp[-3].ttype), yyvsp[-1].ttype); ;} ! break; ! ! case 527: #line 2361 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, combine_strings (yyvsp[0].ttype), NULL_TREE); ;} ! break; ! ! case 528: #line 2363 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, combine_strings (yyvsp[0].ttype), yyvsp[-2].ttype); ;} ! break; ! ! case 529: #line 2373 "c-parse.y" ! { pushlevel (0); clear_parm_order (); ! declare_parm_level (0); ;} ! break; ! ! case 530: #line 2377 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; parmlist_tags_warning (); ! poplevel (0, 0, 0); ;} ! break; ! ! case 532: #line 2385 "c-parse.y" ! { tree parm; if (pedantic) pedwarn ("ISO C forbids forward parameter declarations"); /* Mark the forward decls as such. */ for (parm = getdecls (); parm; parm = TREE_CHAIN (parm)) TREE_ASM_WRITTEN (parm) = 1; ! clear_parm_order (); ;} ! break; ! ! case 533: #line 2393 "c-parse.y" ! { /* Dummy action so attributes are in known place ! on parser stack. */ ;} ! break; ! ! case 534: #line 2396 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ;} ! break; ! ! case 535: #line 2398 "c-parse.y" ! { yyval.ttype = tree_cons (NULL_TREE, NULL_TREE, NULL_TREE); ;} ! break; ! ! case 536: #line 2404 "c-parse.y" ! { yyval.ttype = get_parm_info (0); ;} ! break; ! ! case 537: #line 2406 "c-parse.y" ! { yyval.ttype = get_parm_info (0); /* Gcc used to allow this as an extension. However, it does not work for all targets, and thus has been disabled. Also, since func (...) and func () are indistinguishable, *************** case 536: *** 4450,4555 **** tries to verify that BUILT_IN_NEXT_ARG is being used correctly. */ error ("ISO C requires a named argument before `...'"); ! ; ! break;} ! case 537: #line 2416 "c-parse.y" ! { yyval.ttype = get_parm_info (1); ; ! break;} ! case 538: #line 2418 "c-parse.y" ! { yyval.ttype = get_parm_info (0); ; ! break;} ! case 539: #line 2423 "c-parse.y" ! { push_parm_decl (yyvsp[0].ttype); ; ! break;} ! case 540: #line 2425 "c-parse.y" ! { push_parm_decl (yyvsp[0].ttype); ; ! break;} ! case 541: #line 2432 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 542: #line 2437 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 543: #line 2442 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 544: #line 2445 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 545: #line 2451 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 546: #line 2459 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 547: #line 2464 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 548: #line 2469 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 549: #line 2472 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ; ! break;} ! case 550: #line 2478 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ; ! break;} ! case 551: #line 2484 "c-parse.y" ! { prefix_attributes = chainon (prefix_attributes, yyvsp[-3].ttype); ! all_prefix_attributes = prefix_attributes; ; ! break;} ! case 552: #line 2493 "c-parse.y" ! { pushlevel (0); clear_parm_order (); ! declare_parm_level (1); ; ! break;} ! case 553: #line 2497 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; parmlist_tags_warning (); ! poplevel (0, 0, 0); ; ! break;} ! case 555: #line 2505 "c-parse.y" ! { tree t; for (t = yyvsp[-1].ttype; t; t = TREE_CHAIN (t)) if (TREE_VALUE (t) == NULL_TREE) error ("`...' in old-style identifier list"); --- 5079,5202 ---- tries to verify that BUILT_IN_NEXT_ARG is being used correctly. */ error ("ISO C requires a named argument before `...'"); ! ;} ! break; ! ! case 538: #line 2416 "c-parse.y" ! { yyval.ttype = get_parm_info (1); ;} ! break; ! ! case 539: #line 2418 "c-parse.y" ! { yyval.ttype = get_parm_info (0); ;} ! break; ! ! case 540: #line 2423 "c-parse.y" ! { push_parm_decl (yyvsp[0].ttype); ;} ! break; ! ! case 541: #line 2425 "c-parse.y" ! { push_parm_decl (yyvsp[0].ttype); ;} ! break; ! ! case 542: #line 2432 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 543: #line 2437 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 544: #line 2442 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 545: #line 2445 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 546: #line 2451 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 547: #line 2459 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 548: #line 2464 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 549: #line 2469 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 550: #line 2472 "c-parse.y" ! { yyval.ttype = build_tree_list (build_tree_list (current_declspecs, yyvsp[-1].ttype), chainon (yyvsp[0].ttype, all_prefix_attributes)); ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 551: #line 2478 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; ! POP_DECLSPEC_STACK; ;} ! break; ! ! case 552: #line 2484 "c-parse.y" ! { prefix_attributes = chainon (prefix_attributes, yyvsp[-3].ttype); ! all_prefix_attributes = prefix_attributes; ;} ! break; ! ! case 553: #line 2493 "c-parse.y" ! { pushlevel (0); clear_parm_order (); ! declare_parm_level (1); ;} ! break; ! ! case 554: #line 2497 "c-parse.y" ! { yyval.ttype = yyvsp[0].ttype; parmlist_tags_warning (); ! poplevel (0, 0, 0); ;} ! break; ! ! case 556: #line 2505 "c-parse.y" ! { tree t; for (t = yyvsp[-1].ttype; t; t = TREE_CHAIN (t)) if (TREE_VALUE (t) == NULL_TREE) error ("`...' in old-style identifier list"); *************** case 555: *** 4561,4617 **** || TREE_PURPOSE (yyval.ttype) == 0 || TREE_CODE (TREE_PURPOSE (yyval.ttype)) != PARM_DECL)) YYERROR1; ! ; ! break;} ! case 556: #line 2523 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ; ! break;} ! case 557: #line 2525 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ; ! break;} ! case 558: #line 2531 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ; ! break;} ! case 559: #line 2533 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ; ! break;} ! case 560: #line 2538 "c-parse.y" ! { yyval.ttype = SAVE_WARN_FLAGS(); pedantic = 0; warn_pointer_arith = 0; ! warn_traditional = 0; ; ! break;} ! } - #line 731 "/usr/share/bison/bison.simple" yyvsp -= yylen; yyssp -= yylen; - #if YYLSP_NEEDED - yylsp -= yylen; - #endif ! #if YYDEBUG ! if (yydebug) ! { ! short *yyssp1 = yyss - 1; ! YYFPRINTF (stderr, "state stack now"); ! while (yyssp1 != yyssp) ! YYFPRINTF (stderr, " %d", *++yyssp1); ! YYFPRINTF (stderr, "\n"); ! } ! #endif *++yyvsp = yyval; ! #if YYLSP_NEEDED ! *++yylsp = yyloc; ! #endif /* Now `shift' the result of the reduction. Determine what state that goes to, based on the state we popped back to and the rule --- 5208,5258 ---- || TREE_PURPOSE (yyval.ttype) == 0 || TREE_CODE (TREE_PURPOSE (yyval.ttype)) != PARM_DECL)) YYERROR1; ! ;} ! break; ! ! case 557: #line 2523 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ;} ! break; ! ! case 558: #line 2525 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ;} ! break; ! ! case 559: #line 2531 "c-parse.y" ! { yyval.ttype = build_tree_list (NULL_TREE, yyvsp[0].ttype); ;} ! break; ! ! case 560: #line 2533 "c-parse.y" ! { yyval.ttype = chainon (yyvsp[-2].ttype, build_tree_list (NULL_TREE, yyvsp[0].ttype)); ;} ! break; ! ! case 561: #line 2538 "c-parse.y" ! { yyval.ttype = SAVE_WARN_FLAGS(); pedantic = 0; warn_pointer_arith = 0; ! warn_traditional = 0; ;} ! break; + } + + /* Line 991 of yacc.c. */ + #line 5246 "c-p10602.c" yyvsp -= yylen; yyssp -= yylen; ! ! YY_STACK_PRINT (yyss, yyssp); *++yyvsp = yyval; ! /* Now `shift' the result of the reduction. Determine what state that goes to, based on the state we popped back to and the rule *************** case 560: *** 4619,4629 **** yyn = yyr1[yyn]; ! yystate = yypgoto[yyn - YYNTBASE] + *yyssp; ! if (yystate >= 0 && yystate <= YYLAST && yycheck[yystate] == *yyssp) yystate = yytable[yystate]; else ! yystate = yydefgoto[yyn - YYNTBASE]; goto yynewstate; --- 5260,5270 ---- yyn = yyr1[yyn]; ! yystate = yypgoto[yyn - YYNTOKENS] + *yyssp; ! if (0 <= yystate && yystate <= YYLAST && yycheck[yystate] == *yyssp) yystate = yytable[yystate]; else ! yystate = yydefgoto[yyn - YYNTOKENS]; goto yynewstate; *************** yyerrlab: *** 4636,4648 **** if (!yyerrstatus) { ++yynerrs; ! ! #ifdef YYERROR_VERBOSE yyn = yypact[yystate]; ! if (yyn > YYFLAG && yyn < YYLAST) { YYSIZE_T yysize = 0; char *yymsg; int yyx, yycount; --- 5277,5289 ---- if (!yyerrstatus) { ++yynerrs; ! #if YYERROR_VERBOSE yyn = yypact[yystate]; ! if (YYPACT_NINF < yyn && yyn < YYLAST) { YYSIZE_T yysize = 0; + int yytype = YYTRANSLATE (yychar); char *yymsg; int yyx, yycount; *************** yyerrlab: *** 4651,4665 **** YYCHECK. */ for (yyx = yyn < 0 ? -yyn : 0; yyx < (int) (sizeof (yytname) / sizeof (char *)); yyx++) ! if (yycheck[yyx + yyn] == yyx) yysize += yystrlen (yytname[yyx]) + 15, yycount++; ! yysize += yystrlen ("parse error, unexpected ") + 1; ! yysize += yystrlen (yytname[YYTRANSLATE (yychar)]); yymsg = (char *) YYSTACK_ALLOC (yysize); if (yymsg != 0) { ! char *yyp = yystpcpy (yymsg, "parse error, unexpected "); ! yyp = yystpcpy (yyp, yytname[YYTRANSLATE (yychar)]); if (yycount < 5) { --- 5292,5306 ---- YYCHECK. */ for (yyx = yyn < 0 ? -yyn : 0; yyx < (int) (sizeof (yytname) / sizeof (char *)); yyx++) ! if (yycheck[yyx + yyn] == yyx && yyx != YYTERROR) yysize += yystrlen (yytname[yyx]) + 15, yycount++; ! yysize += yystrlen ("syntax error, unexpected ") + 1; ! yysize += yystrlen (yytname[yytype]); yymsg = (char *) YYSTACK_ALLOC (yysize); if (yymsg != 0) { ! char *yyp = yystpcpy (yymsg, "syntax error, unexpected "); ! yyp = yystpcpy (yyp, yytname[yytype]); if (yycount < 5) { *************** yyerrlab: *** 4667,4673 **** for (yyx = yyn < 0 ? -yyn : 0; yyx < (int) (sizeof (yytname) / sizeof (char *)); yyx++) ! if (yycheck[yyx + yyn] == yyx) { const char *yyq = ! yycount ? ", expecting " : " or "; yyp = yystpcpy (yyp, yyq); --- 5308,5314 ---- for (yyx = yyn < 0 ? -yyn : 0; yyx < (int) (sizeof (yytname) / sizeof (char *)); yyx++) ! if (yycheck[yyx + yyn] == yyx && yyx != YYTERROR) { const char *yyq = ! yycount ? ", expecting " : " or "; yyp = yystpcpy (yyp, yyq); *************** yyerrlab: *** 4679,4780 **** YYSTACK_FREE (yymsg); } else ! yyerror ("parse error; also virtual memory exhausted"); } else ! #endif /* defined (YYERROR_VERBOSE) */ ! yyerror ("parse error"); } - goto yyerrlab1; ! /*--------------------------------------------------. ! | yyerrlab1 -- error raised explicitly by an action | ! `--------------------------------------------------*/ ! yyerrlab1: if (yyerrstatus == 3) { /* If just tried and failed to reuse lookahead token after an error, discard it. */ ! /* return failure if at end of input */ if (yychar == YYEOF) ! YYABORT; ! YYDPRINTF ((stderr, "Discarding token %d (%s).\n", ! yychar, yytname[yychar1])); yychar = YYEMPTY; } /* Else will try to reuse lookahead token after shifting the error token. */ - yyerrstatus = 3; /* Each real token shifted decrements this */ ! goto yyerrhandle; - /*-------------------------------------------------------------------. - | yyerrdefault -- current state does not do anything special for the | - | error token. | - `-------------------------------------------------------------------*/ - yyerrdefault: - #if 0 - /* This is wrong; only states that explicitly want error tokens - should shift them. */ ! /* If its default is to accept any token, ok. Otherwise pop it. */ ! yyn = yydefact[yystate]; ! if (yyn) ! goto yydefault; ! #endif /*---------------------------------------------------------------. ! | yyerrpop -- pop the current state because it cannot handle the | ! | error token | `---------------------------------------------------------------*/ ! yyerrpop: ! if (yyssp == yyss) ! YYABORT; ! yyvsp--; ! yystate = *--yyssp; ! #if YYLSP_NEEDED ! yylsp--; ! #endif ! #if YYDEBUG ! if (yydebug) { ! short *yyssp1 = yyss - 1; ! YYFPRINTF (stderr, "Error: state stack now"); ! while (yyssp1 != yyssp) ! YYFPRINTF (stderr, " %d", *++yyssp1); ! YYFPRINTF (stderr, "\n"); ! } ! #endif ! /*--------------. ! | yyerrhandle. | ! `--------------*/ ! yyerrhandle: ! yyn = yypact[yystate]; ! if (yyn == YYFLAG) ! goto yyerrdefault; ! yyn += YYTERROR; ! if (yyn < 0 || yyn > YYLAST || yycheck[yyn] != YYTERROR) ! goto yyerrdefault; ! yyn = yytable[yyn]; ! if (yyn < 0) ! { ! if (yyn == YYFLAG) ! goto yyerrpop; ! yyn = -yyn; ! goto yyreduce; } - else if (yyn == 0) - goto yyerrpop; if (yyn == YYFINAL) YYACCEPT; --- 5320,5411 ---- YYSTACK_FREE (yymsg); } else ! yyerror ("syntax error; also virtual memory exhausted"); } else ! #endif /* YYERROR_VERBOSE */ ! yyerror ("syntax error"); } ! if (yyerrstatus == 3) { /* If just tried and failed to reuse lookahead token after an error, discard it. */ ! /* Return failure if at end of input. */ if (yychar == YYEOF) ! { ! /* Pop the error token. */ ! YYPOPSTACK; ! /* Pop the rest of the stack. */ ! while (yyss < yyssp) ! { ! YYDSYMPRINTF ("Error: popping", yystos[*yyssp], yyvsp, yylsp); ! yydestruct (yystos[*yyssp], yyvsp); ! YYPOPSTACK; ! } ! YYABORT; ! } ! ! YYDSYMPRINTF ("Error: discarding", yytoken, &yylval, &yylloc); ! yydestruct (yytoken, &yylval); yychar = YYEMPTY; + } /* Else will try to reuse lookahead token after shifting the error token. */ + goto yyerrlab2; ! /*----------------------------------------------------. ! | yyerrlab1 -- error raised explicitly by an action. | ! `----------------------------------------------------*/ ! yyerrlab1: + /* Suppress GCC warning that yyerrlab1 is unused when no action + invokes YYERROR. */ + #if defined (__GNUC_MINOR__) && 2093 <= (__GNUC__ * 1000 + __GNUC_MINOR__) + __attribute__ ((__unused__)); + #endif ! goto yyerrlab2; /*---------------------------------------------------------------. ! | yyerrlab2 -- pop states until the error token can be shifted. | `---------------------------------------------------------------*/ ! yyerrlab2: ! yyerrstatus = 3; /* Each real token shifted decrements this. */ ! for (;;) { ! yyn = yypact[yystate]; ! if (yyn != YYPACT_NINF) ! { ! yyn += YYTERROR; ! if (0 <= yyn && yyn <= YYLAST && yycheck[yyn] == YYTERROR) ! { ! yyn = yytable[yyn]; ! if (0 < yyn) ! break; ! } ! } ! /* Pop the current state because it cannot handle the error token. */ ! if (yyssp == yyss) ! YYABORT; ! YYDSYMPRINTF ("Error: popping", yystos[*yyssp], yyvsp, yylsp); ! yydestruct (yystos[yystate], yyvsp); ! yyvsp--; ! yystate = *--yyssp; ! YY_STACK_PRINT (yyss, yyssp); } if (yyn == YYFINAL) YYACCEPT; *************** yyerrhandle: *** 4782,4790 **** YYDPRINTF ((stderr, "Shifting error token, ")); *++yyvsp = yylval; ! #if YYLSP_NEEDED ! *++yylsp = yylloc; ! #endif yystate = yyn; goto yynewstate; --- 5413,5419 ---- YYDPRINTF ((stderr, "Shifting error token, ")); *++yyvsp = yylval; ! yystate = yyn; goto yynewstate; *************** yyabortlab: *** 4804,4816 **** yyresult = 1; goto yyreturn; ! /*---------------------------------------------. ! | yyoverflowab -- parser overflow comes here. | ! `---------------------------------------------*/ yyoverflowlab: yyerror ("parser stack overflow"); yyresult = 2; /* Fall through. */ yyreturn: #ifndef yyoverflow --- 5433,5447 ---- yyresult = 1; goto yyreturn; ! #ifndef yyoverflow ! /*----------------------------------------------. ! | yyoverflowlab -- parser overflow comes here. | ! `----------------------------------------------*/ yyoverflowlab: yyerror ("parser stack overflow"); yyresult = 2; /* Fall through. */ + #endif yyreturn: #ifndef yyoverflow *************** yyreturn: *** 4819,4824 **** --- 5450,5457 ---- #endif return yyresult; } + + #line 2544 "c-parse.y" *************** make_pointer_declarator (type_quals_attr *** 5369,5371 **** --- 6002,6006 ---- itarget = tree_cons (attrs, target, NULL_TREE); return build1 (INDIRECT_REF, quals, itarget); } + + diff -Nrc3pad gcc-3.2.2/gcc/c-typeck.c gcc-3.2.3/gcc/c-typeck.c *** gcc-3.2.2/gcc/c-typeck.c Thu Jan 9 13:18:41 2003 --- gcc-3.2.3/gcc/c-typeck.c Wed Mar 5 09:00:37 2003 *************** push_init_level (implicit) *** 5292,5297 **** --- 5292,5298 ---- && constructor_fields == 0) process_init_element (pop_init_level (1)); else if (TREE_CODE (constructor_type) == ARRAY_TYPE + && constructor_max_index && tree_int_cst_lt (constructor_max_index, constructor_index)) process_init_element (pop_init_level (1)); else diff -Nrc3pad gcc-3.2.2/gcc/cfgcleanup.c gcc-3.2.3/gcc/cfgcleanup.c *** gcc-3.2.2/gcc/cfgcleanup.c Mon Feb 3 18:01:32 2003 --- gcc-3.2.3/gcc/cfgcleanup.c Sun Mar 23 20:41:22 2003 *************** outgoing_edges_match (mode, bb1, bb2) *** 1078,1086 **** /* If BB1 has only one successor, we may be looking at either an unconditional jump, or a fake edge to exit. */ if (bb1->succ && !bb1->succ->succ_next ! && !(bb1->succ->flags & (EDGE_COMPLEX | EDGE_FAKE))) return (bb2->succ && !bb2->succ->succ_next ! && (bb2->succ->flags & (EDGE_COMPLEX | EDGE_FAKE)) == 0); /* Match conditional jumps - this may get tricky when fallthru and branch edges are crossed. */ --- 1078,1088 ---- /* If BB1 has only one successor, we may be looking at either an unconditional jump, or a fake edge to exit. */ if (bb1->succ && !bb1->succ->succ_next ! && (bb1->succ->flags & (EDGE_COMPLEX | EDGE_FAKE)) == 0 ! && (GET_CODE (bb1->end) != JUMP_INSN || simplejump_p (bb1->end))) return (bb2->succ && !bb2->succ->succ_next ! && (bb2->succ->flags & (EDGE_COMPLEX | EDGE_FAKE)) == 0 ! && (GET_CODE (bb2->end) != JUMP_INSN || simplejump_p (bb2->end))); /* Match conditional jumps - this may get tricky when fallthru and branch edges are crossed. */ *************** try_optimize_cfg (mode) *** 1638,1645 **** /* If the jump insn has side effects, we can't kill the edge. */ && (GET_CODE (b->end) != JUMP_INSN ! || (onlyjump_p (b->end) ! && !tablejump_p (b->end))) && merge_blocks (s, b, c, mode)) changed_here = true; --- 1640,1648 ---- /* If the jump insn has side effects, we can't kill the edge. */ && (GET_CODE (b->end) != JUMP_INSN ! || (flow2_completed ! ? simplejump_p (b->end) ! : onlyjump_p (b->end))) && merge_blocks (s, b, c, mode)) changed_here = true; diff -Nrc3pad gcc-3.2.2/gcc/cfgrtl.c gcc-3.2.3/gcc/cfgrtl.c *** gcc-3.2.2/gcc/cfgrtl.c Mon Nov 11 03:35:59 2002 --- gcc-3.2.3/gcc/cfgrtl.c Thu Mar 27 22:25:48 2003 *************** try_redirect_by_replacing_jump (e, targe *** 665,671 **** edge tmp; rtx set; int fallthru = 0; - rtx table; /* Verify that all targets will be TARGET. */ for (tmp = src->succ; tmp; tmp = tmp->succ_next) --- 665,670 ---- *************** try_redirect_by_replacing_jump (e, targe *** 675,685 **** if (tmp || !onlyjump_p (insn)) return false; ! if (reload_completed && JUMP_LABEL (insn) ! && (table = NEXT_INSN (JUMP_LABEL (insn))) != NULL_RTX ! && GET_CODE (table) == JUMP_INSN ! && (GET_CODE (PATTERN (table)) == ADDR_VEC ! || GET_CODE (PATTERN (table)) == ADDR_DIFF_VEC)) return false; /* Avoid removing branch with side effects. */ --- 674,680 ---- if (tmp || !onlyjump_p (insn)) return false; ! if ((!optimize || flow2_completed) && tablejump_p (insn)) return false; /* Avoid removing branch with side effects. */ diff -Nrc3pad gcc-3.2.2/gcc/collect2.c gcc-3.2.3/gcc/collect2.c *** gcc-3.2.2/gcc/collect2.c Fri Aug 16 18:03:06 2002 --- gcc-3.2.3/gcc/collect2.c Mon Mar 31 01:14:02 2003 *************** collect_wait (prog) *** 1522,1528 **** int sig = WTERMSIG (status); error ("%s terminated with signal %d [%s]%s", prog, sig, strsignal(sig), ! status & 0200 ? "" : ", core dumped"); collect_exit (FATAL_EXIT_CODE); } --- 1522,1528 ---- int sig = WTERMSIG (status); error ("%s terminated with signal %d [%s]%s", prog, sig, strsignal(sig), ! WCOREDUMP(status) ? ", core dumped" : ""); collect_exit (FATAL_EXIT_CODE); } diff -Nrc3pad gcc-3.2.2/gcc/combine.c gcc-3.2.3/gcc/combine.c *** gcc-3.2.2/gcc/combine.c Mon Jan 27 17:25:14 2003 --- gcc-3.2.3/gcc/combine.c Wed Mar 19 01:36:16 2003 *************** *** 1,6 **** /* Optimize by combining instructions for GNU compiler. Copyright (C) 1987, 1988, 1992, 1993, 1994, 1995, 1996, 1997, 1998, ! 1999, 2000, 2001, 2002 Free Software Foundation, Inc. This file is part of GCC. --- 1,6 ---- /* Optimize by combining instructions for GNU compiler. Copyright (C) 1987, 1988, 1992, 1993, 1994, 1995, 1996, 1997, 1998, ! 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc. This file is part of GCC. *************** force_to_mode (x, mode, mask, reg, just_ *** 7125,7131 **** < GET_MODE_BITSIZE (GET_MODE (x))) && INTVAL (XEXP (XEXP (x, 0), 1)) < HOST_BITS_PER_WIDE_INT) { ! temp = GEN_INT (mask << INTVAL (XEXP (XEXP (x, 0), 1))); temp = gen_binary (XOR, GET_MODE (x), XEXP (XEXP (x, 0), 0), temp); x = gen_binary (LSHIFTRT, GET_MODE (x), temp, XEXP (XEXP (x, 0), 1)); --- 7125,7132 ---- < GET_MODE_BITSIZE (GET_MODE (x))) && INTVAL (XEXP (XEXP (x, 0), 1)) < HOST_BITS_PER_WIDE_INT) { ! temp = gen_int_mode (mask << INTVAL (XEXP (XEXP (x, 0), 1)), ! GET_MODE (x)); temp = gen_binary (XOR, GET_MODE (x), XEXP (XEXP (x, 0), 0), temp); x = gen_binary (LSHIFTRT, GET_MODE (x), temp, XEXP (XEXP (x, 0), 1)); diff -Nrc3pad gcc-3.2.2/gcc/config/alpha/alpha.md gcc-3.2.3/gcc/config/alpha/alpha.md *** gcc-3.2.2/gcc/config/alpha/alpha.md Sun Sep 8 05:30:19 2002 --- gcc-3.2.3/gcc/config/alpha/alpha.md Sat Feb 22 01:58:21 2003 *************** *** 1,6 **** ;; Machine description for DEC Alpha for GNU C compiler ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, ! ;; 2000, 2001 Free Software Foundation, Inc. ;; Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) ;; ;; This file is part of GNU CC. --- 1,6 ---- ;; Machine description for DEC Alpha for GNU C compiler ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, ! ;; 2000, 2001, 2003 Free Software Foundation, Inc. ;; Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) ;; ;; This file is part of GNU CC. *************** fadd,fmul,fcpys,fdiv,fsqrt,misc,mvi,ftoi *** 5523,5532 **** [(match_dup 0)] "operands[0] = split_small_symbolic_operand (operands[0]);") (define_insn "movdi_er_high_g" [(set (match_operand:DI 0 "register_operand" "=r") (unspec:DI [(match_operand:DI 1 "register_operand" "r") ! (match_operand:DI 2 "global_symbolic_operand" "") (match_operand 3 "const_int_operand" "")] UNSPEC_LITERAL))] "TARGET_EXPLICIT_RELOCS" --- 5523,5534 ---- [(match_dup 0)] "operands[0] = split_small_symbolic_operand (operands[0]);") + ;; Accepts any symbolic, not just global, since function calls that + ;; don't go via bsr still use !literal in hopes of linker relaxation. (define_insn "movdi_er_high_g" [(set (match_operand:DI 0 "register_operand" "=r") (unspec:DI [(match_operand:DI 1 "register_operand" "r") ! (match_operand:DI 2 "symbolic_operand" "") (match_operand 3 "const_int_operand" "")] UNSPEC_LITERAL))] "TARGET_EXPLICIT_RELOCS" diff -Nrc3pad gcc-3.2.2/gcc/config/alpha/osf.h gcc-3.2.3/gcc/config/alpha/osf.h *** gcc-3.2.2/gcc/config/alpha/osf.h Fri Apr 12 22:16:56 2002 --- gcc-3.2.3/gcc/config/alpha/osf.h Mon Mar 17 14:52:14 2003 *************** *** 1,5 **** /* Definitions of target machine for GNU compiler, for DEC Alpha on OSF/1. ! Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 2001 Free Software Foundation, Inc. Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) --- 1,5 ---- /* Definitions of target machine for GNU compiler, for DEC Alpha on OSF/1. ! Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 2001, 2002, 2003 Free Software Foundation, Inc. Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) *************** Boston, MA 02111-1307, USA. */ *** 33,39 **** /* Names to predefine in the preprocessor for this target machine. */ #define CPP_PREDEFINES "\ ! -Dunix -D__osf__ -D_LONGLONG -DSYSTYPE_BSD \ -D_SYSTYPE_BSD -Asystem=unix -Asystem=xpg4" /* Tru64 UNIX V5 requires additional definitions for 16 byte long double --- 33,39 ---- /* Names to predefine in the preprocessor for this target machine. */ #define CPP_PREDEFINES "\ ! -Dunix -D__osf__ -D__digital__ -D__arch64__ -D_LONGLONG -DSYSTYPE_BSD \ -D_SYSTYPE_BSD -Asystem=unix -Asystem=xpg4" /* Tru64 UNIX V5 requires additional definitions for 16 byte long double *************** Boston, MA 02111-1307, USA. */ *** 48,54 **** #undef CPP_SUBTARGET_SPEC #define CPP_SUBTARGET_SPEC \ "%{pthread|threads:-D_REENTRANT} %{threads:-D_PTHREAD_USE_D4} %(cpp_xfloat) \ ! -D__EXTERN_PREFIX" /* Under OSF4, -p and -pg require -lprof1, and -lprof1 requires -lpdf. */ --- 48,54 ---- #undef CPP_SUBTARGET_SPEC #define CPP_SUBTARGET_SPEC \ "%{pthread|threads:-D_REENTRANT} %{threads:-D_PTHREAD_USE_D4} %(cpp_xfloat) \ ! -D__PRAGMA_EXTERN_PREFIX" /* Under OSF4, -p and -pg require -lprof1, and -lprof1 requires -lpdf. */ diff -Nrc3pad gcc-3.2.2/gcc/config/cris/cris.md gcc-3.2.3/gcc/config/cris/cris.md *** gcc-3.2.2/gcc/config/cris/cris.md Mon Jun 17 22:06:34 2002 --- gcc-3.2.3/gcc/config/cris/cris.md Mon Apr 14 21:16:12 2003 *************** *** 1,5 **** ;; GCC machine description for CRIS cpu cores. ! ;; Copyright (C) 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. ;; Contributed by Axis Communications. ;; This file is part of GCC. --- 1,5 ---- ;; GCC machine description for CRIS cpu cores. ! ;; Copyright (C) 1998, 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc. ;; Contributed by Axis Communications. ;; This file is part of GCC. *************** *** 496,502 **** [(set (match_operand:QI 0 "register_operand" "=r,r,r") (mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 496,502 ---- [(set (match_operand:QI 0 "register_operand" "=r,r,r") (mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 519,525 **** [(set (match_operand:HI 0 "register_operand" "=r,r,r") (mem:HI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 519,525 ---- [(set (match_operand:HI 0 "register_operand" "=r,r,r") (mem:HI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 542,548 **** [(set (match_operand:SI 0 "register_operand" "=r,r,r") (mem:SI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 542,548 ---- [(set (match_operand:SI 0 "register_operand" "=r,r,r") (mem:SI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 671,677 **** (define_insn "*mov_sideqi_mem" [(set (mem:QI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r>Ri,r,>Ri"))) (match_operand:QI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) --- 671,677 ---- (define_insn "*mov_sideqi_mem" [(set (mem:QI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r>Rn,r,>Rn"))) (match_operand:QI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) *************** *** 696,702 **** (define_insn "*mov_sidehi_mem" [(set (mem:HI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r>Ri,r,>Ri"))) (match_operand:HI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) --- 696,702 ---- (define_insn "*mov_sidehi_mem" [(set (mem:HI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r>Rn,r,>Rn"))) (match_operand:HI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) *************** *** 721,727 **** (define_insn "*mov_sidesi_mem" [(set (mem:SI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r>Ri,r,>Ri"))) (match_operand:SI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) --- 721,727 ---- (define_insn "*mov_sidesi_mem" [(set (mem:SI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r>Rn,r,>Rn"))) (match_operand:SI 2 "register_operand" "r,r,r,r")) (set (match_operand:SI 3 "register_operand" "=*0,!*2,r,r") (plus:SI (match_dup 0) *************** *** 786,792 **** (define_insn "*clear_sidesi" [(set (mem:SI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r,>Ri"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) --- 786,792 ---- (define_insn "*clear_sidesi" [(set (mem:SI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r,>Rn"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) *************** *** 826,832 **** (define_insn "*clear_sidehi" [(set (mem:HI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r,>Ri"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) --- 826,832 ---- (define_insn "*clear_sidehi" [(set (mem:HI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r,>Rn"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) *************** *** 866,872 **** (define_insn "*clear_sideqi" [(set (mem:QI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Ri,r,>Ri"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) --- 866,872 ---- (define_insn "*clear_sideqi" [(set (mem:QI (plus:SI (match_operand:SI 0 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 1 "cris_bdap_operand" "r>Rn,r,>Rn"))) (const_int 0)) (set (match_operand:SI 2 "register_operand" "=*0,r,r") (plus:SI (match_dup 0) *************** *** 1127,1133 **** 4 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 1127,1133 ---- 4 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 1152,1158 **** 4 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 1152,1158 ---- 4 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 1177,1183 **** 4 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] --- 1177,1183 ---- 4 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 1 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 2 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 3 "register_operand" "=*1,r,r") (plus:SI (match_dup 1) (match_dup 2)))] *************** *** 1473,1479 **** [(match_operand:QI 1 "register_operand" "0,0,0") (mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] --- 1473,1479 ---- [(match_operand:QI 1 "register_operand" "0,0,0") (mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] *************** *** 1499,1505 **** [(match_operand:HI 1 "register_operand" "0,0,0") (mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] --- 1499,1505 ---- [(match_operand:HI 1 "register_operand" "0,0,0") (mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] *************** *** 1525,1531 **** [(match_operand:SI 1 "register_operand" "0,0,0") (mem:SI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] --- 1525,1531 ---- [(match_operand:SI 1 "register_operand" "0,0,0") (mem:SI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) (match_dup 3)))] *************** *** 1624,1630 **** 5 "cris_commutative_orth_op" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri"))) (match_operand:QI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 1624,1630 ---- 5 "cris_commutative_orth_op" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn"))) (match_operand:QI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 1650,1656 **** 5 "cris_commutative_orth_op" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri"))) (match_operand:HI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 1650,1656 ---- 5 "cris_commutative_orth_op" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn"))) (match_operand:HI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 1676,1682 **** 5 "cris_commutative_orth_op" [(mem:SI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri"))) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 1676,1682 ---- 5 "cris_commutative_orth_op" [(mem:SI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn"))) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 1965,1971 **** 6 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 1965,1971 ---- 6 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 1995,2001 **** 6 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 1995,2001 ---- 6 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 2026,2032 **** 6 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 2026,2032 ---- 6 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn") ))])])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 2135,2141 **** 5 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))]) (match_operand:HI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 2135,2141 ---- 5 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))]) (match_operand:HI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 2164,2170 **** 5 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))]) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 2164,2170 ---- 5 "cris_extend_operator" [(mem:QI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))]) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 2193,2199 **** 5 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Ri,r,>Ri")))]) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) --- 2193,2199 ---- 5 "cris_extend_operator" [(mem:HI (plus:SI (match_operand:SI 2 "cris_bdap_operand" "%r,r,r") ! (match_operand:SI 3 "cris_bdap_operand" "r>Rn,r,>Rn")))]) (match_operand:SI 1 "register_operand" "0,0,0")])) (set (match_operand:SI 4 "register_operand" "=*2,r,r") (plus:SI (match_dup 2) *************** *** 4854,4863 **** (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Ri,r,>Ri")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Ri,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Ri,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (mem (match_dup 0)))] "(rtx_equal_p (operands[2], operands[0]) --- 4854,4863 ---- (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Rn,r,>Rn")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Rn,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Rn,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (mem (match_dup 0)))] "(rtx_equal_p (operands[2], operands[0]) *************** *** 4882,4891 **** (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Ri,r,>Ri")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Ri,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Ri,r,0,0"))) (set (mem (match_dup 0)) (match_operand 4 "register_operand" "=r,r,r,r"))] "(rtx_equal_p (operands[2], operands[0]) --- 4882,4891 ---- (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Rn,r,>Rn")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Rn,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Rn,r,0,0"))) (set (mem (match_dup 0)) (match_operand 4 "register_operand" "=r,r,r,r"))] "(rtx_equal_p (operands[2], operands[0]) *************** *** 4912,4921 **** (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Ri,r,>Ri")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Ri,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Ri,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (match_operator 5 "cris_orthogonal_operator" [(match_dup 3) --- 4912,4921 ---- (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Rn,r,>Rn")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Rn,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Rn,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (match_operator 5 "cris_orthogonal_operator" [(match_dup 3) *************** *** 4942,4951 **** (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Ri,r,>Ri")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Ri,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Ri,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (match_operator 5 "cris_commutative_orth_op" [(mem (match_dup 0)) --- 4942,4951 ---- (define_peephole [(set (match_operand:SI 0 "register_operand" "=r,r,r,r") ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,>Rn,r,>Rn")) (set (match_dup 0) ! (plus:SI (match_operand:SI 2 "cris_bdap_biap_operand" "0,0,r>Rn,r") ! (match_operand:SI 3 "cris_bdap_biap_operand" "r>Rn,r,0,0"))) (set (match_operand 4 "register_operand" "=r,r,r,r") (match_operator 5 "cris_commutative_orth_op" [(mem (match_dup 0)) *************** *** 5014,5021 **** (define_peephole [(set (match_operand 0 "register_operand" "=r,r,r,r") (mem (plus:SI ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,r>Ri,r,r>Ri") ! (match_operand:SI 2 "cris_bdap_biap_operand" "r>Ri,r,r>Ri,r")))) (set (match_dup 0) (match_operator 5 "cris_commutative_orth_op" [(match_operand 3 "register_operand" "0,0,r,r") --- 5014,5021 ---- (define_peephole [(set (match_operand 0 "register_operand" "=r,r,r,r") (mem (plus:SI ! (match_operand:SI 1 "cris_bdap_biap_operand" "r,r>Rn,r,r>Rn") ! (match_operand:SI 2 "cris_bdap_biap_operand" "r>Rn,r,r>Rn,r")))) (set (match_dup 0) (match_operator 5 "cris_commutative_orth_op" [(match_operand 3 "register_operand" "0,0,r,r") diff -Nrc3pad gcc-3.2.2/gcc/config/i386/i386.c gcc-3.2.3/gcc/config/i386/i386.c *** gcc-3.2.2/gcc/config/i386/i386.c Fri Jan 31 22:06:28 2003 --- gcc-3.2.3/gcc/config/i386/i386.c Wed Mar 12 09:04:01 2003 *************** static enum x86_64_reg_class merge_class *** 822,827 **** --- 822,833 ---- struct gcc_target targetm = TARGET_INITIALIZER; + /* The svr4 ABI for the i386 says that records and unions are returned + in memory. */ + #ifndef DEFAULT_PCC_STRUCT_RETURN + #define DEFAULT_PCC_STRUCT_RETURN 1 + #endif + /* Sometimes certain combinations of command options do not make sense on a particular target machine. You can define a macro `OVERRIDE_OPTIONS' to take account of this. This macro, if *************** function_arg (cum, mode, type, named) *** 2232,2237 **** --- 2238,2246 ---- break; case BLKmode: + if (bytes < 0) + break; + /* FALLTHRU */ case DImode: case SImode: case HImode: *************** memory_address_length (addr) *** 9930,9936 **** if (disp) { if (GET_CODE (disp) == CONST_INT ! && CONST_OK_FOR_LETTER_P (INTVAL (disp), 'K')) len = 1; else len = 4; --- 9939,9946 ---- if (disp) { if (GET_CODE (disp) == CONST_INT ! && CONST_OK_FOR_LETTER_P (INTVAL (disp), 'K') ! && base) len = 1; else len = 4; *************** ix86_attr_length_address_default (insn) *** 9993,9998 **** --- 10003,10028 ---- rtx insn; { int i; + + if (get_attr_type (insn) == TYPE_LEA) + { + rtx set = PATTERN (insn); + if (GET_CODE (set) == SET) + ; + else if (GET_CODE (set) == PARALLEL + && GET_CODE (XVECEXP (set, 0, 0)) == SET) + set = XVECEXP (set, 0, 0); + else + { + #ifdef ENABLE_CHECKING + abort (); + #endif + return 0; + } + + return memory_address_length (SET_SRC (set)); + } + extract_insn_cached (insn); for (i = recog_data.n_operands - 1; i >= 0; --i) if (GET_CODE (recog_data.operand[i]) == MEM) diff -Nrc3pad gcc-3.2.2/gcc/config/i386/i386.h gcc-3.2.3/gcc/config/i386/i386.h *** gcc-3.2.2/gcc/config/i386/i386.h Tue Dec 10 00:40:11 2002 --- gcc-3.2.3/gcc/config/i386/i386.h Thu Feb 20 20:04:02 2003 *************** extern int ix86_arch; *** 587,593 **** %{march=pentiumpro|march=i686|march=pentium2|march=pentium3:-D__i686 -D__i686__ \ -D__pentiumpro -D__pentiumpro__ \ %{!mcpu*:-D__tune_i686__ -D__tune_pentiumpro__ }}\ ! %{march=march=pentium2|march=pentium3: -D__pentium2 -D__pentium2__\ %{!mcpu*:-D__tune_pentium2__ }}\ %{march=pentium3: -D__pentium3 -D__pentium3__\ %{!mcpu*:-D__tune_pentium3__ }}\ --- 587,593 ---- %{march=pentiumpro|march=i686|march=pentium2|march=pentium3:-D__i686 -D__i686__ \ -D__pentiumpro -D__pentiumpro__ \ %{!mcpu*:-D__tune_i686__ -D__tune_pentiumpro__ }}\ ! %{march=pentium2|march=pentium3: -D__pentium2 -D__pentium2__\ %{!mcpu*:-D__tune_pentium2__ }}\ %{march=pentium3: -D__pentium3 -D__pentium3__\ %{!mcpu*:-D__tune_pentium3__ }}\ *************** typedef struct ix86_args { *** 1723,1737 **** /* If PIC, we cannot make sibling calls to global functions because the PLT requires %ebx live. ! If we are returning floats on the register stack, we cannot make ! sibling calls to functions that return floats. (The stack adjust ! instruction will wind up after the sibcall jump, and not be executed.) */ #define FUNCTION_OK_FOR_SIBCALL(DECL) \ ((DECL) \ && (! flag_pic || ! TREE_PUBLIC (DECL)) \ && (! TARGET_FLOAT_RETURNS_IN_80387 \ ! || ! FLOAT_MODE_P (TYPE_MODE (TREE_TYPE (TREE_TYPE (DECL)))) \ ! || FLOAT_MODE_P (TYPE_MODE (TREE_TYPE (TREE_TYPE (cfun->decl)))))) /* Perform any needed actions needed for a function that is receiving a variable number of arguments. --- 1723,1739 ---- /* If PIC, we cannot make sibling calls to global functions because the PLT requires %ebx live. ! If we are returning floats on the 80387 register stack, we cannot ! make a sibcall from a function that doesn't return a float to a ! function that does or, conversely, from a function that does return ! a float to a function that doesn't; the necessary stack adjustment ! would not be executed. */ #define FUNCTION_OK_FOR_SIBCALL(DECL) \ ((DECL) \ && (! flag_pic || ! TREE_PUBLIC (DECL)) \ && (! TARGET_FLOAT_RETURNS_IN_80387 \ ! || (FLOAT_MODE_P (TYPE_MODE (TREE_TYPE (TREE_TYPE (DECL)))) \ ! == FLOAT_MODE_P (TYPE_MODE (TREE_TYPE (TREE_TYPE (cfun->decl))))))) /* Perform any needed actions needed for a function that is receiving a variable number of arguments. diff -Nrc3pad gcc-3.2.2/gcc/config/i386/i386.md gcc-3.2.3/gcc/config/i386/i386.md *** gcc-3.2.2/gcc/config/i386/i386.md Thu Oct 24 17:11:54 2002 --- gcc-3.2.3/gcc/config/i386/i386.md Tue Mar 25 10:42:12 2003 *************** *** 131,137 **** ;; The (bounding maximum) length of an instruction immediate. (define_attr "length_immediate" "" ! (cond [(eq_attr "type" "incdec,setcc,icmov,ibr,str,cld,lea,other,multi,idiv,sse,mmx") (const_int 0) (eq_attr "i387" "1") (const_int 0) --- 131,137 ---- ;; The (bounding maximum) length of an instruction immediate. (define_attr "length_immediate" "" ! (cond [(eq_attr "type" "incdec,setcc,icmov,str,cld,lea,other,multi,idiv,sse,mmx") (const_int 0) (eq_attr "i387" "1") (const_int 0) *************** *** 147,159 **** (if_then_else (match_operand 1 "constant_call_address_operand" "") (const_int 4) (const_int 0)) (eq_attr "type" "ibr") ! (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -128)) ! (lt (minus (match_dup 0) (pc)) ! (const_int 124))) ! (const_int 1) ! (const_int 4)) ] (symbol_ref "/* Update immediate_length and other attributes! */ abort(),1"))) --- 147,156 ---- (if_then_else (match_operand 1 "constant_call_address_operand" "") (const_int 4) (const_int 0)) + ;; We don't know the size before shorten_branches. Expect + ;; the instruction to fit for better scheduling. (eq_attr "type" "ibr") ! (const_int 1) ] (symbol_ref "/* Update immediate_length and other attributes! */ abort(),1"))) *************** *** 162,168 **** (cond [(eq_attr "type" "str,cld,other,multi,fxch") (const_int 0) (and (eq_attr "type" "call") ! (match_operand 1 "constant_call_address_operand" "")) (const_int 0) (and (eq_attr "type" "callv") (match_operand 1 "constant_call_address_operand" "")) --- 159,165 ---- (cond [(eq_attr "type" "str,cld,other,multi,fxch") (const_int 0) (and (eq_attr "type" "call") ! (match_operand 0 "constant_call_address_operand" "")) (const_int 0) (and (eq_attr "type" "callv") (match_operand 1 "constant_call_address_operand" "")) *************** *** 205,210 **** --- 202,213 ---- (and (match_operand 0 "register_operand" "") (match_operand 1 "immediate_operand" ""))) (const_int 0) + (and (eq_attr "type" "call") + (match_operand 0 "constant_call_address_operand" "")) + (const_int 0) + (and (eq_attr "type" "callv") + (match_operand 1 "constant_call_address_operand" "")) + (const_int 0) ] (const_int 1))) *************** *** 1733,1746 **** (set_attr "mode" "SI") (set_attr "length_immediate" "1")]) - ; The first alternative is used only to compute proper length of instruction. - ; Reload's algorithm does not take into account the cost of spill instructions - ; needed to free register in given class, so avoid it from choosing the first - ; alternative when eax is not available. - (define_insn "*movsi_1" ! [(set (match_operand:SI 0 "nonimmediate_operand" "=*?a,r,*?a,m,!*y,!rm,!*y,!*Y,!rm,!*Y") ! (match_operand:SI 1 "general_operand" "im,rinm,rinm,rin,rm,*y,*y,rm,*Y,*Y"))] "GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM" { switch (get_attr_type (insn)) --- 1736,1744 ---- (set_attr "mode" "SI") (set_attr "length_immediate" "1")]) (define_insn "*movsi_1" ! [(set (match_operand:SI 0 "nonimmediate_operand" "=r,m,!*y,!rm,!*y,!*Y,!rm,!*Y") ! (match_operand:SI 1 "general_operand" "rinm,rin,rm,*y,*y,rm,*Y,*Y"))] "GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM" { switch (get_attr_type (insn)) *************** *** 1765,1781 **** } } [(set (attr "type") ! (cond [(eq_attr "alternative" "4,5,6") (const_string "mmx") ! (eq_attr "alternative" "7,8,9") (const_string "sse") (and (ne (symbol_ref "flag_pic") (const_int 0)) (match_operand:SI 1 "symbolic_operand" "")) (const_string "lea") ] (const_string "imov"))) ! (set_attr "modrm" "0,*,0,*,*,*,*,*,*,*") ! (set_attr "mode" "SI,SI,SI,SI,SI,SI,DI,TI,SI,SI")]) ;; Stores and loads of ax to arbitary constant address. ;; We fake an second form of instruction to force reload to load address --- 1763,1778 ---- } } [(set (attr "type") ! (cond [(eq_attr "alternative" "2,3,4") (const_string "mmx") ! (eq_attr "alternative" "5,6,7") (const_string "sse") (and (ne (symbol_ref "flag_pic") (const_int 0)) (match_operand:SI 1 "symbolic_operand" "")) (const_string "lea") ] (const_string "imov"))) ! (set_attr "mode" "SI,SI,SI,SI,DI,TI,SI,SI")]) ;; Stores and loads of ax to arbitary constant address. ;; We fake an second form of instruction to force reload to load address *************** *** 1848,1861 **** [(set_attr "type" "push") (set_attr "mode" "QI")]) - ; The first alternative is used only to compute proper length of instruction. - ; Reload's algorithm does not take into account the cost of spill instructions - ; needed to free register in given class, so avoid it from choosing the first - ; alternative when eax is not available. - (define_insn "*movhi_1" ! [(set (match_operand:HI 0 "nonimmediate_operand" "=*?a,r,r,*?a,r,m") ! (match_operand:HI 1 "general_operand" "i,r,rn,rm,rm,rn"))] "GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM" { switch (get_attr_type (insn)) --- 1845,1853 ---- [(set_attr "type" "push") (set_attr "mode" "QI")]) (define_insn "*movhi_1" ! [(set (match_operand:HI 0 "nonimmediate_operand" "=r,r,r,m") ! (match_operand:HI 1 "general_operand" "r,rn,rm,rn"))] "GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM" { switch (get_attr_type (insn)) *************** *** 1872,1907 **** } } [(set (attr "type") ! (cond [(and (eq_attr "alternative" "0,1") (ior (eq (symbol_ref "TARGET_PARTIAL_REG_STALL") (const_int 0)) (eq (symbol_ref "TARGET_HIMODE_MATH") (const_int 0)))) (const_string "imov") ! (and (eq_attr "alternative" "2,3,4") (match_operand:HI 1 "aligned_operand" "")) (const_string "imov") (and (ne (symbol_ref "TARGET_MOVX") (const_int 0)) ! (eq_attr "alternative" "0,1,3,4")) (const_string "imovx") ] (const_string "imov"))) (set (attr "mode") (cond [(eq_attr "type" "imovx") (const_string "SI") ! (and (eq_attr "alternative" "2,3,4") (match_operand:HI 1 "aligned_operand" "")) (const_string "SI") ! (and (eq_attr "alternative" "0,1") (ior (eq (symbol_ref "TARGET_PARTIAL_REG_STALL") (const_int 0)) (eq (symbol_ref "TARGET_HIMODE_MATH") (const_int 0)))) (const_string "SI") ] ! (const_string "HI"))) ! (set_attr "modrm" "0,*,*,0,*,*")]) ;; Stores and loads of ax to arbitary constant address. ;; We fake an second form of instruction to force reload to load address --- 1864,1898 ---- } } [(set (attr "type") ! (cond [(and (eq_attr "alternative" "0") (ior (eq (symbol_ref "TARGET_PARTIAL_REG_STALL") (const_int 0)) (eq (symbol_ref "TARGET_HIMODE_MATH") (const_int 0)))) (const_string "imov") ! (and (eq_attr "alternative" "1,2") (match_operand:HI 1 "aligned_operand" "")) (const_string "imov") (and (ne (symbol_ref "TARGET_MOVX") (const_int 0)) ! (eq_attr "alternative" "0,2")) (const_string "imovx") ] (const_string "imov"))) (set (attr "mode") (cond [(eq_attr "type" "imovx") (const_string "SI") ! (and (eq_attr "alternative" "1,2") (match_operand:HI 1 "aligned_operand" "")) (const_string "SI") ! (and (eq_attr "alternative" "0") (ior (eq (symbol_ref "TARGET_PARTIAL_REG_STALL") (const_int 0)) (eq (symbol_ref "TARGET_HIMODE_MATH") (const_int 0)))) (const_string "SI") ] ! (const_string "HI")))]) ;; Stores and loads of ax to arbitary constant address. ;; We fake an second form of instruction to force reload to load address *************** *** 2122,2128 **** (define_expand "movstrictqi" [(set (strict_low_part (match_operand:QI 0 "nonimmediate_operand" "")) (match_operand:QI 1 "general_operand" ""))] ! "! TARGET_PARTIAL_REG_STALL" { /* Don't generate memory->memory moves, go through a register. */ if (GET_CODE (operands[0]) == MEM && GET_CODE (operands[1]) == MEM) --- 2113,2119 ---- (define_expand "movstrictqi" [(set (strict_low_part (match_operand:QI 0 "nonimmediate_operand" "")) (match_operand:QI 1 "general_operand" ""))] ! "! TARGET_PARTIAL_REG_STALL || optimize_size" { /* Don't generate memory->memory moves, go through a register. */ if (GET_CODE (operands[0]) == MEM && GET_CODE (operands[1]) == MEM) *************** *** 2132,2138 **** (define_insn "*movstrictqi_1" [(set (strict_low_part (match_operand:QI 0 "nonimmediate_operand" "+qm,q")) (match_operand:QI 1 "general_operand" "*qn,m"))] ! "! TARGET_PARTIAL_REG_STALL && (GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM)" "mov{b}\t{%1, %0|%0, %1}" [(set_attr "type" "imov") --- 2123,2129 ---- (define_insn "*movstrictqi_1" [(set (strict_low_part (match_operand:QI 0 "nonimmediate_operand" "+qm,q")) (match_operand:QI 1 "general_operand" "*qn,m"))] ! "(! TARGET_PARTIAL_REG_STALL || optimize_size) && (GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM)" "mov{b}\t{%1, %0|%0, %1}" [(set_attr "type" "imov") *************** *** 12961,12973 **** "" "%+j%C1\t%l0" [(set_attr "type" "ibr") ! (set (attr "prefix_0f") (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -128)) (lt (minus (match_dup 0) (pc)) ! (const_int 124))) ! (const_int 0) ! (const_int 1)))]) (define_insn "*jcc_2" [(set (pc) --- 12952,12965 ---- "" "%+j%C1\t%l0" [(set_attr "type" "ibr") ! (set_attr "modrm" "0") ! (set (attr "length") (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -126)) (lt (minus (match_dup 0) (pc)) ! (const_int 128))) ! (const_int 2) ! (const_int 6)))]) (define_insn "*jcc_2" [(set (pc) *************** *** 12978,12990 **** "" "%+j%c1\t%l0" [(set_attr "type" "ibr") ! (set (attr "prefix_0f") (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -128)) (lt (minus (match_dup 0) (pc)) ! (const_int 124))) ! (const_int 0) ! (const_int 1)))]) ;; In general it is not safe to assume too much about CCmode registers, ;; so simplify-rtx stops when it sees a second one. Under certain --- 12970,12983 ---- "" "%+j%c1\t%l0" [(set_attr "type" "ibr") ! (set_attr "modrm" "0") ! (set (attr "length") (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -126)) (lt (minus (match_dup 0) (pc)) ! (const_int 128))) ! (const_int 2) ! (const_int 6)))]) ;; In general it is not safe to assume too much about CCmode registers, ;; so simplify-rtx stops when it sees a second one. Under certain *************** *** 13244,13250 **** (label_ref (match_operand 0 "" "")))] "" "jmp\t%l0" ! [(set_attr "type" "ibr")]) (define_expand "indirect_jump" [(set (pc) (match_operand 0 "nonimmediate_operand" "rm"))] --- 13237,13251 ---- (label_ref (match_operand 0 "" "")))] "" "jmp\t%l0" ! [(set_attr "type" "ibr") ! (set (attr "length") ! (if_then_else (and (ge (minus (match_dup 0) (pc)) ! (const_int -126)) ! (lt (minus (match_dup 0) (pc)) ! (const_int 128))) ! (const_int 2) ! (const_int 5))) ! (set_attr "modrm" "0")]) (define_expand "indirect_jump" [(set (pc) (match_operand 0 "nonimmediate_operand" "rm"))] *************** *** 13357,13370 **** return "dec{l}\t%1\;%+jne\t%l0"; } [(set_attr "ppro_uops" "many") ! (set (attr "type") (if_then_else (and (eq_attr "alternative" "0") (and (ge (minus (match_dup 0) (pc)) ! (const_int -128)) (lt (minus (match_dup 0) (pc)) ! (const_int 124)))) ! (const_string "ibr") ! (const_string "multi")))]) (define_split [(set (pc) --- 13358,13374 ---- return "dec{l}\t%1\;%+jne\t%l0"; } [(set_attr "ppro_uops" "many") ! (set (attr "length") (if_then_else (and (eq_attr "alternative" "0") (and (ge (minus (match_dup 0) (pc)) ! (const_int -126)) (lt (minus (match_dup 0) (pc)) ! (const_int 128)))) ! (const_int 2) ! (const_int 16))) ! ;; We don't know the type before shorten branches. Optimistically expect ! ;; the loop instruction to match. ! (set (attr "type") (const_string "ibr"))]) (define_split [(set (pc) *************** *** 13879,13885 **** [(set_attr "length_immediate" "0") (set_attr "length" "1") (set_attr "modrm" "0") - (set_attr "modrm" "0") (set_attr "athlon_decode" "vector") (set_attr "ppro_uops" "few")]) --- 13883,13888 ---- *************** *** 13892,13904 **** [(set_attr "length_immediate" "0") (set_attr "length" "1") (set_attr "modrm" "0") - (set_attr "modrm" "0") (set_attr "athlon_decode" "vector") (set_attr "ppro_uops" "few")]) (define_expand "ffssi2" [(set (match_operand:SI 0 "nonimmediate_operand" "") ! (ffs:SI (match_operand:SI 1 "general_operand" "")))] "" { rtx out = gen_reg_rtx (SImode), tmp = gen_reg_rtx (SImode); --- 13895,13906 ---- [(set_attr "length_immediate" "0") (set_attr "length" "1") (set_attr "modrm" "0") (set_attr "athlon_decode" "vector") (set_attr "ppro_uops" "few")]) (define_expand "ffssi2" [(set (match_operand:SI 0 "nonimmediate_operand" "") ! (ffs:SI (match_operand:SI 1 "nonimmediate_operand" "")))] "" { rtx out = gen_reg_rtx (SImode), tmp = gen_reg_rtx (SImode); *************** *** 16862,16867 **** --- 16864,16873 ---- operands[2] = gen_lowpart (SImode, operands[2]); PUT_MODE (operands[3], SImode);") + ; Promote the QImode tests, as i386 has encoding of the AND + ; instruction with 32-bit sign-extended immediate and thus the + ; instruction size is unchanged, except in the %eax case for + ; which it is increased by one byte, hence the ! optimize_size. (define_split [(set (reg 17) (compare (and (match_operand 1 "aligned_operand" "") *************** *** 16870,16879 **** (set (match_operand 0 "register_operand" "") (and (match_dup 1) (match_dup 2)))] "! TARGET_PARTIAL_REG_STALL && reload_completed ! && ix86_match_ccmode (insn, CCNOmode) && (GET_MODE (operands[0]) == HImode ! || (GET_MODE (operands[0]) == QImode ! && (TARGET_PROMOTE_QImode || optimize_size)))" [(parallel [(set (reg:CCNO 17) (compare:CCNO (and:SI (match_dup 1) (match_dup 2)) (const_int 0))) --- 16876,16886 ---- (set (match_operand 0 "register_operand" "") (and (match_dup 1) (match_dup 2)))] "! TARGET_PARTIAL_REG_STALL && reload_completed ! /* Ensure that the operand will remain sign-extended immediate. */ ! && ix86_match_ccmode (insn, INTVAL (operands[2]) >= 0 ? CCNOmode : CCZmode) ! && ! optimize_size && (GET_MODE (operands[0]) == HImode ! || (GET_MODE (operands[0]) == QImode && TARGET_PROMOTE_QImode))" [(parallel [(set (reg:CCNO 17) (compare:CCNO (and:SI (match_dup 1) (match_dup 2)) (const_int 0))) *************** *** 16886,16901 **** operands[0] = gen_lowpart (SImode, operands[0]); operands[1] = gen_lowpart (SImode, operands[1]);") (define_split [(set (reg 17) ! (compare (and (match_operand 0 "aligned_operand" "") ! (match_operand 1 "const_int_operand" "")) (const_int 0)))] "! TARGET_PARTIAL_REG_STALL && reload_completed ! && ix86_match_ccmode (insn, CCNOmode) ! && (GET_MODE (operands[0]) == HImode ! || (GET_MODE (operands[0]) == QImode ! && (TARGET_PROMOTE_QImode || optimize_size)))" [(set (reg:CCNO 17) (compare:CCNO (and:SI (match_dup 0) (match_dup 1)) (const_int 0)))] --- 16893,16911 ---- operands[0] = gen_lowpart (SImode, operands[0]); operands[1] = gen_lowpart (SImode, operands[1]);") + ; Don't promote the QImode tests, as i386 doesn't have encoding of + ; the TEST instruction with 32-bit sign-extended immediate and thus + ; the instruction size would at least double, which is not what we + ; want even with ! optimize_size. (define_split [(set (reg 17) ! (compare (and (match_operand:HI 0 "aligned_operand" "") ! (match_operand:HI 1 "const_int_operand" "")) (const_int 0)))] "! TARGET_PARTIAL_REG_STALL && reload_completed ! /* Ensure that the operand will remain sign-extended immediate. */ ! && ix86_match_ccmode (insn, INTVAL (operands[1]) >= 0 ? CCNOmode : CCZmode) ! && ! optimize_size" [(set (reg:CCNO 17) (compare:CCNO (and:SI (match_dup 0) (match_dup 1)) (const_int 0)))] diff -Nrc3pad gcc-3.2.2/gcc/config/i386/linux.h gcc-3.2.3/gcc/config/i386/linux.h *** gcc-3.2.2/gcc/config/i386/linux.h Mon Apr 15 20:27:27 2002 --- gcc-3.2.3/gcc/config/i386/linux.h Thu Mar 6 20:19:22 2003 *************** Boston, MA 02111-1307, USA. */ *** 218,225 **** #endif /* Do code reading to identify a signal frame, and set the frame ! state data appropriately. See unwind-dw2.c for the structs. */ #ifdef IN_LIBGCC2 #include #include --- 218,227 ---- #endif /* Do code reading to identify a signal frame, and set the frame ! state data appropriately. See unwind-dw2.c for the structs. ! Don't use this at all if inhibit_libc is used. */ + #ifndef inhibit_libc #ifdef IN_LIBGCC2 #include #include *************** Boston, MA 02111-1307, USA. */ *** 278,280 **** --- 280,283 ---- (FS)->retaddr_column = 8; \ goto SUCCESS; \ } while (0) + #endif /* ifndef inhibit_libc */ diff -Nrc3pad gcc-3.2.2/gcc/config/i386/linux64.h gcc-3.2.3/gcc/config/i386/linux64.h *** gcc-3.2.2/gcc/config/i386/linux64.h Sun Oct 27 09:24:50 2002 --- gcc-3.2.3/gcc/config/i386/linux64.h Fri Mar 14 12:18:24 2003 *************** Boston, MA 02111-1307, USA. */ *** 28,34 **** #define CPP_PREDEFINES "-D__ELF__ -Dunix -D__gnu_linux__ -Dlinux -Asystem(posix)" #undef CPP_SPEC ! #define CPP_SPEC "%(cpp_cpu) %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} %{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT} %{!m32:-D__LONG_MAX__=9223372036854775807L}" /* The svr4 ABI for the i386 says that records and unions are returned in memory. In the 64bit compilation we will turn this flag off in --- 28,35 ---- #define CPP_PREDEFINES "-D__ELF__ -Dunix -D__gnu_linux__ -Dlinux -Asystem(posix)" #undef CPP_SPEC ! #define CPP_SPEC "%(cpp_cpu) %{fPIC:-D__PIC__ -D__pic__} %{fpic:-D__PIC__ -D__pic__} %{posix:-D_POSIX_SOURCE} %{pthread:-D_REENTRANT} \ ! %{!m32:-D__LONG_MAX__=9223372036854775807L -D__LP64__ -D_LP64}" /* The svr4 ABI for the i386 says that records and unions are returned in memory. In the 64bit compilation we will turn this flag off in diff -Nrc3pad gcc-3.2.2/gcc/config/m68k/m68k.md gcc-3.2.3/gcc/config/m68k/m68k.md *** gcc-3.2.2/gcc/config/m68k/m68k.md Thu Jan 30 16:57:24 2003 --- gcc-3.2.3/gcc/config/m68k/m68k.md Mon Mar 17 10:22:00 2003 *************** *** 1,5 **** ;;- Machine description for GNU compiler, Motorola 68000 Version ! ;; Copyright (C) 1987, 1988, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2002 ;; Free Software Foundation, Inc. ;; This file is part of GNU CC. --- 1,5 ---- ;;- Machine description for GNU compiler, Motorola 68000 Version ! ;; Copyright (C) 1987, 1988, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2001, 2002, 2003 ;; Free Software Foundation, Inc. ;; This file is part of GNU CC. *************** *** 3092,3098 **** [(parallel [(set (subreg:SI (match_operand:DI 0 "register_operand" "") 4) (mult:SI (match_operand:SI 1 "register_operand" "") ! (match_operand:SI 2 "nonimmediate_operand" ""))) (set (subreg:SI (match_dup 0) 0) (truncate:SI (lshiftrt:DI (mult:DI (zero_extend:DI (match_dup 1)) (zero_extend:DI (match_dup 2))) --- 3092,3098 ---- [(parallel [(set (subreg:SI (match_operand:DI 0 "register_operand" "") 4) (mult:SI (match_operand:SI 1 "register_operand" "") ! (match_operand:SI 2 "register_operand" ""))) (set (subreg:SI (match_dup 0) 0) (truncate:SI (lshiftrt:DI (mult:DI (zero_extend:DI (match_dup 1)) (zero_extend:DI (match_dup 2))) *************** *** 3131,3137 **** [(parallel [(set (subreg:SI (match_operand:DI 0 "register_operand" "") 4) (mult:SI (match_operand:SI 1 "register_operand" "") ! (match_operand:SI 2 "nonimmediate_operand" ""))) (set (subreg:SI (match_dup 0) 0) (truncate:SI (lshiftrt:DI (mult:DI (sign_extend:DI (match_dup 1)) (sign_extend:DI (match_dup 2))) --- 3131,3137 ---- [(parallel [(set (subreg:SI (match_operand:DI 0 "register_operand" "") 4) (mult:SI (match_operand:SI 1 "register_operand" "") ! (match_operand:SI 2 "register_operand" ""))) (set (subreg:SI (match_dup 0) 0) (truncate:SI (lshiftrt:DI (mult:DI (sign_extend:DI (match_dup 1)) (sign_extend:DI (match_dup 2))) *************** *** 3832,3838 **** case -1 : /* FIXME : a scratch register would be welcome here if operand[0] is not a register */ ! output_asm_insn (\"move%.l %#-1,%R0\", operands); break; default : { --- 3832,3838 ---- case -1 : /* FIXME : a scratch register would be welcome here if operand[0] is not a register */ ! output_asm_insn (\"move%.l %#-1,%0\", operands); break; default : { diff -Nrc3pad gcc-3.2.2/gcc/config/mips/iris6.h gcc-3.2.3/gcc/config/mips/iris6.h *** gcc-3.2.2/gcc/config/mips/iris6.h Sun May 19 15:21:35 2002 --- gcc-3.2.3/gcc/config/mips/iris6.h Thu Mar 27 20:08:13 2003 *************** *** 1,5 **** /* Definitions of target machine for GNU compiler. Iris version 6. ! Copyright (C) 1994, 1995, 1996, 1997, 1998, 2000, 2001 Free Software Foundation, Inc. This file is part of GNU CC. --- 1,6 ---- /* Definitions of target machine for GNU compiler. Iris version 6. ! Copyright (C) 1994, 1995, 1996, 1997, 1998, 2000, 2001, 2002, 2003 ! Free Software Foundation, Inc. This file is part of GNU CC. *************** Boston, MA 02111-1307, USA. */ *** 129,139 **** prior to 6.5. They normally get defined in SUBTARGET_CPP_SPEC if !ansi, for g++ we want them regardless. We don't need this on irix6.5 itself, but it shouldn't hurt other than the namespace ! pollution. */ #undef CPLUSPLUS_CPP_SPEC #define CPLUSPLUS_CPP_SPEC "\ -D__LANGUAGE_C_PLUS_PLUS -D_LANGUAGE_C_PLUS_PLUS \ ! %{ansi:-D__EXTENSIONS__ -D_SGI_SOURCE} %(cpp) \ " /* Irix 6 uses DWARF-2. */ --- 130,141 ---- prior to 6.5. They normally get defined in SUBTARGET_CPP_SPEC if !ansi, for g++ we want them regardless. We don't need this on irix6.5 itself, but it shouldn't hurt other than the namespace ! pollution. libstdc++ v3 needs many ISO C99 features provided ! in IRIX 6.5.18, but protected by the __c99 macro. */ #undef CPLUSPLUS_CPP_SPEC #define CPLUSPLUS_CPP_SPEC "\ -D__LANGUAGE_C_PLUS_PLUS -D_LANGUAGE_C_PLUS_PLUS \ ! %{ansi:-D__EXTENSIONS__ -D_SGI_SOURCE} -D__c99 %(cpp) \ " /* Irix 6 uses DWARF-2. */ diff -Nrc3pad gcc-3.2.2/gcc/config/mips/mips-protos.h gcc-3.2.3/gcc/config/mips/mips-protos.h *** gcc-3.2.2/gcc/config/mips/mips-protos.h Sun Mar 24 08:13:16 2002 --- gcc-3.2.3/gcc/config/mips/mips-protos.h Wed Feb 12 15:25:45 2003 *************** extern void init_cumulative_args PARAMS *** 80,85 **** --- 80,86 ---- tree, rtx)); extern void gen_conditional_move PARAMS ((rtx *)); extern void mips_gen_conditional_trap PARAMS ((rtx *)); + extern void mips_emit_fcc_reload PARAMS ((rtx, rtx, rtx)); extern void machine_dependent_reorg PARAMS ((rtx)); extern int mips_address_cost PARAMS ((rtx)); extern void mips_count_memory_refs PARAMS ((rtx, int)); diff -Nrc3pad gcc-3.2.2/gcc/config/mips/mips.c gcc-3.2.3/gcc/config/mips/mips.c *** gcc-3.2.2/gcc/config/mips/mips.c Fri Jul 26 23:23:02 2002 --- gcc-3.2.3/gcc/config/mips/mips.c Wed Feb 12 15:25:49 2003 *************** mips_gen_conditional_trap (operands) *** 3267,3272 **** --- 3267,3317 ---- gen_rtx (cmp_code, GET_MODE (operands[0]), op0, op1), operands[1])); } + + /* Return true if operand OP is a condition code register. + Only for use during or after reload. */ + + int + fcc_register_operand (op, mode) + rtx op; + enum machine_mode mode; + { + return ((mode == VOIDmode || mode == GET_MODE (op)) + && (reload_in_progress || reload_completed) + && (GET_CODE (op) == REG || GET_CODE (op) == SUBREG) + && ST_REG_P (true_regnum (op))); + } + + /* Emit code to move general operand SRC into condition-code + register DEST. SCRATCH is a scratch TFmode float register. + The sequence is: + + FP1 = SRC + FP2 = 0.0f + DEST = FP2 < FP1 + + where FP1 and FP2 are single-precision float registers + taken from SCRATCH. */ + + void + mips_emit_fcc_reload (dest, src, scratch) + rtx dest, src, scratch; + { + rtx fp1, fp2; + + /* Change the source to SFmode. */ + if (GET_CODE (src) == MEM) + src = adjust_address (src, SFmode, 0); + else if (GET_CODE (src) == REG || GET_CODE (src) == SUBREG) + src = gen_rtx_REG (SFmode, true_regnum (src)); + + fp1 = gen_rtx_REG (SFmode, REGNO (scratch)); + fp2 = gen_rtx_REG (SFmode, REGNO (scratch) + FP_INC); + + emit_move_insn (copy_rtx (fp1), src); + emit_move_insn (copy_rtx (fp2), CONST0_RTX (SFmode)); + emit_insn (gen_slt_sf (dest, fp2, fp1)); + } /* Write a loop to move a constant number of bytes. Generate load/stores as follows: diff -Nrc3pad gcc-3.2.2/gcc/config/mips/mips.h gcc-3.2.3/gcc/config/mips/mips.h *** gcc-3.2.2/gcc/config/mips/mips.h Fri Apr 26 21:32:14 2002 --- gcc-3.2.3/gcc/config/mips/mips.h Wed Feb 12 15:25:48 2003 *************** do { \ *** 1582,1587 **** --- 1582,1591 ---- /* For MIPS, width of a floating point register. */ #define UNITS_PER_FPREG (TARGET_FLOAT64 ? 8 : 4) + /* If register $f0 holds a floating-point value, $f(0 + FP_INC) is + the next available register. */ + #define FP_INC (TARGET_FLOAT64 || TARGET_SINGLE_FLOAT ? 1 : 2) + /* A C expression for the size in bits of the type `int' on the target machine. If you don't define this, the default is one word. */ *************** while (0) *** 4001,4006 **** --- 4005,4011 ---- {"se_nonimmediate_operand", { SUBREG, REG, MEM, SIGN_EXTEND }}, \ {"consttable_operand", { LABEL_REF, SYMBOL_REF, CONST_INT, \ CONST_DOUBLE, CONST }}, \ + {"fcc_register_operand", { REG, SUBREG }}, \ {"extend_operator", { SIGN_EXTEND, ZERO_EXTEND }}, \ {"highpart_shift_operator", { ASHIFTRT, LSHIFTRT, ROTATERT, ROTATE }}, diff -Nrc3pad gcc-3.2.2/gcc/config/mips/mips.md gcc-3.2.3/gcc/config/mips/mips.md *** gcc-3.2.2/gcc/config/mips/mips.md Mon Nov 11 05:57:14 2002 --- gcc-3.2.3/gcc/config/mips/mips.md Wed Feb 12 15:25:50 2003 *************** move\\t%0,%z4\\n\\ *** 5786,5862 **** (set_attr "mode" "SI") (set_attr "length" "8,4,4,8,4,8,4,4,4,4,8,4,8")]) ! ;; Reload condition code registers. These need scratch registers. ! (define_expand "reload_incc" ! [(set (match_operand:CC 0 "register_operand" "=z") ! (match_operand:CC 1 "general_operand" "z")) (clobber (match_operand:TF 2 "register_operand" "=&f"))] "ISA_HAS_8CC && TARGET_HARD_FLOAT" " { ! rtx source; ! rtx fp1, fp2; ! int regno; ! ! /* This is called when are copying some value into a condition code ! register. Operand 0 is the condition code register. Operand 1 ! is the source. Operand 2 is a scratch register; we use TFmode ! because we actually need two floating point registers. */ ! if (! ST_REG_P (true_regnum (operands[0])) ! || ! FP_REG_P (true_regnum (operands[2]))) ! abort (); ! ! /* We need to get the source in SFmode so that the insn is ! recognized. */ ! if (GET_CODE (operands[1]) == MEM) ! source = adjust_address (operands[1], SFmode, 0); ! else if (GET_CODE (operands[1]) == REG || GET_CODE (operands[1]) == SUBREG) ! source = gen_rtx_REG (SFmode, true_regnum (operands[1])); ! else ! source = operands[1]; ! ! /* FP1 and FP2 are the two halves of the TFmode scratch operand. They ! will be single registers in 64-bit mode and register pairs in 32-bit ! mode. SOURCE is loaded into FP1 and zero is loaded into FP2. */ ! regno = REGNO (operands[2]); ! fp1 = gen_rtx_REG (SFmode, regno); ! fp2 = gen_rtx_REG (SFmode, regno + HARD_REGNO_NREGS (regno, DFmode)); ! ! emit_insn (gen_move_insn (fp1, source)); ! emit_insn (gen_move_insn (fp2, gen_rtx_REG (SFmode, 0))); ! emit_insn (gen_rtx_SET (VOIDmode, operands[0], ! gen_rtx_LT (CCmode, fp2, fp1))); ! DONE; }") (define_expand "reload_outcc" ! [(set (match_operand:CC 0 "general_operand" "=z") ! (match_operand:CC 1 "register_operand" "z")) ! (clobber (match_operand:CC 2 "register_operand" "=&d"))] "ISA_HAS_8CC && TARGET_HARD_FLOAT" " { ! /* This is called when we are copying a condition code register out ! to save it somewhere. Operand 0 should be the location we are ! going to save it to. Operand 1 should be the condition code ! register. Operand 2 should be a scratch general purpose register ! created for us by reload. The mips_secondary_reload_class ! function should have told reload that we don't need a scratch ! register if the destination is a general purpose register anyhow. */ ! if (ST_REG_P (true_regnum (operands[0])) ! || GP_REG_P (true_regnum (operands[0])) ! || ! ST_REG_P (true_regnum (operands[1])) ! || ! GP_REG_P (true_regnum (operands[2]))) ! abort (); ! ! /* All we have to do is copy the value from the condition code to ! the data register, which movcc can handle, and then store the ! value into the real final destination. */ ! emit_insn (gen_move_insn (operands[2], operands[1])); ! emit_insn (gen_move_insn (operands[0], operands[2])); ! DONE; }") --- 5786,5824 ---- (set_attr "mode" "SI") (set_attr "length" "8,4,4,8,4,8,4,4,4,4,8,4,8")]) ! ;; Reload condition code registers. reload_incc and reload_outcc ! ;; both handle moves from arbitrary operands into condition code ! ;; registers. reload_incc handles the more common case in which ! ;; a source operand is constrained to be in a condition-code ! ;; register, but has not been allocated to one. ! ;; ! ;; Sometimes, such as in movcc, we have a CCmode destination whose ! ;; constraints do not include 'z'. reload_outcc handles the case ! ;; when such an operand is allocated to a condition-code register. ! ;; ! ;; Note that reloads from a condition code register to some ! ;; other location can be done using ordinary moves. Moving ! ;; into a GPR takes a single movcc, moving elsewhere takes ! ;; two. We can leave these cases to the generic reload code. (define_expand "reload_incc" ! [(set (match_operand:CC 0 "fcc_register_operand" "=z") ! (match_operand:CC 1 "general_operand" "")) (clobber (match_operand:TF 2 "register_operand" "=&f"))] "ISA_HAS_8CC && TARGET_HARD_FLOAT" " { ! mips_emit_fcc_reload (operands[0], operands[1], operands[2]); DONE; }") (define_expand "reload_outcc" ! [(set (match_operand:CC 0 "fcc_register_operand" "=z") ! (match_operand:CC 1 "register_operand" "")) ! (clobber (match_operand:TF 2 "register_operand" "=&f"))] "ISA_HAS_8CC && TARGET_HARD_FLOAT" " { ! mips_emit_fcc_reload (operands[0], operands[1], operands[2]); DONE; }") diff -Nrc3pad gcc-3.2.2/gcc/config/pa/pa-protos.h gcc-3.2.3/gcc/config/pa/pa-protos.h *** gcc-3.2.2/gcc/config/pa/pa-protos.h Thu Jul 11 18:22:02 2002 --- gcc-3.2.3/gcc/config/pa/pa-protos.h Wed Apr 16 23:00:20 2003 *************** extern int cmpib_comparison_operator PAR *** 157,163 **** extern int reloc_needed PARAMS ((tree)); #ifdef RTX_CODE extern rtx function_arg PARAMS ((CUMULATIVE_ARGS *, enum machine_mode, ! tree, int, int)); #endif extern int function_arg_partial_nregs PARAMS ((CUMULATIVE_ARGS *, enum machine_mode, --- 157,163 ---- extern int reloc_needed PARAMS ((tree)); #ifdef RTX_CODE extern rtx function_arg PARAMS ((CUMULATIVE_ARGS *, enum machine_mode, ! tree, int)); #endif extern int function_arg_partial_nregs PARAMS ((CUMULATIVE_ARGS *, enum machine_mode, diff -Nrc3pad gcc-3.2.2/gcc/config/pa/pa.c gcc-3.2.3/gcc/config/pa/pa.c *** gcc-3.2.2/gcc/config/pa/pa.c Sat Feb 1 04:50:32 2003 --- gcc-3.2.3/gcc/config/pa/pa.c Wed Apr 16 23:00:23 2003 *************** output_cbranch (operands, nullify, lengt *** 5159,5171 **** static char buf[100]; int useskip = 0; ! /* A conditional branch to the following instruction (eg the delay slot) is ! asking for a disaster. This can happen when not optimizing. ! In such cases it is safe to emit nothing. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return ""; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ --- 5159,5176 ---- static char buf[100]; int useskip = 0; ! /* A conditional branch to the following instruction (eg the delay slot) ! is asking for a disaster. This can happen when not optimizing and ! when jump optimization fails. ! While it is usually safe to emit nothing, this can fail if the preceding ! instruction is a nullified branch with an empty delay slot and the ! same branch target as this branch. We could check for this but ! jump optimization should eliminate these jumps. It is always ! safe to emit a nop. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return "nop"; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ *************** output_bb (operands, nullify, length, ne *** 5369,5375 **** jump. But be prepared just in case. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return ""; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ --- 5374,5380 ---- jump. But be prepared just in case. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return "nop"; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ *************** output_bvb (operands, nullify, length, n *** 5517,5523 **** jump. But be prepared just in case. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return ""; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ --- 5522,5528 ---- jump. But be prepared just in case. */ if (next_active_insn (JUMP_LABEL (insn)) == next_active_insn (insn)) ! return "nop"; /* If this is a long branch with its delay slot unfilled, set `nullify' as it can nullify the delay slot and save a nop. */ *************** output_millicode_call (insn, call_dest) *** 5926,5935 **** output_asm_insn ("{bl|b,l} .+8,%%r1", xoperands); /* Add %r1 to the offset of our target from the next insn. */ ! output_asm_insn ("addil L%%%0-%1,%%r1", xoperands); ! ASM_OUTPUT_INTERNAL_LABEL (asm_out_file, "L", ! CODE_LABEL_NUMBER (xoperands[1])); ! output_asm_insn ("ldo R%%%0-%1(%%r1),%%r1", xoperands); /* Get the return address into %r31. */ output_asm_insn ("blr 0,%3", xoperands); --- 5931,5949 ---- output_asm_insn ("{bl|b,l} .+8,%%r1", xoperands); /* Add %r1 to the offset of our target from the next insn. */ ! if (TARGET_SOM || !TARGET_GAS) ! { ! output_asm_insn ("addil L%%%0-%1,%%r1", xoperands); ! ASM_OUTPUT_INTERNAL_LABEL (asm_out_file, "L", ! CODE_LABEL_NUMBER (xoperands[1])); ! output_asm_insn ("ldo R%%%0-%1(%%r1),%%r1", xoperands); ! } ! else ! { ! output_asm_insn ("addil L'%0-$PIC_pcrel$0+8,%%r1", xoperands); ! output_asm_insn ("ldo R'%0-$PIC_pcrel$0+12(%%r1),%%r1", ! xoperands); ! } /* Get the return address into %r31. */ output_asm_insn ("blr 0,%3", xoperands); *************** insn_refs_are_delayed (insn) *** 7192,7203 **** ??? We might want to restructure this so that it looks more like other ports. */ rtx ! function_arg (cum, mode, type, named, incoming) CUMULATIVE_ARGS *cum; enum machine_mode mode; tree type; int named ATTRIBUTE_UNUSED; - int incoming; { int max_arg_words = (TARGET_64BIT ? 8 : 4); int fpr_reg_base; --- 7206,7216 ---- ??? We might want to restructure this so that it looks more like other ports. */ rtx ! function_arg (cum, mode, type, named) CUMULATIVE_ARGS *cum; enum machine_mode mode; tree type; int named ATTRIBUTE_UNUSED; { int max_arg_words = (TARGET_64BIT ? 8 : 4); int fpr_reg_base; *************** function_arg (cum, mode, type, named, in *** 7331,7337 **** if (((TARGET_PORTABLE_RUNTIME || TARGET_64BIT || TARGET_ELF32) /* If we are doing soft-float with portable runtime, then there is no need to worry about FP regs. */ ! && ! TARGET_SOFT_FLOAT /* The parameter must be some kind of float, else we can just pass it in integer registers. */ && FLOAT_MODE_P (mode) --- 7344,7350 ---- if (((TARGET_PORTABLE_RUNTIME || TARGET_64BIT || TARGET_ELF32) /* If we are doing soft-float with portable runtime, then there is no need to worry about FP regs. */ ! && !TARGET_SOFT_FLOAT /* The parameter must be some kind of float, else we can just pass it in integer registers. */ && FLOAT_MODE_P (mode) *************** function_arg (cum, mode, type, named, in *** 7340,7353 **** /* libcalls do not need to pass items in both FP and general registers. */ && type != NULL_TREE ! /* All this hair applies to outgoing args only. */ ! && ! incoming) /* Also pass outgoing floating arguments in both registers in indirect calls with the 32 bit ABI and the HP assembler since there is no way to the specify argument locations in static functions. */ ! || (! TARGET_64BIT ! && ! TARGET_GAS ! && ! incoming && cum->indirect && FLOAT_MODE_P (mode))) { --- 7353,7367 ---- /* libcalls do not need to pass items in both FP and general registers. */ && type != NULL_TREE ! /* All this hair applies to "outgoing" args only. This includes ! sibcall arguments setup with FUNCTION_INCOMING_ARG. */ ! && !cum->incoming) /* Also pass outgoing floating arguments in both registers in indirect calls with the 32 bit ABI and the HP assembler since there is no way to the specify argument locations in static functions. */ ! || (!TARGET_64BIT ! && !TARGET_GAS ! && !cum->incoming && cum->indirect && FLOAT_MODE_P (mode))) { diff -Nrc3pad gcc-3.2.2/gcc/config/pa/pa.h gcc-3.2.3/gcc/config/pa/pa.h *** gcc-3.2.2/gcc/config/pa/pa.h Sat Dec 28 23:27:08 2002 --- gcc-3.2.3/gcc/config/pa/pa.h Wed Apr 16 23:00:25 2003 *************** extern struct rtx_def *hppa_pic_save_rtx *** 715,726 **** and about the args processed so far, enough to enable macros such as FUNCTION_ARG to determine where the next arg should go. ! On the HP-PA, this is a single integer, which is a number of words of arguments scanned so far (including the invisible argument, ! if any, which holds the structure-value-address). ! Thus 4 or more means all following args should go on the stack. */ ! struct hppa_args {int words, nargs_prototype, indirect; }; #define CUMULATIVE_ARGS struct hppa_args --- 715,735 ---- and about the args processed so far, enough to enable macros such as FUNCTION_ARG to determine where the next arg should go. ! On the HP-PA, the WORDS field holds the number of words of arguments scanned so far (including the invisible argument, ! if any, which holds the structure-value-address). Thus, 4 or ! more means all following args should go on the stack. ! ! The INCOMING field tracks whether this is an "incoming" or ! "outgoing" argument. ! ! The INDIRECT field indicates whether this is is an indirect ! call or not. ! ! The NARGS_PROTOTYPE field indicates that an argument does not ! have a prototype when it less than or equal to 0. */ ! struct hppa_args {int words, nargs_prototype, incoming, indirect; }; #define CUMULATIVE_ARGS struct hppa_args *************** struct hppa_args {int words, nargs_proto *** 730,735 **** --- 739,745 ---- #define INIT_CUMULATIVE_ARGS(CUM,FNTYPE,LIBNAME,INDIRECT) \ (CUM).words = 0, \ + (CUM).incoming = 0, \ (CUM).indirect = INDIRECT, \ (CUM).nargs_prototype = (FNTYPE && TYPE_ARG_TYPES (FNTYPE) \ ? (list_length (TYPE_ARG_TYPES (FNTYPE)) - 1 \ *************** struct hppa_args {int words, nargs_proto *** 744,749 **** --- 754,760 ---- #define INIT_CUMULATIVE_INCOMING_ARGS(CUM,FNTYPE,IGNORE) \ (CUM).words = 0, \ + (CUM).incoming = 1, \ (CUM).indirect = 0, \ (CUM).nargs_prototype = 1000 *************** struct hppa_args {int words, nargs_proto *** 817,826 **** tempted to try and simply it, but I worry about breaking something. */ #define FUNCTION_ARG(CUM, MODE, TYPE, NAMED) \ ! function_arg (&CUM, MODE, TYPE, NAMED, 0) ! ! #define FUNCTION_INCOMING_ARG(CUM, MODE, TYPE, NAMED) \ ! function_arg (&CUM, MODE, TYPE, NAMED, 1) /* For an arg passed partly in registers and partly in memory, this is the number of registers used. --- 828,834 ---- tempted to try and simply it, but I worry about breaking something. */ #define FUNCTION_ARG(CUM, MODE, TYPE, NAMED) \ ! function_arg (&CUM, MODE, TYPE, NAMED) /* For an arg passed partly in registers and partly in memory, this is the number of registers used. diff -Nrc3pad gcc-3.2.2/gcc/config/pa/pa.md gcc-3.2.3/gcc/config/pa/pa.md *** gcc-3.2.2/gcc/config/pa/pa.md Fri Jan 24 15:51:23 2003 --- gcc-3.2.3/gcc/config/pa/pa.md Fri Feb 7 22:59:30 2003 *************** *** 5681,5692 **** xoperands[0] = operands[0]; xoperands[1] = gen_label_rtx (); ! output_asm_insn (\"{bl|b,l} .+8,%%r1\\n\\taddil L'%l0-%l1,%%r1\", ! xoperands); ! ASM_OUTPUT_INTERNAL_LABEL (asm_out_file, \"L\", ! CODE_LABEL_NUMBER (xoperands[1])); ! output_asm_insn (\"ldo R'%l0-%l1(%%r1),%%r1\\n\\tbv %%r0(%%r1)\", ! xoperands); } else output_asm_insn (\"ldil L'%l0,%%r1\\n\\tbe R'%l0(%%sr4,%%r1)\", operands);; --- 5681,5701 ---- xoperands[0] = operands[0]; xoperands[1] = gen_label_rtx (); ! if (TARGET_SOM || !TARGET_GAS) ! { ! output_asm_insn (\"{bl|b,l} .+8,%%r1\\n\\taddil L'%l0-%l1,%%r1\", ! xoperands); ! ASM_OUTPUT_INTERNAL_LABEL (asm_out_file, \"L\", ! CODE_LABEL_NUMBER (xoperands[1])); ! output_asm_insn (\"ldo R'%l0-%l1(%%r1),%%r1\\n\\tbv %%r0(%%r1)\", ! xoperands); ! } ! else ! { ! output_asm_insn (\"{bl|b,l} .+8,%%r1\", xoperands); ! output_asm_insn (\"addil L'%l0-$PIC_pcrel$0+4,%%r1\", xoperands); ! output_asm_insn (\"ldo R'%l0-$PIC_pcrel$0+8(%%r1),%%r1\", xoperands); ! } } else output_asm_insn (\"ldil L'%l0,%%r1\\n\\tbe R'%l0(%%sr4,%%r1)\", operands);; diff -Nrc3pad gcc-3.2.2/gcc/config/rs6000/rs6000.c gcc-3.2.3/gcc/config/rs6000/rs6000.c *** gcc-3.2.2/gcc/config/rs6000/rs6000.c Thu Jan 23 22:19:42 2003 --- gcc-3.2.3/gcc/config/rs6000/rs6000.c Tue Apr 8 22:03:23 2003 *************** first_reg_to_save () *** 7409,7415 **** if (regs_ever_live[first_reg] && (! call_used_regs[first_reg] || (first_reg == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic == 1) || (DEFAULT_ABI == ABI_DARWIN && flag_pic))))) break; --- 7409,7415 ---- if (regs_ever_live[first_reg] && (! call_used_regs[first_reg] || (first_reg == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic != 0) || (DEFAULT_ABI == ABI_DARWIN && flag_pic))))) break; *************** void *** 8053,8059 **** rs6000_emit_load_toc_table (fromprolog) int fromprolog; { ! rtx dest; dest = gen_rtx_REG (Pmode, RS6000_PIC_OFFSET_TABLE_REGNUM); if (TARGET_ELF && DEFAULT_ABI == ABI_V4 && flag_pic == 1) --- 8053,8059 ---- rs6000_emit_load_toc_table (fromprolog) int fromprolog; { ! rtx dest, insn; dest = gen_rtx_REG (Pmode, RS6000_PIC_OFFSET_TABLE_REGNUM); if (TARGET_ELF && DEFAULT_ABI == ABI_V4 && flag_pic == 1) *************** rs6000_emit_load_toc_table (fromprolog) *** 8061,8068 **** rtx temp = (fromprolog ? gen_rtx_REG (Pmode, LINK_REGISTER_REGNUM) : gen_reg_rtx (Pmode)); ! rs6000_maybe_dead (emit_insn (gen_load_toc_v4_pic_si (temp))); ! rs6000_maybe_dead (emit_move_insn (dest, temp)); } else if (TARGET_ELF && DEFAULT_ABI != ABI_AIX && flag_pic == 2) { --- 8061,8072 ---- rtx temp = (fromprolog ? gen_rtx_REG (Pmode, LINK_REGISTER_REGNUM) : gen_reg_rtx (Pmode)); ! insn = emit_insn (gen_load_toc_v4_pic_si (temp)); ! if (fromprolog) ! rs6000_maybe_dead (insn); ! insn = emit_move_insn (dest, temp); ! if (fromprolog) ! rs6000_maybe_dead (insn); } else if (TARGET_ELF && DEFAULT_ABI != ABI_AIX && flag_pic == 2) { *************** rs6000_emit_load_toc_table (fromprolog) *** 8109,8122 **** ASM_GENERATE_INTERNAL_LABEL (buf, "LCG", reload_toc_labelno++); symF = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (buf)); ! rs6000_maybe_dead (emit_insn (gen_load_toc_v4_PIC_1b (tempLR, ! symF, ! tocsym))); ! rs6000_maybe_dead (emit_move_insn (dest, tempLR)); ! rs6000_maybe_dead (emit_move_insn (temp0, ! gen_rtx_MEM (Pmode, dest))); } ! rs6000_maybe_dead (emit_insn (gen_addsi3 (dest, temp0, dest))); } else if (TARGET_ELF && !TARGET_AIX && flag_pic == 0 && TARGET_MINIMAL_TOC) { --- 8113,8125 ---- ASM_GENERATE_INTERNAL_LABEL (buf, "LCG", reload_toc_labelno++); symF = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (buf)); ! emit_insn (gen_load_toc_v4_PIC_1b (tempLR, symF, tocsym)); ! emit_move_insn (dest, tempLR); ! emit_move_insn (temp0, gen_rtx_MEM (Pmode, dest)); } ! insn = emit_insn (gen_addsi3 (dest, temp0, dest)); ! if (fromprolog) ! rs6000_maybe_dead (insn); } else if (TARGET_ELF && !TARGET_AIX && flag_pic == 0 && TARGET_MINIMAL_TOC) { *************** rs6000_emit_load_toc_table (fromprolog) *** 8126,8140 **** ASM_GENERATE_INTERNAL_LABEL (buf, "LCTOC", 1); realsym = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (buf)); ! rs6000_maybe_dead (emit_insn (gen_elf_high (dest, realsym))); ! rs6000_maybe_dead (emit_insn (gen_elf_low (dest, dest, realsym))); } else if (DEFAULT_ABI == ABI_AIX) { if (TARGET_32BIT) ! rs6000_maybe_dead (emit_insn (gen_load_toc_aix_si (dest))); else ! rs6000_maybe_dead (emit_insn (gen_load_toc_aix_di (dest))); } else abort (); --- 8129,8149 ---- ASM_GENERATE_INTERNAL_LABEL (buf, "LCTOC", 1); realsym = gen_rtx_SYMBOL_REF (Pmode, ggc_strdup (buf)); ! insn = emit_insn (gen_elf_high (dest, realsym)); ! if (fromprolog) ! rs6000_maybe_dead (insn); ! insn = emit_insn (gen_elf_low (dest, dest, realsym)); ! if (fromprolog) ! rs6000_maybe_dead (insn); } else if (DEFAULT_ABI == ABI_AIX) { if (TARGET_32BIT) ! insn = emit_insn (gen_load_toc_aix_si (dest)); else ! insn = emit_insn (gen_load_toc_aix_di (dest)); ! if (fromprolog) ! rs6000_maybe_dead (insn); } else abort (); *************** rs6000_emit_prologue () *** 8793,8799 **** if ((regs_ever_live[info->first_gp_reg_save+i] && ! call_used_regs[info->first_gp_reg_save+i]) || (i+info->first_gp_reg_save == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic == 1) || (DEFAULT_ABI == ABI_DARWIN && flag_pic)))) { rtx addr, reg, mem; --- 8802,8808 ---- if ((regs_ever_live[info->first_gp_reg_save+i] && ! call_used_regs[info->first_gp_reg_save+i]) || (i+info->first_gp_reg_save == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic != 0) || (DEFAULT_ABI == ABI_DARWIN && flag_pic)))) { rtx addr, reg, mem; *************** rs6000_emit_prologue () *** 8889,8895 **** /* Set frame pointer, if needed. */ if (frame_pointer_needed) { ! insn = emit_move_insn (gen_rtx_REG (reg_mode, FRAME_POINTER_REGNUM), sp_reg_rtx); RTX_FRAME_RELATED_P (insn) = 1; } --- 8898,8904 ---- /* Set frame pointer, if needed. */ if (frame_pointer_needed) { ! insn = emit_move_insn (gen_rtx_REG (Pmode, FRAME_POINTER_REGNUM), sp_reg_rtx); RTX_FRAME_RELATED_P (insn) = 1; } *************** rs6000_emit_epilogue (sibcall) *** 9179,9185 **** if ((regs_ever_live[info->first_gp_reg_save+i] && ! call_used_regs[info->first_gp_reg_save+i]) || (i+info->first_gp_reg_save == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic == 1) || (DEFAULT_ABI == ABI_DARWIN && flag_pic)))) { rtx addr = gen_rtx_PLUS (Pmode, frame_reg_rtx, --- 9188,9194 ---- if ((regs_ever_live[info->first_gp_reg_save+i] && ! call_used_regs[info->first_gp_reg_save+i]) || (i+info->first_gp_reg_save == RS6000_PIC_OFFSET_TABLE_REGNUM ! && ((DEFAULT_ABI == ABI_V4 && flag_pic != 0) || (DEFAULT_ABI == ABI_DARWIN && flag_pic)))) { rtx addr = gen_rtx_PLUS (Pmode, frame_reg_rtx, diff -Nrc3pad gcc-3.2.2/gcc/config/rs6000/rs6000.h gcc-3.2.3/gcc/config/rs6000/rs6000.h *** gcc-3.2.2/gcc/config/rs6000/rs6000.h Thu Aug 8 17:52:40 2002 --- gcc-3.2.3/gcc/config/rs6000/rs6000.h Sat Mar 29 12:39:20 2003 *************** *** 1,6 **** /* Definitions of target machine for GNU compiler, for IBM RS/6000. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, ! 2000, 2001, 2002 Free Software Foundation, Inc. Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) This file is part of GNU CC. --- 1,6 ---- /* Definitions of target machine for GNU compiler, for IBM RS/6000. Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, ! 2000, 2001, 2002, 2003 Free Software Foundation, Inc. Contributed by Richard Kenner (kenner@vlsi1.ultra.nyu.edu) This file is part of GNU CC. *************** extern int rs6000_altivec_abi; *** 962,967 **** --- 962,971 ---- = call_really_used_regs[i] = 1; \ if (DEFAULT_ABI == ABI_V4 \ && PIC_OFFSET_TABLE_REGNUM != INVALID_REGNUM \ + && flag_pic == 2) \ + fixed_regs[RS6000_PIC_OFFSET_TABLE_REGNUM] = 1; \ + if (DEFAULT_ABI == ABI_V4 \ + && PIC_OFFSET_TABLE_REGNUM != INVALID_REGNUM \ && flag_pic == 1) \ fixed_regs[RS6000_PIC_OFFSET_TABLE_REGNUM] \ = call_used_regs[RS6000_PIC_OFFSET_TABLE_REGNUM] \ *************** typedef struct rs6000_stack { *** 1539,1558 **** as seen by the caller. On RS/6000, this is r3, fp1, and v2 (for AltiVec). */ ! #define FUNCTION_VALUE_REGNO_P(N) ((N) == GP_ARG_RETURN \ ! || ((N) == FP_ARG_RETURN) \ ! || (TARGET_ALTIVEC && \ ! (N) == ALTIVEC_ARG_RETURN)) /* 1 if N is a possible register number for function argument passing. On RS/6000, these are r3-r10 and fp1-fp13. On AltiVec, v2 - v13 are used for passing vectors. */ #define FUNCTION_ARG_REGNO_P(N) \ ! (((unsigned)((N) - GP_ARG_MIN_REG) < (unsigned)(GP_ARG_NUM_REG)) \ ! || (TARGET_ALTIVEC && \ ! (unsigned)((N) - ALTIVEC_ARG_MIN_REG) < (unsigned)(ALTIVEC_ARG_NUM_REG)) \ ! || ((unsigned)((N) - FP_ARG_MIN_REG) < (unsigned)(FP_ARG_NUM_REG))) ! /* A C structure for machine-specific, per-function data. This is added to the cfun structure. */ --- 1543,1562 ---- as seen by the caller. On RS/6000, this is r3, fp1, and v2 (for AltiVec). */ ! #define FUNCTION_VALUE_REGNO_P(N) \ ! ((N) == GP_ARG_RETURN \ ! || ((N) == FP_ARG_RETURN && TARGET_HARD_FLOAT) \ ! || ((N) == ALTIVEC_ARG_RETURN && TARGET_ALTIVEC)) /* 1 if N is a possible register number for function argument passing. On RS/6000, these are r3-r10 and fp1-fp13. On AltiVec, v2 - v13 are used for passing vectors. */ #define FUNCTION_ARG_REGNO_P(N) \ ! ((unsigned) (N) - GP_ARG_MIN_REG < GP_ARG_NUM_REG \ ! || ((unsigned) (N) - ALTIVEC_ARG_MIN_REG < ALTIVEC_ARG_NUM_REG \ ! && TARGET_ALTIVEC) \ ! || ((unsigned) (N) - FP_ARG_MIN_REG < FP_ARG_NUM_REG \ ! && TARGET_HARD_FLOAT)) /* A C structure for machine-specific, per-function data. This is added to the cfun structure. */ diff -Nrc3pad gcc-3.2.2/gcc/config/rs6000/rs6000.md gcc-3.2.3/gcc/config/rs6000/rs6000.md *** gcc-3.2.2/gcc/config/rs6000/rs6000.md Tue Nov 26 15:59:58 2002 --- gcc-3.2.3/gcc/config/rs6000/rs6000.md Thu Feb 27 02:08:01 2003 *************** *** 8439,8444 **** --- 8439,8470 ---- operands[5] = GEN_INT (CONST_DOUBLE_LOW (operands[1])); }") + (define_split + [(set (match_operand:TI 0 "gpc_reg_operand" "") + (match_operand:TI 1 "const_double_operand" ""))] + "TARGET_POWERPC64" + [(set (match_dup 2) (match_dup 4)) + (set (match_dup 3) (match_dup 5))] + " + { + operands[2] = operand_subword_force (operands[0], WORDS_BIG_ENDIAN == 0, + TImode); + operands[3] = operand_subword_force (operands[0], WORDS_BIG_ENDIAN != 0, + TImode); + if (GET_CODE (operands[1]) == CONST_DOUBLE) + { + operands[4] = GEN_INT (CONST_DOUBLE_HIGH (operands[1])); + operands[5] = GEN_INT (CONST_DOUBLE_LOW (operands[1])); + } + else if (GET_CODE (operands[1]) == CONST_INT) + { + operands[4] = GEN_INT (- (INTVAL (operands[1]) < 0)); + operands[5] = operands[1]; + } + else + FAIL; + }") + (define_insn "*movdi_internal64" [(set (match_operand:DI 0 "nonimmediate_operand" "=r,r,m,r,r,r,r,f,f,m,r,*h,*h") (match_operand:DI 1 "input_operand" "r,m,r,I,L,nF,R,f,m,f,*h,r,0"))] diff -Nrc3pad gcc-3.2.2/gcc/config/sparc/sparc.h gcc-3.2.3/gcc/config/sparc/sparc.h *** gcc-3.2.2/gcc/config/sparc/sparc.h Mon Jun 24 16:50:44 2002 --- gcc-3.2.3/gcc/config/sparc/sparc.h Fri Mar 21 10:20:50 2003 *************** do { \ *** 2203,2208 **** --- 2203,2210 ---- If you change this, execute "rm explow.o recog.o reload.o". */ + #define SYMBOLIC_CONST(X) symbolic_operand (X, VOIDmode) + #define RTX_OK_FOR_BASE_P(X) \ ((GET_CODE (X) == REG && REG_OK_FOR_BASE_P (X)) \ || (GET_CODE (X) == SUBREG \ *************** do { \ *** 2236,2241 **** --- 2238,2245 ---- && GET_CODE (op1) != REG \ && GET_CODE (op1) != LO_SUM \ && GET_CODE (op1) != MEM \ + && (! SYMBOLIC_CONST (op1) \ + || MODE == Pmode) \ && (GET_CODE (op1) != CONST_INT \ || SMALL_INT (op1))) \ goto ADDR; \ *************** do { \ *** 2323,2328 **** --- 2327,2360 ---- else if (GET_CODE (X) == CONST_INT && SMALL_INT (X)) \ goto ADDR; \ } + + /* Go to LABEL if ADDR (a legitimate address expression) + has an effect that depends on the machine mode it is used for. + + In PIC mode, + + (mem:HI [%l7+a]) + + is not equivalent to + + (mem:QI [%l7+a]) (mem:QI [%l7+a+1]) + + because [%l7+a+1] is interpreted as the address of (a+1). */ + + #define GO_IF_MODE_DEPENDENT_ADDRESS(ADDR, LABEL) \ + { \ + if (flag_pic == 1) \ + { \ + if (GET_CODE (ADDR) == PLUS) \ + { \ + rtx op0 = XEXP (ADDR, 0); \ + rtx op1 = XEXP (ADDR, 1); \ + if (op0 == pic_offset_table_rtx \ + && SYMBOLIC_CONST (op1)) \ + goto LABEL; \ + } \ + } \ + } /* Try machine-dependent ways of modifying an illegitimate address to be legitimate. If we find one, return the new, valid address. *************** do { *** 2400,2411 **** } \ /* ??? 64-bit reloads. */ \ } while (0) - - /* Go to LABEL if ADDR (a legitimate address expression) - has an effect that depends on the machine mode it is used for. - On the SPARC this is never true. */ - - #define GO_IF_MODE_DEPENDENT_ADDRESS(ADDR,LABEL) /* If we are referencing a function make the SYMBOL_REF special. In the Embedded Medium/Anywhere code model, %g4 points to the data segment --- 2432,2437 ---- diff -Nrc3pad gcc-3.2.2/gcc/config/sparc/sparc.md gcc-3.2.3/gcc/config/sparc/sparc.md *** gcc-3.2.2/gcc/config/sparc/sparc.md Wed Oct 2 03:47:05 2002 --- gcc-3.2.3/gcc/config/sparc/sparc.md Fri Mar 28 09:24:08 2003 *************** *** 2531,2539 **** (define_insn "*movdi_insn_sp32_v9" [(set (match_operand:DI 0 "nonimmediate_operand" ! "=T,o,T,U,o,r,r,r,?T,?f,?f,?o,?f,?e,?e,?W") (match_operand:DI 1 "input_operand" ! " J,J,U,T,r,o,i,r, f, T, o, f, f, e, W, e"))] "! TARGET_ARCH64 && TARGET_V9 && (GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM)" "@ --- 2531,2539 ---- (define_insn "*movdi_insn_sp32_v9" [(set (match_operand:DI 0 "nonimmediate_operand" ! "=T,o,T,U,o,r,r,r,?T,?f,?f,?o,?e,?e,?W") (match_operand:DI 1 "input_operand" ! " J,J,U,T,r,o,i,r, f, T, o, f, e, W, e"))] "! TARGET_ARCH64 && TARGET_V9 && (GET_CODE (operands[0]) != MEM || GET_CODE (operands[1]) != MEM)" "@ *************** *** 2549,2561 **** ldd\\t%1, %0 # # - # fmovd\\t%1, %0 ldd\\t%1, %0 std\\t%1, %0" ! [(set_attr "type" "store,store,store,load,*,*,*,*,fpstore,fpload,*,*,*,fpmove,fpload,fpstore") ! (set_attr "length" "*,2,*,*,2,2,2,2,*,*,2,2,2,*,*,*") ! (set_attr "fptype" "*,*,*,*,*,*,*,*,*,*,*,*,*,double,*,*")]) (define_insn "*movdi_insn_sp32" [(set (match_operand:DI 0 "nonimmediate_operand" --- 2549,2560 ---- ldd\\t%1, %0 # # fmovd\\t%1, %0 ldd\\t%1, %0 std\\t%1, %0" ! [(set_attr "type" "store,store,store,load,*,*,*,*,fpstore,fpload,*,*,fpmove,fpload,fpstore") ! (set_attr "length" "*,2,*,*,2,2,2,2,*,*,2,2,*,*,*") ! (set_attr "fptype" "*,*,*,*,*,*,*,*,*,*,*,*,double,*,*")]) (define_insn "*movdi_insn_sp32" [(set (match_operand:DI 0 "nonimmediate_operand" *************** *** 2899,2905 **** (define_split [(set (match_operand:DI 0 "register_operand" "") (match_operand:DI 1 "register_operand" ""))] ! "! TARGET_ARCH64 && reload_completed" [(clobber (const_int 0))] " { --- 2898,2911 ---- (define_split [(set (match_operand:DI 0 "register_operand" "") (match_operand:DI 1 "register_operand" ""))] ! "reload_completed ! && (! TARGET_V9 ! || (! TARGET_ARCH64 ! && ((GET_CODE (operands[0]) == REG ! && REGNO (operands[0]) < 32) ! || (GET_CODE (operands[0]) == SUBREG ! && GET_CODE (SUBREG_REG (operands[0])) == REG ! && REGNO (SUBREG_REG (operands[0])) < 32))))" [(clobber (const_int 0))] " { *************** *** 7951,7957 **** == INSN_ADDRESSES (INSN_UID (insn)))) return \"b\\t%l0%#\"; else ! return TARGET_V9 ? \"ba,pt%*\\t%%xcc, %l0%(\" : \"b%*\\t%l0%(\"; }" [(set_attr "type" "uncond_branch")]) --- 7957,7963 ---- == INSN_ADDRESSES (INSN_UID (insn)))) return \"b\\t%l0%#\"; else ! return TARGET_V9 ? \"ba%*,pt\\t%%xcc, %l0%(\" : \"b%*\\t%l0%(\"; }" [(set_attr "type" "uncond_branch")]) *************** *** 8669,8675 **** && mems_ok_for_ldd_peep (operands[0], operands[1], NULL_RTX)" [(set (match_dup 0) (const_int 0))] ! "operands[0] = change_address (operands[0], DImode, NULL);") (define_peephole2 [(set (match_operand:SI 0 "memory_operand" "") --- 8675,8681 ---- && mems_ok_for_ldd_peep (operands[0], operands[1], NULL_RTX)" [(set (match_dup 0) (const_int 0))] ! "operands[0] = widen_memory_access (operands[0], DImode, 0);") (define_peephole2 [(set (match_operand:SI 0 "memory_operand" "") *************** *** 8680,8686 **** && mems_ok_for_ldd_peep (operands[1], operands[0], NULL_RTX)" [(set (match_dup 1) (const_int 0))] ! "operands[1] = change_address (operands[1], DImode, NULL);") (define_peephole2 [(set (match_operand:SI 0 "register_operand" "") --- 8686,8692 ---- && mems_ok_for_ldd_peep (operands[1], operands[0], NULL_RTX)" [(set (match_dup 1) (const_int 0))] ! "operands[1] = widen_memory_access (operands[1], DImode, 0);") (define_peephole2 [(set (match_operand:SI 0 "register_operand" "") *************** *** 8691,8697 **** && mems_ok_for_ldd_peep (operands[1], operands[3], operands[0])" [(set (match_dup 0) (match_dup 1))] ! "operands[1] = change_address (operands[1], DImode, NULL); operands[0] = gen_rtx_REG (DImode, REGNO (operands[0]));") (define_peephole2 --- 8697,8703 ---- && mems_ok_for_ldd_peep (operands[1], operands[3], operands[0])" [(set (match_dup 0) (match_dup 1))] ! "operands[1] = widen_memory_access (operands[1], DImode, 0); operands[0] = gen_rtx_REG (DImode, REGNO (operands[0]));") (define_peephole2 *************** *** 8703,8709 **** && mems_ok_for_ldd_peep (operands[0], operands[2], NULL_RTX)" [(set (match_dup 0) (match_dup 1))] ! "operands[0] = change_address (operands[0], DImode, NULL); operands[1] = gen_rtx_REG (DImode, REGNO (operands[1]));") (define_peephole2 --- 8709,8715 ---- && mems_ok_for_ldd_peep (operands[0], operands[2], NULL_RTX)" [(set (match_dup 0) (match_dup 1))] ! "operands[0] = widen_memory_access (operands[0], DImode, 0); operands[1] = gen_rtx_REG (DImode, REGNO (operands[1]));") (define_peephole2 *************** *** 8715,8721 **** && mems_ok_for_ldd_peep (operands[1], operands[3], operands[0])" [(set (match_dup 0) (match_dup 1))] ! "operands[1] = change_address (operands[1], DFmode, NULL); operands[0] = gen_rtx_REG (DFmode, REGNO (operands[0]));") (define_peephole2 --- 8721,8727 ---- && mems_ok_for_ldd_peep (operands[1], operands[3], operands[0])" [(set (match_dup 0) (match_dup 1))] ! "operands[1] = widen_memory_access (operands[1], DFmode, 0); operands[0] = gen_rtx_REG (DFmode, REGNO (operands[0]));") (define_peephole2 *************** *** 8727,8733 **** && mems_ok_for_ldd_peep (operands[0], operands[2], NULL_RTX)" [(set (match_dup 0) (match_dup 1))] ! "operands[0] = change_address (operands[0], DFmode, NULL); operands[1] = gen_rtx_REG (DFmode, REGNO (operands[1]));") (define_peephole2 --- 8733,8739 ---- && mems_ok_for_ldd_peep (operands[0], operands[2], NULL_RTX)" [(set (match_dup 0) (match_dup 1))] ! "operands[0] = widen_memory_access (operands[0], DFmode, 0); operands[1] = gen_rtx_REG (DFmode, REGNO (operands[1]));") (define_peephole2 *************** *** 8739,8745 **** && mems_ok_for_ldd_peep (operands[3], operands[1], operands[0])" [(set (match_dup 2) (match_dup 3))] ! "operands[3] = change_address (operands[3], DImode, NULL); operands[2] = gen_rtx_REG (DImode, REGNO (operands[2]));") (define_peephole2 --- 8745,8751 ---- && mems_ok_for_ldd_peep (operands[3], operands[1], operands[0])" [(set (match_dup 2) (match_dup 3))] ! "operands[3] = widen_memory_access (operands[3], DImode, 0); operands[2] = gen_rtx_REG (DImode, REGNO (operands[2]));") (define_peephole2 *************** *** 8751,8757 **** && mems_ok_for_ldd_peep (operands[2], operands[0], NULL_RTX)" [(set (match_dup 2) (match_dup 3))] ! "operands[2] = change_address (operands[2], DImode, NULL); operands[3] = gen_rtx_REG (DImode, REGNO (operands[3])); ") --- 8757,8763 ---- && mems_ok_for_ldd_peep (operands[2], operands[0], NULL_RTX)" [(set (match_dup 2) (match_dup 3))] ! "operands[2] = widen_memory_access (operands[2], DImode, 0); operands[3] = gen_rtx_REG (DImode, REGNO (operands[3])); ") *************** *** 8764,8770 **** && mems_ok_for_ldd_peep (operands[3], operands[1], operands[0])" [(set (match_dup 2) (match_dup 3))] ! "operands[3] = change_address (operands[3], DFmode, NULL); operands[2] = gen_rtx_REG (DFmode, REGNO (operands[2]));") (define_peephole2 --- 8770,8776 ---- && mems_ok_for_ldd_peep (operands[3], operands[1], operands[0])" [(set (match_dup 2) (match_dup 3))] ! "operands[3] = widen_memory_access (operands[3], DFmode, 0); operands[2] = gen_rtx_REG (DFmode, REGNO (operands[2]));") (define_peephole2 *************** *** 8776,8782 **** && mems_ok_for_ldd_peep (operands[2], operands[0], NULL_RTX)" [(set (match_dup 2) (match_dup 3))] ! "operands[2] = change_address (operands[2], DFmode, NULL); operands[3] = gen_rtx_REG (DFmode, REGNO (operands[3]));") ;; Optimize the case of following a reg-reg move with a test --- 8782,8788 ---- && mems_ok_for_ldd_peep (operands[2], operands[0], NULL_RTX)" [(set (match_dup 2) (match_dup 3))] ! "operands[2] = widen_memory_access (operands[2], DFmode, 0); operands[3] = gen_rtx_REG (DFmode, REGNO (operands[3]));") ;; Optimize the case of following a reg-reg move with a test diff -Nrc3pad gcc-3.2.2/gcc/config/xtensa/xtensa.c gcc-3.2.3/gcc/config/xtensa/xtensa.c *** gcc-3.2.2/gcc/config/xtensa/xtensa.c Mon Dec 2 21:30:12 2002 --- gcc-3.2.3/gcc/config/xtensa/xtensa.c Tue Feb 11 22:18:53 2003 *************** xtensa_reorg (first) *** 2245,2252 **** continue; pat = PATTERN (insn); ! if (GET_CODE (pat) == UNSPEC_VOLATILE ! && (XINT (pat, 1) == UNSPECV_SET_FP)) { set_frame_ptr_insn = insn; break; --- 2245,2253 ---- continue; pat = PATTERN (insn); ! if (GET_CODE (pat) == SET ! && GET_CODE (SET_SRC (pat)) == UNSPEC_VOLATILE ! && (XINT (SET_SRC (pat), 1) == UNSPECV_SET_FP)) { set_frame_ptr_insn = insn; break; *************** order_regs_for_local_alloc () *** 2729,2734 **** --- 2730,2739 ---- for (i = 0; i < num_arg_regs; i++) reg_alloc_order[nxt++] = GP_ARG_FIRST + i; + /* list the coprocessor registers in order */ + for (i = 0; i < BR_REG_NUM; i++) + reg_alloc_order[nxt++] = BR_REG_FIRST + i; + /* list the FP registers in order for now */ for (i = 0; i < 16; i++) reg_alloc_order[nxt++] = FP_REG_FIRST + i; *************** order_regs_for_local_alloc () *** 2738,2747 **** reg_alloc_order[nxt++] = 1; /* a1 = stack pointer */ reg_alloc_order[nxt++] = 16; /* pseudo frame pointer */ reg_alloc_order[nxt++] = 17; /* pseudo arg pointer */ - - /* list the coprocessor registers in order */ - for (i = 0; i < BR_REG_NUM; i++) - reg_alloc_order[nxt++] = BR_REG_FIRST + i; reg_alloc_order[nxt++] = ACC_REG_FIRST; /* MAC16 accumulator */ } --- 2743,2748 ---- diff -Nrc3pad gcc-3.2.2/gcc/config/xtensa/xtensa.h gcc-3.2.3/gcc/config/xtensa/xtensa.h *** gcc-3.2.2/gcc/config/xtensa/xtensa.h Mon Dec 2 21:30:11 2002 --- gcc-3.2.3/gcc/config/xtensa/xtensa.h Mon Apr 14 15:31:30 2003 *************** extern unsigned xtensa_current_frame_siz *** 251,257 **** /* Size in bits of various types on the target machine. */ #define INT_TYPE_SIZE 32 - #define MAX_INT_TYPE_SIZE 32 #define SHORT_TYPE_SIZE 16 #define LONG_TYPE_SIZE 32 #define MAX_LONG_TYPE_SIZE 32 --- 251,256 ---- *************** extern unsigned xtensa_current_frame_siz *** 360,366 **** 0 - 15 AR[0] - AR[15] 16 FRAME_POINTER (fake = initial sp) 17 ARG_POINTER (fake = initial sp + framesize) - 18 LOOP_COUNT (loop count special register) 18 BR[0] for floating-point CC 19 - 34 FR[0] - FR[15] 35 MAC16 accumulator */ --- 359,364 ---- *************** extern unsigned xtensa_current_frame_siz *** 409,418 **** have been exhausted. */ #define REG_ALLOC_ORDER \ ! { 8, 9, 10, 11, 12, 13, 14, 15, 7, 6, 5, 4, 3, 2, 19, \ ! 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, \ 0, 1, 16, 17, \ ! 36, \ } #define ORDER_REGS_FOR_LOCAL_ALLOC order_regs_for_local_alloc () --- 407,417 ---- have been exhausted. */ #define REG_ALLOC_ORDER \ ! { 8, 9, 10, 11, 12, 13, 14, 15, 7, 6, 5, 4, 3, 2, \ ! 18, \ ! 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, \ 0, 1, 16, 17, \ ! 35, \ } #define ORDER_REGS_FOR_LOCAL_ALLOC order_regs_for_local_alloc () *************** extern int leaf_function; *** 439,449 **** #define GP_REG_LAST 17 #define GP_REG_NUM (GP_REG_LAST - GP_REG_FIRST + 1) - /* Special registers */ - #define SPEC_REG_FIRST 18 - #define SPEC_REG_LAST 18 - #define SPEC_REG_NUM (SPEC_REG_LAST - SPEC_REG_FIRST + 1) - /* Coprocessor registers */ #define BR_REG_FIRST 18 #define BR_REG_LAST 18 --- 438,443 ---- *************** extern char xtensa_hard_regno_mode_ok[][ *** 488,496 **** == (GET_MODE_CLASS (MODE2) == MODE_FLOAT || \ GET_MODE_CLASS (MODE2) == MODE_COMPLEX_FLOAT)) - /* Register to use for LCOUNT special register. */ - #define COUNT_REGISTER_REGNUM (SPEC_REG_FIRST + 0) - /* Register to use for pushing function arguments. */ #define STACK_POINTER_REGNUM (GP_REG_FIRST + 1) --- 482,487 ---- *************** typedef struct xtensa_args { *** 1271,1282 **** to contain offsets from the address of the table. Do not define this if the table should contain absolute addresses. */ /* #define CASE_VECTOR_PC_RELATIVE */ - - /* Specify the tree operation to be used to convert reals to integers. */ - #define IMPLICIT_FIX_EXPR FIX_ROUND_EXPR - - /* This is the kind of divide that is easiest to do in the general case. */ - #define EASY_DIV_EXPR TRUNC_DIV_EXPR /* Define this as 1 if 'char' should by default be signed; else as 0. */ #define DEFAULT_SIGNED_CHAR 0 --- 1262,1267 ---- diff -Nrc3pad gcc-3.2.2/gcc/config/xtensa/xtensa.md gcc-3.2.3/gcc/config/xtensa/xtensa.md *** gcc-3.2.2/gcc/config/xtensa/xtensa.md Fri Nov 22 19:27:42 2002 --- gcc-3.2.3/gcc/config/xtensa/xtensa.md Wed Mar 12 21:11:40 2003 *************** *** 97,102 **** --- 97,103 ---- "" " { + rtx srclo; rtx dstlo = gen_lowpart (SImode, operands[0]); rtx src1lo = gen_lowpart (SImode, operands[1]); rtx src2lo = gen_lowpart (SImode, operands[2]); *************** *** 105,113 **** rtx src1hi = gen_highpart (SImode, operands[1]); rtx src2hi = gen_highpart (SImode, operands[2]); emit_insn (gen_addsi3 (dstlo, src1lo, src2lo)); emit_insn (gen_addsi3 (dsthi, src1hi, src2hi)); ! emit_insn (gen_adddi_carry (dsthi, dstlo, src2lo)); DONE; }") --- 106,126 ---- rtx src1hi = gen_highpart (SImode, operands[1]); rtx src2hi = gen_highpart (SImode, operands[2]); + /* Either source can be used for overflow checking, as long as it's + not clobbered by the first addition. */ + if (!rtx_equal_p (dstlo, src1lo)) + srclo = src1lo; + else if (!rtx_equal_p (dstlo, src2lo)) + srclo = src2lo; + else + { + srclo = gen_reg_rtx (SImode); + emit_move_insn (srclo, src1lo); + } + emit_insn (gen_addsi3 (dstlo, src1lo, src2lo)); emit_insn (gen_addsi3 (dsthi, src1hi, src2hi)); ! emit_insn (gen_adddi_carry (dsthi, dstlo, srclo)); DONE; }") *************** *** 209,217 **** rtx src1hi = gen_highpart (SImode, operands[1]); rtx src2hi = gen_highpart (SImode, operands[2]); - emit_insn (gen_subsi3 (dstlo, src1lo, src2lo)); emit_insn (gen_subsi3 (dsthi, src1hi, src2hi)); emit_insn (gen_subdi_carry (dsthi, src1lo, src2lo)); DONE; }") --- 222,230 ---- rtx src1hi = gen_highpart (SImode, operands[1]); rtx src2hi = gen_highpart (SImode, operands[2]); emit_insn (gen_subsi3 (dsthi, src1hi, src2hi)); emit_insn (gen_subdi_carry (dsthi, src1lo, src2lo)); + emit_insn (gen_subsi3 (dstlo, src1lo, src2lo)); DONE; }") *************** *** 2392,2398 **** ;; to set up the frame pointer. (define_insn "set_frame_ptr" ! [(unspec_volatile [(const_int 0)] UNSPECV_SET_FP)] "" "* { --- 2405,2411 ---- ;; to set up the frame pointer. (define_insn "set_frame_ptr" ! [(set (reg:SI A7_REG) (unspec_volatile [(const_int 0)] UNSPECV_SET_FP))] "" "* { *************** *** 2406,2412 **** ;; Post-reload splitter to remove fp assignment when it's not needed. (define_split ! [(unspec_volatile [(const_int 0)] UNSPECV_SET_FP)] "reload_completed && !frame_pointer_needed" [(unspec [(const_int 0)] UNSPEC_NOP)] "") --- 2419,2425 ---- ;; Post-reload splitter to remove fp assignment when it's not needed. (define_split ! [(set (reg:SI A7_REG) (unspec_volatile [(const_int 0)] UNSPECV_SET_FP))] "reload_completed && !frame_pointer_needed" [(unspec [(const_int 0)] UNSPEC_NOP)] "") diff -Nrc3pad gcc-3.2.2/gcc/config.gcc gcc-3.2.3/gcc/config.gcc *** gcc-3.2.2/gcc/config.gcc Thu Jan 30 14:03:42 2003 --- gcc-3.2.3/gcc/config.gcc Fri Feb 28 18:38:19 2003 *************** m68k-*-linux*) # Motorola m68k's runnin *** 2090,2096 **** # aka the GNU/Linux C library 6. tm_file=m68k/linux.h tmake_file="t-slibgcc-elf-ver t-linux m68k/t-linux" ! extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o" float_format=m68k gnu_ld=yes ;; --- 2090,2096 ---- # aka the GNU/Linux C library 6. tm_file=m68k/linux.h tmake_file="t-slibgcc-elf-ver t-linux m68k/t-linux" ! extra_parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o" float_format=m68k gnu_ld=yes ;; *************** xtensa-*-elf*) *** 3429,3435 **** ;; xtensa-*-linux*) tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h xtensa/linux.h" ! tmake_file="t-linux xtensa/t-xtensa" extra_parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o" gas=yes gnu_ld=yes ;; --- 3429,3435 ---- ;; xtensa-*-linux*) tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h xtensa/linux.h" ! tmake_file="t-slibgcc-elf-ver t-linux xtensa/t-xtensa" extra_parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o" gas=yes gnu_ld=yes ;; diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.1 gcc-3.2.3/gcc/doc/cpp.1 *** gcc-3.2.2/gcc/doc/cpp.1 Wed Feb 5 03:13:55 2003 --- gcc-3.2.3/gcc/doc/cpp.1 Tue Apr 22 07:07:27 2003 *************** *** 1,5 **** .\" Automatically generated by Pod::Man version 1.15 ! .\" Wed Feb 5 03:13:55 2003 .\" .\" Standard preamble: .\" ====================================================================== --- 1,5 ---- .\" Automatically generated by Pod::Man version 1.15 ! .\" Tue Apr 22 07:07:27 2003 .\" .\" Standard preamble: .\" ====================================================================== *************** *** 138,144 **** .\" ====================================================================== .\" .IX Title "CPP 1" ! .TH CPP 1 "gcc-3.2.2" "2003-02-05" "GNU" .UC .SH "NAME" cpp \- The C Preprocessor --- 138,144 ---- .\" ====================================================================== .\" .IX Title "CPP 1" ! .TH CPP 1 "gcc-3.2.3" "2003-04-22" "GNU" .UC .SH "NAME" cpp \- The C Preprocessor diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info gcc-3.2.3/gcc/doc/cpp.info *** gcc-3.2.2/gcc/doc/cpp.info Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info Tue Apr 22 07:07:10 2003 *************** *** 0 **** --- 1,86 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + Indirect: + cpp.info-1: 191 + cpp.info-2: 49827 + cpp.info-3: 96680 + cpp.info-4: 142535 + cpp.info-5: 190066 +  + Tag Table: + (Indirect) + Node: Top191 + Node: Overview2796 + Node: Initial processing5164 + Node: Tokenization11621 + Ref: Tokenization-Footnote-118792 + Node: The preprocessing language18903 + Node: Header Files21776 + Node: Include Syntax23654 + Node: Include Operation25156 + Node: Search Path27052 + Node: Once-Only Headers30129 + Node: Computed Includes31783 + Node: Wrapper Headers34922 + Node: System Headers37341 + Node: Macros39386 + Node: Object-like Macros40486 + Node: Function-like Macros44072 + Node: Macro Arguments45682 + Node: Stringification49827 + Node: Concatenation53028 + Node: Variadic Macros56142 + Node: Predefined Macros60932 + Node: Standard Predefined Macros61515 + Node: Common Predefined Macros66795 + Node: System-specific Predefined Macros73375 + Node: C++ Named Operators75387 + Node: Undefining and Redefining Macros76342 + Node: Macro Pitfalls78420 + Node: Misnesting78945 + Node: Operator Precedence Problems80046 + Node: Swallowing the Semicolon81901 + Node: Duplication of Side Effects83913 + Node: Self-Referential Macros86085 + Node: Argument Prescan88495 + Node: Newlines in Arguments92238 + Node: Conditionals93183 + Node: Conditional Uses95012 + Node: Conditional Syntax96365 + Node: Ifdef96680 + Node: If99846 + Node: Defined102259 + Node: Else103532 + Node: Elif104093 + Node: Deleted Code105373 + Node: Diagnostics106615 + Node: Line Control108232 + Node: Pragmas112039 + Node: Other Directives116308 + Node: Preprocessor Output117502 + Node: Traditional Mode120702 + Node: Implementation Details126281 + Node: Implementation-defined behavior126903 + Node: Implementation limits129176 + Node: Obsolete Features131883 + Node: Assertions132370 + Node: Obsolete once-only headers134901 + Node: Miscellaneous obsolete features136669 + Node: Differences from previous versions138023 + Node: Invocation142535 + Ref: -MF149854 + Node: Environment Variables162264 + Ref: DEPENDENCIES_OUTPUT163914 + Node: GNU Free Documentation License164954 + Node: Option Index184852 + Node: Index of Directives188319 + Node: Concept Index190066 +  + End Tag Table diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info-1 gcc-3.2.3/gcc/doc/cpp.info-1 *** gcc-3.2.2/gcc/doc/cpp.info-1 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info-1 Tue Apr 22 07:07:09 2003 *************** *** 0 **** --- 1,1240 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + File: cpp.info, Node: Top, Next: Overview, Up: (dir) + + + + The C preprocessor implements the macro language used to transform C, + C++, and Objective-C programs before they are compiled. It can also be + useful on its own. + + * Menu: + + * Overview:: + * Header Files:: + * Macros:: + * Conditionals:: + * Diagnostics:: + * Line Control:: + * Pragmas:: + * Other Directives:: + * Preprocessor Output:: + * Traditional Mode:: + * Implementation Details:: + * Invocation:: + * Environment Variables:: + * GNU Free Documentation License:: + * Option Index:: + * Index of Directives:: + * Concept Index:: + + --- The Detailed Node Listing --- + + Overview + + * Initial processing:: + * Tokenization:: + * The preprocessing language:: + + Header Files + + * Include Syntax:: + * Include Operation:: + * Search Path:: + * Once-Only Headers:: + * Computed Includes:: + * Wrapper Headers:: + * System Headers:: + + Macros + + * Object-like Macros:: + * Function-like Macros:: + * Macro Arguments:: + * Stringification:: + * Concatenation:: + * Variadic Macros:: + * Predefined Macros:: + * Undefining and Redefining Macros:: + * Macro Pitfalls:: + + Predefined Macros + + * Standard Predefined Macros:: + * Common Predefined Macros:: + * System-specific Predefined Macros:: + * C++ Named Operators:: + + Macro Pitfalls + + * Misnesting:: + * Operator Precedence Problems:: + * Swallowing the Semicolon:: + * Duplication of Side Effects:: + * Self-Referential Macros:: + * Argument Prescan:: + * Newlines in Arguments:: + + Conditionals + + * Conditional Uses:: + * Conditional Syntax:: + * Deleted Code:: + + Conditional Syntax + + * Ifdef:: + * If:: + * Defined:: + * Else:: + * Elif:: + + Implementation Details + + * Implementation-defined behavior:: + * Implementation limits:: + * Obsolete Features:: + * Differences from previous versions:: + + Obsolete Features + + * Assertions:: + * Obsolete once-only headers:: + * Miscellaneous obsolete features:: + + Copyright (C) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996, 1997, + 1998, 1999, 2000, 2001 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation. A copy of + the license is included in the section entitled "GNU Free Documentation + License". + + This manual contains no Invariant Sections. The Front-Cover Texts + are (a) (see below), and the Back-Cover Texts are (b) (see below). + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise funds + for GNU development. + +  + File: cpp.info, Node: Overview, Next: Header Files, Prev: Top, Up: Top + + Overview + ******** + + The C preprocessor, often known as "cpp", is a "macro processor" + that is used automatically by the C compiler to transform your program + before compilation. It is called a macro processor because it allows + you to define "macros", which are brief abbreviations for longer + constructs. + + The C preprocessor is intended to be used only with C, C++, and + Objective-C source code. In the past, it has been abused as a general + text processor. It will choke on input which does not obey C's lexical + rules. For example, apostrophes will be interpreted as the beginning of + character constants, and cause errors. Also, you cannot rely on it + preserving characteristics of the input which are not significant to + C-family languages. If a Makefile is preprocessed, all the hard tabs + will be removed, and the Makefile will not work. + + Having said that, you can often get away with using cpp on things + which are not C. Other Algol-ish programming languages are often safe + (Pascal, Ada, etc.) So is assembly, with caution. `-traditional' mode + preserves more white space, and is otherwise more permissive. Many of + the problems can be avoided by writing C or C++ style comments instead + of native language comments, and keeping macros simple. + + Wherever possible, you should use a preprocessor geared to the + language you are writing in. Modern versions of the GNU assembler have + macro facilities. Most high level programming languages have their own + conditional compilation and inclusion mechanism. If all else fails, + try a true general text processor, such as GNU M4. + + C preprocessors vary in some details. This manual discusses the GNU + C preprocessor, which provides a small superset of the features of ISO + Standard C. In its default mode, the GNU C preprocessor does not do a + few things required by the standard. These are features which are + rarely, if ever, used, and may cause surprising changes to the meaning + of a program which does not expect them. To get strict ISO Standard C, + you should use the `-std=c89' or `-std=c99' options, depending on which + version of the standard you want. To get all the mandatory + diagnostics, you must also use `-pedantic'. *Note Invocation::. + + * Menu: + + * Initial processing:: + * Tokenization:: + * The preprocessing language:: + +  + File: cpp.info, Node: Initial processing, Next: Tokenization, Up: Overview + + Initial processing + ================== + + The preprocessor performs a series of textual transformations on its + input. These happen before all other processing. Conceptually, they + happen in a rigid order, and the entire file is run through each + transformation before the next one begins. GNU CPP actually does them + all at once, for performance reasons. These transformations correspond + roughly to the first three "phases of translation" described in the C + standard. + + 1. The input file is read into memory and broken into lines. + + GNU CPP expects its input to be a text file, that is, an + unstructured stream of ASCII characters, with some characters + indicating the end of a line of text. Extended ASCII character + sets, such as ISO Latin-1 or Unicode encoded in UTF-8, are also + acceptable. Character sets that are not strict supersets of + seven-bit ASCII will not work. We plan to add complete support + for international character sets in a future release. + + Different systems use different conventions to indicate the end of + a line. GCC accepts the ASCII control sequences `LF', `CR LF', + `CR', and `LF CR' as end-of-line markers. The first three are the + canonical sequences used by Unix, DOS and VMS, and the classic Mac + OS (before OSX) respectively. You may therefore safely copy + source code written on any of those systems to a different one and + use it without conversion. (GCC may lose track of the current + line number if a file doesn't consistently use one convention, as + sometimes happens when it is edited on computers with different + conventions that share a network file system.) `LF CR' is + included because it has been reported as an end-of-line marker + under exotic conditions. + + If the last line of any input file lacks an end-of-line marker, + the end of the file is considered to implicitly supply one. The C + standard says that this condition provokes undefined behavior, so + GCC will emit a warning message. + + 2. If trigraphs are enabled, they are replaced by their corresponding + single characters. + + These are nine three-character sequences, all starting with `??', + that are defined by ISO C to stand for single characters. They + permit obsolete systems that lack some of C's punctuation to use + C. For example, `??/' stands for `\', so '??/n' is a character + constant for a newline. By default, GCC ignores trigraphs, but if + you request a strictly conforming mode with the `-std' option, then + it converts them. + + Trigraphs are not popular and many compilers implement them + incorrectly. Portable code should not rely on trigraphs being + either converted or ignored. If you use the `-Wall' or + `-Wtrigraphs' options, GCC will warn you when a trigraph would + change the meaning of your program if it were converted. + + In a string constant, you can prevent a sequence of question marks + from being confused with a trigraph by inserting a backslash + between the question marks. "(??\?)" is the string `(???)', not + `(?]'. Traditional C compilers do not recognize this idiom. + + The nine trigraphs and their replacements are + + Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- + Replacement: [ ] { } # \ ^ | ~ + + 3. Continued lines are merged into one long line. + + A continued line is a line which ends with a backslash, `\'. The + backslash is removed and the following line is joined with the + current one. No space is inserted, so you may split a line + anywhere, even in the middle of a word. (It is generally more + readable to split lines only at white space.) + + The trailing backslash on a continued line is commonly referred to + as a "backslash-newline". + + If there is white space between a backslash and the end of a line, + that is still a continued line. However, as this is usually the + result of an editing mistake, and many compilers will not accept + it as a continued line, GCC will warn you about it. + + 4. All comments are replaced with single spaces. + + There are two kinds of comments. "Block comments" begin with `/*' + and continue until the next `*/'. Block comments do not nest: + + /* this is /* one comment */ text outside comment + + "Line comments" begin with `//' and continue to the end of the + current line. Line comments do not nest either, but it does not + matter, because they would end in the same place anyway. + + // this is // one comment + text outside comment + + It is safe to put line comments inside block comments, or vice versa. + + /* block comment + // contains line comment + yet more comment + */ outside comment + + // line comment /* contains block comment */ + + But beware of commenting out one end of a block comment with a line + comment. + + // l.c. /* block comment begins + oops! this isn't a comment anymore */ + + Comments are not recognized within string literals. "/* blah */" is + the string constant `/* blah */', not an empty string. + + Line comments are not in the 1989 edition of the C standard, but they + are recognized by GCC as an extension. In C++ and in the 1999 edition + of the C standard, they are an official part of the language. + + Since these transformations happen before all other processing, you + can split a line mechanically with backslash-newline anywhere. You can + comment out the end of a line. You can continue a line comment onto the + next line with backslash-newline. You can even split `/*', `*/', and + `//' onto multiple lines with backslash-newline. For example: + + /\ + * + */ # /* + */ defi\ + ne FO\ + O 10\ + 20 + + is equivalent to `#define FOO 1020'. All these tricks are extremely + confusing and should not be used in code intended to be readable. + + There is no way to prevent a backslash at the end of a line from + being interpreted as a backslash-newline. + + "foo\\ + bar" + + is equivalent to `"foo\bar"', not to `"foo\\bar"'. To avoid having to + worry about this, do not use the deprecated GNU extension which permits + multi-line strings. Instead, use string literal concatenation: + + "foo\\" + "bar" + + Your program will be more portable this way, too. + +  + File: cpp.info, Node: Tokenization, Next: The preprocessing language, Prev: Initial processing, Up: Overview + + Tokenization + ============ + + After the textual transformations are finished, the input file is + converted into a sequence of "preprocessing tokens". These mostly + correspond to the syntactic tokens used by the C compiler, but there are + a few differences. White space separates tokens; it is not itself a + token of any kind. Tokens do not have to be separated by white space, + but it is often necessary to avoid ambiguities. + + When faced with a sequence of characters that has more than one + possible tokenization, the preprocessor is greedy. It always makes + each token, starting from the left, as big as possible before moving on + to the next token. For instance, `a+++++b' is interpreted as + `a ++ ++ + b', not as `a ++ + ++ b', even though the latter + tokenization could be part of a valid C program and the former could + not. + + Once the input file is broken into tokens, the token boundaries never + change, except when the `##' preprocessing operator is used to paste + tokens together. *Note Concatenation::. For example, + + #define foo() bar + foo()baz + ==> bar baz + _not_ + ==> barbaz + + The compiler does not re-tokenize the preprocessor's output. Each + preprocessing token becomes one compiler token. + + Preprocessing tokens fall into five broad classes: identifiers, + preprocessing numbers, string literals, punctuators, and other. An + "identifier" is the same as an identifier in C: any sequence of + letters, digits, or underscores, which begins with a letter or + underscore. Keywords of C have no significance to the preprocessor; + they are ordinary identifiers. You can define a macro whose name is a + keyword, for instance. The only identifier which can be considered a + preprocessing keyword is `defined'. *Note Defined::. + + This is mostly true of other languages which use the C preprocessor. + However, a few of the keywords of C++ are significant even in the + preprocessor. *Note C++ Named Operators::. + + In the 1999 C standard, identifiers may contain letters which are not + part of the "basic source character set," at the implementation's + discretion (such as accented Latin letters, Greek letters, or Chinese + ideograms). This may be done with an extended character set, or the + `\u' and `\U' escape sequences. GCC does not presently implement + either feature in the preprocessor or the compiler. + + As an extension, GCC treats `$' as a letter. This is for + compatibility with some systems, such as VMS, where `$' is commonly + used in system-defined function and object names. `$' is not a letter + in strictly conforming mode, or if you specify the `-$' option. *Note + Invocation::. + + A "preprocessing number" has a rather bizarre definition. The + category includes all the normal integer and floating point constants + one expects of C, but also a number of other things one might not + initially recognize as a number. Formally, preprocessing numbers begin + with an optional period, a required decimal digit, and then continue + with any sequence of letters, digits, underscores, periods, and + exponents. Exponents are the two-character sequences `e+', `e-', `E+', + `E-', `p+', `p-', `P+', and `P-'. (The exponents that begin with `p' + or `P' are new to C99. They are used for hexadecimal floating-point + constants.) + + The purpose of this unusual definition is to isolate the preprocessor + from the full complexity of numeric constants. It does not have to + distinguish between lexically valid and invalid floating-point numbers, + which is complicated. The definition also permits you to split an + identifier at any position and get exactly two tokens, which can then be + pasted back together with the `##' operator. + + It's possible for preprocessing numbers to cause programs to be + misinterpreted. For example, `0xE+12' is a preprocessing number which + does not translate to any valid numeric constant, therefore a syntax + error. It does not mean `0xE + 12', which is what you might have + intended. + + "String literals" are string constants, character constants, and + header file names (the argument of `#include').(1) String constants + and character constants are straightforward: "..." or '...'. In either + case embedded quotes should be escaped with a backslash: '\'' is the + character constant for `''. There is no limit on the length of a + character constant, but the value of a character constant that contains + more than one character is implementation-defined. *Note + Implementation Details::. + + Header file names either look like string constants, "...", or are + written with angle brackets instead, <...>. In either case, backslash + is an ordinary character. There is no way to escape the closing quote + or angle bracket. The preprocessor looks for the header file in + different places depending on which form you use. *Note Include + Operation::. + + In standard C, no string literal may extend past the end of a line. + GNU CPP accepts multi-line string constants, but not multi-line + character constants or header file names. This extension is deprecated + and will be removed in GCC 3.1. You may use continued lines instead, + or string constant concatenation. *Note Differences from previous + versions::. + + "Punctuators" are all the usual bits of punctuation which are + meaningful to C and C++. All but three of the punctuation characters in + ASCII are C punctuators. The exceptions are `@', `$', and ``'. In + addition, all the two- and three-character operators are punctuators. + There are also six "digraphs", which the C++ standard calls + "alternative tokens", which are merely alternate ways to spell other + punctuators. This is a second attempt to work around missing + punctuation in obsolete systems. It has no negative side effects, + unlike trigraphs, but does not cover as much ground. The digraphs and + their corresponding normal punctuators are: + + Digraph: <% %> <: :> %: %:%: + Punctuator: { } [ ] # ## + + Any other single character is considered "other." It is passed on to + the preprocessor's output unmolested. The C compiler will almost + certainly reject source code containing "other" tokens. In ASCII, the + only other characters are `@', `$', ``', and control characters other + than NUL (all bits zero). (Note that `$' is normally considered a + letter.) All characters with the high bit set (numeric range + 0x7F-0xFF) are also "other" in the present implementation. This will + change when proper support for international character sets is added to + GCC. + + NUL is a special case because of the high probability that its + appearance is accidental, and because it may be invisible to the user + (many terminals do not display NUL at all). Within comments, NULs are + silently ignored, just as any other character would be. In running + text, NUL is considered white space. For example, these two directives + have the same meaning. + + #define X^@1 + #define X 1 + + (where `^@' is ASCII NUL). Within string or character constants, NULs + are preserved. In the latter two cases the preprocessor emits a + warning message. + + ---------- Footnotes ---------- + + (1) The C standard uses the term "string literal" to refer only to + what we are calling "string constants". + +  + File: cpp.info, Node: The preprocessing language, Prev: Tokenization, Up: Overview + + The preprocessing language + ========================== + + After tokenization, the stream of tokens may simply be passed + straight to the compiler's parser. However, if it contains any + operations in the "preprocessing language", it will be transformed + first. This stage corresponds roughly to the standard's "translation + phase 4" and is what most people think of as the preprocessor's job. + + The preprocessing language consists of "directives" to be executed + and "macros" to be expanded. Its primary capabilities are: + + * Inclusion of header files. These are files of declarations that + can be substituted into your program. + + * Macro expansion. You can define "macros", which are abbreviations + for arbitrary fragments of C code. The preprocessor will replace + the macros with their definitions throughout the program. Some + macros are automatically defined for you. + + * Conditional compilation. You can include or exclude parts of the + program according to various conditions. + + * Line control. If you use a program to combine or rearrange source + files into an intermediate file which is then compiled, you can + use line control to inform the compiler where each source line + originally came from. + + * Diagnostics. You can detect problems at compile time and issue + errors or warnings. + + There are a few more, less useful, features. + + Except for expansion of predefined macros, all these operations are + triggered with "preprocessing directives". Preprocessing directives + are lines in your program that start with `#'. Whitespace is allowed + before and after the `#'. The `#' is followed by an identifier, the + "directive name". It specifies the operation to perform. Directives + are commonly referred to as `#NAME' where NAME is the directive name. + For example, `#define' is the directive that defines a macro. + + The `#' which begins a directive cannot come from a macro expansion. + Also, the directive name is not macro expanded. Thus, if `foo' is + defined as a macro expanding to `define', that does not make `#foo' a + valid preprocessing directive. + + The set of valid directive names is fixed. Programs cannot define + new preprocessing directives. + + Some directives require arguments; these make up the rest of the + directive line and must be separated from the directive name by + whitespace. For example, `#define' must be followed by a macro name + and the intended expansion of the macro. + + A preprocessing directive cannot cover more than one line. The line + may, however, be continued with backslash-newline, or by a block comment + which extends past the end of the line. In either case, when the + directive is processed, the continuations have already been merged with + the first line to make one long line. + +  + File: cpp.info, Node: Header Files, Next: Macros, Prev: Overview, Up: Top + + Header Files + ************ + + A header file is a file containing C declarations and macro + definitions (*note Macros::) to be shared between several source files. + You request the use of a header file in your program by "including" + it, with the C preprocessing directive `#include'. + + Header files serve two purposes. + + * System header files declare the interfaces to parts of the + operating system. You include them in your program to supply the + definitions and declarations you need to invoke system calls and + libraries. + + * Your own header files contain declarations for interfaces between + the source files of your program. Each time you have a group of + related declarations and macro definitions all or most of which + are needed in several different source files, it is a good idea to + create a header file for them. + + Including a header file produces the same results as copying the + header file into each source file that needs it. Such copying would be + time-consuming and error-prone. With a header file, the related + declarations appear in only one place. If they need to be changed, they + can be changed in one place, and programs that include the header file + will automatically use the new version when next recompiled. The header + file eliminates the labor of finding and changing all the copies as well + as the risk that a failure to find one copy will result in + inconsistencies within a program. + + In C, the usual convention is to give header files names that end + with `.h'. It is most portable to use only letters, digits, dashes, and + underscores in header file names, and at most one dot. + + * Menu: + + * Include Syntax:: + * Include Operation:: + * Search Path:: + * Once-Only Headers:: + * Computed Includes:: + * Wrapper Headers:: + * System Headers:: + +  + File: cpp.info, Node: Include Syntax, Next: Include Operation, Up: Header Files + + Include Syntax + ============== + + Both user and system header files are included using the + preprocessing directive `#include'. It has two variants: + + `#include ' + This variant is used for system header files. It searches for a + file named FILE in a standard list of system directories. You can + prepend directories to this list with the `-I' option (*note + Invocation::). + + `#include "FILE"' + This variant is used for header files of your own program. It + searches for a file named FILE first in the directory containing + the current file, then in the same directories used for `'. + + The argument of `#include', whether delimited with quote marks or + angle brackets, behaves like a string constant in that comments are not + recognized, and macro names are not expanded. Thus, `#include ' + specifies inclusion of a system header file named `x/*y'. + + However, if backslashes occur within FILE, they are considered + ordinary text characters, not escape characters. None of the character + escape sequences appropriate to string constants in C are processed. + Thus, `#include "x\n\\y"' specifies a filename containing three + backslashes. (Some systems interpret `\' as a pathname separator. All + of these also interpret `/' the same way. It is most portable to use + only `/'.) + + It is an error if there is anything (other than comments) on the line + after the file name. + +  + File: cpp.info, Node: Include Operation, Next: Search Path, Prev: Include Syntax, Up: Header Files + + Include Operation + ================= + + The `#include' directive works by directing the C preprocessor to + scan the specified file as input before continuing with the rest of the + current file. The output from the preprocessor contains the output + already generated, followed by the output resulting from the included + file, followed by the output that comes from the text after the + `#include' directive. For example, if you have a header file + `header.h' as follows, + + char *test (void); + + and a main program called `program.c' that uses the header file, like + this, + + int x; + #include "header.h" + + int + main (void) + { + puts (test ()); + } + + the compiler will see the same token stream as it would if `program.c' + read + + int x; + char *test (void); + + int + main (void) + { + puts (test ()); + } + + Included files are not limited to declarations and macro definitions; + those are merely the typical uses. Any fragment of a C program can be + included from another file. The include file could even contain the + beginning of a statement that is concluded in the containing file, or + the end of a statement that was started in the including file. However, + a comment or a string or character constant may not start in the + included file and finish in the including file. An unterminated + comment, string constant or character constant in an included file is + considered to end (with an error message) at the end of the file. + + To avoid confusion, it is best if header files contain only complete + syntactic units--function declarations or definitions, type + declarations, etc. + + The line following the `#include' directive is always treated as a + separate line by the C preprocessor, even if the included file lacks a + final newline. + +  + File: cpp.info, Node: Search Path, Next: Once-Only Headers, Prev: Include Operation, Up: Header Files + + Search Path + =========== + + GCC looks in several different places for headers. On a normal Unix + system, if you do not instruct it otherwise, it will look for headers + requested with `#include ' in: + + /usr/local/include + /usr/lib/gcc-lib/TARGET/VERSION/include + /usr/TARGET/include + /usr/include + + For C++ programs, it will also look in `/usr/include/g++-v3', first. + In the above, TARGET is the canonical name of the system GCC was + configured to compile code for; often but not always the same as the + canonical name of the system it runs on. VERSION is the version of GCC + in use. + + You can add to this list with the `-IDIR' command line option. All + the directories named by `-I' are searched, in left-to-right order, + _before_ the default directories. The only exception is when `dir' is + already searched by default. In this case, the option is ignored and + the search order for system directories remains unchanged. + + Duplicate directories are removed from the quote and bracket search + chains before the two chains are merged to make the final search chain. + Thus, it is possible for a directory to occur twice in the final search + chain if it was specified in both the quote and bracket chains. + + You can prevent GCC from searching any of the default directories + with the `-nostdinc' option. This is useful when you are compiling an + operating system kernel or some other program that does not use the + standard C library facilities, or the standard C library itself. `-I' + options are not ignored as described above when `-nostdinc' is in + effect. + + GCC looks for headers requested with `#include "FILE"' first in the + directory containing the current file, then in the same places it would + have looked for a header requested with angle brackets. For example, + if `/usr/include/sys/stat.h' contains `#include "types.h"', GCC looks + for `types.h' first in `/usr/include/sys', then in its usual search + path. + + `#line' (*note Line Control::) does not change GCC's idea of the + directory containing the current file. + + You may put `-I-' at any point in your list of `-I' options. This + has two effects. First, directories appearing before the `-I-' in the + list are searched only for headers requested with quote marks. + Directories after `-I-' are searched for all headers. Second, the + directory containing the current file is not searched for anything, + unless it happens to be one of the directories named by an `-I' switch. + + `-I. -I-' is not the same as no `-I' options at all, and does not + cause the same behavior for `<>' includes that `""' includes get with + no special options. `-I.' searches the compiler's current working + directory for header files. That may or may not be the same as the + directory containing the current file. + + If you need to look for headers in a directory named `-', write + `-I./-'. + + There are several more ways to adjust the header search path. They + are generally less useful. *Note Invocation::. + +  + File: cpp.info, Node: Once-Only Headers, Next: Computed Includes, Prev: Search Path, Up: Header Files + + Once-Only Headers + ================= + + If a header file happens to be included twice, the compiler will + process its contents twice. This is very likely to cause an error, + e.g. when the compiler sees the same structure definition twice. Even + if it does not, it will certainly waste time. + + The standard way to prevent this is to enclose the entire real + contents of the file in a conditional, like this: + + /* File foo. */ + #ifndef FILE_FOO_SEEN + #define FILE_FOO_SEEN + + THE ENTIRE FILE + + #endif /* !FILE_FOO_SEEN */ + + This construct is commonly known as a "wrapper #ifndef". When the + header is included again, the conditional will be false, because + `FILE_FOO_SEEN' is defined. The preprocessor will skip over the entire + contents of the file, and the compiler will not see it twice. + + GNU CPP optimizes even further. It remembers when a header file has + a wrapper `#ifndef'. If a subsequent `#include' specifies that header, + and the macro in the `#ifndef' is still defined, it does not bother to + rescan the file at all. + + You can put comments outside the wrapper. They will not interfere + with this optimization. + + The macro `FILE_FOO_SEEN' is called the "controlling macro" or + "guard macro". In a user header file, the macro name should not begin + with `_'. In a system header file, it should begin with `__' to avoid + conflicts with user programs. In any kind of header file, the macro + name should contain the name of the file and some additional text, to + avoid conflicts with other header files. + +  + File: cpp.info, Node: Computed Includes, Next: Wrapper Headers, Prev: Once-Only Headers, Up: Header Files + + Computed Includes + ================= + + Sometimes it is necessary to select one of several different header + files to be included into your program. They might specify + configuration parameters to be used on different sorts of operating + systems, for instance. You could do this with a series of conditionals, + + #if SYSTEM_1 + # include "system_1.h" + #elif SYSTEM_2 + # include "system_2.h" + #elif SYSTEM_3 + ... + #endif + + That rapidly becomes tedious. Instead, the preprocessor offers the + ability to use a macro for the header name. This is called a "computed + include". Instead of writing a header name as the direct argument of + `#include', you simply put a macro name there instead: + + #define SYSTEM_H "system_1.h" + ... + #include SYSTEM_H + + `SYSTEM_H' will be expanded, and the preprocessor will look for + `system_1.h' as if the `#include' had been written that way originally. + `SYSTEM_H' could be defined by your Makefile with a `-D' option. + + You must be careful when you define the macro. `#define' saves + tokens, not text. The preprocessor has no way of knowing that the macro + will be used as the argument of `#include', so it generates ordinary + tokens, not a header name. This is unlikely to cause problems if you + use double-quote includes, which are close enough to string constants. + If you use angle brackets, however, you may have trouble. + + The syntax of a computed include is actually a bit more general than + the above. If the first non-whitespace character after `#include' is + not `"' or `<', then the entire line is macro-expanded like running + text would be. + + If the line expands to a single string constant, the contents of that + string constant are the file to be included. CPP does not re-examine + the string for embedded quotes, but neither does it process backslash + escapes in the string. Therefore + + #define HEADER "a\"b" + #include HEADER + + looks for a file named `a\"b'. CPP searches for the file according to + the rules for double-quoted includes. + + If the line expands to a token stream beginning with a `<' token and + including a `>' token, then the tokens between the `<' and the first + `>' are combined to form the filename to be included. Any whitespace + between tokens is reduced to a single space; then any space after the + initial `<' is retained, but a trailing space before the closing `>' is + ignored. CPP searches for the file according to the rules for + angle-bracket includes. + + In either case, if there are any tokens on the line after the file + name, an error occurs and the directive is not processed. It is also + an error if the result of expansion does not match either of the two + expected forms. + + These rules are implementation-defined behavior according to the C + standard. To minimize the risk of different compilers interpreting your + computed includes differently, we recommend you use only a single + object-like macro which expands to a string constant. This will also + minimize confusion for people reading your program. + +  + File: cpp.info, Node: Wrapper Headers, Next: System Headers, Prev: Computed Includes, Up: Header Files + + Wrapper Headers + =============== + + Sometimes it is necessary to adjust the contents of a system-provided + header file without editing it directly. GCC's `fixincludes' operation + does this, for example. One way to do that would be to create a new + header file with the same name and insert it in the search path before + the original header. That works fine as long as you're willing to + replace the old header entirely. But what if you want to refer to the + old header from the new one? + + You cannot simply include the old header with `#include'. That will + start from the beginning, and find your new header again. If your + header is not protected from multiple inclusion (*note Once-Only + Headers::), it will recurse infinitely and cause a fatal error. + + You could include the old header with an absolute pathname: + #include "/usr/include/old-header.h" + + This works, but is not clean; should the system headers ever move, you + would have to edit the new headers to match. + + There is no way to solve this problem within the C standard, but you + can use the GNU extension `#include_next'. It means, "Include the + _next_ file with this name." This directive works like `#include' + except in searching for the specified file: it starts searching the + list of header file directories _after_ the directory in which the + current file was found. + + Suppose you specify `-I /usr/local/include', and the list of + directories to search also includes `/usr/include'; and suppose both + directories contain `signal.h'. Ordinary `#include ' finds + the file under `/usr/local/include'. If that file contains + `#include_next ', it starts searching after that directory, + and finds the file in `/usr/include'. + + `#include_next' does not distinguish between `' and `"FILE"' + inclusion, nor does it check that the file you specify has the same + name as the current file. It simply looks for the file named, starting + with the directory in the search path after the one where the current + file was found. + + The use of `#include_next' can lead to great confusion. We + recommend it be used only when there is no other alternative. In + particular, it should not be used in the headers belonging to a specific + program; it should be used only to make global corrections along the + lines of `fixincludes'. + +  + File: cpp.info, Node: System Headers, Prev: Wrapper Headers, Up: Header Files + + System Headers + ============== + + The header files declaring interfaces to the operating system and + runtime libraries often cannot be written in strictly conforming C. + Therefore, GCC gives code found in "system headers" special treatment. + All warnings, other than those generated by `#warning' (*note + Diagnostics::), are suppressed while GCC is processing a system header. + Macros defined in a system header are immune to a few warnings + wherever they are expanded. This immunity is granted on an ad-hoc + basis, when we find that a warning generates lots of false positives + because of code in macros defined in system headers. + + Normally, only the headers found in specific directories are + considered system headers. These directories are determined when GCC + is compiled. There are, however, two ways to make normal headers into + system headers. + + The `-isystem' command line option adds its argument to the list of + directories to search for headers, just like `-I'. Any headers found + in that directory will be considered system headers. + + All directories named by `-isystem' are searched _after_ all + directories named by `-I', no matter what their order was on the + command line. If the same directory is named by both `-I' and + `-isystem', the `-I' option is ignored. GCC provides an informative + message when this occurs if `-v' is used. + + There is also a directive, `#pragma GCC system_header', which tells + GCC to consider the rest of the current include file a system header, + no matter where it was found. Code that comes before the `#pragma' in + the file will not be affected. `#pragma GCC system_header' has no + effect in the primary source file. + + On very old systems, some of the pre-defined system header + directories get even more special treatment. GNU C++ considers code in + headers found in those directories to be surrounded by an `extern "C"' + block. There is no way to request this behavior with a `#pragma', or + from the command line. + +  + File: cpp.info, Node: Macros, Next: Conditionals, Prev: Header Files, Up: Top + + Macros + ****** + + A "macro" is a fragment of code which has been given a name. + Whenever the name is used, it is replaced by the contents of the macro. + There are two kinds of macros. They differ mostly in what they look + like when they are used. "Object-like" macros resemble data objects + when used, "function-like" macros resemble function calls. + + You may define any valid identifier as a macro, even if it is a C + keyword. The preprocessor does not know anything about keywords. This + can be useful if you wish to hide a keyword such as `const' from an + older compiler that does not understand it. However, the preprocessor + operator `defined' (*note Defined::) can never be defined as a macro, + and C++'s named operators (*note C++ Named Operators::) cannot be + macros when you are compiling C++. + + * Menu: + + * Object-like Macros:: + * Function-like Macros:: + * Macro Arguments:: + * Stringification:: + * Concatenation:: + * Variadic Macros:: + * Predefined Macros:: + * Undefining and Redefining Macros:: + * Macro Pitfalls:: + +  + File: cpp.info, Node: Object-like Macros, Next: Function-like Macros, Up: Macros + + Object-like Macros + ================== + + An "object-like macro" is a simple identifier which will be replaced + by a code fragment. It is called object-like because it looks like a + data object in code that uses it. They are most commonly used to give + symbolic names to numeric constants. + + You create macros with the `#define' directive. `#define' is + followed by the name of the macro and then the token sequence it should + be an abbreviation for, which is variously referred to as the macro's + "body", "expansion" or "replacement list". For example, + + #define BUFFER_SIZE 1024 + + defines a macro named `BUFFER_SIZE' as an abbreviation for the token + `1024'. If somewhere after this `#define' directive there comes a C + statement of the form + + foo = (char *) malloc (BUFFER_SIZE); + + then the C preprocessor will recognize and "expand" the macro + `BUFFER_SIZE'. The C compiler will see the same tokens as it would if + you had written + + foo = (char *) malloc (1024); + + By convention, macro names are written in upper case. Programs are + easier to read when it is possible to tell at a glance which names are + macros. + + The macro's body ends at the end of the `#define' line. You may + continue the definition onto multiple lines, if necessary, using + backslash-newline. When the macro is expanded, however, it will all + come out on one line. For example, + + #define NUMBERS 1, \ + 2, \ + 3 + int x[] = { NUMBERS }; + ==> int x[] = { 1, 2, 3 }; + + The most common visible consequence of this is surprising line numbers + in error messages. + + There is no restriction on what can go in a macro body provided it + decomposes into valid preprocessing tokens. Parentheses need not + balance, and the body need not resemble valid C code. (If it does not, + you may get error messages from the C compiler when you use the macro.) + + The C preprocessor scans your program sequentially. Macro + definitions take effect at the place you write them. Therefore, the + following input to the C preprocessor + + foo = X; + #define X 4 + bar = X; + + produces + + foo = X; + bar = 4; + + When the preprocessor expands a macro name, the macro's expansion + replaces the macro invocation, then the expansion is examined for more + macros to expand. For example, + + #define TABLESIZE BUFSIZE + #define BUFSIZE 1024 + TABLESIZE + ==> BUFSIZE + ==> 1024 + + `TABLESIZE' is expanded first to produce `BUFSIZE', then that macro is + expanded to produce the final result, `1024'. + + Notice that `BUFSIZE' was not defined when `TABLESIZE' was defined. + The `#define' for `TABLESIZE' uses exactly the expansion you + specify--in this case, `BUFSIZE'--and does not check to see whether it + too contains macro names. Only when you _use_ `TABLESIZE' is the + result of its expansion scanned for more macro names. + + This makes a difference if you change the definition of `BUFSIZE' at + some point in the source file. `TABLESIZE', defined as shown, will + always expand using the definition of `BUFSIZE' that is currently in + effect: + + #define BUFSIZE 1020 + #define TABLESIZE BUFSIZE + #undef BUFSIZE + #define BUFSIZE 37 + + Now `TABLESIZE' expands (in two stages) to `37'. + + If the expansion of a macro contains its own name, either directly or + via intermediate macros, it is not expanded again when the expansion is + examined for more macros. This prevents infinite recursion. *Note + Self-Referential Macros::, for the precise details. + +  + File: cpp.info, Node: Function-like Macros, Next: Macro Arguments, Prev: Object-like Macros, Up: Macros + + Function-like Macros + ==================== + + You can also define macros whose use looks like a function call. + These are called "function-like macros". To define a function-like + macro, you use the same `#define' directive, but you put a pair of + parentheses immediately after the macro name. For example, + + #define lang_init() c_init() + lang_init() + ==> c_init() + + A function-like macro is only expanded if its name appears with a + pair of parentheses after it. If you write just the name, it is left + alone. This can be useful when you have a function and a macro of the + same name, and you wish to use the function sometimes. + + extern void foo(void); + #define foo() /* optimized inline version */ + ... + foo(); + funcptr = foo; + + Here the call to `foo()' will use the macro, but the function + pointer will get the address of the real function. If the macro were to + be expanded, it would cause a syntax error. + + If you put spaces between the macro name and the parentheses in the + macro definition, that does not define a function-like macro, it defines + an object-like macro whose expansion happens to begin with a pair of + parentheses. + + #define lang_init () c_init() + lang_init() + ==> () c_init()() + + The first two pairs of parentheses in this expansion come from the + macro. The third is the pair that was originally after the macro + invocation. Since `lang_init' is an object-like macro, it does not + consume those parentheses. + +  + File: cpp.info, Node: Macro Arguments, Next: Stringification, Prev: Function-like Macros, Up: Macros + + Macro Arguments + =============== + + Function-like macros can take "arguments", just like true functions. + To define a macro that uses arguments, you insert "parameters" between + the pair of parentheses in the macro definition that make the macro + function-like. The parameters must be valid C identifiers, separated + by commas and optionally whitespace. + + To invoke a macro that takes arguments, you write the name of the + macro followed by a list of "actual arguments" in parentheses, separated + by commas. The invocation of the macro need not be restricted to a + single logical line--it can cross as many lines in the source file as + you wish. The number of arguments you give must match the number of + parameters in the macro definition. When the macro is expanded, each + use of a parameter in its body is replaced by the tokens of the + corresponding argument. (You need not use all of the parameters in the + macro body.) + + As an example, here is a macro that computes the minimum of two + numeric values, as it is defined in many C programs, and some uses. + + #define min(X, Y) ((X) < (Y) ? (X) : (Y)) + x = min(a, b); ==> x = ((a) < (b) ? (a) : (b)); + y = min(1, 2); ==> y = ((1) < (2) ? (1) : (2)); + z = min(a + 28, *p); ==> z = ((a + 28) < (*p) ? (a + 28) : (*p)); + + (In this small example you can already see several of the dangers of + macro arguments. *Note Macro Pitfalls::, for detailed explanations.) + + Leading and trailing whitespace in each argument is dropped, and all + whitespace between the tokens of an argument is reduced to a single + space. Parentheses within each argument must balance; a comma within + such parentheses does not end the argument. However, there is no + requirement for square brackets or braces to balance, and they do not + prevent a comma from separating arguments. Thus, + + macro (array[x = y, x + 1]) + + passes two arguments to `macro': `array[x = y' and `x + 1]'. If you + want to supply `array[x = y, x + 1]' as an argument, you can write it + as `array[(x = y, x + 1)]', which is equivalent C code. + + All arguments to a macro are completely macro-expanded before they + are substituted into the macro body. After substitution, the complete + text is scanned again for macros to expand, including the arguments. + This rule may seem strange, but it is carefully designed so you need + not worry about whether any function call is actually a macro + invocation. You can run into trouble if you try to be too clever, + though. *Note Argument Prescan::, for detailed discussion. + + For example, `min (min (a, b), c)' is first expanded to + + min (((a) < (b) ? (a) : (b)), (c)) + + and then to + + ((((a) < (b) ? (a) : (b))) < (c) + ? (((a) < (b) ? (a) : (b))) + : (c)) + + (Line breaks shown here for clarity would not actually be generated.) + + You can leave macro arguments empty; this is not an error to the + preprocessor (but many macros will then expand to invalid code). You + cannot leave out arguments entirely; if a macro takes two arguments, + there must be exactly one comma at the top level of its argument list. + Here are some silly examples using `min': + + min(, b) ==> (( ) < (b) ? ( ) : (b)) + min(a, ) ==> ((a ) < ( ) ? (a ) : ( )) + min(,) ==> (( ) < ( ) ? ( ) : ( )) + min((,),) ==> (((,)) < ( ) ? ((,)) : ( )) + + min() error--> macro "min" requires 2 arguments, but only 1 given + min(,,) error--> macro "min" passed 3 arguments, but takes just 2 + + Whitespace is not a preprocessing token, so if a macro `foo' takes + one argument, `foo ()' and `foo ( )' both supply it an empty argument. + Previous GNU preprocessor implementations and documentation were + incorrect on this point, insisting that a function-like macro that + takes a single argument be passed a space if an empty argument was + required. + + Macro parameters appearing inside string literals are not replaced by + their corresponding actual arguments. + + #define foo(x) x, "x" + foo(bar) ==> bar, "x" + diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info-2 gcc-3.2.3/gcc/doc/cpp.info-2 *** gcc-3.2.2/gcc/doc/cpp.info-2 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info-2 Tue Apr 22 07:07:10 2003 *************** *** 0 **** --- 1,1148 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + File: cpp.info, Node: Stringification, Next: Concatenation, Prev: Macro Arguments, Up: Macros + + Stringification + =============== + + Sometimes you may want to convert a macro argument into a string + constant. Parameters are not replaced inside string constants, but you + can use the `#' preprocessing operator instead. When a macro parameter + is used with a leading `#', the preprocessor replaces it with the + literal text of the actual argument, converted to a string constant. + Unlike normal parameter replacement, the argument is not macro-expanded + first. This is called "stringification". + + There is no way to combine an argument with surrounding text and + stringify it all together. Instead, you can write a series of adjacent + string constants and stringified arguments. The preprocessor will + replace the stringified arguments with string constants. The C + compiler will then combine all the adjacent string constants into one + long string. + + Here is an example of a macro definition that uses stringification: + + #define WARN_IF(EXP) \ + do { if (EXP) \ + fprintf (stderr, "Warning: " #EXP "\n"); } \ + while (0) + WARN_IF (x == 0); + ==> do { if (x == 0) + fprintf (stderr, "Warning: " "x == 0" "\n"); } while (0); + + The argument for `EXP' is substituted once, as-is, into the `if' + statement, and once, stringified, into the argument to `fprintf'. If + `x' were a macro, it would be expanded in the `if' statement, but not + in the string. + + The `do' and `while (0)' are a kludge to make it possible to write + `WARN_IF (ARG);', which the resemblance of `WARN_IF' to a function + would make C programmers want to do; see *Note Swallowing the + Semicolon::. + + Stringification in C involves more than putting double-quote + characters around the fragment. The preprocessor backslash-escapes the + quotes surrounding embedded string constants, and all backslashes + within string and character constants, in order to get a valid C string + constant with the proper contents. Thus, stringifying `p = "foo\n";' + results in "p = \"foo\\n\";". However, backslashes that are not inside + string or character constants are not duplicated: `\n' by itself + stringifies to "\n". + + All leading and trailing whitespace in text being stringified is + ignored. Any sequence of whitespace in the middle of the text is + converted to a single space in the stringified result. Comments are + replaced by whitespace long before stringification happens, so they + never appear in stringified text. + + There is no way to convert a macro argument into a character + constant. + + If you want to stringify the result of expansion of a macro argument, + you have to use two levels of macros. + + #define xstr(s) str(s) + #define str(s) #s + #define foo 4 + str (foo) + ==> "foo" + xstr (foo) + ==> xstr (4) + ==> str (4) + ==> "4" + + `s' is stringified when it is used in `str', so it is not + macro-expanded first. But `s' is an ordinary argument to `xstr', so it + is completely macro-expanded before `xstr' itself is expanded (*note + Argument Prescan::). Therefore, by the time `str' gets to its + argument, it has already been macro-expanded. + +  + File: cpp.info, Node: Concatenation, Next: Variadic Macros, Prev: Stringification, Up: Macros + + Concatenation + ============= + + It is often useful to merge two tokens into one while expanding + macros. This is called "token pasting" or "token concatenation". The + `##' preprocessing operator performs token pasting. When a macro is + expanded, the two tokens on either side of each `##' operator are + combined into a single token, which then replaces the `##' and the two + original tokens in the macro expansion. Usually both will be + identifiers, or one will be an identifier and the other a preprocessing + number. When pasted, they make a longer identifier. This isn't the + only valid case. It is also possible to concatenate two numbers (or a + number and a name, such as `1.5' and `e3') into a number. Also, + multi-character operators such as `+=' can be formed by token pasting. + + However, two tokens that don't together form a valid token cannot be + pasted together. For example, you cannot concatenate `x' with `+' in + either order. If you try, the preprocessor issues a warning and emits + the two tokens. Whether it puts white space between the tokens is + undefined. It is common to find unnecessary uses of `##' in complex + macros. If you get this warning, it is likely that you can simply + remove the `##'. + + Both the tokens combined by `##' could come from the macro body, but + you could just as well write them as one token in the first place. + Token pasting is most useful when one or both of the tokens comes from a + macro argument. If either of the tokens next to an `##' is a parameter + name, it is replaced by its actual argument before `##' executes. As + with stringification, the actual argument is not macro-expanded first. + If the argument is empty, that `##' has no effect. + + Keep in mind that the C preprocessor converts comments to whitespace + before macros are even considered. Therefore, you cannot create a + comment by concatenating `/' and `*'. You can put as much whitespace + between `##' and its operands as you like, including comments, and you + can put comments in arguments that will be concatenated. However, it + is an error if `##' appears at either end of a macro body. + + Consider a C program that interprets named commands. There probably + needs to be a table of commands, perhaps an array of structures declared + as follows: + + struct command + { + char *name; + void (*function) (void); + }; + + struct command commands[] = + { + { "quit", quit_command }, + { "help", help_command }, + ... + }; + + It would be cleaner not to have to give each command name twice, + once in the string constant and once in the function name. A macro + which takes the name of a command as an argument can make this + unnecessary. The string constant can be created with stringification, + and the function name by concatenating the argument with `_command'. + Here is how it is done: + + #define COMMAND(NAME) { #NAME, NAME ## _command } + + struct command commands[] = + { + COMMAND (quit), + COMMAND (help), + ... + }; + +  + File: cpp.info, Node: Variadic Macros, Next: Predefined Macros, Prev: Concatenation, Up: Macros + + Variadic Macros + =============== + + A macro can be declared to accept a variable number of arguments + much as a function can. The syntax for defining the macro is similar + to that of a function. Here is an example: + + #define eprintf(...) fprintf (stderr, __VA_ARGS__) + + This kind of macro is called "variadic". When the macro is invoked, + all the tokens in its argument list after the last named argument (this + macro has none), including any commas, become the "variable argument". + This sequence of tokens replaces the identifier `__VA_ARGS__' in the + macro body wherever it appears. Thus, we have this expansion: + + eprintf ("%s:%d: ", input_file, lineno) + ==> fprintf (stderr, "%s:%d: ", input_file, lineno) + + The variable argument is completely macro-expanded before it is + inserted into the macro expansion, just like an ordinary argument. You + may use the `#' and `##' operators to stringify the variable argument + or to paste its leading or trailing token with another token. (But see + below for an important special case for `##'.) + + If your macro is complicated, you may want a more descriptive name + for the variable argument than `__VA_ARGS__'. GNU CPP permits this, as + an extension. You may write an argument name immediately before the + `...'; that name is used for the variable argument. The `eprintf' + macro above could be written + + #define eprintf(args...) fprintf (stderr, args) + + using this extension. You cannot use `__VA_ARGS__' and this extension + in the same macro. + + You can have named arguments as well as variable arguments in a + variadic macro. We could define `eprintf' like this, instead: + + #define eprintf(format, ...) fprintf (stderr, format, __VA_ARGS__) + + This formulation looks more descriptive, but unfortunately it is less + flexible: you must now supply at least one argument after the format + string. In standard C, you cannot omit the comma separating the named + argument from the variable arguments. Furthermore, if you leave the + variable argument empty, you will get a syntax error, because there + will be an extra comma after the format string. + + eprintf("success!\n", ); + ==> fprintf(stderr, "success!\n", ); + + GNU CPP has a pair of extensions which deal with this problem. + First, you are allowed to leave the variable argument out entirely: + + eprintf ("success!\n") + ==> fprintf(stderr, "success!\n", ); + + Second, the `##' token paste operator has a special meaning when placed + between a comma and a variable argument. If you write + + #define eprintf(format, ...) fprintf (stderr, format, ##__VA_ARGS__) + + and the variable argument is left out when the `eprintf' macro is used, + then the comma before the `##' will be deleted. This does _not_ happen + if you pass an empty argument, nor does it happen if the token + preceding `##' is anything other than a comma. + + eprintf ("success!\n") + ==> fprintf(stderr, "success!\n"); + + The above explanation is ambiguous about the case where the only macro + parameter is a variable arguments parameter, as it is meaningless to + try to distinguish whether no argument at all is an empty argument or a + missing argument. In this case the C99 standard is clear that the + comma must remain, however the existing GCC extension used to swallow + the comma. So CPP retains the comma when conforming to a specific C + standard, and drops it otherwise. + + C99 mandates that the only place the identifier `__VA_ARGS__' can + appear is in the replacement list of a variadic macro. It may not be + used as a macro name, macro argument name, or within a different type + of macro. It may also be forbidden in open text; the standard is + ambiguous. We recommend you avoid using it except for its defined + purpose. + + Variadic macros are a new feature in C99. GNU CPP has supported them + for a long time, but only with a named variable argument (`args...', + not `...' and `__VA_ARGS__'). If you are concerned with portability to + previous versions of GCC, you should use only named variable arguments. + On the other hand, if you are concerned with portability to other + conforming implementations of C99, you should use only `__VA_ARGS__'. + + Previous versions of GNU CPP implemented the comma-deletion extension + much more generally. We have restricted it in this release to minimize + the differences from C99. To get the same effect with both this and + previous versions of GCC, the token preceding the special `##' must be + a comma, and there must be white space between that comma and whatever + comes immediately before it: + + #define eprintf(format, args...) fprintf (stderr, format , ##args) + + *Note Differences from previous versions::, for the gory details. + +  + File: cpp.info, Node: Predefined Macros, Next: Undefining and Redefining Macros, Prev: Variadic Macros, Up: Macros + + Predefined Macros + ================= + + Several object-like macros are predefined; you use them without + supplying their definitions. They fall into three classes: standard, + common, and system-specific. + + In C++, there is a fourth category, the named operators. They act + like predefined macros, but you cannot undefine them. + + * Menu: + + * Standard Predefined Macros:: + * Common Predefined Macros:: + * System-specific Predefined Macros:: + * C++ Named Operators:: + +  + File: cpp.info, Node: Standard Predefined Macros, Next: Common Predefined Macros, Up: Predefined Macros + + Standard Predefined Macros + -------------------------- + + The standard predefined macros are specified by the C and/or C++ + language standards, so they are available with all compilers that + implement those standards. Older compilers may not provide all of + them. Their names all start with double underscores. + + `__FILE__' + This macro expands to the name of the current input file, in the + form of a C string constant. This is the path by which the + preprocessor opened the file, not the short name specified in + `#include' or as the input file name argument. For example, + `"/usr/local/include/myheader.h"' is a possible expansion of this + macro. + + `__LINE__' + This macro expands to the current input line number, in the form + of a decimal integer constant. While we call it a predefined + macro, it's a pretty strange macro, since its "definition" changes + with each new line of source code. + + `__FILE__' and `__LINE__' are useful in generating an error message + to report an inconsistency detected by the program; the message can + state the source line at which the inconsistency was detected. For + example, + + fprintf (stderr, "Internal error: " + "negative string length " + "%d at %s, line %d.", + length, __FILE__, __LINE__); + + An `#include' directive changes the expansions of `__FILE__' and + `__LINE__' to correspond to the included file. At the end of that + file, when processing resumes on the input file that contained the + `#include' directive, the expansions of `__FILE__' and `__LINE__' + revert to the values they had before the `#include' (but `__LINE__' is + then incremented by one as processing moves to the line after the + `#include'). + + A `#line' directive changes `__LINE__', and may change `__FILE__' as + well. *Note Line Control::. + + C99 introduces `__func__', and GCC has provided `__FUNCTION__' for a + long time. Both of these are strings containing the name of the + current function (there are slight semantic differences; see the GCC + manual). Neither of them is a macro; the preprocessor does not know the + name of the current function. They tend to be useful in conjunction + with `__FILE__' and `__LINE__', though. + + `__DATE__' + This macro expands to a string constant that describes the date on + which the preprocessor is being run. The string constant contains + eleven characters and looks like `"Feb 12 1996"'. If the day of + the month is less than 10, it is padded with a space on the left. + + `__TIME__' + This macro expands to a string constant that describes the time at + which the preprocessor is being run. The string constant contains + eight characters and looks like `"23:59:01"'. + + `__STDC__' + In normal operation, this macro expands to the constant 1, to + signify that this compiler conforms to ISO Standard C. If GNU CPP + is used with a compiler other than GCC, this is not necessarily + true; however, the preprocessor always conforms to the standard, + unless the `-traditional' option is used. + + This macro is not defined if the `-traditional' option is used. + + On some hosts, the system compiler uses a different convention, + where `__STDC__' is normally 0, but is 1 if the user specifies + strict conformance to the C Standard. GNU CPP follows the host + convention when processing system header files, but when + processing user files `__STDC__' is always 1. This has been + reported to cause problems; for instance, some versions of Solaris + provide X Windows headers that expect `__STDC__' to be either + undefined or 1. *Note Invocation::. + + `__STDC_VERSION__' + This macro expands to the C Standard's version number, a long + integer constant of the form `YYYYMML' where YYYY and MM are the + year and month of the Standard version. This signifies which + version of the C Standard the compiler conforms to. Like + `__STDC__', this is not necessarily accurate for the entire + implementation, unless GNU CPP is being used with GCC. + + The value `199409L' signifies the 1989 C standard as amended in + 1994, which is the current default; the value `199901L' signifies + the 1999 revision of the C standard. Support for the 1999 + revision is not yet complete. + + This macro is not defined if the `-traditional' option is used, nor + when compiling C++ or Objective-C. + + `__STDC_HOSTED__' + This macro is defined, with value 1, if the compiler's target is a + "hosted environment". A hosted environment has the complete + facilities of the standard C library available. + + `__cplusplus' + This macro is defined when the C++ compiler is in use. You can use + `__cplusplus' to test whether a header is compiled by a C compiler + or a C++ compiler. This macro is similar to `__STDC_VERSION__', in + that it expands to a version number. A fully conforming + implementation of the 1998 C++ standard will define this macro to + `199711L'. The GNU C++ compiler is not yet fully conforming, so + it uses `1' instead. We hope to complete our implementation in + the near future. + + +  + File: cpp.info, Node: Common Predefined Macros, Next: System-specific Predefined Macros, Prev: Standard Predefined Macros, Up: Predefined Macros + + Common Predefined Macros + ------------------------ + + The common predefined macros are GNU C extensions. They are + available with the same meanings regardless of the machine or operating + system on which you are using GNU C. Their names all start with double + underscores. + + `__GNUC__' + `__GNUC_MINOR__' + `__GNUC_PATCHLEVEL__' + These macros are defined by all GNU compilers that use the C + preprocessor: C, C++, and Objective-C. Their values are the major + version, minor version, and patch level of the compiler, as integer + constants. For example, GCC 3.2.1 will define `__GNUC__' to 3, + `__GNUC_MINOR__' to 2, and `__GNUC_PATCHLEVEL__' to 1. They are + defined only when the entire compiler is in use; if you invoke the + preprocessor directly, they are not defined. + + `__GNUC_PATCHLEVEL__' is new to GCC 3.0; it is also present in the + widely-used development snapshots leading up to 3.0 (which identify + themselves as GCC 2.96 or 2.97, depending on which snapshot you + have). + + If all you need to know is whether or not your program is being + compiled by GCC, you can simply test `__GNUC__'. If you need to + write code which depends on a specific version, you must be more + careful. Each time the minor version is increased, the patch + level is reset to zero; each time the major version is increased + (which happens rarely), the minor version and patch level are + reset. If you wish to use the predefined macros directly in the + conditional, you will need to write it like this: + + /* Test for GCC > 3.2.0 */ + #if __GNUC__ > 3 || \ + (__GNUC__ == 3 && (__GNUC_MINOR__ > 2 || \ + (__GNUC_MINOR__ == 2 && \ + __GNUC_PATCHLEVEL__ > 0)) + + Another approach is to use the predefined macros to calculate a + single number, then compare that against a threshold: + + #define GCC_VERSION (__GNUC__ * 10000 \ + + __GNUC_MINOR__ * 100 \ + + __GNUC_PATCHLEVEL__) + ... + /* Test for GCC > 3.2.0 */ + #if GCC_VERSION > 30200 + + Many people find this form easier to understand. + + `__OBJC__' + This macro is defined, with value 1, when the Objective-C compiler + is in use. You can use `__OBJC__' to test whether a header is + compiled by a C compiler or a Objective-C compiler. + + `__GNUG__' + The GNU C++ compiler defines this. Testing it is equivalent to + testing `(__GNUC__ && __cplusplus)'. + + `__STRICT_ANSI__' + GCC defines this macro if and only if the `-ansi' switch, or a + `-std' switch specifying strict conformance to some version of ISO + C, was specified when GCC was invoked. It is defined to `1'. + This macro exists primarily to direct GNU libc's header files to + restrict their definitions to the minimal set found in the 1989 C + standard. + + `__BASE_FILE__' + This macro expands to the name of the main input file, in the form + of a C string constant. This is the source file that was specified + on the command line of the preprocessor or C compiler. + + `__INCLUDE_LEVEL__' + This macro expands to a decimal integer constant that represents + the depth of nesting in include files. The value of this macro is + incremented on every `#include' directive and decremented at the + end of every included file. It starts out at 0, it's value within + the base file specified on the command line. + + `__VERSION__' + This macro expands to a string constant which describes the + version of the compiler in use. You should not rely on its + contents having any particular form, but it can be counted on to + contain at least the release number. + + `__OPTIMIZE__' + `__OPTIMIZE_SIZE__' + `__NO_INLINE__' + These macros describe the compilation mode. `__OPTIMIZE__' is + defined in all optimizing compilations. `__OPTIMIZE_SIZE__' is + defined if the compiler is optimizing for size, not speed. + `__NO_INLINE__' is defined if no functions will be inlined into + their callers (when not optimizing, or when inlining has been + specifically disabled by `-fno-inline'). + + These macros cause certain GNU header files to provide optimized + definitions, using macros or inline functions, of system library + functions. You should not use these macros in any way unless you + make sure that programs will execute with the same effect whether + or not they are defined. If they are defined, their value is 1. + + `__CHAR_UNSIGNED__' + GCC defines this macro if and only if the data type `char' is + unsigned on the target machine. It exists to cause the standard + header file `limits.h' to work correctly. You should not use this + macro yourself; instead, refer to the standard macros defined in + `limits.h'. + + `__REGISTER_PREFIX__' + This macro expands to a single token (not a string constant) which + is the prefix applied to CPU register names in assembly language + for this target. You can use it to write assembly that is usable + in multiple environments. For example, in the `m68k-aout' + environment it expands to nothing, but in the `m68k-coff' + environment it expands to a single `%'. + + `__USER_LABEL_PREFIX__' + This macro expands to a single token which is the prefix applied to + user labels (symbols visible to C code) in assembly. For example, + in the `m68k-aout' environment it expands to an `_', but in the + `m68k-coff' environment it expands to nothing. + + This macro will have the correct definition even if + `-f(no-)underscores' is in use, but it will not be correct if + target-specific options that adjust this prefix are used (e.g. the + OSF/rose `-mno-underscores' option). + + `__SIZE_TYPE__' + `__PTRDIFF_TYPE__' + `__WCHAR_TYPE__' + `__WINT_TYPE__' + These macros are defined to the correct underlying types for the + `size_t', `ptrdiff_t', `wchar_t', and `wint_t' typedefs, + respectively. They exist to make the standard header files + `stddef.h' and `wchar.h' work correctly. You should not use these + macros directly; instead, include the appropriate headers and use + the typedefs. + + `__USING_SJLJ_EXCEPTIONS__' + This macro is defined, with value 1, if the compiler uses the old + mechanism based on `setjmp' and `longjmp' for exception handling. + +  + File: cpp.info, Node: System-specific Predefined Macros, Next: C++ Named Operators, Prev: Common Predefined Macros, Up: Predefined Macros + + System-specific Predefined Macros + --------------------------------- + + The C preprocessor normally predefines several macros that indicate + what type of system and machine is in use. They are obviously + different on each target supported by GCC. This manual, being for all + systems and machines, cannot tell you what their names are, but you can + use `cpp -dM' to see them all. *Note Invocation::. All system-specific + predefined macros expand to the constant 1, so you can test them with + either `#ifdef' or `#if'. + + The C standard requires that all system-specific macros be part of + the "reserved namespace". All names which begin with two underscores, + or an underscore and a capital letter, are reserved for the compiler and + library to use as they wish. However, historically system-specific + macros have had names with no special prefix; for instance, it is common + to find `unix' defined on Unix systems. For all such macros, GCC + provides a parallel macro with two underscores added at the beginning + and the end. If `unix' is defined, `__unix__' will be defined too. + There will never be more than two underscores; the parallel of `_mips' + is `__mips__'. + + When the `-ansi' option, or any `-std' option that requests strict + conformance, is given to the compiler, all the system-specific + predefined macros outside the reserved namespace are suppressed. The + parallel macros, inside the reserved namespace, remain defined. + + We are slowly phasing out all predefined macros which are outside the + reserved namespace. You should never use them in new programs, and we + encourage you to correct older code to use the parallel macros whenever + you find it. We don't recommend you use the system-specific macros that + are in the reserved namespace, either. It is better in the long run to + check specifically for features you need, using a tool such as + `autoconf'. + +  + File: cpp.info, Node: C++ Named Operators, Prev: System-specific Predefined Macros, Up: Predefined Macros + + C++ Named Operators + ------------------- + + In C++, there are eleven keywords which are simply alternate + spellings of operators normally written with punctuation. These + keywords are treated as such even in the preprocessor. They function + as operators in `#if', and they cannot be defined as macros or + poisoned. In C, you can request that those keywords take their C++ + meaning by including `iso646.h'. That header defines each one as a + normal object-like macro expanding to the appropriate punctuator. + + These are the named operators and their corresponding punctuators: + + Named Operator Punctuator + `and' `&&' + `and_eq' `&=' + `bitand' `&' + `bitor' `|' + `compl' `~' + `not' `!' + `not_eq' `!=' + `or' `||' + `or_eq' `|=' + `xor' `^' + `xor_eq' `^=' + +  + File: cpp.info, Node: Undefining and Redefining Macros, Next: Macro Pitfalls, Prev: Predefined Macros, Up: Macros + + Undefining and Redefining Macros + ================================ + + If a macro ceases to be useful, it may be "undefined" with the + `#undef' directive. `#undef' takes a single argument, the name of the + macro to undefine. You use the bare macro name, even if the macro is + function-like. It is an error if anything appears on the line after + the macro name. `#undef' has no effect if the name is not a macro. + + #define FOO 4 + x = FOO; ==> x = 4; + #undef FOO + x = FOO; ==> x = FOO; + + Once a macro has been undefined, that identifier may be "redefined" + as a macro by a subsequent `#define' directive. The new definition + need not have any resemblance to the old definition. + + However, if an identifier which is currently a macro is redefined, + then the new definition must be "effectively the same" as the old one. + Two macro definitions are effectively the same if: + * Both are the same type of macro (object- or function-like). + + * All the tokens of the replacement list are the same. + + * If there are any parameters, they are the same. + + * Whitespace appears in the same places in both. It need not be + exactly the same amount of whitespace, though. Remember that + comments count as whitespace. + + These definitions are effectively the same: + #define FOUR (2 + 2) + #define FOUR (2 + 2) + #define FOUR (2 /* two */ + 2) + + but these are not: + #define FOUR (2 + 2) + #define FOUR ( 2+2 ) + #define FOUR (2 * 2) + #define FOUR(score,and,seven,years,ago) (2 + 2) + + If a macro is redefined with a definition that is not effectively the + same as the old one, the preprocessor issues a warning and changes the + macro to use the new definition. If the new definition is effectively + the same, the redefinition is silently ignored. This allows, for + instance, two different headers to define a common macro. The + preprocessor will only complain if the definitions do not match. + +  + File: cpp.info, Node: Macro Pitfalls, Prev: Undefining and Redefining Macros, Up: Macros + + Macro Pitfalls + ============== + + In this section we describe some special rules that apply to macros + and macro expansion, and point out certain cases in which the rules have + counter-intuitive consequences that you must watch out for. + + * Menu: + + * Misnesting:: + * Operator Precedence Problems:: + * Swallowing the Semicolon:: + * Duplication of Side Effects:: + * Self-Referential Macros:: + * Argument Prescan:: + * Newlines in Arguments:: + +  + File: cpp.info, Node: Misnesting, Next: Operator Precedence Problems, Up: Macro Pitfalls + + Misnesting + ---------- + + When a macro is called with arguments, the arguments are substituted + into the macro body and the result is checked, together with the rest of + the input file, for more macro calls. It is possible to piece together + a macro call coming partially from the macro body and partially from the + arguments. For example, + + #define twice(x) (2*(x)) + #define call_with_1(x) x(1) + call_with_1 (twice) + ==> twice(1) + ==> (2*(1)) + + Macro definitions do not have to have balanced parentheses. By + writing an unbalanced open parenthesis in a macro body, it is possible + to create a macro call that begins inside the macro body but ends + outside of it. For example, + + #define strange(file) fprintf (file, "%s %d", + ... + strange(stderr) p, 35) + ==> fprintf (stderr, "%s %d", p, 35) + + The ability to piece together a macro call can be useful, but the + use of unbalanced open parentheses in a macro body is just confusing, + and should be avoided. + +  + File: cpp.info, Node: Operator Precedence Problems, Next: Swallowing the Semicolon, Prev: Misnesting, Up: Macro Pitfalls + + Operator Precedence Problems + ---------------------------- + + You may have noticed that in most of the macro definition examples + shown above, each occurrence of a macro argument name had parentheses + around it. In addition, another pair of parentheses usually surround + the entire macro definition. Here is why it is best to write macros + that way. + + Suppose you define a macro as follows, + + #define ceil_div(x, y) (x + y - 1) / y + + whose purpose is to divide, rounding up. (One use for this operation is + to compute how many `int' objects are needed to hold a certain number + of `char' objects.) Then suppose it is used as follows: + + a = ceil_div (b & c, sizeof (int)); + ==> a = (b & c + sizeof (int) - 1) / sizeof (int); + + This does not do what is intended. The operator-precedence rules of C + make it equivalent to this: + + a = (b & (c + sizeof (int) - 1)) / sizeof (int); + + What we want is this: + + a = ((b & c) + sizeof (int) - 1)) / sizeof (int); + + Defining the macro as + + #define ceil_div(x, y) ((x) + (y) - 1) / (y) + + provides the desired result. + + Unintended grouping can result in another way. Consider `sizeof + ceil_div(1, 2)'. That has the appearance of a C expression that would + compute the size of the type of `ceil_div (1, 2)', but in fact it means + something very different. Here is what it expands to: + + sizeof ((1) + (2) - 1) / (2) + + This would take the size of an integer and divide it by two. The + precedence rules have put the division outside the `sizeof' when it was + intended to be inside. + + Parentheses around the entire macro definition prevent such problems. + Here, then, is the recommended way to define `ceil_div': + + #define ceil_div(x, y) (((x) + (y) - 1) / (y)) + +  + File: cpp.info, Node: Swallowing the Semicolon, Next: Duplication of Side Effects, Prev: Operator Precedence Problems, Up: Macro Pitfalls + + Swallowing the Semicolon + ------------------------ + + Often it is desirable to define a macro that expands into a compound + statement. Consider, for example, the following macro, that advances a + pointer (the argument `p' says where to find it) across whitespace + characters: + + #define SKIP_SPACES(p, limit) \ + { char *lim = (limit); \ + while (p < lim) { \ + if (*p++ != ' ') { \ + p--; break; }}} + + Here backslash-newline is used to split the macro definition, which must + be a single logical line, so that it resembles the way such code would + be laid out if not part of a macro definition. + + A call to this macro might be `SKIP_SPACES (p, lim)'. Strictly + speaking, the call expands to a compound statement, which is a complete + statement with no need for a semicolon to end it. However, since it + looks like a function call, it minimizes confusion if you can use it + like a function call, writing a semicolon afterward, as in `SKIP_SPACES + (p, lim);' + + This can cause trouble before `else' statements, because the + semicolon is actually a null statement. Suppose you write + + if (*p != 0) + SKIP_SPACES (p, lim); + else ... + + The presence of two statements--the compound statement and a null + statement--in between the `if' condition and the `else' makes invalid C + code. + + The definition of the macro `SKIP_SPACES' can be altered to solve + this problem, using a `do ... while' statement. Here is how: + + #define SKIP_SPACES(p, limit) \ + do { char *lim = (limit); \ + while (p < lim) { \ + if (*p++ != ' ') { \ + p--; break; }}} \ + while (0) + + Now `SKIP_SPACES (p, lim);' expands into + + do {...} while (0); + + which is one statement. The loop executes exactly once; most compilers + generate no extra code for it. + +  + File: cpp.info, Node: Duplication of Side Effects, Next: Self-Referential Macros, Prev: Swallowing the Semicolon, Up: Macro Pitfalls + + Duplication of Side Effects + --------------------------- + + Many C programs define a macro `min', for "minimum", like this: + + #define min(X, Y) ((X) < (Y) ? (X) : (Y)) + + When you use this macro with an argument containing a side effect, + as shown here, + + next = min (x + y, foo (z)); + + it expands as follows: + + next = ((x + y) < (foo (z)) ? (x + y) : (foo (z))); + + where `x + y' has been substituted for `X' and `foo (z)' for `Y'. + + The function `foo' is used only once in the statement as it appears + in the program, but the expression `foo (z)' has been substituted twice + into the macro expansion. As a result, `foo' might be called two times + when the statement is executed. If it has side effects or if it takes + a long time to compute, the results might not be what you intended. We + say that `min' is an "unsafe" macro. + + The best solution to this problem is to define `min' in a way that + computes the value of `foo (z)' only once. The C language offers no + standard way to do this, but it can be done with GNU extensions as + follows: + + #define min(X, Y) \ + ({ typeof (X) x_ = (X); \ + typeof (Y) y_ = (Y); \ + (x_ < y_) ? x_ : y_; }) + + The `({ ... })' notation produces a compound statement that acts as + an expression. Its value is the value of its last statement. This + permits us to define local variables and assign each argument to one. + The local variables have underscores after their names to reduce the + risk of conflict with an identifier of wider scope (it is impossible to + avoid this entirely). Now each argument is evaluated exactly once. + + If you do not wish to use GNU C extensions, the only solution is to + be careful when _using_ the macro `min'. For example, you can + calculate the value of `foo (z)', save it in a variable, and use that + variable in `min': + + #define min(X, Y) ((X) < (Y) ? (X) : (Y)) + ... + { + int tem = foo (z); + next = min (x + y, tem); + } + + (where we assume that `foo' returns type `int'). + +  + File: cpp.info, Node: Self-Referential Macros, Next: Argument Prescan, Prev: Duplication of Side Effects, Up: Macro Pitfalls + + Self-Referential Macros + ----------------------- + + A "self-referential" macro is one whose name appears in its + definition. Recall that all macro definitions are rescanned for more + macros to replace. If the self-reference were considered a use of the + macro, it would produce an infinitely large expansion. To prevent this, + the self-reference is not considered a macro call. It is passed into + the preprocessor output unchanged. Let's consider an example: + + #define foo (4 + foo) + + where `foo' is also a variable in your program. + + Following the ordinary rules, each reference to `foo' will expand + into `(4 + foo)'; then this will be rescanned and will expand into `(4 + + (4 + foo))'; and so on until the computer runs out of memory. + + The self-reference rule cuts this process short after one step, at + `(4 + foo)'. Therefore, this macro definition has the possibly useful + effect of causing the program to add 4 to the value of `foo' wherever + `foo' is referred to. + + In most cases, it is a bad idea to take advantage of this feature. A + person reading the program who sees that `foo' is a variable will not + expect that it is a macro as well. The reader will come across the + identifier `foo' in the program and think its value should be that of + the variable `foo', whereas in fact the value is four greater. + + One common, useful use of self-reference is to create a macro which + expands to itself. If you write + + #define EPERM EPERM + + then the macro `EPERM' expands to `EPERM'. Effectively, it is left + alone by the preprocessor whenever it's used in running text. You can + tell that it's a macro with `#ifdef'. You might do this if you want to + define numeric constants with an `enum', but have `#ifdef' be true for + each constant. + + If a macro `x' expands to use a macro `y', and the expansion of `y' + refers to the macro `x', that is an "indirect self-reference" of `x'. + `x' is not expanded in this case either. Thus, if we have + + #define x (4 + y) + #define y (2 * x) + + then `x' and `y' expand as follows: + + x ==> (4 + y) + ==> (4 + (2 * x)) + + y ==> (2 * x) + ==> (2 * (4 + y)) + + Each macro is expanded when it appears in the definition of the other + macro, but not when it indirectly appears in its own definition. + +  + File: cpp.info, Node: Argument Prescan, Next: Newlines in Arguments, Prev: Self-Referential Macros, Up: Macro Pitfalls + + Argument Prescan + ---------------- + + Macro arguments are completely macro-expanded before they are + substituted into a macro body, unless they are stringified or pasted + with other tokens. After substitution, the entire macro body, including + the substituted arguments, is scanned again for macros to be expanded. + The result is that the arguments are scanned _twice_ to expand macro + calls in them. + + Most of the time, this has no effect. If the argument contained any + macro calls, they are expanded during the first scan. The result + therefore contains no macro calls, so the second scan does not change + it. If the argument were substituted as given, with no prescan, the + single remaining scan would find the same macro calls and produce the + same results. + + You might expect the double scan to change the results when a + self-referential macro is used in an argument of another macro (*note + Self-Referential Macros::): the self-referential macro would be + expanded once in the first scan, and a second time in the second scan. + However, this is not what happens. The self-references that do not + expand in the first scan are marked so that they will not expand in the + second scan either. + + You might wonder, "Why mention the prescan, if it makes no + difference? And why not skip it and make the preprocessor faster?" + The answer is that the prescan does make a difference in three special + cases: + + * Nested calls to a macro. + + We say that "nested" calls to a macro occur when a macro's argument + contains a call to that very macro. For example, if `f' is a macro + that expects one argument, `f (f (1))' is a nested pair of calls to + `f'. The desired expansion is made by expanding `f (1)' and + substituting that into the definition of `f'. The prescan causes + the expected result to happen. Without the prescan, `f (1)' itself + would be substituted as an argument, and the inner use of `f' would + appear during the main scan as an indirect self-reference and + would not be expanded. + + * Macros that call other macros that stringify or concatenate. + + If an argument is stringified or concatenated, the prescan does not + occur. If you _want_ to expand a macro, then stringify or + concatenate its expansion, you can do that by causing one macro to + call another macro that does the stringification or concatenation. + For instance, if you have + + #define AFTERX(x) X_ ## x + #define XAFTERX(x) AFTERX(x) + #define TABLESIZE 1024 + #define BUFSIZE TABLESIZE + + then `AFTERX(BUFSIZE)' expands to `X_BUFSIZE', and + `XAFTERX(BUFSIZE)' expands to `X_1024'. (Not to `X_TABLESIZE'. + Prescan always does a complete expansion.) + + * Macros used in arguments, whose expansions contain unshielded + commas. + + This can cause a macro expanded on the second scan to be called + with the wrong number of arguments. Here is an example: + + #define foo a,b + #define bar(x) lose(x) + #define lose(x) (1 + (x)) + + We would like `bar(foo)' to turn into `(1 + (foo))', which would + then turn into `(1 + (a,b))'. Instead, `bar(foo)' expands into + `lose(a,b)', and you get an error because `lose' requires a single + argument. In this case, the problem is easily solved by the same + parentheses that ought to be used to prevent misnesting of + arithmetic operations: + + #define foo (a,b) + or + #define bar(x) lose((x)) + + The extra pair of parentheses prevents the comma in `foo''s + definition from being interpreted as an argument separator. + + +  + File: cpp.info, Node: Newlines in Arguments, Prev: Argument Prescan, Up: Macro Pitfalls + + Newlines in Arguments + --------------------- + + The invocation of a function-like macro can extend over many logical + lines. However, in the present implementation, the entire expansion + comes out on one line. Thus line numbers emitted by the compiler or + debugger refer to the line the invocation started on, which might be + different to the line containing the argument causing the problem. + + Here is an example illustrating this: + + #define ignore_second_arg(a,b,c) a; c + + ignore_second_arg (foo (), + ignored (), + syntax error); + + The syntax error triggered by the tokens `syntax error' results in an + error message citing line three--the line of ignore_second_arg-- even + though the problematic code comes from line five. + + We consider this a bug, and intend to fix it in the near future. + +  + File: cpp.info, Node: Conditionals, Next: Diagnostics, Prev: Macros, Up: Top + + Conditionals + ************ + + A "conditional" is a directive that instructs the preprocessor to + select whether or not to include a chunk of code in the final token + stream passed to the compiler. Preprocessor conditionals can test + arithmetic expressions, or whether a name is defined as a macro, or both + simultaneously using the special `defined' operator. + + A conditional in the C preprocessor resembles in some ways an `if' + statement in C, but it is important to understand the difference between + them. The condition in an `if' statement is tested during the + execution of your program. Its purpose is to allow your program to + behave differently from run to run, depending on the data it is + operating on. The condition in a preprocessing conditional directive is + tested when your program is compiled. Its purpose is to allow different + code to be included in the program depending on the situation at the + time of compilation. + + However, the distinction is becoming less clear. Modern compilers + often do test `if' statements when a program is compiled, if their + conditions are known not to vary at run time, and eliminate code which + can never be executed. If you can count on your compiler to do this, + you may find that your program is more readable if you use `if' + statements with constant conditions (perhaps determined by macros). Of + course, you can only use this to exclude code, not type definitions or + other preprocessing directives, and you can only do it if the code + remains syntactically valid when it is not to be used. + + GCC version 3 eliminates this kind of never-executed code even when + not optimizing. Older versions did it only when optimizing. + + * Menu: + + * Conditional Uses:: + * Conditional Syntax:: + * Deleted Code:: + +  + File: cpp.info, Node: Conditional Uses, Next: Conditional Syntax, Up: Conditionals + + Conditional Uses + ================ + + There are three general reasons to use a conditional. + + * A program may need to use different code depending on the machine + or operating system it is to run on. In some cases the code for + one operating system may be erroneous on another operating system; + for example, it might refer to data types or constants that do not + exist on the other system. When this happens, it is not enough to + avoid executing the invalid code. Its mere presence will cause + the compiler to reject the program. With a preprocessing + conditional, the offending code can be effectively excised from + the program when it is not valid. + + * You may want to be able to compile the same source file into two + different programs. One version might make frequent time-consuming + consistency checks on its intermediate data, or print the values of + those data for debugging, and the other not. + + * A conditional whose condition is always false is one way to + exclude code from the program but keep it as a sort of comment for + future reference. + + Simple programs that do not need system-specific logic or complex + debugging hooks generally will not need to use preprocessing + conditionals. + +  + File: cpp.info, Node: Conditional Syntax, Next: Deleted Code, Prev: Conditional Uses, Up: Conditionals + + Conditional Syntax + ================== + + A conditional in the C preprocessor begins with a "conditional + directive": `#if', `#ifdef' or `#ifndef'. + + * Menu: + + * Ifdef:: + * If:: + * Defined:: + * Else:: + * Elif:: + diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info-3 gcc-3.2.3/gcc/doc/cpp.info-3 *** gcc-3.2.2/gcc/doc/cpp.info-3 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info-3 Tue Apr 22 07:07:10 2003 *************** *** 0 **** --- 1,1103 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + File: cpp.info, Node: Ifdef, Next: If, Up: Conditional Syntax + + Ifdef + ----- + + The simplest sort of conditional is + + #ifdef MACRO + + CONTROLLED TEXT + + #endif /* MACRO */ + + This block is called a "conditional group". CONTROLLED TEXT will be + included in the output of the preprocessor if and only if MACRO is + defined. We say that the conditional "succeeds" if MACRO is defined, + "fails" if it is not. + + The CONTROLLED TEXT inside of a conditional can include + preprocessing directives. They are executed only if the conditional + succeeds. You can nest conditional groups inside other conditional + groups, but they must be completely nested. In other words, `#endif' + always matches the nearest `#ifdef' (or `#ifndef', or `#if'). Also, + you cannot start a conditional group in one file and end it in another. + + Even if a conditional fails, the CONTROLLED TEXT inside it is still + run through initial transformations and tokenization. Therefore, it + must all be lexically valid C. Normally the only way this matters is + that all comments and string literals inside a failing conditional group + must still be properly ended. + + The comment following the `#endif' is not required, but it is a good + practice if there is a lot of CONTROLLED TEXT, because it helps people + match the `#endif' to the corresponding `#ifdef'. Older programs + sometimes put MACRO directly after the `#endif' without enclosing it in + a comment. This is invalid code according to the C standard. GNU CPP + accepts it with a warning. It never affects which `#ifndef' the + `#endif' matches. + + Sometimes you wish to use some code if a macro is _not_ defined. + You can do this by writing `#ifndef' instead of `#ifdef'. One common + use of `#ifndef' is to include code only the first time a header file + is included. *Note Once-Only Headers::. + + Macro definitions can vary between compilations for several reasons. + Here are some samples. + + * Some macros are predefined on each kind of machine (*note + System-specific Predefined Macros::). This allows you to provide + code specially tuned for a particular machine. + + * System header files define more macros, associated with the + features they implement. You can test these macros with + conditionals to avoid using a system feature on a machine where it + is not implemented. + + * Macros can be defined or undefined with the `-D' and `-U' command + line options when you compile the program. You can arrange to + compile the same source file into two different programs by + choosing a macro name to specify which program you want, writing + conditionals to test whether or how this macro is defined, and + then controlling the state of the macro with command line options, + perhaps set in the Makefile. *Note Invocation::. + + * Your program might have a special header file (often called + `config.h') that is adjusted when the program is compiled. It can + define or not define macros depending on the features of the + system and the desired capabilities of the program. The + adjustment can be automated by a tool such as `autoconf', or done + by hand. + +  + File: cpp.info, Node: If, Next: Defined, Prev: Ifdef, Up: Conditional Syntax + + If + -- + + The `#if' directive allows you to test the value of an arithmetic + expression, rather than the mere existence of one macro. Its syntax is + + #if EXPRESSION + + CONTROLLED TEXT + + #endif /* EXPRESSION */ + + EXPRESSION is a C expression of integer type, subject to stringent + restrictions. It may contain + + * Integer constants. + + * Character constants, which are interpreted as they would be in + normal code. + + * Arithmetic operators for addition, subtraction, multiplication, + division, bitwise operations, shifts, comparisons, and logical + operations (`&&' and `||'). The latter two obey the usual + short-circuiting rules of standard C. + + * Macros. All macros in the expression are expanded before actual + computation of the expression's value begins. + + * Uses of the `defined' operator, which lets you check whether macros + are defined in the middle of an `#if'. + + * Identifiers that are not macros, which are all considered to be the + number zero. This allows you to write `#if MACRO' instead of + `#ifdef MACRO', if you know that MACRO, when defined, will always + have a nonzero value. Function-like macros used without their + function call parentheses are also treated as zero. + + In some contexts this shortcut is undesirable. The `-Wundef' + option causes GCC to warn whenever it encounters an identifier + which is not a macro in an `#if'. + + The preprocessor does not know anything about types in the language. + Therefore, `sizeof' operators are not recognized in `#if', and neither + are `enum' constants. They will be taken as identifiers which are not + macros, and replaced by zero. In the case of `sizeof', this is likely + to cause the expression to be invalid. + + The preprocessor calculates the value of EXPRESSION. It carries out + all calculations in the widest integer type known to the compiler; on + most machines supported by GCC this is 64 bits. This is not the same + rule as the compiler uses to calculate the value of a constant + expression, and may give different results in some cases. If the value + comes out to be nonzero, the `#if' succeeds and the CONTROLLED TEXT is + included; otherwise it is skipped. + + If EXPRESSION is not correctly formed, GCC issues an error and + treats the conditional as having failed. + +  + File: cpp.info, Node: Defined, Next: Else, Prev: If, Up: Conditional Syntax + + Defined + ------- + + The special operator `defined' is used in `#if' and `#elif' + expressions to test whether a certain name is defined as a macro. + `defined NAME' and `defined (NAME)' are both expressions whose value is + 1 if NAME is defined as a macro at the current point in the program, + and 0 otherwise. Thus, `#if defined MACRO' is precisely equivalent to + `#ifdef MACRO'. + + `defined' is useful when you wish to test more than one macro for + existence at once. For example, + + #if defined (__vax__) || defined (__ns16000__) + + would succeed if either of the names `__vax__' or `__ns16000__' is + defined as a macro. + + Conditionals written like this: + + #if defined BUFSIZE && BUFSIZE >= 1024 + + can generally be simplified to just `#if BUFSIZE >= 1024', since if + `BUFSIZE' is not defined, it will be interpreted as having the value + zero. + + If the `defined' operator appears as a result of a macro expansion, + the C standard says the behavior is undefined. GNU cpp treats it as a + genuine `defined' operator and evaluates it normally. It will warn + wherever your code uses this feature if you use the command-line option + `-pedantic', since other compilers may handle it differently. + +  + File: cpp.info, Node: Else, Next: Elif, Prev: Defined, Up: Conditional Syntax + + Else + ---- + + The `#else' directive can be added to a conditional to provide + alternative text to be used if the condition fails. This is what it + looks like: + + #if EXPRESSION + TEXT-IF-TRUE + #else /* Not EXPRESSION */ + TEXT-IF-FALSE + #endif /* Not EXPRESSION */ + + If EXPRESSION is nonzero, the TEXT-IF-TRUE is included and the + TEXT-IF-FALSE is skipped. If EXPRESSION is zero, the opposite happens. + + You can use `#else' with `#ifdef' and `#ifndef', too. + +  + File: cpp.info, Node: Elif, Prev: Else, Up: Conditional Syntax + + Elif + ---- + + One common case of nested conditionals is used to check for more + than two possible alternatives. For example, you might have + + #if X == 1 + ... + #else /* X != 1 */ + #if X == 2 + ... + #else /* X != 2 */ + ... + #endif /* X != 2 */ + #endif /* X != 1 */ + + Another conditional directive, `#elif', allows this to be + abbreviated as follows: + + #if X == 1 + ... + #elif X == 2 + ... + #else /* X != 2 and X != 1*/ + ... + #endif /* X != 2 and X != 1*/ + + `#elif' stands for "else if". Like `#else', it goes in the middle + of a conditional group and subdivides it; it does not require a + matching `#endif' of its own. Like `#if', the `#elif' directive + includes an expression to be tested. The text following the `#elif' is + processed only if the original `#if'-condition failed and the `#elif' + condition succeeds. + + More than one `#elif' can go in the same conditional group. Then + the text after each `#elif' is processed only if the `#elif' condition + succeeds after the original `#if' and all previous `#elif' directives + within it have failed. + + `#else' is allowed after any number of `#elif' directives, but + `#elif' may not follow `#else'. + +  + File: cpp.info, Node: Deleted Code, Prev: Conditional Syntax, Up: Conditionals + + Deleted Code + ============ + + If you replace or delete a part of the program but want to keep the + old code around for future reference, you often cannot simply comment it + out. Block comments do not nest, so the first comment inside the old + code will end the commenting-out. The probable result is a flood of + syntax errors. + + One way to avoid this problem is to use an always-false conditional + instead. For instance, put `#if 0' before the deleted code and + `#endif' after it. This works even if the code being turned off + contains conditionals, but they must be entire conditionals (balanced + `#if' and `#endif'). + + Some people use `#ifdef notdef' instead. This is risky, because + `notdef' might be accidentally defined as a macro, and then the + conditional would succeed. `#if 0' can be counted on to fail. + + Do not use `#if 0' for comments which are not C code. Use a real + comment, instead. The interior of `#if 0' must consist of complete + tokens; in particular, single-quote characters must balance. Comments + often contain unbalanced single-quote characters (known in English as + apostrophes). These confuse `#if 0'. They don't confuse `/*'. + +  + File: cpp.info, Node: Diagnostics, Next: Line Control, Prev: Conditionals, Up: Top + + Diagnostics + *********** + + The directive `#error' causes the preprocessor to report a fatal + error. The tokens forming the rest of the line following `#error' are + used as the error message. + + You would use `#error' inside of a conditional that detects a + combination of parameters which you know the program does not properly + support. For example, if you know that the program will not run + properly on a VAX, you might write + + #ifdef __vax__ + #error "Won't work on VAXen. See comments at get_last_object." + #endif + + If you have several configuration parameters that must be set up by + the installation in a consistent way, you can use conditionals to detect + an inconsistency and report it with `#error'. For example, + + #if !defined(UNALIGNED_INT_ASM_OP) && defined(DWARF2_DEBUGGING_INFO) + #error "DWARF2_DEBUGGING_INFO requires UNALIGNED_INT_ASM_OP." + #endif + + The directive `#warning' is like `#error', but causes the + preprocessor to issue a warning and continue preprocessing. The tokens + following `#warning' are used as the warning message. + + You might use `#warning' in obsolete header files, with a message + directing the user to the header file which should be used instead. + + Neither `#error' nor `#warning' macro-expands its argument. + Internal whitespace sequences are each replaced with a single space. + The line must consist of complete tokens. It is wisest to make the + argument of these directives be a single string constant; this avoids + problems with apostrophes and the like. + +  + File: cpp.info, Node: Line Control, Next: Pragmas, Prev: Diagnostics, Up: Top + + Line Control + ************ + + The C preprocessor informs the C compiler of the location in your + source code where each token came from. Presently, this is just the + file name and line number. All the tokens resulting from macro + expansion are reported as having appeared on the line of the source + file where the outermost macro was used. We intend to be more accurate + in the future. + + If you write a program which generates source code, such as the + `bison' parser generator, you may want to adjust the preprocessor's + notion of the current file name and line number by hand. Parts of the + output from `bison' are generated from scratch, other parts come from a + standard parser file. The rest are copied verbatim from `bison''s + input. You would like compiler error messages and symbolic debuggers + to be able to refer to `bison''s input file. + + `bison' or any such program can arrange this by writing `#line' + directives into the output file. `#line' is a directive that specifies + the original line number and source file name for subsequent input in + the current preprocessor input file. `#line' has three variants: + + `#line LINENUM' + LINENUM is a non-negative decimal integer constant. It specifies + the line number which should be reported for the following line of + input. Subsequent lines are counted from LINENUM. + + `#line LINENUM FILENAME' + LINENUM is the same as for the first form, and has the same + effect. In addition, FILENAME is a string constant. The + following line and all subsequent lines are reported to come from + the file it specifies, until something else happens to change that. + FILENAME is interpreted according to the normal rules for a string + constant: backslash escapes are interpreted. This is different + from `#include'. + + Previous versions of GNU CPP did not interpret escapes in `#line'; + we have changed it because the standard requires they be + interpreted, and most other compilers do. + + `#line ANYTHING ELSE' + ANYTHING ELSE is checked for macro calls, which are expanded. The + result should match one of the above two forms. + + `#line' directives alter the results of the `__FILE__' and + `__LINE__' predefined macros from that point on. *Note Standard + Predefined Macros::. They do not have any effect on `#include''s idea + of the directory containing the current file. This is a change from + GCC 2.95. Previously, a file reading + + #line 1 "../src/gram.y" + #include "gram.h" + + would search for `gram.h' in `../src', then the `-I' chain; the + directory containing the physical source file would not be searched. + In GCC 3.0 and later, the `#include' is not affected by the presence of + a `#line' referring to a different directory. + + We made this change because the old behavior caused problems when + generated source files were transported between machines. For instance, + it is common practice to ship generated parsers with a source release, + so that people building the distribution do not need to have yacc or + Bison installed. These files frequently have `#line' directives + referring to the directory tree of the system where the distribution was + created. If GCC tries to search for headers in those directories, the + build is likely to fail. + + The new behavior can cause failures too, if the generated file is not + in the same directory as its source and it attempts to include a header + which would be visible searching from the directory containing the + source file. However, this problem is easily solved with an additional + `-I' switch on the command line. The failures caused by the old + semantics could sometimes be corrected only by editing the generated + files, which is difficult and error-prone. + +  + File: cpp.info, Node: Pragmas, Next: Other Directives, Prev: Line Control, Up: Top + + Pragmas + ******* + + The `#pragma' directive is the method specified by the C standard + for providing additional information to the compiler, beyond what is + conveyed in the language itself. Three forms of this directive + (commonly known as "pragmas") are specified by the 1999 C standard. A + C compiler is free to attach any meaning it likes to other pragmas. + + GCC has historically preferred to use extensions to the syntax of the + language, such as `__attribute__', for this purpose. However, GCC does + define a few pragmas of its own. These mostly have effects on the + entire translation unit or source file. + + In GCC version 3, all GNU-defined, supported pragmas have been given + a `GCC' prefix. This is in line with the `STDC' prefix on all pragmas + defined by C99. For backward compatibility, pragmas which were + recognized by previous versions are still recognized without the `GCC' + prefix, but that usage is deprecated. Some older pragmas are + deprecated in their entirety. They are not recognized with the `GCC' + prefix. *Note Obsolete Features::. + + C99 introduces the `_Pragma' operator. This feature addresses a + major problem with `#pragma': being a directive, it cannot be produced + as the result of macro expansion. `_Pragma' is an operator, much like + `sizeof' or `defined', and can be embedded in a macro. + + Its syntax is `_Pragma (STRING-LITERAL)', where STRING-LITERAL can + be either a normal or wide-character string literal. It is + destringized, by replacing all `\\' with a single `\' and all `\"' with + a `"'. The result is then processed as if it had appeared as the right + hand side of a `#pragma' directive. For example, + + _Pragma ("GCC dependency \"parse.y\"") + + has the same effect as `#pragma GCC dependency "parse.y"'. The same + effect could be achieved using macros, for example + + #define DO_PRAGMA(x) _Pragma (#x) + DO_PRAGMA (GCC dependency "parse.y") + + The standard is unclear on where a `_Pragma' operator can appear. + The preprocessor does not accept it within a preprocessing conditional + directive like `#if'. To be safe, you are probably best keeping it out + of directives other than `#define', and putting it on a line of its own. + + This manual documents the pragmas which are meaningful to the + preprocessor itself. Other pragmas are meaningful to the C or C++ + compilers. They are documented in the GCC manual. + + `#pragma GCC dependency' + `#pragma GCC dependency' allows you to check the relative dates of + the current file and another file. If the other file is more + recent than the current file, a warning is issued. This is useful + if the current file is derived from the other file, and should be + regenerated. The other file is searched for using the normal + include search path. Optional trailing text can be used to give + more information in the warning message. + + #pragma GCC dependency "parse.y" + #pragma GCC dependency "/usr/include/time.h" rerun fixincludes + + `#pragma GCC poison' + Sometimes, there is an identifier that you want to remove + completely from your program, and make sure that it never creeps + back in. To enforce this, you can "poison" the identifier with + this pragma. `#pragma GCC poison' is followed by a list of + identifiers to poison. If any of those identifiers appears + anywhere in the source after the directive, it is a hard error. + For example, + + #pragma GCC poison printf sprintf fprintf + sprintf(some_string, "hello"); + + will produce an error. + + If a poisoned identifier appears as part of the expansion of a + macro which was defined before the identifier was poisoned, it + will _not_ cause an error. This lets you poison an identifier + without worrying about system headers defining macros that use it. + + For example, + + #define strrchr rindex + #pragma GCC poison rindex + strrchr(some_string, 'h'); + + will not produce an error. + + `#pragma GCC system_header' + This pragma takes no arguments. It causes the rest of the code in + the current file to be treated as if it came from a system header. + *Note System Headers::. + + +  + File: cpp.info, Node: Other Directives, Next: Preprocessor Output, Prev: Pragmas, Up: Top + + Other Directives + **************** + + The `#ident' directive takes one argument, a string constant. On + some systems, that string constant is copied into a special segment of + the object file. On other systems, the directive is ignored. + + This directive is not part of the C standard, but it is not an + official GNU extension either. We believe it came from System V. + + The `#sccs' directive is recognized on some systems, because it + appears in their header files. It is a very old, obscure, extension + which we did not invent, and we have been unable to find any + documentation of what it should do, so GCC simply ignores it. + + The "null directive" consists of a `#' followed by a newline, with + only whitespace (including comments) in between. A null directive is + understood as a preprocessing directive but has no effect on the + preprocessor output. The primary significance of the existence of the + null directive is that an input line consisting of just a `#' will + produce no output, rather than a line of output containing just a `#'. + Supposedly some old C programs contain such lines. + +  + File: cpp.info, Node: Preprocessor Output, Next: Traditional Mode, Prev: Other Directives, Up: Top + + Preprocessor Output + ******************* + + When the C preprocessor is used with the C, C++, or Objective-C + compilers, it is integrated into the compiler and communicates a stream + of binary tokens directly to the compiler's parser. However, it can + also be used in the more conventional standalone mode, where it produces + textual output. + + The output from the C preprocessor looks much like the input, except + that all preprocessing directive lines have been replaced with blank + lines and all comments with spaces. Long runs of blank lines are + discarded. + + The ISO standard specifies that it is implementation defined whether + a preprocessor preserves whitespace between tokens, or replaces it with + e.g. a single space. In GNU CPP, whitespace between tokens is collapsed + to become a single space, with the exception that the first token on a + non-directive line is preceded with sufficient spaces that it appears in + the same column in the preprocessed output that it appeared in the + original source file. This is so the output is easy to read. *Note + Differences from previous versions::. CPP does not insert any + whitespace where there was none in the original source, except where + necessary to prevent an accidental token paste. + + Source file name and line number information is conveyed by lines of + the form + + # LINENUM FILENAME FLAGS + + These are called "linemarkers". They are inserted as needed into the + output (but never within a string or character constant). They mean + that the following line originated in file FILENAME at line LINENUM. + FILENAME will never contain any non-printing characters; they are + replaced with octal escape sequences. + + After the file name comes zero or more flags, which are `1', `2', + `3', or `4'. If there are multiple flags, spaces separate them. Here + is what the flags mean: + + `1' + This indicates the start of a new file. + + `2' + This indicates returning to a file (after having included another + file). + + `3' + This indicates that the following text comes from a system header + file, so certain warnings should be suppressed. + + `4' + This indicates that the following text should be treated as being + wrapped in an implicit `extern "C"' block. + + As an extension, the preprocessor accepts linemarkers in + non-assembler input files. They are treated like the corresponding + `#line' directive, (*note Line Control::), except that trailing flags + are permitted, and are interpreted with the meanings described above. + If multiple flags are given, they must be in ascending order. + + Some directives may be duplicated in the output of the preprocessor. + These are `#ident' (always), `#pragma' (only if the preprocessor does + not handle the pragma itself), and `#define' and `#undef' (with certain + debugging options). If this happens, the `#' of the directive will + always be in the first column, and there will be no space between the + `#' and the directive name. If macro expansion happens to generate + tokens which might be mistaken for a duplicated directive, a space will + be inserted between the `#' and the directive name. + +  + File: cpp.info, Node: Traditional Mode, Next: Implementation Details, Prev: Preprocessor Output, Up: Top + + Traditional Mode + **************** + + Traditional (pre-standard) C preprocessing is rather different from + the preprocessing specified by the standard. When GCC is given the + `-traditional' option, it attempts to emulate a traditional + preprocessor. We do not guarantee that GCC's behavior under + `-traditional' matches any pre-standard preprocessor exactly. + + Traditional mode exists only for backward compatibility. We have no + plans to augment it in any way nor will we change it except to fix + catastrophic bugs. You should be aware that modern C libraries often + have header files which are incompatible with traditional mode. + + This is a list of the differences. It may not be complete, and may + not correspond exactly to the behavior of either GCC or a true + traditional preprocessor. + + * Traditional macro expansion pays no attention to single-quote or + double-quote characters; macro argument symbols are replaced by the + argument values even when they appear within apparent string or + character constants. + + * Traditionally, it is permissible for a macro expansion to end in + the middle of a string or character constant. The constant + continues into the text surrounding the macro call. + + * However, the end of the line terminates a string or character + constant, with no error. (This is a kluge. Traditional mode is + commonly used to preprocess things which are not C, and have a + different comment syntax. Single apostrophes often appear in + comments. This kluge prevents the traditional preprocessor from + issuing errors on such comments.) + + * Preprocessing directives are recognized in traditional C only when + their leading `#' appears in the first column. There can be no + whitespace between the beginning of the line and the `#'. + + * In traditional C, a comment is equivalent to no text at all. (In + ISO C, a comment counts as whitespace.) It can be used sort of + the same way that `##' is used in ISO C, to paste macro arguments + together. + + * Traditional C does not have the concept of a preprocessing number. + + * A macro is not suppressed within its own definition, in + traditional C. Thus, any macro that is used recursively + inevitably causes an error. + + * The `#' and `##' operators are not available in traditional C. + + * In traditional C, the text at the end of a macro expansion can run + together with the text after the macro call, to produce a single + token. This is impossible in ISO C. + + * None of the GNU extensions to the preprocessor are available in + traditional mode, with the exception of a partial implementation of + assertions, and those may be removed in the future. + + * A true traditional C preprocessor does not recognize `#elif', + `#error', or `#pragma'. GCC supports `#elif' and `#error' even in + traditional mode, but not `#pragma'. + + * Traditional mode is text-based, not token-based, and comments are + stripped after macro expansion. Therefore, `/**/' can be used to + paste tokens together provided that there is no whitespace between + it and the tokens to be pasted. + + * Traditional mode preserves the amount and form of whitespace + provided by the user. Hard tabs remain hard tabs. This can be + useful, e.g. if you are preprocessing a Makefile (which we do not + encourage). + + You can request warnings about features that did not exist, or worked + differently, in traditional C with the `-Wtraditional' option. This + works only if you do _not_ specify `-traditional'. GCC does not warn + about features of ISO C which you must use when you are using a + conforming compiler, such as the `#' and `##' operators. + + Presently `-Wtraditional' warns about: + + * Macro parameters that appear within string literals in the macro + body. In traditional C macro replacement takes place within + string literals, but does not in ISO C. + + * In traditional C, some preprocessor directives did not exist. + Traditional preprocessors would only consider a line to be a + directive if the `#' appeared in column 1 on the line. Therefore + `-Wtraditional' warns about directives that traditional C + understands but would ignore because the `#' does not appear as the + first character on the line. It also suggests you hide directives + like `#pragma' not understood by traditional C by indenting them. + Some traditional implementations would not recognize `#elif', so it + suggests avoiding it altogether. + + * A function-like macro that appears without an argument list. In + traditional C this was an error. In ISO C it merely means that the + macro is not expanded. + + * The unary plus operator. This did not exist in traditional C. + + * The `U' and `LL' integer constant suffixes, which were not + available in traditional C. (Traditional C does support the `L' + suffix for simple long integer constants.) You are not warned + about uses of these suffixes in macros defined in system headers. + For instance, `UINT_MAX' may well be defined as `4294967295U', but + you will not be warned if you use `UINT_MAX'. + + You can usually avoid the warning, and the related warning about + constants which are so large that they are unsigned, by writing the + integer constant in question in hexadecimal, with no U suffix. + Take care, though, because this gives the wrong result in exotic + cases. + +  + File: cpp.info, Node: Implementation Details, Next: Invocation, Prev: Traditional Mode, Up: Top + + Implementation Details + ********************** + + Here we document details of how the preprocessor's implementation + affects its user-visible behavior. You should try to avoid undue + reliance on behavior described here, as it is possible that it will + change subtly in future implementations. + + Also documented here are obsolete features and changes from previous + versions of GNU CPP. + + * Menu: + + * Implementation-defined behavior:: + * Implementation limits:: + * Obsolete Features:: + * Differences from previous versions:: + +  + File: cpp.info, Node: Implementation-defined behavior, Next: Implementation limits, Up: Implementation Details + + Implementation-defined behavior + =============================== + + This is how GNU CPP behaves in all the cases which the C standard + describes as "implementation-defined". This term means that the + implementation is free to do what it likes, but must document its choice + and stick to it. + + * The mapping of physical source file multi-byte characters to the + execution character set. + + Currently, GNU cpp only supports character sets that are strict + supersets of ASCII, and performs no translation of characters. + + * Non-empty sequences of whitespace characters. + + In textual output, each whitespace sequence is collapsed to a + single space. For aesthetic reasons, the first token on each + non-directive line of output is preceded with sufficient spaces + that it appears in the same column as it did in the original + source file. + + * The numeric value of character constants in preprocessor + expressions. + + The preprocessor and compiler interpret character constants in the + same way; escape sequences such as `\a' are given the values they + would have on the target machine. + + Multi-character character constants are interpreted a character at + a time, shifting the previous result left by the number of bits per + character on the host, and adding the new character. For example, + 'ab' on an 8-bit host would be interpreted as 'a' * 256 + 'b'. If + there are more characters in the constant than can fit in the + widest native integer type on the host, usually a `long', the + excess characters are ignored and a diagnostic is given. + + * Source file inclusion. + + For a discussion on how the preprocessor locates header files, + *Note Include Operation::. + + * Interpretation of the filename resulting from a macro-expanded + `#include' directive. + + *Note Computed Includes::. + + * Treatment of a `#pragma' directive that after macro-expansion + results in a standard pragma. + + No macro expansion occurs on any `#pragma' directive line, so the + question does not arise. + + Note that GCC does not yet implement any of the standard pragmas. + + +  + File: cpp.info, Node: Implementation limits, Next: Obsolete Features, Prev: Implementation-defined behavior, Up: Implementation Details + + Implementation limits + ===================== + + GNU CPP has a small number of internal limits. This section lists + the limits which the C standard requires to be no lower than some + minimum, and all the others we are aware of. We intend there to be as + few limits as possible. If you encounter an undocumented or + inconvenient limit, please report that to us as a bug. (See the + section on reporting bugs in the GCC manual.) + + Where we say something is limited "only by available memory", that + means that internal data structures impose no intrinsic limit, and space + is allocated with `malloc' or equivalent. The actual limit will + therefore depend on many things, such as the size of other things + allocated by the compiler at the same time, the amount of memory + consumed by other processes on the same computer, etc. + + * Nesting levels of `#include' files. + + We impose an arbitrary limit of 200 levels, to avoid runaway + recursion. The standard requires at least 15 levels. + + * Nesting levels of conditional inclusion. + + The C standard mandates this be at least 63. GNU CPP is limited + only by available memory. + + * Levels of parenthesised expressions within a full expression. + + The C standard requires this to be at least 63. In preprocessor + conditional expressions, it is limited only by available memory. + + * Significant initial characters in an identifier or macro name. + + The preprocessor treats all characters as significant. The C + standard requires only that the first 63 be significant. + + * Number of macros simultaneously defined in a single translation + unit. + + The standard requires at least 4095 be possible. GNU CPP is + limited only by available memory. + + * Number of parameters in a macro definition and arguments in a + macro call. + + We allow `USHRT_MAX', which is no smaller than 65,535. The minimum + required by the standard is 127. + + * Number of characters on a logical source line. + + The C standard requires a minimum of 4096 be permitted. GNU CPP + places no limits on this, but you may get incorrect column numbers + reported in diagnostics for lines longer than 65,535 characters. + + * Maximum size of a source file. + + The standard does not specify any lower limit on the maximum size + of a source file. GNU cpp maps files into memory, so it is + limited by the available address space. This is generally at + least two gigabytes. Depending on the operating system, the size + of physical memory may or may not be a limitation. + + +  + File: cpp.info, Node: Obsolete Features, Next: Differences from previous versions, Prev: Implementation limits, Up: Implementation Details + + Obsolete Features + ================= + + GNU CPP has a number of features which are present mainly for + compatibility with older programs. We discourage their use in new code. + In some cases, we plan to remove the feature in a future version of GCC. + + * Menu: + + * Assertions:: + * Obsolete once-only headers:: + * Miscellaneous obsolete features:: + +  + File: cpp.info, Node: Assertions, Next: Obsolete once-only headers, Up: Obsolete Features + + Assertions + ---------- + + "Assertions" are a deprecated alternative to macros in writing + conditionals to test what sort of computer or system the compiled + program will run on. Assertions are usually predefined, but you can + define them with preprocessing directives or command-line options. + + Assertions were intended to provide a more systematic way to describe + the compiler's target system. However, in practice they are just as + unpredictable as the system-specific predefined macros. In addition, + they are not part of any standard, and only a few compilers support + them. Therefore, the use of assertions is *less* portable than the use + of system-specific predefined macros. We recommend you do not use them + at all. + + An assertion looks like this: + + #PREDICATE (ANSWER) + + PREDICATE must be a single identifier. ANSWER can be any sequence of + tokens; all characters are significant except for leading and trailing + whitespace, and differences in internal whitespace sequences are + ignored. (This is similar to the rules governing macro redefinition.) + Thus, `(x + y)' is different from `(x+y)' but equivalent to + `( x + y )'. Parentheses do not nest inside an answer. + + To test an assertion, you write it in an `#if'. For example, this + conditional succeeds if either `vax' or `ns16000' has been asserted as + an answer for `machine'. + + #if #machine (vax) || #machine (ns16000) + + You can test whether _any_ answer is asserted for a predicate by + omitting the answer in the conditional: + + #if #machine + + Assertions are made with the `#assert' directive. Its sole argument + is the assertion to make, without the leading `#' that identifies + assertions in conditionals. + + #assert PREDICATE (ANSWER) + + You may make several assertions with the same predicate and different + answers. Subsequent assertions do not override previous ones for the + same predicate. All the answers for any given predicate are + simultaneously true. + + Assertions can be cancelled with the `#unassert' directive. It has + the same syntax as `#assert'. In that form it cancels only the answer + which was specified on the `#unassert' line; other answers for that + predicate remain true. You can cancel an entire predicate by leaving + out the answer: + + #unassert PREDICATE + + In either form, if no such assertion has been made, `#unassert' has no + effect. + + You can also make or cancel assertions using command line options. + *Note Invocation::. + +  + File: cpp.info, Node: Obsolete once-only headers, Next: Miscellaneous obsolete features, Prev: Assertions, Up: Obsolete Features + + Obsolete once-only headers + -------------------------- + + GNU CPP supports two more ways of indicating that a header file + should be read only once. Neither one is as portable as a wrapper + `#ifndef', and we recommend you do not use them in new programs. + + In the Objective-C language, there is a variant of `#include' called + `#import' which includes a file, but does so at most once. If you use + `#import' instead of `#include', then you don't need the conditionals + inside the header file to prevent multiple inclusion of the contents. + GCC permits the use of `#import' in C and C++ as well as Objective-C. + However, it is not in standard C or C++ and should therefore not be + used by portable programs. + + `#import' is not a well designed feature. It requires the users of + a header file to know that it should only be included once. It is much + better for the header file's implementor to write the file so that users + don't need to know this. Using a wrapper `#ifndef' accomplishes this + goal. + + In the present implementation, a single use of `#import' will + prevent the file from ever being read again, by either `#import' or + `#include'. You should not rely on this; do not use both `#import' and + `#include' to refer to the same header file. + + Another way to prevent a header file from being included more than + once is with the `#pragma once' directive. If `#pragma once' is seen + when scanning a header file, that file will never be read again, no + matter what. + + `#pragma once' does not have the problems that `#import' does, but + it is not recognized by all preprocessors, so you cannot rely on it in + a portable program. + +  + File: cpp.info, Node: Miscellaneous obsolete features, Prev: Obsolete once-only headers, Up: Obsolete Features + + Miscellaneous obsolete features + ------------------------------- + + Here are a few more obsolete features. + + * Attempting to paste two tokens which together do not form a valid + preprocessing token. + + The preprocessor currently warns about this, and the resulting + preprocessed output is undefined. The tokens remain distinct if + the preprocessor is being used directly by the compiler front end. + + Most of the time, when you get this warning, you will find that + `##' is being used superstitiously, to guard against whitespace + appearing between two tokens. It is almost always safe to delete + the `##'. + + * `#pragma poison' + + This is the same as `#pragma GCC poison'. The version without the + `GCC' prefix is deprecated. *Note Pragmas::. + + * Multi-line string constants + + GCC currently allows a string constant to extend across multiple + logical lines of the source file. This extension is deprecated + and will be removed in a future version of GCC. Such string + constants are already rejected in all directives apart from + `#define'. + + Instead, make use of ISO C concatenation of adjacent string + literals, or use `\n' followed by a backslash-newline. + + +  + File: cpp.info, Node: Differences from previous versions, Prev: Obsolete Features, Up: Implementation Details + + Differences from previous versions + ================================== + + This section details behavior which has changed from previous + versions of GNU CPP. We do not plan to change it again in the near + future, but we do not promise not to, either. + + The "previous versions" discussed here are 2.95 and before. The + behavior of GCC 3.0 is mostly the same as the behavior of the widely + used 2.96 and 2.97 development snapshots. Where there are differences, + they generally represent bugs in the snapshots. + + * Order of evaluation of `#' and `##' operators + + The standard does not specify the order of evaluation of a chain of + `##' operators, nor whether `#' is evaluated before, after, or at + the same time as `##'. You should therefore not write any code + which depends on any specific ordering. It is possible to + guarantee an ordering, if you need one, by suitable use of nested + macros. + + An example of where this might matter is pasting the arguments `1', + `e' and `-2'. This would be fine for left-to-right pasting, but + right-to-left pasting would produce an invalid token `e-2'. + + GCC 3.0 evaluates `#' and `##' at the same time and strictly left + to right. Older versions evaluated all `#' operators first, then + all `##' operators, in an unreliable order. + + * The form of whitespace betwen tokens in preprocessor output + + *Note Preprocessor Output::, for the current textual format. This + is also the format used by stringification. Normally, the + preprocessor communicates tokens directly to the compiler's + parser, and whitespace does not come up at all. + + Older versions of GCC preserved all whitespace provided by the + user and inserted lots more whitespace of their own, because they + could not accurately predict when extra spaces were needed to + prevent accidental token pasting. + + * Optional argument when invoking rest argument macros + + As an extension, GCC permits you to omit the variable arguments + entirely when you use a variable argument macro. This is + forbidden by the 1999 C standard, and will provoke a pedantic + warning with GCC 3.0. Previous versions accepted it silently. + + * `##' swallowing preceding text in rest argument macros + + Formerly, in a macro expansion, if `##' appeared before a variable + arguments parameter, and the set of tokens specified for that + argument in the macro invocation was empty, previous versions of + GNU CPP would back up and remove the preceding sequence of + non-whitespace characters (*not* the preceding token). This + extension is in direct conflict with the 1999 C standard and has + been drastically pared back. + + In the current version of the preprocessor, if `##' appears between + a comma and a variable arguments parameter, and the variable + argument is omitted entirely, the comma will be removed from the + expansion. If the variable argument is empty, or the token before + `##' is not a comma, then `##' behaves as a normal token paste. + + * Traditional mode and GNU extensions + + Traditional mode used to be implemented in the same program as + normal preprocessing. Therefore, all the GNU extensions to the + preprocessor were still available in traditional mode. It is now + a separate program and does not implement any of the GNU + extensions, except for a partial implementation of assertions. + Even those may be removed in a future release. + + * `#line' and `#include' + + The `#line' directive used to change GCC's notion of the + "directory containing the current file," used by `#include' with a + double-quoted header file name. In 3.0 and later, it does not. + *Note Line Control::, for further explanation. + + * Syntax of `#line' + + In GCC 2.95 and previous, the string constant argument to `#line' + was treated the same way as the argument to `#include': backslash + escapes were not honored, and the string ended at the second `"'. + This is not compliant with the C standard. In GCC 3.0, an attempt + was made to correct the behavior, so that the string was treated + as a real string constant, but it turned out to be buggy. In 3.1, + the bugs have been fixed. (We are not fixing the bugs in 3.0 + because they affect relatively few people and the fix is quite + invasive.) + + diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info-4 gcc-3.2.3/gcc/doc/cpp.info-4 *** gcc-3.2.2/gcc/doc/cpp.info-4 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info-4 Tue Apr 22 07:07:10 2003 *************** *** 0 **** --- 1,1054 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + File: cpp.info, Node: Invocation, Next: Environment Variables, Prev: Implementation Details, Up: Top + + Invocation + ********** + + Most often when you use the C preprocessor you will not have to + invoke it explicitly: the C compiler will do so automatically. + However, the preprocessor is sometimes useful on its own. All the + options listed here are also acceptable to the C compiler and have the + same meaning, except that the C compiler has different rules for + specifying the output file. + + *Note:* Whether you use the preprocessor by way of `gcc' or `cpp', + the "compiler driver" is run first. This program's purpose is to + translate your command into invocations of the programs that do the + actual work. Their command line interfaces are similar but not + identical to the documented interface, and may change without notice. + + The C preprocessor expects two file names as arguments, INFILE and + OUTFILE. The preprocessor reads INFILE together with any other files + it specifies with `#include'. All the output generated by the combined + input files is written in OUTFILE. + + Either INFILE or OUTFILE may be `-', which as INFILE means to read + from standard input and as OUTFILE means to write to standard output. + Also, if either file is omitted, it means the same as if `-' had been + specified for that file. + + Unless otherwise noted, or the option ends in `=', all options which + take an argument may have that argument appear either immediately after + the option, or with a space between option and argument: `-Ifoo' and + `-I foo' have the same effect. + + Many options have multi-letter names; therefore multiple + single-letter options may _not_ be grouped: `-dM' is very different from + `-d -M'. + + `-D NAME' + Predefine NAME as a macro, with definition `1'. + + `-D NAME=DEFINITION' + Predefine NAME as a macro, with definition DEFINITION. There are + no restrictions on the contents of DEFINITION, but if you are + invoking the preprocessor from a shell or shell-like program you + may need to use the shell's quoting syntax to protect characters + such as spaces that have a meaning in the shell syntax. + + If you wish to define a function-like macro on the command line, + write its argument list with surrounding parentheses before the + equals sign (if any). Parentheses are meaningful to most shells, + so you will need to quote the option. With `sh' and `csh', + `-D'NAME(ARGS...)=DEFINITION'' works. + + `-D' and `-U' options are processed in the order they are given on + the command line. All `-imacros FILE' and `-include FILE' options + are processed after all `-D' and `-U' options. + + `-U NAME' + Cancel any previous definition of NAME, either built in or + provided with a `-D' option. + + `-undef' + Do not predefine any system-specific macros. The common predefined + macros remain defined. + + `-I DIR' + Add the directory DIR to the list of directories to be searched + for header files. *Note Search Path::. Directories named by `-I' + are searched before the standard system include directories. + + It is dangerous to specify a standard system include directory in + an `-I' option. This defeats the special treatment of system + headers (*note System Headers::) . It can also defeat the repairs + to buggy system headers which GCC makes when it is installed. + + `-o FILE' + Write output to FILE. This is the same as specifying FILE as the + second non-option argument to `cpp'. `gcc' has a different + interpretation of a second non-option argument, so you must use + `-o' to specify the output file. + + `-Wall' + Turns on all optional warnings which are desirable for normal + code. At present this is `-Wcomment' and `-Wtrigraphs'. Note that + many of the preprocessor's warnings are on by default and have no + options to control them. + + `-Wcomment' + `-Wcomments' + Warn whenever a comment-start sequence `/*' appears in a `/*' + comment, or whenever a backslash-newline appears in a `//' comment. + (Both forms have the same effect.) + + `-Wtrigraphs' + Warn if any trigraphs are encountered. This option used to take + effect only if `-trigraphs' was also specified, but now works + independently. Warnings are not given for trigraphs within + comments, as they do not affect the meaning of the program. + + `-Wtraditional' + Warn about certain constructs that behave differently in + traditional and ISO C. Also warn about ISO C constructs that have + no traditional C equivalent, and problematic constructs which + should be avoided. *Note Traditional Mode::. + + `-Wimport' + Warn the first time `#import' is used. + + `-Wundef' + Warn whenever an identifier which is not a macro is encountered in + an `#if' directive, outside of `defined'. Such identifiers are + replaced with zero. + + `-Werror' + Make all warnings into hard errors. Source code which triggers + warnings will be rejected. + + `-Wsystem-headers' + Issue warnings for code in system headers. These are normally + unhelpful in finding bugs in your own code, therefore suppressed. + If you are responsible for the system library, you may want to see + them. + + `-w' + Suppress all warnings, including those which GNU CPP issues by + default. + + `-pedantic' + Issue all the mandatory diagnostics listed in the C standard. + Some of them are left out by default, since they trigger + frequently on harmless code. + + `-pedantic-errors' + Issue all the mandatory diagnostics, and make all mandatory + diagnostics into errors. This includes mandatory diagnostics that + GCC issues without `-pedantic' but treats as warnings. + + `-M' + Instead of outputting the result of preprocessing, output a rule + suitable for `make' describing the dependencies of the main source + file. The preprocessor outputs one `make' rule containing the + object file name for that source file, a colon, and the names of + all the included files, including those coming from `-include' or + `-imacros' command line options. + + Unless specified explicitly (with `-MT' or `-MQ'), the object file + name consists of the basename of the source file with any suffix + replaced with object file suffix. If there are many included + files then the rule is split into several lines using `\'-newline. + The rule has no commands. + + This option does not suppress the preprocessor's debug output, + such as `-dM'. To avoid mixing such debug output with the + dependency rules you should explicitly specify the dependency + output file with `-MF', or use an environment variable like + `DEPENDENCIES_OUTPUT' (*note DEPENDENCIES_OUTPUT::). Debug output + will still be sent to the regular output stream as normal. + + Passing `-M' to the driver implies `-E'. + + `-MM' + Like `-M' but do not mention header files that are found in system + header directories, nor header files that are included, directly + or indirectly, from such a header. + + This implies that the choice of angle brackets or double quotes in + an `#include' directive does not in itself determine whether that + header will appear in `-MM' dependency output. This is a slight + change in semantics from GCC versions 3.0 and earlier. + + `-MF FILE' + When used with `-M' or `-MM', specifies a file to write the + dependencies to. If no `-MF' switch is given the preprocessor + sends the rules to the same place it would have sent preprocessed + output. + + When used with the driver options `-MD' or `-MMD', `-MF' overrides + the default dependency output file. + + `-MG' + When used with `-M' or `-MM', `-MG' says to treat missing header + files as generated files and assume they live in the same + directory as the source file. It suppresses preprocessed output, + as a missing header file is ordinarily an error. + + This feature is used in automatic updating of makefiles. + + `-MP' + This option instructs CPP to add a phony target for each dependency + other than the main file, causing each to depend on nothing. These + dummy rules work around errors `make' gives if you remove header + files without updating the `Makefile' to match. + + This is typical output: + + test.o: test.c test.h + + test.h: + + `-MT TARGET' + Change the target of the rule emitted by dependency generation. By + default CPP takes the name of the main input file, including any + path, deletes any file suffix such as `.c', and appends the + platform's usual object suffix. The result is the target. + + An `-MT' option will set the target to be exactly the string you + specify. If you want multiple targets, you can specify them as a + single argument to `-MT', or use multiple `-MT' options. + + For example, `-MT '$(objpfx)foo.o'' might give + + $(objpfx)foo.o: foo.c + + `-MQ TARGET' + Same as `-MT', but it quotes any characters which are special to + Make. `-MQ '$(objpfx)foo.o'' gives + + $$(objpfx)foo.o: foo.c + + The default target is automatically quoted, as if it were given + with `-MQ'. + + `-MD' + `-MD' is equivalent to `-M -MF FILE', except that `-E' is not + implied. The driver determines FILE based on whether an `-o' + option is given. If it is, the driver uses its argument but with + a suffix of `.d', otherwise it take the basename of the input file + and applies a `.d' suffix. + + If `-MD' is used in conjunction with `-E', any `-o' switch is + understood to specify the dependency output file (but *note + -MF::), but if used without `-E', each `-o' is understood to + specify a target object file. + + Since `-E' is not implied, `-MD' can be used to generate a + dependency output file as a side-effect of the compilation process. + + `-MMD' + Like `-MD' except mention only user header files, not system + -header files. + + `-x c' + `-x c++' + `-x objective-c' + `-x assembler-with-cpp' + Specify the source language: C, C++, Objective-C, or assembly. + This has nothing to do with standards conformance or extensions; + it merely selects which base syntax to expect. If you give none + of these options, cpp will deduce the language from the extension + of the source file: `.c', `.cc', `.m', or `.S'. Some other common + extensions for C++ and assembly are also recognized. If cpp does + not recognize the extension, it will treat the file as C; this is + the most generic mode. + + *Note:* Previous versions of cpp accepted a `-lang' option which + selected both the language and the standards conformance level. + This option has been removed, because it conflicts with the `-l' + option. + + `-std=STANDARD' + `-ansi' + Specify the standard to which the code should conform. Currently + cpp only knows about the standards for C; other language standards + will be added in the future. + + STANDARD may be one of: + `iso9899:1990' + `c89' + The ISO C standard from 1990. `c89' is the customary + shorthand for this version of the standard. + + The `-ansi' option is equivalent to `-std=c89'. + + `iso9899:199409' + The 1990 C standard, as amended in 1994. + + `iso9899:1999' + `c99' + `iso9899:199x' + `c9x' + The revised ISO C standard, published in December 1999. + Before publication, this was known as C9X. + + `gnu89' + The 1990 C standard plus GNU extensions. This is the default. + + `gnu99' + `gnu9x' + The 1999 C standard plus GNU extensions. + + `-I-' + Split the include path. Any directories specified with `-I' + options before `-I-' are searched only for headers requested with + `#include "FILE"'; they are not searched for `#include '. + If additional directories are specified with `-I' options after + the `-I-', those directories are searched for all `#include' + directives. + + In addition, `-I-' inhibits the use of the directory of the current + file directory as the first search directory for `#include "FILE"'. + *Note Search Path::. + + `-nostdinc' + Do not search the standard system directories for header files. + Only the directories you have specified with `-I' options (and the + directory of the current file, if appropriate) are searched. + + `-nostdinc++' + Do not search for header files in the C++-specific standard + directories, but do still search the other standard directories. + (This option is used when building the C++ library.) + + `-include FILE' + Process FILE as if `#include "file"' appeared as the first line of + the primary source file. However, the first directory searched + for FILE is the preprocessor's working directory _instead of_ the + directory containing the main source file. If not found there, it + is searched for in the remainder of the `#include "..."' search + chain as normal. + + If multiple `-include' options are given, the files are included + in the order they appear on the command line. + + `-imacros FILE' + Exactly like `-include', except that any output produced by + scanning FILE is thrown away. Macros it defines remain defined. + This allows you to acquire all the macros from a header without + also processing its declarations. + + All files specified by `-imacros' are processed before all files + specified by `-include'. + + `-idirafter DIR' + Search DIR for header files, but do it _after_ all directories + specified with `-I' and the standard system directories have been + exhausted. DIR is treated as a system include directory. + + `-iprefix PREFIX' + Specify PREFIX as the prefix for subsequent `-iwithprefix' + options. If the prefix represents a directory, you should include + the final `/'. + + `-iwithprefix DIR' + `-iwithprefixbefore DIR' + Append DIR to the prefix specified previously with `-iprefix', and + add the resulting directory to the include search path. + `-iwithprefixbefore' puts it in the same place `-I' would; + `-iwithprefix' puts it where `-idirafter' would. + + Use of these options is discouraged. + + `-isystem DIR' + Search DIR for header files, after all directories specified by + `-I' but before the standard system directories. Mark it as a + system directory, so that it gets the same special treatment as is + applied to the standard system directories. *Note System + Headers::. + + `-fpreprocessed' + Indicate to the preprocessor that the input file has already been + preprocessed. This suppresses things like macro expansion, + trigraph conversion, escaped newline splicing, and processing of + most directives. The preprocessor still recognizes and removes + comments, so that you can pass a file preprocessed with `-C' to + the compiler without problems. In this mode the integrated + preprocessor is little more than a tokenizer for the front ends. + + `-fpreprocessed' is implicit if the input file has one of the + extensions `.i', `.ii' or `.mi'. These are the extensions that + GCC uses for preprocessed files created by `-save-temps'. + + `-ftabstop=WIDTH' + Set the distance between tab stops. This helps the preprocessor + report correct column numbers in warnings or errors, even if tabs + appear on the line. If the value is less than 1 or greater than + 100, the option is ignored. The default is 8. + + `-fno-show-column' + Do not print column numbers in diagnostics. This may be necessary + if diagnostics are being scanned by a program that does not + understand the column numbers, such as `dejagnu'. + + `-A PREDICATE=ANSWER' + Make an assertion with the predicate PREDICATE and answer ANSWER. + This form is preferred to the older form `-A PREDICATE(ANSWER)', + which is still supported, because it does not use shell special + characters. *Note Assertions::. + + `-A -PREDICATE=ANSWER' + Cancel an assertion with the predicate PREDICATE and answer ANSWER. + + `-A-' + Cancel all predefined assertions and all assertions preceding it on + the command line. Also, undefine all predefined macros and all + macros preceding it on the command line. (This is a historical + wart and may change in the future.) + + `-dCHARS' + CHARS is a sequence of one or more of the following characters, + and must not be preceded by a space. Other characters are + interpreted by the compiler proper, or reserved for future + versions of GCC, and so are silently ignored. If you specify + characters whose behavior conflicts, the result is undefined. + + `M' + Instead of the normal output, generate a list of `#define' + directives for all the macros defined during the execution of + the preprocessor, including predefined macros. This gives + you a way of finding out what is predefined in your version + of the preprocessor. Assuming you have no file `foo.h', the + command + + touch foo.h; cpp -dM foo.h + + will show all the predefined macros. + + `D' + Like `M' except in two respects: it does _not_ include the + predefined macros, and it outputs _both_ the `#define' + directives and the result of preprocessing. Both kinds of + output go to the standard output file. + + `N' + Like `D', but emit only the macro names, not their expansions. + + `I' + Output `#include' directives in addition to the result of + preprocessing. + + `-P' + Inhibit generation of linemarkers in the output from the + preprocessor. This might be useful when running the preprocessor + on something that is not C code, and will be sent to a program + which might be confused by the linemarkers. *Note Preprocessor + Output::. + + `-C' + Do not discard comments. All comments are passed through to the + output file, except for comments in processed directives, which + are deleted along with the directive. + + You should be prepared for side effects when using `-C'; it causes + the preprocessor to treat comments as tokens in their own right. + For example, comments appearing at the start of what would be a + directive line have the effect of turning that line into an + ordinary source line, since the first token on the line is no + longer a `#'. + + `-gcc' + Define the macros __GNUC__, __GNUC_MINOR__ and + __GNUC_PATCHLEVEL__. These are defined automatically when you use + `gcc -E'; you can turn them off in that case with `-no-gcc'. + + `-traditional' + Try to imitate the behavior of old-fashioned C, as opposed to ISO + C. *Note Traditional Mode::. + + `-trigraphs' + Process trigraph sequences. *Note Initial processing::. + + `-remap' + Enable special code to work around file systems which only permit + very short file names, such as MS-DOS. + + `-$' + Forbid the use of `$' in identifiers. The C standard allows + implementations to define extra characters that can appear in + identifiers. By default GNU CPP permits `$', a common extension. + + `-h' + `--help' + `--target-help' + Print text describing all the command line options instead of + preprocessing anything. + + `-v' + Verbose mode. Print out GNU CPP's version number at the beginning + of execution, and report the final form of the include path. + + `-H' + Print the name of each header file used, in addition to other + normal activities. Each name is indented to show how deep in the + `#include' stack it is. + + `-version' + `--version' + Print out GNU CPP's version number. With one dash, proceed to + preprocess as normal. With two dashes, exit immediately. + +  + File: cpp.info, Node: Environment Variables, Next: GNU Free Documentation License, Prev: Invocation, Up: Top + + Environment Variables + ********************* + + This section describes the environment variables that affect how CPP + operates. You can use them to specify directories or prefixes to use + when searching for include files, or to control dependency output. + + Note that you can also specify places to search using options such as + `-I', and control dependency output with options like `-M' (*note + Invocation::). These take precedence over environment variables, which + in turn take precedence over the configuration of GCC. + + `CPATH' + `C_INCLUDE_PATH' + `CPLUS_INCLUDE_PATH' + `OBJC_INCLUDE_PATH' + Each variable's value is a list of directories separated by a + special character, much like `PATH', in which to look for header + files. The special character, `PATH_SEPARATOR', is + target-dependent and determined at GCC build time. For + Windows-based targets it is a semicolon, and for almost all other + targets it is a colon. + + `CPATH' specifies a list of directories to be searched as if + specified with `-I', but after any paths given with `-I' options + on the command line. The environment variable is used regardless + of which language is being preprocessed. + + The remaining environment variables apply only when preprocessing + the particular language indicated. Each specifies a list of + directories to be searched as if specified with `-isystem', but + after any paths given with `-isystem' options on the command line. + + See also *Note Search Path::. + + `DEPENDENCIES_OUTPUT' + If this variable is set, its value specifies how to output + dependencies for Make based on the non-system header files + processed by the compiler. System header files are ignored in the + dependency output. + + The value of `DEPENDENCIES_OUTPUT' can be just a file name, in + which case the Make rules are written to that file, guessing the + target name from the source file name. Or the value can have the + form `FILE TARGET', in which case the rules are written to file + FILE using TARGET as the target name. + + In other words, this environment variable is equivalent to + combining the options `-MM' and `-MF' (*note Invocation::), with + an optional `-MT' switch too. + + `SUNPRO_DEPENDENCIES' + This variable is the same as the environment variable + `DEPENDENCIES_OUTPUT' (*note DEPENDENCIES_OUTPUT::), except that + system header files are not ignored, so it implies `-M' rather + than `-MM'. However, the dependence on the main input file is + omitted. *Note Invocation::. + +  + File: cpp.info, Node: GNU Free Documentation License, Next: Option Index, Prev: Environment Variables, Up: Top + + GNU Free Documentation License + ****************************** + + Version 1.1, March 2000 + Copyright (C) 2000 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + written document "free" in the sense of freedom: to assure everyone + the effective freedom to copy and redistribute it, with or without + modifying it, either commercially or noncommercially. Secondarily, + this License preserves for the author and publisher a way to get + credit for their work, while not being considered responsible for + modifications made by others. + + This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. + It complements the GNU General Public License, which is a copyleft + license designed for free software. + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same freedoms + that the software does. But this License is not limited to + software manuals; it can be used for any textual work, regardless + of subject matter or whether it is published as a printed book. + We recommend this License principally for works whose purpose is + instruction or reference. + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be distributed + under the terms of this License. The "Document", below, refers to + any such manual or work. Any member of the public is a licensee, + and is addressed as "you". + + A "Modified Version" of the Document means any work containing the + Document or a portion of it, either copied verbatim, or with + modifications and/or translated into another language. + + A "Secondary Section" is a named appendix or a front-matter + section of the Document that deals exclusively with the + relationship of the publishers or authors of the Document to the + Document's overall subject (or to related matters) and contains + nothing that could fall directly within that overall subject. + (For example, if the Document is in part a textbook of + mathematics, a Secondary Section may not explain any mathematics.) + The relationship could be a matter of historical connection with + the subject or with related matters, or of legal, commercial, + philosophical, ethical or political position regarding them. + + The "Invariant Sections" are certain Secondary Sections whose + titles are designated, as being those of Invariant Sections, in + the notice that says that the Document is released under this + License. + + The "Cover Texts" are certain short passages of text that are + listed, as Front-Cover Texts or Back-Cover Texts, in the notice + that says that the Document is released under this License. + + A "Transparent" copy of the Document means a machine-readable copy, + represented in a format whose specification is available to the + general public, whose contents can be viewed and edited directly + and straightforwardly with generic text editors or (for images + composed of pixels) generic paint programs or (for drawings) some + widely available drawing editor, and that is suitable for input to + text formatters or for automatic translation to a variety of + formats suitable for input to text formatters. A copy made in an + otherwise Transparent file format whose markup has been designed + to thwart or discourage subsequent modification by readers is not + Transparent. A copy that is not "Transparent" is called "Opaque". + + Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and + standard-conforming simple HTML designed for human modification. + Opaque formats include PostScript, PDF, proprietary formats that + can be read and edited only by proprietary word processors, SGML + or XML for which the DTD and/or processing tools are not generally + available, and the machine-generated HTML produced by some word + processors for output purposes only. + + The "Title Page" means, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the + material this License requires to appear in the title page. For + works in formats which do not have any title page as such, "Title + Page" means the text near the most prominent appearance of the + work's title, preceding the beginning of the body of the text. + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that you + add no other conditions whatsoever to those of this License. You + may not use technical measures to obstruct or control the reading + or further copying of the copies you make or distribute. However, + you may accept compensation in exchange for copies. If you + distribute a large enough number of copies you must also follow + the conditions in section 3. + + You may also lend copies, under the same conditions stated above, + and you may publicly display copies. + + 3. COPYING IN QUANTITY + + If you publish printed copies of the Document numbering more than + 100, and the Document's license notice requires Cover Texts, you + must enclose the copies in covers that carry, clearly and legibly, + all these Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also clearly + and legibly identify you as the publisher of these copies. The + front cover must present the full title with all words of the + title equally prominent and visible. You may add other material + on the covers in addition. Copying with changes limited to the + covers, as long as they preserve the title of the Document and + satisfy these conditions, can be treated as verbatim copying in + other respects. + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a + machine-readable Transparent copy along with each Opaque copy, or + state in or with each Opaque copy a publicly-accessible + computer-network location containing a complete Transparent copy + of the Document, free of added material, which the general + network-using public has access to download anonymously at no + charge using public-standard network protocols. If you use the + latter option, you must take reasonably prudent steps, when you + begin distribution of Opaque copies in quantity, to ensure that + this Transparent copy will remain thus accessible at the stated + location until at least one year after the last time you + distribute an Opaque copy (directly or through your agents or + retailers) of that edition to the public. + + It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of + copies, to give them a chance to provide you with an updated + version of the Document. + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you + release the Modified Version under precisely this License, with + the Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version to + whoever possesses a copy of it. In addition, you must do these + things in the Modified Version: + + A. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of + previous versions (which should, if there were any, be listed + in the History section of the Document). You may use the + same title as a previous version if the original publisher of + that version gives permission. + + B. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in + the Modified Version, together with at least five of the + principal authors of the Document (all of its principal + authors, if it has less than five). + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified + Version under the terms of this License, in the form shown in + the Addendum below. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. Preserve the section entitled "History", and its title, and + add to it an item stating at least the title, year, new + authors, and publisher of the Modified Version as given on + the Title Page. If there is no section entitled "History" in + the Document, create one stating the title, year, authors, + and publisher of the Document as given on its Title Page, + then add an item describing the Modified Version as stated in + the previous sentence. + + J. Preserve the network location, if any, given in the Document + for public access to a Transparent copy of the Document, and + likewise the network locations given in the Document for + previous versions it was based on. These may be placed in + the "History" section. You may omit a network location for a + work that was published at least four years before the + Document itself, or if the original publisher of the version + it refers to gives permission. + + K. In any section entitled "Acknowledgments" or "Dedications", + preserve the section's title, and preserve in the section all + the substance and tone of each of the contributor + acknowledgments and/or dedications given therein. + + L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section + titles. + + M. Delete any section entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section as "Endorsements" or to + conflict in title with any Invariant Section. + + If the Modified Version includes new front-matter sections or + appendices that qualify as Secondary Sections and contain no + material copied from the Document, you may at your option + designate some or all of these sections as invariant. To do this, + add their titles to the list of Invariant Sections in the Modified + Version's license notice. These titles must be distinct from any + other section titles. + + You may add a section entitled "Endorsements", provided it contains + nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + + You may add a passage of up to five words as a Front-Cover Text, + and a passage of up to 25 words as a Back-Cover Text, to the end + of the list of Cover Texts in the Modified Version. Only one + passage of Front-Cover Text and one of Back-Cover Text may be + added by (or through arrangements made by) any one entity. If the + Document already includes a cover text for the same cover, + previously added by you or by arrangement made by the same entity + you are acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + + The author(s) and publisher(s) of the Document do not by this + License give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version. + + 5. COMBINING DOCUMENTS + + You may combine the Document with other documents released under + this License, under the terms defined in section 4 above for + modified versions, provided that you include in the combination + all of the Invariant Sections of all of the original documents, + unmodified, and list them all as Invariant Sections of your + combined work in its license notice. + + The combined work need only contain one copy of this License, and + multiple identical Invariant Sections may be replaced with a single + copy. If there are multiple Invariant Sections with the same name + but different contents, make the title of each such section unique + by adding at the end of it, in parentheses, the name of the + original author or publisher of that section if known, or else a + unique number. Make the same adjustment to the section titles in + the list of Invariant Sections in the license notice of the + combined work. + + In the combination, you must combine any sections entitled + "History" in the various original documents, forming one section + entitled "History"; likewise combine any sections entitled + "Acknowledgments", and any sections entitled "Dedications". You + must delete all sections entitled "Endorsements." + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other + documents released under this License, and replace the individual + copies of this License in the various documents with a single copy + that is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + + You may extract a single document from such a collection, and + distribute it individually under this License, provided you insert + a copy of this License into the extracted document, and follow + this License in all other respects regarding verbatim copying of + that document. + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with other + separate and independent documents or works, in or on a volume of + a storage or distribution medium, does not as a whole count as a + Modified Version of the Document, provided no compilation + copyright is claimed for the compilation. Such a compilation is + called an "aggregate", and this License does not apply to the + other self-contained works thus compiled with the Document, on + account of their being thus compiled, if they are not themselves + derivative works of the Document. + + If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may be + placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section + 4. Replacing Invariant Sections with translations requires special + permission from their copyright holders, but you may include + translations of some or all Invariant Sections in addition to the + original versions of these Invariant Sections. You may include a + translation of this License provided that you also include the + original English version of this License. In case of a + disagreement between the translation and the original English + version of this License, the original English version will prevail. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided for under this License. Any other + attempt to copy, modify, sublicense or distribute the Document is + void, and will automatically terminate your rights under this + License. However, parties who have received copies, or rights, + from you under this License will not have their licenses + terminated so long as such parties remain in full compliance. + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software Foundation may publish new, revised versions of + the GNU Free Documentation License from time to time. Such new + versions will be similar in spirit to the present version, but may + differ in detail to address new problems or concerns. See + `http://www.gnu.org/copyleft/'. + + Each version of the License is given a distinguishing version + number. If the Document specifies that a particular numbered + version of this License "or any later version" applies to it, you + have the option of following the terms and conditions either of + that specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by the + Free Software Foundation. + + ADDENDUM: How to use this License for your documents + ==================================================== + + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and license + notices just after the title page: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 + or any later version published by the Free Software Foundation; + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + A copy of the license is included in the section entitled ``GNU + Free Documentation License''. + + If you have no Invariant Sections, write "with no Invariant Sections" + instead of saying which ones are invariant. If you have no Front-Cover + Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being + LIST"; likewise for Back-Cover Texts. + + If your document contains nontrivial examples of program code, we + recommend releasing these examples in parallel under your choice of + free software license, such as the GNU General Public License, to + permit their use in free software. + +  + File: cpp.info, Node: Option Index, Next: Index of Directives, Prev: GNU Free Documentation License, Up: Top + + Option Index + ************ + + CPP's command line options are indexed here without any initial `-' + or `--'. + + * Menu: + + * $: Invocation. + * A: Invocation. + * A-: Invocation. + * ansi: Invocation. + * C: Invocation. + * D: Invocation. + * dD: Invocation. + * dI: Invocation. + * dM: Invocation. + * dN: Invocation. + * fno-show-column: Invocation. + * fpreprocessed: Invocation. + * ftabstop: Invocation. + * gcc: Invocation. + * H: Invocation. + * h: Invocation. + * help: Invocation. + * I: Invocation. + * I-: Invocation. + * idirafter: Invocation. + * imacros: Invocation. + * include: Invocation. + * iprefix: Invocation. + * isystem: Invocation. + * iwithprefix: Invocation. + * iwithprefixbefore: Invocation. + * M: Invocation. + * MD: Invocation. + * MF: Invocation. + * MG: Invocation. + * MM: Invocation. + * MMD: Invocation. + * MP: Invocation. + * MQ: Invocation. + * MT: Invocation. + * nostdinc: Invocation. + * nostdinc++: Invocation. + * o: Invocation. + * P: Invocation. + * pedantic: Invocation. + * pedantic-errors: Invocation. + * remap: Invocation. + * std=: Invocation. + * target-help: Invocation. + * traditional: Invocation. + * trigraphs: Invocation. + * U: Invocation. + * undef: Invocation. + * v: Invocation. + * version: Invocation. + * w: Invocation. + * Wall: Invocation. + * Wcomment: Invocation. + * Wcomments: Invocation. + * Werror: Invocation. + * Wimport: Invocation. + * Wsystem-headers: Invocation. + * Wtraditional: Invocation. + * Wtrigraphs: Invocation. + * Wundef: Invocation. + * x: Invocation. + +  + File: cpp.info, Node: Index of Directives, Next: Concept Index, Prev: Option Index, Up: Top + + Index of Directives + ******************* + + * Menu: + + * #assert: Assertions. + * #define: Object-like Macros. + * #elif: Elif. + * #else: Else. + * #endif: Ifdef. + * #error: Diagnostics. + * #ident: Other Directives. + * #if: Conditional Syntax. + * #ifdef: Ifdef. + * #ifndef: Ifdef. + * #import: Obsolete once-only headers. + * #include: Include Syntax. + * #include_next: Wrapper Headers. + * #line: Line Control. + * #pragma GCC dependency: Pragmas. + * #pragma GCC poison: Pragmas. + * #pragma GCC system_header <1>: Pragmas. + * #pragma GCC system_header: System Headers. + * #sccs: Other Directives. + * #unassert: Assertions. + * #undef: Undefining and Redefining Macros. + * #warning: Diagnostics. + * C_INCLUDE_PATH: Environment Variables. + * CPATH: Environment Variables. + * CPLUS_INCLUDE_PATH: Environment Variables. + * DEPENDENCIES_OUTPUT: Environment Variables. + * OBJC_INCLUDE_PATH: Environment Variables. + * SUNPRO_DEPENDENCIES: Environment Variables. + diff -Nrc3pad gcc-3.2.2/gcc/doc/cpp.info-5 gcc-3.2.3/gcc/doc/cpp.info-5 *** gcc-3.2.2/gcc/doc/cpp.info-5 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cpp.info-5 Tue Apr 22 07:07:10 2003 *************** *** 0 **** --- 1,126 ---- + This is doc/cpp.info, produced by makeinfo version 4.5 from + doc/cpp.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpp: (cpp). The GNU C preprocessor. + END-INFO-DIR-ENTRY + +  + File: cpp.info, Node: Concept Index, Prev: Index of Directives, Up: Top + + Concept Index + ************* + + * Menu: + + * # operator: Stringification. + * ## operator: Concatenation. + * _Pragma: Pragmas. + * alternative tokens: Tokenization. + * arguments: Macro Arguments. + * arguments in macro definitions: Macro Arguments. + * assertions: Assertions. + * assertions, cancelling: Assertions. + * backslash-newline: Initial processing. + * block comments: Initial processing. + * C++ named operators: C++ Named Operators. + * character constants: Tokenization. + * character sets: Initial processing. + * command line: Invocation. + * commenting out code: Deleted Code. + * comments: Initial processing. + * common predefined macros: Common Predefined Macros. + * computed includes: Computed Includes. + * concatenation: Concatenation. + * conditional group: Ifdef. + * conditionals: Conditionals. + * continued lines: Initial processing. + * controlling macro: Once-Only Headers. + * defined: Defined. + * dependencies for make as output: Environment Variables. + * dependencies, make: Invocation. + * diagnostic: Diagnostics. + * differences from previous versions: Differences from previous versions. + * digraphs: Tokenization. + * directive line: The preprocessing language. + * directive name: The preprocessing language. + * directives: The preprocessing language. + * empty macro arguments: Macro Arguments. + * environment variables: Environment Variables. + * expansion of arguments: Argument Prescan. + * FDL, GNU Free Documentation License: GNU Free Documentation License. + * function-like macros: Function-like Macros. + * grouping options: Invocation. + * guard macro: Once-Only Headers. + * header file: Header Files. + * header file names: Tokenization. + * identifiers: Tokenization. + * implementation limits: Implementation limits. + * implementation-defined behavior: Implementation-defined behavior. + * including just once: Once-Only Headers. + * invalid token paste: Miscellaneous obsolete features. + * invocation: Invocation. + * iso646.h: C++ Named Operators. + * line comments: Initial processing. + * line control: Line Control. + * line endings: Initial processing. + * linemarkers: Preprocessor Output. + * macro argument expansion: Argument Prescan. + * macros in include: Computed Includes. + * macros with arguments: Macro Arguments. + * macros with variable arguments: Variadic Macros. + * make: Invocation. + * manifest constants: Object-like Macros. + * multi-line string constants: Miscellaneous obsolete features. + * named operators: C++ Named Operators. + * newlines in macro arguments: Newlines in Arguments. + * null directive: Other Directives. + * numbers: Tokenization. + * object-like macro: Object-like Macros. + * options: Invocation. + * options, grouping: Invocation. + * other tokens: Tokenization. + * output format: Preprocessor Output. + * overriding a header file: Wrapper Headers. + * parentheses in macro bodies: Operator Precedence Problems. + * pitfalls of macros: Macro Pitfalls. + * pragma poison: Miscellaneous obsolete features. + * predefined macros: Predefined Macros. + * predefined macros, system-specific: System-specific Predefined Macros. + * predicates: Assertions. + * preprocessing directives: The preprocessing language. + * preprocessing numbers: Tokenization. + * preprocessing tokens: Tokenization. + * prescan of macro arguments: Argument Prescan. + * problems with macros: Macro Pitfalls. + * punctuators: Tokenization. + * redefining macros: Undefining and Redefining Macros. + * repeated inclusion: Once-Only Headers. + * reporting errors: Diagnostics. + * reporting warnings: Diagnostics. + * reserved namespace: System-specific Predefined Macros. + * self-reference: Self-Referential Macros. + * semicolons (after macro calls): Swallowing the Semicolon. + * side effects (in macro arguments): Duplication of Side Effects. + * standard predefined macros.: Standard Predefined Macros. + * string constants: Tokenization. + * string literals: Tokenization. + * stringification: Stringification. + * symbolic constants: Object-like Macros. + * system header files <1>: System Headers. + * system header files: Header Files. + * system-specific predefined macros: System-specific Predefined Macros. + * testing predicates: Assertions. + * token concatenation: Concatenation. + * token pasting: Concatenation. + * tokens: Tokenization. + * trigraphs: Initial processing. + * undefining macros: Undefining and Redefining Macros. + * unsafe macros: Duplication of Side Effects. + * variable number of arguments: Variadic Macros. + * variadic macros: Variadic Macros. + * wrapper #ifndef: Once-Only Headers. + * wrapper headers: Wrapper Headers. + + diff -Nrc3pad gcc-3.2.2/gcc/doc/cppinternals.info gcc-3.2.3/gcc/doc/cppinternals.info *** gcc-3.2.2/gcc/doc/cppinternals.info Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/cppinternals.info Tue Apr 22 07:07:26 2003 *************** *** 0 **** --- 1,1034 ---- + This is doc/cppinternals.info, produced by makeinfo version 4.5 from + doc/cppinternals.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * Cpplib: (cppinternals). Cpplib internals. + END-INFO-DIR-ENTRY + + This file documents the internals of the GNU C Preprocessor. + + Copyright 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to make and distribute verbatim copies of this + manual provided the copyright notice and this permission notice are + preserved on all copies. + + Permission is granted to copy and distribute modified versions of + this manual under the conditions for verbatim copying, provided also + that the entire resulting derived work is distributed under the terms + of a permission notice identical to this one. + + Permission is granted to copy and distribute translations of this + manual into another language, under the above conditions for modified + versions. + +  + File: cppinternals.info, Node: Top, Next: Conventions, Up: (dir) + + + + Cpplib--the GNU C Preprocessor + ****************************** + + The GNU C preprocessor in GCC 3.x has been completely rewritten. It + is now implemented as a library, "cpplib", so it can be easily shared + between a stand-alone preprocessor, and a preprocessor integrated with + the C, C++ and Objective-C front ends. It is also available for use by + other programs, though this is not recommended as its exposed interface + has not yet reached a point of reasonable stability. + + The library has been written to be re-entrant, so that it can be used + to preprocess many files simultaneously if necessary. It has also been + written with the preprocessing token as the fundamental unit; the + preprocessor in previous versions of GCC would operate on text strings + as the fundamental unit. + + This brief manual documents the internals of cpplib, and explains + some of the tricky issues. It is intended that, along with the + comments in the source code, a reasonably competent C programmer should + be able to figure out what the code is doing, and why things have been + implemented the way they have. + + * Menu: + + * Conventions:: Conventions used in the code. + * Lexer:: The combined C, C++ and Objective-C Lexer. + * Hash Nodes:: All identifiers are entered into a hash table. + * Macro Expansion:: Macro expansion algorithm. + * Token Spacing:: Spacing and paste avoidance issues. + * Line Numbering:: Tracking location within files. + * Guard Macros:: Optimizing header files with guard macros. + * Files:: File handling. + * Index:: Index. + +  + File: cppinternals.info, Node: Conventions, Next: Lexer, Prev: Top, Up: Top + + Conventions + *********** + + cpplib has two interfaces--one is exposed internally only, and the + other is for both internal and external use. + + The convention is that functions and types that are exposed to + multiple files internally are prefixed with `_cpp_', and are to be + found in the file `cpphash.h'. Functions and types exposed to external + clients are in `cpplib.h', and prefixed with `cpp_'. For historical + reasons this is no longer quite true, but we should strive to stick to + it. + + We are striving to reduce the information exposed in `cpplib.h' to + the bare minimum necessary, and then to keep it there. This makes clear + exactly what external clients are entitled to assume, and allows us to + change internals in the future without worrying whether library clients + are perhaps relying on some kind of undocumented implementation-specific + behavior. + +  + File: cppinternals.info, Node: Lexer, Next: Hash Nodes, Prev: Conventions, Up: Top + + The Lexer + ********* + + Overview + ======== + + The lexer is contained in the file `cpplex.c'. It is a hand-coded + lexer, and not implemented as a state machine. It can understand C, C++ + and Objective-C source code, and has been extended to allow reasonably + successful preprocessing of assembly language. The lexer does not make + an initial pass to strip out trigraphs and escaped newlines, but handles + them as they are encountered in a single pass of the input file. It + returns preprocessing tokens individually, not a line at a time. + + It is mostly transparent to users of the library, since the library's + interface for obtaining the next token, `cpp_get_token', takes care of + lexing new tokens, handling directives, and expanding macros as + necessary. However, the lexer does expose some functionality so that + clients of the library can easily spell a given token, such as + `cpp_spell_token' and `cpp_token_len'. These functions are useful when + generating diagnostics, and for emitting the preprocessed output. + + Lexing a token + ============== + + Lexing of an individual token is handled by `_cpp_lex_direct' and + its subroutines. In its current form the code is quite complicated, + with read ahead characters and such-like, since it strives to not step + back in the character stream in preparation for handling non-ASCII file + encodings. The current plan is to convert any such files to UTF-8 + before processing them. This complexity is therefore unnecessary and + will be removed, so I'll not discuss it further here. + + The job of `_cpp_lex_direct' is simply to lex a token. It is not + responsible for issues like directive handling, returning lookahead + tokens directly, multiple-include optimization, or conditional block + skipping. It necessarily has a minor ro^le to play in memory + management of lexed lines. I discuss these issues in a separate section + (*note Lexing a line::). + + The lexer places the token it lexes into storage pointed to by the + variable `cur_token', and then increments it. This variable is + important for correct diagnostic positioning. Unless a specific line + and column are passed to the diagnostic routines, they will examine the + `line' and `col' values of the token just before the location that + `cur_token' points to, and use that location to report the diagnostic. + + The lexer does not consider whitespace to be a token in its own + right. If whitespace (other than a new line) precedes a token, it sets + the `PREV_WHITE' bit in the token's flags. Each token has its `line' + and `col' variables set to the line and column of the first character + of the token. This line number is the line number in the translation + unit, and can be converted to a source (file, line) pair using the line + map code. + + The first token on a logical, i.e. unescaped, line has the flag + `BOL' set for beginning-of-line. This flag is intended for internal + use, both to distinguish a `#' that begins a directive from one that + doesn't, and to generate a call-back to clients that want to be + notified about the start of every non-directive line with tokens on it. + Clients cannot reliably determine this for themselves: the first token + might be a macro, and the tokens of a macro expansion do not have the + `BOL' flag set. The macro expansion may even be empty, and the next + token on the line certainly won't have the `BOL' flag set. + + New lines are treated specially; exactly how the lexer handles them + is context-dependent. The C standard mandates that directives are + terminated by the first unescaped newline character, even if it appears + in the middle of a macro expansion. Therefore, if the state variable + `in_directive' is set, the lexer returns a `CPP_EOF' token, which is + normally used to indicate end-of-file, to indicate end-of-directive. + In a directive a `CPP_EOF' token never means end-of-file. + Conveniently, if the caller was `collect_args', it already handles + `CPP_EOF' as if it were end-of-file, and reports an error about an + unterminated macro argument list. + + The C standard also specifies that a new line in the middle of the + arguments to a macro is treated as whitespace. This white space is + important in case the macro argument is stringified. The state variable + `parsing_args' is nonzero when the preprocessor is collecting the + arguments to a macro call. It is set to 1 when looking for the opening + parenthesis to a function-like macro, and 2 when collecting the actual + arguments up to the closing parenthesis, since these two cases need to + be distinguished sometimes. One such time is here: the lexer sets the + `PREV_WHITE' flag of a token if it meets a new line when `parsing_args' + is set to 2. It doesn't set it if it meets a new line when + `parsing_args' is 1, since then code like + + #define foo() bar + foo + baz + + would be output with an erroneous space before `baz': + + foo + baz + + This is a good example of the subtlety of getting token spacing + correct in the preprocessor; there are plenty of tests in the test + suite for corner cases like this. + + The lexer is written to treat each of `\r', `\n', `\r\n' and `\n\r' + as a single new line indicator. This allows it to transparently + preprocess MS-DOS, Macintosh and Unix files without their needing to + pass through a special filter beforehand. + + We also decided to treat a backslash, either `\' or the trigraph + `??/', separated from one of the above newline indicators by + non-comment whitespace only, as intending to escape the newline. It + tends to be a typing mistake, and cannot reasonably be mistaken for + anything else in any of the C-family grammars. Since handling it this + way is not strictly conforming to the ISO standard, the library issues a + warning wherever it encounters it. + + Handling newlines like this is made simpler by doing it in one place + only. The function `handle_newline' takes care of all newline + characters, and `skip_escaped_newlines' takes care of arbitrarily long + sequences of escaped newlines, deferring to `handle_newline' to handle + the newlines themselves. + + The most painful aspect of lexing ISO-standard C and C++ is handling + trigraphs and backlash-escaped newlines. Trigraphs are processed before + any interpretation of the meaning of a character is made, and + unfortunately there is a trigraph representation for a backslash, so it + is possible for the trigraph `??/' to introduce an escaped newline. + + Escaped newlines are tedious because theoretically they can occur + anywhere--between the `+' and `=' of the `+=' token, within the + characters of an identifier, and even between the `*' and `/' that + terminates a comment. Moreover, you cannot be sure there is just + one--there might be an arbitrarily long sequence of them. + + So, for example, the routine that lexes a number, `parse_number', + cannot assume that it can scan forwards until the first non-number + character and be done with it, because this could be the `\' + introducing an escaped newline, or the `?' introducing the trigraph + sequence that represents the `\' of an escaped newline. If it + encounters a `?' or `\', it calls `skip_escaped_newlines' to skip over + any potential escaped newlines before checking whether the number has + been finished. + + Similarly code in the main body of `_cpp_lex_direct' cannot simply + check for a `=' after a `+' character to determine whether it has a + `+=' token; it needs to be prepared for an escaped newline of some + sort. Such cases use the function `get_effective_char', which returns + the first character after any intervening escaped newlines. + + The lexer needs to keep track of the correct column position, + including counting tabs as specified by the `-ftabstop=' option. This + should be done even within C-style comments; they can appear in the + middle of a line, and we want to report diagnostics in the correct + position for text appearing after the end of the comment. + + Some identifiers, such as `__VA_ARGS__' and poisoned identifiers, + may be invalid and require a diagnostic. However, if they appear in a + macro expansion we don't want to complain with each use of the macro. + It is therefore best to catch them during the lexing stage, in + `parse_identifier'. In both cases, whether a diagnostic is needed or + not is dependent upon the lexer's state. For example, we don't want to + issue a diagnostic for re-poisoning a poisoned identifier, or for using + `__VA_ARGS__' in the expansion of a variable-argument macro. Therefore + `parse_identifier' makes use of state flags to determine whether a + diagnostic is appropriate. Since we change state on a per-token basis, + and don't lex whole lines at a time, this is not a problem. + + Another place where state flags are used to change behavior is whilst + lexing header names. Normally, a `<' would be lexed as a single token. + After a `#include' directive, though, it should be lexed as a single + token as far as the nearest `>' character. Note that we don't allow + the terminators of header names to be escaped; the first `"' or `>' + terminates the header name. + + Interpretation of some character sequences depends upon whether we + are lexing C, C++ or Objective-C, and on the revision of the standard in + force. For example, `::' is a single token in C++, but in C it is two + separate `:' tokens and almost certainly a syntax error. Such cases + are handled by `_cpp_lex_direct' based upon command-line flags stored + in the `cpp_options' structure. + + Once a token has been lexed, it leads an independent existence. The + spelling of numbers, identifiers and strings is copied to permanent + storage from the original input buffer, so a token remains valid and + correct even if its source buffer is freed with `_cpp_pop_buffer'. The + storage holding the spellings of such tokens remains until the client + program calls cpp_destroy, probably at the end of the translation unit. + + Lexing a line + ============= + + When the preprocessor was changed to return pointers to tokens, one + feature I wanted was some sort of guarantee regarding how long a + returned pointer remains valid. This is important to the stand-alone + preprocessor, the future direction of the C family front ends, and even + to cpplib itself internally. + + Occasionally the preprocessor wants to be able to peek ahead in the + token stream. For example, after the name of a function-like macro, it + wants to check the next token to see if it is an opening parenthesis. + Another example is that, after reading the first few tokens of a + `#pragma' directive and not recognizing it as a registered pragma, it + wants to backtrack and allow the user-defined handler for unknown + pragmas to access the full `#pragma' token stream. The stand-alone + preprocessor wants to be able to test the current token with the + previous one to see if a space needs to be inserted to preserve their + separate tokenization upon re-lexing (paste avoidance), so it needs to + be sure the pointer to the previous token is still valid. The + recursive-descent C++ parser wants to be able to perform tentative + parsing arbitrarily far ahead in the token stream, and then to be able + to jump back to a prior position in that stream if necessary. + + The rule I chose, which is fairly natural, is to arrange that the + preprocessor lex all tokens on a line consecutively into a token buffer, + which I call a "token run", and when meeting an unescaped new line + (newlines within comments do not count either), to start lexing back at + the beginning of the run. Note that we do _not_ lex a line of tokens + at once; if we did that `parse_identifier' would not have state flags + available to warn about invalid identifiers (*note Invalid + identifiers::). + + In other words, accessing tokens that appeared earlier in the current + line is valid, but since each logical line overwrites the tokens of the + previous line, tokens from prior lines are unavailable. In particular, + since a directive only occupies a single logical line, this means that + the directive handlers like the `#pragma' handler can jump around in + the directive's tokens if necessary. + + Two issues remain: what about tokens that arise from macro + expansions, and what happens when we have a long line that overflows + the token run? + + Since we promise clients that we preserve the validity of pointers + that we have already returned for tokens that appeared earlier in the + line, we cannot reallocate the run. Instead, on overflow it is + expanded by chaining a new token run on to the end of the existing one. + + The tokens forming a macro's replacement list are collected by the + `#define' handler, and placed in storage that is only freed by + `cpp_destroy'. So if a macro is expanded in our line of tokens, the + pointers to the tokens of its expansion that we return will always + remain valid. However, macros are a little trickier than that, since + they give rise to three sources of fresh tokens. They are the built-in + macros like `__LINE__', and the `#' and `##' operators for + stringification and token pasting. I handled this by allocating space + for these tokens from the lexer's token run chain. This means they + automatically receive the same lifetime guarantees as lexed tokens, and + we don't need to concern ourselves with freeing them. + + Lexing into a line of tokens solves some of the token memory + management issues, but not all. The opening parenthesis after a + function-like macro name might lie on a different line, and the front + ends definitely want the ability to look ahead past the end of the + current line. So cpplib only moves back to the start of the token run + at the end of a line if the variable `keep_tokens' is zero. + Line-buffering is quite natural for the preprocessor, and as a result + the only time cpplib needs to increment this variable is whilst looking + for the opening parenthesis to, and reading the arguments of, a + function-like macro. In the near future cpplib will export an + interface to increment and decrement this variable, so that clients can + share full control over the lifetime of token pointers too. + + The routine `_cpp_lex_token' handles moving to new token runs, + calling `_cpp_lex_direct' to lex new tokens, or returning + previously-lexed tokens if we stepped back in the token stream. It also + checks each token for the `BOL' flag, which might indicate a directive + that needs to be handled, or require a start-of-line call-back to be + made. `_cpp_lex_token' also handles skipping over tokens in failed + conditional blocks, and invalidates the control macro of the + multiple-include optimization if a token was successfully lexed outside + a directive. In other words, its callers do not need to concern + themselves with such issues. + +  + File: cppinternals.info, Node: Hash Nodes, Next: Macro Expansion, Prev: Lexer, Up: Top + + Hash Nodes + ********** + + When cpplib encounters an "identifier", it generates a hash code for + it and stores it in the hash table. By "identifier" we mean tokens + with type `CPP_NAME'; this includes identifiers in the usual C sense, + as well as keywords, directive names, macro names and so on. For + example, all of `pragma', `int', `foo' and `__GNUC__' are identifiers + and hashed when lexed. + + Each node in the hash table contain various information about the + identifier it represents. For example, its length and type. At any one + time, each identifier falls into exactly one of three categories: + + * Macros + + These have been declared to be macros, either on the command line + or with `#define'. A few, such as `__TIME__' are built-ins + entered in the hash table during initialization. The hash node + for a normal macro points to a structure with more information + about the macro, such as whether it is function-like, how many + arguments it takes, and its expansion. Built-in macros are + flagged as special, and instead contain an enum indicating which + of the various built-in macros it is. + + * Assertions + + Assertions are in a separate namespace to macros. To enforce + this, cpp actually prepends a `#' character before hashing and + entering it in the hash table. An assertion's node points to a + chain of answers to that assertion. + + * Void + + Everything else falls into this category--an identifier that is not + currently a macro, or a macro that has since been undefined with + `#undef'. + + When preprocessing C++, this category also includes the named + operators, such as `xor'. In expressions these behave like the + operators they represent, but in contexts where the spelling of a + token matters they are spelt differently. This spelling + distinction is relevant when they are operands of the stringizing + and pasting macro operators `#' and `##'. Named operator hash + nodes are flagged, both to catch the spelling distinction and to + prevent them from being defined as macros. + + The same identifiers share the same hash node. Since each identifier + token, after lexing, contains a pointer to its hash node, this is used + to provide rapid lookup of various information. For example, when + parsing a `#define' statement, CPP flags each argument's identifier + hash node with the index of that argument. This makes duplicated + argument checking an O(1) operation for each argument. Similarly, for + each identifier in the macro's expansion, lookup to see if it is an + argument, and which argument it is, is also an O(1) operation. Further, + each directive name, such as `endif', has an associated directive enum + stored in its hash node, so that directive lookup is also O(1). + +  + File: cppinternals.info, Node: Macro Expansion, Next: Token Spacing, Prev: Hash Nodes, Up: Top + + Macro Expansion Algorithm + ************************* + + Macro expansion is a tricky operation, fraught with nasty corner + cases and situations that render what you thought was a nifty way to + optimize the preprocessor's expansion algorithm wrong in quite subtle + ways. + + I strongly recommend you have a good grasp of how the C and C++ + standards require macros to be expanded before diving into this + section, let alone the code!. If you don't have a clear mental picture + of how things like nested macro expansion, stringification and token + pasting are supposed to work, damage to your sanity can quickly result. + + Internal representation of macros + ================================= + + The preprocessor stores macro expansions in tokenized form. This + saves repeated lexing passes during expansion, at the cost of a small + increase in memory consumption on average. The tokens are stored + contiguously in memory, so a pointer to the first one and a token count + is all you need to get the replacement list of a macro. + + If the macro is a function-like macro the preprocessor also stores + its parameters, in the form of an ordered list of pointers to the hash + table entry of each parameter's identifier. Further, in the macro's + stored expansion each occurrence of a parameter is replaced with a + special token of type `CPP_MACRO_ARG'. Each such token holds the index + of the parameter it represents in the parameter list, which allows + rapid replacement of parameters with their arguments during expansion. + Despite this optimization it is still necessary to store the original + parameters to the macro, both for dumping with e.g., `-dD', and to warn + about non-trivial macro redefinitions when the parameter names have + changed. + + Macro expansion overview + ======================== + + The preprocessor maintains a "context stack", implemented as a + linked list of `cpp_context' structures, which together represent the + macro expansion state at any one time. The `struct cpp_reader' member + variable `context' points to the current top of this stack. The top + normally holds the unexpanded replacement list of the innermost macro + under expansion, except when cpplib is about to pre-expand an argument, + in which case it holds that argument's unexpanded tokens. + + When there are no macros under expansion, cpplib is in "base + context". All contexts other than the base context contain a + contiguous list of tokens delimited by a starting and ending token. + When not in base context, cpplib obtains the next token from the list + of the top context. If there are no tokens left in the list, it pops + that context off the stack, and subsequent ones if necessary, until an + unexhausted context is found or it returns to base context. In base + context, cpplib reads tokens directly from the lexer. + + If it encounters an identifier that is both a macro and enabled for + expansion, cpplib prepares to push a new context for that macro on the + stack by calling the routine `enter_macro_context'. When this routine + returns, the new context will contain the unexpanded tokens of the + replacement list of that macro. In the case of function-like macros, + `enter_macro_context' also replaces any parameters in the replacement + list, stored as `CPP_MACRO_ARG' tokens, with the appropriate macro + argument. If the standard requires that the parameter be replaced with + its expanded argument, the argument will have been fully macro expanded + first. + + `enter_macro_context' also handles special macros like `__LINE__'. + Although these macros expand to a single token which cannot contain any + further macros, for reasons of token spacing (*note Token Spacing::) + and simplicity of implementation, cpplib handles these special macros + by pushing a context containing just that one token. + + The final thing that `enter_macro_context' does before returning is + to mark the macro disabled for expansion (except for special macros + like `__TIME__'). The macro is re-enabled when its context is later + popped from the context stack, as described above. This strict + ordering ensures that a macro is disabled whilst its expansion is being + scanned, but that it is _not_ disabled whilst any arguments to it are + being expanded. + + Scanning the replacement list for macros to expand + ================================================== + + The C standard states that, after any parameters have been replaced + with their possibly-expanded arguments, the replacement list is scanned + for nested macros. Further, any identifiers in the replacement list + that are not expanded during this scan are never again eligible for + expansion in the future, if the reason they were not expanded is that + the macro in question was disabled. + + Clearly this latter condition can only apply to tokens resulting from + argument pre-expansion. Other tokens never have an opportunity to be + re-tested for expansion. It is possible for identifiers that are + function-like macros to not expand initially but to expand during a + later scan. This occurs when the identifier is the last token of an + argument (and therefore originally followed by a comma or a closing + parenthesis in its macro's argument list), and when it replaces its + parameter in the macro's replacement list, the subsequent token happens + to be an opening parenthesis (itself possibly the first token of an + argument). + + It is important to note that when cpplib reads the last token of a + given context, that context still remains on the stack. Only when + looking for the _next_ token do we pop it off the stack and drop to a + lower context. This makes backing up by one token easy, but more + importantly ensures that the macro corresponding to the current context + is still disabled when we are considering the last token of its + replacement list for expansion (or indeed expanding it). As an + example, which illustrates many of the points above, consider + + #define foo(x) bar x + foo(foo) (2) + + which fully expands to `bar foo (2)'. During pre-expansion of the + argument, `foo' does not expand even though the macro is enabled, since + it has no following parenthesis [pre-expansion of an argument only uses + tokens from that argument; it cannot take tokens from whatever follows + the macro invocation]. This still leaves the argument token `foo' + eligible for future expansion. Then, when re-scanning after argument + replacement, the token `foo' is rejected for expansion, and marked + ineligible for future expansion, since the macro is now disabled. It + is disabled because the replacement list `bar foo' of the macro is + still on the context stack. + + If instead the algorithm looked for an opening parenthesis first and + then tested whether the macro were disabled it would be subtly wrong. + In the example above, the replacement list of `foo' would be popped in + the process of finding the parenthesis, re-enabling `foo' and expanding + it a second time. + + Looking for a function-like macro's opening parenthesis + ======================================================= + + Function-like macros only expand when immediately followed by a + parenthesis. To do this cpplib needs to temporarily disable macros and + read the next token. Unfortunately, because of spacing issues (*note + Token Spacing::), there can be fake padding tokens in-between, and if + the next real token is not a parenthesis cpplib needs to be able to + back up that one token as well as retain the information in any + intervening padding tokens. + + Backing up more than one token when macros are involved is not + permitted by cpplib, because in general it might involve issues like + restoring popped contexts onto the context stack, which are too hard. + Instead, searching for the parenthesis is handled by a special + function, `funlike_invocation_p', which remembers padding information + as it reads tokens. If the next real token is not an opening + parenthesis, it backs up that one token, and then pushes an extra + context just containing the padding information if necessary. + + Marking tokens ineligible for future expansion + ============================================== + + As discussed above, cpplib needs a way of marking tokens as + unexpandable. Since the tokens cpplib handles are read-only once they + have been lexed, it instead makes a copy of the token and adds the flag + `NO_EXPAND' to the copy. + + For efficiency and to simplify memory management by avoiding having + to remember to free these tokens, they are allocated as temporary tokens + from the lexer's current token run (*note Lexing a line::) using the + function `_cpp_temp_token'. The tokens are then re-used once the + current line of tokens has been read in. + + This might sound unsafe. However, tokens runs are not re-used at the + end of a line if it happens to be in the middle of a macro argument + list, and cpplib only wants to back-up more than one lexer token in + situations where no macro expansion is involved, so the optimization is + safe. + +  + File: cppinternals.info, Node: Token Spacing, Next: Line Numbering, Prev: Macro Expansion, Up: Top + + Token Spacing + ************* + + First, let's look at an issue that only concerns the stand-alone + preprocessor: we want to guarantee that re-reading its preprocessed + output results in an identical token stream. Without taking special + measures, this might not be the case because of macro substitution. + For example: + + #define PLUS + + #define EMPTY + #define f(x) =x= + +PLUS -EMPTY- PLUS+ f(=) + ==> + + - - + + = = = + _not_ + ==> ++ -- ++ === + + One solution would be to simply insert a space between all adjacent + tokens. However, we would like to keep space insertion to a minimum, + both for aesthetic reasons and because it causes problems for people who + still try to abuse the preprocessor for things like Fortran source and + Makefiles. + + For now, just notice that when tokens are added (or removed, as + shown by the `EMPTY' example) from the original lexed token stream, we + need to check for accidental token pasting. We call this "paste + avoidance". Token addition and removal can only occur because of macro + expansion, but accidental pasting can occur in many places: both before + and after each macro replacement, each argument replacement, and + additionally each token created by the `#' and `##' operators. + + Let's look at how the preprocessor gets whitespace output correct + normally. The `cpp_token' structure contains a flags byte, and one of + those flags is `PREV_WHITE'. This is flagged by the lexer, and + indicates that the token was preceded by whitespace of some form other + than a new line. The stand-alone preprocessor can use this flag to + decide whether to insert a space between tokens in the output. + + Now consider the result of the following macro expansion: + + #define add(x, y, z) x + y +z; + sum = add (1,2, 3); + ==> sum = 1 + 2 +3; + + The interesting thing here is that the tokens `1' and `2' are output + with a preceding space, and `3' is output without a preceding space, + but when lexed none of these tokens had that property. Careful + consideration reveals that `1' gets its preceding whitespace from the + space preceding `add' in the macro invocation, _not_ replacement list. + `2' gets its whitespace from the space preceding the parameter `y' in + the macro replacement list, and `3' has no preceding space because + parameter `z' has none in the replacement list. + + Once lexed, tokens are effectively fixed and cannot be altered, since + pointers to them might be held in many places, in particular by + in-progress macro expansions. So instead of modifying the two tokens + above, the preprocessor inserts a special token, which I call a + "padding token", into the token stream to indicate that spacing of the + subsequent token is special. The preprocessor inserts padding tokens + in front of every macro expansion and expanded macro argument. These + point to a "source token" from which the subsequent real token should + inherit its spacing. In the above example, the source tokens are `add' + in the macro invocation, and `y' and `z' in the macro replacement list, + respectively. + + It is quite easy to get multiple padding tokens in a row, for + example if a macro's first replacement token expands straight into + another macro. + + #define foo bar + #define bar baz + [foo] + ==> [baz] + + Here, two padding tokens are generated with sources the `foo' token + between the brackets, and the `bar' token from foo's replacement list, + respectively. Clearly the first padding token is the one we should + use, so our output code should contain a rule that the first padding + token in a sequence is the one that matters. + + But what if we happen to leave a macro expansion? Adjusting the + above example slightly: + + #define foo bar + #define bar EMPTY baz + #define EMPTY + [foo] EMPTY; + ==> [ baz] ; + + As shown, now there should be a space before `baz' and the semicolon + in the output. + + The rules we decided above fail for `baz': we generate three padding + tokens, one per macro invocation, before the token `baz'. We would + then have it take its spacing from the first of these, which carries + source token `foo' with no leading space. + + It is vital that cpplib get spacing correct in these examples since + any of these macro expansions could be stringified, where spacing + matters. + + So, this demonstrates that not just entering macro and argument + expansions, but leaving them requires special handling too. I made + cpplib insert a padding token with a `NULL' source token when leaving + macro expansions, as well as after each replaced argument in a macro's + replacement list. It also inserts appropriate padding tokens on either + side of tokens created by the `#' and `##' operators. I expanded the + rule so that, if we see a padding token with a `NULL' source token, + _and_ that source token has no leading space, then we behave as if we + have seen no padding tokens at all. A quick check shows this rule will + then get the above example correct as well. + + Now a relationship with paste avoidance is apparent: we have to be + careful about paste avoidance in exactly the same locations we have + padding tokens in order to get white space correct. This makes + implementation of paste avoidance easy: wherever the stand-alone + preprocessor is fixing up spacing because of padding tokens, and it + turns out that no space is needed, it has to take the extra step to + check that a space is not needed after all to avoid an accidental paste. + The function `cpp_avoid_paste' advises whether a space is required + between two consecutive tokens. To avoid excessive spacing, it tries + hard to only require a space if one is likely to be necessary, but for + reasons of efficiency it is slightly conservative and might recommend a + space where one is not strictly needed. + +  + File: cppinternals.info, Node: Line Numbering, Next: Guard Macros, Prev: Token Spacing, Up: Top + + Line numbering + ************** + + Just which line number anyway? + ============================== + + There are three reasonable requirements a cpplib client might have + for the line number of a token passed to it: + + * The source line it was lexed on. + + * The line it is output on. This can be different to the line it was + lexed on if, for example, there are intervening escaped newlines or + C-style comments. For example: + + foo /* A long + comment */ bar \ + baz + => + foo bar baz + + * If the token results from a macro expansion, the line of the macro + name, or possibly the line of the closing parenthesis in the case + of function-like macro expansion. + + The `cpp_token' structure contains `line' and `col' members. The + lexer fills these in with the line and column of the first character of + the token. Consequently, but maybe unexpectedly, a token from the + replacement list of a macro expansion carries the location of the token + within the `#define' directive, because cpplib expands a macro by + returning pointers to the tokens in its replacement list. The current + implementation of cpplib assigns tokens created from built-in macros + and the `#' and `##' operators the location of the most recently lexed + token. This is a because they are allocated from the lexer's token + runs, and because of the way the diagnostic routines infer the + appropriate location to report. + + The diagnostic routines in cpplib display the location of the most + recently _lexed_ token, unless they are passed a specific line and + column to report. For diagnostics regarding tokens that arise from + macro expansions, it might also be helpful for the user to see the + original location in the macro definition that the token came from. + Since that is exactly the information each token carries, such an + enhancement could be made relatively easily in future. + + The stand-alone preprocessor faces a similar problem when determining + the correct line to output the token on: the position attached to a + token is fairly useless if the token came from a macro expansion. All + tokens on a logical line should be output on its first physical line, so + the token's reported location is also wrong if it is part of a physical + line other than the first. + + To solve these issues, cpplib provides a callback that is generated + whenever it lexes a preprocessing token that starts a new logical line + other than a directive. It passes this token (which may be a `CPP_EOF' + token indicating the end of the translation unit) to the callback + routine, which can then use the line and column of this token to + produce correct output. + + Representation of line numbers + ============================== + + As mentioned above, cpplib stores with each token the line number + that it was lexed on. In fact, this number is not the number of the + line in the source file, but instead bears more resemblance to the + number of the line in the translation unit. + + The preprocessor maintains a monotonic increasing line count, which + is incremented at every new line character (and also at the end of any + buffer that does not end in a new line). Since a line number of zero is + useful to indicate certain special states and conditions, this variable + starts counting from one. + + This variable therefore uniquely enumerates each line in the + translation unit. With some simple infrastructure, it is straight + forward to map from this to the original source file and line number + pair, saving space whenever line number information needs to be saved. + The code the implements this mapping lies in the files `line-map.c' and + `line-map.h'. + + Command-line macros and assertions are implemented by pushing a + buffer containing the right hand side of an equivalent `#define' or + `#assert' directive. Some built-in macros are handled similarly. + Since these are all processed before the first line of the main input + file, it will typically have an assigned line closer to twenty than to + one. + +  + File: cppinternals.info, Node: Guard Macros, Next: Files, Prev: Line Numbering, Up: Top + + The Multiple-Include Optimization + ********************************* + + Header files are often of the form + + #ifndef FOO + #define FOO + ... + #endif + + to prevent the compiler from processing them more than once. The + preprocessor notices such header files, so that if the header file + appears in a subsequent `#include' directive and `FOO' is defined, then + it is ignored and it doesn't preprocess or even re-open the file a + second time. This is referred to as the "multiple include + optimization". + + Under what circumstances is such an optimization valid? If the file + were included a second time, it can only be optimized away if that + inclusion would result in no tokens to return, and no relevant + directives to process. Therefore the current implementation imposes + requirements and makes some allowances as follows: + + 1. There must be no tokens outside the controlling `#if'-`#endif' + pair, but whitespace and comments are permitted. + + 2. There must be no directives outside the controlling directive + pair, but the "null directive" (a line containing nothing other + than a single `#' and possibly whitespace) is permitted. + + 3. The opening directive must be of the form + + #ifndef FOO + + or + + #if !defined FOO [equivalently, #if !defined(FOO)] + + 4. In the second form above, the tokens forming the `#if' expression + must have come directly from the source file--no macro expansion + must have been involved. This is because macro definitions can + change, and tracking whether or not a relevant change has been + made is not worth the implementation cost. + + 5. There can be no `#else' or `#elif' directives at the outer + conditional block level, because they would probably contain + something of interest to a subsequent pass. + + First, when pushing a new file on the buffer stack, + `_stack_include_file' sets the controlling macro `mi_cmacro' to `NULL', + and sets `mi_valid' to `true'. This indicates that the preprocessor + has not yet encountered anything that would invalidate the + multiple-include optimization. As described in the next few + paragraphs, these two variables having these values effectively + indicates top-of-file. + + When about to return a token that is not part of a directive, + `_cpp_lex_token' sets `mi_valid' to `false'. This enforces the + constraint that tokens outside the controlling conditional block + invalidate the optimization. + + The `do_if', when appropriate, and `do_ifndef' directive handlers + pass the controlling macro to the function `push_conditional'. cpplib + maintains a stack of nested conditional blocks, and after processing + every opening conditional this function pushes an `if_stack' structure + onto the stack. In this structure it records the controlling macro for + the block, provided there is one and we're at top-of-file (as described + above). If an `#elif' or `#else' directive is encountered, the + controlling macro for that block is cleared to `NULL'. Otherwise, it + survives until the `#endif' closing the block, upon which `do_endif' + sets `mi_valid' to true and stores the controlling macro in `mi_cmacro'. + + `_cpp_handle_directive' clears `mi_valid' when processing any + directive other than an opening conditional and the null directive. + With this, and requiring top-of-file to record a controlling macro, and + no `#else' or `#elif' for it to survive and be copied to `mi_cmacro' by + `do_endif', we have enforced the absence of directives outside the main + conditional block for the optimization to be on. + + Note that whilst we are inside the conditional block, `mi_valid' is + likely to be reset to `false', but this does not matter since the the + closing `#endif' restores it to `true' if appropriate. + + Finally, since `_cpp_lex_direct' pops the file off the buffer stack + at `EOF' without returning a token, if the `#endif' directive was not + followed by any tokens, `mi_valid' is `true' and `_cpp_pop_file_buffer' + remembers the controlling macro associated with the file. Subsequent + calls to `stack_include_file' result in no buffer being pushed if the + controlling macro is defined, effecting the optimization. + + A quick word on how we handle the + + #if !defined FOO + + case. `_cpp_parse_expr' and `parse_defined' take steps to see whether + the three stages `!', `defined-expression' and `end-of-directive' occur + in order in a `#if' expression. If so, they return the guard macro to + `do_if' in the variable `mi_ind_cmacro', and otherwise set it to `NULL'. + `enter_macro_context' sets `mi_valid' to false, so if a macro was + expanded whilst parsing any part of the expression, then the + top-of-file test in `push_conditional' fails and the optimization is + turned off. + +  + File: cppinternals.info, Node: Files, Next: Index, Prev: Guard Macros, Up: Top + + File Handling + ************* + + Fairly obviously, the file handling code of cpplib resides in the + file `cppfiles.c'. It takes care of the details of file searching, + opening, reading and caching, for both the main source file and all the + headers it recursively includes. + + The basic strategy is to minimize the number of system calls. On + many systems, the basic `open ()' and `fstat ()' system calls can be + quite expensive. For every `#include'-d file, we need to try all the + directories in the search path until we find a match. Some projects, + such as glibc, pass twenty or thirty include paths on the command line, + so this can rapidly become time consuming. + + For a header file we have not encountered before we have little + choice but to do this. However, it is often the case that the same + headers are repeatedly included, and in these cases we try to avoid + repeating the filesystem queries whilst searching for the correct file. + + For each file we try to open, we store the constructed path in a + splay tree. This path first undergoes simplification by the function + `_cpp_simplify_pathname'. For example, `/usr/include/bits/../foo.h' is + simplified to `/usr/include/foo.h' before we enter it in the splay tree + and try to `open ()' the file. CPP will then find subsequent uses of + `foo.h', even as `/usr/include/foo.h', in the splay tree and save + system calls. + + Further, it is likely the file contents have also been cached, + saving a `read ()' system call. We don't bother caching the contents of + header files that are re-inclusion protected, and whose re-inclusion + macro is defined when we leave the header file for the first time. If + the host supports it, we try to map suitably large files into memory, + rather than reading them in directly. + + The include paths are internally stored on a null-terminated + singly-linked list, starting with the `"header.h"' directory search + chain, which then links into the `' directory chain. + + Files included with the `' syntax start the lookup directly + in the second half of this chain. However, files included with the + `"foo.h"' syntax start at the beginning of the chain, but with one + extra directory prepended. This is the directory of the current file; + the one containing the `#include' directive. Prepending this directory + on a per-file basis is handled by the function `search_from'. + + Note that a header included with a directory component, such as + `#include "mydir/foo.h"' and opened as + `/usr/local/include/mydir/foo.h', will have the complete path minus the + basename `foo.h' as the current directory. + + Enough information is stored in the splay tree that CPP can + immediately tell whether it can skip the header file because of the + multiple include optimization, whether the file didn't exist or + couldn't be opened for some reason, or whether the header was flagged + not to be re-used, as it is with the obsolete `#import' directive. + + For the benefit of MS-DOS filesystems with an 8.3 filename + limitation, CPP offers the ability to treat various include file names + as aliases for the real header files with shorter names. The map from + one to the other is found in a special file called `header.gcc', stored + in the command line (or system) include directories to which the mapping + applies. This may be higher up the directory tree than the full path to + the file minus the base name. + +  + File: cppinternals.info, Node: Index, Prev: Files, Up: Top + + Index + ***** + + * Menu: + + * assertions: Hash Nodes. + * controlling macros: Guard Macros. + * escaped newlines: Lexer. + * files: Files. + * guard macros: Guard Macros. + * hash table: Hash Nodes. + * header files: Conventions. + * identifiers: Hash Nodes. + * interface: Conventions. + * lexer: Lexer. + * line numbers: Line Numbering. + * macro expansion: Macro Expansion. + * macro representation (internal): Macro Expansion. + * macros: Hash Nodes. + * multiple-include optimization: Guard Macros. + * named operators: Hash Nodes. + * newlines: Lexer. + * paste avoidance: Token Spacing. + * spacing: Token Spacing. + * token run: Lexer. + * token spacing: Token Spacing. + + +  + Tag Table: + Node: Top910 + Node: Conventions2579 + Node: Lexer3523 + Ref: Invalid identifiers11446 + Ref: Lexing a line13395 + Node: Hash Nodes18168 + Node: Macro Expansion21050 + Node: Token Spacing30015 + Node: Line Numbering35897 + Node: Guard Macros39988 + Node: Files44786 + Node: Index48250 +  + End Tag Table diff -Nrc3pad gcc-3.2.2/gcc/doc/extend.texi gcc-3.2.3/gcc/doc/extend.texi *** gcc-3.2.2/gcc/doc/extend.texi Wed Oct 9 21:31:00 2002 --- gcc-3.2.3/gcc/doc/extend.texi Fri Mar 21 15:02:35 2003 *************** the containing function. You should spe *** 843,861 **** returned by @code{__builtin_apply}. @end deftypefn - @cindex underscores in variables in macros - @cindex @samp{_} in variables in macros - @cindex local variables in macros - @cindex variables, local, in macros - @cindex macros, local variables in - - The reason for using names that start with underscores for the local - variables is to avoid conflicts with variable names that occur within the - expressions that are substituted for @code{a} and @code{b}. Eventually we - hope to design a new form of declaration syntax that allows you to declare - variables whose scopes start only after their initializers; this will be a - more reliable way to prevent such conflicts. - @node Typeof @section Referring to a Type with @code{typeof} @findex typeof --- 843,848 ---- *************** arithmetic type and evaluates each of it *** 906,911 **** --- 893,911 ---- _a > _b ? _a : _b; @}) @end example + @cindex underscores in variables in macros + @cindex @samp{_} in variables in macros + @cindex local variables in macros + @cindex variables, local, in macros + @cindex macros, local variables in + + The reason for using names that start with underscores for the local + variables is to avoid conflicts with variable names that occur within the + expressions that are substituted for @code{a} and @code{b}. Eventually we + hope to design a new form of declaration syntax that allows you to declare + variables whose scopes start only after their initializers; this will be a + more reliable way to prevent such conflicts. + @noindent Some more examples of the use of @code{typeof}: *************** empty string. *** 6072,6078 **** This pragma is similar in intent to to the asm labels extension (@pxref{Asm Labels}) in that the system programmer wants to change the assembly-level ABI without changing the source-level API. The ! preprocessor defines @code{__EXTERN_PREFIX} if the pragma is available. @end table @node Unnamed Fields --- 6072,6079 ---- This pragma is similar in intent to to the asm labels extension (@pxref{Asm Labels}) in that the system programmer wants to change the assembly-level ABI without changing the source-level API. The ! preprocessor defines @code{__PRAGMA_EXTERN_PREFIX} if the pragma is ! available. @end table @node Unnamed Fields diff -Nrc3pad gcc-3.2.2/gcc/doc/fsf-funding.7 gcc-3.2.3/gcc/doc/fsf-funding.7 *** gcc-3.2.2/gcc/doc/fsf-funding.7 Wed Feb 5 03:13:59 2003 --- gcc-3.2.3/gcc/doc/fsf-funding.7 Tue Apr 22 07:07:34 2003 *************** *** 1,5 **** .\" Automatically generated by Pod::Man version 1.15 ! .\" Wed Feb 5 03:13:59 2003 .\" .\" Standard preamble: .\" ====================================================================== --- 1,5 ---- .\" Automatically generated by Pod::Man version 1.15 ! .\" Tue Apr 22 07:07:34 2003 .\" .\" Standard preamble: .\" ====================================================================== *************** *** 138,144 **** .\" ====================================================================== .\" .IX Title "fsf-funding 7" ! .TH fsf-funding 7 "gcc-3.2.2" "2003-02-05" "GNU" .UC .SH "NAME" fsf-funding \- Funding Free Software --- 138,144 ---- .\" ====================================================================== .\" .IX Title "fsf-funding 7" ! .TH fsf-funding 7 "gcc-3.2.3" "2003-04-22" "GNU" .UC .SH "NAME" fsf-funding \- Funding Free Software diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.1 gcc-3.2.3/gcc/doc/gcc.1 *** gcc-3.2.2/gcc/doc/gcc.1 Wed Feb 5 03:13:59 2003 --- gcc-3.2.3/gcc/doc/gcc.1 Tue Apr 22 07:07:33 2003 *************** *** 1,5 **** .\" Automatically generated by Pod::Man version 1.15 ! .\" Wed Feb 5 03:13:56 2003 .\" .\" Standard preamble: .\" ====================================================================== --- 1,5 ---- .\" Automatically generated by Pod::Man version 1.15 ! .\" Tue Apr 22 07:07:29 2003 .\" .\" Standard preamble: .\" ====================================================================== *************** *** 138,144 **** .\" ====================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "gcc-3.2.2" "2003-02-05" "GNU" .UC .SH "NAME" gcc \- \s-1GNU\s0 project C and \*(C+ compiler --- 138,144 ---- .\" ====================================================================== .\" .IX Title "GCC 1" ! .TH GCC 1 "gcc-3.2.3" "2003-04-22" "GNU" .UC .SH "NAME" gcc \- \s-1GNU\s0 project C and \*(C+ compiler diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info gcc-3.2.3/gcc/doc/gcc.info *** gcc-3.2.2/gcc/doc/gcc.info Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,265 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + Indirect: + gcc.info-1: 1225 + gcc.info-2: 46116 + gcc.info-3: 79123 + gcc.info-4: 112372 + gcc.info-5: 161065 + gcc.info-6: 194212 + gcc.info-7: 240279 + gcc.info-8: 286354 + gcc.info-9: 335494 + gcc.info-10: 372165 + gcc.info-11: 421193 + gcc.info-12: 462678 + gcc.info-13: 510634 + gcc.info-14: 554468 + gcc.info-15: 603958 + gcc.info-16: 613610 + gcc.info-17: 670545 + gcc.info-18: 719787 + gcc.info-19: 761299 + gcc.info-20: 804819 + gcc.info-21: 854438 + gcc.info-22: 899250 + gcc.info-23: 969159 +  + Tag Table: + (Indirect) + Node: Top1225 + Node: G++ and GCC2941 + Node: Standards5494 + Node: Invoking GCC12730 + Node: Option Summary16379 + Node: Overall Options37807 + Node: Invoking G++44670 + Node: C Dialect Options46116 + Node: C++ Dialect Options59639 + Node: Objective-C Dialect Options75711 + Node: Language Independent Options77335 + Node: Warning Options79123 + Node: Debugging Options112372 + Node: Optimize Options131328 + Node: Preprocessor Options161065 + Ref: -MF167647 + Node: Assembler Options180438 + Node: Link Options180805 + Ref: Link Options-Footnote-1188884 + Node: Directory Options189220 + Node: Spec Files194212 + Node: Target Options211719 + Node: Submodel Options215706 + Node: M680x0 Options217488 + Node: M68hc1x Options223496 + Node: VAX Options224677 + Node: SPARC Options225213 + Node: Convex Options234702 + Node: AMD29K Options236883 + Node: ARM Options240279 + Node: MN10200 Options252800 + Node: MN10300 Options253322 + Node: M32R/D Options254373 + Node: M88K Options256832 + Node: RS/6000 and PowerPC Options264756 + Node: RT Options284651 + Node: MIPS Options286354 + Node: i386 and x86-64 Options298035 + Node: HPPA Options312613 + Node: Intel 960 Options316689 + Node: DEC Alpha Options319632 + Node: DEC Alpha/VMS Options330649 + Node: Clipper Options331027 + Node: H8/300 Options331431 + Node: SH Options332360 + Node: System V Options334676 + Node: TMS320C3x/C4x Options335494 + Node: V850 Options341007 + Node: ARC Options343016 + Node: NS32K Options344218 + Node: AVR Options348468 + Node: MCore Options350269 + Node: IA-64 Options351413 + Node: D30V Options353801 + Node: S/390 and zSeries Options355044 + Node: CRIS Options356978 + Node: MMIX Options361012 + Node: PDP-11 Options363352 + Node: Xstormy16 Options365178 + Node: Xtensa Options365454 + Node: Code Gen Options372165 + Node: Environment Variables387980 + Ref: DEPENDENCIES_OUTPUT394297 + Node: Running Protoize395357 + Node: C Implementation401714 + Node: Translation implementation402648 + Node: Environment implementation403016 + Node: Identifiers implementation403309 + Node: Characters implementation403712 + Node: Integers implementation405569 + Node: Floating point implementation406421 + Node: Arrays and pointers implementation408270 + Ref: Arrays and pointers implementation-Footnote-1409573 + Node: Hints implementation409699 + Node: Structures unions enumerations and bit-fields implementation410128 + Node: Qualifiers implementation410937 + Node: Preprocessing directives implementation411248 + Node: Library functions implementation412865 + Node: Architecture implementation413190 + Node: Locale-specific behavior implementation413755 + Node: C Extensions414053 + Node: Statement Exprs418139 + Node: Local Labels421193 + Node: Labels as Values423258 + Ref: Labels as Values-Footnote-1425317 + Node: Nested Functions425502 + Node: Constructing Calls429340 + Node: Typeof431421 + Node: Lvalues434597 + Node: Conditionals437037 + Node: Long Long437928 + Node: Complex439427 + Node: Hex Floats442095 + Node: Zero Length443124 + Node: Variable Length446168 + Node: Variadic Macros448930 + Node: Escaped Newlines451320 + Node: Multi-line Strings452203 + Node: Subscripting452807 + Node: Pointer Arith453535 + Node: Initializers454100 + Node: Compound Literals454583 + Node: Designated Inits456746 + Node: Case Ranges460420 + Node: Cast to Union461100 + Node: Mixed Declarations462183 + Node: Function Attributes462678 + Node: Attribute Syntax484657 + Node: Function Prototypes495034 + Node: C++ Comments496827 + Node: Dollar Signs497422 + Node: Character Escapes497880 + Node: Alignment498167 + Node: Variable Attributes499487 + Node: Type Attributes510634 + Node: Inline521165 + Node: Extended Asm525874 + Node: Constraints542991 + Node: Simple Constraints543834 + Node: Multi-Alternative550324 + Node: Modifiers552035 + Node: Machine Constraints554468 + Node: Asm Labels571062 + Node: Explicit Reg Vars572738 + Node: Global Reg Vars574192 + Node: Local Reg Vars578757 + Node: Alternate Keywords580557 + Node: Incomplete Enums582244 + Node: Function Names583000 + Node: Return Address585437 + Node: Vector Extensions588016 + Node: Other Builtins590901 + Node: Target Builtins603457 + Node: X86 Built-in Functions603958 + Node: PowerPC AltiVec Built-in Functions613610 + Node: Pragmas670545 + Node: ARM Pragmas671011 + Node: Darwin Pragmas671605 + Node: Solaris Pragmas672644 + Node: Tru64 Pragmas673207 + Node: Unnamed Fields673948 + Node: C++ Extensions675019 + Node: Min and Max676580 + Node: Volatiles677964 + Node: Restricted Pointers681334 + Node: Vague Linkage682904 + Node: C++ Interface686563 + Ref: C++ Interface-Footnote-1691651 + Node: Template Instantiation691790 + Node: Bound member functions700621 + Node: C++ Attributes702172 + Node: Java Exceptions703777 + Node: Deprecated Features705174 + Node: Backwards Compatibility707140 + Node: Objective-C708488 + Node: Executing code before main709067 + Node: What you can and what you cannot do in +load711705 + Node: Type encoding713871 + Node: Garbage Collection717123 + Node: Constant string objects719787 + Node: compatibility_alias721421 + Node: Compatibility722300 + Node: Gcov728887 + Node: Gcov Intro729356 + Node: Invoking Gcov732031 + Node: Gcov and Optimization738105 + Node: Gcov Data Files739522 + Node: Trouble743087 + Node: Actual Bugs744681 + Node: Cross-Compiler Problems745589 + Node: Interoperation747099 + Node: External Bugs759807 + Node: Incompatibilities761299 + Node: Fixed Headers770907 + Node: Standard Libraries773216 + Node: Disappointments774586 + Node: C++ Misunderstandings779308 + Node: Static Definitions780034 + Node: Temporaries781081 + Node: Copy Assignment783058 + Node: Protoize Caveats784876 + Node: Non-bugs788831 + Node: Warnings and Errors798723 + Node: Bugs800483 + Node: Bug Criteria801836 + Node: Bug Lists804260 + Node: Bug Reporting804819 + Node: gccbug816922 + Node: Service817742 + Node: Contributing818488 + Node: VMS819227 + Node: Include Files and VMS819609 + Node: Global Declarations823474 + Node: VMS Misc827778 + Node: Funding832081 + Node: GNU Project834576 + Node: Copying835227 + Node: GNU Free Documentation License854438 + Node: Contributors874322 + Node: Option Index899250 + Node: Index969159 +  + End Tag Table diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-1 gcc-3.2.3/gcc/doc/gcc.info-1 *** gcc-3.2.2/gcc/doc/gcc.info-1 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-1 Tue Apr 22 07:07:13 2003 *************** *** 0 **** --- 1,1071 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Top, Next: G++ and GCC, Up: (DIR) + + Introduction + ************ + + This manual documents how to use the GNU compilers, as well as their + features and incompatibilities, and how to report bugs. It corresponds + to GCC version 3.2.3. The internals of the GNU compilers, including + how to port them to new targets and some information about how to write + front ends for new languages, are documented in a separate manual. + *Note Introduction: (gccint)Top. + + * Menu: + + * G++ and GCC:: You can compile C or C++ programs. + * Standards:: Language standards supported by GCC. + * Invoking GCC:: Command options supported by `gcc'. + * C Implementation:: How GCC implements the ISO C specification. + * C Extensions:: GNU extensions to the C language family. + * C++ Extensions:: GNU extensions to the C++ language. + * Objective-C:: GNU Objective-C runtime features. + * Compatibility:: Binary Compatibility + * Gcov:: `gcov'---a test coverage program. + * Trouble:: If you have trouble using GCC. + * Bugs:: How, why and where to report bugs. + * Service:: How to find suppliers of support for GCC. + * Contributing:: How to contribute to testing and developing GCC. + * VMS:: Using GCC on VMS. + + * Funding:: How to help assure funding for free software. + * GNU Project:: The GNU Project and GNU/Linux. + + * Copying:: GNU General Public License says + how you can copy and share GCC. + * GNU Free Documentation License:: How you can copy and share this manual. + * Contributors:: People who have contributed to GCC. + + * Option Index:: Index to command line options. + * Index:: Index of concepts and symbol names. + +  + File: gcc.info, Node: G++ and GCC, Next: Standards, Prev: Top, Up: Top + + Compile C, C++, Objective-C, Ada, Fortran, or Java + ************************************************** + + Several versions of the compiler (C, C++, Objective-C, Ada, Fortran, + and Java) are integrated; this is why we use the name "GNU Compiler + Collection". GCC can compile programs written in any of these + languages. The Ada, Fortran, and Java compilers are described in + separate manuals. + + "GCC" is a common shorthand term for the GNU Compiler Collection. + This is both the most general name for the compiler, and the name used + when the emphasis is on compiling C programs (as the abbreviation + formerly stood for "GNU C Compiler"). + + When referring to C++ compilation, it is usual to call the compiler + "G++". Since there is only one compiler, it is also accurate to call + it "GCC" no matter what the language context; however, the term "G++" + is more useful when the emphasis is on compiling C++ programs. + + Similarly, when we talk about Ada compilation, we usually call the + compiler "GNAT", for the same reasons. + + We use the name "GCC" to refer to the compilation system as a whole, + and more specifically to the language-independent part of the compiler. + For example, we refer to the optimization options as affecting the + behavior of "GCC" or sometimes just "the compiler". + + Front ends for other languages, such as Mercury and Pascal exist but + have not yet been integrated into GCC. These front ends, like that for + C++, are built in subdirectories of GCC and link to it. The result is + an integrated compiler that can compile programs written in C, C++, + Objective-C, or any of the languages for which you have installed front + ends. + + In this manual, we only discuss the options for the C, Objective-C, + and C++ compilers and those of the GCC core. Consult the documentation + of the other front ends for the options to use when compiling programs + written in other languages. + + G++ is a _compiler_, not merely a preprocessor. G++ builds object + code directly from your C++ program source. There is no intermediate C + version of the program. (By contrast, for example, some other + implementations use a program that generates a C program from your C++ + source.) Avoiding an intermediate C representation of the program means + that you get better object code, and better debugging information. The + GNU debugger, GDB, works with this information in the object code to + give you comprehensive C++ source-level editing capabilities (*note C + and C++: (gdb.info)C.). + +  + File: gcc.info, Node: Standards, Next: Invoking GCC, Prev: G++ and GCC, Up: Top + + Language Standards Supported by GCC + *********************************** + + For each language compiled by GCC for which there is a standard, GCC + attempts to follow one or more versions of that standard, possibly with + some exceptions, and possibly with some extensions. + + GCC supports three versions of the C standard, although support for + the most recent version is not yet complete. + + The original ANSI C standard (X3.159-1989) was ratified in 1989 and + published in 1990. This standard was ratified as an ISO standard + (ISO/IEC 9899:1990) later in 1990. There were no technical differences + between these publications, although the sections of the ANSI standard + were renumbered and became clauses in the ISO standard. This standard, + in both its forms, is commonly known as "C89", or occasionally as + "C90", from the dates of ratification. The ANSI standard, but not the + ISO standard, also came with a Rationale document. To select this + standard in GCC, use one of the options `-ansi', `-std=c89' or + `-std=iso9899:1990'; to obtain all the diagnostics required by the + standard, you should also specify `-pedantic' (or `-pedantic-errors' if + you want them to be errors rather than warnings). *Note Options + Controlling C Dialect: C Dialect Options. + + Errors in the 1990 ISO C standard were corrected in two Technical + Corrigenda published in 1994 and 1996. GCC does not support the + uncorrected version. + + An amendment to the 1990 standard was published in 1995. This + amendment added digraphs and `__STDC_VERSION__' to the language, but + otherwise concerned the library. This amendment is commonly known as + "AMD1"; the amended standard is sometimes known as "C94" or "C95". To + select this standard in GCC, use the option `-std=iso9899:199409' + (with, as for other standard versions, `-pedantic' to receive all + required diagnostics). + + A new edition of the ISO C standard was published in 1999 as ISO/IEC + 9899:1999, and is commonly known as "C99". GCC has incomplete support + for this standard version; see + `http://gcc.gnu.org/gcc-3.1/c99status.html' for details. To select this + standard, use `-std=c99' or `-std=iso9899:1999'. (While in + development, drafts of this standard version were referred to as "C9X".) + + Errors in the 1999 ISO C standard were corrected in a Technical + Corrigendum published in 2001. GCC does not support the uncorrected + version. + + GCC also has some limited support for traditional (pre-ISO) C with + the `-traditional' option. This support may be of use for compiling + some very old programs that have not been updated to ISO C, but should + not be used for new programs. It will not work with some modern C + libraries such as the GNU C library. + + By default, GCC provides some extensions to the C language that on + rare occasions conflict with the C standard. *Note Extensions to the C + Language Family: C Extensions. Use of the `-std' options listed above + will disable these extensions where they conflict with the C standard + version selected. You may also select an extended version of the C + language explicitly with `-std=gnu89' (for C89 with GNU extensions) or + `-std=gnu99' (for C99 with GNU extensions). The default, if no C + language dialect options are given, is `-std=gnu89'; this will change to + `-std=gnu99' in some future release when the C99 support is complete. + Some features that are part of the C99 standard are accepted as + extensions in C89 mode. + + The ISO C standard defines (in clause 4) two classes of conforming + implementation. A "conforming hosted implementation" supports the + whole standard including all the library facilities; a "conforming + freestanding implementation" is only required to provide certain + library facilities: those in `', `', `', + and `'; since AMD1, also those in `'; and in C99, + also those in `' and `'. In addition, complex + types, added in C99, are not required for freestanding implementations. + The standard also defines two environments for programs, a + "freestanding environment", required of all implementations and which + may not have library facilities beyond those required of freestanding + implementations, where the handling of program startup and termination + are implementation-defined, and a "hosted environment", which is not + required, in which all the library facilities are provided and startup + is through a function `int main (void)' or `int main (int, char *[])'. + An OS kernel would be a freestanding environment; a program using the + facilities of an operating system would normally be in a hosted + implementation. + + GCC aims towards being usable as a conforming freestanding + implementation, or as the compiler for a conforming hosted + implementation. By default, it will act as the compiler for a hosted + implementation, defining `__STDC_HOSTED__' as `1' and presuming that + when the names of ISO C functions are used, they have the semantics + defined in the standard. To make it act as a conforming freestanding + implementation for a freestanding environment, use the option + `-ffreestanding'; it will then define `__STDC_HOSTED__' to `0' and not + make assumptions about the meanings of function names from the standard + library, with exceptions noted below. To build an OS kernel, you may + well still need to make your own arrangements for linking and startup. + *Note Options Controlling C Dialect: C Dialect Options. + + GCC does not provide the library facilities required only of hosted + implementations, nor yet all the facilities required by C99 of + freestanding implementations; to use the facilities of a hosted + environment, you will need to find them elsewhere (for example, in the + GNU C library). *Note Standard Libraries: Standard Libraries. + + Most of the compiler support routines used by GCC are present in + `libgcc', but there are a few exceptions. GCC requires the + freestanding environment provide `memcpy', `memmove', `memset' and + `memcmp'. Some older ports of GCC are configured to use the BSD + `bcopy', `bzero' and `bcmp' functions instead, but this is deprecated + for new ports. Finally, if `__builtin_trap' is used, and the target + does not implement the `trap' pattern, then GCC will emit a call to + `abort'. + + For references to Technical Corrigenda, Rationale documents and + information concerning the history of C that is available online, see + `http://gcc.gnu.org/readings.html' + + There is no formal written standard for Objective-C. The most + authoritative manual is "Object-Oriented Programming and the + Objective-C Language", available at a number of web sites + + * `http://developer.apple.com/techpubs/macosx/Cocoa/ObjectiveC/' is + a recent version + + * `http://www.toodarkpark.org/computers/objc/' is an older example + + * `http://www.gnustep.org' has additional useful information + + *Note GNAT Reference Manual: (gnat_rm)Top, for information on + standard conformance and compatibility of the Ada compiler. + + *Note The GNU Fortran Language: (g77)Language, for details of the + Fortran language supported by GCC. + + *Note Compatibility with the Java Platform: (gcj)Compatibility, for + details of compatibility between `gcj' and the Java Platform. + +  + File: gcc.info, Node: Invoking GCC, Next: C Implementation, Prev: Standards, Up: Top + + GCC Command Options + ******************* + + When you invoke GCC, it normally does preprocessing, compilation, + assembly and linking. The "overall options" allow you to stop this + process at an intermediate stage. For example, the `-c' option says + not to run the linker. Then the output consists of object files output + by the assembler. + + Other options are passed on to one stage of processing. Some options + control the preprocessor and others the compiler itself. Yet other + options control the assembler and linker; most of these are not + documented here, since you rarely need to use any of them. + + Most of the command line options that you can use with GCC are useful + for C programs; when an option is only useful with another language + (usually C++), the explanation says so explicitly. If the description + for a particular option does not mention a source language, you can use + that option with all supported languages. + + *Note Compiling C++ Programs: Invoking G++, for a summary of special + options for compiling C++ programs. + + The `gcc' program accepts options and file names as operands. Many + options have multi-letter names; therefore multiple single-letter + options may _not_ be grouped: `-dr' is very different from `-d -r'. + + You can mix options and other arguments. For the most part, the + order you use doesn't matter. Order does matter when you use several + options of the same kind; for example, if you specify `-L' more than + once, the directories are searched in the order specified. + + Many options have long names starting with `-f' or with `-W'--for + example, `-fforce-mem', `-fstrength-reduce', `-Wformat' and so on. + Most of these have both positive and negative forms; the negative form + of `-ffoo' would be `-fno-foo'. This manual documents only one of + these two forms, whichever one is not the default. + + *Note Option Index::, for an index to GCC's options. + + * Menu: + + * Option Summary:: Brief list of all options, without explanations. + * Overall Options:: Controlling the kind of output: + an executable, object files, assembler files, + or preprocessed source. + * Invoking G++:: Compiling C++ programs. + * C Dialect Options:: Controlling the variant of C language compiled. + * C++ Dialect Options:: Variations on C++. + * Objective-C Dialect Options:: Variations on Objective-C. + * Language Independent Options:: Controlling how diagnostics should be + formatted. + * Warning Options:: How picky should the compiler be? + * Debugging Options:: Symbol tables, measurements, and debugging dumps. + * Optimize Options:: How much optimization? + * Preprocessor Options:: Controlling header files and macro definitions. + Also, getting dependency information for Make. + * Assembler Options:: Passing options to the assembler. + * Link Options:: Specifying libraries and so on. + * Directory Options:: Where to find header files and libraries. + Where to find the compiler executable files. + * Spec Files:: How to pass switches to sub-processes. + * Target Options:: Running a cross-compiler, or an old version of GCC. + * Submodel Options:: Specifying minor hardware or convention variations, + such as 68010 vs 68020. + * Code Gen Options:: Specifying conventions for function calls, data layout + and register usage. + * Environment Variables:: Env vars that affect GCC. + * Running Protoize:: Automatically adding or removing function prototypes. + +  + File: gcc.info, Node: Option Summary, Next: Overall Options, Up: Invoking GCC + + Option Summary + ============== + + Here is a summary of all the options, grouped by type. Explanations + are in the following sections. + + _Overall Options_ + *Note Options Controlling the Kind of Output: Overall Options. + -c -S -E -o FILE -pipe -pass-exit-codes -x LANGUAGE + -v -### --help --target-help --version + + _C Language Options_ + *Note Options Controlling C Dialect: C Dialect Options. + -ansi -std=STANDARD -aux-info FILENAME + -fno-asm -fno-builtin -fno-builtin-FUNCTION + -fhosted -ffreestanding + -trigraphs -no-integrated-cpp -traditional -traditional-cpp + -fallow-single-precision -fcond-mismatch + -fsigned-bitfields -fsigned-char + -funsigned-bitfields -funsigned-char + -fwritable-strings + + _C++ Language Options_ + *Note Options Controlling C++ Dialect: C++ Dialect Options. + -fno-access-control -fcheck-new -fconserve-space + -fno-const-strings -fdollars-in-identifiers + -fno-elide-constructors + -fno-enforce-eh-specs -fexternal-templates + -falt-external-templates + -ffor-scope -fno-for-scope -fno-gnu-keywords + -fno-implicit-templates + -fno-implicit-inline-templates + -fno-implement-inlines -fms-extensions + -fno-nonansi-builtins -fno-operator-names + -fno-optional-diags -fpermissive + -frepo -fno-rtti -fstats -ftemplate-depth-N + -fuse-cxa-atexit -fvtable-gc -fno-weak -nostdinc++ + -fno-default-inline -Wabi -Wctor-dtor-privacy + -Wnon-virtual-dtor -Wreorder + -Weffc++ -Wno-deprecated + -Wno-non-template-friend -Wold-style-cast + -Woverloaded-virtual -Wno-pmf-conversions + -Wsign-promo -Wsynth + + _Objective-C Language Options_ + *Note Options Controlling Objective-C Dialect: Objective-C Dialect + Options. + -fconstant-string-class=CLASS-NAME + -fgnu-runtime -fnext-runtime -gen-decls + -Wno-protocol -Wselector + + _Language Independent Options_ + *Note Options to Control Diagnostic Messages Formatting: Language + Independent Options. + -fmessage-length=N + -fdiagnostics-show-location=[once|every-line] + + _Warning Options_ + *Note Options to Request or Suppress Warnings: Warning Options. + -fsyntax-only -pedantic -pedantic-errors + -w -W -Wall -Waggregate-return + -Wcast-align -Wcast-qual -Wchar-subscripts -Wcomment + -Wconversion -Wno-deprecated-declarations + -Wdisabled-optimization -Wdiv-by-zero -Werror + -Wfloat-equal -Wformat -Wformat=2 + -Wformat-nonliteral -Wformat-security + -Wimplicit -Wimplicit-int + -Wimplicit-function-declaration + -Werror-implicit-function-declaration + -Wimport -Winline + -Wlarger-than-LEN -Wlong-long + -Wmain -Wmissing-braces + -Wmissing-format-attribute -Wmissing-noreturn + -Wmultichar -Wno-format-extra-args -Wno-format-y2k + -Wno-import -Wpacked -Wpadded + -Wparentheses -Wpointer-arith -Wredundant-decls + -Wreturn-type -Wsequence-point -Wshadow + -Wsign-compare -Wswitch -Wsystem-headers + -Wtrigraphs -Wundef -Wuninitialized + -Wunknown-pragmas -Wunreachable-code + -Wunused -Wunused-function -Wunused-label -Wunused-parameter + -Wunused-value -Wunused-variable -Wwrite-strings + + _C-only Warning Options_ + -Wbad-function-cast -Wmissing-declarations + -Wmissing-prototypes -Wnested-externs + -Wstrict-prototypes -Wtraditional + + _Debugging Options_ + *Note Options for Debugging Your Program or GCC: Debugging Options. + -dLETTERS -dumpspecs -dumpmachine -dumpversion + -fdump-unnumbered -fdump-translation-unit[-N] + -fdump-class-hierarchy[-N] + -fdump-tree-original[-N] -fdump-tree-optimized[-N] + -fdump-tree-inlined[-N] + -fmem-report -fpretend-float + -fprofile-arcs -fsched-verbose=N + -ftest-coverage -ftime-report + -g -gLEVEL -gcoff -gdwarf -gdwarf-1 -gdwarf-1+ -gdwarf-2 + -ggdb -gstabs -gstabs+ -gvms -gxcoff -gxcoff+ + -p -pg -print-file-name=LIBRARY -print-libgcc-file-name + -print-multi-directory -print-multi-lib + -print-prog-name=PROGRAM -print-search-dirs -Q + -save-temps -time + + _Optimization Options_ + *Note Options that Control Optimization: Optimize Options. + -falign-functions=N -falign-jumps=N + -falign-labels=N -falign-loops=N + -fbounds-check + -fbranch-probabilities -fcaller-saves -fcprop-registers + -fcse-follow-jumps -fcse-skip-blocks -fdata-sections + -fdelayed-branch -fdelete-null-pointer-checks + -fexpensive-optimizations -ffast-math -ffloat-store + -fforce-addr -fforce-mem -ffunction-sections + -fgcse -fgcse-lm -fgcse-sm + -finline-functions -finline-limit=N -fkeep-inline-functions + -fkeep-static-consts -fmerge-constants -fmerge-all-constants + -fmove-all-movables -fno-branch-count-reg + -fno-default-inline -fno-defer-pop + -fno-function-cse -fno-guess-branch-probability + -fno-inline -fno-math-errno -fno-peephole -fno-peephole2 + -funsafe-math-optimizations -fno-trapping-math + -fomit-frame-pointer -foptimize-register-move + -foptimize-sibling-calls -fprefetch-loop-arrays + -freduce-all-givs -fregmove -frename-registers + -frerun-cse-after-loop -frerun-loop-opt + -fschedule-insns -fschedule-insns2 + -fno-sched-interblock -fno-sched-spec + -fsched-spec-load -fsched-spec-load-dangerous + -fsingle-precision-constant -fssa -fssa-ccp -fssa-dce + -fstrength-reduce -fstrict-aliasing -fthread-jumps + -ftrapv -funroll-all-loops -funroll-loops + --param NAME=VALUE + -O -O0 -O1 -O2 -O3 -Os + + _Preprocessor Options_ + *Note Options Controlling the Preprocessor: Preprocessor Options. + -$ -AQUESTION=ANSWER -A-QUESTION[=ANSWER] + -C -dD -dI -dM -dN + -DMACRO[=DEFN] -E -H + -idirafter DIR + -include FILE -imacros FILE + -iprefix FILE -iwithprefix DIR + -iwithprefixbefore DIR -isystem DIR + -M -MM -MF -MG -MP -MQ -MT -nostdinc -P -remap + -trigraphs -undef -UMACRO -Wp,OPTION + + _Assembler Option_ + *Note Passing Options to the Assembler: Assembler Options. + -Wa,OPTION + + _Linker Options_ + *Note Options for Linking: Link Options. + OBJECT-FILE-NAME -lLIBRARY + -nostartfiles -nodefaultlibs -nostdlib + -s -static -static-libgcc -shared -shared-libgcc -symbolic + -Wl,OPTION -Xlinker OPTION + -u SYMBOL + + _Directory Options_ + *Note Options for Directory Search: Directory Options. + -BPREFIX -IDIR -I- -LDIR -specs=FILE + + _Target Options_ + *Note Target Options::. + -b MACHINE -V VERSION + + _Machine Dependent Options_ + *Note Hardware Models and Configurations: Submodel Options. + + _M680x0 Options_ + -m68000 -m68020 -m68020-40 -m68020-60 -m68030 -m68040 + -m68060 -mcpu32 -m5200 -m68881 -mbitfield -mc68000 -mc68020 + -mfpa -mnobitfield -mrtd -mshort -msoft-float -mpcrel + -malign-int -mstrict-align + + _M68hc1x Options_ + -m6811 -m6812 -m68hc11 -m68hc12 + -mauto-incdec -mshort -msoft-reg-count=COUNT + + _VAX Options_ + -mg -mgnu -munix + + _SPARC Options_ + -mcpu=CPU-TYPE + -mtune=CPU-TYPE + -mcmodel=CODE-MODEL + -m32 -m64 + -mapp-regs -mbroken-saverestore -mcypress + -mfaster-structs -mflat + -mfpu -mhard-float -mhard-quad-float + -mimpure-text -mlive-g0 -mno-app-regs + -mno-faster-structs -mno-flat -mno-fpu + -mno-impure-text -mno-stack-bias -mno-unaligned-doubles + -msoft-float -msoft-quad-float -msparclite -mstack-bias + -msupersparc -munaligned-doubles -mv8 + + _Convex Options_ + -mc1 -mc2 -mc32 -mc34 -mc38 + -margcount -mnoargcount + -mlong32 -mlong64 + -mvolatile-cache -mvolatile-nocache + + _AMD29K Options_ + -m29000 -m29050 -mbw -mnbw -mdw -mndw + -mlarge -mnormal -msmall + -mkernel-registers -mno-reuse-arg-regs + -mno-stack-check -mno-storem-bug + -mreuse-arg-regs -msoft-float -mstack-check + -mstorem-bug -muser-registers + + _ARM Options_ + -mapcs-frame -mno-apcs-frame + -mapcs-26 -mapcs-32 + -mapcs-stack-check -mno-apcs-stack-check + -mapcs-float -mno-apcs-float + -mapcs-reentrant -mno-apcs-reentrant + -msched-prolog -mno-sched-prolog + -mlittle-endian -mbig-endian -mwords-little-endian + -malignment-traps -mno-alignment-traps + -msoft-float -mhard-float -mfpe + -mthumb-interwork -mno-thumb-interwork + -mcpu=NAME -march=NAME -mfpe=NAME + -mstructure-size-boundary=N + -mbsd -mxopen -mno-symrename + -mabort-on-noreturn + -mlong-calls -mno-long-calls + -msingle-pic-base -mno-single-pic-base + -mpic-register=REG + -mnop-fun-dllimport + -mpoke-function-name + -mthumb -marm + -mtpcs-frame -mtpcs-leaf-frame + -mcaller-super-interworking -mcallee-super-interworking + + _MN10200 Options_ + -mrelax + + _MN10300 Options_ + -mmult-bug -mno-mult-bug + -mam33 -mno-am33 + -mno-crt0 -mrelax + + _M32R/D Options_ + -m32rx -m32r -mcode-model=MODEL-TYPE -msdata=SDATA-TYPE + -G NUM + + _M88K Options_ + -m88000 -m88100 -m88110 -mbig-pic + -mcheck-zero-division -mhandle-large-shift + -midentify-revision -mno-check-zero-division + -mno-ocs-debug-info -mno-ocs-frame-position + -mno-optimize-arg-area -mno-serialize-volatile + -mno-underscores -mocs-debug-info + -mocs-frame-position -moptimize-arg-area + -mserialize-volatile -mshort-data-NUM -msvr3 + -msvr4 -mtrap-large-shift -muse-div-instruction + -mversion-03.00 -mwarn-passed-structs + + _RS/6000 and PowerPC Options_ + -mcpu=CPU-TYPE + -mtune=CPU-TYPE + -mpower -mno-power -mpower2 -mno-power2 + -mpowerpc -mpowerpc64 -mno-powerpc + -maltivec -mno-altivec + -mpowerpc-gpopt -mno-powerpc-gpopt + -mpowerpc-gfxopt -mno-powerpc-gfxopt + -mnew-mnemonics -mold-mnemonics + -mfull-toc -mminimal-toc -mno-fp-in-toc -mno-sum-in-toc + -m64 -m32 -mxl-call -mno-xl-call -mpe + -msoft-float -mhard-float -mmultiple -mno-multiple + -mstring -mno-string -mupdate -mno-update + -mfused-madd -mno-fused-madd -mbit-align -mno-bit-align + -mstrict-align -mno-strict-align -mrelocatable + -mno-relocatable -mrelocatable-lib -mno-relocatable-lib + -mtoc -mno-toc -mlittle -mlittle-endian -mbig -mbig-endian + -mcall-aix -mcall-sysv -mcall-netbsd + -maix-struct-return -msvr4-struct-return + -mabi=altivec -mabi=no-altivec + -mprototype -mno-prototype + -msim -mmvme -mads -myellowknife -memb -msdata + -msdata=OPT -mvxworks -G NUM -pthread + + _RT Options_ + -mcall-lib-mul -mfp-arg-in-fpregs -mfp-arg-in-gregs + -mfull-fp-blocks -mhc-struct-return -min-line-mul + -mminimum-fp-blocks -mnohc-struct-return + + _MIPS Options_ + -mabicalls -march=CPU-TYPE -mtune=CPU=TYPE + -mcpu=CPU-TYPE -membedded-data -muninit-const-in-rodata + -membedded-pic -mfp32 -mfp64 -mfused-madd -mno-fused-madd + -mgas -mgp32 -mgp64 + -mgpopt -mhalf-pic -mhard-float -mint64 -mips1 + -mips2 -mips3 -mips4 -mlong64 -mlong32 -mlong-calls -mmemcpy + -mmips-as -mmips-tfile -mno-abicalls + -mno-embedded-data -mno-uninit-const-in-rodata + -mno-embedded-pic -mno-gpopt -mno-long-calls + -mno-memcpy -mno-mips-tfile -mno-rnames -mno-stats + -mrnames -msoft-float + -m4650 -msingle-float -mmad + -mstats -EL -EB -G NUM -nocpp + -mabi=32 -mabi=n32 -mabi=64 -mabi=eabi + -mfix7000 -mno-crt0 -mflush-func=FUNC -mno-flush-func + + _i386 and x86-64 Options_ + -mcpu=CPU-TYPE -march=CPU-TYPE -mfpmath=UNIT + -masm=DIALECT -mno-fancy-math-387 + -mno-fp-ret-in-387 -msoft-float -msvr3-shlib + -mno-wide-multiply -mrtd -malign-double + -mpreferred-stack-boundary=NUM + -mmmx -msse -msse2 -m3dnow + -mthreads -mno-align-stringops -minline-all-stringops + -mpush-args -maccumulate-outgoing-args -m128bit-long-double + -m96bit-long-double -mregparm=NUM -momit-leaf-frame-pointer + -mno-red-zone + -mcmodel=CODE-MODEL + -m32 -m64 + + _HPPA Options_ + -march=ARCHITECTURE-TYPE + -mbig-switch -mdisable-fpregs -mdisable-indexing + -mfast-indirect-calls -mgas -mjump-in-delay + -mlong-load-store -mno-big-switch -mno-disable-fpregs + -mno-disable-indexing -mno-fast-indirect-calls -mno-gas + -mno-jump-in-delay -mno-long-load-store + -mno-portable-runtime -mno-soft-float + -mno-space-regs -msoft-float -mpa-risc-1-0 + -mpa-risc-1-1 -mpa-risc-2-0 -mportable-runtime + -mschedule=CPU-TYPE -mspace-regs + + _Intel 960 Options_ + -mCPU-TYPE -masm-compat -mclean-linkage + -mcode-align -mcomplex-addr -mleaf-procedures + -mic-compat -mic2.0-compat -mic3.0-compat + -mintel-asm -mno-clean-linkage -mno-code-align + -mno-complex-addr -mno-leaf-procedures + -mno-old-align -mno-strict-align -mno-tail-call + -mnumerics -mold-align -msoft-float -mstrict-align + -mtail-call + + _DEC Alpha Options_ + -mno-fp-regs -msoft-float -malpha-as -mgas + -mieee -mieee-with-inexact -mieee-conformant + -mfp-trap-mode=MODE -mfp-rounding-mode=MODE + -mtrap-precision=MODE -mbuild-constants + -mcpu=CPU-TYPE -mtune=CPU-TYPE + -mbwx -mmax -mfix -mcix + -mfloat-vax -mfloat-ieee + -mexplicit-relocs -msmall-data -mlarge-data + -mmemory-latency=TIME + + _DEC Alpha/VMS Options_ + -mvms-return-codes + + _Clipper Options_ + -mc300 -mc400 + + _H8/300 Options_ + -mrelax -mh -ms -mint32 -malign-300 + + _SH Options_ + -m1 -m2 -m3 -m3e + -m4-nofpu -m4-single-only -m4-single -m4 + -m5-64media -m5-64media-nofpu + -m5-32media -m5-32media-nofpu + -m5-compact -m5-compact-nofpu + -mb -ml -mdalign -mrelax + -mbigtable -mfmovd -mhitachi -mnomacsave + -mieee -misize -mpadstruct -mspace + -mprefergot -musermode + + _System V Options_ + -Qy -Qn -YP,PATHS -Ym,DIR + + _ARC Options_ + -EB -EL + -mmangle-cpu -mcpu=CPU -mtext=TEXT-SECTION + -mdata=DATA-SECTION -mrodata=READONLY-DATA-SECTION + + _TMS320C3x/C4x Options_ + -mcpu=CPU -mbig -msmall -mregparm -mmemparm + -mfast-fix -mmpyi -mbk -mti -mdp-isr-reload + -mrpts=COUNT -mrptb -mdb -mloop-unsigned + -mparallel-insns -mparallel-mpy -mpreserve-float + + _V850 Options_ + -mlong-calls -mno-long-calls -mep -mno-ep + -mprolog-function -mno-prolog-function -mspace + -mtda=N -msda=N -mzda=N + -mv850 -mbig-switch + + _NS32K Options_ + -m32032 -m32332 -m32532 -m32081 -m32381 + -mmult-add -mnomult-add -msoft-float -mrtd -mnortd + -mregparam -mnoregparam -msb -mnosb + -mbitfield -mnobitfield -mhimem -mnohimem + + _AVR Options_ + -mmcu=MCU -msize -minit-stack=N -mno-interrupts + -mcall-prologues -mno-tablejump -mtiny-stack + + _MCore Options_ + -mhardlit -mno-hardlit -mdiv -mno-div -mrelax-immediates + -mno-relax-immediates -mwide-bitfields -mno-wide-bitfields + -m4byte-functions -mno-4byte-functions -mcallgraph-data + -mno-callgraph-data -mslow-bytes -mno-slow-bytes -mno-lsim + -mlittle-endian -mbig-endian -m210 -m340 -mstack-increment + + _MMIX Options_ + -mlibfuncs -mno-libfuncs -mepsilon -mno-epsilon -mabi=gnu + -mabi=mmixware -mzero-extend -mknuthdiv -mtoplevel-symbols + -melf -mbranch-predict -mno-branch-predict -mbase-addresses + -mno-base-addresses + + _IA-64 Options_ + -mbig-endian -mlittle-endian -mgnu-as -mgnu-ld -mno-pic + -mvolatile-asm-stop -mb-step -mregister-names -mno-sdata + -mconstant-gp -mauto-pic -minline-divide-min-latency + -minline-divide-max-throughput -mno-dwarf2-asm + -mfixed-range=REGISTER-RANGE + + _D30V Options_ + -mextmem -mextmemory -monchip -mno-asm-optimize + -masm-optimize -mbranch-cost=N -mcond-exec=N + + _S/390 and zSeries Options_ + -mhard-float -msoft-float -mbackchain -mno-backchain + -msmall-exec -mno-small-exec -mmvcle -mno-mvcle + -m64 -m31 -mdebug -mno-debug + + _CRIS Options_ + -mcpu=CPU -march=CPU -mtune=CPU + -mmax-stack-frame=N -melinux-stacksize=N + -metrax4 -metrax100 -mpdebug -mcc-init -mno-side-effects + -mstack-align -mdata-align -mconst-align + -m32-bit -m16-bit -m8-bit -mno-prologue-epilogue -mno-gotplt + -melf -maout -melinux -mlinux -sim -sim2 + + _PDP-11 Options_ + -mfpu -msoft-float -mac0 -mno-ac0 -m40 -m45 -m10 + -mbcopy -mbcopy-builtin -mint32 -mno-int16 + -mint16 -mno-int32 -mfloat32 -mno-float64 + -mfloat64 -mno-float32 -mabshi -mno-abshi + -mbranch-expensive -mbranch-cheap + -msplit -mno-split -munix-asm -mdec-asm + + _Xstormy16 Options_ + -msim + + _Xtensa Options_ + -mbig-endian -mlittle-endian + -mdensity -mno-density + -mmac16 -mno-mac16 + -mmul16 -mno-mul16 + -mmul32 -mno-mul32 + -mnsa -mno-nsa + -mminmax -mno-minmax + -msext -mno-sext + -mbooleans -mno-booleans + -mhard-float -msoft-float + -mfused-madd -mno-fused-madd + -mserialize-volatile -mno-serialize-volatile + -mtext-section-literals -mno-text-section-literals + -mtarget-align -mno-target-align + -mlongcalls -mno-longcalls + + _Code Generation Options_ + *Note Options for Code Generation Conventions: Code Gen Options. + -fcall-saved-REG -fcall-used-REG + -ffixed-REG -fexceptions + -fnon-call-exceptions -funwind-tables + -fasynchronous-unwind-tables + -finhibit-size-directive -finstrument-functions + -fno-common -fno-ident -fno-gnu-linker + -fpcc-struct-return -fpic -fPIC + -freg-struct-return -fshared-data -fshort-enums + -fshort-double -fshort-wchar -fvolatile + -fvolatile-global -fvolatile-static + -fverbose-asm -fpack-struct -fstack-check + -fstack-limit-register=REG -fstack-limit-symbol=SYM + -fargument-alias -fargument-noalias + -fargument-noalias-global -fleading-underscore + + + * Menu: + + * Overall Options:: Controlling the kind of output: + an executable, object files, assembler files, + or preprocessed source. + * C Dialect Options:: Controlling the variant of C language compiled. + * C++ Dialect Options:: Variations on C++. + * Objective-C Dialect Options:: Variations on Objective-C. + * Language Independent Options:: Controlling how diagnostics should be + formatted. + * Warning Options:: How picky should the compiler be? + * Debugging Options:: Symbol tables, measurements, and debugging dumps. + * Optimize Options:: How much optimization? + * Preprocessor Options:: Controlling header files and macro definitions. + Also, getting dependency information for Make. + * Assembler Options:: Passing options to the assembler. + * Link Options:: Specifying libraries and so on. + * Directory Options:: Where to find header files and libraries. + Where to find the compiler executable files. + * Spec Files:: How to pass switches to sub-processes. + * Target Options:: Running a cross-compiler, or an old version of GCC. + +  + File: gcc.info, Node: Overall Options, Next: Invoking G++, Prev: Option Summary, Up: Invoking GCC + + Options Controlling the Kind of Output + ====================================== + + Compilation can involve up to four stages: preprocessing, compilation + proper, assembly and linking, always in that order. The first three + stages apply to an individual source file, and end by producing an + object file; linking combines all the object files (those newly + compiled, and those specified as input) into an executable file. + + For any given input file, the file name suffix determines what kind + of compilation is done: + + `FILE.c' + C source code which must be preprocessed. + + `FILE.i' + C source code which should not be preprocessed. + + `FILE.ii' + C++ source code which should not be preprocessed. + + `FILE.m' + Objective-C source code. Note that you must link with the library + `libobjc.a' to make an Objective-C program work. + + `FILE.mi' + Objective-C source code which should not be preprocessed. + + `FILE.h' + C header file (not to be compiled or linked). + + `FILE.cc' + `FILE.cp' + `FILE.cxx' + `FILE.cpp' + `FILE.c++' + `FILE.C' + C++ source code which must be preprocessed. Note that in `.cxx', + the last two letters must both be literally `x'. Likewise, `.C' + refers to a literal capital C. + + `FILE.f' + `FILE.for' + `FILE.FOR' + Fortran source code which should not be preprocessed. + + `FILE.F' + `FILE.fpp' + `FILE.FPP' + Fortran source code which must be preprocessed (with the + traditional preprocessor). + + `FILE.r' + Fortran source code which must be preprocessed with a RATFOR + preprocessor (not included with GCC). + + *Note Options Controlling the Kind of Output: (g77)Overall + Options, for more details of the handling of Fortran input files. + + `FILE.ads' + Ada source code file which contains a library unit declaration (a + declaration of a package, subprogram, or generic, or a generic + instantiation), or a library unit renaming declaration (a package, + generic, or subprogram renaming declaration). Such files are also + called "specs". + + `FILE.adb' + Ada source code file containing a library unit body (a subprogram + or package body). Such files are also called "bodies". + + `FILE.s' + Assembler code. + + `FILE.S' + Assembler code which must be preprocessed. + + `OTHER' + An object file to be fed straight into linking. Any file name + with no recognized suffix is treated this way. + + You can specify the input language explicitly with the `-x' option: + + `-x LANGUAGE' + Specify explicitly the LANGUAGE for the following input files + (rather than letting the compiler choose a default based on the + file name suffix). This option applies to all following input + files until the next `-x' option. Possible values for LANGUAGE + are: + c c-header cpp-output + c++ c++-cpp-output + objective-c objc-cpp-output + assembler assembler-with-cpp + ada + f77 f77-cpp-input ratfor + java + + `-x none' + Turn off any specification of a language, so that subsequent files + are handled according to their file name suffixes (as they are if + `-x' has not been used at all). + + `-pass-exit-codes' + Normally the `gcc' program will exit with the code of 1 if any + phase of the compiler returns a non-success return code. If you + specify `-pass-exit-codes', the `gcc' program will instead return + with numerically highest error produced by any phase that returned + an error indication. + + If you only want some of the stages of compilation, you can use `-x' + (or filename suffixes) to tell `gcc' where to start, and one of the + options `-c', `-S', or `-E' to say where `gcc' is to stop. Note that + some combinations (for example, `-x cpp-output -E') instruct `gcc' to + do nothing at all. + + `-c' + Compile or assemble the source files, but do not link. The linking + stage simply is not done. The ultimate output is in the form of an + object file for each source file. + + By default, the object file name for a source file is made by + replacing the suffix `.c', `.i', `.s', etc., with `.o'. + + Unrecognized input files, not requiring compilation or assembly, + are ignored. + + `-S' + Stop after the stage of compilation proper; do not assemble. The + output is in the form of an assembler code file for each + non-assembler input file specified. + + By default, the assembler file name for a source file is made by + replacing the suffix `.c', `.i', etc., with `.s'. + + Input files that don't require compilation are ignored. + + `-E' + Stop after the preprocessing stage; do not run the compiler + proper. The output is in the form of preprocessed source code, + which is sent to the standard output. + + Input files which don't require preprocessing are ignored. + + `-o FILE' + Place output in file FILE. This applies regardless to whatever + sort of output is being produced, whether it be an executable file, + an object file, an assembler file or preprocessed C code. + + Since only one output file can be specified, it does not make + sense to use `-o' when compiling more than one input file, unless + you are producing an executable file as output. + + If `-o' is not specified, the default is to put an executable file + in `a.out', the object file for `SOURCE.SUFFIX' in `SOURCE.o', its + assembler file in `SOURCE.s', and all preprocessed C source on + standard output. + + `-v' + Print (on standard error output) the commands executed to run the + stages of compilation. Also print the version number of the + compiler driver program and of the preprocessor and the compiler + proper. + + `-###' + Like `-v' except the commands are not executed and all command + arguments are quoted. This is useful for shell scripts to capture + the driver-generated command lines. + + `-pipe' + Use pipes rather than temporary files for communication between the + various stages of compilation. This fails to work on some systems + where the assembler is unable to read from a pipe; but the GNU + assembler has no trouble. + + `--help' + Print (on the standard output) a description of the command line + options understood by `gcc'. If the `-v' option is also specified + then `--help' will also be passed on to the various processes + invoked by `gcc', so that they can display the command line options + they accept. If the `-W' option is also specified then command + line options which have no documentation associated with them will + also be displayed. + + `--target-help' + Print (on the standard output) a description of target specific + command line options for each tool. + + `--version' + Display the version number and copyrights of the invoked GCC. + +  + File: gcc.info, Node: Invoking G++, Next: C Dialect Options, Prev: Overall Options, Up: Invoking GCC + + Compiling C++ Programs + ====================== + + C++ source files conventionally use one of the suffixes `.C', `.cc', + `.cpp', `.c++', `.cp', or `.cxx'; preprocessed C++ files use the suffix + `.ii'. GCC recognizes files with these names and compiles them as C++ + programs even if you call the compiler the same way as for compiling C + programs (usually with the name `gcc'). + + However, C++ programs often require class libraries as well as a + compiler that understands the C++ language--and under some + circumstances, you might want to compile programs from standard input, + or otherwise without a suffix that flags them as C++ programs. `g++' + is a program that calls GCC with the default language set to C++, and + automatically specifies linking against the C++ library. On many + systems, `g++' is also installed with the name `c++'. + + When you compile C++ programs, you may specify many of the same + command-line options that you use for compiling programs in any + language; or command-line options meaningful for C and related + languages; or options that are meaningful only for C++ programs. *Note + Options Controlling C Dialect: C Dialect Options, for explanations of + options for languages related to C. *Note Options Controlling C++ + Dialect: C++ Dialect Options, for explanations of options that are + meaningful only for C++ programs. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-10 gcc-3.2.3/gcc/doc/gcc.info-10 *** gcc-3.2.2/gcc/doc/gcc.info-10 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-10 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,1177 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Code Gen Options, Next: Environment Variables, Prev: Submodel Options, Up: Invoking GCC + + Options for Code Generation Conventions + ======================================= + + These machine-independent options control the interface conventions + used in code generation. + + Most of them have both positive and negative forms; the negative form + of `-ffoo' would be `-fno-foo'. In the table below, only one of the + forms is listed--the one which is not the default. You can figure out + the other form by either removing `no-' or adding it. + + `-fexceptions' + Enable exception handling. Generates extra code needed to + propagate exceptions. For some targets, this implies GCC will + generate frame unwind information for all functions, which can + produce significant data size overhead, although it does not + affect execution. If you do not specify this option, GCC will + enable it by default for languages like C++ which normally require + exception handling, and disable it for languages like C that do + not normally require it. However, you may need to enable this + option when compiling C code that needs to interoperate properly + with exception handlers written in C++. You may also wish to + disable this option if you are compiling older C++ programs that + don't use exception handling. + + `-fnon-call-exceptions' + Generate code that allows trapping instructions to throw + exceptions. Note that this requires platform-specific runtime + support that does not exist everywhere. Moreover, it only allows + _trapping_ instructions to throw exceptions, i.e. memory + references or floating point instructions. It does not allow + exceptions to be thrown from arbitrary signal handlers such as + `SIGALRM'. + + `-funwind-tables' + Similar to `-fexceptions', except that it will just generate any + needed static data, but will not affect the generated code in any + other way. You will normally not enable this option; instead, a + language processor that needs this handling would enable it on + your behalf. + + `-fasynchronous-unwind-tables' + Generate unwind table in dwarf2 format, if supported by target + machine. The table is exact at each instruction boundary, so it + can be used for stack unwinding from asynchronous events (such as + debugger or garbage collector). + + `-fpcc-struct-return' + Return "short" `struct' and `union' values in memory like longer + ones, rather than in registers. This convention is less + efficient, but it has the advantage of allowing intercallability + between GCC-compiled files and files compiled with other + compilers, particularly the Portable C Compiler (pcc). + + The precise convention for returning structures in memory depends + on the target configuration macros. + + Short structures and unions are those whose size and alignment + match that of some integer type. + + *Warning:* code compiled with the `-fpcc-struct-return' switch is + not binary compatible with code compiled with the + `-freg-struct-return' switch. Use it to conform to a non-default + application binary interface. + + `-freg-struct-return' + Return `struct' and `union' values in registers when possible. + This is more efficient for small structures than + `-fpcc-struct-return'. + + If you specify neither `-fpcc-struct-return' nor + `-freg-struct-return', GCC defaults to whichever convention is + standard for the target. If there is no standard convention, GCC + defaults to `-fpcc-struct-return', except on targets where GCC is + the principal compiler. In those cases, we can choose the + standard, and we chose the more efficient register return + alternative. + + *Warning:* code compiled with the `-freg-struct-return' switch is + not binary compatible with code compiled with the + `-fpcc-struct-return' switch. Use it to conform to a non-default + application binary interface. + + `-fshort-enums' + Allocate to an `enum' type only as many bytes as it needs for the + declared range of possible values. Specifically, the `enum' type + will be equivalent to the smallest integer type which has enough + room. + + *Warning:* the `-fshort-enums' switch causes GCC to generate code + that is not binary compatible with code generated without that + switch. Use it to conform to a non-default application binary + interface. + + `-fshort-double' + Use the same size for `double' as for `float'. + + *Warning:* the `-fshort-double' switch causes GCC to generate code + that is not binary compatible with code generated without that + switch. Use it to conform to a non-default application binary + interface. + + `-fshort-wchar' + Override the underlying type for `wchar_t' to be `short unsigned + int' instead of the default for the target. This option is useful + for building programs to run under WINE. + + *Warning:* the `-fshort-wchar' switch causes GCC to generate code + that is not binary compatible with code generated without that + switch. Use it to conform to a non-default application binary + interface. + + `-fshared-data' + Requests that the data and non-`const' variables of this + compilation be shared data rather than private data. The + distinction makes sense only on certain operating systems, where + shared data is shared between processes running the same program, + while private data exists in one copy per process. + + `-fno-common' + In C, allocate even uninitialized global variables in the data + section of the object file, rather than generating them as common + blocks. This has the effect that if the same variable is declared + (without `extern') in two different compilations, you will get an + error when you link them. The only reason this might be useful is + if you wish to verify that the program will work on other systems + which always work this way. + + `-fno-ident' + Ignore the `#ident' directive. + + `-fno-gnu-linker' + Do not output global initializations (such as C++ constructors and + destructors) in the form used by the GNU linker (on systems where + the GNU linker is the standard method of handling them). Use this + option when you want to use a non-GNU linker, which also requires + using the `collect2' program to make sure the system linker + includes constructors and destructors. (`collect2' is included in + the GCC distribution.) For systems which _must_ use `collect2', + the compiler driver `gcc' is configured to do this automatically. + + `-finhibit-size-directive' + Don't output a `.size' assembler directive, or anything else that + would cause trouble if the function is split in the middle, and the + two halves are placed at locations far apart in memory. This + option is used when compiling `crtstuff.c'; you should not need to + use it for anything else. + + `-fverbose-asm' + Put extra commentary information in the generated assembly code to + make it more readable. This option is generally only of use to + those who actually need to read the generated assembly code + (perhaps while debugging the compiler itself). + + `-fno-verbose-asm', the default, causes the extra information to + be omitted and is useful when comparing two assembler files. + + `-fvolatile' + Consider all memory references through pointers to be volatile. + + `-fvolatile-global' + Consider all memory references to extern and global data items to + be volatile. GCC does not consider static data items to be + volatile because of this switch. + + `-fvolatile-static' + Consider all memory references to static data to be volatile. + + `-fpic' + Generate position-independent code (PIC) suitable for use in a + shared library, if supported for the target machine. Such code + accesses all constant addresses through a global offset table + (GOT). The dynamic loader resolves the GOT entries when the + program starts (the dynamic loader is not part of GCC; it is part + of the operating system). If the GOT size for the linked + executable exceeds a machine-specific maximum size, you get an + error message from the linker indicating that `-fpic' does not + work; in that case, recompile with `-fPIC' instead. (These + maximums are 16k on the m88k, 8k on the Sparc, and 32k on the m68k + and RS/6000. The 386 has no such limit.) + + Position-independent code requires special support, and therefore + works only on certain machines. For the 386, GCC supports PIC for + System V but not for the Sun 386i. Code generated for the IBM + RS/6000 is always position-independent. + + `-fPIC' + If supported for the target machine, emit position-independent + code, suitable for dynamic linking and avoiding any limit on the + size of the global offset table. This option makes a difference + on the m68k, m88k, and the Sparc. + + Position-independent code requires special support, and therefore + works only on certain machines. + + `-ffixed-REG' + Treat the register named REG as a fixed register; generated code + should never refer to it (except perhaps as a stack pointer, frame + pointer or in some other fixed role). + + REG must be the name of a register. The register names accepted + are machine-specific and are defined in the `REGISTER_NAMES' macro + in the machine description macro file. + + This flag does not have a negative form, because it specifies a + three-way choice. + + `-fcall-used-REG' + Treat the register named REG as an allocable register that is + clobbered by function calls. It may be allocated for temporaries + or variables that do not live across a call. Functions compiled + this way will not save and restore the register REG. + + It is an error to used this flag with the frame pointer or stack + pointer. Use of this flag for other registers that have fixed + pervasive roles in the machine's execution model will produce + disastrous results. + + This flag does not have a negative form, because it specifies a + three-way choice. + + `-fcall-saved-REG' + Treat the register named REG as an allocable register saved by + functions. It may be allocated even for temporaries or variables + that live across a call. Functions compiled this way will save + and restore the register REG if they use it. + + It is an error to used this flag with the frame pointer or stack + pointer. Use of this flag for other registers that have fixed + pervasive roles in the machine's execution model will produce + disastrous results. + + A different sort of disaster will result from the use of this flag + for a register in which function values may be returned. + + This flag does not have a negative form, because it specifies a + three-way choice. + + `-fpack-struct' + Pack all structure members together without holes. + + *Warning:* the `-fpack-struct' switch causes GCC to generate code + that is not binary compatible with code generated without that + switch. Additionally, it makes the code suboptimial. Use it to + conform to a non-default application binary interface. + + `-finstrument-functions' + Generate instrumentation calls for entry and exit to functions. + Just after function entry and just before function exit, the + following profiling functions will be called with the address of + the current function and its call site. (On some platforms, + `__builtin_return_address' does not work beyond the current + function, so the call site information may not be available to the + profiling functions otherwise.) + + void __cyg_profile_func_enter (void *this_fn, + void *call_site); + void __cyg_profile_func_exit (void *this_fn, + void *call_site); + + The first argument is the address of the start of the current + function, which may be looked up exactly in the symbol table. + + This instrumentation is also done for functions expanded inline in + other functions. The profiling calls will indicate where, + conceptually, the inline function is entered and exited. This + means that addressable versions of such functions must be + available. If all your uses of a function are expanded inline, + this may mean an additional expansion of code size. If you use + `extern inline' in your C code, an addressable version of such + functions must be provided. (This is normally the case anyways, + but if you get lucky and the optimizer always expands the + functions inline, you might have gotten away without providing + static copies.) + + A function may be given the attribute `no_instrument_function', in + which case this instrumentation will not be done. This can be + used, for example, for the profiling functions listed above, + high-priority interrupt routines, and any functions from which the + profiling functions cannot safely be called (perhaps signal + handlers, if the profiling routines generate output or allocate + memory). + + `-fstack-check' + Generate code to verify that you do not go beyond the boundary of + the stack. You should specify this flag if you are running in an + environment with multiple threads, but only rarely need to specify + it in a single-threaded environment since stack overflow is + automatically detected on nearly all systems if there is only one + stack. + + Note that this switch does not actually cause checking to be done; + the operating system must do that. The switch causes generation + of code to ensure that the operating system sees the stack being + extended. + + `-fstack-limit-register=REG' + `-fstack-limit-symbol=SYM' + `-fno-stack-limit' + Generate code to ensure that the stack does not grow beyond a + certain value, either the value of a register or the address of a + symbol. If the stack would grow beyond the value, a signal is + raised. For most targets, the signal is raised before the stack + overruns the boundary, so it is possible to catch the signal + without taking special precautions. + + For instance, if the stack starts at absolute address `0x80000000' + and grows downwards, you can use the flags + `-fstack-limit-symbol=__stack_limit' and + `-Wl,--defsym,__stack_limit=0x7ffe0000' to enforce a stack limit + of 128KB. Note that this may only work with the GNU linker. + + `-fargument-alias' + `-fargument-noalias' + `-fargument-noalias-global' + Specify the possible relationships among parameters and between + parameters and global data. + + `-fargument-alias' specifies that arguments (parameters) may alias + each other and may alias global storage. + `-fargument-noalias' specifies that arguments do not alias each + other, but may alias global storage. + `-fargument-noalias-global' specifies that arguments do not alias + each other and do not alias global storage. + + Each language will automatically use whatever option is required by + the language standard. You should not need to use these options + yourself. + + `-fleading-underscore' + This option and its counterpart, `-fno-leading-underscore', + forcibly change the way C symbols are represented in the object + file. One use is to help link with legacy assembly code. + + *Warning:* the `-fleading-underscore' switch causes GCC to + generate code that is not binary compatible with code generated + without that switch. Use it to conform to a non-default + application binary interface. Not all targets provide complete + support for this switch. + +  + File: gcc.info, Node: Environment Variables, Next: Running Protoize, Prev: Code Gen Options, Up: Invoking GCC + + Environment Variables Affecting GCC + =================================== + + This section describes several environment variables that affect how + GCC operates. Some of them work by specifying directories or prefixes + to use when searching for various kinds of files. Some are used to + specify other aspects of the compilation environment. + + Note that you can also specify places to search using options such as + `-B', `-I' and `-L' (*note Directory Options::). These take precedence + over places specified using environment variables, which in turn take + precedence over those specified by the configuration of GCC. *Note + Controlling the Compilation Driver `gcc': (gccint)Driver. + + `LANG' + `LC_CTYPE' + `LC_MESSAGES' + `LC_ALL' + These environment variables control the way that GCC uses + localization information that allow GCC to work with different + national conventions. GCC inspects the locale categories + `LC_CTYPE' and `LC_MESSAGES' if it has been configured to do so. + These locale categories can be set to any value supported by your + installation. A typical value is `en_UK' for English in the United + Kingdom. + + The `LC_CTYPE' environment variable specifies character + classification. GCC uses it to determine the character boundaries + in a string; this is needed for some multibyte encodings that + contain quote and escape characters that would otherwise be + interpreted as a string end or escape. + + The `LC_MESSAGES' environment variable specifies the language to + use in diagnostic messages. + + If the `LC_ALL' environment variable is set, it overrides the value + of `LC_CTYPE' and `LC_MESSAGES'; otherwise, `LC_CTYPE' and + `LC_MESSAGES' default to the value of the `LANG' environment + variable. If none of these variables are set, GCC defaults to + traditional C English behavior. + + `TMPDIR' + If `TMPDIR' is set, it specifies the directory to use for temporary + files. GCC uses temporary files to hold the output of one stage of + compilation which is to be used as input to the next stage: for + example, the output of the preprocessor, which is the input to the + compiler proper. + + `GCC_EXEC_PREFIX' + If `GCC_EXEC_PREFIX' is set, it specifies a prefix to use in the + names of the subprograms executed by the compiler. No slash is + added when this prefix is combined with the name of a subprogram, + but you can specify a prefix that ends with a slash if you wish. + + If `GCC_EXEC_PREFIX' is not set, GCC will attempt to figure out an + appropriate prefix to use based on the pathname it was invoked + with. + + If GCC cannot find the subprogram using the specified prefix, it + tries looking in the usual places for the subprogram. + + The default value of `GCC_EXEC_PREFIX' is `PREFIX/lib/gcc-lib/' + where PREFIX is the value of `prefix' when you ran the `configure' + script. + + Other prefixes specified with `-B' take precedence over this + prefix. + + This prefix is also used for finding files such as `crt0.o' that + are used for linking. + + In addition, the prefix is used in an unusual way in finding the + directories to search for header files. For each of the standard + directories whose name normally begins with + `/usr/local/lib/gcc-lib' (more precisely, with the value of + `GCC_INCLUDE_DIR'), GCC tries replacing that beginning with the + specified prefix to produce an alternate directory name. Thus, + with `-Bfoo/', GCC will search `foo/bar' where it would normally + search `/usr/local/lib/bar'. These alternate directories are + searched first; the standard directories come next. + + `COMPILER_PATH' + The value of `COMPILER_PATH' is a colon-separated list of + directories, much like `PATH'. GCC tries the directories thus + specified when searching for subprograms, if it can't find the + subprograms using `GCC_EXEC_PREFIX'. + + `LIBRARY_PATH' + The value of `LIBRARY_PATH' is a colon-separated list of + directories, much like `PATH'. When configured as a native + compiler, GCC tries the directories thus specified when searching + for special linker files, if it can't find them using + `GCC_EXEC_PREFIX'. Linking using GCC also uses these directories + when searching for ordinary libraries for the `-l' option (but + directories specified with `-L' come first). + + `LANG' + This variable is used to pass locale information to the compiler. + One way in which this information is used is to determine the + character set to be used when character literals, string literals + and comments are parsed in C and C++. When the compiler is + configured to allow multibyte characters, the following values for + `LANG' are recognized: + + `C-JIS' + Recognize JIS characters. + + `C-SJIS' + Recognize SJIS characters. + + `C-EUCJP' + Recognize EUCJP characters. + + If `LANG' is not defined, or if it has some other value, then the + compiler will use mblen and mbtowc as defined by the default + locale to recognize and translate multibyte characters. + + Some additional environments variables affect the behavior of the + preprocessor. + + `CPATH' + `C_INCLUDE_PATH' + `CPLUS_INCLUDE_PATH' + `OBJC_INCLUDE_PATH' + Each variable's value is a list of directories separated by a + special character, much like `PATH', in which to look for header + files. The special character, `PATH_SEPARATOR', is + target-dependent and determined at GCC build time. For + Windows-based targets it is a semicolon, and for almost all other + targets it is a colon. + + `CPATH' specifies a list of directories to be searched as if + specified with `-I', but after any paths given with `-I' options + on the command line. The environment variable is used regardless + of which language is being preprocessed. + + The remaining environment variables apply only when preprocessing + the particular language indicated. Each specifies a list of + directories to be searched as if specified with `-isystem', but + after any paths given with `-isystem' options on the command line. + + `DEPENDENCIES_OUTPUT' + If this variable is set, its value specifies how to output + dependencies for Make based on the non-system header files + processed by the compiler. System header files are ignored in the + dependency output. + + The value of `DEPENDENCIES_OUTPUT' can be just a file name, in + which case the Make rules are written to that file, guessing the + target name from the source file name. Or the value can have the + form `FILE TARGET', in which case the rules are written to file + FILE using TARGET as the target name. + + In other words, this environment variable is equivalent to + combining the options `-MM' and `-MF' (*note Preprocessor + Options::), with an optional `-MT' switch too. + + `SUNPRO_DEPENDENCIES' + This variable is the same as the environment variable + `DEPENDENCIES_OUTPUT' (*note DEPENDENCIES_OUTPUT::), except that + system header files are not ignored, so it implies `-M' rather + than `-MM'. However, the dependence on the main input file is + omitted. *Note Preprocessor Options::. + +  + File: gcc.info, Node: Running Protoize, Prev: Environment Variables, Up: Invoking GCC + + Running Protoize + ================ + + The program `protoize' is an optional part of GCC. You can use it + to add prototypes to a program, thus converting the program to ISO C in + one respect. The companion program `unprotoize' does the reverse: it + removes argument types from any prototypes that are found. + + When you run these programs, you must specify a set of source files + as command line arguments. The conversion programs start out by + compiling these files to see what functions they define. The + information gathered about a file FOO is saved in a file named `FOO.X'. + + After scanning comes actual conversion. The specified files are all + eligible to be converted; any files they include (whether sources or + just headers) are eligible as well. + + But not all the eligible files are converted. By default, + `protoize' and `unprotoize' convert only source and header files in the + current directory. You can specify additional directories whose files + should be converted with the `-d DIRECTORY' option. You can also + specify particular files to exclude with the `-x FILE' option. A file + is converted if it is eligible, its directory name matches one of the + specified directory names, and its name within the directory has not + been excluded. + + Basic conversion with `protoize' consists of rewriting most function + definitions and function declarations to specify the types of the + arguments. The only ones not rewritten are those for varargs functions. + + `protoize' optionally inserts prototype declarations at the + beginning of the source file, to make them available for any calls that + precede the function's definition. Or it can insert prototype + declarations with block scope in the blocks where undeclared functions + are called. + + Basic conversion with `unprotoize' consists of rewriting most + function declarations to remove any argument types, and rewriting + function definitions to the old-style pre-ISO form. + + Both conversion programs print a warning for any function + declaration or definition that they can't convert. You can suppress + these warnings with `-q'. + + The output from `protoize' or `unprotoize' replaces the original + source file. The original file is renamed to a name ending with + `.save' (for DOS, the saved filename ends in `.sav' without the + original `.c' suffix). If the `.save' (`.sav' for DOS) file already + exists, then the source file is simply discarded. + + `protoize' and `unprotoize' both depend on GCC itself to scan the + program and collect information about the functions it uses. So + neither of these programs will work until GCC is installed. + + Here is a table of the options you can use with `protoize' and + `unprotoize'. Each option works with both programs unless otherwise + stated. + + `-B DIRECTORY' + Look for the file `SYSCALLS.c.X' in DIRECTORY, instead of the + usual directory (normally `/usr/local/lib'). This file contains + prototype information about standard system functions. This option + applies only to `protoize'. + + `-c COMPILATION-OPTIONS' + Use COMPILATION-OPTIONS as the options when running `gcc' to + produce the `.X' files. The special option `-aux-info' is always + passed in addition, to tell `gcc' to write a `.X' file. + + Note that the compilation options must be given as a single + argument to `protoize' or `unprotoize'. If you want to specify + several `gcc' options, you must quote the entire set of + compilation options to make them a single word in the shell. + + There are certain `gcc' arguments that you cannot use, because they + would produce the wrong kind of output. These include `-g', `-O', + `-c', `-S', and `-o' If you include these in the + COMPILATION-OPTIONS, they are ignored. + + `-C' + Rename files to end in `.C' (`.cc' for DOS-based file systems) + instead of `.c'. This is convenient if you are converting a C + program to C++. This option applies only to `protoize'. + + `-g' + Add explicit global declarations. This means inserting explicit + declarations at the beginning of each source file for each function + that is called in the file and was not declared. These + declarations precede the first function definition that contains a + call to an undeclared function. This option applies only to + `protoize'. + + `-i STRING' + Indent old-style parameter declarations with the string STRING. + This option applies only to `protoize'. + + `unprotoize' converts prototyped function definitions to old-style + function definitions, where the arguments are declared between the + argument list and the initial `{'. By default, `unprotoize' uses + five spaces as the indentation. If you want to indent with just + one space instead, use `-i " "'. + + `-k' + Keep the `.X' files. Normally, they are deleted after conversion + is finished. + + `-l' + Add explicit local declarations. `protoize' with `-l' inserts a + prototype declaration for each function in each block which calls + the function without any declaration. This option applies only to + `protoize'. + + `-n' + Make no real changes. This mode just prints information about the + conversions that would have been done without `-n'. + + `-N' + Make no `.save' files. The original files are simply deleted. + Use this option with caution. + + `-p PROGRAM' + Use the program PROGRAM as the compiler. Normally, the name `gcc' + is used. + + `-q' + Work quietly. Most warnings are suppressed. + + `-v' + Print the version number, just like `-v' for `gcc'. + + If you need special compiler options to compile one of your program's + source files, then you should generate that file's `.X' file specially, + by running `gcc' on that source file with the appropriate options and + the option `-aux-info'. Then run `protoize' on the entire set of + files. `protoize' will use the existing `.X' file because it is newer + than the source file. For example: + + gcc -Dfoo=bar file1.c -aux-info file1.X + protoize *.c + + You need to include the special files along with the rest in the + `protoize' command, even though their `.X' files already exist, because + otherwise they won't get converted. + + *Note Protoize Caveats::, for more information on how to use + `protoize' successfully. + +  + File: gcc.info, Node: C Implementation, Next: C Extensions, Prev: Invoking GCC, Up: Top + + C Implementation-defined behavior + ********************************* + + A conforming implementation of ISO C is required to document its + choice of behavior in each of the areas that are designated + "implementation defined." The following lists all such areas, along + with the section number from the ISO/IEC 9899:1999 standard. + + * Menu: + + * Translation implementation:: + * Environment implementation:: + * Identifiers implementation:: + * Characters implementation:: + * Integers implementation:: + * Floating point implementation:: + * Arrays and pointers implementation:: + * Hints implementation:: + * Structures unions enumerations and bit-fields implementation:: + * Qualifiers implementation:: + * Preprocessing directives implementation:: + * Library functions implementation:: + * Architecture implementation:: + * Locale-specific behavior implementation:: + +  + File: gcc.info, Node: Translation implementation, Next: Environment implementation, Up: C Implementation + + Translation + =========== + + * `How a diagnostic is identified (3.10, 5.1.1.3).' + + * `Whether each nonempty sequence of white-space characters other + than new-line is retained or replaced by one space character in + translation phase 3 (5.1.1.2).' + +  + File: gcc.info, Node: Environment implementation, Next: Identifiers implementation, Prev: Translation implementation, Up: C Implementation + + Environment + =========== + + The behavior of these points are dependent on the implementation of + the C library, and are not defined by GCC itself. + +  + File: gcc.info, Node: Identifiers implementation, Next: Characters implementation, Prev: Environment implementation, Up: C Implementation + + Identifiers + =========== + + * `Which additional multibyte characters may appear in identifiers + and their correspondence to universal character names (6.4.2).' + + * `The number of significant initial characters in an identifier + (5.2.4.1, 6.4.2).' + +  + File: gcc.info, Node: Characters implementation, Next: Integers implementation, Prev: Identifiers implementation, Up: C Implementation + + Characters + ========== + + * `The number of bits in a byte (3.6).' + + * `The values of the members of the execution character set (5.2.1).' + + * `The unique value of the member of the execution character set + produced for each of the standard alphabetic escape sequences + (5.2.2).' + + * `The value of a `char' object into which has been stored any + character other than a member of the basic execution character set + (6.2.5).' + + * `Which of `signed char' or `unsigned char' has the same range, + representation, and behavior as "plain" `char' (6.2.5, 6.3.1.1).' + + * `The mapping of members of the source character set (in character + constants and string literals) to members of the execution + character set (6.4.4.4, 5.1.1.2).' + + * `The value of an integer character constant containing more than + one character or containing a character or escape sequence that + does not map to a single-byte execution character (6.4.4.4).' + + * `The value of a wide character constant containing more than one + multibyte character, or containing a multibyte character or escape + sequence not represented in the extended execution character set + (6.4.4.4).' + + * `The current locale used to convert a wide character constant + consisting of a single multibyte character that maps to a member + of the extended execution character set into a corresponding wide + character code (6.4.4.4).' + + * `The current locale used to convert a wide string literal into + corresponding wide character codes (6.4.5).' + + * `The value of a string literal containing a multibyte character or + escape sequence not represented in the execution character set + (6.4.5).' + +  + File: gcc.info, Node: Integers implementation, Next: Floating point implementation, Prev: Characters implementation, Up: C Implementation + + Integers + ======== + + * `Any extended integer types that exist in the implementation + (6.2.5).' + + * `Whether signed integer types are represented using sign and + magnitude, two's complement, or one's complement, and whether the + extraordinary value is a trap representation or an ordinary value + (6.2.6.2).' + + * `The rank of any extended integer type relative to another extended + integer type with the same precision (6.3.1.1).' + + * `The result of, or the signal raised by, converting an integer to a + signed integer type when the value cannot be represented in an + object of that type (6.3.1.3).' + + * `The results of some bitwise operations on signed integers (6.5).' + +  + File: gcc.info, Node: Floating point implementation, Next: Arrays and pointers implementation, Prev: Integers implementation, Up: C Implementation + + Floating point + ============== + + * `The accuracy of the floating-point operations and of the library + functions in `' and `' that return + floating-point results (5.2.4.2.2).' + + * `The rounding behaviors characterized by non-standard values of + `FLT_ROUNDS' (5.2.4.2.2).' + + * `The evaluation methods characterized by non-standard negative + values of `FLT_EVAL_METHOD' (5.2.4.2.2).' + + * `The direction of rounding when an integer is converted to a + floating-point number that cannot exactly represent the original + value (6.3.1.4).' + + * `The direction of rounding when a floating-point number is + converted to a narrower floating-point number (6.3.1.5).' + + * `How the nearest representable value or the larger or smaller + representable value immediately adjacent to the nearest + representable value is chosen for certain floating constants + (6.4.4.2).' + + * `Whether and how floating expressions are contracted when not + disallowed by the `FP_CONTRACT' pragma (6.5).' + + * `The default state for the `FENV_ACCESS' pragma (7.6.1).' + + * `Additional floating-point exceptions, rounding modes, + environments, and classifications, and their macro names (7.6, + 7.12).' + + * `The default state for the `FP_CONTRACT' pragma (7.12.2).' + + * `Whether the "inexact" floating-point exception can be raised when + the rounded result actually does equal the mathematical result in + an IEC 60559 conformant implementation (F.9).' + + * `Whether the "underflow" (and "inexact") floating-point exception + can be raised when a result is tiny but not inexact in an IEC + 60559 conformant implementation (F.9).' + + +  + File: gcc.info, Node: Arrays and pointers implementation, Next: Hints implementation, Prev: Floating point implementation, Up: C Implementation + + Arrays and pointers + =================== + + * `The result of converting a pointer to an integer or vice versa + (6.3.2.3).' + + A cast from pointer to integer discards most-significant bits if + the pointer representation is larger than the integer type, + sign-extends(1) if the pointer representation is smaller than the + integer type, otherwise the bits are unchanged. + + A cast from integer to pointer discards most-significant bits if + the pointer representation is smaller than the integer type, + extends according to the signedness of the integer type if the + pointer representation is larger than the integer type, otherwise + the bits are unchanged. + + When casting from pointer to integer and back again, the resulting + pointer must reference the same object as the original pointer, + otherwise the behavior is undefined. That is, one may not use + integer arithmetic to avoid the undefined behavior of pointer + arithmetic as proscribed in 6.5.6/8. + + * `The size of the result of subtracting two pointers to elements of + the same array (6.5.6).' + + + ---------- Footnotes ---------- + + (1) Future versions of GCC may zero-extend, or use a target-defined + `ptr_extend' pattern. Do not rely on sign extension. + +  + File: gcc.info, Node: Hints implementation, Next: Structures unions enumerations and bit-fields implementation, Prev: Arrays and pointers implementation, Up: C Implementation + + Hints + ===== + + * `The extent to which suggestions made by using the `register' + storage-class specifier are effective (6.7.1).' + + * `The extent to which suggestions made by using the inline function + specifier are effective (6.7.4).' + + +  + File: gcc.info, Node: Structures unions enumerations and bit-fields implementation, Next: Qualifiers implementation, Prev: Hints implementation, Up: C Implementation + + Structures, unions, enumerations, and bit-fields + ================================================ + + * `Whether a "plain" int bit-field is treated as a `signed int' + bit-field or as an `unsigned int' bit-field (6.7.2, 6.7.2.1).' + + * `Allowable bit-field types other than `_Bool', `signed int', and + `unsigned int' (6.7.2.1).' + + * `Whether a bit-field can straddle a storage-unit boundary + (6.7.2.1).' + + * `The order of allocation of bit-fields within a unit (6.7.2.1).' + + * `The alignment of non-bit-field members of structures (6.7.2.1).' + + * `The integer type compatible with each enumerated type (6.7.2.2).' + + +  + File: gcc.info, Node: Qualifiers implementation, Next: Preprocessing directives implementation, Prev: Structures unions enumerations and bit-fields implementation, Up: C Implementation + + Qualifiers + ========== + + * `What constitutes an access to an object that has + volatile-qualified type (6.7.3).' + + +  + File: gcc.info, Node: Preprocessing directives implementation, Next: Library functions implementation, Prev: Qualifiers implementation, Up: C Implementation + + Preprocessing directives + ======================== + + * `How sequences in both forms of header names are mapped to headers + or external source file names (6.4.7).' + + * `Whether the value of a character constant in a constant expression + that controls conditional inclusion matches the value of the same + character constant in the execution character set (6.10.1).' + + * `Whether the value of a single-character character constant in a + constant expression that controls conditional inclusion may have a + negative value (6.10.1).' + + * `The places that are searched for an included `<>' delimited + header, and how the places are specified or the header is + identified (6.10.2).' + + * `How the named source file is searched for in an included `""' + delimited header (6.10.2).' + + * `The method by which preprocessing tokens (possibly resulting from + macro expansion) in a `#include' directive are combined into a + header name (6.10.2).' + + * `The nesting limit for `#include' processing (6.10.2).' + + * `Whether the `#' operator inserts a `\' character before the `\' + character that begins a universal character name in a character + constant or string literal (6.10.3.2).' + + * `The behavior on each recognized non-`STDC #pragma' directive + (6.10.6).' + + * `The definitions for `__DATE__' and `__TIME__' when respectively, + the date and time of translation are not available (6.10.8).' + + +  + File: gcc.info, Node: Library functions implementation, Next: Architecture implementation, Prev: Preprocessing directives implementation, Up: C Implementation + + Library functions + ================= + + The behavior of these points are dependent on the implementation of + the C library, and are not defined by GCC itself. + +  + File: gcc.info, Node: Architecture implementation, Next: Locale-specific behavior implementation, Prev: Library functions implementation, Up: C Implementation + + Architecture + ============ + + * `The values or expressions assigned to the macros specified in the + headers `', `', and `' (5.2.4.2, + 7.18.2, 7.18.3).' + + * `The number, order, and encoding of bytes in any object (when not + explicitly specified in this International Standard) (6.2.6.1).' + + * `The value of the result of the sizeof operator (6.5.3.4).' + + +  + File: gcc.info, Node: Locale-specific behavior implementation, Prev: Architecture implementation, Up: C Implementation + + Locale-specific behavior + ======================== + + The behavior of these points are dependent on the implementation of + the C library, and are not defined by GCC itself. + +  + File: gcc.info, Node: C Extensions, Next: C++ Extensions, Prev: C Implementation, Up: Top + + Extensions to the C Language Family + *********************************** + + GNU C provides several language features not found in ISO standard C. + (The `-pedantic' option directs GCC to print a warning message if any + of these features is used.) To test for the availability of these + features in conditional compilation, check for a predefined macro + `__GNUC__', which is always defined under GCC. + + These extensions are available in C and Objective-C. Most of them + are also available in C++. *Note Extensions to the C++ Language: C++ + Extensions, for extensions that apply _only_ to C++. + + Some features that are in ISO C99 but not C89 or C++ are also, as + extensions, accepted by GCC in C89 mode and in C++. + + * Menu: + + * Statement Exprs:: Putting statements and declarations inside expressions. + * Local Labels:: Labels local to a statement-expression. + * Labels as Values:: Getting pointers to labels, and computed gotos. + * Nested Functions:: As in Algol and Pascal, lexical scoping of functions. + * Constructing Calls:: Dispatching a call to another function. + * Typeof:: `typeof': referring to the type of an expression. + * Lvalues:: Using `?:', `,' and casts in lvalues. + * Conditionals:: Omitting the middle operand of a `?:' expression. + * Long Long:: Double-word integers---`long long int'. + * Complex:: Data types for complex numbers. + * Hex Floats:: Hexadecimal floating-point constants. + * Zero Length:: Zero-length arrays. + * Variable Length:: Arrays whose length is computed at run time. + * Variadic Macros:: Macros with a variable number of arguments. + * Escaped Newlines:: Slightly looser rules for escaped newlines. + * Multi-line Strings:: String literals with embedded newlines. + * Subscripting:: Any array can be subscripted, even if not an lvalue. + * Pointer Arith:: Arithmetic on `void'-pointers and function pointers. + * Initializers:: Non-constant initializers. + * Compound Literals:: Compound literals give structures, unions + or arrays as values. + * Designated Inits:: Labeling elements of initializers. + * Cast to Union:: Casting to union type from any member of the union. + * Case Ranges:: `case 1 ... 9' and such. + * Mixed Declarations:: Mixing declarations and code. + * Function Attributes:: Declaring that functions have no side effects, + or that they can never return. + * Attribute Syntax:: Formal syntax for attributes. + * Function Prototypes:: Prototype declarations and old-style definitions. + * C++ Comments:: C++ comments are recognized. + * Dollar Signs:: Dollar sign is allowed in identifiers. + * Character Escapes:: `\e' stands for the character . + * Variable Attributes:: Specifying attributes of variables. + * Type Attributes:: Specifying attributes of types. + * Alignment:: Inquiring about the alignment of a type or variable. + * Inline:: Defining inline functions (as fast as macros). + * Extended Asm:: Assembler instructions with C expressions as operands. + (With them you can define ``built-in'' functions.) + * Constraints:: Constraints for asm operands + * Asm Labels:: Specifying the assembler name to use for a C symbol. + * Explicit Reg Vars:: Defining variables residing in specified registers. + * Alternate Keywords:: `__const__', `__asm__', etc., for header files. + * Incomplete Enums:: `enum foo;', with details to follow. + * Function Names:: Printable strings which are the name of the current + function. + * Return Address:: Getting the return or frame address of a function. + * Vector Extensions:: Using vector instructions through built-in functions. + * Other Builtins:: Other built-in functions. + * Target Builtins:: Built-in functions specific to particular targets. + * Pragmas:: Pragmas accepted by GCC. + * Unnamed Fields:: Unnamed struct/union fields within structs/unions. + +  + File: gcc.info, Node: Statement Exprs, Next: Local Labels, Up: C Extensions + + Statements and Declarations in Expressions + ========================================== + + A compound statement enclosed in parentheses may appear as an + expression in GNU C. This allows you to use loops, switches, and local + variables within an expression. + + Recall that a compound statement is a sequence of statements + surrounded by braces; in this construct, parentheses go around the + braces. For example: + + ({ int y = foo (); int z; + if (y > 0) z = y; + else z = - y; + z; }) + + is a valid (though slightly more complex than necessary) expression for + the absolute value of `foo ()'. + + The last thing in the compound statement should be an expression + followed by a semicolon; the value of this subexpression serves as the + value of the entire construct. (If you use some other kind of statement + last within the braces, the construct has type `void', and thus + effectively no value.) + + This feature is especially useful in making macro definitions "safe" + (so that they evaluate each operand exactly once). For example, the + "maximum" function is commonly defined as a macro in standard C as + follows: + + #define max(a,b) ((a) > (b) ? (a) : (b)) + + But this definition computes either A or B twice, with bad results if + the operand has side effects. In GNU C, if you know the type of the + operands (here let's assume `int'), you can define the macro safely as + follows: + + #define maxint(a,b) \ + ({int _a = (a), _b = (b); _a > _b ? _a : _b; }) + + Embedded statements are not allowed in constant expressions, such as + the value of an enumeration constant, the width of a bit-field, or the + initial value of a static variable. + + If you don't know the type of the operand, you can still do this, + but you must use `typeof' (*note Typeof::). + + Statement expressions are not supported fully in G++, and their fate + there is unclear. (It is possible that they will become fully supported + at some point, or that they will be deprecated, or that the bugs that + are present will continue to exist indefinitely.) Presently, statement + expressions do not work well as default arguments. + + In addition, there are semantic issues with statement-expressions in + C++. If you try to use statement-expressions instead of inline + functions in C++, you may be surprised at the way object destruction is + handled. For example: + + #define foo(a) ({int b = (a); b + 3; }) + + does not work the same way as: + + inline int foo(int a) { int b = a; return b + 3; } + + In particular, if the expression passed into `foo' involves the + creation of temporaries, the destructors for those temporaries will be + run earlier in the case of the macro than in the case of the function. + + These considerations mean that it is probably a bad idea to use + statement-expressions of this form in header files that are designed to + work with C++. (Note that some versions of the GNU C Library contained + header files using statement-expression that lead to precisely this + bug.) + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-11 gcc-3.2.3/gcc/doc/gcc.info-11 *** gcc-3.2.2/gcc/doc/gcc.info-11 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-11 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,1143 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Local Labels, Next: Labels as Values, Prev: Statement Exprs, Up: C Extensions + + Locally Declared Labels + ======================= + + Each statement expression is a scope in which "local labels" can be + declared. A local label is simply an identifier; you can jump to it + with an ordinary `goto' statement, but only from within the statement + expression it belongs to. + + A local label declaration looks like this: + + __label__ LABEL; + + or + + __label__ LABEL1, LABEL2, ...; + + Local label declarations must come at the beginning of the statement + expression, right after the `({', before any ordinary declarations. + + The label declaration defines the label _name_, but does not define + the label itself. You must do this in the usual way, with `LABEL:', + within the statements of the statement expression. + + The local label feature is useful because statement expressions are + often used in macros. If the macro contains nested loops, a `goto' can + be useful for breaking out of them. However, an ordinary label whose + scope is the whole function cannot be used: if the macro can be + expanded several times in one function, the label will be multiply + defined in that function. A local label avoids this problem. For + example: + + #define SEARCH(array, target) \ + ({ \ + __label__ found; \ + typeof (target) _SEARCH_target = (target); \ + typeof (*(array)) *_SEARCH_array = (array); \ + int i, j; \ + int value; \ + for (i = 0; i < max; i++) \ + for (j = 0; j < max; j++) \ + if (_SEARCH_array[i][j] == _SEARCH_target) \ + { value = i; goto found; } \ + value = -1; \ + found: \ + value; \ + }) + +  + File: gcc.info, Node: Labels as Values, Next: Nested Functions, Prev: Local Labels, Up: C Extensions + + Labels as Values + ================ + + You can get the address of a label defined in the current function + (or a containing function) with the unary operator `&&'. The value has + type `void *'. This value is a constant and can be used wherever a + constant of that type is valid. For example: + + void *ptr; + ... + ptr = &&foo; + + To use these values, you need to be able to jump to one. This is + done with the computed goto statement(1), `goto *EXP;'. For example, + + goto *ptr; + + Any expression of type `void *' is allowed. + + One way of using these constants is in initializing a static array + that will serve as a jump table: + + static void *array[] = { &&foo, &&bar, &&hack }; + + Then you can select a label with indexing, like this: + + goto *array[i]; + + Note that this does not check whether the subscript is in bounds--array + indexing in C never does that. + + Such an array of label values serves a purpose much like that of the + `switch' statement. The `switch' statement is cleaner, so use that + rather than an array unless the problem does not fit a `switch' + statement very well. + + Another use of label values is in an interpreter for threaded code. + The labels within the interpreter function can be stored in the + threaded code for super-fast dispatching. + + You may not use this mechanism to jump to code in a different + function. If you do that, totally unpredictable things will happen. + The best way to avoid this is to store the label address only in + automatic variables and never pass it as an argument. + + An alternate way to write the above example is + + static const int array[] = { &&foo - &&foo, &&bar - &&foo, + &&hack - &&foo }; + goto *(&&foo + array[i]); + + This is more friendly to code living in shared libraries, as it reduces + the number of dynamic relocations that are needed, and by consequence, + allows the data to be read-only. + + ---------- Footnotes ---------- + + (1) The analogous feature in Fortran is called an assigned goto, but + that name seems inappropriate in C, where one can do more than simply + store label addresses in label variables. + +  + File: gcc.info, Node: Nested Functions, Next: Constructing Calls, Prev: Labels as Values, Up: C Extensions + + Nested Functions + ================ + + A "nested function" is a function defined inside another function. + (Nested functions are not supported for GNU C++.) The nested function's + name is local to the block where it is defined. For example, here we + define a nested function named `square', and call it twice: + + foo (double a, double b) + { + double square (double z) { return z * z; } + + return square (a) + square (b); + } + + The nested function can access all the variables of the containing + function that are visible at the point of its definition. This is + called "lexical scoping". For example, here we show a nested function + which uses an inherited variable named `offset': + + bar (int *array, int offset, int size) + { + int access (int *array, int index) + { return array[index + offset]; } + int i; + ... + for (i = 0; i < size; i++) + ... access (array, i) ... + } + + Nested function definitions are permitted within functions in the + places where variable definitions are allowed; that is, in any block, + before the first statement in the block. + + It is possible to call the nested function from outside the scope of + its name by storing its address or passing the address to another + function: + + hack (int *array, int size) + { + void store (int index, int value) + { array[index] = value; } + + intermediate (store, size); + } + + Here, the function `intermediate' receives the address of `store' as + an argument. If `intermediate' calls `store', the arguments given to + `store' are used to store into `array'. But this technique works only + so long as the containing function (`hack', in this example) does not + exit. + + If you try to call the nested function through its address after the + containing function has exited, all hell will break loose. If you try + to call it after a containing scope level has exited, and if it refers + to some of the variables that are no longer in scope, you may be lucky, + but it's not wise to take the risk. If, however, the nested function + does not refer to anything that has gone out of scope, you should be + safe. + + GCC implements taking the address of a nested function using a + technique called "trampolines". A paper describing them is available as + + `http://people.debian.org/~aaronl/Usenix88-lexic.pdf'. + + A nested function can jump to a label inherited from a containing + function, provided the label was explicitly declared in the containing + function (*note Local Labels::). Such a jump returns instantly to the + containing function, exiting the nested function which did the `goto' + and any intermediate functions as well. Here is an example: + + bar (int *array, int offset, int size) + { + __label__ failure; + int access (int *array, int index) + { + if (index > size) + goto failure; + return array[index + offset]; + } + int i; + ... + for (i = 0; i < size; i++) + ... access (array, i) ... + ... + return 0; + + /* Control comes here from `access' + if it detects an error. */ + failure: + return -1; + } + + A nested function always has internal linkage. Declaring one with + `extern' is erroneous. If you need to declare the nested function + before its definition, use `auto' (which is otherwise meaningless for + function declarations). + + bar (int *array, int offset, int size) + { + __label__ failure; + auto int access (int *, int); + ... + int access (int *array, int index) + { + if (index > size) + goto failure; + return array[index + offset]; + } + ... + } + +  + File: gcc.info, Node: Constructing Calls, Next: Typeof, Prev: Nested Functions, Up: C Extensions + + Constructing Function Calls + =========================== + + Using the built-in functions described below, you can record the + arguments a function received, and call another function with the same + arguments, without knowing the number or types of the arguments. + + You can also record the return value of that function call, and + later return that value, without knowing what data type the function + tried to return (as long as your caller expects that data type). + + - Built-in Function: void * __builtin_apply_args () + This built-in function returns a pointer to data describing how to + perform a call with the same arguments as were passed to the + current function. + + The function saves the arg pointer register, structure value + address, and all registers that might be used to pass arguments to + a function into a block of memory allocated on the stack. Then it + returns the address of that block. + + - Built-in Function: void * __builtin_apply (void (*FUNCTION)(), void + *ARGUMENTS, size_t SIZE) + This built-in function invokes FUNCTION with a copy of the + parameters described by ARGUMENTS and SIZE. + + The value of ARGUMENTS should be the value returned by + `__builtin_apply_args'. The argument SIZE specifies the size of + the stack argument data, in bytes. + + This function returns a pointer to data describing how to return + whatever value was returned by FUNCTION. The data is saved in a + block of memory allocated on the stack. + + It is not always simple to compute the proper value for SIZE. The + value is used by `__builtin_apply' to compute the amount of data + that should be pushed on the stack and copied from the incoming + argument area. + + - Built-in Function: void __builtin_return (void *RESULT) + This built-in function returns the value described by RESULT from + the containing function. You should specify, for RESULT, a value + returned by `__builtin_apply'. + +  + File: gcc.info, Node: Typeof, Next: Lvalues, Prev: Constructing Calls, Up: C Extensions + + Referring to a Type with `typeof' + ================================= + + Another way to refer to the type of an expression is with `typeof'. + The syntax of using of this keyword looks like `sizeof', but the + construct acts semantically like a type name defined with `typedef'. + + There are two ways of writing the argument to `typeof': with an + expression or with a type. Here is an example with an expression: + + typeof (x[0](1)) + + This assumes that `x' is an array of pointers to functions; the type + described is that of the values of the functions. + + Here is an example with a typename as the argument: + + typeof (int *) + + Here the type described is that of pointers to `int'. + + If you are writing a header file that must work when included in ISO + C programs, write `__typeof__' instead of `typeof'. *Note Alternate + Keywords::. + + A `typeof'-construct can be used anywhere a typedef name could be + used. For example, you can use it in a declaration, in a cast, or + inside of `sizeof' or `typeof'. + + `typeof' is often useful in conjunction with the + statements-within-expressions feature. Here is how the two together can + be used to define a safe "maximum" macro that operates on any + arithmetic type and evaluates each of its arguments exactly once: + + #define max(a,b) \ + ({ typeof (a) _a = (a); \ + typeof (b) _b = (b); \ + _a > _b ? _a : _b; }) + + The reason for using names that start with underscores for the local + variables is to avoid conflicts with variable names that occur within + the expressions that are substituted for `a' and `b'. Eventually we + hope to design a new form of declaration syntax that allows you to + declare variables whose scopes start only after their initializers; + this will be a more reliable way to prevent such conflicts. + + Some more examples of the use of `typeof': + + * This declares `y' with the type of what `x' points to. + + typeof (*x) y; + + * This declares `y' as an array of such values. + + typeof (*x) y[4]; + + * This declares `y' as an array of pointers to characters: + + typeof (typeof (char *)[4]) y; + + It is equivalent to the following traditional C declaration: + + char *y[4]; + + To see the meaning of the declaration using `typeof', and why it + might be a useful way to write, let's rewrite it with these macros: + + #define pointer(T) typeof(T *) + #define array(T, N) typeof(T [N]) + + Now the declaration can be rewritten this way: + + array (pointer (char), 4) y; + + Thus, `array (pointer (char), 4)' is the type of arrays of 4 + pointers to `char'. + + _Compatibility Note:_ In addition to `typeof', GCC 2 supported a + more limited extension which permitted one to write + + typedef T = EXPR; + + with the effect of declaring T to have the type of the expression EXPR. + This extension does not work with GCC 3 (versions between 3.0 and 3.2 + will crash; 3.2.1 and later give an error). Code which relies on it + should be rewritten to use `typeof': + + typedef typeof(EXPR) T; + + This will work with all versions of GCC. + +  + File: gcc.info, Node: Lvalues, Next: Conditionals, Prev: Typeof, Up: C Extensions + + Generalized Lvalues + =================== + + Compound expressions, conditional expressions and casts are allowed + as lvalues provided their operands are lvalues. This means that you + can take their addresses or store values into them. + + Standard C++ allows compound expressions and conditional expressions + as lvalues, and permits casts to reference type, so use of this + extension is deprecated for C++ code. + + For example, a compound expression can be assigned, provided the last + expression in the sequence is an lvalue. These two expressions are + equivalent: + + (a, b) += 5 + a, (b += 5) + + Similarly, the address of the compound expression can be taken. + These two expressions are equivalent: + + &(a, b) + a, &b + + A conditional expression is a valid lvalue if its type is not void + and the true and false branches are both valid lvalues. For example, + these two expressions are equivalent: + + (a ? b : c) = 5 + (a ? b = 5 : (c = 5)) + + A cast is a valid lvalue if its operand is an lvalue. A simple + assignment whose left-hand side is a cast works by converting the + right-hand side first to the specified type, then to the type of the + inner left-hand side expression. After this is stored, the value is + converted back to the specified type to become the value of the + assignment. Thus, if `a' has type `char *', the following two + expressions are equivalent: + + (int)a = 5 + (int)(a = (char *)(int)5) + + An assignment-with-arithmetic operation such as `+=' applied to a + cast performs the arithmetic using the type resulting from the cast, + and then continues as in the previous case. Therefore, these two + expressions are equivalent: + + (int)a += 5 + (int)(a = (char *)(int) ((int)a + 5)) + + You cannot take the address of an lvalue cast, because the use of its + address would not work out coherently. Suppose that `&(int)f' were + permitted, where `f' has type `float'. Then the following statement + would try to store an integer bit-pattern where a floating point number + belongs: + + *&(int)f = 1; + + This is quite different from what `(int)f = 1' would do--that would + convert 1 to floating point and store it. Rather than cause this + inconsistency, we think it is better to prohibit use of `&' on a cast. + + If you really do want an `int *' pointer with the address of `f', + you can simply write `(int *)&f'. + +  + File: gcc.info, Node: Conditionals, Next: Long Long, Prev: Lvalues, Up: C Extensions + + Conditionals with Omitted Operands + ================================== + + The middle operand in a conditional expression may be omitted. Then + if the first operand is nonzero, its value is the value of the + conditional expression. + + Therefore, the expression + + x ? : y + + has the value of `x' if that is nonzero; otherwise, the value of `y'. + + This example is perfectly equivalent to + + x ? x : y + + In this simple case, the ability to omit the middle operand is not + especially useful. When it becomes useful is when the first operand + does, or may (if it is a macro argument), contain a side effect. Then + repeating the operand in the middle would perform the side effect + twice. Omitting the middle operand uses the value already computed + without the undesirable effects of recomputing it. + +  + File: gcc.info, Node: Long Long, Next: Complex, Prev: Conditionals, Up: C Extensions + + Double-Word Integers + ==================== + + ISO C99 supports data types for integers that are at least 64 bits + wide, and as an extension GCC supports them in C89 mode and in C++. + Simply write `long long int' for a signed integer, or `unsigned long + long int' for an unsigned integer. To make an integer constant of type + `long long int', add the suffix `LL' to the integer. To make an + integer constant of type `unsigned long long int', add the suffix `ULL' + to the integer. + + You can use these types in arithmetic like any other integer types. + Addition, subtraction, and bitwise boolean operations on these types + are open-coded on all types of machines. Multiplication is open-coded + if the machine supports fullword-to-doubleword a widening multiply + instruction. Division and shifts are open-coded only on machines that + provide special support. The operations that are not open-coded use + special library routines that come with GCC. + + There may be pitfalls when you use `long long' types for function + arguments, unless you declare function prototypes. If a function + expects type `int' for its argument, and you pass a value of type `long + long int', confusion will result because the caller and the subroutine + will disagree about the number of bytes for the argument. Likewise, if + the function expects `long long int' and you pass `int'. The best way + to avoid such problems is to use prototypes. + +  + File: gcc.info, Node: Complex, Next: Hex Floats, Prev: Long Long, Up: C Extensions + + Complex Numbers + =============== + + ISO C99 supports complex floating data types, and as an extension GCC + supports them in C89 mode and in C++, and supports complex integer data + types which are not part of ISO C99. You can declare complex types + using the keyword `_Complex'. As an extension, the older GNU keyword + `__complex__' is also supported. + + For example, `_Complex double x;' declares `x' as a variable whose + real part and imaginary part are both of type `double'. `_Complex + short int y;' declares `y' to have real and imaginary parts of type + `short int'; this is not likely to be useful, but it shows that the set + of complex types is complete. + + To write a constant with a complex data type, use the suffix `i' or + `j' (either one; they are equivalent). For example, `2.5fi' has type + `_Complex float' and `3i' has type `_Complex int'. Such a constant + always has a pure imaginary value, but you can form any complex value + you like by adding one to a real constant. This is a GNU extension; if + you have an ISO C99 conforming C library (such as GNU libc), and want + to construct complex constants of floating type, you should include + `' and use the macros `I' or `_Complex_I' instead. + + To extract the real part of a complex-valued expression EXP, write + `__real__ EXP'. Likewise, use `__imag__' to extract the imaginary + part. This is a GNU extension; for values of floating type, you should + use the ISO C99 functions `crealf', `creal', `creall', `cimagf', + `cimag' and `cimagl', declared in `' and also provided as + built-in functions by GCC. + + The operator `~' performs complex conjugation when used on a value + with a complex type. This is a GNU extension; for values of floating + type, you should use the ISO C99 functions `conjf', `conj' and `conjl', + declared in `' and also provided as built-in functions by + GCC. + + GCC can allocate complex automatic variables in a noncontiguous + fashion; it's even possible for the real part to be in a register while + the imaginary part is on the stack (or vice-versa). None of the + supported debugging info formats has a way to represent noncontiguous + allocation like this, so GCC describes a noncontiguous complex variable + as if it were two separate variables of noncomplex type. If the + variable's actual name is `foo', the two fictitious variables are named + `foo$real' and `foo$imag'. You can examine and set these two + fictitious variables with your debugger. + + A future version of GDB will know how to recognize such pairs and + treat them as a single variable with a complex type. + +  + File: gcc.info, Node: Hex Floats, Next: Zero Length, Prev: Complex, Up: C Extensions + + Hex Floats + ========== + + ISO C99 supports floating-point numbers written not only in the usual + decimal notation, such as `1.55e1', but also numbers such as `0x1.fp3' + written in hexadecimal format. As a GNU extension, GCC supports this + in C89 mode (except in some cases when strictly conforming) and in C++. + In that format the `0x' hex introducer and the `p' or `P' exponent + field are mandatory. The exponent is a decimal number that indicates + the power of 2 by which the significant part will be multiplied. Thus + `0x1.f' is 1 15/16, `p3' multiplies it by 8, and the value of `0x1.fp3' + is the same as `1.55e1'. + + Unlike for floating-point numbers in the decimal notation the + exponent is always required in the hexadecimal notation. Otherwise the + compiler would not be able to resolve the ambiguity of, e.g., `0x1.f'. + This could mean `1.0f' or `1.9375' since `f' is also the extension for + floating-point constants of type `float'. + +  + File: gcc.info, Node: Zero Length, Next: Variable Length, Prev: Hex Floats, Up: C Extensions + + Arrays of Length Zero + ===================== + + Zero-length arrays are allowed in GNU C. They are very useful as the + last element of a structure which is really a header for a + variable-length object: + + struct line { + int length; + char contents[0]; + }; + + struct line *thisline = (struct line *) + malloc (sizeof (struct line) + this_length); + thisline->length = this_length; + + In ISO C89, you would have to give `contents' a length of 1, which + means either you waste space or complicate the argument to `malloc'. + + In ISO C99, you would use a "flexible array member", which is + slightly different in syntax and semantics: + + * Flexible array members are written as `contents[]' without the `0'. + + * Flexible array members have incomplete type, and so the `sizeof' + operator may not be applied. As a quirk of the original + implementation of zero-length arrays, `sizeof' evaluates to zero. + + * Flexible array members may only appear as the last member of a + `struct' that is otherwise non-empty. + + GCC versions before 3.0 allowed zero-length arrays to be statically + initialized, as if they were flexible arrays. In addition to those + cases that were useful, it also allowed initializations in situations + that would corrupt later data. Non-empty initialization of zero-length + arrays is now treated like any case where there are more initializer + elements than the array holds, in that a suitable warning about "excess + elements in array" is given, and the excess elements (all of them, in + this case) are ignored. + + Instead GCC allows static initialization of flexible array members. + This is equivalent to defining a new structure containing the original + structure followed by an array of sufficient size to contain the data. + I.e. in the following, `f1' is constructed as if it were declared like + `f2'. + + struct f1 { + int x; int y[]; + } f1 = { 1, { 2, 3, 4 } }; + + struct f2 { + struct f1 f1; int data[3]; + } f2 = { { 1 }, { 2, 3, 4 } }; + + The convenience of this extension is that `f1' has the desired type, + eliminating the need to consistently refer to `f2.f1'. + + This has symmetry with normal static arrays, in that an array of + unknown size is also written with `[]'. + + Of course, this extension only makes sense if the extra data comes at + the end of a top-level object, as otherwise we would be overwriting + data at subsequent offsets. To avoid undue complication and confusion + with initialization of deeply nested arrays, we simply disallow any + non-empty initialization except when the structure is the top-level + object. For example: + + struct foo { int x; int y[]; }; + struct bar { struct foo z; }; + + struct foo a = { 1, { 2, 3, 4 } }; // Valid. + struct bar b = { { 1, { 2, 3, 4 } } }; // Invalid. + struct bar c = { { 1, { } } }; // Valid. + struct foo d[1] = { { 1 { 2, 3, 4 } } }; // Invalid. + +  + File: gcc.info, Node: Variable Length, Next: Variadic Macros, Prev: Zero Length, Up: C Extensions + + Arrays of Variable Length + ========================= + + Variable-length automatic arrays are allowed in ISO C99, and as an + extension GCC accepts them in C89 mode and in C++. (However, GCC's + implementation of variable-length arrays does not yet conform in detail + to the ISO C99 standard.) These arrays are declared like any other + automatic arrays, but with a length that is not a constant expression. + The storage is allocated at the point of declaration and deallocated + when the brace-level is exited. For example: + + FILE * + concat_fopen (char *s1, char *s2, char *mode) + { + char str[strlen (s1) + strlen (s2) + 1]; + strcpy (str, s1); + strcat (str, s2); + return fopen (str, mode); + } + + Jumping or breaking out of the scope of the array name deallocates + the storage. Jumping into the scope is not allowed; you get an error + message for it. + + You can use the function `alloca' to get an effect much like + variable-length arrays. The function `alloca' is available in many + other C implementations (but not in all). On the other hand, + variable-length arrays are more elegant. + + There are other differences between these two methods. Space + allocated with `alloca' exists until the containing _function_ returns. + The space for a variable-length array is deallocated as soon as the + array name's scope ends. (If you use both variable-length arrays and + `alloca' in the same function, deallocation of a variable-length array + will also deallocate anything more recently allocated with `alloca'.) + + You can also use variable-length arrays as arguments to functions: + + struct entry + tester (int len, char data[len][len]) + { + ... + } + + The length of an array is computed once when the storage is allocated + and is remembered for the scope of the array in case you access it with + `sizeof'. + + If you want to pass the array first and the length afterward, you can + use a forward declaration in the parameter list--another GNU extension. + + struct entry + tester (int len; char data[len][len], int len) + { + ... + } + + The `int len' before the semicolon is a "parameter forward + declaration", and it serves the purpose of making the name `len' known + when the declaration of `data' is parsed. + + You can write any number of such parameter forward declarations in + the parameter list. They can be separated by commas or semicolons, but + the last one must end with a semicolon, which is followed by the "real" + parameter declarations. Each forward declaration must match a "real" + declaration in parameter name and data type. ISO C99 does not support + parameter forward declarations. + +  + File: gcc.info, Node: Variadic Macros, Next: Escaped Newlines, Prev: Variable Length, Up: C Extensions + + Macros with a Variable Number of Arguments. + =========================================== + + In the ISO C standard of 1999, a macro can be declared to accept a + variable number of arguments much as a function can. The syntax for + defining the macro is similar to that of a function. Here is an + example: + + #define debug(format, ...) fprintf (stderr, format, __VA_ARGS__) + + Here `...' is a "variable argument". In the invocation of such a + macro, it represents the zero or more tokens until the closing + parenthesis that ends the invocation, including any commas. This set of + tokens replaces the identifier `__VA_ARGS__' in the macro body wherever + it appears. See the CPP manual for more information. + + GCC has long supported variadic macros, and used a different syntax + that allowed you to give a name to the variable arguments just like any + other argument. Here is an example: + + #define debug(format, args...) fprintf (stderr, format, args) + + This is in all ways equivalent to the ISO C example above, but + arguably more readable and descriptive. + + GNU CPP has two further variadic macro extensions, and permits them + to be used with either of the above forms of macro definition. + + In standard C, you are not allowed to leave the variable argument out + entirely; but you are allowed to pass an empty argument. For example, + this invocation is invalid in ISO C, because there is no comma after + the string: + + debug ("A message") + + GNU CPP permits you to completely omit the variable arguments in this + way. In the above examples, the compiler would complain, though since + the expansion of the macro still has the extra comma after the format + string. + + To help solve this problem, CPP behaves specially for variable + arguments used with the token paste operator, `##'. If instead you + write + + #define debug(format, ...) fprintf (stderr, format, ## __VA_ARGS__) + + and if the variable arguments are omitted or empty, the `##' + operator causes the preprocessor to remove the comma before it. If you + do provide some variable arguments in your macro invocation, GNU CPP + does not complain about the paste operation and instead places the + variable arguments after the comma. Just like any other pasted macro + argument, these arguments are not macro expanded. + +  + File: gcc.info, Node: Escaped Newlines, Next: Multi-line Strings, Prev: Variadic Macros, Up: C Extensions + + Slightly Looser Rules for Escaped Newlines + ========================================== + + Recently, the non-traditional preprocessor has relaxed its treatment + of escaped newlines. Previously, the newline had to immediately follow + a backslash. The current implementation allows whitespace in the form + of spaces, horizontal and vertical tabs, and form feeds between the + backslash and the subsequent newline. The preprocessor issues a + warning, but treats it as a valid escaped newline and combines the two + lines to form a single logical line. This works within comments and + tokens, including multi-line strings, as well as between tokens. + Comments are _not_ treated as whitespace for the purposes of this + relaxation, since they have not yet been replaced with spaces. + +  + File: gcc.info, Node: Multi-line Strings, Next: Subscripting, Prev: Escaped Newlines, Up: C Extensions + + String Literals with Embedded Newlines + ====================================== + + As an extension, GNU CPP permits string literals to cross multiple + lines without escaping the embedded newlines. Each embedded newline is + replaced with a single `\n' character in the resulting string literal, + regardless of what form the newline took originally. + + CPP currently allows such strings in directives as well (other than + the `#include' family). This is deprecated and will eventually be + removed. + +  + File: gcc.info, Node: Subscripting, Next: Pointer Arith, Prev: Multi-line Strings, Up: C Extensions + + Non-Lvalue Arrays May Have Subscripts + ===================================== + + In ISO C99, arrays that are not lvalues still decay to pointers, and + may be subscripted, although they may not be modified or used after the + next sequence point and the unary `&' operator may not be applied to + them. As an extension, GCC allows such arrays to be subscripted in C89 + mode, though otherwise they do not decay to pointers outside C99 mode. + For example, this is valid in GNU C though not valid in C89: + + struct foo {int a[4];}; + + struct foo f(); + + bar (int index) + { + return f().a[index]; + } + +  + File: gcc.info, Node: Pointer Arith, Next: Initializers, Prev: Subscripting, Up: C Extensions + + Arithmetic on `void'- and Function-Pointers + =========================================== + + In GNU C, addition and subtraction operations are supported on + pointers to `void' and on pointers to functions. This is done by + treating the size of a `void' or of a function as 1. + + A consequence of this is that `sizeof' is also allowed on `void' and + on function types, and returns 1. + + The option `-Wpointer-arith' requests a warning if these extensions + are used. + +  + File: gcc.info, Node: Initializers, Next: Compound Literals, Prev: Pointer Arith, Up: C Extensions + + Non-Constant Initializers + ========================= + + As in standard C++ and ISO C99, the elements of an aggregate + initializer for an automatic variable are not required to be constant + expressions in GNU C. Here is an example of an initializer with + run-time varying elements: + + foo (float f, float g) + { + float beat_freqs[2] = { f-g, f+g }; + ... + } + +  + File: gcc.info, Node: Compound Literals, Next: Designated Inits, Prev: Initializers, Up: C Extensions + + Compound Literals + ================= + + ISO C99 supports compound literals. A compound literal looks like a + cast containing an initializer. Its value is an object of the type + specified in the cast, containing the elements specified in the + initializer; it is an lvalue. As an extension, GCC supports compound + literals in C89 mode and in C++. + + Usually, the specified type is a structure. Assume that `struct + foo' and `structure' are declared as shown: + + struct foo {int a; char b[2];} structure; + + Here is an example of constructing a `struct foo' with a compound + literal: + + structure = ((struct foo) {x + y, 'a', 0}); + + This is equivalent to writing the following: + + { + struct foo temp = {x + y, 'a', 0}; + structure = temp; + } + + You can also construct an array. If all the elements of the + compound literal are (made up of) simple constant expressions, suitable + for use in initializers of objects of static storage duration, then the + compound literal can be coerced to a pointer to its first element and + used in such an initializer, as shown here: + + char **foo = (char *[]) { "x", "y", "z" }; + + Compound literals for scalar types and union types are is also + allowed, but then the compound literal is equivalent to a cast. + + As a GNU extension, GCC allows initialization of objects with static + storage duration by compound literals (which is not possible in ISO + C99, because the initializer is not a constant). It is handled as if + the object was initialized only with the bracket enclosed list if + compound literal's and object types match. The initializer list of the + compound literal must be constant. If the object being initialized has + array type of unknown size, the size is determined by compound literal + size. + + static struct foo x = (struct foo) {1, 'a', 'b'}; + static int y[] = (int []) {1, 2, 3}; + static int z[] = (int [3]) {1}; + + The above lines are equivalent to the following: + static struct foo x = {1, 'a', 'b'}; + static int y[] = {1, 2, 3}; + static int z[] = {1, 0, 0}; + +  + File: gcc.info, Node: Designated Inits, Next: Cast to Union, Prev: Compound Literals, Up: C Extensions + + Designated Initializers + ======================= + + Standard C89 requires the elements of an initializer to appear in a + fixed order, the same as the order of the elements in the array or + structure being initialized. + + In ISO C99 you can give the elements in any order, specifying the + array indices or structure field names they apply to, and GNU C allows + this as an extension in C89 mode as well. This extension is not + implemented in GNU C++. + + To specify an array index, write `[INDEX] =' before the element + value. For example, + + int a[6] = { [4] = 29, [2] = 15 }; + + is equivalent to + + int a[6] = { 0, 0, 15, 0, 29, 0 }; + + The index values must be constant expressions, even if the array being + initialized is automatic. + + An alternative syntax for this which has been obsolete since GCC 2.5 + but GCC still accepts is to write `[INDEX]' before the element value, + with no `='. + + To initialize a range of elements to the same value, write `[FIRST + ... LAST] = VALUE'. This is a GNU extension. For example, + + int widths[] = { [0 ... 9] = 1, [10 ... 99] = 2, [100] = 3 }; + + If the value in it has side-effects, the side-effects will happen only + once, not for each initialized field by the range initializer. + + Note that the length of the array is the highest value specified plus + one. + + In a structure initializer, specify the name of a field to initialize + with `.FIELDNAME =' before the element value. For example, given the + following structure, + + struct point { int x, y; }; + + the following initialization + + struct point p = { .y = yvalue, .x = xvalue }; + + is equivalent to + + struct point p = { xvalue, yvalue }; + + Another syntax which has the same meaning, obsolete since GCC 2.5, is + `FIELDNAME:', as shown here: + + struct point p = { y: yvalue, x: xvalue }; + + The `[INDEX]' or `.FIELDNAME' is known as a "designator". You can + also use a designator (or the obsolete colon syntax) when initializing + a union, to specify which element of the union should be used. For + example, + + union foo { int i; double d; }; + + union foo f = { .d = 4 }; + + will convert 4 to a `double' to store it in the union using the second + element. By contrast, casting 4 to type `union foo' would store it + into the union as the integer `i', since it is an integer. (*Note Cast + to Union::.) + + You can combine this technique of naming elements with ordinary C + initialization of successive elements. Each initializer element that + does not have a designator applies to the next consecutive element of + the array or structure. For example, + + int a[6] = { [1] = v1, v2, [4] = v4 }; + + is equivalent to + + int a[6] = { 0, v1, v2, 0, v4, 0 }; + + Labeling the elements of an array initializer is especially useful + when the indices are characters or belong to an `enum' type. For + example: + + int whitespace[256] + = { [' '] = 1, ['\t'] = 1, ['\h'] = 1, + ['\f'] = 1, ['\n'] = 1, ['\r'] = 1 }; + + You can also write a series of `.FIELDNAME' and `[INDEX]' + designators before an `=' to specify a nested subobject to initialize; + the list is taken relative to the subobject corresponding to the + closest surrounding brace pair. For example, with the `struct point' + declaration above: + + struct point ptarray[10] = { [2].y = yv2, [2].x = xv2, [0].x = xv0 }; + + If the same field is initialized multiple times, it will have value from + the last initialization. If any such overridden initialization has + side-effect, it is unspecified whether the side-effect happens or not. + Currently, gcc will discard them and issue a warning. + +  + File: gcc.info, Node: Case Ranges, Next: Mixed Declarations, Prev: Cast to Union, Up: C Extensions + + Case Ranges + =========== + + You can specify a range of consecutive values in a single `case' + label, like this: + + case LOW ... HIGH: + + This has the same effect as the proper number of individual `case' + labels, one for each integer value from LOW to HIGH, inclusive. + + This feature is especially useful for ranges of ASCII character + codes: + + case 'A' ... 'Z': + + *Be careful:* Write spaces around the `...', for otherwise it may be + parsed wrong when you use it with integer values. For example, write + this: + + case 1 ... 5: + + rather than this: + + case 1...5: + +  + File: gcc.info, Node: Cast to Union, Next: Case Ranges, Prev: Designated Inits, Up: C Extensions + + Cast to a Union Type + ==================== + + A cast to union type is similar to other casts, except that the type + specified is a union type. You can specify the type either with `union + TAG' or with a typedef name. A cast to union is actually a constructor + though, not a cast, and hence does not yield an lvalue like normal + casts. (*Note Compound Literals::.) + + The types that may be cast to the union type are those of the members + of the union. Thus, given the following union and variables: + + union foo { int i; double d; }; + int x; + double y; + + both `x' and `y' can be cast to type `union foo'. + + Using the cast as the right-hand side of an assignment to a variable + of union type is equivalent to storing in a member of the union: + + union foo u; + ... + u = (union foo) x == u.i = x + u = (union foo) y == u.d = y + + You can also use the union cast as a function argument: + + void hack (union foo); + ... + hack ((union foo) x); + +  + File: gcc.info, Node: Mixed Declarations, Next: Function Attributes, Prev: Case Ranges, Up: C Extensions + + Mixed Declarations and Code + =========================== + + ISO C99 and ISO C++ allow declarations and code to be freely mixed + within compound statements. As an extension, GCC also allows this in + C89 mode. For example, you could do: + + int i; + ... + i++; + int j = i + 2; + + Each identifier is visible from where it is declared until the end of + the enclosing block. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-12 gcc-3.2.3/gcc/doc/gcc.info-12 *** gcc-3.2.2/gcc/doc/gcc.info-12 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-12 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,1098 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Function Attributes, Next: Attribute Syntax, Prev: Mixed Declarations, Up: C Extensions + + Declaring Attributes of Functions + ================================= + + In GNU C, you declare certain things about functions called in your + program which help the compiler optimize function calls and check your + code more carefully. + + The keyword `__attribute__' allows you to specify special attributes + when making a declaration. This keyword is followed by an attribute + specification inside double parentheses. The following attributes are + currently defined for functions on all targets: `noreturn', `noinline', + `always_inline', `pure', `const', `format', `format_arg', + `no_instrument_function', `section', `constructor', `destructor', + `used', `unused', `deprecated', `weak', `malloc', and `alias'. Several + other attributes are defined for functions on particular target + systems. Other attributes, including `section' are supported for + variables declarations (*note Variable Attributes::) and for types + (*note Type Attributes::). + + You may also specify attributes with `__' preceding and following + each keyword. This allows you to use them in header files without + being concerned about a possible macro of the same name. For example, + you may use `__noreturn__' instead of `noreturn'. + + *Note Attribute Syntax::, for details of the exact syntax for using + attributes. + + `noreturn' + A few standard library functions, such as `abort' and `exit', + cannot return. GCC knows this automatically. Some programs define + their own functions that never return. You can declare them + `noreturn' to tell the compiler this fact. For example, + + void fatal () __attribute__ ((noreturn)); + + void + fatal (...) + { + ... /* Print error message. */ ... + exit (1); + } + + The `noreturn' keyword tells the compiler to assume that `fatal' + cannot return. It can then optimize without regard to what would + happen if `fatal' ever did return. This makes slightly better + code. More importantly, it helps avoid spurious warnings of + uninitialized variables. + + Do not assume that registers saved by the calling function are + restored before calling the `noreturn' function. + + It does not make sense for a `noreturn' function to have a return + type other than `void'. + + The attribute `noreturn' is not implemented in GCC versions + earlier than 2.5. An alternative way to declare that a function + does not return, which works in the current version and in some + older versions, is as follows: + + typedef void voidfn (); + + volatile voidfn fatal; + + `noinline' + This function attribute prevents a function from being considered + for inlining. + + `always_inline' + Generally, functions are not inlined unless optimization is + specified. For functions declared inline, this attribute inlines + the function even if no optimization level was specified. + + `pure' + Many functions have no effects except the return value and their + return value depends only on the parameters and/or global + variables. Such a function can be subject to common subexpression + elimination and loop optimization just as an arithmetic operator + would be. These functions should be declared with the attribute + `pure'. For example, + + int square (int) __attribute__ ((pure)); + + says that the hypothetical function `square' is safe to call fewer + times than the program says. + + Some of common examples of pure functions are `strlen' or `memcmp'. + Interesting non-pure functions are functions with infinite loops + or those depending on volatile memory or other system resource, + that may change between two consecutive calls (such as `feof' in a + multithreading environment). + + The attribute `pure' is not implemented in GCC versions earlier + than 2.96. + + `const' + Many functions do not examine any values except their arguments, + and have no effects except the return value. Basically this is + just slightly more strict class than the `pure' attribute above, + since function is not allowed to read global memory. + + Note that a function that has pointer arguments and examines the + data pointed to must _not_ be declared `const'. Likewise, a + function that calls a non-`const' function usually must not be + `const'. It does not make sense for a `const' function to return + `void'. + + The attribute `const' is not implemented in GCC versions earlier + than 2.5. An alternative way to declare that a function has no + side effects, which works in the current version and in some older + versions, is as follows: + + typedef int intfn (); + + extern const intfn square; + + This approach does not work in GNU C++ from 2.6.0 on, since the + language specifies that the `const' must be attached to the return + value. + + `format (ARCHETYPE, STRING-INDEX, FIRST-TO-CHECK)' + The `format' attribute specifies that a function takes `printf', + `scanf', `strftime' or `strfmon' style arguments which should be + type-checked against a format string. For example, the + declaration: + + extern int + my_printf (void *my_object, const char *my_format, ...) + __attribute__ ((format (printf, 2, 3))); + + causes the compiler to check the arguments in calls to `my_printf' + for consistency with the `printf' style format string argument + `my_format'. + + The parameter ARCHETYPE determines how the format string is + interpreted, and should be `printf', `scanf', `strftime' or + `strfmon'. (You can also use `__printf__', `__scanf__', + `__strftime__' or `__strfmon__'.) The parameter STRING-INDEX + specifies which argument is the format string argument (starting + from 1), while FIRST-TO-CHECK is the number of the first argument + to check against the format string. For functions where the + arguments are not available to be checked (such as `vprintf'), + specify the third parameter as zero. In this case the compiler + only checks the format string for consistency. For `strftime' + formats, the third parameter is required to be zero. + + In the example above, the format string (`my_format') is the second + argument of the function `my_print', and the arguments to check + start with the third argument, so the correct parameters for the + format attribute are 2 and 3. + + The `format' attribute allows you to identify your own functions + which take format strings as arguments, so that GCC can check the + calls to these functions for errors. The compiler always (unless + `-ffreestanding' is used) checks formats for the standard library + functions `printf', `fprintf', `sprintf', `scanf', `fscanf', + `sscanf', `strftime', `vprintf', `vfprintf' and `vsprintf' + whenever such warnings are requested (using `-Wformat'), so there + is no need to modify the header file `stdio.h'. In C99 mode, the + functions `snprintf', `vsnprintf', `vscanf', `vfscanf' and + `vsscanf' are also checked. Except in strictly conforming C + standard modes, the X/Open function `strfmon' is also checked as + are `printf_unlocked' and `fprintf_unlocked'. *Note Options + Controlling C Dialect: C Dialect Options. + + `format_arg (STRING-INDEX)' + The `format_arg' attribute specifies that a function takes a format + string for a `printf', `scanf', `strftime' or `strfmon' style + function and modifies it (for example, to translate it into + another language), so the result can be passed to a `printf', + `scanf', `strftime' or `strfmon' style function (with the + remaining arguments to the format function the same as they would + have been for the unmodified string). For example, the + declaration: + + extern char * + my_dgettext (char *my_domain, const char *my_format) + __attribute__ ((format_arg (2))); + + causes the compiler to check the arguments in calls to a `printf', + `scanf', `strftime' or `strfmon' type function, whose format + string argument is a call to the `my_dgettext' function, for + consistency with the format string argument `my_format'. If the + `format_arg' attribute had not been specified, all the compiler + could tell in such calls to format functions would be that the + format string argument is not constant; this would generate a + warning when `-Wformat-nonliteral' is used, but the calls could + not be checked without the attribute. + + The parameter STRING-INDEX specifies which argument is the format + string argument (starting from 1). + + The `format-arg' attribute allows you to identify your own + functions which modify format strings, so that GCC can check the + calls to `printf', `scanf', `strftime' or `strfmon' type function + whose operands are a call to one of your own function. The + compiler always treats `gettext', `dgettext', and `dcgettext' in + this manner except when strict ISO C support is requested by + `-ansi' or an appropriate `-std' option, or `-ffreestanding' is + used. *Note Options Controlling C Dialect: C Dialect Options. + + `no_instrument_function' + If `-finstrument-functions' is given, profiling function calls will + be generated at entry and exit of most user-compiled functions. + Functions with this attribute will not be so instrumented. + + `section ("SECTION-NAME")' + Normally, the compiler places the code it generates in the `text' + section. Sometimes, however, you need additional sections, or you + need certain particular functions to appear in special sections. + The `section' attribute specifies that a function lives in a + particular section. For example, the declaration: + + extern void foobar (void) __attribute__ ((section ("bar"))); + + puts the function `foobar' in the `bar' section. + + Some file formats do not support arbitrary sections so the + `section' attribute is not available on all platforms. If you + need to map the entire contents of a module to a particular + section, consider using the facilities of the linker instead. + + `constructor' + `destructor' + The `constructor' attribute causes the function to be called + automatically before execution enters `main ()'. Similarly, the + `destructor' attribute causes the function to be called + automatically after `main ()' has completed or `exit ()' has been + called. Functions with these attributes are useful for + initializing data that will be used implicitly during the + execution of the program. + + These attributes are not currently implemented for Objective-C. + + `unused' + This attribute, attached to a function, means that the function is + meant to be possibly unused. GCC will not produce a warning for + this function. GNU C++ does not currently support this attribute + as definitions without parameters are valid in C++. + + `used' + This attribute, attached to a function, means that code must be + emitted for the function even if it appears that the function is + not referenced. This is useful, for example, when the function is + referenced only in inline assembly. + + `deprecated' + The `deprecated' attribute results in a warning if the function is + used anywhere in the source file. This is useful when identifying + functions that are expected to be removed in a future version of a + program. The warning also includes the location of the declaration + of the deprecated function, to enable users to easily find further + information about why the function is deprecated, or what they + should do instead. Note that the warnings only occurs for uses: + + int old_fn () __attribute__ ((deprecated)); + int old_fn (); + int (*fn_ptr)() = old_fn; + + results in a warning on line 3 but not line 2. + + The `deprecated' attribute can also be used for variables and + types (*note Variable Attributes::, *note Type Attributes::.) + + `weak' + The `weak' attribute causes the declaration to be emitted as a weak + symbol rather than a global. This is primarily useful in defining + library functions which can be overridden in user code, though it + can also be used with non-function declarations. Weak symbols are + supported for ELF targets, and also for a.out targets when using + the GNU assembler and linker. + + `malloc' + The `malloc' attribute is used to tell the compiler that a function + may be treated as if it were the malloc function. The compiler + assumes that calls to malloc result in a pointers that cannot + alias anything. This will often improve optimization. + + `alias ("TARGET")' + The `alias' attribute causes the declaration to be emitted as an + alias for another symbol, which must be specified. For instance, + + void __f () { /* do something */; } + void f () __attribute__ ((weak, alias ("__f"))); + + declares `f' to be a weak alias for `__f'. In C++, the mangled + name for the target must be used. + + Not all target machines support this attribute. + + `regparm (NUMBER)' + On the Intel 386, the `regparm' attribute causes the compiler to + pass up to NUMBER integer arguments in registers EAX, EDX, and ECX + instead of on the stack. Functions that take a variable number of + arguments will continue to be passed all of their arguments on the + stack. + + `stdcall' + On the Intel 386, the `stdcall' attribute causes the compiler to + assume that the called function will pop off the stack space used + to pass arguments, unless it takes a variable number of arguments. + + The PowerPC compiler for Windows NT currently ignores the `stdcall' + attribute. + + `cdecl' + On the Intel 386, the `cdecl' attribute causes the compiler to + assume that the calling function will pop off the stack space used + to pass arguments. This is useful to override the effects of the + `-mrtd' switch. + + The PowerPC compiler for Windows NT currently ignores the `cdecl' + attribute. + + `longcall' + On the RS/6000 and PowerPC, the `longcall' attribute causes the + compiler to always call the function via a pointer, so that + functions which reside further than 64 megabytes (67,108,864 + bytes) from the current location can be called. + + `long_call/short_call' + This attribute allows to specify how to call a particular function + on ARM. Both attributes override the `-mlong-calls' (*note ARM + Options::) command line switch and `#pragma long_calls' settings. + The `long_call' attribute causes the compiler to always call the + function by first loading its address into a register and then + using the contents of that register. The `short_call' attribute + always places the offset to the function from the call site into + the `BL' instruction directly. + + `dllimport' + On the PowerPC running Windows NT, the `dllimport' attribute causes + the compiler to call the function via a global pointer to the + function pointer that is set up by the Windows NT dll library. + The pointer name is formed by combining `__imp_' and the function + name. + + `dllexport' + On the PowerPC running Windows NT, the `dllexport' attribute causes + the compiler to provide a global pointer to the function pointer, + so that it can be called with the `dllimport' attribute. The + pointer name is formed by combining `__imp_' and the function name. + + `exception (EXCEPT-FUNC [, EXCEPT-ARG])' + On the PowerPC running Windows NT, the `exception' attribute causes + the compiler to modify the structured exception table entry it + emits for the declared function. The string or identifier + EXCEPT-FUNC is placed in the third entry of the structured + exception table. It represents a function, which is called by the + exception handling mechanism if an exception occurs. If it was + specified, the string or identifier EXCEPT-ARG is placed in the + fourth entry of the structured exception table. + + `function_vector' + Use this attribute on the H8/300 and H8/300H to indicate that the + specified function should be called through the function vector. + Calling a function through the function vector will reduce code + size, however; the function vector has a limited size (maximum 128 + entries on the H8/300 and 64 entries on the H8/300H) and shares + space with the interrupt vector. + + You must use GAS and GLD from GNU binutils version 2.7 or later for + this attribute to work correctly. + + `interrupt' + Use this attribute on the ARM, AVR, M32R/D and Xstormy16 ports to + indicate that the specified function is an interrupt handler. The + compiler will generate function entry and exit sequences suitable + for use in an interrupt handler when this attribute is present. + + Note, interrupt handlers for the H8/300, H8/300H and SH processors + can be specified via the `interrupt_handler' attribute. + + Note, on the AVR interrupts will be enabled inside the function. + + Note, for the ARM you can specify the kind of interrupt to be + handled by adding an optional parameter to the interrupt attribute + like this: + + void f () __attribute__ ((interrupt ("IRQ"))); + + Permissible values for this parameter are: IRQ, FIQ, SWI, ABORT + and UNDEF. + + `interrupt_handler' + Use this attribute on the H8/300, H8/300H and SH to indicate that + the specified function is an interrupt handler. The compiler will + generate function entry and exit sequences suitable for use in an + interrupt handler when this attribute is present. + + `sp_switch' + Use this attribute on the SH to indicate an `interrupt_handler' + function should switch to an alternate stack. It expects a string + argument that names a global variable holding the address of the + alternate stack. + + void *alt_stack; + void f () __attribute__ ((interrupt_handler, + sp_switch ("alt_stack"))); + + `trap_exit' + Use this attribute on the SH for an `interrupt_handle' to return + using `trapa' instead of `rte'. This attribute expects an integer + argument specifying the trap number to be used. + + `eightbit_data' + Use this attribute on the H8/300 and H8/300H to indicate that the + specified variable should be placed into the eight bit data + section. The compiler will generate more efficient code for + certain operations on data in the eight bit data area. Note the + eight bit data area is limited to 256 bytes of data. + + You must use GAS and GLD from GNU binutils version 2.7 or later for + this attribute to work correctly. + + `tiny_data' + Use this attribute on the H8/300H to indicate that the specified + variable should be placed into the tiny data section. The + compiler will generate more efficient code for loads and stores on + data in the tiny data section. Note the tiny data area is limited + to slightly under 32kbytes of data. + + `signal' + Use this attribute on the AVR to indicate that the specified + function is an signal handler. The compiler will generate function + entry and exit sequences suitable for use in an signal handler + when this attribute is present. Interrupts will be disabled + inside function. + + `naked' + Use this attribute on the ARM or AVR ports to indicate that the + specified function do not need prologue/epilogue sequences + generated by the compiler. It is up to the programmer to provide + these sequences. + + `model (MODEL-NAME)' + Use this attribute on the M32R/D to set the addressability of an + object, and the code generated for a function. The identifier + MODEL-NAME is one of `small', `medium', or `large', representing + each of the code models. + + Small model objects live in the lower 16MB of memory (so that their + addresses can be loaded with the `ld24' instruction), and are + callable with the `bl' instruction. + + Medium model objects may live anywhere in the 32-bit address space + (the compiler will generate `seth/add3' instructions to load their + addresses), and are callable with the `bl' instruction. + + Large model objects may live anywhere in the 32-bit address space + (the compiler will generate `seth/add3' instructions to load their + addresses), and may not be reachable with the `bl' instruction + (the compiler will generate the much slower `seth/add3/jl' + instruction sequence). + + + You can specify multiple attributes in a declaration by separating + them by commas within the double parentheses or by immediately + following an attribute declaration with another attribute declaration. + + Some people object to the `__attribute__' feature, suggesting that + ISO C's `#pragma' should be used instead. At the time `__attribute__' + was designed, there were two reasons for not doing this. + + 1. It is impossible to generate `#pragma' commands from a macro. + + 2. There is no telling what the same `#pragma' might mean in another + compiler. + + These two reasons applied to almost any application that might have + been proposed for `#pragma'. It was basically a mistake to use + `#pragma' for _anything_. + + The ISO C99 standard includes `_Pragma', which now allows pragmas to + be generated from macros. In addition, a `#pragma GCC' namespace is + now in use for GCC-specific pragmas. However, it has been found + convenient to use `__attribute__' to achieve a natural attachment of + attributes to their corresponding declarations, whereas `#pragma GCC' + is of use for constructs that do not naturally form part of the + grammar. *Note Miscellaneous Preprocessing Directives: (cpp)Other + Directives. + +  + File: gcc.info, Node: Attribute Syntax, Next: Function Prototypes, Prev: Function Attributes, Up: C Extensions + + Attribute Syntax + ================ + + This section describes the syntax with which `__attribute__' may be + used, and the constructs to which attribute specifiers bind, for the C + language. Some details may vary for C++ and Objective-C. Because of + infelicities in the grammar for attributes, some forms described here + may not be successfully parsed in all cases. + + There are some problems with the semantics of attributes in C++. For + example, there are no manglings for attributes, although they may affect + code generation, so problems may arise when attributed types are used in + conjunction with templates or overloading. Similarly, `typeid' does + not distinguish between types with different attributes. Support for + attributes in C++ may be restricted in future to attributes on + declarations only, but not on nested declarators. + + *Note Function Attributes::, for details of the semantics of + attributes applying to functions. *Note Variable Attributes::, for + details of the semantics of attributes applying to variables. *Note + Type Attributes::, for details of the semantics of attributes applying + to structure, union and enumerated types. + + An "attribute specifier" is of the form `__attribute__ + ((ATTRIBUTE-LIST))'. An "attribute list" is a possibly empty + comma-separated sequence of "attributes", where each attribute is one + of the following: + + * Empty. Empty attributes are ignored. + + * A word (which may be an identifier such as `unused', or a reserved + word such as `const'). + + * A word, followed by, in parentheses, parameters for the attribute. + These parameters take one of the following forms: + + * An identifier. For example, `mode' attributes use this form. + + * An identifier followed by a comma and a non-empty + comma-separated list of expressions. For example, `format' + attributes use this form. + + * A possibly empty comma-separated list of expressions. For + example, `format_arg' attributes use this form with the list + being a single integer constant expression, and `alias' + attributes use this form with the list being a single string + constant. + + An "attribute specifier list" is a sequence of one or more attribute + specifiers, not separated by any other tokens. + + An attribute specifier list may appear after the colon following a + label, other than a `case' or `default' label. The only attribute it + makes sense to use after a label is `unused'. This feature is intended + for code generated by programs which contains labels that may be unused + but which is compiled with `-Wall'. It would not normally be + appropriate to use in it human-written code, though it could be useful + in cases where the code that jumps to the label is contained within an + `#ifdef' conditional. + + An attribute specifier list may appear as part of a `struct', + `union' or `enum' specifier. It may go either immediately after the + `struct', `union' or `enum' keyword, or after the closing brace. It is + ignored if the content of the structure, union or enumerated type is + not defined in the specifier in which the attribute specifier list is + used--that is, in usages such as `struct __attribute__((foo)) bar' with + no following opening brace. Where attribute specifiers follow the + closing brace, they are considered to relate to the structure, union or + enumerated type defined, not to any enclosing declaration the type + specifier appears in, and the type defined is not complete until after + the attribute specifiers. + + Otherwise, an attribute specifier appears as part of a declaration, + counting declarations of unnamed parameters and type names, and relates + to that declaration (which may be nested in another declaration, for + example in the case of a parameter declaration), or to a particular + declarator within a declaration. Where an attribute specifier is + applied to a parameter declared as a function or an array, it should + apply to the function or array rather than the pointer to which the + parameter is implicitly converted, but this is not yet correctly + implemented. + + Any list of specifiers and qualifiers at the start of a declaration + may contain attribute specifiers, whether or not such a list may in that + context contain storage class specifiers. (Some attributes, however, + are essentially in the nature of storage class specifiers, and only make + sense where storage class specifiers may be used; for example, + `section'.) There is one necessary limitation to this syntax: the + first old-style parameter declaration in a function definition cannot + begin with an attribute specifier, because such an attribute applies to + the function instead by syntax described below (which, however, is not + yet implemented in this case). In some other cases, attribute + specifiers are permitted by this grammar but not yet supported by the + compiler. All attribute specifiers in this place relate to the + declaration as a whole. In the obsolescent usage where a type of `int' + is implied by the absence of type specifiers, such a list of specifiers + and qualifiers may be an attribute specifier list with no other + specifiers or qualifiers. + + An attribute specifier list may appear immediately before a + declarator (other than the first) in a comma-separated list of + declarators in a declaration of more than one identifier using a single + list of specifiers and qualifiers. Such attribute specifiers apply + only to the identifier before whose declarator they appear. For + example, in + + __attribute__((noreturn)) void d0 (void), + __attribute__((format(printf, 1, 2))) d1 (const char *, ...), + d2 (void) + + the `noreturn' attribute applies to all the functions declared; the + `format' attribute only applies to `d1'. + + An attribute specifier list may appear immediately before the comma, + `=' or semicolon terminating the declaration of an identifier other + than a function definition. At present, such attribute specifiers apply + to the declared object or function, but in future they may attach to the + outermost adjacent declarator. In simple cases there is no difference, + but, for example, in + + void (****f)(void) __attribute__((noreturn)); + + at present the `noreturn' attribute applies to `f', which causes a + warning since `f' is not a function, but in future it may apply to the + function `****f'. The precise semantics of what attributes in such + cases will apply to are not yet specified. Where an assembler name for + an object or function is specified (*note Asm Labels::), at present the + attribute must follow the `asm' specification; in future, attributes + before the `asm' specification may apply to the adjacent declarator, + and those after it to the declared object or function. + + An attribute specifier list may, in future, be permitted to appear + after the declarator in a function definition (before any old-style + parameter declarations or the function body). + + Attribute specifiers may be mixed with type qualifiers appearing + inside the `[]' of a parameter array declarator, in the C99 construct by + which such qualifiers are applied to the pointer to which the array is + implicitly converted. Such attribute specifiers apply to the pointer, + not to the array, but at present this is not implemented and they are + ignored. + + An attribute specifier list may appear at the start of a nested + declarator. At present, there are some limitations in this usage: the + attributes correctly apply to the declarator, but for most individual + attributes the semantics this implies are not implemented. When + attribute specifiers follow the `*' of a pointer declarator, they may + be mixed with any type qualifiers present. The following describes the + formal semantics of this syntax. It will make the most sense if you + are familiar with the formal specification of declarators in the ISO C + standard. + + Consider (as in C99 subclause 6.7.5 paragraph 4) a declaration `T + D1', where `T' contains declaration specifiers that specify a type TYPE + (such as `int') and `D1' is a declarator that contains an identifier + IDENT. The type specified for IDENT for derived declarators whose type + does not include an attribute specifier is as in the ISO C standard. + + If `D1' has the form `( ATTRIBUTE-SPECIFIER-LIST D )', and the + declaration `T D' specifies the type "DERIVED-DECLARATOR-TYPE-LIST + TYPE" for IDENT, then `T D1' specifies the type + "DERIVED-DECLARATOR-TYPE-LIST ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT. + + If `D1' has the form `* TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST + D', and the declaration `T D' specifies the type + "DERIVED-DECLARATOR-TYPE-LIST TYPE" for IDENT, then `T D1' specifies + the type "DERIVED-DECLARATOR-TYPE-LIST + TYPE-QUALIFIER-AND-ATTRIBUTE-SPECIFIER-LIST TYPE" for IDENT. + + For example, + + void (__attribute__((noreturn)) ****f) (void); + + specifies the type "pointer to pointer to pointer to pointer to + non-returning function returning `void'". As another example, + + char *__attribute__((aligned(8))) *f; + + specifies the type "pointer to 8-byte-aligned pointer to `char'". Note + again that this does not work with most attributes; for example, the + usage of `aligned' and `noreturn' attributes given above is not yet + supported. + + For compatibility with existing code written for compiler versions + that did not implement attributes on nested declarators, some laxity is + allowed in the placing of attributes. If an attribute that only applies + to types is applied to a declaration, it will be treated as applying to + the type of that declaration. If an attribute that only applies to + declarations is applied to the type of a declaration, it will be treated + as applying to that declaration; and, for compatibility with code + placing the attributes immediately before the identifier declared, such + an attribute applied to a function return type will be treated as + applying to the function type, and such an attribute applied to an array + element type will be treated as applying to the array type. If an + attribute that only applies to function types is applied to a + pointer-to-function type, it will be treated as applying to the pointer + target type; if such an attribute is applied to a function return type + that is not a pointer-to-function type, it will be treated as applying + to the function type. + +  + File: gcc.info, Node: Function Prototypes, Next: C++ Comments, Prev: Attribute Syntax, Up: C Extensions + + Prototypes and Old-Style Function Definitions + ============================================= + + GNU C extends ISO C to allow a function prototype to override a later + old-style non-prototype definition. Consider the following example: + + /* Use prototypes unless the compiler is old-fashioned. */ + #ifdef __STDC__ + #define P(x) x + #else + #define P(x) () + #endif + + /* Prototype function declaration. */ + int isroot P((uid_t)); + + /* Old-style function definition. */ + int + isroot (x) /* ??? lossage here ??? */ + uid_t x; + { + return x == 0; + } + + Suppose the type `uid_t' happens to be `short'. ISO C does not + allow this example, because subword arguments in old-style + non-prototype definitions are promoted. Therefore in this example the + function definition's argument is really an `int', which does not match + the prototype argument type of `short'. + + This restriction of ISO C makes it hard to write code that is + portable to traditional C compilers, because the programmer does not + know whether the `uid_t' type is `short', `int', or `long'. Therefore, + in cases like these GNU C allows a prototype to override a later + old-style definition. More precisely, in GNU C, a function prototype + argument type overrides the argument type specified by a later + old-style definition if the former type is the same as the latter type + before promotion. Thus in GNU C the above example is equivalent to the + following: + + int isroot (uid_t); + + int + isroot (uid_t x) + { + return x == 0; + } + + GNU C++ does not support old-style function definitions, so this + extension is irrelevant. + +  + File: gcc.info, Node: C++ Comments, Next: Dollar Signs, Prev: Function Prototypes, Up: C Extensions + + C++ Style Comments + ================== + + In GNU C, you may use C++ style comments, which start with `//' and + continue until the end of the line. Many other C implementations allow + such comments, and they are likely to be in a future C standard. + However, C++ style comments are not recognized if you specify `-ansi', + a `-std' option specifying a version of ISO C before C99, or + `-traditional', since they are incompatible with traditional constructs + like `dividend//*comment*/divisor'. + +  + File: gcc.info, Node: Dollar Signs, Next: Character Escapes, Prev: C++ Comments, Up: C Extensions + + Dollar Signs in Identifier Names + ================================ + + In GNU C, you may normally use dollar signs in identifier names. + This is because many traditional C implementations allow such + identifiers. However, dollar signs in identifiers are not supported on + a few target machines, typically because the target assembler does not + allow them. + +  + File: gcc.info, Node: Character Escapes, Next: Variable Attributes, Prev: Dollar Signs, Up: C Extensions + + The Character in Constants + ================================ + + You can use the sequence `\e' in a string or character constant to + stand for the ASCII character . + +  + File: gcc.info, Node: Alignment, Next: Inline, Prev: Type Attributes, Up: C Extensions + + Inquiring on Alignment of Types or Variables + ============================================ + + The keyword `__alignof__' allows you to inquire about how an object + is aligned, or the minimum alignment usually required by a type. Its + syntax is just like `sizeof'. + + For example, if the target machine requires a `double' value to be + aligned on an 8-byte boundary, then `__alignof__ (double)' is 8. This + is true on many RISC machines. On more traditional machine designs, + `__alignof__ (double)' is 4 or even 2. + + Some machines never actually require alignment; they allow reference + to any data type even at an odd addresses. For these machines, + `__alignof__' reports the _recommended_ alignment of a type. + + If the operand of `__alignof__' is an lvalue rather than a type, its + value is the required alignment for its type, taking into account any + minimum alignment specified with GCC's `__attribute__' extension (*note + Variable Attributes::). For example, after this declaration: + + struct foo { int x; char y; } foo1; + + the value of `__alignof__ (foo1.y)' is 1, even though its actual + alignment is probably 2 or 4, the same as `__alignof__ (int)'. + + It is an error to ask for the alignment of an incomplete type. + +  + File: gcc.info, Node: Variable Attributes, Next: Type Attributes, Prev: Character Escapes, Up: C Extensions + + Specifying Attributes of Variables + ================================== + + The keyword `__attribute__' allows you to specify special attributes + of variables or structure fields. This keyword is followed by an + attribute specification inside double parentheses. Ten attributes are + currently defined for variables: `aligned', `mode', `nocommon', + `packed', `section', `transparent_union', `unused', `deprecated', + `vector_size', and `weak'. Some other attributes are defined for + variables on particular target systems. Other attributes are available + for functions (*note Function Attributes::) and for types (*note Type + Attributes::). Other front ends might define more attributes (*note + Extensions to the C++ Language: C++ Extensions.). + + You may also specify attributes with `__' preceding and following + each keyword. This allows you to use them in header files without + being concerned about a possible macro of the same name. For example, + you may use `__aligned__' instead of `aligned'. + + *Note Attribute Syntax::, for details of the exact syntax for using + attributes. + + `aligned (ALIGNMENT)' + This attribute specifies a minimum alignment for the variable or + structure field, measured in bytes. For example, the declaration: + + int x __attribute__ ((aligned (16))) = 0; + + causes the compiler to allocate the global variable `x' on a + 16-byte boundary. On a 68040, this could be used in conjunction + with an `asm' expression to access the `move16' instruction which + requires 16-byte aligned operands. + + You can also specify the alignment of structure fields. For + example, to create a double-word aligned `int' pair, you could + write: + + struct foo { int x[2] __attribute__ ((aligned (8))); }; + + This is an alternative to creating a union with a `double' member + that forces the union to be double-word aligned. + + As in the preceding examples, you can explicitly specify the + alignment (in bytes) that you wish the compiler to use for a given + variable or structure field. Alternatively, you can leave out the + alignment factor and just ask the compiler to align a variable or + field to the maximum useful alignment for the target machine you + are compiling for. For example, you could write: + + short array[3] __attribute__ ((aligned)); + + Whenever you leave out the alignment factor in an `aligned' + attribute specification, the compiler automatically sets the + alignment for the declared variable or field to the largest + alignment which is ever used for any data type on the target + machine you are compiling for. Doing this can often make copy + operations more efficient, because the compiler can use whatever + instructions copy the biggest chunks of memory when performing + copies to or from the variables or fields that you have aligned + this way. + + The `aligned' attribute can only increase the alignment; but you + can decrease it by specifying `packed' as well. See below. + + Note that the effectiveness of `aligned' attributes may be limited + by inherent limitations in your linker. On many systems, the + linker is only able to arrange for variables to be aligned up to a + certain maximum alignment. (For some linkers, the maximum + supported alignment may be very very small.) If your linker is + only able to align variables up to a maximum of 8 byte alignment, + then specifying `aligned(16)' in an `__attribute__' will still + only provide you with 8 byte alignment. See your linker + documentation for further information. + + `mode (MODE)' + This attribute specifies the data type for the + declaration--whichever type corresponds to the mode MODE. This in + effect lets you request an integer or floating point type + according to its width. + + You may also specify a mode of `byte' or `__byte__' to indicate + the mode corresponding to a one-byte integer, `word' or `__word__' + for the mode of a one-word integer, and `pointer' or `__pointer__' + for the mode used to represent pointers. + + `nocommon' + This attribute specifies requests GCC not to place a variable + "common" but instead to allocate space for it directly. If you + specify the `-fno-common' flag, GCC will do this for all variables. + + Specifying the `nocommon' attribute for a variable provides an + initialization of zeros. A variable may only be initialized in one + source file. + + `packed' + The `packed' attribute specifies that a variable or structure field + should have the smallest possible alignment--one byte for a + variable, and one bit for a field, unless you specify a larger + value with the `aligned' attribute. + + Here is a structure in which the field `x' is packed, so that it + immediately follows `a': + + struct foo + { + char a; + int x[2] __attribute__ ((packed)); + }; + + `section ("SECTION-NAME")' + Normally, the compiler places the objects it generates in sections + like `data' and `bss'. Sometimes, however, you need additional + sections, or you need certain particular variables to appear in + special sections, for example to map to special hardware. The + `section' attribute specifies that a variable (or function) lives + in a particular section. For example, this small program uses + several specific section names: + + struct duart a __attribute__ ((section ("DUART_A"))) = { 0 }; + struct duart b __attribute__ ((section ("DUART_B"))) = { 0 }; + char stack[10000] __attribute__ ((section ("STACK"))) = { 0 }; + int init_data __attribute__ ((section ("INITDATA"))) = 0; + + main() + { + /* Initialize stack pointer */ + init_sp (stack + sizeof (stack)); + + /* Initialize initialized data */ + memcpy (&init_data, &data, &edata - &data); + + /* Turn on the serial ports */ + init_duart (&a); + init_duart (&b); + } + + Use the `section' attribute with an _initialized_ definition of a + _global_ variable, as shown in the example. GCC issues a warning + and otherwise ignores the `section' attribute in uninitialized + variable declarations. + + You may only use the `section' attribute with a fully initialized + global definition because of the way linkers work. The linker + requires each object be defined once, with the exception that + uninitialized variables tentatively go in the `common' (or `bss') + section and can be multiply "defined". You can force a variable + to be initialized with the `-fno-common' flag or the `nocommon' + attribute. + + Some file formats do not support arbitrary sections so the + `section' attribute is not available on all platforms. If you + need to map the entire contents of a module to a particular + section, consider using the facilities of the linker instead. + + `shared' + On Windows NT, in addition to putting variable definitions in a + named section, the section can also be shared among all running + copies of an executable or DLL. For example, this small program + defines shared data by putting it in a named section `shared' and + marking the section shareable: + + int foo __attribute__((section ("shared"), shared)) = 0; + + int + main() + { + /* Read and write foo. All running + copies see the same value. */ + return 0; + } + + You may only use the `shared' attribute along with `section' + attribute with a fully initialized global definition because of + the way linkers work. See `section' attribute for more + information. + + The `shared' attribute is only available on Windows NT. + + `transparent_union' + This attribute, attached to a function parameter which is a union, + means that the corresponding argument may have the type of any + union member, but the argument is passed as if its type were that + of the first union member. For more details see *Note Type + Attributes::. You can also use this attribute on a `typedef' for + a union data type; then it applies to all function parameters with + that type. + + `unused' + This attribute, attached to a variable, means that the variable is + meant to be possibly unused. GCC will not produce a warning for + this variable. + + `deprecated' + The `deprecated' attribute results in a warning if the variable is + used anywhere in the source file. This is useful when identifying + variables that are expected to be removed in a future version of a + program. The warning also includes the location of the declaration + of the deprecated variable, to enable users to easily find further + information about why the variable is deprecated, or what they + should do instead. Note that the warnings only occurs for uses: + + extern int old_var __attribute__ ((deprecated)); + extern int old_var; + int new_fn () { return old_var; } + + results in a warning on line 3 but not line 2. + + The `deprecated' attribute can also be used for functions and + types (*note Function Attributes::, *note Type Attributes::.) + + `vector_size (BYTES)' + This attribute specifies the vector size for the variable, + measured in bytes. For example, the declaration: + + int foo __attribute__ ((vector_size (16))); + + causes the compiler to set the mode for `foo', to be 16 bytes, + divided into `int' sized units. Assuming a 32-bit int (a vector of + 4 units of 4 bytes), the corresponding mode of `foo' will be V4SI. + + This attribute is only applicable to integral and float scalars, + although arrays, pointers, and function return values are allowed + in conjunction with this construct. + + Aggregates with this attribute are invalid, even if they are of + the same size as a corresponding scalar. For example, the + declaration: + + struct S { int a; }; + struct S __attribute__ ((vector_size (16))) foo; + + is invalid even if the size of the structure is the same as the + size of the `int'. + + `weak' + The `weak' attribute is described in *Note Function Attributes::. + + `model (MODEL-NAME)' + Use this attribute on the M32R/D to set the addressability of an + object. The identifier MODEL-NAME is one of `small', `medium', or + `large', representing each of the code models. + + Small model objects live in the lower 16MB of memory (so that their + addresses can be loaded with the `ld24' instruction). + + Medium and large model objects may live anywhere in the 32-bit + address space (the compiler will generate `seth/add3' instructions + to load their addresses). + + + To specify multiple attributes, separate them by commas within the + double parentheses: for example, `__attribute__ ((aligned (16), + packed))'. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-13 gcc-3.2.3/gcc/doc/gcc.info-13 *** gcc-3.2.2/gcc/doc/gcc.info-13 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-13 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,981 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Type Attributes, Next: Alignment, Prev: Variable Attributes, Up: C Extensions + + Specifying Attributes of Types + ============================== + + The keyword `__attribute__' allows you to specify special attributes + of `struct' and `union' types when you define such types. This keyword + is followed by an attribute specification inside double parentheses. + Five attributes are currently defined for types: `aligned', `packed', + `transparent_union', `unused', and `deprecated'. Other attributes are + defined for functions (*note Function Attributes::) and for variables + (*note Variable Attributes::). + + You may also specify any one of these attributes with `__' preceding + and following its keyword. This allows you to use these attributes in + header files without being concerned about a possible macro of the same + name. For example, you may use `__aligned__' instead of `aligned'. + + You may specify the `aligned' and `transparent_union' attributes + either in a `typedef' declaration or just past the closing curly brace + of a complete enum, struct or union type _definition_ and the `packed' + attribute only past the closing brace of a definition. + + You may also specify attributes between the enum, struct or union + tag and the name of the type rather than after the closing brace. + + *Note Attribute Syntax::, for details of the exact syntax for using + attributes. + + `aligned (ALIGNMENT)' + This attribute specifies a minimum alignment (in bytes) for + variables of the specified type. For example, the declarations: + + struct S { short f[3]; } __attribute__ ((aligned (8))); + typedef int more_aligned_int __attribute__ ((aligned (8))); + + force the compiler to insure (as far as it can) that each variable + whose type is `struct S' or `more_aligned_int' will be allocated + and aligned _at least_ on a 8-byte boundary. On a Sparc, having + all variables of type `struct S' aligned to 8-byte boundaries + allows the compiler to use the `ldd' and `std' (doubleword load and + store) instructions when copying one variable of type `struct S' to + another, thus improving run-time efficiency. + + Note that the alignment of any given `struct' or `union' type is + required by the ISO C standard to be at least a perfect multiple of + the lowest common multiple of the alignments of all of the members + of the `struct' or `union' in question. This means that you _can_ + effectively adjust the alignment of a `struct' or `union' type by + attaching an `aligned' attribute to any one of the members of such + a type, but the notation illustrated in the example above is a + more obvious, intuitive, and readable way to request the compiler + to adjust the alignment of an entire `struct' or `union' type. + + As in the preceding example, you can explicitly specify the + alignment (in bytes) that you wish the compiler to use for a given + `struct' or `union' type. Alternatively, you can leave out the + alignment factor and just ask the compiler to align a type to the + maximum useful alignment for the target machine you are compiling + for. For example, you could write: + + struct S { short f[3]; } __attribute__ ((aligned)); + + Whenever you leave out the alignment factor in an `aligned' + attribute specification, the compiler automatically sets the + alignment for the type to the largest alignment which is ever used + for any data type on the target machine you are compiling for. + Doing this can often make copy operations more efficient, because + the compiler can use whatever instructions copy the biggest chunks + of memory when performing copies to or from the variables which + have types that you have aligned this way. + + In the example above, if the size of each `short' is 2 bytes, then + the size of the entire `struct S' type is 6 bytes. The smallest + power of two which is greater than or equal to that is 8, so the + compiler sets the alignment for the entire `struct S' type to 8 + bytes. + + Note that although you can ask the compiler to select a + time-efficient alignment for a given type and then declare only + individual stand-alone objects of that type, the compiler's + ability to select a time-efficient alignment is primarily useful + only when you plan to create arrays of variables having the + relevant (efficiently aligned) type. If you declare or use arrays + of variables of an efficiently-aligned type, then it is likely + that your program will also be doing pointer arithmetic (or + subscripting, which amounts to the same thing) on pointers to the + relevant type, and the code that the compiler generates for these + pointer arithmetic operations will often be more efficient for + efficiently-aligned types than for other types. + + The `aligned' attribute can only increase the alignment; but you + can decrease it by specifying `packed' as well. See below. + + Note that the effectiveness of `aligned' attributes may be limited + by inherent limitations in your linker. On many systems, the + linker is only able to arrange for variables to be aligned up to a + certain maximum alignment. (For some linkers, the maximum + supported alignment may be very very small.) If your linker is + only able to align variables up to a maximum of 8 byte alignment, + then specifying `aligned(16)' in an `__attribute__' will still + only provide you with 8 byte alignment. See your linker + documentation for further information. + + `packed' + This attribute, attached to an `enum', `struct', or `union' type + definition, specified that the minimum required memory be used to + represent the type. + + Specifying this attribute for `struct' and `union' types is + equivalent to specifying the `packed' attribute on each of the + structure or union members. Specifying the `-fshort-enums' flag + on the line is equivalent to specifying the `packed' attribute on + all `enum' definitions. + + You may only specify this attribute after a closing curly brace on + an `enum' definition, not in a `typedef' declaration, unless that + declaration also contains the definition of the `enum'. + + `transparent_union' + This attribute, attached to a `union' type definition, indicates + that any function parameter having that union type causes calls to + that function to be treated in a special way. + + First, the argument corresponding to a transparent union type can + be of any type in the union; no cast is required. Also, if the + union contains a pointer type, the corresponding argument can be a + null pointer constant or a void pointer expression; and if the + union contains a void pointer type, the corresponding argument can + be any pointer expression. If the union member type is a pointer, + qualifiers like `const' on the referenced type must be respected, + just as with normal pointer conversions. + + Second, the argument is passed to the function using the calling + conventions of first member of the transparent union, not the + calling conventions of the union itself. All members of the union + must have the same machine representation; this is necessary for + this argument passing to work properly. + + Transparent unions are designed for library functions that have + multiple interfaces for compatibility reasons. For example, + suppose the `wait' function must accept either a value of type + `int *' to comply with Posix, or a value of type `union wait *' to + comply with the 4.1BSD interface. If `wait''s parameter were + `void *', `wait' would accept both kinds of arguments, but it + would also accept any other pointer type and this would make + argument type checking less useful. Instead, `' might + define the interface as follows: + + typedef union + { + int *__ip; + union wait *__up; + } wait_status_ptr_t __attribute__ ((__transparent_union__)); + + pid_t wait (wait_status_ptr_t); + + This interface allows either `int *' or `union wait *' arguments + to be passed, using the `int *' calling convention. The program + can call `wait' with arguments of either type: + + int w1 () { int w; return wait (&w); } + int w2 () { union wait w; return wait (&w); } + + With this interface, `wait''s implementation might look like this: + + pid_t wait (wait_status_ptr_t p) + { + return waitpid (-1, p.__ip, 0); + } + + `unused' + When attached to a type (including a `union' or a `struct'), this + attribute means that variables of that type are meant to appear + possibly unused. GCC will not produce a warning for any variables + of that type, even if the variable appears to do nothing. This is + often the case with lock or thread classes, which are usually + defined and then not referenced, but contain constructors and + destructors that have nontrivial bookkeeping functions. + + `deprecated' + The `deprecated' attribute results in a warning if the type is + used anywhere in the source file. This is useful when identifying + types that are expected to be removed in a future version of a + program. If possible, the warning also includes the location of + the declaration of the deprecated type, to enable users to easily + find further information about why the type is deprecated, or what + they should do instead. Note that the warnings only occur for + uses and then only if the type is being applied to an identifier + that itself is not being declared as deprecated. + + typedef int T1 __attribute__ ((deprecated)); + T1 x; + typedef T1 T2; + T2 y; + typedef T1 T3 __attribute__ ((deprecated)); + T3 z __attribute__ ((deprecated)); + + results in a warning on line 2 and 3 but not lines 4, 5, or 6. No + warning is issued for line 4 because T2 is not explicitly + deprecated. Line 5 has no warning because T3 is explicitly + deprecated. Similarly for line 6. + + The `deprecated' attribute can also be used for functions and + variables (*note Function Attributes::, *note Variable + Attributes::.) + + + To specify multiple attributes, separate them by commas within the + double parentheses: for example, `__attribute__ ((aligned (16), + packed))'. + +  + File: gcc.info, Node: Inline, Next: Extended Asm, Prev: Alignment, Up: C Extensions + + An Inline Function is As Fast As a Macro + ======================================== + + By declaring a function `inline', you can direct GCC to integrate + that function's code into the code for its callers. This makes + execution faster by eliminating the function-call overhead; in + addition, if any of the actual argument values are constant, their known + values may permit simplifications at compile time so that not all of the + inline function's code needs to be included. The effect on code size is + less predictable; object code may be larger or smaller with function + inlining, depending on the particular case. Inlining of functions is an + optimization and it really "works" only in optimizing compilation. If + you don't use `-O', no function is really inline. + + Inline functions are included in the ISO C99 standard, but there are + currently substantial differences between what GCC implements and what + the ISO C99 standard requires. + + To declare a function inline, use the `inline' keyword in its + declaration, like this: + + inline int + inc (int *a) + { + (*a)++; + } + + (If you are writing a header file to be included in ISO C programs, + write `__inline__' instead of `inline'. *Note Alternate Keywords::.) + You can also make all "simple enough" functions inline with the option + `-finline-functions'. + + Note that certain usages in a function definition can make it + unsuitable for inline substitution. Among these usages are: use of + varargs, use of alloca, use of variable sized data types (*note + Variable Length::), use of computed goto (*note Labels as Values::), + use of nonlocal goto, and nested functions (*note Nested Functions::). + Using `-Winline' will warn when a function marked `inline' could not be + substituted, and will give the reason for the failure. + + Note that in C and Objective-C, unlike C++, the `inline' keyword + does not affect the linkage of the function. + + GCC automatically inlines member functions defined within the class + body of C++ programs even if they are not explicitly declared `inline'. + (You can override this with `-fno-default-inline'; *note Options + Controlling C++ Dialect: C++ Dialect Options..) + + When a function is both inline and `static', if all calls to the + function are integrated into the caller, and the function's address is + never used, then the function's own assembler code is never referenced. + In this case, GCC does not actually output assembler code for the + function, unless you specify the option `-fkeep-inline-functions'. + Some calls cannot be integrated for various reasons (in particular, + calls that precede the function's definition cannot be integrated, and + neither can recursive calls within the definition). If there is a + nonintegrated call, then the function is compiled to assembler code as + usual. The function must also be compiled as usual if the program + refers to its address, because that can't be inlined. + + When an inline function is not `static', then the compiler must + assume that there may be calls from other source files; since a global + symbol can be defined only once in any program, the function must not + be defined in the other source files, so the calls therein cannot be + integrated. Therefore, a non-`static' inline function is always + compiled on its own in the usual fashion. + + If you specify both `inline' and `extern' in the function + definition, then the definition is used only for inlining. In no case + is the function compiled on its own, not even if you refer to its + address explicitly. Such an address becomes an external reference, as + if you had only declared the function, and had not defined it. + + This combination of `inline' and `extern' has almost the effect of a + macro. The way to use it is to put a function definition in a header + file with these keywords, and put another copy of the definition + (lacking `inline' and `extern') in a library file. The definition in + the header file will cause most calls to the function to be inlined. + If any uses of the function remain, they will refer to the single copy + in the library. + + For future compatibility with when GCC implements ISO C99 semantics + for inline functions, it is best to use `static inline' only. (The + existing semantics will remain available when `-std=gnu89' is + specified, but eventually the default will be `-std=gnu99' and that + will implement the C99 semantics, though it does not do so yet.) + + GCC does not inline any functions when not optimizing unless you + specify the `always_inline' attribute for the function, like this: + + /* Prototype. */ + inline void foo (const char) __attribute__((always_inline)); + +  + File: gcc.info, Node: Extended Asm, Next: Constraints, Prev: Inline, Up: C Extensions + + Assembler Instructions with C Expression Operands + ================================================= + + In an assembler instruction using `asm', you can specify the + operands of the instruction using C expressions. This means you need + not guess which registers or memory locations will contain the data you + want to use. + + You must specify an assembler instruction template much like what + appears in a machine description, plus an operand constraint string for + each operand. + + For example, here is how to use the 68881's `fsinx' instruction: + + asm ("fsinx %1,%0" : "=f" (result) : "f" (angle)); + + Here `angle' is the C expression for the input operand while `result' + is that of the output operand. Each has `"f"' as its operand + constraint, saying that a floating point register is required. The `=' + in `=f' indicates that the operand is an output; all output operands' + constraints must use `='. The constraints use the same language used + in the machine description (*note Constraints::). + + Each operand is described by an operand-constraint string followed by + the C expression in parentheses. A colon separates the assembler + template from the first output operand and another separates the last + output operand from the first input, if any. Commas separate the + operands within each group. The total number of operands is currently + limited to 30; this limitation may be lifted in some future version of + GCC. + + If there are no output operands but there are input operands, you + must place two consecutive colons surrounding the place where the output + operands would go. + + As of GCC version 3.1, it is also possible to specify input and + output operands using symbolic names which can be referenced within the + assembler code. These names are specified inside square brackets + preceding the constraint string, and can be referenced inside the + assembler code using `%[NAME]' instead of a percentage sign followed by + the operand number. Using named operands the above example could look + like: + + asm ("fsinx %[angle],%[output]" + : [output] "=f" (result) + : [angle] "f" (angle)); + + Note that the symbolic operand names have no relation whatsoever to + other C identifiers. You may use any name you like, even those of + existing C symbols, but must ensure that no two operands within the same + assembler construct use the same symbolic name. + + Output operand expressions must be lvalues; the compiler can check + this. The input operands need not be lvalues. The compiler cannot + check whether the operands have data types that are reasonable for the + instruction being executed. It does not parse the assembler instruction + template and does not know what it means or even whether it is valid + assembler input. The extended `asm' feature is most often used for + machine instructions the compiler itself does not know exist. If the + output expression cannot be directly addressed (for example, it is a + bit-field), your constraint must allow a register. In that case, GCC + will use the register as the output of the `asm', and then store that + register into the output. + + The ordinary output operands must be write-only; GCC will assume that + the values in these operands before the instruction are dead and need + not be generated. Extended asm supports input-output or read-write + operands. Use the constraint character `+' to indicate such an operand + and list it with the output operands. + + When the constraints for the read-write operand (or the operand in + which only some of the bits are to be changed) allows a register, you + may, as an alternative, logically split its function into two separate + operands, one input operand and one write-only output operand. The + connection between them is expressed by constraints which say they need + to be in the same location when the instruction executes. You can use + the same C expression for both operands, or different expressions. For + example, here we write the (fictitious) `combine' instruction with + `bar' as its read-only source operand and `foo' as its read-write + destination: + + asm ("combine %2,%0" : "=r" (foo) : "0" (foo), "g" (bar)); + + The constraint `"0"' for operand 1 says that it must occupy the same + location as operand 0. A number in constraint is allowed only in an + input operand and it must refer to an output operand. + + Only a number in the constraint can guarantee that one operand will + be in the same place as another. The mere fact that `foo' is the value + of both operands is not enough to guarantee that they will be in the + same place in the generated assembler code. The following would not + work reliably: + + asm ("combine %2,%0" : "=r" (foo) : "r" (foo), "g" (bar)); + + Various optimizations or reloading could cause operands 0 and 1 to + be in different registers; GCC knows no reason not to do so. For + example, the compiler might find a copy of the value of `foo' in one + register and use it for operand 1, but generate the output operand 0 in + a different register (copying it afterward to `foo''s own address). Of + course, since the register for operand 1 is not even mentioned in the + assembler code, the result will not work, but GCC can't tell that. + + As of GCC version 3.1, one may write `[NAME]' instead of the operand + number for a matching constraint. For example: + + asm ("cmoveq %1,%2,%[result]" + : [result] "=r"(result) + : "r" (test), "r"(new), "[result]"(old)); + + Some instructions clobber specific hard registers. To describe this, + write a third colon after the input operands, followed by the names of + the clobbered hard registers (given as strings). Here is a realistic + example for the VAX: + + asm volatile ("movc3 %0,%1,%2" + : /* no outputs */ + : "g" (from), "g" (to), "g" (count) + : "r0", "r1", "r2", "r3", "r4", "r5"); + + You may not write a clobber description in a way that overlaps with + an input or output operand. For example, you may not have an operand + describing a register class with one member if you mention that register + in the clobber list. There is no way for you to specify that an input + operand is modified without also specifying it as an output operand. + Note that if all the output operands you specify are for this purpose + (and hence unused), you will then also need to specify `volatile' for + the `asm' construct, as described below, to prevent GCC from deleting + the `asm' statement as unused. + + If you refer to a particular hardware register from the assembler + code, you will probably have to list the register after the third colon + to tell the compiler the register's value is modified. In some + assemblers, the register names begin with `%'; to produce one `%' in the + assembler code, you must write `%%' in the input. + + If your assembler instruction can alter the condition code register, + add `cc' to the list of clobbered registers. GCC on some machines + represents the condition codes as a specific hardware register; `cc' + serves to name this register. On other machines, the condition code is + handled differently, and specifying `cc' has no effect. But it is + valid no matter what the machine. + + If your assembler instruction modifies memory in an unpredictable + fashion, add `memory' to the list of clobbered registers. This will + cause GCC to not keep memory values cached in registers across the + assembler instruction. You will also want to add the `volatile' + keyword if the memory affected is not listed in the inputs or outputs + of the `asm', as the `memory' clobber does not count as a side-effect + of the `asm'. + + You can put multiple assembler instructions together in a single + `asm' template, separated by the characters normally used in assembly + code for the system. A combination that works in most places is a + newline to break the line, plus a tab character to move to the + instruction field (written as `\n\t'). Sometimes semicolons can be + used, if the assembler allows semicolons as a line-breaking character. + Note that some assembler dialects use semicolons to start a comment. + The input operands are guaranteed not to use any of the clobbered + registers, and neither will the output operands' addresses, so you can + read and write the clobbered registers as many times as you like. Here + is an example of multiple instructions in a template; it assumes the + subroutine `_foo' accepts arguments in registers 9 and 10: + + asm ("movl %0,r9\n\tmovl %1,r10\n\tcall _foo" + : /* no outputs */ + : "g" (from), "g" (to) + : "r9", "r10"); + + Unless an output operand has the `&' constraint modifier, GCC may + allocate it in the same register as an unrelated input operand, on the + assumption the inputs are consumed before the outputs are produced. + This assumption may be false if the assembler code actually consists of + more than one instruction. In such a case, use `&' for each output + operand that may not overlap an input. *Note Modifiers::. + + If you want to test the condition code produced by an assembler + instruction, you must include a branch and a label in the `asm' + construct, as follows: + + asm ("clr %0\n\tfrob %1\n\tbeq 0f\n\tmov #1,%0\n0:" + : "g" (result) + : "g" (input)); + + This assumes your assembler supports local labels, as the GNU assembler + and most Unix assemblers do. + + Speaking of labels, jumps from one `asm' to another are not + supported. The compiler's optimizers do not know about these jumps, and + therefore they cannot take account of them when deciding how to + optimize. + + Usually the most convenient way to use these `asm' instructions is to + encapsulate them in macros that look like functions. For example, + + #define sin(x) \ + ({ double __value, __arg = (x); \ + asm ("fsinx %1,%0": "=f" (__value): "f" (__arg)); \ + __value; }) + + Here the variable `__arg' is used to make sure that the instruction + operates on a proper `double' value, and to accept only those arguments + `x' which can convert automatically to a `double'. + + Another way to make sure the instruction operates on the correct data + type is to use a cast in the `asm'. This is different from using a + variable `__arg' in that it converts more different types. For + example, if the desired type were `int', casting the argument to `int' + would accept a pointer with no complaint, while assigning the argument + to an `int' variable named `__arg' would warn about using a pointer + unless the caller explicitly casts it. + + If an `asm' has output operands, GCC assumes for optimization + purposes the instruction has no side effects except to change the output + operands. This does not mean instructions with a side effect cannot be + used, but you must be careful, because the compiler may eliminate them + if the output operands aren't used, or move them out of loops, or + replace two with one if they constitute a common subexpression. Also, + if your instruction does have a side effect on a variable that otherwise + appears not to change, the old value of the variable may be reused later + if it happens to be found in a register. + + You can prevent an `asm' instruction from being deleted, moved + significantly, or combined, by writing the keyword `volatile' after the + `asm'. For example: + + #define get_and_set_priority(new) \ + ({ int __old; \ + asm volatile ("get_and_set_priority %0, %1" \ + : "=g" (__old) : "g" (new)); \ + __old; }) + + If you write an `asm' instruction with no outputs, GCC will know the + instruction has side-effects and will not delete the instruction or + move it outside of loops. + + The `volatile' keyword indicates that the instruction has important + side-effects. GCC will not delete a volatile `asm' if it is reachable. + (The instruction can still be deleted if GCC can prove that + control-flow will never reach the location of the instruction.) In + addition, GCC will not reschedule instructions across a volatile `asm' + instruction. For example: + + *(volatile int *)addr = foo; + asm volatile ("eieio" : : ); + + Assume `addr' contains the address of a memory mapped device register. + The PowerPC `eieio' instruction (Enforce In-order Execution of I/O) + tells the CPU to make sure that the store to that device register + happens before it issues any other I/O. + + Note that even a volatile `asm' instruction can be moved in ways + that appear insignificant to the compiler, such as across jump + instructions. You can't expect a sequence of volatile `asm' + instructions to remain perfectly consecutive. If you want consecutive + output, use a single `asm'. Also, GCC will perform some optimizations + across a volatile `asm' instruction; GCC does not "forget everything" + when it encounters a volatile `asm' instruction the way some other + compilers do. + + An `asm' instruction without any operands or clobbers (an "old + style" `asm') will be treated identically to a volatile `asm' + instruction. + + It is a natural idea to look for a way to give access to the + condition code left by the assembler instruction. However, when we + attempted to implement this, we found no way to make it work reliably. + The problem is that output operands might need reloading, which would + result in additional following "store" instructions. On most machines, + these instructions would alter the condition code before there was time + to test it. This problem doesn't arise for ordinary "test" and + "compare" instructions because they don't have any output operands. + + For reasons similar to those described above, it is not possible to + give an assembler instruction access to the condition code left by + previous instructions. + + If you are writing a header file that should be includable in ISO C + programs, write `__asm__' instead of `asm'. *Note Alternate Keywords::. + + i386 floating point asm operands + -------------------------------- + + There are several rules on the usage of stack-like regs in + asm_operands insns. These rules apply only to the operands that are + stack-like regs: + + 1. Given a set of input regs that die in an asm_operands, it is + necessary to know which are implicitly popped by the asm, and + which must be explicitly popped by gcc. + + An input reg that is implicitly popped by the asm must be + explicitly clobbered, unless it is constrained to match an output + operand. + + 2. For any input reg that is implicitly popped by an asm, it is + necessary to know how to adjust the stack to compensate for the + pop. If any non-popped input is closer to the top of the + reg-stack than the implicitly popped reg, it would not be possible + to know what the stack looked like--it's not clear how the rest of + the stack "slides up". + + All implicitly popped input regs must be closer to the top of the + reg-stack than any input that is not implicitly popped. + + It is possible that if an input dies in an insn, reload might use + the input reg for an output reload. Consider this example: + + asm ("foo" : "=t" (a) : "f" (b)); + + This asm says that input B is not popped by the asm, and that the + asm pushes a result onto the reg-stack, i.e., the stack is one + deeper after the asm than it was before. But, it is possible that + reload will think that it can use the same reg for both the input + and the output, if input B dies in this insn. + + If any input operand uses the `f' constraint, all output reg + constraints must use the `&' earlyclobber. + + The asm above would be written as + + asm ("foo" : "=&t" (a) : "f" (b)); + + 3. Some operands need to be in particular places on the stack. All + output operands fall in this category--there is no other way to + know which regs the outputs appear in unless the user indicates + this in the constraints. + + Output operands must specifically indicate which reg an output + appears in after an asm. `=f' is not allowed: the operand + constraints must select a class with a single reg. + + 4. Output operands may not be "inserted" between existing stack regs. + Since no 387 opcode uses a read/write operand, all output operands + are dead before the asm_operands, and are pushed by the + asm_operands. It makes no sense to push anywhere but the top of + the reg-stack. + + Output operands must start at the top of the reg-stack: output + operands may not "skip" a reg. + + 5. Some asm statements may need extra stack space for internal + calculations. This can be guaranteed by clobbering stack registers + unrelated to the inputs and outputs. + + + Here are a couple of reasonable asms to want to write. This asm + takes one input, which is internally popped, and produces two outputs. + + asm ("fsincos" : "=t" (cos), "=u" (sin) : "0" (inp)); + + This asm takes two inputs, which are popped by the `fyl2xp1' opcode, + and replaces them with one output. The user must code the `st(1)' + clobber for reg-stack.c to know that `fyl2xp1' pops both inputs. + + asm ("fyl2xp1" : "=t" (result) : "0" (x), "u" (y) : "st(1)"); + +  + File: gcc.info, Node: Constraints, Next: Asm Labels, Prev: Extended Asm, Up: C Extensions + + Constraints for `asm' Operands + ============================== + + Here are specific details on what constraint letters you can use with + `asm' operands. Constraints can say whether an operand may be in a + register, and which kinds of register; whether the operand can be a + memory reference, and which kinds of address; whether the operand may + be an immediate constant, and which possible values it may have. + Constraints can also require two operands to match. + + * Menu: + + * Simple Constraints:: Basic use of constraints. + * Multi-Alternative:: When an insn has two alternative constraint-patterns. + * Modifiers:: More precise control over effects of constraints. + * Machine Constraints:: Special constraints for some particular machines. + +  + File: gcc.info, Node: Simple Constraints, Next: Multi-Alternative, Up: Constraints + + Simple Constraints + ------------------ + + The simplest kind of constraint is a string full of letters, each of + which describes one kind of operand that is permitted. Here are the + letters that are allowed: + + whitespace + Whitespace characters are ignored and can be inserted at any + position except the first. This enables each alternative for + different operands to be visually aligned in the machine + description even if they have different number of constraints and + modifiers. + + `m' + A memory operand is allowed, with any kind of address that the + machine supports in general. + + `o' + A memory operand is allowed, but only if the address is + "offsettable". This means that adding a small integer (actually, + the width in bytes of the operand, as determined by its machine + mode) may be added to the address and the result is also a valid + memory address. + + For example, an address which is constant is offsettable; so is an + address that is the sum of a register and a constant (as long as a + slightly larger constant is also within the range of + address-offsets supported by the machine); but an autoincrement or + autodecrement address is not offsettable. More complicated + indirect/indexed addresses may or may not be offsettable depending + on the other addressing modes that the machine supports. + + Note that in an output operand which can be matched by another + operand, the constraint letter `o' is valid only when accompanied + by both `<' (if the target machine has predecrement addressing) + and `>' (if the target machine has preincrement addressing). + + `V' + A memory operand that is not offsettable. In other words, + anything that would fit the `m' constraint but not the `o' + constraint. + + `<' + A memory operand with autodecrement addressing (either + predecrement or postdecrement) is allowed. + + `>' + A memory operand with autoincrement addressing (either + preincrement or postincrement) is allowed. + + `r' + A register operand is allowed provided that it is in a general + register. + + `i' + An immediate integer operand (one with constant value) is allowed. + This includes symbolic constants whose values will be known only at + assembly time. + + `n' + An immediate integer operand with a known numeric value is allowed. + Many systems cannot support assembly-time constants for operands + less than a word wide. Constraints for these operands should use + `n' rather than `i'. + + `I', `J', `K', ... `P' + Other letters in the range `I' through `P' may be defined in a + machine-dependent fashion to permit immediate integer operands with + explicit integer values in specified ranges. For example, on the + 68000, `I' is defined to stand for the range of values 1 to 8. + This is the range permitted as a shift count in the shift + instructions. + + `E' + An immediate floating operand (expression code `const_double') is + allowed, but only if the target floating point format is the same + as that of the host machine (on which the compiler is running). + + `F' + An immediate floating operand (expression code `const_double') is + allowed. + + `G', `H' + `G' and `H' may be defined in a machine-dependent fashion to + permit immediate floating operands in particular ranges of values. + + `s' + An immediate integer operand whose value is not an explicit + integer is allowed. + + This might appear strange; if an insn allows a constant operand + with a value not known at compile time, it certainly must allow + any known value. So why use `s' instead of `i'? Sometimes it + allows better code to be generated. + + For example, on the 68000 in a fullword instruction it is possible + to use an immediate operand; but if the immediate value is between + -128 and 127, better code results from loading the value into a + register and using the register. This is because the load into + the register can be done with a `moveq' instruction. We arrange + for this to happen by defining the letter `K' to mean "any integer + outside the range -128 to 127", and then specifying `Ks' in the + operand constraints. + + `g' + Any register, memory or immediate integer operand is allowed, + except for registers that are not general registers. + + `X' + Any operand whatsoever is allowed. + + `0', `1', `2', ... `9' + An operand that matches the specified operand number is allowed. + If a digit is used together with letters within the same + alternative, the digit should come last. + + This number is allowed to be more than a single digit. If multiple + digits are encountered consecutavely, they are interpreted as a + single decimal integer. There is scant chance for ambiguity, + since to-date it has never been desirable that `10' be interpreted + as matching either operand 1 _or_ operand 0. Should this be + desired, one can use multiple alternatives instead. + + This is called a "matching constraint" and what it really means is + that the assembler has only a single operand that fills two roles + which `asm' distinguishes. For example, an add instruction uses + two input operands and an output operand, but on most CISC + machines an add instruction really has only two operands, one of + them an input-output operand: + + addl #35,r12 + + Matching constraints are used in these circumstances. More + precisely, the two operands that match must include one input-only + operand and one output-only operand. Moreover, the digit must be a + smaller number than the number of the operand that uses it in the + constraint. + + `p' + An operand that is a valid memory address is allowed. This is for + "load address" and "push address" instructions. + + `p' in the constraint must be accompanied by `address_operand' as + the predicate in the `match_operand'. This predicate interprets + the mode specified in the `match_operand' as the mode of the memory + reference for which the address would be valid. + + OTHER-LETTERS + Other letters can be defined in machine-dependent fashion to stand + for particular classes of registers or other arbitrary operand + types. `d', `a' and `f' are defined on the 68000/68020 to stand + for data, address and floating point registers. + + +  + File: gcc.info, Node: Multi-Alternative, Next: Modifiers, Prev: Simple Constraints, Up: Constraints + + Multiple Alternative Constraints + -------------------------------- + + Sometimes a single instruction has multiple alternative sets of + possible operands. For example, on the 68000, a logical-or instruction + can combine register or an immediate value into memory, or it can + combine any kind of operand into a register; but it cannot combine one + memory location into another. + + These constraints are represented as multiple alternatives. An + alternative can be described by a series of letters for each operand. + The overall constraint for an operand is made from the letters for this + operand from the first alternative, a comma, the letters for this + operand from the second alternative, a comma, and so on until the last + alternative. + + If all the operands fit any one alternative, the instruction is + valid. Otherwise, for each alternative, the compiler counts how many + instructions must be added to copy the operands so that that + alternative applies. The alternative requiring the least copying is + chosen. If two alternatives need the same amount of copying, the one + that comes first is chosen. These choices can be altered with the `?' + and `!' characters: + + `?' + Disparage slightly the alternative that the `?' appears in, as a + choice when no alternative applies exactly. The compiler regards + this alternative as one unit more costly for each `?' that appears + in it. + + `!' + Disparage severely the alternative that the `!' appears in. This + alternative can still be used if it fits without reloading, but if + reloading is needed, some other alternative will be used. + +  + File: gcc.info, Node: Modifiers, Next: Machine Constraints, Prev: Multi-Alternative, Up: Constraints + + Constraint Modifier Characters + ------------------------------ + + Here are constraint modifier characters. + + `=' + Means that this operand is write-only for this instruction: the + previous value is discarded and replaced by output data. + + `+' + Means that this operand is both read and written by the + instruction. + + When the compiler fixes up the operands to satisfy the constraints, + it needs to know which operands are inputs to the instruction and + which are outputs from it. `=' identifies an output; `+' + identifies an operand that is both input and output; all other + operands are assumed to be input only. + + If you specify `=' or `+' in a constraint, you put it in the first + character of the constraint string. + + `&' + Means (in a particular alternative) that this operand is an + "earlyclobber" operand, which is modified before the instruction is + finished using the input operands. Therefore, this operand may + not lie in a register that is used as an input operand or as part + of any memory address. + + `&' applies only to the alternative in which it is written. In + constraints with multiple alternatives, sometimes one alternative + requires `&' while others do not. See, for example, the `movdf' + insn of the 68000. + + An input operand can be tied to an earlyclobber operand if its only + use as an input occurs before the early result is written. Adding + alternatives of this form often allows GCC to produce better code + when only some of the inputs can be affected by the earlyclobber. + See, for example, the `mulsi3' insn of the ARM. + + `&' does not obviate the need to write `='. + + `%' + Declares the instruction to be commutative for this operand and the + following operand. This means that the compiler may interchange + the two operands if that is the cheapest way to make all operands + fit the constraints. + + `#' + Says that all following characters, up to the next comma, are to be + ignored as a constraint. They are significant only for choosing + register preferences. + + `*' + Says that the following character should be ignored when choosing + register preferences. `*' has no effect on the meaning of the + constraint as a constraint, and no effect on reloading. + + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-14 gcc-3.2.3/gcc/doc/gcc.info-14 *** gcc-3.2.2/gcc/doc/gcc.info-14 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-14 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1584 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Machine Constraints, Prev: Modifiers, Up: Constraints + + Constraints for Particular Machines + ----------------------------------- + + Whenever possible, you should use the general-purpose constraint + letters in `asm' arguments, since they will convey meaning more readily + to people reading your code. Failing that, use the constraint letters + that usually have very similar meanings across architectures. The most + commonly used constraints are `m' and `r' (for memory and + general-purpose registers respectively; *note Simple Constraints::), and + `I', usually the letter indicating the most common immediate-constant + format. + + For each machine architecture, the `config/MACHINE/MACHINE.h' file + defines additional constraints. These constraints are used by the + compiler itself for instruction generation, as well as for `asm' + statements; therefore, some of the constraints are not particularly + interesting for `asm'. The constraints are defined through these + macros: + + `REG_CLASS_FROM_LETTER' + Register class constraints (usually lower case). + + `CONST_OK_FOR_LETTER_P' + Immediate constant constraints, for non-floating point constants of + word size or smaller precision (usually upper case). + + `CONST_DOUBLE_OK_FOR_LETTER_P' + Immediate constant constraints, for all floating point constants + and for constants of greater than word size precision (usually + upper case). + + `EXTRA_CONSTRAINT' + Special cases of registers or memory. This macro is not required, + and is only defined for some machines. + + Inspecting these macro definitions in the compiler source for your + machine is the best way to be certain you have the right constraints. + However, here is a summary of the machine-dependent constraints + available on some particular machines. + + _ARM family--`arm.h'_ + + `f' + Floating-point register + + `F' + One of the floating-point constants 0.0, 0.5, 1.0, 2.0, 3.0, + 4.0, 5.0 or 10.0 + + `G' + Floating-point constant that would satisfy the constraint `F' + if it were negated + + `I' + Integer that is valid as an immediate operand in a data + processing instruction. That is, an integer in the range 0 + to 255 rotated by a multiple of 2 + + `J' + Integer in the range -4095 to 4095 + + `K' + Integer that satisfies constraint `I' when inverted (ones + complement) + + `L' + Integer that satisfies constraint `I' when negated (twos + complement) + + `M' + Integer in the range 0 to 32 + + `Q' + A memory reference where the exact address is in a single + register (``m'' is preferable for `asm' statements) + + `R' + An item in the constant pool + + `S' + A symbol in the text segment of the current file + + _AMD 29000 family--`a29k.h'_ + + `l' + Local register 0 + + `b' + Byte Pointer (`BP') register + + `q' + `Q' register + + `h' + Special purpose register + + `A' + First accumulator register + + `a' + Other accumulator register + + `f' + Floating point register + + `I' + Constant greater than 0, less than 0x100 + + `J' + Constant greater than 0, less than 0x10000 + + `K' + Constant whose high 24 bits are on (1) + + `L' + 16-bit constant whose high 8 bits are on (1) + + `M' + 32-bit constant whose high 16 bits are on (1) + + `N' + 32-bit negative constant that fits in 8 bits + + `O' + The constant 0x80000000 or, on the 29050, any 32-bit constant + whose low 16 bits are 0. + + `P' + 16-bit negative constant that fits in 8 bits + + `G' + `H' + A floating point constant (in `asm' statements, use the + machine independent `E' or `F' instead) + + _AVR family--`avr.h'_ + + `l' + Registers from r0 to r15 + + `a' + Registers from r16 to r23 + + `d' + Registers from r16 to r31 + + `w' + Registers from r24 to r31. These registers can be used in + `adiw' command + + `e' + Pointer register (r26-r31) + + `b' + Base pointer register (r28-r31) + + `q' + Stack pointer register (SPH:SPL) + + `t' + Temporary register r0 + + `x' + Register pair X (r27:r26) + + `y' + Register pair Y (r29:r28) + + `z' + Register pair Z (r31:r30) + + `I' + Constant greater than -1, less than 64 + + `J' + Constant greater than -64, less than 1 + + `K' + Constant integer 2 + + `L' + Constant integer 0 + + `M' + Constant that fits in 8 bits + + `N' + Constant integer -1 + + `O' + Constant integer 8, 16, or 24 + + `P' + Constant integer 1 + + `G' + A floating point constant 0.0 + + _IBM RS6000--`rs6000.h'_ + + `b' + Address base register + + `f' + Floating point register + + `h' + `MQ', `CTR', or `LINK' register + + `q' + `MQ' register + + `c' + `CTR' register + + `l' + `LINK' register + + `x' + `CR' register (condition register) number 0 + + `y' + `CR' register (condition register) + + `z' + `FPMEM' stack memory for FPR-GPR transfers + + `I' + Signed 16-bit constant + + `J' + Unsigned 16-bit constant shifted left 16 bits (use `L' + instead for `SImode' constants) + + `K' + Unsigned 16-bit constant + + `L' + Signed 16-bit constant shifted left 16 bits + + `M' + Constant larger than 31 + + `N' + Exact power of 2 + + `O' + Zero + + `P' + Constant whose negation is a signed 16-bit constant + + `G' + Floating point constant that can be loaded into a register + with one instruction per word + + `Q' + Memory operand that is an offset from a register (`m' is + preferable for `asm' statements) + + `R' + AIX TOC entry + + `S' + Constant suitable as a 64-bit mask operand + + `T' + Constant suitable as a 32-bit mask operand + + `U' + System V Release 4 small data area reference + + _Intel 386--`i386.h'_ + + `q' + `a', `b', `c', or `d' register for the i386. For x86-64 it + is equivalent to `r' class. (for 8-bit instructions that do + not use upper halves) + + `Q' + `a', `b', `c', or `d' register. (for 8-bit instructions, that + do use upper halves) + + `R' + Legacy register--equivalent to `r' class in i386 mode. (for + non-8-bit registers used together with 8-bit upper halves in + a single instruction) + + `A' + Specifies the `a' or `d' registers. This is primarily useful + for 64-bit integer values (when in 32-bit mode) intended to + be returned with the `d' register holding the most + significant bits and the `a' register holding the least + significant bits. + + `f' + Floating point register + + `t' + First (top of stack) floating point register + + `u' + Second floating point register + + `a' + `a' register + + `b' + `b' register + + `c' + `c' register + + `d' + `d' register + + `D' + `di' register + + `S' + `si' register + + `x' + `xmm' SSE register + + `y' + MMX register + + `I' + Constant in range 0 to 31 (for 32-bit shifts) + + `J' + Constant in range 0 to 63 (for 64-bit shifts) + + `K' + `0xff' + + `L' + `0xffff' + + `M' + 0, 1, 2, or 3 (shifts for `lea' instruction) + + `N' + Constant in range 0 to 255 (for `out' instruction) + + `Z' + Constant in range 0 to `0xffffffff' or symbolic reference + known to fit specified range. (for using immediates in zero + extending 32-bit to 64-bit x86-64 instructions) + + `e' + Constant in range -2147483648 to 2147483647 or symbolic + reference known to fit specified range. (for using + immediates in 64-bit x86-64 instructions) + + `G' + Standard 80387 floating point constant + + _Intel 960--`i960.h'_ + + `f' + Floating point register (`fp0' to `fp3') + + `l' + Local register (`r0' to `r15') + + `b' + Global register (`g0' to `g15') + + `d' + Any local or global register + + `I' + Integers from 0 to 31 + + `J' + 0 + + `K' + Integers from -31 to 0 + + `G' + Floating point 0 + + `H' + Floating point 1 + + _MIPS--`mips.h'_ + + `d' + General-purpose integer register + + `f' + Floating-point register (if available) + + `h' + `Hi' register + + `l' + `Lo' register + + `x' + `Hi' or `Lo' register + + `y' + General-purpose integer register + + `z' + Floating-point status register + + `I' + Signed 16-bit constant (for arithmetic instructions) + + `J' + Zero + + `K' + Zero-extended 16-bit constant (for logic instructions) + + `L' + Constant with low 16 bits zero (can be loaded with `lui') + + `M' + 32-bit constant which requires two instructions to load (a + constant which is not `I', `K', or `L') + + `N' + Negative 16-bit constant + + `O' + Exact power of two + + `P' + Positive 16-bit constant + + `G' + Floating point zero + + `Q' + Memory reference that can be loaded with more than one + instruction (`m' is preferable for `asm' statements) + + `R' + Memory reference that can be loaded with one instruction (`m' + is preferable for `asm' statements) + + `S' + Memory reference in external OSF/rose PIC format (`m' is + preferable for `asm' statements) + + _Motorola 680x0--`m68k.h'_ + + `a' + Address register + + `d' + Data register + + `f' + 68881 floating-point register, if available + + `x' + Sun FPA (floating-point) register, if available + + `y' + First 16 Sun FPA registers, if available + + `I' + Integer in the range 1 to 8 + + `J' + 16-bit signed number + + `K' + Signed number whose magnitude is greater than 0x80 + + `L' + Integer in the range -8 to -1 + + `M' + Signed number whose magnitude is greater than 0x100 + + `G' + Floating point constant that is not a 68881 constant + + `H' + Floating point constant that can be used by Sun FPA + + _Motorola 68HC11 & 68HC12 families--`m68hc11.h'_ + + `a' + Register 'a' + + `b' + Register 'b' + + `d' + Register 'd' + + `q' + An 8-bit register + + `t' + Temporary soft register _.tmp + + `u' + A soft register _.d1 to _.d31 + + `w' + Stack pointer register + + `x' + Register 'x' + + `y' + Register 'y' + + `z' + Pseudo register 'z' (replaced by 'x' or 'y' at the end) + + `A' + An address register: x, y or z + + `B' + An address register: x or y + + `D' + Register pair (x:d) to form a 32-bit value + + `L' + Constants in the range -65536 to 65535 + + `M' + Constants whose 16-bit low part is zero + + `N' + Constant integer 1 or -1 + + `O' + Constant integer 16 + + `P' + Constants in the range -8 to 2 + + + _SPARC--`sparc.h'_ + + `f' + Floating-point register that can hold 32- or 64-bit values. + + `e' + Floating-point register that can hold 64- or 128-bit values. + + `I' + Signed 13-bit constant + + `J' + Zero + + `K' + 32-bit constant with the low 12 bits clear (a constant that + can be loaded with the `sethi' instruction) + + `L' + A constant in the range supported by `movcc' instructions + + `M' + A constant in the range supported by `movrcc' instructions + + `N' + Same as `K', except that it verifies that bits that are not + in the lower 32-bit range are all zero. Must be used instead + of `K' for modes wider than `SImode' + + `G' + Floating-point zero + + `H' + Signed 13-bit constant, sign-extended to 32 or 64 bits + + `Q' + Floating-point constant whose integral representation can be + moved into an integer register using a single sethi + instruction + + `R' + Floating-point constant whose integral representation can be + moved into an integer register using a single mov instruction + + `S' + Floating-point constant whose integral representation can be + moved into an integer register using a high/lo_sum + instruction sequence + + `T' + Memory address aligned to an 8-byte boundary + + `U' + Even register + + `W' + Memory address for `e' constraint registers. + + + _TMS320C3x/C4x--`c4x.h'_ + + `a' + Auxiliary (address) register (ar0-ar7) + + `b' + Stack pointer register (sp) + + `c' + Standard (32-bit) precision integer register + + `f' + Extended (40-bit) precision register (r0-r11) + + `k' + Block count register (bk) + + `q' + Extended (40-bit) precision low register (r0-r7) + + `t' + Extended (40-bit) precision register (r0-r1) + + `u' + Extended (40-bit) precision register (r2-r3) + + `v' + Repeat count register (rc) + + `x' + Index register (ir0-ir1) + + `y' + Status (condition code) register (st) + + `z' + Data page register (dp) + + `G' + Floating-point zero + + `H' + Immediate 16-bit floating-point constant + + `I' + Signed 16-bit constant + + `J' + Signed 8-bit constant + + `K' + Signed 5-bit constant + + `L' + Unsigned 16-bit constant + + `M' + Unsigned 8-bit constant + + `N' + Ones complement of unsigned 16-bit constant + + `O' + High 16-bit constant (32-bit constant with 16 LSBs zero) + + `Q' + Indirect memory reference with signed 8-bit or index register + displacement + + `R' + Indirect memory reference with unsigned 5-bit displacement + + `S' + Indirect memory reference with 1 bit or index register + displacement + + `T' + Direct memory reference + + `U' + Symbolic address + + + _S/390 and zSeries--`s390.h'_ + + `a' + Address register (general purpose register except r0) + + `d' + Data register (arbitrary general purpose register) + + `f' + Floating-point register + + `I' + Unsigned 8-bit constant (0-255) + + `J' + Unsigned 12-bit constant (0-4095) + + `K' + Signed 16-bit constant (-32768-32767) + + `L' + Unsigned 16-bit constant (0-65535) + + `Q' + Memory reference without index register + + `S' + Symbolic constant suitable for use with the `larl' instruction + + + _Xstormy16--`stormy16.h'_ + + `a' + Register r0. + + `b' + Register r1. + + `c' + Register r2. + + `d' + Register r8. + + `e' + Registers r0 through r7. + + `t' + Registers r0 and r1. + + `y' + The carry register. + + `z' + Registers r8 and r9. + + `I' + A constant between 0 and 3 inclusive. + + `J' + A constant that has exactly one bit set. + + `K' + A constant that has exactly one bit clear. + + `L' + A constant between 0 and 255 inclusive. + + `M' + A constant between -255 and 0 inclusive. + + `N' + A constant between -3 and 0 inclusive. + + `O' + A constant between 1 and 4 inclusive. + + `P' + A constant between -4 and -1 inclusive. + + `Q' + A memory reference that is a stack push. + + `R' + A memory reference that is a stack pop. + + `S' + A memory reference that refers to an constant address of + known value. + + `T' + The register indicated by Rx (not implemented yet). + + `U' + A constant that is not between 2 and 15 inclusive. + + + _Xtensa--`xtensa.h'_ + + `a' + General-purpose 32-bit register + + `b' + One-bit boolean register + + `A' + MAC16 40-bit accumulator register + + `I' + Signed 12-bit integer constant, for use in MOVI instructions + + `J' + Signed 8-bit integer constant, for use in ADDI instructions + + `K' + Integer constant valid for BccI instructions + + `L' + Unsigned constant valid for BccUI instructions + + + +  + File: gcc.info, Node: Asm Labels, Next: Explicit Reg Vars, Prev: Constraints, Up: C Extensions + + Controlling Names Used in Assembler Code + ======================================== + + You can specify the name to be used in the assembler code for a C + function or variable by writing the `asm' (or `__asm__') keyword after + the declarator as follows: + + int foo asm ("myfoo") = 2; + + This specifies that the name to be used for the variable `foo' in the + assembler code should be `myfoo' rather than the usual `_foo'. + + On systems where an underscore is normally prepended to the name of + a C function or variable, this feature allows you to define names for + the linker that do not start with an underscore. + + It does not make sense to use this feature with a non-static local + variable since such variables do not have assembler names. If you are + trying to put the variable in a particular register, see *Note Explicit + Reg Vars::. GCC presently accepts such code with a warning, but will + probably be changed to issue an error, rather than a warning, in the + future. + + You cannot use `asm' in this way in a function _definition_; but you + can get the same effect by writing a declaration for the function + before its definition and putting `asm' there, like this: + + extern func () asm ("FUNC"); + + func (x, y) + int x, y; + ... + + It is up to you to make sure that the assembler names you choose do + not conflict with any other assembler symbols. Also, you must not use a + register name; that would produce completely invalid assembler code. + GCC does not as yet have the ability to store static variables in + registers. Perhaps that will be added. + +  + File: gcc.info, Node: Explicit Reg Vars, Next: Alternate Keywords, Prev: Asm Labels, Up: C Extensions + + Variables in Specified Registers + ================================ + + GNU C allows you to put a few global variables into specified + hardware registers. You can also specify the register in which an + ordinary register variable should be allocated. + + * Global register variables reserve registers throughout the program. + This may be useful in programs such as programming language + interpreters which have a couple of global variables that are + accessed very often. + + * Local register variables in specific registers do not reserve the + registers. The compiler's data flow analysis is capable of + determining where the specified registers contain live values, and + where they are available for other uses. Stores into local + register variables may be deleted when they appear to be dead + according to dataflow analysis. References to local register + variables may be deleted or moved or simplified. + + These local variables are sometimes convenient for use with the + extended `asm' feature (*note Extended Asm::), if you want to + write one output of the assembler instruction directly into a + particular register. (This will work provided the register you + specify fits the constraints specified for that operand in the + `asm'.) + + * Menu: + + * Global Reg Vars:: + * Local Reg Vars:: + +  + File: gcc.info, Node: Global Reg Vars, Next: Local Reg Vars, Up: Explicit Reg Vars + + Defining Global Register Variables + ---------------------------------- + + You can define a global register variable in GNU C like this: + + register int *foo asm ("a5"); + + Here `a5' is the name of the register which should be used. Choose a + register which is normally saved and restored by function calls on your + machine, so that library routines will not clobber it. + + Naturally the register name is cpu-dependent, so you would need to + conditionalize your program according to cpu type. The register `a5' + would be a good choice on a 68000 for a variable of pointer type. On + machines with register windows, be sure to choose a "global" register + that is not affected magically by the function call mechanism. + + In addition, operating systems on one type of cpu may differ in how + they name the registers; then you would need additional conditionals. + For example, some 68000 operating systems call this register `%a5'. + + Eventually there may be a way of asking the compiler to choose a + register automatically, but first we need to figure out how it should + choose and how to enable you to guide the choice. No solution is + evident. + + Defining a global register variable in a certain register reserves + that register entirely for this use, at least within the current + compilation. The register will not be allocated for any other purpose + in the functions in the current compilation. The register will not be + saved and restored by these functions. Stores into this register are + never deleted even if they would appear to be dead, but references may + be deleted or moved or simplified. + + It is not safe to access the global register variables from signal + handlers, or from more than one thread of control, because the system + library routines may temporarily use the register for other things + (unless you recompile them specially for the task at hand). + + It is not safe for one function that uses a global register variable + to call another such function `foo' by way of a third function `lose' + that was compiled without knowledge of this variable (i.e. in a + different source file in which the variable wasn't declared). This is + because `lose' might save the register and put some other value there. + For example, you can't expect a global register variable to be + available in the comparison-function that you pass to `qsort', since + `qsort' might have put something else in that register. (If you are + prepared to recompile `qsort' with the same global register variable, + you can solve this problem.) + + If you want to recompile `qsort' or other source files which do not + actually use your global register variable, so that they will not use + that register for any other purpose, then it suffices to specify the + compiler option `-ffixed-REG'. You need not actually add a global + register declaration to their source code. + + A function which can alter the value of a global register variable + cannot safely be called from a function compiled without this variable, + because it could clobber the value the caller expects to find there on + return. Therefore, the function which is the entry point into the part + of the program that uses the global register variable must explicitly + save and restore the value which belongs to its caller. + + On most machines, `longjmp' will restore to each global register + variable the value it had at the time of the `setjmp'. On some + machines, however, `longjmp' will not change the value of global + register variables. To be portable, the function that called `setjmp' + should make other arrangements to save the values of the global register + variables, and to restore them in a `longjmp'. This way, the same + thing will happen regardless of what `longjmp' does. + + All global register variable declarations must precede all function + definitions. If such a declaration could appear after function + definitions, the declaration would be too late to prevent the register + from being used for other purposes in the preceding functions. + + Global register variables may not have initial values, because an + executable file has no means to supply initial contents for a register. + + On the Sparc, there are reports that g3 ... g7 are suitable + registers, but certain library functions, such as `getwd', as well as + the subroutines for division and remainder, modify g3 and g4. g1 and + g2 are local temporaries. + + On the 68000, a2 ... a5 should be suitable, as should d2 ... d7. Of + course, it will not do to use more than a few of those. + +  + File: gcc.info, Node: Local Reg Vars, Prev: Global Reg Vars, Up: Explicit Reg Vars + + Specifying Registers for Local Variables + ---------------------------------------- + + You can define a local register variable with a specified register + like this: + + register int *foo asm ("a5"); + + Here `a5' is the name of the register which should be used. Note that + this is the same syntax used for defining global register variables, + but for a local variable it would appear within a function. + + Naturally the register name is cpu-dependent, but this is not a + problem, since specific registers are most often useful with explicit + assembler instructions (*note Extended Asm::). Both of these things + generally require that you conditionalize your program according to cpu + type. + + In addition, operating systems on one type of cpu may differ in how + they name the registers; then you would need additional conditionals. + For example, some 68000 operating systems call this register `%a5'. + + Defining such a register variable does not reserve the register; it + remains available for other uses in places where flow control determines + the variable's value is not live. However, these registers are made + unavailable for use in the reload pass; excessive use of this feature + leaves the compiler too few available registers to compile certain + functions. + + This option does not guarantee that GCC will generate code that has + this variable in the register you specify at all times. You may not + code an explicit reference to this register in an `asm' statement and + assume it will always refer to this variable. + + Stores into local register variables may be deleted when they appear + to be dead according to dataflow analysis. References to local + register variables may be deleted or moved or simplified. + +  + File: gcc.info, Node: Alternate Keywords, Next: Incomplete Enums, Prev: Explicit Reg Vars, Up: C Extensions + + Alternate Keywords + ================== + + The option `-traditional' disables certain keywords; `-ansi' and the + various `-std' options disable certain others. This causes trouble + when you want to use GNU C extensions, or ISO C features, in a + general-purpose header file that should be usable by all programs, + including ISO C programs and traditional ones. The keywords `asm', + `typeof' and `inline' cannot be used since they won't work in a program + compiled with `-ansi' (although `inline' can be used in a program + compiled with `-std=c99'), while the keywords `const', `volatile', + `signed', `typeof' and `inline' won't work in a program compiled with + `-traditional'. The ISO C99 keyword `restrict' is only available when + `-std=gnu99' (which will eventually be the default) or `-std=c99' (or + the equivalent `-std=iso9899:1999') is used. + + The way to solve these problems is to put `__' at the beginning and + end of each problematical keyword. For example, use `__asm__' instead + of `asm', `__const__' instead of `const', and `__inline__' instead of + `inline'. + + Other C compilers won't accept these alternative keywords; if you + want to compile with another compiler, you can define the alternate + keywords as macros to replace them with the customary keywords. It + looks like this: + + #ifndef __GNUC__ + #define __asm__ asm + #endif + + `-pedantic' and other options cause warnings for many GNU C + extensions. You can prevent such warnings within one expression by + writing `__extension__' before the expression. `__extension__' has no + effect aside from this. + +  + File: gcc.info, Node: Incomplete Enums, Next: Function Names, Prev: Alternate Keywords, Up: C Extensions + + Incomplete `enum' Types + ======================= + + You can define an `enum' tag without specifying its possible values. + This results in an incomplete type, much like what you get if you write + `struct foo' without describing the elements. A later declaration + which does specify the possible values completes the type. + + You can't allocate variables or storage using the type while it is + incomplete. However, you can work with pointers to that type. + + This extension may not be very useful, but it makes the handling of + `enum' more consistent with the way `struct' and `union' are handled. + + This extension is not supported by GNU C++. + +  + File: gcc.info, Node: Function Names, Next: Return Address, Prev: Incomplete Enums, Up: C Extensions + + Function Names as Strings + ========================= + + GCC predefines two magic identifiers to hold the name of the current + function. The identifier `__FUNCTION__' holds the name of the function + as it appears in the source. The identifier `__PRETTY_FUNCTION__' + holds the name of the function pretty printed in a language specific + fashion. + + These names are always the same in a C function, but in a C++ + function they may be different. For example, this program: + + extern "C" { + extern int printf (char *, ...); + } + + class a { + public: + sub (int i) + { + printf ("__FUNCTION__ = %s\n", __FUNCTION__); + printf ("__PRETTY_FUNCTION__ = %s\n", __PRETTY_FUNCTION__); + } + }; + + int + main (void) + { + a ax; + ax.sub (0); + return 0; + } + + gives this output: + + __FUNCTION__ = sub + __PRETTY_FUNCTION__ = int a::sub (int) + + The compiler automagically replaces the identifiers with a string + literal containing the appropriate name. Thus, they are neither + preprocessor macros, like `__FILE__' and `__LINE__', nor variables. + This means that they catenate with other string literals, and that they + can be used to initialize char arrays. For example + + char here[] = "Function " __FUNCTION__ " in " __FILE__; + + On the other hand, `#ifdef __FUNCTION__' does not have any special + meaning inside a function, since the preprocessor does not do anything + special with the identifier `__FUNCTION__'. + + Note that these semantics are deprecated, and that GCC 3.2 will + handle `__FUNCTION__' and `__PRETTY_FUNCTION__' the same way as + `__func__'. `__func__' is defined by the ISO standard C99: + + The identifier `__func__' is implicitly declared by the translator + as if, immediately following the opening brace of each function + definition, the declaration + static const char __func__[] = "function-name"; + + appeared, where function-name is the name of the lexically-enclosing + function. This name is the unadorned name of the function. + + By this definition, `__func__' is a variable, not a string literal. + In particular, `__func__' does not catenate with other string literals. + + In `C++', `__FUNCTION__' and `__PRETTY_FUNCTION__' are variables, + declared in the same way as `__func__'. + +  + File: gcc.info, Node: Return Address, Next: Vector Extensions, Prev: Function Names, Up: C Extensions + + Getting the Return or Frame Address of a Function + ================================================= + + These functions may be used to get information about the callers of a + function. + + - Built-in Function: void * __builtin_return_address (unsigned int + LEVEL) + This function returns the return address of the current function, + or of one of its callers. The LEVEL argument is number of frames + to scan up the call stack. A value of `0' yields the return + address of the current function, a value of `1' yields the return + address of the caller of the current function, and so forth. + + The LEVEL argument must be a constant integer. + + On some machines it may be impossible to determine the return + address of any function other than the current one; in such cases, + or when the top of the stack has been reached, this function will + return `0' or a random value. In addition, + `__builtin_frame_address' may be used to determine if the top of + the stack has been reached. + + This function should only be used with a nonzero argument for + debugging purposes. + + - Built-in Function: void * __builtin_frame_address (unsigned int + LEVEL) + This function is similar to `__builtin_return_address', but it + returns the address of the function frame rather than the return + address of the function. Calling `__builtin_frame_address' with a + value of `0' yields the frame address of the current function, a + value of `1' yields the frame address of the caller of the current + function, and so forth. + + The frame is the area on the stack which holds local variables and + saved registers. The frame address is normally the address of the + first word pushed on to the stack by the function. However, the + exact definition depends upon the processor and the calling + convention. If the processor has a dedicated frame pointer + register, and the function has a frame, then + `__builtin_frame_address' will return the value of the frame + pointer register. + + On some machines it may be impossible to determine the frame + address of any function other than the current one; in such cases, + or when the top of the stack has been reached, this function will + return `0' if the first frame pointer is properly initialized by + the startup code. + + This function should only be used with a nonzero argument for + debugging purposes. + +  + File: gcc.info, Node: Vector Extensions, Next: Other Builtins, Prev: Return Address, Up: C Extensions + + Using vector instructions through built-in functions + ==================================================== + + On some targets, the instruction set contains SIMD vector + instructions that operate on multiple values contained in one large + register at the same time. For example, on the i386 the MMX, 3Dnow! + and SSE extensions can be used this way. + + The first step in using these extensions is to provide the necessary + data types. This should be done using an appropriate `typedef': + + typedef int v4si __attribute__ ((mode(V4SI))); + + The base type `int' is effectively ignored by the compiler, the + actual properties of the new type `v4si' are defined by the + `__attribute__'. It defines the machine mode to be used; for vector + types these have the form `VNB'; N should be the number of elements in + the vector, and B should be the base mode of the individual elements. + The following can be used as base modes: + + `QI' + An integer that is as wide as the smallest addressable unit, + usually 8 bits. + + `HI' + An integer, twice as wide as a QI mode integer, usually 16 bits. + + `SI' + An integer, four times as wide as a QI mode integer, usually 32 + bits. + + `DI' + An integer, eight times as wide as a QI mode integer, usually 64 + bits. + + `SF' + A floating point value, as wide as a SI mode integer, usually 32 + bits. + + `DF' + A floating point value, as wide as a DI mode integer, usually 64 + bits. + + Not all base types or combinations are always valid; which modes can + be used is determined by the target machine. For example, if + targetting the i386 MMX extensions, only `V8QI', `V4HI' and `V2SI' are + allowed modes. + + There are no `V1xx' vector modes - they would be identical to the + corresponding base mode. + + There is no distinction between signed and unsigned vector modes. + This distinction is made by the operations that perform on the vectors, + not by the data type. + + The types defined in this manner are somewhat special, they cannot be + used with most normal C operations (i.e., a vector addition can _not_ + be represented by a normal addition of two vector type variables). You + can declare only variables and use them in function calls and returns, + as well as in assignments and some casts. It is possible to cast from + one vector type to another, provided they are of the same size (in + fact, you can also cast vectors to and from other datatypes of the same + size). + + A port that supports vector operations provides a set of built-in + functions that can be used to operate on vectors. For example, a + function to add two vectors and multiply the result by a third could + look like this: + + v4si f (v4si a, v4si b, v4si c) + { + v4si tmp = __builtin_addv4si (a, b); + return __builtin_mulv4si (tmp, c); + } + +  + File: gcc.info, Node: Other Builtins, Next: Target Builtins, Prev: Vector Extensions, Up: C Extensions + + Other built-in functions provided by GCC + ======================================== + + GCC provides a large number of built-in functions other than the ones + mentioned above. Some of these are for internal use in the processing + of exceptions or variable-length argument lists and will not be + documented here because they may change from time to time; we do not + recommend general use of these functions. + + The remaining functions are provided for optimization purposes. + + GCC includes built-in versions of many of the functions in the + standard C library. The versions prefixed with `__builtin_' will + always be treated as having the same meaning as the C library function + even if you specify the `-fno-builtin' option. (*note C Dialect + Options::) Many of these functions are only optimized in certain cases; + if they are not optimized in a particular case, a call to the library + function will be emitted. + + The functions `abort', `exit', `_Exit' and `_exit' are recognized + and presumed not to return, but otherwise are not built in. `_exit' is + not recognized in strict ISO C mode (`-ansi', `-std=c89' or + `-std=c99'). `_Exit' is not recognized in strict C89 mode (`-ansi' or + `-std=c89'). + + Outside strict ISO C mode, the functions `alloca', `bcmp', `bzero', + `index', `rindex', `ffs', `fputs_unlocked', `printf_unlocked' and + `fprintf_unlocked' may be handled as built-in functions. All these + functions have corresponding versions prefixed with `__builtin_', which + may be used even in strict C89 mode. + + The ISO C99 functions `conj', `conjf', `conjl', `creal', `crealf', + `creall', `cimag', `cimagf', `cimagl', `llabs' and `imaxabs' are + handled as built-in functions except in strict ISO C89 mode. There are + also built-in versions of the ISO C99 functions `cosf', `cosl', + `fabsf', `fabsl', `sinf', `sinl', `sqrtf', and `sqrtl', that are + recognized in any mode since ISO C89 reserves these names for the + purpose to which ISO C99 puts them. All these functions have + corresponding versions prefixed with `__builtin_'. + + The ISO C89 functions `abs', `cos', `fabs', `fprintf', `fputs', + `labs', `memcmp', `memcpy', `memset', `printf', `sin', `sqrt', `strcat', + `strchr', `strcmp', `strcpy', `strcspn', `strlen', `strncat', + `strncmp', `strncpy', `strpbrk', `strrchr', `strspn', and `strstr' are + all recognized as built-in functions unless `-fno-builtin' is specified + (or `-fno-builtin-FUNCTION' is specified for an individual function). + All of these functions have corresponding versions prefixed with + `__builtin_'. + + GCC provides built-in versions of the ISO C99 floating point + comparison macros that avoid raising exceptions for unordered operands. + They have the same names as the standard macros ( `isgreater', + `isgreaterequal', `isless', `islessequal', `islessgreater', and + `isunordered') , with `__builtin_' prefixed. We intend for a library + implementor to be able to simply `#define' each standard macro to its + built-in equivalent. + + - Built-in Function: int __builtin_types_compatible_p (TYPE1, TYPE2) + You can use the built-in function `__builtin_types_compatible_p' to + determine whether two types are the same. + + This built-in function returns 1 if the unqualified versions of the + types TYPE1 and TYPE2 (which are types, not expressions) are + compatible, 0 otherwise. The result of this built-in function can + be used in integer constant expressions. + + This built-in function ignores top level qualifiers (e.g., `const', + `volatile'). For example, `int' is equivalent to `const int'. + + The type `int[]' and `int[5]' are compatible. On the other hand, + `int' and `char *' are not compatible, even if the size of their + types, on the particular architecture are the same. Also, the + amount of pointer indirection is taken into account when + determining similarity. Consequently, `short *' is not similar to + `short **'. Furthermore, two types that are typedefed are + considered compatible if their underlying types are compatible. + + An `enum' type is considered to be compatible with another `enum' + type. For example, `enum {foo, bar}' is similar to `enum {hot, + dog}'. + + You would typically use this function in code whose execution + varies depending on the arguments' types. For example: + + #define foo(x) \ + ({ \ + typeof (x) tmp; \ + if (__builtin_types_compatible_p (typeof (x), long double)) \ + tmp = foo_long_double (tmp); \ + else if (__builtin_types_compatible_p (typeof (x), double)) \ + tmp = foo_double (tmp); \ + else if (__builtin_types_compatible_p (typeof (x), float)) \ + tmp = foo_float (tmp); \ + else \ + abort (); \ + tmp; \ + }) + + _Note:_ This construct is only available for C. + + + - Built-in Function: TYPE __builtin_choose_expr (CONST_EXP, EXP1, EXP2) + You can use the built-in function `__builtin_choose_expr' to + evaluate code depending on the value of a constant expression. + This built-in function returns EXP1 if CONST_EXP, which is a + constant expression that must be able to be determined at compile + time, is nonzero. Otherwise it returns 0. + + This built-in function is analogous to the `? :' operator in C, + except that the expression returned has its type unaltered by + promotion rules. Also, the built-in function does not evaluate + the expression that was not chosen. For example, if CONST_EXP + evaluates to true, EXP2 is not evaluated even if it has + side-effects. + + This built-in function can return an lvalue if the chosen argument + is an lvalue. + + If EXP1 is returned, the return type is the same as EXP1's type. + Similarly, if EXP2 is returned, its return type is the same as + EXP2. + + Example: + + #define foo(x) \ + __builtin_choose_expr (__builtin_types_compatible_p (typeof (x), double), \ + foo_double (x), \ + __builtin_choose_expr (__builtin_types_compatible_p (typeof (x), float), \ + foo_float (x), \ + /* The void expression results in a compile-time error \ + when assigning the result to something. */ \ + (void)0)) + + _Note:_ This construct is only available for C. Furthermore, the + unused expression (EXP1 or EXP2 depending on the value of + CONST_EXP) may still generate syntax errors. This may change in + future revisions. + + + - Built-in Function: int __builtin_constant_p (EXP) + You can use the built-in function `__builtin_constant_p' to + determine if a value is known to be constant at compile-time and + hence that GCC can perform constant-folding on expressions + involving that value. The argument of the function is the value + to test. The function returns the integer 1 if the argument is + known to be a compile-time constant and 0 if it is not known to be + a compile-time constant. A return of 0 does not indicate that the + value is _not_ a constant, but merely that GCC cannot prove it is + a constant with the specified value of the `-O' option. + + You would typically use this function in an embedded application + where memory was a critical resource. If you have some complex + calculation, you may want it to be folded if it involves + constants, but need to call a function if it does not. For + example: + + #define Scale_Value(X) \ + (__builtin_constant_p (X) \ + ? ((X) * SCALE + OFFSET) : Scale (X)) + + You may use this built-in function in either a macro or an inline + function. However, if you use it in an inlined function and pass + an argument of the function as the argument to the built-in, GCC + will never return 1 when you call the inline function with a + string constant or compound literal (*note Compound Literals::) + and will not return 1 when you pass a constant numeric value to + the inline function unless you specify the `-O' option. + + You may also use `__builtin_constant_p' in initializers for static + data. For instance, you can write + + static const int table[] = { + __builtin_constant_p (EXPRESSION) ? (EXPRESSION) : -1, + /* ... */ + }; + + This is an acceptable initializer even if EXPRESSION is not a + constant expression. GCC must be more conservative about + evaluating the built-in in this case, because it has no + opportunity to perform optimization. + + Previous versions of GCC did not accept this built-in in data + initializers. The earliest version where it is completely safe is + 3.0.1. + + - Built-in Function: long __builtin_expect (long EXP, long C) + You may use `__builtin_expect' to provide the compiler with branch + prediction information. In general, you should prefer to use + actual profile feedback for this (`-fprofile-arcs'), as + programmers are notoriously bad at predicting how their programs + actually perform. However, there are applications in which this + data is hard to collect. + + The return value is the value of EXP, which should be an integral + expression. The value of C must be a compile-time constant. The + semantics of the built-in are that it is expected that EXP == C. + For example: + + if (__builtin_expect (x, 0)) + foo (); + + would indicate that we do not expect to call `foo', since we + expect `x' to be zero. Since you are limited to integral + expressions for EXP, you should use constructions such as + + if (__builtin_expect (ptr != NULL, 1)) + error (); + + when testing pointer or floating-point values. + + - Built-in Function: void __builtin_prefetch (const void *ADDR, ...) + This function is used to minimize cache-miss latency by moving + data into a cache before it is accessed. You can insert calls to + `__builtin_prefetch' into code for which you know addresses of + data in memory that is likely to be accessed soon. If the target + supports them, data prefetch instructions will be generated. If + the prefetch is done early enough before the access then the data + will be in the cache by the time it is accessed. + + The value of ADDR is the address of the memory to prefetch. There + are two optional arguments, RW and LOCALITY. The value of RW is a + compile-time constant one or zero; one means that the prefetch is + preparing for a write to the memory address and zero, the default, + means that the prefetch is preparing for a read. The value + LOCALITY must be a compile-time constant integer between zero and + three. A value of zero means that the data has no temporal + locality, so it need not be left in the cache after the access. A + value of three means that the data has a high degree of temporal + locality and should be left in all levels of cache possible. + Values of one and two mean, respectively, a low or moderate degree + of temporal locality. The default is three. + + for (i = 0; i < n; i++) + { + a[i] = a[i] + b[i]; + __builtin_prefetch (&a[i+j], 1, 1); + __builtin_prefetch (&b[i+j], 0, 1); + /* ... */ + } + + Data prefetch does not generate faults if ADDR is invalid, but the + address expression itself must be valid. For example, a prefetch + of `p->next' will not fault if `p->next' is not a valid address, + but evaluation will fault if `p' is not a valid address. + + If the target does not support data prefetch, the address + expression is evaluated if it includes side effects but no other + code is generated and GCC does not issue a warning. + +  + File: gcc.info, Node: Target Builtins, Next: Pragmas, Prev: Other Builtins, Up: C Extensions + + Built-in Functions Specific to Particular Target Machines + ========================================================= + + On some target machines, GCC supports many built-in functions + specific to those machines. Generally these generate calls to specific + machine instructions, but allow the compiler to schedule those calls. + + * Menu: + + * X86 Built-in Functions:: + * PowerPC AltiVec Built-in Functions:: + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-15 gcc-3.2.3/gcc/doc/gcc.info-15 *** gcc-3.2.2/gcc/doc/gcc.info-15 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-15 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,261 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: X86 Built-in Functions, Next: PowerPC AltiVec Built-in Functions, Up: Target Builtins + + X86 Built-in Functions + ---------------------- + + These built-in functions are available for the i386 and x86-64 family + of computers, depending on the command-line switches used. + + The following machine modes are available for use with MMX built-in + functions (*note Vector Extensions::): `V2SI' for a vector of two + 32-bit integers, `V4HI' for a vector of four 16-bit integers, and + `V8QI' for a vector of eight 8-bit integers. Some of the built-in + functions operate on MMX registers as a whole 64-bit entity, these use + `DI' as their mode. + + If 3Dnow extensions are enabled, `V2SF' is used as a mode for a + vector of two 32-bit floating point values. + + If SSE extensions are enabled, `V4SF' is used for a vector of four + 32-bit floating point values. Some instructions use a vector of four + 32-bit integers, these use `V4SI'. Finally, some instructions operate + on an entire vector register, interpreting it as a 128-bit integer, + these use mode `TI'. + + The following built-in functions are made available by `-mmmx'. All + of them generate the machine instruction that is part of the name. + + v8qi __builtin_ia32_paddb (v8qi, v8qi) + v4hi __builtin_ia32_paddw (v4hi, v4hi) + v2si __builtin_ia32_paddd (v2si, v2si) + v8qi __builtin_ia32_psubb (v8qi, v8qi) + v4hi __builtin_ia32_psubw (v4hi, v4hi) + v2si __builtin_ia32_psubd (v2si, v2si) + v8qi __builtin_ia32_paddsb (v8qi, v8qi) + v4hi __builtin_ia32_paddsw (v4hi, v4hi) + v8qi __builtin_ia32_psubsb (v8qi, v8qi) + v4hi __builtin_ia32_psubsw (v4hi, v4hi) + v8qi __builtin_ia32_paddusb (v8qi, v8qi) + v4hi __builtin_ia32_paddusw (v4hi, v4hi) + v8qi __builtin_ia32_psubusb (v8qi, v8qi) + v4hi __builtin_ia32_psubusw (v4hi, v4hi) + v4hi __builtin_ia32_pmullw (v4hi, v4hi) + v4hi __builtin_ia32_pmulhw (v4hi, v4hi) + di __builtin_ia32_pand (di, di) + di __builtin_ia32_pandn (di,di) + di __builtin_ia32_por (di, di) + di __builtin_ia32_pxor (di, di) + v8qi __builtin_ia32_pcmpeqb (v8qi, v8qi) + v4hi __builtin_ia32_pcmpeqw (v4hi, v4hi) + v2si __builtin_ia32_pcmpeqd (v2si, v2si) + v8qi __builtin_ia32_pcmpgtb (v8qi, v8qi) + v4hi __builtin_ia32_pcmpgtw (v4hi, v4hi) + v2si __builtin_ia32_pcmpgtd (v2si, v2si) + v8qi __builtin_ia32_punpckhbw (v8qi, v8qi) + v4hi __builtin_ia32_punpckhwd (v4hi, v4hi) + v2si __builtin_ia32_punpckhdq (v2si, v2si) + v8qi __builtin_ia32_punpcklbw (v8qi, v8qi) + v4hi __builtin_ia32_punpcklwd (v4hi, v4hi) + v2si __builtin_ia32_punpckldq (v2si, v2si) + v8qi __builtin_ia32_packsswb (v4hi, v4hi) + v4hi __builtin_ia32_packssdw (v2si, v2si) + v8qi __builtin_ia32_packuswb (v4hi, v4hi) + + The following built-in functions are made available either with + `-msse', or with a combination of `-m3dnow' and `-march=athlon'. All + of them generate the machine instruction that is part of the name. + + v4hi __builtin_ia32_pmulhuw (v4hi, v4hi) + v8qi __builtin_ia32_pavgb (v8qi, v8qi) + v4hi __builtin_ia32_pavgw (v4hi, v4hi) + v4hi __builtin_ia32_psadbw (v8qi, v8qi) + v8qi __builtin_ia32_pmaxub (v8qi, v8qi) + v4hi __builtin_ia32_pmaxsw (v4hi, v4hi) + v8qi __builtin_ia32_pminub (v8qi, v8qi) + v4hi __builtin_ia32_pminsw (v4hi, v4hi) + int __builtin_ia32_pextrw (v4hi, int) + v4hi __builtin_ia32_pinsrw (v4hi, int, int) + int __builtin_ia32_pmovmskb (v8qi) + void __builtin_ia32_maskmovq (v8qi, v8qi, char *) + void __builtin_ia32_movntq (di *, di) + void __builtin_ia32_sfence (void) + + The following built-in functions are available when `-msse' is used. + All of them generate the machine instruction that is part of the name. + + int __builtin_ia32_comieq (v4sf, v4sf) + int __builtin_ia32_comineq (v4sf, v4sf) + int __builtin_ia32_comilt (v4sf, v4sf) + int __builtin_ia32_comile (v4sf, v4sf) + int __builtin_ia32_comigt (v4sf, v4sf) + int __builtin_ia32_comige (v4sf, v4sf) + int __builtin_ia32_ucomieq (v4sf, v4sf) + int __builtin_ia32_ucomineq (v4sf, v4sf) + int __builtin_ia32_ucomilt (v4sf, v4sf) + int __builtin_ia32_ucomile (v4sf, v4sf) + int __builtin_ia32_ucomigt (v4sf, v4sf) + int __builtin_ia32_ucomige (v4sf, v4sf) + v4sf __builtin_ia32_addps (v4sf, v4sf) + v4sf __builtin_ia32_subps (v4sf, v4sf) + v4sf __builtin_ia32_mulps (v4sf, v4sf) + v4sf __builtin_ia32_divps (v4sf, v4sf) + v4sf __builtin_ia32_addss (v4sf, v4sf) + v4sf __builtin_ia32_subss (v4sf, v4sf) + v4sf __builtin_ia32_mulss (v4sf, v4sf) + v4sf __builtin_ia32_divss (v4sf, v4sf) + v4si __builtin_ia32_cmpeqps (v4sf, v4sf) + v4si __builtin_ia32_cmpltps (v4sf, v4sf) + v4si __builtin_ia32_cmpleps (v4sf, v4sf) + v4si __builtin_ia32_cmpgtps (v4sf, v4sf) + v4si __builtin_ia32_cmpgeps (v4sf, v4sf) + v4si __builtin_ia32_cmpunordps (v4sf, v4sf) + v4si __builtin_ia32_cmpneqps (v4sf, v4sf) + v4si __builtin_ia32_cmpnltps (v4sf, v4sf) + v4si __builtin_ia32_cmpnleps (v4sf, v4sf) + v4si __builtin_ia32_cmpngtps (v4sf, v4sf) + v4si __builtin_ia32_cmpngeps (v4sf, v4sf) + v4si __builtin_ia32_cmpordps (v4sf, v4sf) + v4si __builtin_ia32_cmpeqss (v4sf, v4sf) + v4si __builtin_ia32_cmpltss (v4sf, v4sf) + v4si __builtin_ia32_cmpless (v4sf, v4sf) + v4si __builtin_ia32_cmpgtss (v4sf, v4sf) + v4si __builtin_ia32_cmpgess (v4sf, v4sf) + v4si __builtin_ia32_cmpunordss (v4sf, v4sf) + v4si __builtin_ia32_cmpneqss (v4sf, v4sf) + v4si __builtin_ia32_cmpnlts (v4sf, v4sf) + v4si __builtin_ia32_cmpnless (v4sf, v4sf) + v4si __builtin_ia32_cmpngtss (v4sf, v4sf) + v4si __builtin_ia32_cmpngess (v4sf, v4sf) + v4si __builtin_ia32_cmpordss (v4sf, v4sf) + v4sf __builtin_ia32_maxps (v4sf, v4sf) + v4sf __builtin_ia32_maxss (v4sf, v4sf) + v4sf __builtin_ia32_minps (v4sf, v4sf) + v4sf __builtin_ia32_minss (v4sf, v4sf) + v4sf __builtin_ia32_andps (v4sf, v4sf) + v4sf __builtin_ia32_andnps (v4sf, v4sf) + v4sf __builtin_ia32_orps (v4sf, v4sf) + v4sf __builtin_ia32_xorps (v4sf, v4sf) + v4sf __builtin_ia32_movss (v4sf, v4sf) + v4sf __builtin_ia32_movhlps (v4sf, v4sf) + v4sf __builtin_ia32_movlhps (v4sf, v4sf) + v4sf __builtin_ia32_unpckhps (v4sf, v4sf) + v4sf __builtin_ia32_unpcklps (v4sf, v4sf) + v4sf __builtin_ia32_cvtpi2ps (v4sf, v2si) + v4sf __builtin_ia32_cvtsi2ss (v4sf, int) + v2si __builtin_ia32_cvtps2pi (v4sf) + int __builtin_ia32_cvtss2si (v4sf) + v2si __builtin_ia32_cvttps2pi (v4sf) + int __builtin_ia32_cvttss2si (v4sf) + v4sf __builtin_ia32_rcpps (v4sf) + v4sf __builtin_ia32_rsqrtps (v4sf) + v4sf __builtin_ia32_sqrtps (v4sf) + v4sf __builtin_ia32_rcpss (v4sf) + v4sf __builtin_ia32_rsqrtss (v4sf) + v4sf __builtin_ia32_sqrtss (v4sf) + v4sf __builtin_ia32_shufps (v4sf, v4sf, int) + void __builtin_ia32_movntps (float *, v4sf) + int __builtin_ia32_movmskps (v4sf) + + The following built-in functions are available when `-msse' is used. + + `v4sf __builtin_ia32_loadaps (float *)' + Generates the `movaps' machine instruction as a load from memory. + + `void __builtin_ia32_storeaps (float *, v4sf)' + Generates the `movaps' machine instruction as a store to memory. + + `v4sf __builtin_ia32_loadups (float *)' + Generates the `movups' machine instruction as a load from memory. + + `void __builtin_ia32_storeups (float *, v4sf)' + Generates the `movups' machine instruction as a store to memory. + + `v4sf __builtin_ia32_loadsss (float *)' + Generates the `movss' machine instruction as a load from memory. + + `void __builtin_ia32_storess (float *, v4sf)' + Generates the `movss' machine instruction as a store to memory. + + `v4sf __builtin_ia32_loadhps (v4sf, v2si *)' + Generates the `movhps' machine instruction as a load from memory. + + `v4sf __builtin_ia32_loadlps (v4sf, v2si *)' + Generates the `movlps' machine instruction as a load from memory + + `void __builtin_ia32_storehps (v4sf, v2si *)' + Generates the `movhps' machine instruction as a store to memory. + + `void __builtin_ia32_storelps (v4sf, v2si *)' + Generates the `movlps' machine instruction as a store to memory. + + The following built-in functions are available when `-m3dnow' is + used. All of them generate the machine instruction that is part of the + name. + + void __builtin_ia32_femms (void) + v8qi __builtin_ia32_pavgusb (v8qi, v8qi) + v2si __builtin_ia32_pf2id (v2sf) + v2sf __builtin_ia32_pfacc (v2sf, v2sf) + v2sf __builtin_ia32_pfadd (v2sf, v2sf) + v2si __builtin_ia32_pfcmpeq (v2sf, v2sf) + v2si __builtin_ia32_pfcmpge (v2sf, v2sf) + v2si __builtin_ia32_pfcmpgt (v2sf, v2sf) + v2sf __builtin_ia32_pfmax (v2sf, v2sf) + v2sf __builtin_ia32_pfmin (v2sf, v2sf) + v2sf __builtin_ia32_pfmul (v2sf, v2sf) + v2sf __builtin_ia32_pfrcp (v2sf) + v2sf __builtin_ia32_pfrcpit1 (v2sf, v2sf) + v2sf __builtin_ia32_pfrcpit2 (v2sf, v2sf) + v2sf __builtin_ia32_pfrsqrt (v2sf) + v2sf __builtin_ia32_pfrsqrtit1 (v2sf, v2sf) + v2sf __builtin_ia32_pfsub (v2sf, v2sf) + v2sf __builtin_ia32_pfsubr (v2sf, v2sf) + v2sf __builtin_ia32_pi2fd (v2si) + v4hi __builtin_ia32_pmulhrw (v4hi, v4hi) + + The following built-in functions are available when both `-m3dnow' + and `-march=athlon' are used. All of them generate the machine + instruction that is part of the name. + + v2si __builtin_ia32_pf2iw (v2sf) + v2sf __builtin_ia32_pfnacc (v2sf, v2sf) + v2sf __builtin_ia32_pfpnacc (v2sf, v2sf) + v2sf __builtin_ia32_pi2fw (v2si) + v2sf __builtin_ia32_pswapdsf (v2sf) + v2si __builtin_ia32_pswapdsi (v2si) + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-16 gcc-3.2.3/gcc/doc/gcc.info-16 *** gcc-3.2.2/gcc/doc/gcc.info-16 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-16 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1106 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: PowerPC AltiVec Built-in Functions, Prev: X86 Built-in Functions, Up: Target Builtins + + PowerPC AltiVec Built-in Functions + ---------------------------------- + + These built-in functions are available for the PowerPC family of + computers, depending on the command-line switches used. + + The following machine modes are available for use with AltiVec + built-in functions (*note Vector Extensions::): `V4SI' for a vector of + four 32-bit integers, `V4SF' for a vector of four 32-bit floating point + numbers, `V8HI' for a vector of eight 16-bit integers, and `V16QI' for + a vector of sixteen 8-bit integers. + + The following functions are made available by including + `' and using `-maltivec' and `-mabi=altivec'. The functions + implement the functionality described in Motorola's AltiVec Programming + Interface Manual. + + _Note:_ Only the `' interface is supported. Internally, + GCC uses built-in functions to achieve the functionality in the + aforementioned header file, but they are not supported and are subject + to change without notice. + + vector signed char vec_abs (vector signed char, vector signed char); + vector signed short vec_abs (vector signed short, vector signed short); + vector signed int vec_abs (vector signed int, vector signed int); + vector signed float vec_abs (vector signed float, vector signed float); + + vector signed char vec_abss (vector signed char, vector signed char); + vector signed short vec_abss (vector signed short, vector signed short); + + vector signed char vec_add (vector signed char, vector signed char); + vector unsigned char vec_add (vector signed char, vector unsigned char); + + vector unsigned char vec_add (vector unsigned char, vector signed char); + + vector unsigned char vec_add (vector unsigned char, + vector unsigned char); + vector signed short vec_add (vector signed short, vector signed short); + vector unsigned short vec_add (vector signed short, + vector unsigned short); + vector unsigned short vec_add (vector unsigned short, + vector signed short); + vector unsigned short vec_add (vector unsigned short, + vector unsigned short); + vector signed int vec_add (vector signed int, vector signed int); + vector unsigned int vec_add (vector signed int, vector unsigned int); + vector unsigned int vec_add (vector unsigned int, vector signed int); + vector unsigned int vec_add (vector unsigned int, vector unsigned int); + vector float vec_add (vector float, vector float); + + vector unsigned int vec_addc (vector unsigned int, vector unsigned int); + + vector unsigned char vec_adds (vector signed char, + vector unsigned char); + vector unsigned char vec_adds (vector unsigned char, + vector signed char); + vector unsigned char vec_adds (vector unsigned char, + vector unsigned char); + vector signed char vec_adds (vector signed char, vector signed char); + vector unsigned short vec_adds (vector signed short, + vector unsigned short); + vector unsigned short vec_adds (vector unsigned short, + vector signed short); + vector unsigned short vec_adds (vector unsigned short, + vector unsigned short); + vector signed short vec_adds (vector signed short, vector signed short); + + vector unsigned int vec_adds (vector signed int, vector unsigned int); + vector unsigned int vec_adds (vector unsigned int, vector signed int); + vector unsigned int vec_adds (vector unsigned int, vector unsigned int); + + vector signed int vec_adds (vector signed int, vector signed int); + + vector float vec_and (vector float, vector float); + vector float vec_and (vector float, vector signed int); + vector float vec_and (vector signed int, vector float); + vector signed int vec_and (vector signed int, vector signed int); + vector unsigned int vec_and (vector signed int, vector unsigned int); + vector unsigned int vec_and (vector unsigned int, vector signed int); + vector unsigned int vec_and (vector unsigned int, vector unsigned int); + vector signed short vec_and (vector signed short, vector signed short); + vector unsigned short vec_and (vector signed short, + vector unsigned short); + vector unsigned short vec_and (vector unsigned short, + vector signed short); + vector unsigned short vec_and (vector unsigned short, + vector unsigned short); + vector signed char vec_and (vector signed char, vector signed char); + vector unsigned char vec_and (vector signed char, vector unsigned char); + + vector unsigned char vec_and (vector unsigned char, vector signed char); + + vector unsigned char vec_and (vector unsigned char, + vector unsigned char); + + vector float vec_andc (vector float, vector float); + vector float vec_andc (vector float, vector signed int); + vector float vec_andc (vector signed int, vector float); + vector signed int vec_andc (vector signed int, vector signed int); + vector unsigned int vec_andc (vector signed int, vector unsigned int); + vector unsigned int vec_andc (vector unsigned int, vector signed int); + vector unsigned int vec_andc (vector unsigned int, vector unsigned int); + + vector signed short vec_andc (vector signed short, vector signed short); + + vector unsigned short vec_andc (vector signed short, + vector unsigned short); + vector unsigned short vec_andc (vector unsigned short, + vector signed short); + vector unsigned short vec_andc (vector unsigned short, + vector unsigned short); + vector signed char vec_andc (vector signed char, vector signed char); + vector unsigned char vec_andc (vector signed char, + vector unsigned char); + vector unsigned char vec_andc (vector unsigned char, + vector signed char); + vector unsigned char vec_andc (vector unsigned char, + vector unsigned char); + + vector unsigned char vec_avg (vector unsigned char, + vector unsigned char); + vector signed char vec_avg (vector signed char, vector signed char); + vector unsigned short vec_avg (vector unsigned short, + vector unsigned short); + vector signed short vec_avg (vector signed short, vector signed short); + vector unsigned int vec_avg (vector unsigned int, vector unsigned int); + vector signed int vec_avg (vector signed int, vector signed int); + + vector float vec_ceil (vector float); + + vector signed int vec_cmpb (vector float, vector float); + + vector signed char vec_cmpeq (vector signed char, vector signed char); + vector signed char vec_cmpeq (vector unsigned char, + vector unsigned char); + vector signed short vec_cmpeq (vector signed short, + vector signed short); + vector signed short vec_cmpeq (vector unsigned short, + vector unsigned short); + vector signed int vec_cmpeq (vector signed int, vector signed int); + vector signed int vec_cmpeq (vector unsigned int, vector unsigned int); + vector signed int vec_cmpeq (vector float, vector float); + + vector signed int vec_cmpge (vector float, vector float); + + vector signed char vec_cmpgt (vector unsigned char, + vector unsigned char); + vector signed char vec_cmpgt (vector signed char, vector signed char); + vector signed short vec_cmpgt (vector unsigned short, + vector unsigned short); + vector signed short vec_cmpgt (vector signed short, + vector signed short); + vector signed int vec_cmpgt (vector unsigned int, vector unsigned int); + vector signed int vec_cmpgt (vector signed int, vector signed int); + vector signed int vec_cmpgt (vector float, vector float); + + vector signed int vec_cmple (vector float, vector float); + + vector signed char vec_cmplt (vector unsigned char, + vector unsigned char); + vector signed char vec_cmplt (vector signed char, vector signed char); + vector signed short vec_cmplt (vector unsigned short, + vector unsigned short); + vector signed short vec_cmplt (vector signed short, + vector signed short); + vector signed int vec_cmplt (vector unsigned int, vector unsigned int); + vector signed int vec_cmplt (vector signed int, vector signed int); + vector signed int vec_cmplt (vector float, vector float); + + vector float vec_ctf (vector unsigned int, const char); + vector float vec_ctf (vector signed int, const char); + + vector signed int vec_cts (vector float, const char); + + vector unsigned int vec_ctu (vector float, const char); + + void vec_dss (const char); + + void vec_dssall (void); + + void vec_dst (void *, int, const char); + + void vec_dstst (void *, int, const char); + + void vec_dststt (void *, int, const char); + + void vec_dstt (void *, int, const char); + + vector float vec_expte (vector float, vector float); + + vector float vec_floor (vector float, vector float); + + vector float vec_ld (int, vector float *); + vector float vec_ld (int, float *): + vector signed int vec_ld (int, int *); + vector signed int vec_ld (int, vector signed int *); + vector unsigned int vec_ld (int, vector unsigned int *); + vector unsigned int vec_ld (int, unsigned int *); + vector signed short vec_ld (int, short *, vector signed short *); + vector unsigned short vec_ld (int, unsigned short *, + vector unsigned short *); + vector signed char vec_ld (int, signed char *); + vector signed char vec_ld (int, vector signed char *); + vector unsigned char vec_ld (int, unsigned char *); + vector unsigned char vec_ld (int, vector unsigned char *); + + vector signed char vec_lde (int, signed char *); + vector unsigned char vec_lde (int, unsigned char *); + vector signed short vec_lde (int, short *); + vector unsigned short vec_lde (int, unsigned short *); + vector float vec_lde (int, float *); + vector signed int vec_lde (int, int *); + vector unsigned int vec_lde (int, unsigned int *); + + void float vec_ldl (int, float *); + void float vec_ldl (int, vector float *); + void signed int vec_ldl (int, vector signed int *); + void signed int vec_ldl (int, int *); + void unsigned int vec_ldl (int, unsigned int *); + void unsigned int vec_ldl (int, vector unsigned int *); + void signed short vec_ldl (int, vector signed short *); + void signed short vec_ldl (int, short *); + void unsigned short vec_ldl (int, vector unsigned short *); + void unsigned short vec_ldl (int, unsigned short *); + void signed char vec_ldl (int, vector signed char *); + void signed char vec_ldl (int, signed char *); + void unsigned char vec_ldl (int, vector unsigned char *); + void unsigned char vec_ldl (int, unsigned char *); + + vector float vec_loge (vector float); + + vector unsigned char vec_lvsl (int, void *, int *); + + vector unsigned char vec_lvsr (int, void *, int *); + + vector float vec_madd (vector float, vector float, vector float); + + vector signed short vec_madds (vector signed short, vector signed short, + vector signed short); + + vector unsigned char vec_max (vector signed char, vector unsigned char); + + vector unsigned char vec_max (vector unsigned char, vector signed char); + + vector unsigned char vec_max (vector unsigned char, + vector unsigned char); + vector signed char vec_max (vector signed char, vector signed char); + vector unsigned short vec_max (vector signed short, + vector unsigned short); + vector unsigned short vec_max (vector unsigned short, + vector signed short); + vector unsigned short vec_max (vector unsigned short, + vector unsigned short); + vector signed short vec_max (vector signed short, vector signed short); + vector unsigned int vec_max (vector signed int, vector unsigned int); + vector unsigned int vec_max (vector unsigned int, vector signed int); + vector unsigned int vec_max (vector unsigned int, vector unsigned int); + vector signed int vec_max (vector signed int, vector signed int); + vector float vec_max (vector float, vector float); + + vector signed char vec_mergeh (vector signed char, vector signed char); + vector unsigned char vec_mergeh (vector unsigned char, + vector unsigned char); + vector signed short vec_mergeh (vector signed short, + vector signed short); + vector unsigned short vec_mergeh (vector unsigned short, + vector unsigned short); + vector float vec_mergeh (vector float, vector float); + vector signed int vec_mergeh (vector signed int, vector signed int); + vector unsigned int vec_mergeh (vector unsigned int, + vector unsigned int); + + vector signed char vec_mergel (vector signed char, vector signed char); + vector unsigned char vec_mergel (vector unsigned char, + vector unsigned char); + vector signed short vec_mergel (vector signed short, + vector signed short); + vector unsigned short vec_mergel (vector unsigned short, + vector unsigned short); + vector float vec_mergel (vector float, vector float); + vector signed int vec_mergel (vector signed int, vector signed int); + vector unsigned int vec_mergel (vector unsigned int, + vector unsigned int); + + vector unsigned short vec_mfvscr (void); + + vector unsigned char vec_min (vector signed char, vector unsigned char); + + vector unsigned char vec_min (vector unsigned char, vector signed char); + + vector unsigned char vec_min (vector unsigned char, + vector unsigned char); + vector signed char vec_min (vector signed char, vector signed char); + vector unsigned short vec_min (vector signed short, + vector unsigned short); + vector unsigned short vec_min (vector unsigned short, + vector signed short); + vector unsigned short vec_min (vector unsigned short, + vector unsigned short); + vector signed short vec_min (vector signed short, vector signed short); + vector unsigned int vec_min (vector signed int, vector unsigned int); + vector unsigned int vec_min (vector unsigned int, vector signed int); + vector unsigned int vec_min (vector unsigned int, vector unsigned int); + vector signed int vec_min (vector signed int, vector signed int); + vector float vec_min (vector float, vector float); + + vector signed short vec_mladd (vector signed short, vector signed short, + vector signed short); + vector signed short vec_mladd (vector signed short, + vector unsigned short, + vector unsigned short); + vector signed short vec_mladd (vector unsigned short, + vector signed short, + vector signed short); + vector unsigned short vec_mladd (vector unsigned short, + vector unsigned short, + vector unsigned short); + + vector signed short vec_mradds (vector signed short, + vector signed short, + vector signed short); + + vector unsigned int vec_msum (vector unsigned char, + vector unsigned char, + vector unsigned int); + vector signed int vec_msum (vector signed char, vector unsigned char, + vector signed int); + vector unsigned int vec_msum (vector unsigned short, + vector unsigned short, + vector unsigned int); + vector signed int vec_msum (vector signed short, vector signed short, + vector signed int); + + vector unsigned int vec_msums (vector unsigned short, + vector unsigned short, + vector unsigned int); + vector signed int vec_msums (vector signed short, vector signed short, + vector signed int); + + void vec_mtvscr (vector signed int); + void vec_mtvscr (vector unsigned int); + void vec_mtvscr (vector signed short); + void vec_mtvscr (vector unsigned short); + void vec_mtvscr (vector signed char); + void vec_mtvscr (vector unsigned char); + + vector unsigned short vec_mule (vector unsigned char, + vector unsigned char); + vector signed short vec_mule (vector signed char, vector signed char); + vector unsigned int vec_mule (vector unsigned short, + vector unsigned short); + vector signed int vec_mule (vector signed short, vector signed short); + + vector unsigned short vec_mulo (vector unsigned char, + vector unsigned char); + vector signed short vec_mulo (vector signed char, vector signed char); + vector unsigned int vec_mulo (vector unsigned short, + vector unsigned short); + vector signed int vec_mulo (vector signed short, vector signed short); + + vector float vec_nmsub (vector float, vector float, vector float); + + vector float vec_nor (vector float, vector float); + vector signed int vec_nor (vector signed int, vector signed int); + vector unsigned int vec_nor (vector unsigned int, vector unsigned int); + vector signed short vec_nor (vector signed short, vector signed short); + vector unsigned short vec_nor (vector unsigned short, + vector unsigned short); + vector signed char vec_nor (vector signed char, vector signed char); + vector unsigned char vec_nor (vector unsigned char, + vector unsigned char); + + vector float vec_or (vector float, vector float); + vector float vec_or (vector float, vector signed int); + vector float vec_or (vector signed int, vector float); + vector signed int vec_or (vector signed int, vector signed int); + vector unsigned int vec_or (vector signed int, vector unsigned int); + vector unsigned int vec_or (vector unsigned int, vector signed int); + vector unsigned int vec_or (vector unsigned int, vector unsigned int); + vector signed short vec_or (vector signed short, vector signed short); + vector unsigned short vec_or (vector signed short, + vector unsigned short); + vector unsigned short vec_or (vector unsigned short, + vector signed short); + vector unsigned short vec_or (vector unsigned short, + vector unsigned short); + vector signed char vec_or (vector signed char, vector signed char); + vector unsigned char vec_or (vector signed char, vector unsigned char); + vector unsigned char vec_or (vector unsigned char, vector signed char); + vector unsigned char vec_or (vector unsigned char, + vector unsigned char); + + vector signed char vec_pack (vector signed short, vector signed short); + vector unsigned char vec_pack (vector unsigned short, + vector unsigned short); + vector signed short vec_pack (vector signed int, vector signed int); + vector unsigned short vec_pack (vector unsigned int, + vector unsigned int); + + vector signed short vec_packpx (vector unsigned int, + vector unsigned int); + + vector unsigned char vec_packs (vector unsigned short, + vector unsigned short); + vector signed char vec_packs (vector signed short, vector signed short); + + vector unsigned short vec_packs (vector unsigned int, + vector unsigned int); + vector signed short vec_packs (vector signed int, vector signed int); + + vector unsigned char vec_packsu (vector unsigned short, + vector unsigned short); + vector unsigned char vec_packsu (vector signed short, + vector signed short); + vector unsigned short vec_packsu (vector unsigned int, + vector unsigned int); + vector unsigned short vec_packsu (vector signed int, vector signed int); + + vector float vec_perm (vector float, vector float, + vector unsigned char); + vector signed int vec_perm (vector signed int, vector signed int, + vector unsigned char); + vector unsigned int vec_perm (vector unsigned int, vector unsigned int, + vector unsigned char); + vector signed short vec_perm (vector signed short, vector signed short, + vector unsigned char); + vector unsigned short vec_perm (vector unsigned short, + vector unsigned short, + vector unsigned char); + vector signed char vec_perm (vector signed char, vector signed char, + vector unsigned char); + vector unsigned char vec_perm (vector unsigned char, + vector unsigned char, + vector unsigned char); + + vector float vec_re (vector float); + + vector signed char vec_rl (vector signed char, vector unsigned char); + vector unsigned char vec_rl (vector unsigned char, + vector unsigned char); + vector signed short vec_rl (vector signed short, vector unsigned short); + + vector unsigned short vec_rl (vector unsigned short, + vector unsigned short); + vector signed int vec_rl (vector signed int, vector unsigned int); + vector unsigned int vec_rl (vector unsigned int, vector unsigned int); + + vector float vec_round (vector float); + + vector float vec_rsqrte (vector float); + + vector float vec_sel (vector float, vector float, vector signed int); + vector float vec_sel (vector float, vector float, vector unsigned int); + vector signed int vec_sel (vector signed int, vector signed int, + vector signed int); + vector signed int vec_sel (vector signed int, vector signed int, + vector unsigned int); + vector unsigned int vec_sel (vector unsigned int, vector unsigned int, + vector signed int); + vector unsigned int vec_sel (vector unsigned int, vector unsigned int, + vector unsigned int); + vector signed short vec_sel (vector signed short, vector signed short, + vector signed short); + vector signed short vec_sel (vector signed short, vector signed short, + vector unsigned short); + vector unsigned short vec_sel (vector unsigned short, + vector unsigned short, + vector signed short); + vector unsigned short vec_sel (vector unsigned short, + vector unsigned short, + vector unsigned short); + vector signed char vec_sel (vector signed char, vector signed char, + vector signed char); + vector signed char vec_sel (vector signed char, vector signed char, + vector unsigned char); + vector unsigned char vec_sel (vector unsigned char, + vector unsigned char, + vector signed char); + vector unsigned char vec_sel (vector unsigned char, + vector unsigned char, + vector unsigned char); + + vector signed char vec_sl (vector signed char, vector unsigned char); + vector unsigned char vec_sl (vector unsigned char, + vector unsigned char); + vector signed short vec_sl (vector signed short, vector unsigned short); + + vector unsigned short vec_sl (vector unsigned short, + vector unsigned short); + vector signed int vec_sl (vector signed int, vector unsigned int); + vector unsigned int vec_sl (vector unsigned int, vector unsigned int); + + vector float vec_sld (vector float, vector float, const char); + vector signed int vec_sld (vector signed int, vector signed int, + const char); + vector unsigned int vec_sld (vector unsigned int, vector unsigned int, + const char); + vector signed short vec_sld (vector signed short, vector signed short, + const char); + vector unsigned short vec_sld (vector unsigned short, + vector unsigned short, const char); + vector signed char vec_sld (vector signed char, vector signed char, + const char); + vector unsigned char vec_sld (vector unsigned char, + vector unsigned char, + const char); + + vector signed int vec_sll (vector signed int, vector unsigned int); + vector signed int vec_sll (vector signed int, vector unsigned short); + vector signed int vec_sll (vector signed int, vector unsigned char); + vector unsigned int vec_sll (vector unsigned int, vector unsigned int); + vector unsigned int vec_sll (vector unsigned int, + vector unsigned short); + vector unsigned int vec_sll (vector unsigned int, vector unsigned char); + + vector signed short vec_sll (vector signed short, vector unsigned int); + vector signed short vec_sll (vector signed short, + vector unsigned short); + vector signed short vec_sll (vector signed short, vector unsigned char); + + vector unsigned short vec_sll (vector unsigned short, + vector unsigned int); + vector unsigned short vec_sll (vector unsigned short, + vector unsigned short); + vector unsigned short vec_sll (vector unsigned short, + vector unsigned char); + vector signed char vec_sll (vector signed char, vector unsigned int); + vector signed char vec_sll (vector signed char, vector unsigned short); + vector signed char vec_sll (vector signed char, vector unsigned char); + vector unsigned char vec_sll (vector unsigned char, + vector unsigned int); + vector unsigned char vec_sll (vector unsigned char, + vector unsigned short); + vector unsigned char vec_sll (vector unsigned char, + vector unsigned char); + + vector float vec_slo (vector float, vector signed char); + vector float vec_slo (vector float, vector unsigned char); + vector signed int vec_slo (vector signed int, vector signed char); + vector signed int vec_slo (vector signed int, vector unsigned char); + vector unsigned int vec_slo (vector unsigned int, vector signed char); + vector unsigned int vec_slo (vector unsigned int, vector unsigned char); + + vector signed short vec_slo (vector signed short, vector signed char); + vector signed short vec_slo (vector signed short, vector unsigned char); + + vector unsigned short vec_slo (vector unsigned short, + vector signed char); + vector unsigned short vec_slo (vector unsigned short, + vector unsigned char); + vector signed char vec_slo (vector signed char, vector signed char); + vector signed char vec_slo (vector signed char, vector unsigned char); + vector unsigned char vec_slo (vector unsigned char, vector signed char); + + vector unsigned char vec_slo (vector unsigned char, + vector unsigned char); + + vector signed char vec_splat (vector signed char, const char); + vector unsigned char vec_splat (vector unsigned char, const char); + vector signed short vec_splat (vector signed short, const char); + vector unsigned short vec_splat (vector unsigned short, const char); + vector float vec_splat (vector float, const char); + vector signed int vec_splat (vector signed int, const char); + vector unsigned int vec_splat (vector unsigned int, const char); + + vector signed char vec_splat_s8 (const char); + + vector signed short vec_splat_s16 (const char); + + vector signed int vec_splat_s32 (const char); + + vector unsigned char vec_splat_u8 (const char); + + vector unsigned short vec_splat_u16 (const char); + + vector unsigned int vec_splat_u32 (const char); + + vector signed char vec_sr (vector signed char, vector unsigned char); + vector unsigned char vec_sr (vector unsigned char, + vector unsigned char); + vector signed short vec_sr (vector signed short, vector unsigned short); + + vector unsigned short vec_sr (vector unsigned short, + vector unsigned short); + vector signed int vec_sr (vector signed int, vector unsigned int); + vector unsigned int vec_sr (vector unsigned int, vector unsigned int); + + vector signed char vec_sra (vector signed char, vector unsigned char); + vector unsigned char vec_sra (vector unsigned char, + vector unsigned char); + vector signed short vec_sra (vector signed short, + vector unsigned short); + vector unsigned short vec_sra (vector unsigned short, + vector unsigned short); + vector signed int vec_sra (vector signed int, vector unsigned int); + vector unsigned int vec_sra (vector unsigned int, vector unsigned int); + + vector signed int vec_srl (vector signed int, vector unsigned int); + vector signed int vec_srl (vector signed int, vector unsigned short); + vector signed int vec_srl (vector signed int, vector unsigned char); + vector unsigned int vec_srl (vector unsigned int, vector unsigned int); + vector unsigned int vec_srl (vector unsigned int, + vector unsigned short); + vector unsigned int vec_srl (vector unsigned int, vector unsigned char); + + vector signed short vec_srl (vector signed short, vector unsigned int); + vector signed short vec_srl (vector signed short, + vector unsigned short); + vector signed short vec_srl (vector signed short, vector unsigned char); + + vector unsigned short vec_srl (vector unsigned short, + vector unsigned int); + vector unsigned short vec_srl (vector unsigned short, + vector unsigned short); + vector unsigned short vec_srl (vector unsigned short, + vector unsigned char); + vector signed char vec_srl (vector signed char, vector unsigned int); + vector signed char vec_srl (vector signed char, vector unsigned short); + vector signed char vec_srl (vector signed char, vector unsigned char); + vector unsigned char vec_srl (vector unsigned char, + vector unsigned int); + vector unsigned char vec_srl (vector unsigned char, + vector unsigned short); + vector unsigned char vec_srl (vector unsigned char, + vector unsigned char); + + vector float vec_sro (vector float, vector signed char); + vector float vec_sro (vector float, vector unsigned char); + vector signed int vec_sro (vector signed int, vector signed char); + vector signed int vec_sro (vector signed int, vector unsigned char); + vector unsigned int vec_sro (vector unsigned int, vector signed char); + vector unsigned int vec_sro (vector unsigned int, vector unsigned char); + + vector signed short vec_sro (vector signed short, vector signed char); + vector signed short vec_sro (vector signed short, vector unsigned char); + + vector unsigned short vec_sro (vector unsigned short, + vector signed char); + vector unsigned short vec_sro (vector unsigned short, + vector unsigned char); + vector signed char vec_sro (vector signed char, vector signed char); + vector signed char vec_sro (vector signed char, vector unsigned char); + vector unsigned char vec_sro (vector unsigned char, vector signed char); + + vector unsigned char vec_sro (vector unsigned char, + vector unsigned char); + + void vec_st (vector float, int, float *); + void vec_st (vector float, int, vector float *); + void vec_st (vector signed int, int, int *); + void vec_st (vector signed int, int, unsigned int *); + void vec_st (vector unsigned int, int, unsigned int *); + void vec_st (vector unsigned int, int, vector unsigned int *); + void vec_st (vector signed short, int, short *); + void vec_st (vector signed short, int, vector unsigned short *); + void vec_st (vector signed short, int, vector signed short *); + void vec_st (vector unsigned short, int, unsigned short *); + void vec_st (vector unsigned short, int, vector unsigned short *); + void vec_st (vector signed char, int, signed char *); + void vec_st (vector signed char, int, unsigned char *); + void vec_st (vector signed char, int, vector signed char *); + void vec_st (vector unsigned char, int, unsigned char *); + void vec_st (vector unsigned char, int, vector unsigned char *); + + void vec_ste (vector signed char, int, unsigned char *); + void vec_ste (vector signed char, int, signed char *); + void vec_ste (vector unsigned char, int, unsigned char *); + void vec_ste (vector signed short, int, short *); + void vec_ste (vector signed short, int, unsigned short *); + void vec_ste (vector unsigned short, int, void *); + void vec_ste (vector signed int, int, unsigned int *); + void vec_ste (vector signed int, int, int *); + void vec_ste (vector unsigned int, int, unsigned int *); + void vec_ste (vector float, int, float *); + + void vec_stl (vector float, int, vector float *); + void vec_stl (vector float, int, float *); + void vec_stl (vector signed int, int, vector signed int *); + void vec_stl (vector signed int, int, int *); + void vec_stl (vector signed int, int, unsigned int *); + void vec_stl (vector unsigned int, int, vector unsigned int *); + void vec_stl (vector unsigned int, int, unsigned int *); + void vec_stl (vector signed short, int, short *); + void vec_stl (vector signed short, int, unsigned short *); + void vec_stl (vector signed short, int, vector signed short *); + void vec_stl (vector unsigned short, int, unsigned short *); + void vec_stl (vector unsigned short, int, vector signed short *); + void vec_stl (vector signed char, int, signed char *); + void vec_stl (vector signed char, int, unsigned char *); + void vec_stl (vector signed char, int, vector signed char *); + void vec_stl (vector unsigned char, int, unsigned char *); + void vec_stl (vector unsigned char, int, vector unsigned char *); + + vector signed char vec_sub (vector signed char, vector signed char); + vector unsigned char vec_sub (vector signed char, vector unsigned char); + + vector unsigned char vec_sub (vector unsigned char, vector signed char); + + vector unsigned char vec_sub (vector unsigned char, + vector unsigned char); + vector signed short vec_sub (vector signed short, vector signed short); + vector unsigned short vec_sub (vector signed short, + vector unsigned short); + vector unsigned short vec_sub (vector unsigned short, + vector signed short); + vector unsigned short vec_sub (vector unsigned short, + vector unsigned short); + vector signed int vec_sub (vector signed int, vector signed int); + vector unsigned int vec_sub (vector signed int, vector unsigned int); + vector unsigned int vec_sub (vector unsigned int, vector signed int); + vector unsigned int vec_sub (vector unsigned int, vector unsigned int); + vector float vec_sub (vector float, vector float); + + vector unsigned int vec_subc (vector unsigned int, vector unsigned int); + + vector unsigned char vec_subs (vector signed char, + vector unsigned char); + vector unsigned char vec_subs (vector unsigned char, + vector signed char); + vector unsigned char vec_subs (vector unsigned char, + vector unsigned char); + vector signed char vec_subs (vector signed char, vector signed char); + vector unsigned short vec_subs (vector signed short, + vector unsigned short); + vector unsigned short vec_subs (vector unsigned short, + vector signed short); + vector unsigned short vec_subs (vector unsigned short, + vector unsigned short); + vector signed short vec_subs (vector signed short, vector signed short); + + vector unsigned int vec_subs (vector signed int, vector unsigned int); + vector unsigned int vec_subs (vector unsigned int, vector signed int); + vector unsigned int vec_subs (vector unsigned int, vector unsigned int); + + vector signed int vec_subs (vector signed int, vector signed int); + + vector unsigned int vec_sum4s (vector unsigned char, + vector unsigned int); + vector signed int vec_sum4s (vector signed char, vector signed int); + vector signed int vec_sum4s (vector signed short, vector signed int); + + vector signed int vec_sum2s (vector signed int, vector signed int); + + vector signed int vec_sums (vector signed int, vector signed int); + + vector float vec_trunc (vector float); + + vector signed short vec_unpackh (vector signed char); + vector unsigned int vec_unpackh (vector signed short); + vector signed int vec_unpackh (vector signed short); + + vector signed short vec_unpackl (vector signed char); + vector unsigned int vec_unpackl (vector signed short); + vector signed int vec_unpackl (vector signed short); + + vector float vec_xor (vector float, vector float); + vector float vec_xor (vector float, vector signed int); + vector float vec_xor (vector signed int, vector float); + vector signed int vec_xor (vector signed int, vector signed int); + vector unsigned int vec_xor (vector signed int, vector unsigned int); + vector unsigned int vec_xor (vector unsigned int, vector signed int); + vector unsigned int vec_xor (vector unsigned int, vector unsigned int); + vector signed short vec_xor (vector signed short, vector signed short); + vector unsigned short vec_xor (vector signed short, + vector unsigned short); + vector unsigned short vec_xor (vector unsigned short, + vector signed short); + vector unsigned short vec_xor (vector unsigned short, + vector unsigned short); + vector signed char vec_xor (vector signed char, vector signed char); + vector unsigned char vec_xor (vector signed char, vector unsigned char); + + vector unsigned char vec_xor (vector unsigned char, vector signed char); + + vector unsigned char vec_xor (vector unsigned char, + vector unsigned char); + + vector signed int vec_all_eq (vector signed char, vector unsigned char); + + vector signed int vec_all_eq (vector signed char, vector signed char); + vector signed int vec_all_eq (vector unsigned char, vector signed char); + + vector signed int vec_all_eq (vector unsigned char, + vector unsigned char); + vector signed int vec_all_eq (vector signed short, + vector unsigned short); + vector signed int vec_all_eq (vector signed short, vector signed short); + + vector signed int vec_all_eq (vector unsigned short, + vector signed short); + vector signed int vec_all_eq (vector unsigned short, + vector unsigned short); + vector signed int vec_all_eq (vector signed int, vector unsigned int); + vector signed int vec_all_eq (vector signed int, vector signed int); + vector signed int vec_all_eq (vector unsigned int, vector signed int); + vector signed int vec_all_eq (vector unsigned int, vector unsigned int); + + vector signed int vec_all_eq (vector float, vector float); + + vector signed int vec_all_ge (vector signed char, vector unsigned char); + + vector signed int vec_all_ge (vector unsigned char, vector signed char); + + vector signed int vec_all_ge (vector unsigned char, + vector unsigned char); + vector signed int vec_all_ge (vector signed char, vector signed char); + vector signed int vec_all_ge (vector signed short, + vector unsigned short); + vector signed int vec_all_ge (vector unsigned short, + vector signed short); + vector signed int vec_all_ge (vector unsigned short, + vector unsigned short); + vector signed int vec_all_ge (vector signed short, vector signed short); + + vector signed int vec_all_ge (vector signed int, vector unsigned int); + vector signed int vec_all_ge (vector unsigned int, vector signed int); + vector signed int vec_all_ge (vector unsigned int, vector unsigned int); + + vector signed int vec_all_ge (vector signed int, vector signed int); + vector signed int vec_all_ge (vector float, vector float); + + vector signed int vec_all_gt (vector signed char, vector unsigned char); + + vector signed int vec_all_gt (vector unsigned char, vector signed char); + + vector signed int vec_all_gt (vector unsigned char, + vector unsigned char); + vector signed int vec_all_gt (vector signed char, vector signed char); + vector signed int vec_all_gt (vector signed short, + vector unsigned short); + vector signed int vec_all_gt (vector unsigned short, + vector signed short); + vector signed int vec_all_gt (vector unsigned short, + vector unsigned short); + vector signed int vec_all_gt (vector signed short, vector signed short); + + vector signed int vec_all_gt (vector signed int, vector unsigned int); + vector signed int vec_all_gt (vector unsigned int, vector signed int); + vector signed int vec_all_gt (vector unsigned int, vector unsigned int); + + vector signed int vec_all_gt (vector signed int, vector signed int); + vector signed int vec_all_gt (vector float, vector float); + + vector signed int vec_all_in (vector float, vector float); + + vector signed int vec_all_le (vector signed char, vector unsigned char); + + vector signed int vec_all_le (vector unsigned char, vector signed char); + + vector signed int vec_all_le (vector unsigned char, + vector unsigned char); + vector signed int vec_all_le (vector signed char, vector signed char); + vector signed int vec_all_le (vector signed short, + vector unsigned short); + vector signed int vec_all_le (vector unsigned short, + vector signed short); + vector signed int vec_all_le (vector unsigned short, + vector unsigned short); + vector signed int vec_all_le (vector signed short, vector signed short); + + vector signed int vec_all_le (vector signed int, vector unsigned int); + vector signed int vec_all_le (vector unsigned int, vector signed int); + vector signed int vec_all_le (vector unsigned int, vector unsigned int); + + vector signed int vec_all_le (vector signed int, vector signed int); + vector signed int vec_all_le (vector float, vector float); + + vector signed int vec_all_lt (vector signed char, vector unsigned char); + + vector signed int vec_all_lt (vector unsigned char, vector signed char); + + vector signed int vec_all_lt (vector unsigned char, + vector unsigned char); + vector signed int vec_all_lt (vector signed char, vector signed char); + vector signed int vec_all_lt (vector signed short, + vector unsigned short); + vector signed int vec_all_lt (vector unsigned short, + vector signed short); + vector signed int vec_all_lt (vector unsigned short, + vector unsigned short); + vector signed int vec_all_lt (vector signed short, vector signed short); + + vector signed int vec_all_lt (vector signed int, vector unsigned int); + vector signed int vec_all_lt (vector unsigned int, vector signed int); + vector signed int vec_all_lt (vector unsigned int, vector unsigned int); + + vector signed int vec_all_lt (vector signed int, vector signed int); + vector signed int vec_all_lt (vector float, vector float); + + vector signed int vec_all_nan (vector float); + + vector signed int vec_all_ne (vector signed char, vector unsigned char); + + vector signed int vec_all_ne (vector signed char, vector signed char); + vector signed int vec_all_ne (vector unsigned char, vector signed char); + + vector signed int vec_all_ne (vector unsigned char, + vector unsigned char); + vector signed int vec_all_ne (vector signed short, + vector unsigned short); + vector signed int vec_all_ne (vector signed short, vector signed short); + + vector signed int vec_all_ne (vector unsigned short, + vector signed short); + vector signed int vec_all_ne (vector unsigned short, + vector unsigned short); + vector signed int vec_all_ne (vector signed int, vector unsigned int); + vector signed int vec_all_ne (vector signed int, vector signed int); + vector signed int vec_all_ne (vector unsigned int, vector signed int); + vector signed int vec_all_ne (vector unsigned int, vector unsigned int); + + vector signed int vec_all_ne (vector float, vector float); + + vector signed int vec_all_nge (vector float, vector float); + + vector signed int vec_all_ngt (vector float, vector float); + + vector signed int vec_all_nle (vector float, vector float); + + vector signed int vec_all_nlt (vector float, vector float); + + vector signed int vec_all_numeric (vector float); + + vector signed int vec_any_eq (vector signed char, vector unsigned char); + + vector signed int vec_any_eq (vector signed char, vector signed char); + vector signed int vec_any_eq (vector unsigned char, vector signed char); + + vector signed int vec_any_eq (vector unsigned char, + vector unsigned char); + vector signed int vec_any_eq (vector signed short, + vector unsigned short); + vector signed int vec_any_eq (vector signed short, vector signed short); + + vector signed int vec_any_eq (vector unsigned short, + vector signed short); + vector signed int vec_any_eq (vector unsigned short, + vector unsigned short); + vector signed int vec_any_eq (vector signed int, vector unsigned int); + vector signed int vec_any_eq (vector signed int, vector signed int); + vector signed int vec_any_eq (vector unsigned int, vector signed int); + vector signed int vec_any_eq (vector unsigned int, vector unsigned int); + + vector signed int vec_any_eq (vector float, vector float); + + vector signed int vec_any_ge (vector signed char, vector unsigned char); + + vector signed int vec_any_ge (vector unsigned char, vector signed char); + + vector signed int vec_any_ge (vector unsigned char, + vector unsigned char); + vector signed int vec_any_ge (vector signed char, vector signed char); + vector signed int vec_any_ge (vector signed short, + vector unsigned short); + vector signed int vec_any_ge (vector unsigned short, + vector signed short); + vector signed int vec_any_ge (vector unsigned short, + vector unsigned short); + vector signed int vec_any_ge (vector signed short, vector signed short); + + vector signed int vec_any_ge (vector signed int, vector unsigned int); + vector signed int vec_any_ge (vector unsigned int, vector signed int); + vector signed int vec_any_ge (vector unsigned int, vector unsigned int); + + vector signed int vec_any_ge (vector signed int, vector signed int); + vector signed int vec_any_ge (vector float, vector float); + + vector signed int vec_any_gt (vector signed char, vector unsigned char); + + vector signed int vec_any_gt (vector unsigned char, vector signed char); + + vector signed int vec_any_gt (vector unsigned char, + vector unsigned char); + vector signed int vec_any_gt (vector signed char, vector signed char); + vector signed int vec_any_gt (vector signed short, + vector unsigned short); + vector signed int vec_any_gt (vector unsigned short, + vector signed short); + vector signed int vec_any_gt (vector unsigned short, + vector unsigned short); + vector signed int vec_any_gt (vector signed short, vector signed short); + + vector signed int vec_any_gt (vector signed int, vector unsigned int); + vector signed int vec_any_gt (vector unsigned int, vector signed int); + vector signed int vec_any_gt (vector unsigned int, vector unsigned int); + + vector signed int vec_any_gt (vector signed int, vector signed int); + vector signed int vec_any_gt (vector float, vector float); + + vector signed int vec_any_le (vector signed char, vector unsigned char); + + vector signed int vec_any_le (vector unsigned char, vector signed char); + + vector signed int vec_any_le (vector unsigned char, + vector unsigned char); + vector signed int vec_any_le (vector signed char, vector signed char); + vector signed int vec_any_le (vector signed short, + vector unsigned short); + vector signed int vec_any_le (vector unsigned short, + vector signed short); + vector signed int vec_any_le (vector unsigned short, + vector unsigned short); + vector signed int vec_any_le (vector signed short, vector signed short); + + vector signed int vec_any_le (vector signed int, vector unsigned int); + vector signed int vec_any_le (vector unsigned int, vector signed int); + vector signed int vec_any_le (vector unsigned int, vector unsigned int); + + vector signed int vec_any_le (vector signed int, vector signed int); + vector signed int vec_any_le (vector float, vector float); + + vector signed int vec_any_lt (vector signed char, vector unsigned char); + + vector signed int vec_any_lt (vector unsigned char, vector signed char); + + vector signed int vec_any_lt (vector unsigned char, + vector unsigned char); + vector signed int vec_any_lt (vector signed char, vector signed char); + vector signed int vec_any_lt (vector signed short, + vector unsigned short); + vector signed int vec_any_lt (vector unsigned short, + vector signed short); + vector signed int vec_any_lt (vector unsigned short, + vector unsigned short); + vector signed int vec_any_lt (vector signed short, vector signed short); + + vector signed int vec_any_lt (vector signed int, vector unsigned int); + vector signed int vec_any_lt (vector unsigned int, vector signed int); + vector signed int vec_any_lt (vector unsigned int, vector unsigned int); + + vector signed int vec_any_lt (vector signed int, vector signed int); + vector signed int vec_any_lt (vector float, vector float); + + vector signed int vec_any_nan (vector float); + + vector signed int vec_any_ne (vector signed char, vector unsigned char); + + vector signed int vec_any_ne (vector signed char, vector signed char); + vector signed int vec_any_ne (vector unsigned char, vector signed char); + + vector signed int vec_any_ne (vector unsigned char, + vector unsigned char); + vector signed int vec_any_ne (vector signed short, + vector unsigned short); + vector signed int vec_any_ne (vector signed short, vector signed short); + + vector signed int vec_any_ne (vector unsigned short, + vector signed short); + vector signed int vec_any_ne (vector unsigned short, + vector unsigned short); + vector signed int vec_any_ne (vector signed int, vector unsigned int); + vector signed int vec_any_ne (vector signed int, vector signed int); + vector signed int vec_any_ne (vector unsigned int, vector signed int); + vector signed int vec_any_ne (vector unsigned int, vector unsigned int); + + vector signed int vec_any_ne (vector float, vector float); + + vector signed int vec_any_nge (vector float, vector float); + + vector signed int vec_any_ngt (vector float, vector float); + + vector signed int vec_any_nle (vector float, vector float); + + vector signed int vec_any_nlt (vector float, vector float); + + vector signed int vec_any_numeric (vector float); + + vector signed int vec_any_out (vector float, vector float); + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-17 gcc-3.2.3/gcc/doc/gcc.info-17 *** gcc-3.2.2/gcc/doc/gcc.info-17 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-17 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1210 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Pragmas, Next: Unnamed Fields, Prev: Target Builtins, Up: C Extensions + + Pragmas Accepted by GCC + ======================= + + GCC supports several types of pragmas, primarily in order to compile + code originally written for other compilers. Note that in general we + do not recommend the use of pragmas; *Note Function Attributes::, for + further explanation. + + * Menu: + + * ARM Pragmas:: + * Darwin Pragmas:: + * Solaris Pragmas:: + * Tru64 Pragmas:: + +  + File: gcc.info, Node: ARM Pragmas, Next: Darwin Pragmas, Up: Pragmas + + ARM Pragmas + ----------- + + The ARM target defines pragmas for controlling the default addition + of `long_call' and `short_call' attributes to functions. *Note + Function Attributes::, for information about the effects of these + attributes. + + `long_calls' + Set all subsequent functions to have the `long_call' attribute. + + `no_long_calls' + Set all subsequent functions to have the `short_call' attribute. + + `long_calls_off' + Do not affect the `long_call' or `short_call' attributes of + subsequent functions. + +  + File: gcc.info, Node: Darwin Pragmas, Next: Solaris Pragmas, Prev: ARM Pragmas, Up: Pragmas + + Darwin Pragmas + -------------- + + The following pragmas are available for all architectures running the + Darwin operating system. These are useful for compatibility with other + MacOS compilers. + + `mark TOKENS...' + This pragma is accepted, but has no effect. + + `options align=ALIGNMENT' + This pragma sets the alignment of fields in structures. The + values of ALIGNMENT may be `mac68k', to emulate m68k alignment, or + `power', to emulate PowerPC alignment. Uses of this pragma nest + properly; to restore the previous setting, use `reset' for the + ALIGNMENT. + + `segment TOKENS...' + This pragma is accepted, but has no effect. + + `unused (VAR [, VAR]...)' + This pragma declares variables to be possibly unused. GCC will not + produce warnings for the listed variables. The effect is similar + to that of the `unused' attribute, except that this pragma may + appear anywhere within the variables' scopes. + +  + File: gcc.info, Node: Solaris Pragmas, Next: Tru64 Pragmas, Prev: Darwin Pragmas, Up: Pragmas + + Solaris Pragmas + --------------- + + For compatibility with the SunPRO compiler, the following pragma is + supported. + + `redefine_extname OLDNAME NEWNAME' + This pragma gives the C function OLDNAME the assembler label + NEWNAME. The pragma must appear before the function declaration. + This pragma is equivalent to the asm labels extension (*note Asm + Labels::). The preprocessor defines `__PRAGMA_REDEFINE_EXTNAME' + if the pragma is available. + +  + File: gcc.info, Node: Tru64 Pragmas, Prev: Solaris Pragmas, Up: Pragmas + + Tru64 Pragmas + ------------- + + For compatibility with the Compaq C compiler, the following pragma + is supported. + + `extern_prefix STRING' + This pragma renames all subsequent function and variable + declarations such that STRING is prepended to the name. This + effect may be terminated by using another `extern_prefix' pragma + with the empty string. + + This pragma is similar in intent to to the asm labels extension + (*note Asm Labels::) in that the system programmer wants to change + the assembly-level ABI without changing the source-level API. The + preprocessor defines `__PRAGMA_EXTERN_PREFIX' if the pragma is + available. + +  + File: gcc.info, Node: Unnamed Fields, Prev: Pragmas, Up: C Extensions + + Unnamed struct/union fields within structs/unions. + ================================================== + + For compatibility with other compilers, GCC allows you to define a + structure or union that contains, as fields, structures and unions + without names. For example: + + struct { + int a; + union { + int b; + float c; + }; + int d; + } foo; + + In this example, the user would be able to access members of the + unnamed union with code like `foo.b'. Note that only unnamed structs + and unions are allowed, you may not have, for example, an unnamed `int'. + + You must never create such structures that cause ambiguous field + definitions. For example, this structure: + + struct { + int a; + struct { + int a; + }; + } foo; + + It is ambiguous which `a' is being referred to with `foo.a'. Such + constructs are not supported and must be avoided. In the future, such + constructs may be detected and treated as compilation errors. + +  + File: gcc.info, Node: C++ Extensions, Next: Objective-C, Prev: C Extensions, Up: Top + + Extensions to the C++ Language + ****************************** + + The GNU compiler provides these extensions to the C++ language (and + you can also use most of the C language extensions in your C++ + programs). If you want to write code that checks whether these + features are available, you can test for the GNU compiler the same way + as for C programs: check for a predefined macro `__GNUC__'. You can + also use `__GNUG__' to test specifically for GNU C++ (*note Standard + Predefined Macros: (cpp.info)Standard Predefined.). + + * Menu: + + * Min and Max:: C++ Minimum and maximum operators. + * Volatiles:: What constitutes an access to a volatile object. + * Restricted Pointers:: C99 restricted pointers and references. + * Vague Linkage:: Where G++ puts inlines, vtables and such. + * C++ Interface:: You can use a single C++ header file for both + declarations and definitions. + * Template Instantiation:: Methods for ensuring that exactly one copy of + each needed template instantiation is emitted. + * Bound member functions:: You can extract a function pointer to the + method denoted by a `->*' or `.*' expression. + * C++ Attributes:: Variable, function, and type attributes for C++ only. + * Java Exceptions:: Tweaking exception handling to work with Java. + * Deprecated Features:: Things might disappear from g++. + * Backwards Compatibility:: Compatibilities with earlier definitions of C++. + +  + File: gcc.info, Node: Min and Max, Next: Volatiles, Up: C++ Extensions + + Minimum and Maximum Operators in C++ + ==================================== + + It is very convenient to have operators which return the "minimum" + or the "maximum" of two arguments. In GNU C++ (but not in GNU C), + + `A ? B' + is the "maximum", returning the larger of the numeric values A and + B. + + These operations are not primitive in ordinary C++, since you can + use a macro to return the minimum of two things in C++, as in the + following example. + + #define MIN(X,Y) ((X) < (Y) ? : (X) : (Y)) + + You might then use `int min = MIN (i, j);' to set MIN to the minimum + value of variables I and J. + + However, side effects in `X' or `Y' may cause unintended behavior. + For example, `MIN (i++, j++)' will fail, incrementing the smaller + counter twice. The GNU C `typeof' extension allows you to write safe + macros that avoid this kind of problem (*note Typeof::). However, + writing `MIN' and `MAX' as macros also forces you to use function-call + notation for a fundamental arithmetic operation. Using GNU C++ + extensions, you can write `int min = i ?' are built into the compiler, they properly + handle expressions with side-effects; `int min = i++ (*ptr1)'. + + When using a reference to volatile, G++ does not treat equivalent + expressions as accesses to volatiles, but instead issues a warning that + no volatile is accessed. The rationale for this is that otherwise it + becomes difficult to determine where volatile access occur, and not + possible to ignore the return value from functions returning volatile + references. Again, if you wish to force a read, cast the reference to + an rvalue. + +  + File: gcc.info, Node: Restricted Pointers, Next: Vague Linkage, Prev: Volatiles, Up: C++ Extensions + + Restricting Pointer Aliasing + ============================ + + As with gcc, g++ understands the C99 feature of restricted pointers, + specified with the `__restrict__', or `__restrict' type qualifier. + Because you cannot compile C++ by specifying the `-std=c99' language + flag, `restrict' is not a keyword in C++. + + In addition to allowing restricted pointers, you can specify + restricted references, which indicate that the reference is not aliased + in the local context. + + void fn (int *__restrict__ rptr, int &__restrict__ rref) + { + ... + } + + In the body of `fn', RPTR points to an unaliased integer and RREF + refers to a (different) unaliased integer. + + You may also specify whether a member function's THIS pointer is + unaliased by using `__restrict__' as a member function qualifier. + + void T::fn () __restrict__ + { + ... + } + + Within the body of `T::fn', THIS will have the effective definition `T + *__restrict__ const this'. Notice that the interpretation of a + `__restrict__' member function qualifier is different to that of + `const' or `volatile' qualifier, in that it is applied to the pointer + rather than the object. This is consistent with other compilers which + implement restricted pointers. + + As with all outermost parameter qualifiers, `__restrict__' is + ignored in function definition matching. This means you only need to + specify `__restrict__' in a function definition, rather than in a + function prototype as well. + +  + File: gcc.info, Node: Vague Linkage, Next: C++ Interface, Prev: Restricted Pointers, Up: C++ Extensions + + Vague Linkage + ============= + + There are several constructs in C++ which require space in the object + file but are not clearly tied to a single translation unit. We say that + these constructs have "vague linkage". Typically such constructs are + emitted wherever they are needed, though sometimes we can be more + clever. + + Inline Functions + Inline functions are typically defined in a header file which can + be included in many different compilations. Hopefully they can + usually be inlined, but sometimes an out-of-line copy is + necessary, if the address of the function is taken or if inlining + fails. In general, we emit an out-of-line copy in all translation + units where one is needed. As an exception, we only emit inline + virtual functions with the vtable, since it will always require a + copy. + + Local static variables and string constants used in an inline + function are also considered to have vague linkage, since they + must be shared between all inlined and out-of-line instances of + the function. + + VTables + C++ virtual functions are implemented in most compilers using a + lookup table, known as a vtable. The vtable contains pointers to + the virtual functions provided by a class, and each object of the + class contains a pointer to its vtable (or vtables, in some + multiple-inheritance situations). If the class declares any + non-inline, non-pure virtual functions, the first one is chosen as + the "key method" for the class, and the vtable is only emitted in + the translation unit where the key method is defined. + + _Note:_ If the chosen key method is later defined as inline, the + vtable will still be emitted in every translation unit which + defines it. Make sure that any inline virtuals are declared + inline in the class body, even if they are not defined there. + + type_info objects + C++ requires information about types to be written out in order to + implement `dynamic_cast', `typeid' and exception handling. For + polymorphic classes (classes with virtual functions), the type_info + object is written out along with the vtable so that `dynamic_cast' + can determine the dynamic type of a class object at runtime. For + all other types, we write out the type_info object when it is + used: when applying `typeid' to an expression, throwing an object, + or referring to a type in a catch clause or exception + specification. + + Template Instantiations + Most everything in this section also applies to template + instantiations, but there are other options as well. *Note + Where's the Template?: Template Instantiation. + + + When used with GNU ld version 2.8 or later on an ELF system such as + Linux/GNU or Solaris 2, or on Microsoft Windows, duplicate copies of + these constructs will be discarded at link time. This is known as + COMDAT support. + + On targets that don't support COMDAT, but do support weak symbols, + GCC will use them. This way one copy will override all the others, but + the unused copies will still take up space in the executable. + + For targets which do not support either COMDAT or weak symbols, most + entities with vague linkage will be emitted as local symbols to avoid + duplicate definition errors from the linker. This will not happen for + local statics in inlines, however, as having multiple copies will + almost certainly break things. + + *Note Declarations and Definitions in One Header: C++ Interface, for + another way to control placement of these constructs. + +  + File: gcc.info, Node: C++ Interface, Next: Template Instantiation, Prev: Vague Linkage, Up: C++ Extensions + + Declarations and Definitions in One Header + ========================================== + + C++ object definitions can be quite complex. In principle, your + source code will need two kinds of things for each object that you use + across more than one source file. First, you need an "interface" + specification, describing its structure with type declarations and + function prototypes. Second, you need the "implementation" itself. It + can be tedious to maintain a separate interface description in a header + file, in parallel to the actual implementation. It is also dangerous, + since separate interface and implementation definitions may not remain + parallel. + + With GNU C++, you can use a single header file for both purposes. + + _Warning:_ The mechanism to specify this is in transition. For the + nonce, you must use one of two `#pragma' commands; in a future + release of GNU C++, an alternative mechanism will make these + `#pragma' commands unnecessary. + + The header file contains the full definitions, but is marked with + `#pragma interface' in the source code. This allows the compiler to + use the header file only as an interface specification when ordinary + source files incorporate it with `#include'. In the single source file + where the full implementation belongs, you can use either a naming + convention or `#pragma implementation' to indicate this alternate use + of the header file. + + `#pragma interface' + `#pragma interface "SUBDIR/OBJECTS.h"' + Use this directive in _header files_ that define object classes, + to save space in most of the object files that use those classes. + Normally, local copies of certain information (backup copies of + inline member functions, debugging information, and the internal + tables that implement virtual functions) must be kept in each + object file that includes class definitions. You can use this + pragma to avoid such duplication. When a header file containing + `#pragma interface' is included in a compilation, this auxiliary + information will not be generated (unless the main input source + file itself uses `#pragma implementation'). Instead, the object + files will contain references to be resolved at link time. + + The second form of this directive is useful for the case where you + have multiple headers with the same name in different directories. + If you use this form, you must specify the same string to `#pragma + implementation'. + + `#pragma implementation' + `#pragma implementation "OBJECTS.h"' + Use this pragma in a _main input file_, when you want full output + from included header files to be generated (and made globally + visible). The included header file, in turn, should use `#pragma + interface'. Backup copies of inline member functions, debugging + information, and the internal tables used to implement virtual + functions are all generated in implementation files. + + If you use `#pragma implementation' with no argument, it applies to + an include file with the same basename(1) as your source file. + For example, in `allclass.cc', giving just `#pragma implementation' + by itself is equivalent to `#pragma implementation "allclass.h"'. + + In versions of GNU C++ prior to 2.6.0 `allclass.h' was treated as + an implementation file whenever you would include it from + `allclass.cc' even if you never specified `#pragma + implementation'. This was deemed to be more trouble than it was + worth, however, and disabled. + + If you use an explicit `#pragma implementation', it must appear in + your source file _before_ you include the affected header files. + + Use the string argument if you want a single implementation file to + include code from multiple header files. (You must also use + `#include' to include the header file; `#pragma implementation' + only specifies how to use the file--it doesn't actually include + it.) + + There is no way to split up the contents of a single header file + into multiple implementation files. + + `#pragma implementation' and `#pragma interface' also have an effect + on function inlining. + + If you define a class in a header file marked with `#pragma + interface', the effect on a function defined in that class is similar to + an explicit `extern' declaration--the compiler emits no code at all to + define an independent version of the function. Its definition is used + only for inlining with its callers. + + Conversely, when you include the same header file in a main source + file that declares it as `#pragma implementation', the compiler emits + code for the function itself; this defines a version of the function + that can be found via pointers (or by callers compiled without + inlining). If all calls to the function can be inlined, you can avoid + emitting the function by compiling with `-fno-implement-inlines'. If + any calls were not inlined, you will get linker errors. + + ---------- Footnotes ---------- + + (1) A file's "basename" was the name stripped of all leading path + information and of trailing suffixes, such as `.h' or `.C' or `.cc'. + +  + File: gcc.info, Node: Template Instantiation, Next: Bound member functions, Prev: C++ Interface, Up: C++ Extensions + + Where's the Template? + ===================== + + C++ templates are the first language feature to require more + intelligence from the environment than one usually finds on a UNIX + system. Somehow the compiler and linker have to make sure that each + template instance occurs exactly once in the executable if it is needed, + and not at all otherwise. There are two basic approaches to this + problem, which I will refer to as the Borland model and the Cfront + model. + + Borland model + Borland C++ solved the template instantiation problem by adding + the code equivalent of common blocks to their linker; the compiler + emits template instances in each translation unit that uses them, + and the linker collapses them together. The advantage of this + model is that the linker only has to consider the object files + themselves; there is no external complexity to worry about. This + disadvantage is that compilation time is increased because the + template code is being compiled repeatedly. Code written for this + model tends to include definitions of all templates in the header + file, since they must be seen to be instantiated. + + Cfront model + The AT&T C++ translator, Cfront, solved the template instantiation + problem by creating the notion of a template repository, an + automatically maintained place where template instances are + stored. A more modern version of the repository works as follows: + As individual object files are built, the compiler places any + template definitions and instantiations encountered in the + repository. At link time, the link wrapper adds in the objects in + the repository and compiles any needed instances that were not + previously emitted. The advantages of this model are more optimal + compilation speed and the ability to use the system linker; to + implement the Borland model a compiler vendor also needs to + replace the linker. The disadvantages are vastly increased + complexity, and thus potential for error; for some code this can be + just as transparent, but in practice it can been very difficult to + build multiple programs in one directory and one program in + multiple directories. Code written for this model tends to + separate definitions of non-inline member templates into a + separate file, which should be compiled separately. + + When used with GNU ld version 2.8 or later on an ELF system such as + Linux/GNU or Solaris 2, or on Microsoft Windows, g++ supports the + Borland model. On other systems, g++ implements neither automatic + model. + + A future version of g++ will support a hybrid model whereby the + compiler will emit any instantiations for which the template definition + is included in the compile, and store template definitions and + instantiation context information into the object file for the rest. + The link wrapper will extract that information as necessary and invoke + the compiler to produce the remaining instantiations. The linker will + then combine duplicate instantiations. + + In the mean time, you have the following options for dealing with + template instantiations: + + 1. Compile your template-using code with `-frepo'. The compiler will + generate files with the extension `.rpo' listing all of the + template instantiations used in the corresponding object files + which could be instantiated there; the link wrapper, `collect2', + will then update the `.rpo' files to tell the compiler where to + place those instantiations and rebuild any affected object files. + The link-time overhead is negligible after the first pass, as the + compiler will continue to place the instantiations in the same + files. + + This is your best option for application code written for the + Borland model, as it will just work. Code written for the Cfront + model will need to be modified so that the template definitions + are available at one or more points of instantiation; usually this + is as simple as adding `#include ' to the end of each + template header. + + For library code, if you want the library to provide all of the + template instantiations it needs, just try to link all of its + object files together; the link will fail, but cause the + instantiations to be generated as a side effect. Be warned, + however, that this may cause conflicts if multiple libraries try + to provide the same instantiations. For greater control, use + explicit instantiation as described in the next option. + + 2. Compile your code with `-fno-implicit-templates' to disable the + implicit generation of template instances, and explicitly + instantiate all the ones you use. This approach requires more + knowledge of exactly which instances you need than do the others, + but it's less mysterious and allows greater control. You can + scatter the explicit instantiations throughout your program, + perhaps putting them in the translation units where the instances + are used or the translation units that define the templates + themselves; you can put all of the explicit instantiations you + need into one big file; or you can create small files like + + #include "Foo.h" + #include "Foo.cc" + + template class Foo; + template ostream& operator << + (ostream&, const Foo&); + + for each of the instances you need, and create a template + instantiation library from those. + + If you are using Cfront-model code, you can probably get away with + not using `-fno-implicit-templates' when compiling files that don't + `#include' the member template definitions. + + If you use one big file to do the instantiations, you may want to + compile it without `-fno-implicit-templates' so you get all of the + instances required by your explicit instantiations (but not by any + other files) without having to specify them as well. + + g++ has extended the template instantiation syntax outlined in the + Working Paper to allow forward declaration of explicit + instantiations (with `extern'), instantiation of the compiler + support data for a template class (i.e. the vtable) without + instantiating any of its members (with `inline'), and + instantiation of only the static data members of a template class, + without the support data or member functions (with (`static'): + + extern template int max (int, int); + inline template class Foo; + static template class Foo; + + 3. Do nothing. Pretend g++ does implement automatic instantiation + management. Code written for the Borland model will work fine, but + each translation unit will contain instances of each of the + templates it uses. In a large program, this can lead to an + unacceptable amount of code duplication. + + 4. Add `#pragma interface' to all files containing template + definitions. For each of these files, add `#pragma implementation + "FILENAME"' to the top of some `.C' file which `#include's it. + Then compile everything with `-fexternal-templates'. The + templates will then only be expanded in the translation unit which + implements them (i.e. has a `#pragma implementation' line for the + file where they live); all other files will use external + references. If you're lucky, everything should work properly. If + you get undefined symbol errors, you need to make sure that each + template instance which is used in the program is used in the file + which implements that template. If you don't have any use for a + particular instance in that file, you can just instantiate it + explicitly, using the syntax from the latest C++ working paper: + + template class A; + template ostream& operator << (ostream&, const A&); + + This strategy will work with code written for either model. If + you are using code written for the Cfront model, the file + containing a class template and the file containing its member + templates should be implemented in the same translation unit. + + 5. A slight variation on this approach is to use the flag + `-falt-external-templates' instead. This flag causes template + instances to be emitted in the translation unit that implements the + header where they are first instantiated, rather than the one which + implements the file where the templates are defined. This header + must be the same in all translation units, or things are likely to + break. + + *Note Declarations and Definitions in One Header: C++ Interface, + for more discussion of these pragmas. + +  + File: gcc.info, Node: Bound member functions, Next: C++ Attributes, Prev: Template Instantiation, Up: C++ Extensions + + Extracting the function pointer from a bound pointer to member function + ======================================================================= + + In C++, pointer to member functions (PMFs) are implemented using a + wide pointer of sorts to handle all the possible call mechanisms; the + PMF needs to store information about how to adjust the `this' pointer, + and if the function pointed to is virtual, where to find the vtable, and + where in the vtable to look for the member function. If you are using + PMFs in an inner loop, you should really reconsider that decision. If + that is not an option, you can extract the pointer to the function that + would be called for a given object/PMF pair and call it directly inside + the inner loop, to save a bit of time. + + Note that you will still be paying the penalty for the call through a + function pointer; on most modern architectures, such a call defeats the + branch prediction features of the CPU. This is also true of normal + virtual function calls. + + The syntax for this extension is + + extern A a; + extern int (A::*fp)(); + typedef int (*fptr)(A *); + + fptr p = (fptr)(a.*fp); + + For PMF constants (i.e. expressions of the form `&Klasse::Member'), + no object is needed to obtain the address of the function. They can be + converted to function pointers directly: + + fptr p1 = (fptr)(&A::foo); + + You must specify `-Wno-pmf-conversions' to use this extension. + +  + File: gcc.info, Node: C++ Attributes, Next: Java Exceptions, Prev: Bound member functions, Up: C++ Extensions + + C++-Specific Variable, Function, and Type Attributes + ==================================================== + + Some attributes only make sense for C++ programs. + + `init_priority (PRIORITY)' + In Standard C++, objects defined at namespace scope are guaranteed + to be initialized in an order in strict accordance with that of + their definitions _in a given translation unit_. No guarantee is + made for initializations across translation units. However, GNU + C++ allows users to control the order of initialization of objects + defined at namespace scope with the `init_priority' attribute by + specifying a relative PRIORITY, a constant integral expression + currently bounded between 101 and 65535 inclusive. Lower numbers + indicate a higher priority. + + In the following example, `A' would normally be created before + `B', but the `init_priority' attribute has reversed that order: + + Some_Class A __attribute__ ((init_priority (2000))); + Some_Class B __attribute__ ((init_priority (543))); + + Note that the particular values of PRIORITY do not matter; only + their relative ordering. + + `java_interface' + This type attribute informs C++ that the class is a Java + interface. It may only be applied to classes declared within an + `extern "Java"' block. Calls to methods declared in this + interface will be dispatched using GCJ's interface table + mechanism, instead of regular virtual table dispatch. + + +  + File: gcc.info, Node: Java Exceptions, Next: Deprecated Features, Prev: C++ Attributes, Up: C++ Extensions + + Java Exceptions + =============== + + The Java language uses a slightly different exception handling model + from C++. Normally, GNU C++ will automatically detect when you are + writing C++ code that uses Java exceptions, and handle them + appropriately. However, if C++ code only needs to execute destructors + when Java exceptions are thrown through it, GCC will guess incorrectly. + Sample problematic code is: + + struct S { ~S(); }; + extern void bar(); // is written in Java, and may throw exceptions + void foo() + { + S s; + bar(); + } + + The usual effect of an incorrect guess is a link failure, complaining of + a missing routine called `__gxx_personality_v0'. + + You can inform the compiler that Java exceptions are to be used in a + translation unit, irrespective of what it might think, by writing + `#pragma GCC java_exceptions' at the head of the file. This `#pragma' + must appear before any functions that throw or catch exceptions, or run + destructors when exceptions are thrown through them. + + You cannot mix Java and C++ exceptions in the same translation unit. + It is believed to be safe to throw a C++ exception from one file + through another file compiled for the Java exception model, or vice + versa, but there may be bugs in this area. + +  + File: gcc.info, Node: Deprecated Features, Next: Backwards Compatibility, Prev: Java Exceptions, Up: C++ Extensions + + Deprecated Features + =================== + + In the past, the GNU C++ compiler was extended to experiment with new + features, at a time when the C++ language was still evolving. Now that + the C++ standard is complete, some of those features are superseded by + superior alternatives. Using the old features might cause a warning in + some cases that the feature will be dropped in the future. In other + cases, the feature might be gone already. + + While the list below is not exhaustive, it documents some of the + options that are now deprecated: + + `-fexternal-templates' + `-falt-external-templates' + These are two of the many ways for g++ to implement template + instantiation. *Note Template Instantiation::. The C++ standard + clearly defines how template definitions have to be organized + across implementation units. g++ has an implicit instantiation + mechanism that should work just fine for standard-conforming code. + + `-fstrict-prototype' + `-fno-strict-prototype' + Previously it was possible to use an empty prototype parameter + list to indicate an unspecified number of parameters (like C), + rather than no parameters, as C++ demands. This feature has been + removed, except where it is required for backwards compatibility + *Note Backwards Compatibility::. + + The named return value extension has been deprecated, and is now + removed from g++. + + The use of initializer lists with new expressions has been + deprecated, and is now removed from g++. + + Floating and complex non-type template parameters have been + deprecated, and are now removed from g++. + + The implicit typename extension has been deprecated and will be + removed from g++ at some point. In some cases g++ determines that a + dependant type such as `TPL::X' is a type without needing a + `typename' keyword, contrary to the standard. + +  + File: gcc.info, Node: Backwards Compatibility, Prev: Deprecated Features, Up: C++ Extensions + + Backwards Compatibility + ======================= + + Now that there is a definitive ISO standard C++, G++ has a + specification to adhere to. The C++ language evolved over time, and + features that used to be acceptable in previous drafts of the standard, + such as the ARM [Annotated C++ Reference Manual], are no longer + accepted. In order to allow compilation of C++ written to such drafts, + G++ contains some backwards compatibilities. _All such backwards + compatibility features are liable to disappear in future versions of + G++._ They should be considered deprecated *Note Deprecated Features::. + + `For scope' + If a variable is declared at for scope, it used to remain in scope + until the end of the scope which contained the for statement + (rather than just within the for scope). G++ retains this, but + issues a warning, if such a variable is accessed outside the for + scope. + + `Implicit C language' + Old C system header files did not contain an `extern "C" {...}' + scope to set the language. On such systems, all header files are + implicitly scoped inside a C language scope. Also, an empty + prototype `()' will be treated as an unspecified number of + arguments, rather than no arguments, as C++ demands. + +  + File: gcc.info, Node: Objective-C, Next: Compatibility, Prev: C++ Extensions, Up: Top + + GNU Objective-C runtime features + ******************************** + + This document is meant to describe some of the GNU Objective-C + runtime features. It is not intended to teach you Objective-C, there + are several resources on the Internet that present the language. + Questions and comments about this document to Ovidiu Predescu + . + + * Menu: + + * Executing code before main:: + * Type encoding:: + * Garbage Collection:: + * Constant string objects:: + * compatibility_alias:: + +  + File: gcc.info, Node: Executing code before main, Next: Type encoding, Prev: Objective-C, Up: Objective-C + + `+load': Executing code before main + =================================== + + The GNU Objective-C runtime provides a way that allows you to execute + code before the execution of the program enters the `main' function. + The code is executed on a per-class and a per-category basis, through a + special class method `+load'. + + This facility is very useful if you want to initialize global + variables which can be accessed by the program directly, without + sending a message to the class first. The usual way to initialize + global variables, in the `+initialize' method, might not be useful + because `+initialize' is only called when the first message is sent to a + class object, which in some cases could be too late. + + Suppose for example you have a `FileStream' class that declares + `Stdin', `Stdout' and `Stderr' as global variables, like below: + + + FileStream *Stdin = nil; + FileStream *Stdout = nil; + FileStream *Stderr = nil; + + @implementation FileStream + + + (void)initialize + { + Stdin = [[FileStream new] initWithFd:0]; + Stdout = [[FileStream new] initWithFd:1]; + Stderr = [[FileStream new] initWithFd:2]; + } + + /* Other methods here */ + @end + + In this example, the initialization of `Stdin', `Stdout' and + `Stderr' in `+initialize' occurs too late. The programmer can send a + message to one of these objects before the variables are actually + initialized, thus sending messages to the `nil' object. The + `+initialize' method which actually initializes the global variables is + not invoked until the first message is sent to the class object. The + solution would require these variables to be initialized just before + entering `main'. + + The correct solution of the above problem is to use the `+load' + method instead of `+initialize': + + + @implementation FileStream + + + (void)load + { + Stdin = [[FileStream new] initWithFd:0]; + Stdout = [[FileStream new] initWithFd:1]; + Stderr = [[FileStream new] initWithFd:2]; + } + + /* Other methods here */ + @end + + The `+load' is a method that is not overridden by categories. If a + class and a category of it both implement `+load', both methods are + invoked. This allows some additional initializations to be performed in + a category. + + This mechanism is not intended to be a replacement for `+initialize'. + You should be aware of its limitations when you decide to use it + instead of `+initialize'. + + * Menu: + + * What you can and what you cannot do in +load:: + +  + File: gcc.info, Node: What you can and what you cannot do in +load, Prev: Executing code before main, Up: Executing code before main + + What you can and what you cannot do in `+load' + ---------------------------------------------- + + The `+load' implementation in the GNU runtime guarantees you the + following things: + + * you can write whatever C code you like; + + * you can send messages to Objective-C constant strings (`@"this is a + constant string"'); + + * you can allocate and send messages to objects whose class is + implemented in the same file; + + * the `+load' implementation of all super classes of a class are + executed before the `+load' of that class is executed; + + * the `+load' implementation of a class is executed before the + `+load' implementation of any category. + + + In particular, the following things, even if they can work in a + particular case, are not guaranteed: + + * allocation of or sending messages to arbitrary objects; + + * allocation of or sending messages to objects whose classes have a + category implemented in the same file; + + + You should make no assumptions about receiving `+load' in sibling + classes when you write `+load' of a class. The order in which sibling + classes receive `+load' is not guaranteed. + + The order in which `+load' and `+initialize' are called could be + problematic if this matters. If you don't allocate objects inside + `+load', it is guaranteed that `+load' is called before `+initialize'. + If you create an object inside `+load' the `+initialize' method of + object's class is invoked even if `+load' was not invoked. Note if you + explicitly call `+load' on a class, `+initialize' will be called first. + To avoid possible problems try to implement only one of these methods. + + The `+load' method is also invoked when a bundle is dynamically + loaded into your running program. This happens automatically without + any intervening operation from you. When you write bundles and you + need to write `+load' you can safely create and send messages to + objects whose classes already exist in the running program. The same + restrictions as above apply to classes defined in bundle. + +  + File: gcc.info, Node: Type encoding, Next: Garbage Collection, Prev: Executing code before main, Up: Objective-C + + Type encoding + ============= + + The Objective-C compiler generates type encodings for all the types. + These type encodings are used at runtime to find out information about + selectors and methods and about objects and classes. + + The types are encoded in the following way: + + `char' `c' + `unsigned char' `C' + `short' `s' + `unsigned short' `S' + `int' `i' + `unsigned int' `I' + `long' `l' + `unsigned long' `L' + `long long' `q' + `unsigned long `Q' + long' + `float' `f' + `double' `d' + `void' `v' + `id' `@' + `Class' `#' + `SEL' `:' + `char*' `*' + unknown type `?' + bit-fields `b' followed by the starting position of the + bit-field, the type of the bit-field and the size of + the bit-field (the bit-fields encoding was changed + from the NeXT's compiler encoding, see below) + + The encoding of bit-fields has changed to allow bit-fields to be + properly handled by the runtime functions that compute sizes and + alignments of types that contain bit-fields. The previous encoding + contained only the size of the bit-field. Using only this information + it is not possible to reliably compute the size occupied by the + bit-field. This is very important in the presence of the Boehm's + garbage collector because the objects are allocated using the typed + memory facility available in this collector. The typed memory + allocation requires information about where the pointers are located + inside the object. + + The position in the bit-field is the position, counting in bits, of + the bit closest to the beginning of the structure. + + The non-atomic types are encoded as follows: + + pointers `^' followed by the pointed type. + arrays `[' followed by the number of elements in the array + followed by the type of the elements followed by `]' + structures `{' followed by the name of the structure (or `?' if the + structure is unnamed), the `=' sign, the type of the + members and by `}' + unions `(' followed by the name of the structure (or `?' if the + union is unnamed), the `=' sign, the type of the members + followed by `)' + + Here are some types and their encodings, as they are generated by the + compiler on an i386 machine: + + + Objective-C type Compiler encoding + int a[10]; `[10i]' + struct { `{?=i[3f]b128i3b131i2c}' + int i; + float f[3]; + int a:3; + int b:2; + char c; + } + + + In addition to the types the compiler also encodes the type + specifiers. The table below describes the encoding of the current + Objective-C type specifiers: + + + Specifier Encoding + `const' `r' + `in' `n' + `inout' `N' + `out' `o' + `bycopy' `O' + `oneway' `V' + + + The type specifiers are encoded just before the type. Unlike types + however, the type specifiers are only encoded when they appear in method + argument types. + +  + File: gcc.info, Node: Garbage Collection, Next: Constant string objects, Prev: Type encoding, Up: Objective-C + + Garbage Collection + ================== + + Support for a new memory management policy has been added by using a + powerful conservative garbage collector, known as the + Boehm-Demers-Weiser conservative garbage collector. It is available + from `http://www.hpl.hp.com/personal/Hans_Boehm/gc/'. + + To enable the support for it you have to configure the compiler + using an additional argument, `--enable-objc-gc'. You need to have + garbage collector installed before building the compiler. This will + build an additional runtime library which has several enhancements to + support the garbage collector. The new library has a new name, + `libobjc_gc.a' to not conflict with the non-garbage-collected library. + + When the garbage collector is used, the objects are allocated using + the so-called typed memory allocation mechanism available in the + Boehm-Demers-Weiser collector. This mode requires precise information + on where pointers are located inside objects. This information is + computed once per class, immediately after the class has been + initialized. + + There is a new runtime function `class_ivar_set_gcinvisible()' which + can be used to declare a so-called "weak pointer" reference. Such a + pointer is basically hidden for the garbage collector; this can be + useful in certain situations, especially when you want to keep track of + the allocated objects, yet allow them to be collected. This kind of + pointers can only be members of objects, you cannot declare a global + pointer as a weak reference. Every type which is a pointer type can be + declared a weak pointer, including `id', `Class' and `SEL'. + + Here is an example of how to use this feature. Suppose you want to + implement a class whose instances hold a weak pointer reference; the + following class does this: + + + @interface WeakPointer : Object + { + const void* weakPointer; + } + + - initWithPointer:(const void*)p; + - (const void*)weakPointer; + @end + + + @implementation WeakPointer + + + (void)initialize + { + class_ivar_set_gcinvisible (self, "weakPointer", YES); + } + + - initWithPointer:(const void*)p + { + weakPointer = p; + return self; + } + + - (const void*)weakPointer + { + return weakPointer; + } + + @end + + Weak pointers are supported through a new type character specifier + represented by the `!' character. The `class_ivar_set_gcinvisible()' + function adds or removes this specifier to the string type description + of the instance variable named as argument. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-18 gcc-3.2.3/gcc/doc/gcc.info-18 *** gcc-3.2.2/gcc/doc/gcc.info-18 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-18 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,985 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Constant string objects, Next: compatibility_alias, Prev: Garbage Collection, Up: Objective-C + + Constant string objects + ======================= + + GNU Objective-C provides constant string objects that are generated + directly by the compiler. You declare a constant string object by + prefixing a C constant string with the character `@': + + id myString = @"this is a constant string object"; + + The constant string objects are usually instances of the + `NXConstantString' class which is provided by the GNU Objective-C + runtime. To get the definition of this class you must include the + `objc/NXConstStr.h' header file. + + User defined libraries may want to implement their own constant + string class. To be able to support them, the GNU Objective-C compiler + provides a new command line options + `-fconstant-string-class=CLASS-NAME'. The provided class should adhere + to a strict structure, the same as `NXConstantString''s structure: + + + @interface NXConstantString : Object + { + char *c_string; + unsigned int len; + } + @end + + User class libraries may choose to inherit the customized constant + string class from a different class than `Object'. There is no + requirement in the methods the constant string class has to implement. + + When a file is compiled with the `-fconstant-string-class' option, + all the constant string objects will be instances of the class specified + as argument to this option. It is possible to have multiple compilation + units referring to different constant string classes, neither the + compiler nor the linker impose any restrictions in doing this. + +  + File: gcc.info, Node: compatibility_alias, Prev: Constant string objects, Up: Objective-C + + compatibility_alias + =================== + + This is a feature of the Objective-C compiler rather than of the + runtime, anyway since it is documented nowhere and its existence was + forgotten, we are documenting it here. + + The keyword `@compatibility_alias' allows you to define a class name + as equivalent to another class name. For example: + + @compatibility_alias WOApplication GSWApplication; + + tells the compiler that each time it encounters `WOApplication' as a + class name, it should replace it with `GSWApplication' (that is, + `WOApplication' is just an alias for `GSWApplication'). + + There are some constraints on how this can be used-- + + * `WOApplication' (the alias) must not be an existing class; + + * `GSWApplication' (the real class) must be an existing class. + + +  + File: gcc.info, Node: Compatibility, Next: Gcov, Prev: Objective-C, Up: Top + + Binary Compatibility + ******************** + + Binary compatibility encompasses several related concepts: + + "application binary interface (ABI)" + The set of runtime conventions followed by all of the tools that + deal with binary representations of a program, including + compilers, assemblers, linkers, and language runtime support. + Some ABIs are formal with a written specification, possibly + designed by multiple interested parties. Others are simply the + way things are actually done by a particular set of tools. + + "ABI conformance" + A compiler conforms to an ABI if it generates code that follows + all of the specifications enumerated by that ABI. A library + conforms to an ABI if it is implemented according to that ABI. An + application conforms to an ABI if it is built using tools that + conform to that ABI and does not contain source code that + specifically changes behavior specified by the ABI. + + "calling conventions" + Calling conventions are a subset of an ABI that specify of how + arguments are passed and function results are returned. + + "interoperability" + Different sets of tools are interoperable if they generate files + that can be used in the same program. The set of tools includes + compilers, assemblers, linkers, libraries, header files, startup + files, and debuggers. Binaries produced by different sets of + tools are not interoperable unless they implement the same ABI. + This applies to different versions of the same tools as well as + tools from different vendors. + + "intercallability" + Whether a function in a binary built by one set of tools can call a + function in a binary built by a different set of tools is a subset + of interoperability. + + "implementation-defined features" + Language standards include lists of implementation-defined + features whose behavior can vary from one implementation to + another. Some of these features are normally covered by a + platform's ABI and others are not. The features that are not + covered by an ABI generally affect how a program behaves, but not + intercallability. + + "compatibility" + Conformance to the same ABI and the same behavior of + implementation-defined features are both relevant for + compatibility. + + The application binary interface implemented by a C or C++ compiler + affects code generation and runtime support for: + + * size and alignment of data types + + * layout of structured types + + * calling conventions + + * register usage conventions + + * interfaces for runtime arithmetic support + + * object file formats + + In addition, the application binary interface implemented by a C++ + compiler affects code generation and runtime support for: + * name mangling + + * exception handling + + * invoking constructors and destructors + + * layout, alignment, and padding of classes + + * layout and alignment of virtual tables + + Some GCC compilation options cause the compiler to generate code that + does not conform to the platform's default ABI. Other options cause + different program behavior for implementation-defined features that are + not covered by an ABI. These options are provided for consistency with + other compilers that do not follow the platform's default ABI or the + usual behavior of implementation-defined features for the platform. Be + very careful about using such options. + + Most platforms have a well-defined ABI that covers C code, but ABIs + that cover C++ functionality are not yet common. + + Starting with GCC 3.2, GCC binary conventions for C++ are based on a + written, vendor-neutral C++ ABI that was designed to be specific to + 64-bit Itanium but also includes generic specifications that apply to + any platform. This C++ ABI is also implemented by other compiler + vendors on some platforms, notably GNU/Linux and BSD systems. We have + tried hard to provide a stable ABI that will be compatible with future + GCC releases, but it is possible that we will encounter problems that + make this difficult. Such problems could include different + interpretations of the C++ ABI by different vendors, bugs in the ABI, or + bugs in the implementation of the ABI in different compilers. GCC's + `-Wabi' switch warns when G++ generates code that is probably not + compatible with the C++ ABI. + + The C++ library used with a C++ compiler includes the Standard C++ + Library, with functionality defined in the C++ Standard, plus language + runtime support. The runtime support is included in a C++ ABI, but + there is no formal ABI for the Standard C++ Library. Two + implementations of that library are interoperable if one follows the + de-facto ABI of the other and if they are both built with the same + compiler, or with compilers that conform to the same ABI for C++ + compiler and runtime support. + + When G++ and another C++ compiler conform to the same C++ ABI, but + the implementations of the Standard C++ Library that they normally use + do not follow the same ABI for the Standard C++ Library, object files + built with those compilers can be used in the same program only if they + use the same C++ library. This requires specifying the location of the + C++ library header files when invoking the compiler whose usual library + is not being used. The location of GCC's C++ header files depends on + how the GCC build was configured, but can be seen by using the G++ `-v' + option. With default configuration options for G++ 3.2 the compile + line for a different C++ compiler needs to include + + -IGCC_INSTALL_DIRECTORY/include/c++/3.2 + + Similarly, compiling code with G++ that must use a C++ library other + than the GNU C++ library requires specifying the location of the header + files for that other library. + + The most straightforward way to link a program to use a particular + C++ library is to use a C++ driver that specifies that C++ library by + default. The `g++' driver, for example, tells the linker where to find + GCC's C++ library (`libstdc++') plus the other libraries and startup + files it needs, in the proper order. + + If a program must use a different C++ library and it's not possible + to do the final link using a C++ driver that uses that library by + default, it is necessary to tell `g++' the location and name of that + library. It might also be necessary to specify different startup files + and other runtime support libraries, and to suppress the use of GCC's + support libraries with one or more of the options `-nostdlib', + `-nostartfiles', and `-nodefaultlibs'. + +  + File: gcc.info, Node: Gcov, Next: Trouble, Prev: Compatibility, Up: Top + + `gcov'--a Test Coverage Program + ******************************* + + `gcov' is a tool you can use in conjunction with GCC to test code + coverage in your programs. + + * Menu: + + * Gcov Intro:: Introduction to gcov. + * Invoking Gcov:: How to use gcov. + * Gcov and Optimization:: Using gcov with GCC optimization. + * Gcov Data Files:: The files used by gcov. + +  + File: gcc.info, Node: Gcov Intro, Next: Invoking Gcov, Up: Gcov + + Introduction to `gcov' + ====================== + + `gcov' is a test coverage program. Use it in concert with GCC to + analyze your programs to help create more efficient, faster running + code. You can use `gcov' as a profiling tool to help discover where + your optimization efforts will best affect your code. You can also use + `gcov' along with the other profiling tool, `gprof', to assess which + parts of your code use the greatest amount of computing time. + + Profiling tools help you analyze your code's performance. Using a + profiler such as `gcov' or `gprof', you can find out some basic + performance statistics, such as: + + * how often each line of code executes + + * what lines of code are actually executed + + * how much computing time each section of code uses + + Once you know these things about how your code works when compiled, + you can look at each module to see which modules should be optimized. + `gcov' helps you determine where to work on optimization. + + Software developers also use coverage testing in concert with + testsuites, to make sure software is actually good enough for a release. + Testsuites can verify that a program works as expected; a coverage + program tests to see how much of the program is exercised by the + testsuite. Developers can then determine what kinds of test cases need + to be added to the testsuites to create both better testing and a better + final product. + + You should compile your code without optimization if you plan to use + `gcov' because the optimization, by combining some lines of code into + one function, may not give you as much information as you need to look + for `hot spots' where the code is using a great deal of computer time. + Likewise, because `gcov' accumulates statistics by line (at the lowest + resolution), it works best with a programming style that places only + one statement on each line. If you use complicated macros that expand + to loops or to other control structures, the statistics are less + helpful--they only report on the line where the macro call appears. If + your complex macros behave like functions, you can replace them with + inline functions to solve this problem. + + `gcov' creates a logfile called `SOURCEFILE.gcov' which indicates + how many times each line of a source file `SOURCEFILE.c' has executed. + You can use these logfiles along with `gprof' to aid in fine-tuning the + performance of your programs. `gprof' gives timing information you can + use along with the information you get from `gcov'. + + `gcov' works only on code compiled with GCC. It is not compatible + with any other profiling or test coverage mechanism. + +  + File: gcc.info, Node: Invoking Gcov, Next: Gcov and Optimization, Prev: Gcov Intro, Up: Gcov + + Invoking gcov + ============= + + gcov [OPTIONS] SOURCEFILE + + `gcov' accepts the following options: + + `-h' + `--help' + Display help about using `gcov' (on the standard output), and exit + without doing any further processing. + + `-v' + `--version' + Display the `gcov' version number (on the standard output), and + exit without doing any further processing. + + `-b' + `--branch-probabilities' + Write branch frequencies to the output file, and write branch + summary info to the standard output. This option allows you to + see how often each branch in your program was taken. + + `-c' + `--branch-counts' + Write branch frequencies as the number of branches taken, rather + than the percentage of branches taken. + + `-n' + `--no-output' + Do not create the `gcov' output file. + + `-l' + `--long-file-names' + Create long file names for included source files. For example, if + the header file `x.h' contains code, and was included in the file + `a.c', then running `gcov' on the file `a.c' will produce an + output file called `a.c.x.h.gcov' instead of `x.h.gcov'. This can + be useful if `x.h' is included in multiple source files. + + `-f' + `--function-summaries' + Output summaries for each function in addition to the file level + summary. + + `-o DIRECTORY' + `--object-directory DIRECTORY' + The directory where the object files live. Gcov will search for + `.bb', `.bbg', and `.da' files in this directory. + + When using `gcov', you must first compile your program with two + special GCC options: `-fprofile-arcs -ftest-coverage'. This tells the + compiler to generate additional information needed by gcov (basically a + flow graph of the program) and also includes additional code in the + object files for generating the extra profiling information needed by + gcov. These additional files are placed in the directory where the + source code is located. + + Running the program will cause profile output to be generated. For + each source file compiled with `-fprofile-arcs', an accompanying `.da' + file will be placed in the source directory. + + Running `gcov' with your program's source file names as arguments + will now produce a listing of the code along with frequency of execution + for each line. For example, if your program is called `tmp.c', this is + what you see when you use the basic `gcov' facility: + + $ gcc -fprofile-arcs -ftest-coverage tmp.c + $ a.out + $ gcov tmp.c + 87.50% of 8 source lines executed in file tmp.c + Creating tmp.c.gcov. + + The file `tmp.c.gcov' contains output from `gcov'. Here is a sample: + + main() + { + 1 int i, total; + + 1 total = 0; + + 11 for (i = 0; i < 10; i++) + 10 total += i; + + 1 if (total != 45) + ###### printf ("Failure\n"); + else + 1 printf ("Success\n"); + 1 } + + When you use the `-b' option, your output looks like this: + + $ gcov -b tmp.c + 87.50% of 8 source lines executed in file tmp.c + 80.00% of 5 branches executed in file tmp.c + 80.00% of 5 branches taken at least once in file tmp.c + 50.00% of 2 calls executed in file tmp.c + Creating tmp.c.gcov. + + Here is a sample of a resulting `tmp.c.gcov' file: + + main() + { + 1 int i, total; + + 1 total = 0; + + 11 for (i = 0; i < 10; i++) + branch 0 taken = 91% + branch 1 taken = 100% + branch 2 taken = 100% + 10 total += i; + + 1 if (total != 45) + branch 0 taken = 100% + ###### printf ("Failure\n"); + call 0 never executed + branch 1 never executed + else + 1 printf ("Success\n"); + call 0 returns = 100% + 1 } + + For each basic block, a line is printed after the last line of the + basic block describing the branch or call that ends the basic block. + There can be multiple branches and calls listed for a single source + line if there are multiple basic blocks that end on that line. In this + case, the branches and calls are each given a number. There is no + simple way to map these branches and calls back to source constructs. + In general, though, the lowest numbered branch or call will correspond + to the leftmost construct on the source line. + + For a branch, if it was executed at least once, then a percentage + indicating the number of times the branch was taken divided by the + number of times the branch was executed will be printed. Otherwise, the + message "never executed" is printed. + + For a call, if it was executed at least once, then a percentage + indicating the number of times the call returned divided by the number + of times the call was executed will be printed. This will usually be + 100%, but may be less for functions call `exit' or `longjmp', and thus + may not return every time they are called. + + The execution counts are cumulative. If the example program were + executed again without removing the `.da' file, the count for the + number of times each line in the source was executed would be added to + the results of the previous run(s). This is potentially useful in + several ways. For example, it could be used to accumulate data over a + number of program runs as part of a test verification suite, or to + provide more accurate long-term information over a large number of + program runs. + + The data in the `.da' files is saved immediately before the program + exits. For each source file compiled with `-fprofile-arcs', the + profiling code first attempts to read in an existing `.da' file; if the + file doesn't match the executable (differing number of basic block + counts) it will ignore the contents of the file. It then adds in the + new execution counts and finally writes the data to the file. + +  + File: gcc.info, Node: Gcov and Optimization, Next: Gcov Data Files, Prev: Invoking Gcov, Up: Gcov + + Using `gcov' with GCC Optimization + ================================== + + If you plan to use `gcov' to help optimize your code, you must first + compile your program with two special GCC options: `-fprofile-arcs + -ftest-coverage'. Aside from that, you can use any other GCC options; + but if you want to prove that every single line in your program was + executed, you should not compile with optimization at the same time. + On some machines the optimizer can eliminate some simple code lines by + combining them with other lines. For example, code like this: + + if (a != b) + c = 1; + else + c = 0; + + can be compiled into one instruction on some machines. In this case, + there is no way for `gcov' to calculate separate execution counts for + each line because there isn't separate code for each line. Hence the + `gcov' output looks like this if you compiled the program with + optimization: + + 100 if (a != b) + 100 c = 1; + 100 else + 100 c = 0; + + The output shows that this block of code, combined by optimization, + executed 100 times. In one sense this result is correct, because there + was only one instruction representing all four of these lines. However, + the output does not indicate how many times the result was 0 and how + many times the result was 1. + +  + File: gcc.info, Node: Gcov Data Files, Prev: Gcov and Optimization, Up: Gcov + + Brief description of `gcov' data files + ====================================== + + `gcov' uses three files for doing profiling. The names of these + files are derived from the original _source_ file by substituting the + file suffix with either `.bb', `.bbg', or `.da'. All of these files + are placed in the same directory as the source file, and contain data + stored in a platform-independent method. + + The `.bb' and `.bbg' files are generated when the source file is + compiled with the GCC `-ftest-coverage' option. The `.bb' file + contains a list of source files (including headers), functions within + those files, and line numbers corresponding to each basic block in the + source file. + + The `.bb' file format consists of several lists of 4-byte integers + which correspond to the line numbers of each basic block in the file. + Each list is terminated by a line number of 0. A line number of -1 is + used to designate that the source file name (padded to a 4-byte + boundary and followed by another -1) follows. In addition, a line + number of -2 is used to designate that the name of a function (also + padded to a 4-byte boundary and followed by a -2) follows. + + The `.bbg' file is used to reconstruct the program flow graph for + the source file. It contains a list of the program flow arcs (possible + branches taken from one basic block to another) for each function which, + in combination with the `.bb' file, enables gcov to reconstruct the + program flow. + + In the `.bbg' file, the format is: + number of basic blocks for function #0 (4-byte number) + total number of arcs for function #0 (4-byte number) + count of arcs in basic block #0 (4-byte number) + destination basic block of arc #0 (4-byte number) + flag bits (4-byte number) + destination basic block of arc #1 (4-byte number) + flag bits (4-byte number) + ... + destination basic block of arc #N (4-byte number) + flag bits (4-byte number) + count of arcs in basic block #1 (4-byte number) + destination basic block of arc #0 (4-byte number) + flag bits (4-byte number) + ... + + A -1 (stored as a 4-byte number) is used to separate each function's + list of basic blocks, and to verify that the file has been read + correctly. + + The `.da' file is generated when a program containing object files + built with the GCC `-fprofile-arcs' option is executed. A separate + `.da' file is created for each source file compiled with this option, + and the name of the `.da' file is stored as an absolute pathname in the + resulting object file. This path name is derived from the source file + name by substituting a `.da' suffix. + + The format of the `.da' file is fairly simple. The first 8-byte + number is the number of counts in the file, followed by the counts + (stored as 8-byte numbers). Each count corresponds to the number of + times each arc in the program is executed. The counts are cumulative; + each time the program is executed, it attempts to combine the existing + `.da' files with the new counts for this invocation of the program. It + ignores the contents of any `.da' files whose number of arcs doesn't + correspond to the current program, and merely overwrites them instead. + + All three of these files use the functions in `gcov-io.h' to store + integers; the functions in this header provide a machine-independent + mechanism for storing and retrieving data from a stream. + +  + File: gcc.info, Node: Trouble, Next: Bugs, Prev: Gcov, Up: Top + + Known Causes of Trouble with GCC + ******************************** + + This section describes known problems that affect users of GCC. Most + of these are not GCC bugs per se--if they were, we would fix them. But + the result for a user may be like the result of a bug. + + Some of these problems are due to bugs in other software, some are + missing features that are too much work to add, and some are places + where people's opinions differ as to what is best. + + * Menu: + + * Actual Bugs:: Bugs we will fix later. + * Cross-Compiler Problems:: Common problems of cross compiling with GCC. + * Interoperation:: Problems using GCC with other compilers, + and with certain linkers, assemblers and debuggers. + * External Bugs:: Problems compiling certain programs. + * Incompatibilities:: GCC is incompatible with traditional C. + * Fixed Headers:: GCC uses corrected versions of system header files. + This is necessary, but doesn't always work smoothly. + * Standard Libraries:: GCC uses the system C library, which might not be + compliant with the ISO C standard. + * Disappointments:: Regrettable things we can't change, but not quite bugs. + * C++ Misunderstandings:: Common misunderstandings with GNU C++. + * Protoize Caveats:: Things to watch out for when using `protoize'. + * Non-bugs:: Things we think are right, but some others disagree. + * Warnings and Errors:: Which problems in your code get warnings, + and which get errors. + +  + File: gcc.info, Node: Actual Bugs, Next: Cross-Compiler Problems, Up: Trouble + + Actual Bugs We Haven't Fixed Yet + ================================ + + * The `fixincludes' script interacts badly with automounters; if the + directory of system header files is automounted, it tends to be + unmounted while `fixincludes' is running. This would seem to be a + bug in the automounter. We don't know any good way to work around + it. + + * The `fixproto' script will sometimes add prototypes for the + `sigsetjmp' and `siglongjmp' functions that reference the + `jmp_buf' type before that type is defined. To work around this, + edit the offending file and place the typedef in front of the + prototypes. + + * When `-pedantic-errors' is specified, GCC will incorrectly give an + error message when a function name is specified in an expression + involving the comma operator. + +  + File: gcc.info, Node: Cross-Compiler Problems, Next: Interoperation, Prev: Actual Bugs, Up: Trouble + + Cross-Compiler Problems + ======================= + + You may run into problems with cross compilation on certain machines, + for several reasons. + + * Cross compilation can run into trouble for certain machines because + some target machines' assemblers require floating point numbers to + be written as _integer_ constants in certain contexts. + + The compiler writes these integer constants by examining the + floating point value as an integer and printing that integer, + because this is simple to write and independent of the details of + the floating point representation. But this does not work if the + compiler is running on a different machine with an incompatible + floating point format, or even a different byte-ordering. + + In addition, correct constant folding of floating point values + requires representing them in the target machine's format. (The C + standard does not quite require this, but in practice it is the + only way to win.) + + It is now possible to overcome these problems by defining macros + such as `REAL_VALUE_TYPE'. But doing so is a substantial amount of + work for each target machine. *Note Cross Compilation and + Floating Point: (gccint)Cross-compilation. + + * At present, the program `mips-tfile' which adds debug support to + object files on MIPS systems does not work in a cross compile + environment. + +  + File: gcc.info, Node: Interoperation, Next: External Bugs, Prev: Cross-Compiler Problems, Up: Trouble + + Interoperation + ============== + + This section lists various difficulties encountered in using GCC + together with other compilers or with the assemblers, linkers, + libraries and debuggers on certain systems. + + * On many platforms, GCC supports a different ABI for C++ than do + other compilers, so the object files compiled by GCC cannot be + used with object files generated by another C++ compiler. + + An area where the difference is most apparent is name mangling. + The use of different name mangling is intentional, to protect you + from more subtle problems. Compilers differ as to many internal + details of C++ implementation, including: how class instances are + laid out, how multiple inheritance is implemented, and how virtual + function calls are handled. If the name encoding were made the + same, your programs would link against libraries provided from + other compilers--but the programs would then crash when run. + Incompatible libraries are then detected at link time, rather than + at run time. + + * Older GDB versions sometimes fail to read the output of GCC version + 2. If you have trouble, get GDB version 4.4 or later. + + * DBX rejects some files produced by GCC, though it accepts similar + constructs in output from PCC. Until someone can supply a coherent + description of what is valid DBX input and what is not, there is + nothing I can do about these problems. You are on your own. + + * The GNU assembler (GAS) does not support PIC. To generate PIC + code, you must use some other assembler, such as `/bin/as'. + + * On some BSD systems, including some versions of Ultrix, use of + profiling causes static variable destructors (currently used only + in C++) not to be run. + + * On some SGI systems, when you use `-lgl_s' as an option, it gets + translated magically to `-lgl_s -lX11_s -lc_s'. Naturally, this + does not happen when you use GCC. You must specify all three + options explicitly. + + * On a Sparc, GCC aligns all values of type `double' on an 8-byte + boundary, and it expects every `double' to be so aligned. The Sun + compiler usually gives `double' values 8-byte alignment, with one + exception: function arguments of type `double' may not be aligned. + + As a result, if a function compiled with Sun CC takes the address + of an argument of type `double' and passes this pointer of type + `double *' to a function compiled with GCC, dereferencing the + pointer may cause a fatal signal. + + One way to solve this problem is to compile your entire program + with GCC. Another solution is to modify the function that is + compiled with Sun CC to copy the argument into a local variable; + local variables are always properly aligned. A third solution is + to modify the function that uses the pointer to dereference it via + the following function `access_double' instead of directly with + `*': + + inline double + access_double (double *unaligned_ptr) + { + union d2i { double d; int i[2]; }; + + union d2i *p = (union d2i *) unaligned_ptr; + union d2i u; + + u.i[0] = p->i[0]; + u.i[1] = p->i[1]; + + return u.d; + } + + Storing into the pointer can be done likewise with the same union. + + * On Solaris, the `malloc' function in the `libmalloc.a' library may + allocate memory that is only 4 byte aligned. Since GCC on the + Sparc assumes that doubles are 8 byte aligned, this may result in a + fatal signal if doubles are stored in memory allocated by the + `libmalloc.a' library. + + The solution is to not use the `libmalloc.a' library. Use instead + `malloc' and related functions from `libc.a'; they do not have + this problem. + + * Sun forgot to include a static version of `libdl.a' with some + versions of SunOS (mainly 4.1). This results in undefined symbols + when linking static binaries (that is, if you use `-static'). If + you see undefined symbols `_dlclose', `_dlsym' or `_dlopen' when + linking, compile and link against the file `mit/util/misc/dlsym.c' + from the MIT version of X windows. + + * The 128-bit long double format that the Sparc port supports + currently works by using the architecturally defined quad-word + floating point instructions. Since there is no hardware that + supports these instructions they must be emulated by the operating + system. Long doubles do not work in Sun OS versions 4.0.3 and + earlier, because the kernel emulator uses an obsolete and + incompatible format. Long doubles do not work in Sun OS version + 4.1.1 due to a problem in a Sun library. Long doubles do work on + Sun OS versions 4.1.2 and higher, but GCC does not enable them by + default. Long doubles appear to work in Sun OS 5.x (Solaris 2.x). + + * On HP-UX version 9.01 on the HP PA, the HP compiler `cc' does not + compile GCC correctly. We do not yet know why. However, GCC + compiled on earlier HP-UX versions works properly on HP-UX 9.01 + and can compile itself properly on 9.01. + + * On the HP PA machine, ADB sometimes fails to work on functions + compiled with GCC. Specifically, it fails to work on functions + that use `alloca' or variable-size arrays. This is because GCC + doesn't generate HP-UX unwind descriptors for such functions. It + may even be impossible to generate them. + + * Debugging (`-g') is not supported on the HP PA machine, unless you + use the preliminary GNU tools. + + * Taking the address of a label may generate errors from the HP-UX + PA assembler. GAS for the PA does not have this problem. + + * Using floating point parameters for indirect calls to static + functions will not work when using the HP assembler. There simply + is no way for GCC to specify what registers hold arguments for + static functions when using the HP assembler. GAS for the PA does + not have this problem. + + * In extremely rare cases involving some very large functions you may + receive errors from the HP linker complaining about an out of + bounds unconditional branch offset. This used to occur more often + in previous versions of GCC, but is now exceptionally rare. If + you should run into it, you can work around by making your + function smaller. + + * GCC compiled code sometimes emits warnings from the HP-UX + assembler of the form: + + (warning) Use of GR3 when + frame >= 8192 may cause conflict. + + These warnings are harmless and can be safely ignored. + + * On the IBM RS/6000, compiling code of the form + + extern int foo; + + ... foo ... + + static int foo; + + will cause the linker to report an undefined symbol `foo'. + Although this behavior differs from most other systems, it is not a + bug because redefining an `extern' variable as `static' is + undefined in ISO C. + + * In extremely rare cases involving some very large functions you may + receive errors from the AIX Assembler complaining about a + displacement that is too large. If you should run into it, you + can work around by making your function smaller. + + * The `libstdc++.a' library in GCC relies on the SVR4 dynamic linker + semantics which merges global symbols between libraries and + applications, especially necessary for C++ streams functionality. + This is not the default behavior of AIX shared libraries and + dynamic linking. `libstdc++.a' is built on AIX with + "runtime-linking" enabled so that symbol merging can occur. To + utilize this feature, the application linked with `libstdc++.a' + must include the `-Wl,-brtl' flag on the link line. G++ cannot + impose this because this option may interfere with the semantics + of the user program and users may not always use `g++' to link his + or her application. Applications are not required to use the + `-Wl,-brtl' flag on the link line--the rest of the `libstdc++.a' + library which is not dependent on the symbol merging semantics + will continue to function correctly. + + * An application can interpose its own definition of functions for + functions invoked by `libstdc++.a' with "runtime-linking" enabled + on AIX. To accomplish this the application must be linked with + "runtime-linking" option and the functions explicitly must be + exported by the application (`-Wl,-brtl,-bE:exportfile'). + + * AIX on the RS/6000 provides support (NLS) for environments outside + of the United States. Compilers and assemblers use NLS to support + locale-specific representations of various objects including + floating-point numbers (`.' vs `,' for separating decimal + fractions). There have been problems reported where the library + linked with GCC does not produce the same floating-point formats + that the assembler accepts. If you have this problem, set the + `LANG' environment variable to `C' or `En_US'. + + * Even if you specify `-fdollars-in-identifiers', you cannot + successfully use `$' in identifiers on the RS/6000 due to a + restriction in the IBM assembler. GAS supports these identifiers. + + * There is an assembler bug in versions of DG/UX prior to 5.4.2.01 + that occurs when the `fldcr' instruction is used. GCC uses + `fldcr' on the 88100 to serialize volatile memory references. Use + the option `-mno-serialize-volatile' if your version of the + assembler has this bug. + + * On VMS, GAS versions 1.38.1 and earlier may cause spurious warning + messages from the linker. These warning messages complain of + mismatched psect attributes. You can ignore them. + + * On NewsOS version 3, if you include both of the files `stddef.h' + and `sys/types.h', you get an error because there are two typedefs + of `size_t'. You should change `sys/types.h' by adding these + lines around the definition of `size_t': + + #ifndef _SIZE_T + #define _SIZE_T + ACTUAL-TYPEDEF-HERE + #endif + + * On the Alliant, the system's own convention for returning + structures and unions is unusual, and is not compatible with GCC + no matter what options are used. + + * On the IBM RT PC, the MetaWare HighC compiler (hc) uses a different + convention for structure and union returning. Use the option + `-mhc-struct-return' to tell GCC to use a convention compatible + with it. + + * On Ultrix, the Fortran compiler expects registers 2 through 5 to + be saved by function calls. However, the C compiler uses + conventions compatible with BSD Unix: registers 2 through 5 may be + clobbered by function calls. + + GCC uses the same convention as the Ultrix C compiler. You can use + these options to produce code compatible with the Fortran compiler: + + -fcall-saved-r2 -fcall-saved-r3 -fcall-saved-r4 -fcall-saved-r5 + + * On the WE32k, you may find that programs compiled with GCC do not + work with the standard shared C library. You may need to link with + the ordinary C compiler. If you do so, you must specify the + following options: + + -L/usr/local/lib/gcc-lib/we32k-att-sysv/2.8.1 -lgcc -lc_s + + The first specifies where to find the library `libgcc.a' specified + with the `-lgcc' option. + + GCC does linking by invoking `ld', just as `cc' does, and there is + no reason why it _should_ matter which compilation program you use + to invoke `ld'. If someone tracks this problem down, it can + probably be fixed easily. + + * On the Alpha, you may get assembler errors about invalid syntax as + a result of floating point constants. This is due to a bug in the + C library functions `ecvt', `fcvt' and `gcvt'. Given valid + floating point numbers, they sometimes print `NaN'. + + * On Irix 4.0.5F (and perhaps in some other versions), an assembler + bug sometimes reorders instructions incorrectly when optimization + is turned on. If you think this may be happening to you, try + using the GNU assembler; GAS version 2.1 supports ECOFF on Irix. + + Or use the `-noasmopt' option when you compile GCC with itself, + and then again when you compile your program. (This is a temporary + kludge to turn off assembler optimization on Irix.) If this + proves to be what you need, edit the assembler spec in the file + `specs' so that it unconditionally passes `-O0' to the assembler, + and never passes `-O2' or `-O3'. + +  + File: gcc.info, Node: External Bugs, Next: Incompatibilities, Prev: Interoperation, Up: Trouble + + Problems Compiling Certain Programs + =================================== + + Certain programs have problems compiling. + + * Parse errors may occur compiling X11 on a Decstation running + Ultrix 4.2 because of problems in DEC's versions of the X11 header + files `X11/Xlib.h' and `X11/Xutil.h'. People recommend adding + `-I/usr/include/mit' to use the MIT versions of the header files, + using the `-traditional' switch to turn off ISO C, or fixing the + header files by adding this: + + #ifdef __STDC__ + #define NeedFunctionPrototypes 0 + #endif + + * On various 386 Unix systems derived from System V, including SCO, + ISC, and ESIX, you may get error messages about running out of + virtual memory while compiling certain programs. + + You can prevent this problem by linking GCC with the GNU malloc + (which thus replaces the malloc that comes with the system). GNU + malloc is available as a separate package, and also in the file + `src/gmalloc.c' in the GNU Emacs 19 distribution. + + If you have installed GNU malloc as a separate library package, + use this option when you relink GCC: + + MALLOC=/usr/local/lib/libgmalloc.a + + Alternatively, if you have compiled `gmalloc.c' from Emacs 19, copy + the object file to `gmalloc.o' and use this option when you relink + GCC: + + MALLOC=gmalloc.o + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-19 gcc-3.2.3/gcc/doc/gcc.info-19 *** gcc-3.2.2/gcc/doc/gcc.info-19 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-19 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1019 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Incompatibilities, Next: Fixed Headers, Prev: External Bugs, Up: Trouble + + Incompatibilities of GCC + ======================== + + There are several noteworthy incompatibilities between GNU C and K&R + (non-ISO) versions of C. The `-traditional' option eliminates many of + these incompatibilities, _but not all_, by telling GCC to behave like a + K&R C compiler. + + * GCC normally makes string constants read-only. If several + identical-looking string constants are used, GCC stores only one + copy of the string. + + One consequence is that you cannot call `mktemp' with a string + constant argument. The function `mktemp' always alters the string + its argument points to. + + Another consequence is that `sscanf' does not work on some systems + when passed a string constant as its format control string or + input. This is because `sscanf' incorrectly tries to write into + the string constant. Likewise `fscanf' and `scanf'. + + The best solution to these problems is to change the program to use + `char'-array variables with initialization strings for these + purposes instead of string constants. But if this is not possible, + you can use the `-fwritable-strings' flag, which directs GCC to + handle string constants the same way most C compilers do. + `-traditional' also has this effect, among others. + + * `-2147483648' is positive. + + This is because 2147483648 cannot fit in the type `int', so + (following the ISO C rules) its data type is `unsigned long int'. + Negating this value yields 2147483648 again. + + * GCC does not substitute macro arguments when they appear inside of + string constants. For example, the following macro in GCC + + #define foo(a) "a" + + will produce output `"a"' regardless of what the argument A is. + + The `-traditional' option directs GCC to handle such cases (among + others) in the old-fashioned (non-ISO) fashion. + + * When you use `setjmp' and `longjmp', the only automatic variables + guaranteed to remain valid are those declared `volatile'. This is + a consequence of automatic register allocation. Consider this + function: + + jmp_buf j; + + foo () + { + int a, b; + + a = fun1 (); + if (setjmp (j)) + return a; + + a = fun2 (); + /* `longjmp (j)' may occur in `fun3'. */ + return a + fun3 (); + } + + Here `a' may or may not be restored to its first value when the + `longjmp' occurs. If `a' is allocated in a register, then its + first value is restored; otherwise, it keeps the last value stored + in it. + + If you use the `-W' option with the `-O' option, you will get a + warning when GCC thinks such a problem might be possible. + + The `-traditional' option directs GCC to put variables in the + stack by default, rather than in registers, in functions that call + `setjmp'. This results in the behavior found in traditional C + compilers. + + * Programs that use preprocessing directives in the middle of macro + arguments do not work with GCC. For example, a program like this + will not work: + + foobar ( + #define luser + hack) + + ISO C does not permit such a construct. It would make sense to + support it when `-traditional' is used, but it is too much work to + implement. + + * K&R compilers allow comments to cross over an inclusion boundary + (i.e. started in an include file and ended in the including file). + I think this would be quite ugly and can't imagine it could be + needed. + + * Declarations of external variables and functions within a block + apply only to the block containing the declaration. In other + words, they have the same scope as any other declaration in the + same place. + + In some other C compilers, a `extern' declaration affects all the + rest of the file even if it happens within a block. + + The `-traditional' option directs GCC to treat all `extern' + declarations as global, like traditional compilers. + + * In traditional C, you can combine `long', etc., with a typedef + name, as shown here: + + typedef int foo; + typedef long foo bar; + + In ISO C, this is not allowed: `long' and other type modifiers + require an explicit `int'. Because this criterion is expressed by + Bison grammar rules rather than C code, the `-traditional' flag + cannot alter it. + + * PCC allows typedef names to be used as function parameters. The + difficulty described immediately above applies here too. + + * When in `-traditional' mode, GCC allows the following erroneous + pair of declarations to appear together in a given scope: + + typedef int foo; + typedef foo foo; + + * GCC treats all characters of identifiers as significant, even when + in `-traditional' mode. According to K&R-1 (2.2), "No more than + the first eight characters are significant, although more may be + used.". Also according to K&R-1 (2.2), "An identifier is a + sequence of letters and digits; the first character must be a + letter. The underscore _ counts as a letter.", but GCC also + allows dollar signs in identifiers. + + * PCC allows whitespace in the middle of compound assignment + operators such as `+='. GCC, following the ISO standard, does not + allow this. The difficulty described immediately above applies + here too. + + * GCC complains about unterminated character constants inside of + preprocessing conditionals that fail. Some programs have English + comments enclosed in conditionals that are guaranteed to fail; if + these comments contain apostrophes, GCC will probably report an + error. For example, this code would produce an error: + + #if 0 + You can't expect this to work. + #endif + + The best solution to such a problem is to put the text into an + actual C comment delimited by `/*...*/'. However, `-traditional' + suppresses these error messages. + + * Many user programs contain the declaration `long time ();'. In the + past, the system header files on many systems did not actually + declare `time', so it did not matter what type your program + declared it to return. But in systems with ISO C headers, `time' + is declared to return `time_t', and if that is not the same as + `long', then `long time ();' is erroneous. + + The solution is to change your program to use appropriate system + headers (`' on systems with ISO C headers) and not to + declare `time' if the system header files declare it, or failing + that to use `time_t' as the return type of `time'. + + * When compiling functions that return `float', PCC converts it to a + double. GCC actually returns a `float'. If you are concerned + with PCC compatibility, you should declare your functions to return + `double'; you might as well say what you mean. + + * When compiling functions that return structures or unions, GCC + output code normally uses a method different from that used on most + versions of Unix. As a result, code compiled with GCC cannot call + a structure-returning function compiled with PCC, and vice versa. + + The method used by GCC is as follows: a structure or union which is + 1, 2, 4 or 8 bytes long is returned like a scalar. A structure or + union with any other size is stored into an address supplied by + the caller (usually in a special, fixed register, but on some + machines it is passed on the stack). The machine-description + macros `STRUCT_VALUE' and `STRUCT_INCOMING_VALUE' tell GCC where + to pass this address. + + By contrast, PCC on most target machines returns structures and + unions of any size by copying the data into an area of static + storage, and then returning the address of that storage as if it + were a pointer value. The caller must copy the data from that + memory area to the place where the value is wanted. GCC does not + use this method because it is slower and nonreentrant. + + On some newer machines, PCC uses a reentrant convention for all + structure and union returning. GCC on most of these machines uses + a compatible convention when returning structures and unions in + memory, but still returns small structures and unions in registers. + + You can tell GCC to use a compatible convention for all structure + and union returning with the option `-fpcc-struct-return'. + + * GCC complains about program fragments such as `0x74ae-0x4000' + which appear to be two hexadecimal constants separated by the minus + operator. Actually, this string is a single "preprocessing token". + Each such token must correspond to one token in C. Since this + does not, GCC prints an error message. Although it may appear + obvious that what is meant is an operator and two values, the ISO + C standard specifically requires that this be treated as erroneous. + + A "preprocessing token" is a "preprocessing number" if it begins + with a digit and is followed by letters, underscores, digits, + periods and `e+', `e-', `E+', `E-', `p+', `p-', `P+', or `P-' + character sequences. (In strict C89 mode, the sequences `p+', + `p-', `P+' and `P-' cannot appear in preprocessing numbers.) + + To make the above program fragment valid, place whitespace in + front of the minus sign. This whitespace will end the + preprocessing number. + +  + File: gcc.info, Node: Fixed Headers, Next: Standard Libraries, Prev: Incompatibilities, Up: Trouble + + Fixed Header Files + ================== + + GCC needs to install corrected versions of some system header files. + This is because most target systems have some header files that won't + work with GCC unless they are changed. Some have bugs, some are + incompatible with ISO C, and some depend on special features of other + compilers. + + Installing GCC automatically creates and installs the fixed header + files, by running a program called `fixincludes' (or for certain + targets an alternative such as `fixinc.svr4'). Normally, you don't + need to pay attention to this. But there are cases where it doesn't do + the right thing automatically. + + * If you update the system's header files, such as by installing a + new system version, the fixed header files of GCC are not + automatically updated. The easiest way to update them is to + reinstall GCC. (If you want to be clever, look in the makefile + and you can find a shortcut.) + + * On some systems, in particular SunOS 4, header file directories + contain machine-specific symbolic links in certain places. This + makes it possible to share most of the header files among hosts + running the same version of SunOS 4 on different machine models. + + The programs that fix the header files do not understand this + special way of using symbolic links; therefore, the directory of + fixed header files is good only for the machine model used to + build it. + + In SunOS 4, only programs that look inside the kernel will notice + the difference between machine models. Therefore, for most + purposes, you need not be concerned about this. + + It is possible to make separate sets of fixed header files for the + different machine models, and arrange a structure of symbolic + links so as to use the proper set, but you'll have to do this by + hand. + + * On Lynxos, GCC by default does not fix the header files. This is + because bugs in the shell cause the `fixincludes' script to fail. + + This means you will encounter problems due to bugs in the system + header files. It may be no comfort that they aren't GCC's fault, + but it does mean that there's nothing for us to do about them. + +  + File: gcc.info, Node: Standard Libraries, Next: Disappointments, Prev: Fixed Headers, Up: Trouble + + Standard Libraries + ================== + + GCC by itself attempts to be a conforming freestanding + implementation. *Note Language Standards Supported by GCC: Standards, + for details of what this means. Beyond the library facilities required + of such an implementation, the rest of the C library is supplied by the + vendor of the operating system. If that C library doesn't conform to + the C standards, then your programs might get warnings (especially when + using `-Wall') that you don't expect. + + For example, the `sprintf' function on SunOS 4.1.3 returns `char *' + while the C standard says that `sprintf' returns an `int'. The + `fixincludes' program could make the prototype for this function match + the Standard, but that would be wrong, since the function will still + return `char *'. + + If you need a Standard compliant library, then you need to find one, + as GCC does not provide one. The GNU C library (called `glibc') + provides ISO C, POSIX, BSD, SystemV and X/Open compatibility for + GNU/Linux and HURD-based GNU systems; no recent version of it supports + other systems, though some very old versions did. Version 2.2 of the + GNU C library includes nearly complete C99 support. You could also ask + your operating system vendor if newer libraries are available. + +  + File: gcc.info, Node: Disappointments, Next: C++ Misunderstandings, Prev: Standard Libraries, Up: Trouble + + Disappointments and Misunderstandings + ===================================== + + These problems are perhaps regrettable, but we don't know any + practical way around them. + + * Certain local variables aren't recognized by debuggers when you + compile with optimization. + + This occurs because sometimes GCC optimizes the variable out of + existence. There is no way to tell the debugger how to compute the + value such a variable "would have had", and it is not clear that + would be desirable anyway. So GCC simply does not mention the + eliminated variable when it writes debugging information. + + You have to expect a certain amount of disagreement between the + executable and your source code, when you use optimization. + + * Users often think it is a bug when GCC reports an error for code + like this: + + int foo (struct mumble *); + + struct mumble { ... }; + + int foo (struct mumble *x) + { ... } + + This code really is erroneous, because the scope of `struct + mumble' in the prototype is limited to the argument list + containing it. It does not refer to the `struct mumble' defined + with file scope immediately below--they are two unrelated types + with similar names in different scopes. + + But in the definition of `foo', the file-scope type is used + because that is available to be inherited. Thus, the definition + and the prototype do not match, and you get an error. + + This behavior may seem silly, but it's what the ISO standard + specifies. It is easy enough for you to make your code work by + moving the definition of `struct mumble' above the prototype. + It's not worth being incompatible with ISO C just to avoid an + error for the example shown above. + + * Accesses to bit-fields even in volatile objects works by accessing + larger objects, such as a byte or a word. You cannot rely on what + size of object is accessed in order to read or write the + bit-field; it may even vary for a given bit-field according to the + precise usage. + + If you care about controlling the amount of memory that is + accessed, use volatile but do not use bit-fields. + + * GCC comes with shell scripts to fix certain known problems in + system header files. They install corrected copies of various + header files in a special directory where only GCC will normally + look for them. The scripts adapt to various systems by searching + all the system header files for the problem cases that we know + about. + + If new system header files are installed, nothing automatically + arranges to update the corrected header files. You will have to + reinstall GCC to fix the new header files. More specifically, go + to the build directory and delete the files `stmp-fixinc' and + `stmp-headers', and the subdirectory `include'; then do `make + install' again. + + * On 68000 and x86 systems, for instance, you can get paradoxical + results if you test the precise values of floating point numbers. + For example, you can find that a floating point value which is not + a NaN is not equal to itself. This results from the fact that the + floating point registers hold a few more bits of precision than + fit in a `double' in memory. Compiled code moves values between + memory and floating point registers at its convenience, and moving + them into memory truncates them. + + You can partially avoid this problem by using the `-ffloat-store' + option (*note Optimize Options::). + + * On the MIPS, variable argument functions using `varargs.h' cannot + have a floating point value for the first argument. The reason + for this is that in the absence of a prototype in scope, if the + first argument is a floating point, it is passed in a floating + point register, rather than an integer register. + + If the code is rewritten to use the ISO standard `stdarg.h' method + of variable arguments, and the prototype is in scope at the time + of the call, everything will work fine. + + * On the H8/300 and H8/300H, variable argument functions must be + implemented using the ISO standard `stdarg.h' method of variable + arguments. Furthermore, calls to functions using `stdarg.h' + variable arguments must have a prototype for the called function + in scope at the time of the call. + + * On AIX and other platforms without weak symbol support, templates + need to be instantiated explicitly and symbols for static members + of templates will not be generated. + +  + File: gcc.info, Node: C++ Misunderstandings, Next: Protoize Caveats, Prev: Disappointments, Up: Trouble + + Common Misunderstandings with GNU C++ + ===================================== + + C++ is a complex language and an evolving one, and its standard + definition (the ISO C++ standard) was only recently completed. As a + result, your C++ compiler may occasionally surprise you, even when its + behavior is correct. This section discusses some areas that frequently + give rise to questions of this sort. + + * Menu: + + * Static Definitions:: Static member declarations are not definitions + * Temporaries:: Temporaries may vanish before you expect + * Copy Assignment:: Copy Assignment operators copy virtual bases twice + +  + File: gcc.info, Node: Static Definitions, Next: Temporaries, Up: C++ Misunderstandings + + Declare _and_ Define Static Members + ----------------------------------- + + When a class has static data members, it is not enough to _declare_ + the static member; you must also _define_ it. For example: + + class Foo + { + ... + void method(); + static int bar; + }; + + This declaration only establishes that the class `Foo' has an `int' + named `Foo::bar', and a member function named `Foo::method'. But you + still need to define _both_ `method' and `bar' elsewhere. According to + the ISO standard, you must supply an initializer in one (and only one) + source file, such as: + + int Foo::bar = 0; + + Other C++ compilers may not correctly implement the standard + behavior. As a result, when you switch to `g++' from one of these + compilers, you may discover that a program that appeared to work + correctly in fact does not conform to the standard: `g++' reports as + undefined symbols any static data members that lack definitions. + +  + File: gcc.info, Node: Temporaries, Next: Copy Assignment, Prev: Static Definitions, Up: C++ Misunderstandings + + Temporaries May Vanish Before You Expect + ---------------------------------------- + + It is dangerous to use pointers or references to _portions_ of a + temporary object. The compiler may very well delete the object before + you expect it to, leaving a pointer to garbage. The most common place + where this problem crops up is in classes like string classes, + especially ones that define a conversion function to type `char *' or + `const char *'--which is one reason why the standard `string' class + requires you to call the `c_str' member function. However, any class + that returns a pointer to some internal structure is potentially + subject to this problem. + + For example, a program may use a function `strfunc' that returns + `string' objects, and another function `charfunc' that operates on + pointers to `char': + + string strfunc (); + void charfunc (const char *); + + void + f () + { + const char *p = strfunc().c_str(); + ... + charfunc (p); + ... + charfunc (p); + } + + In this situation, it may seem reasonable to save a pointer to the C + string returned by the `c_str' member function and use that rather than + call `c_str' repeatedly. However, the temporary string created by the + call to `strfunc' is destroyed after `p' is initialized, at which point + `p' is left pointing to freed memory. + + Code like this may run successfully under some other compilers, + particularly obsolete cfront-based compilers that delete temporaries + along with normal local variables. However, the GNU C++ behavior is + standard-conforming, so if your program depends on late destruction of + temporaries it is not portable. + + The safe way to write such code is to give the temporary a name, + which forces it to remain until the end of the scope of the name. For + example: + + string& tmp = strfunc (); + charfunc (tmp.c_str ()); + +  + File: gcc.info, Node: Copy Assignment, Prev: Temporaries, Up: C++ Misunderstandings + + Implicit Copy-Assignment for Virtual Bases + ------------------------------------------ + + When a base class is virtual, only one subobject of the base class + belongs to each full object. Also, the constructors and destructors are + invoked only once, and called from the most-derived class. However, + such objects behave unspecified when being assigned. For example: + + struct Base{ + char *name; + Base(char *n) : name(strdup(n)){} + Base& operator= (const Base& other){ + free (name); + name = strdup (other.name); + } + }; + + struct A:virtual Base{ + int val; + A():Base("A"){} + }; + + struct B:virtual Base{ + int bval; + B():Base("B"){} + }; + + struct Derived:public A, public B{ + Derived():Base("Derived"){} + }; + + void func(Derived &d1, Derived &d2) + { + d1 = d2; + } + + The C++ standard specifies that `Base::Base' is only called once + when constructing or copy-constructing a Derived object. It is + unspecified whether `Base::operator=' is called more than once when the + implicit copy-assignment for Derived objects is invoked (as it is + inside `func' in the example). + + g++ implements the "intuitive" algorithm for copy-assignment: assign + all direct bases, then assign all members. In that algorithm, the + virtual base subobject can be encountered many times. In the example, + copying proceeds in the following order: `val', `name' (via `strdup'), + `bval', and `name' again. + + If application code relies on copy-assignment, a user-defined + copy-assignment operator removes any uncertainties. With such an + operator, the application can define whether and how the virtual base + subobject is assigned. + +  + File: gcc.info, Node: Protoize Caveats, Next: Non-bugs, Prev: C++ Misunderstandings, Up: Trouble + + Caveats of using `protoize' + =========================== + + The conversion programs `protoize' and `unprotoize' can sometimes + change a source file in a way that won't work unless you rearrange it. + + * `protoize' can insert references to a type name or type tag before + the definition, or in a file where they are not defined. + + If this happens, compiler error messages should show you where the + new references are, so fixing the file by hand is straightforward. + + * There are some C constructs which `protoize' cannot figure out. + For example, it can't determine argument types for declaring a + pointer-to-function variable; this you must do by hand. `protoize' + inserts a comment containing `???' each time it finds such a + variable; so you can find all such variables by searching for this + string. ISO C does not require declaring the argument types of + pointer-to-function types. + + * Using `unprotoize' can easily introduce bugs. If the program + relied on prototypes to bring about conversion of arguments, these + conversions will not take place in the program without prototypes. + One case in which you can be sure `unprotoize' is safe is when you + are removing prototypes that were made with `protoize'; if the + program worked before without any prototypes, it will work again + without them. + + You can find all the places where this problem might occur by + compiling the program with the `-Wconversion' option. It prints a + warning whenever an argument is converted. + + * Both conversion programs can be confused if there are macro calls + in and around the text to be converted. In other words, the + standard syntax for a declaration or definition must not result + from expanding a macro. This problem is inherent in the design of + C and cannot be fixed. If only a few functions have confusing + macro calls, you can easily convert them manually. + + * `protoize' cannot get the argument types for a function whose + definition was not actually compiled due to preprocessing + conditionals. When this happens, `protoize' changes nothing in + regard to such a function. `protoize' tries to detect such + instances and warn about them. + + You can generally work around this problem by using `protoize' step + by step, each time specifying a different set of `-D' options for + compilation, until all of the functions have been converted. + There is no automatic way to verify that you have got them all, + however. + + * Confusion may result if there is an occasion to convert a function + declaration or definition in a region of source code where there + is more than one formal parameter list present. Thus, attempts to + convert code containing multiple (conditionally compiled) versions + of a single function header (in the same vicinity) may not produce + the desired (or expected) results. + + If you plan on converting source files which contain such code, it + is recommended that you first make sure that each conditionally + compiled region of source code which contains an alternative + function header also contains at least one additional follower + token (past the final right parenthesis of the function header). + This should circumvent the problem. + + * `unprotoize' can become confused when trying to convert a function + definition or declaration which contains a declaration for a + pointer-to-function formal argument which has the same name as the + function being defined or declared. We recommend you avoid such + choices of formal parameter names. + + * You might also want to correct some of the indentation by hand and + break long lines. (The conversion programs don't write lines + longer than eighty characters in any case.) + +  + File: gcc.info, Node: Non-bugs, Next: Warnings and Errors, Prev: Protoize Caveats, Up: Trouble + + Certain Changes We Don't Want to Make + ===================================== + + This section lists changes that people frequently request, but which + we do not make because we think GCC is better without them. + + * Checking the number and type of arguments to a function which has + an old-fashioned definition and no prototype. + + Such a feature would work only occasionally--only for calls that + appear in the same file as the called function, following the + definition. The only way to check all calls reliably is to add a + prototype for the function. But adding a prototype eliminates the + motivation for this feature. So the feature is not worthwhile. + + * Warning about using an expression whose type is signed as a shift + count. + + Shift count operands are probably signed more often than unsigned. + Warning about this would cause far more annoyance than good. + + * Warning about assigning a signed value to an unsigned variable. + + Such assignments must be very common; warning about them would + cause more annoyance than good. + + * Warning when a non-void function value is ignored. + + Coming as I do from a Lisp background, I balk at the idea that + there is something dangerous about discarding a value. There are + functions that return values which some callers may find useful; + it makes no sense to clutter the program with a cast to `void' + whenever the value isn't useful. + + * Making `-fshort-enums' the default. + + This would cause storage layout to be incompatible with most other + C compilers. And it doesn't seem very important, given that you + can get the same result in other ways. The case where it matters + most is when the enumeration-valued object is inside a structure, + and in that case you can specify a field width explicitly. + + * Making bit-fields unsigned by default on particular machines where + "the ABI standard" says to do so. + + The ISO C standard leaves it up to the implementation whether a + bit-field declared plain `int' is signed or not. This in effect + creates two alternative dialects of C. + + The GNU C compiler supports both dialects; you can specify the + signed dialect with `-fsigned-bitfields' and the unsigned dialect + with `-funsigned-bitfields'. However, this leaves open the + question of which dialect to use by default. + + Currently, the preferred dialect makes plain bit-fields signed, + because this is simplest. Since `int' is the same as `signed int' + in every other context, it is cleanest for them to be the same in + bit-fields as well. + + Some computer manufacturers have published Application Binary + Interface standards which specify that plain bit-fields should be + unsigned. It is a mistake, however, to say anything about this + issue in an ABI. This is because the handling of plain bit-fields + distinguishes two dialects of C. Both dialects are meaningful on + every type of machine. Whether a particular object file was + compiled using signed bit-fields or unsigned is of no concern to + other object files, even if they access the same bit-fields in the + same data structures. + + A given program is written in one or the other of these two + dialects. The program stands a chance to work on most any machine + if it is compiled with the proper dialect. It is unlikely to work + at all if compiled with the wrong dialect. + + Many users appreciate the GNU C compiler because it provides an + environment that is uniform across machines. These users would be + inconvenienced if the compiler treated plain bit-fields + differently on certain machines. + + Occasionally users write programs intended only for a particular + machine type. On these occasions, the users would benefit if the + GNU C compiler were to support by default the same dialect as the + other compilers on that machine. But such applications are rare. + And users writing a program to run on more than one type of + machine cannot possibly benefit from this kind of compatibility. + + This is why GCC does and will treat plain bit-fields in the same + fashion on all types of machines (by default). + + There are some arguments for making bit-fields unsigned by default + on all machines. If, for example, this becomes a universal de + facto standard, it would make sense for GCC to go along with it. + This is something to be considered in the future. + + (Of course, users strongly concerned about portability should + indicate explicitly in each bit-field whether it is signed or not. + In this way, they write programs which have the same meaning in + both C dialects.) + + * Undefining `__STDC__' when `-ansi' is not used. + + Currently, GCC defines `__STDC__' as long as you don't use + `-traditional'. This provides good results in practice. + + Programmers normally use conditionals on `__STDC__' to ask whether + it is safe to use certain features of ISO C, such as function + prototypes or ISO token concatenation. Since plain `gcc' supports + all the features of ISO C, the correct answer to these questions is + "yes". + + Some users try to use `__STDC__' to check for the availability of + certain library facilities. This is actually incorrect usage in + an ISO C program, because the ISO C standard says that a conforming + freestanding implementation should define `__STDC__' even though it + does not have the library facilities. `gcc -ansi -pedantic' is a + conforming freestanding implementation, and it is therefore + required to define `__STDC__', even though it does not come with + an ISO C library. + + Sometimes people say that defining `__STDC__' in a compiler that + does not completely conform to the ISO C standard somehow violates + the standard. This is illogical. The standard is a standard for + compilers that claim to support ISO C, such as `gcc -ansi'--not + for other compilers such as plain `gcc'. Whatever the ISO C + standard says is relevant to the design of plain `gcc' without + `-ansi' only for pragmatic reasons, not as a requirement. + + GCC normally defines `__STDC__' to be 1, and in addition defines + `__STRICT_ANSI__' if you specify the `-ansi' option, or a `-std' + option for strict conformance to some version of ISO C. On some + hosts, system include files use a different convention, where + `__STDC__' is normally 0, but is 1 if the user specifies strict + conformance to the C Standard. GCC follows the host convention + when processing system include files, but when processing user + files it follows the usual GNU C convention. + + * Undefining `__STDC__' in C++. + + Programs written to compile with C++-to-C translators get the + value of `__STDC__' that goes with the C compiler that is + subsequently used. These programs must test `__STDC__' to + determine what kind of C preprocessor that compiler uses: whether + they should concatenate tokens in the ISO C fashion or in the + traditional fashion. + + These programs work properly with GNU C++ if `__STDC__' is defined. + They would not work otherwise. + + In addition, many header files are written to provide prototypes + in ISO C but not in traditional C. Many of these header files can + work without change in C++ provided `__STDC__' is defined. If + `__STDC__' is not defined, they will all fail, and will all need + to be changed to test explicitly for C++ as well. + + * Deleting "empty" loops. + + Historically, GCC has not deleted "empty" loops under the + assumption that the most likely reason you would put one in a + program is to have a delay, so deleting them will not make real + programs run any faster. + + However, the rationale here is that optimization of a nonempty loop + cannot produce an empty one, which holds for C but is not always + the case for C++. + + Moreover, with `-funroll-loops' small "empty" loops are already + removed, so the current behavior is both sub-optimal and + inconsistent and will change in the future. + + * Making side effects happen in the same order as in some other + compiler. + + It is never safe to depend on the order of evaluation of side + effects. For example, a function call like this may very well + behave differently from one compiler to another: + + void func (int, int); + + int i = 2; + func (i++, i++); + + There is no guarantee (in either the C or the C++ standard language + definitions) that the increments will be evaluated in any + particular order. Either increment might happen first. `func' + might get the arguments `2, 3', or it might get `3, 2', or even + `2, 2'. + + * Not allowing structures with volatile fields in registers. + + Strictly speaking, there is no prohibition in the ISO C standard + against allowing structures with volatile fields in registers, but + it does not seem to make any sense and is probably not what you + wanted to do. So the compiler will give an error message in this + case. + + * Making certain warnings into errors by default. + + Some ISO C testsuites report failure when the compiler does not + produce an error message for a certain program. + + ISO C requires a "diagnostic" message for certain kinds of invalid + programs, but a warning is defined by GCC to count as a + diagnostic. If GCC produces a warning but not an error, that is + correct ISO C support. If test suites call this "failure", they + should be run with the GCC option `-pedantic-errors', which will + turn these warnings into errors. + + +  + File: gcc.info, Node: Warnings and Errors, Prev: Non-bugs, Up: Trouble + + Warning Messages and Error Messages + =================================== + + The GNU compiler can produce two kinds of diagnostics: errors and + warnings. Each kind has a different purpose: + + "Errors" report problems that make it impossible to compile your + program. GCC reports errors with the source file name and line + number where the problem is apparent. + + "Warnings" report other unusual conditions in your code that _may_ + indicate a problem, although compilation can (and does) proceed. + Warning messages also report the source file name and line number, + but include the text `warning:' to distinguish them from error + messages. + + Warnings may indicate danger points where you should check to make + sure that your program really does what you intend; or the use of + obsolete features; or the use of nonstandard features of GNU C or C++. + Many warnings are issued only if you ask for them, with one of the `-W' + options (for instance, `-Wall' requests a variety of useful warnings). + + GCC always tries to compile your program if possible; it never + gratuitously rejects a program whose meaning is clear merely because + (for instance) it fails to conform to a standard. In some cases, + however, the C and C++ standards specify that certain extensions are + forbidden, and a diagnostic _must_ be issued by a conforming compiler. + The `-pedantic' option tells GCC to issue warnings in such cases; + `-pedantic-errors' says to make them errors instead. This does not + mean that _all_ non-ISO constructs get warnings or errors. + + *Note Options to Request or Suppress Warnings: Warning Options, for + more detail on these and related command-line options. + +  + File: gcc.info, Node: Bugs, Next: Service, Prev: Trouble, Up: Top + + Reporting Bugs + ************** + + Your bug reports play an essential role in making GCC reliable. + + When you encounter a problem, the first thing to do is to see if it + is already known. *Note Trouble::. If it isn't known, then you should + report the problem. + + Reporting a bug may help you by bringing a solution to your problem, + or it may not. (If it does not, look in the service directory; see + *Note Service::.) In any case, the principal function of a bug report + is to help the entire community by making the next version of GCC work + better. Bug reports are your contribution to the maintenance of GCC. + + Since the maintainers are very overloaded, we cannot respond to every + bug report. However, if the bug has not been fixed, we are likely to + send you a patch and ask you to tell us whether it works. + + In order for a bug report to serve its purpose, you must include the + information that makes for fixing the bug. + + * Menu: + + * Criteria: Bug Criteria. Have you really found a bug? + * Where: Bug Lists. Where to send your bug report. + * Reporting: Bug Reporting. How to report a bug effectively. + * GNATS: gccbug. You can use a bug reporting tool. + * Known: Trouble. Known problems. + * Help: Service. Where to ask for help. + +  + File: gcc.info, Node: Bug Criteria, Next: Bug Lists, Up: Bugs + + Have You Found a Bug? + ===================== + + If you are not sure whether you have found a bug, here are some + guidelines: + + * If the compiler gets a fatal signal, for any input whatever, that + is a compiler bug. Reliable compilers never crash. + + * If the compiler produces invalid assembly code, for any input + whatever (except an `asm' statement), that is a compiler bug, + unless the compiler reports errors (not just warnings) which would + ordinarily prevent the assembler from being run. + + * If the compiler produces valid assembly code that does not + correctly execute the input source code, that is a compiler bug. + + However, you must double-check to make sure, because you may have + run into an incompatibility between GNU C and traditional C (*note + Incompatibilities::). These incompatibilities might be considered + bugs, but they are inescapable consequences of valuable features. + + Or you may have a program whose behavior is undefined, which + happened by chance to give the desired results with another C or + C++ compiler. + + For example, in many nonoptimizing compilers, you can write `x;' + at the end of a function instead of `return x;', with the same + results. But the value of the function is undefined if `return' + is omitted; it is not a bug when GCC produces different results. + + Problems often result from expressions with two increment + operators, as in `f (*p++, *p++)'. Your previous compiler might + have interpreted that expression the way you intended; GCC might + interpret it another way. Neither compiler is wrong. The bug is + in your code. + + After you have localized the error to a single source line, it + should be easy to check for these things. If your program is + correct and well defined, you have found a compiler bug. + + * If the compiler produces an error message for valid input, that is + a compiler bug. + + * If the compiler does not produce an error message for invalid + input, that is a compiler bug. However, you should note that your + idea of "invalid input" might be my idea of "an extension" or + "support for traditional practice". + + * If you are an experienced user of one of the languages GCC + supports, your suggestions for improvement of GCC are welcome in + any case. + +  + File: gcc.info, Node: Bug Lists, Next: Bug Reporting, Prev: Bug Criteria, Up: Bugs + + Where to Report Bugs + ==================== + + Send bug reports for the GNU Compiler Collection to + . In accordance with the GNU-wide convention, in + which bug reports for tool "foo" are sent to `bug-foo@gnu.org', the + address may also be used; it will forward to the + address given above. + + Please read `http://gcc.gnu.org/bugs.html' for additional and/or + more up-to-date bug reporting instructions before you post a bug report. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-2 gcc-3.2.3/gcc/doc/gcc.info-2 *** gcc-3.2.2/gcc/doc/gcc.info-2 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-2 Tue Apr 22 07:07:13 2003 *************** *** 0 **** --- 1,811 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: C Dialect Options, Next: C++ Dialect Options, Prev: Invoking G++, Up: Invoking GCC + + Options Controlling C Dialect + ============================= + + The following options control the dialect of C (or languages derived + from C, such as C++ and Objective-C) that the compiler accepts: + + `-ansi' + In C mode, support all ISO C89 programs. In C++ mode, remove GNU + extensions that conflict with ISO C++. + + This turns off certain features of GCC that are incompatible with + ISO C89 (when compiling C code), or of standard C++ (when + compiling C++ code), such as the `asm' and `typeof' keywords, and + predefined macros such as `unix' and `vax' that identify the type + of system you are using. It also enables the undesirable and + rarely used ISO trigraph feature. For the C compiler, it disables + recognition of C++ style `//' comments as well as the `inline' + keyword. + + The alternate keywords `__asm__', `__extension__', `__inline__' + and `__typeof__' continue to work despite `-ansi'. You would not + want to use them in an ISO C program, of course, but it is useful + to put them in header files that might be included in compilations + done with `-ansi'. Alternate predefined macros such as `__unix__' + and `__vax__' are also available, with or without `-ansi'. + + The `-ansi' option does not cause non-ISO programs to be rejected + gratuitously. For that, `-pedantic' is required in addition to + `-ansi'. *Note Warning Options::. + + The macro `__STRICT_ANSI__' is predefined when the `-ansi' option + is used. Some header files may notice this macro and refrain from + declaring certain functions or defining certain macros that the + ISO standard doesn't call for; this is to avoid interfering with + any programs that might use these names for other things. + + Functions which would normally be built in but do not have + semantics defined by ISO C (such as `alloca' and `ffs') are not + built-in functions with `-ansi' is used. *Note Other built-in + functions provided by GCC: Other Builtins, for details of the + functions affected. + + `-std=' + Determine the language standard. This option is currently only + supported when compiling C. A value for this option must be + provided; possible values are + + `c89' + `iso9899:1990' + ISO C89 (same as `-ansi'). + + `iso9899:199409' + ISO C89 as modified in amendment 1. + + `c99' + `c9x' + `iso9899:1999' + `iso9899:199x' + ISO C99. Note that this standard is not yet fully supported; + see `http://gcc.gnu.org/gcc-3.1/c99status.html' for more + information. The names `c9x' and `iso9899:199x' are + deprecated. + + `gnu89' + Default, ISO C89 plus GNU extensions (including some C99 + features). + + `gnu99' + + `gnu9x' + ISO C99 plus GNU extensions. When ISO C99 is fully + implemented in GCC, this will become the default. The name + `gnu9x' is deprecated. + + + Even when this option is not specified, you can still use some of + the features of newer standards in so far as they do not conflict + with previous C standards. For example, you may use + `__restrict__' even when `-std=c99' is not specified. + + The `-std' options specifying some version of ISO C have the same + effects as `-ansi', except that features that were not in ISO C89 + but are in the specified version (for example, `//' comments and + the `inline' keyword in ISO C99) are not disabled. + + *Note Language Standards Supported by GCC: Standards, for details + of these standard versions. + + `-aux-info FILENAME' + Output to the given filename prototyped declarations for all + functions declared and/or defined in a translation unit, including + those in header files. This option is silently ignored in any + language other than C. + + Besides declarations, the file indicates, in comments, the origin + of each declaration (source file and line), whether the + declaration was implicit, prototyped or unprototyped (`I', `N' for + new or `O' for old, respectively, in the first character after the + line number and the colon), and whether it came from a declaration + or a definition (`C' or `F', respectively, in the following + character). In the case of function definitions, a K&R-style list + of arguments followed by their declarations is also provided, + inside comments, after the declaration. + + `-fno-asm' + Do not recognize `asm', `inline' or `typeof' as a keyword, so that + code can use these words as identifiers. You can use the keywords + `__asm__', `__inline__' and `__typeof__' instead. `-ansi' implies + `-fno-asm'. + + In C++, this switch only affects the `typeof' keyword, since `asm' + and `inline' are standard keywords. You may want to use the + `-fno-gnu-keywords' flag instead, which has the same effect. In + C99 mode (`-std=c99' or `-std=gnu99'), this switch only affects + the `asm' and `typeof' keywords, since `inline' is a standard + keyword in ISO C99. + + `-fno-builtin' + `-fno-builtin-FUNCTION (C and Objective-C only)' + Don't recognize built-in functions that do not begin with + `__builtin_' as prefix. *Note Other built-in functions provided + by GCC: Other Builtins, for details of the functions affected, + including those which are not built-in functions when `-ansi' or + `-std' options for strict ISO C conformance are used because they + do not have an ISO standard meaning. + + GCC normally generates special code to handle certain built-in + functions more efficiently; for instance, calls to `alloca' may + become single instructions that adjust the stack directly, and + calls to `memcpy' may become inline copy loops. The resulting + code is often both smaller and faster, but since the function + calls no longer appear as such, you cannot set a breakpoint on + those calls, nor can you change the behavior of the functions by + linking with a different library. + + In C++, `-fno-builtin' is always in effect. The `-fbuiltin' + option has no effect. Therefore, in C++, the only way to get the + optimization benefits of built-in functions is to call the function + using the `__builtin_' prefix. The GNU C++ Standard Library uses + built-in functions to implement many functions (like + `std::strchr'), so that you automatically get efficient code. + + With the `-fno-builtin-FUNCTION' option, not available when + compiling C++, only the built-in function FUNCTION is disabled. + FUNCTION must not begin with `__builtin_'. If a function is named + this is not built-in in this version of GCC, this option is + ignored. There is no corresponding `-fbuiltin-FUNCTION' option; + if you wish to enable built-in functions selectively when using + `-fno-builtin' or `-ffreestanding', you may define macros such as: + + #define abs(n) __builtin_abs ((n)) + #define strcpy(d, s) __builtin_strcpy ((d), (s)) + + `-fhosted' + Assert that compilation takes place in a hosted environment. This + implies `-fbuiltin'. A hosted environment is one in which the + entire standard library is available, and in which `main' has a + return type of `int'. Examples are nearly everything except a + kernel. This is equivalent to `-fno-freestanding'. + + `-ffreestanding' + Assert that compilation takes place in a freestanding environment. + This implies `-fno-builtin'. A freestanding environment is one + in which the standard library may not exist, and program startup + may not necessarily be at `main'. The most obvious example is an + OS kernel. This is equivalent to `-fno-hosted'. + + *Note Language Standards Supported by GCC: Standards, for details + of freestanding and hosted environments. + + `-trigraphs' + Support ISO C trigraphs. The `-ansi' option (and `-std' options + for strict ISO C conformance) implies `-trigraphs'. + + `-no-integrated-cpp' + Invoke the external cpp during compilation. The default is to use + the integrated cpp (internal cpp). This option also allows a + user-supplied cpp via the `-B' option. This flag is applicable in + both C and C++ modes. + + We do not guarantee to retain this option in future, and we may + change its semantics. + + `-traditional' + Attempt to support some aspects of traditional C compilers. + Specifically: + + * All `extern' declarations take effect globally even if they + are written inside of a function definition. This includes + implicit declarations of functions. + + * The newer keywords `typeof', `inline', `signed', `const' and + `volatile' are not recognized. (You can still use the + alternative keywords such as `__typeof__', `__inline__', and + so on.) + + * Comparisons between pointers and integers are always allowed. + + * Integer types `unsigned short' and `unsigned char' promote to + `unsigned int'. + + * Out-of-range floating point literals are not an error. + + * Certain constructs which ISO regards as a single invalid + preprocessing number, such as `0xe-0xd', are treated as + expressions instead. + + * String "constants" are not necessarily constant; they are + stored in writable space, and identical looking constants are + allocated separately. (This is the same as the effect of + `-fwritable-strings'.) + + * All automatic variables not declared `register' are preserved + by `longjmp'. Ordinarily, GNU C follows ISO C: automatic + variables not declared `volatile' may be clobbered. + + * The character escape sequences `\x' and `\a' evaluate as the + literal characters `x' and `a' respectively. Without + `-traditional', `\x' is a prefix for the hexadecimal + representation of a character, and `\a' produces a bell. + + This option is deprecated and may be removed. + + You may wish to use `-fno-builtin' as well as `-traditional' if + your program uses names that are normally GNU C built-in functions + for other purposes of its own. + + You cannot use `-traditional' if you include any header files that + rely on ISO C features. Some vendors are starting to ship systems + with ISO C header files and you cannot use `-traditional' on such + systems to compile files that include any system headers. + + The `-traditional' option also enables `-traditional-cpp'. + + `-traditional-cpp' + Attempt to support some aspects of traditional C preprocessors. + See the GNU CPP manual for details. + + `-fcond-mismatch' + Allow conditional expressions with mismatched types in the second + and third arguments. The value of such an expression is void. + This option is not supported for C++. + + `-funsigned-char' + Let the type `char' be unsigned, like `unsigned char'. + + Each kind of machine has a default for what `char' should be. It + is either like `unsigned char' by default or like `signed char' by + default. + + Ideally, a portable program should always use `signed char' or + `unsigned char' when it depends on the signedness of an object. + But many programs have been written to use plain `char' and expect + it to be signed, or expect it to be unsigned, depending on the + machines they were written for. This option, and its inverse, let + you make such a program work with the opposite default. + + The type `char' is always a distinct type from each of `signed + char' or `unsigned char', even though its behavior is always just + like one of those two. + + `-fsigned-char' + Let the type `char' be signed, like `signed char'. + + Note that this is equivalent to `-fno-unsigned-char', which is the + negative form of `-funsigned-char'. Likewise, the option + `-fno-signed-char' is equivalent to `-funsigned-char'. + + `-fsigned-bitfields' + `-funsigned-bitfields' + `-fno-signed-bitfields' + `-fno-unsigned-bitfields' + These options control whether a bit-field is signed or unsigned, + when the declaration does not use either `signed' or `unsigned'. + By default, such a bit-field is signed, because this is + consistent: the basic integer types such as `int' are signed types. + + However, when `-traditional' is used, bit-fields are all unsigned + no matter what. + + `-fwritable-strings' + Store string constants in the writable data segment and don't + uniquize them. This is for compatibility with old programs which + assume they can write into string constants. The option + `-traditional' also has this effect. + + Writing into string constants is a very bad idea; "constants" + should be constant. + + `-fallow-single-precision' + Do not promote single precision math operations to double + precision, even when compiling with `-traditional'. + + Traditional K&R C promotes all floating point operations to double + precision, regardless of the sizes of the operands. On the + architecture for which you are compiling, single precision may be + faster than double precision. If you must use `-traditional', + but want to use single precision operations when the operands are + single precision, use this option. This option has no effect + when compiling with ISO or GNU C conventions (the default). + +  + File: gcc.info, Node: C++ Dialect Options, Next: Objective-C Dialect Options, Prev: C Dialect Options, Up: Invoking GCC + + Options Controlling C++ Dialect + =============================== + + This section describes the command-line options that are only + meaningful for C++ programs; but you can also use most of the GNU + compiler options regardless of what language your program is in. For + example, you might compile a file `firstClass.C' like this: + + g++ -g -frepo -O -c firstClass.C + + In this example, only `-frepo' is an option meant only for C++ + programs; you can use the other options with any language supported by + GCC. + + Here is a list of options that are _only_ for compiling C++ programs: + + `-fno-access-control' + Turn off all access checking. This switch is mainly useful for + working around bugs in the access control code. + + `-fcheck-new' + Check that the pointer returned by `operator new' is non-null + before attempting to modify the storage allocated. The current + Working Paper requires that `operator new' never return a null + pointer, so this check is normally unnecessary. + + An alternative to using this option is to specify that your + `operator new' does not throw any exceptions; if you declare it + `throw()', G++ will check the return value. See also `new + (nothrow)'. + + `-fconserve-space' + Put uninitialized or runtime-initialized global variables into the + common segment, as C does. This saves space in the executable at + the cost of not diagnosing duplicate definitions. If you compile + with this flag and your program mysteriously crashes after + `main()' has completed, you may have an object that is being + destroyed twice because two definitions were merged. + + This option is no longer useful on most targets, now that support + has been added for putting variables into BSS without making them + common. + + `-fno-const-strings' + Give string constants type `char *' instead of type `const char + *'. By default, G++ uses type `const char *' as required by the + standard. Even if you use `-fno-const-strings', you cannot + actually modify the value of a string constant, unless you also use + `-fwritable-strings'. + + This option might be removed in a future release of G++. For + maximum portability, you should structure your code so that it + works with string constants that have type `const char *'. + + `-fdollars-in-identifiers' + Accept `$' in identifiers. You can also explicitly prohibit use of + `$' with the option `-fno-dollars-in-identifiers'. (GNU C allows + `$' by default on most target systems, but there are a few + exceptions.) Traditional C allowed the character `$' to form part + of identifiers. However, ISO C and C++ forbid `$' in identifiers. + + `-fno-elide-constructors' + The C++ standard allows an implementation to omit creating a + temporary which is only used to initialize another object of the + same type. Specifying this option disables that optimization, and + forces G++ to call the copy constructor in all cases. + + `-fno-enforce-eh-specs' + Don't check for violation of exception specifications at runtime. + This option violates the C++ standard, but may be useful for + reducing code size in production builds, much like defining + `NDEBUG'. The compiler will still optimize based on the exception + specifications. + + `-fexternal-templates' + Cause `#pragma interface' and `implementation' to apply to + template instantiation; template instances are emitted or not + according to the location of the template definition. *Note + Template Instantiation::, for more information. + + This option is deprecated. + + `-falt-external-templates' + Similar to `-fexternal-templates', but template instances are + emitted or not according to the place where they are first + instantiated. *Note Template Instantiation::, for more + information. + + This option is deprecated. + + `-ffor-scope' + `-fno-for-scope' + If `-ffor-scope' is specified, the scope of variables declared in + a for-init-statement is limited to the `for' loop itself, as + specified by the C++ standard. If `-fno-for-scope' is specified, + the scope of variables declared in a for-init-statement extends to + the end of the enclosing scope, as was the case in old versions of + G++, and other (traditional) implementations of C++. + + The default if neither flag is given to follow the standard, but + to allow and give a warning for old-style code that would + otherwise be invalid, or have different behavior. + + `-fno-gnu-keywords' + Do not recognize `typeof' as a keyword, so that code can use this + word as an identifier. You can use the keyword `__typeof__' + instead. `-ansi' implies `-fno-gnu-keywords'. + + `-fno-implicit-templates' + Never emit code for non-inline templates which are instantiated + implicitly (i.e. by use); only emit code for explicit + instantiations. *Note Template Instantiation::, for more + information. + + `-fno-implicit-inline-templates' + Don't emit code for implicit instantiations of inline templates, + either. The default is to handle inlines differently so that + compiles with and without optimization will need the same set of + explicit instantiations. + + `-fno-implement-inlines' + To save space, do not emit out-of-line copies of inline functions + controlled by `#pragma implementation'. This will cause linker + errors if these functions are not inlined everywhere they are + called. + + `-fms-extensions' + Disable pedantic warnings about constructs used in MFC, such as + implicit int and getting a pointer to member function via + non-standard syntax. + + `-fno-nonansi-builtins' + Disable built-in declarations of functions that are not mandated by + ANSI/ISO C. These include `ffs', `alloca', `_exit', `index', + `bzero', `conjf', and other related functions. + + `-fno-operator-names' + Do not treat the operator name keywords `and', `bitand', `bitor', + `compl', `not', `or' and `xor' as synonyms as keywords. + + `-fno-optional-diags' + Disable diagnostics that the standard says a compiler does not + need to issue. Currently, the only such diagnostic issued by G++ + is the one for a name having multiple meanings within a class. + + `-fpermissive' + Downgrade messages about nonconformant code from errors to + warnings. By default, G++ effectively sets `-pedantic-errors' + without `-pedantic'; this option reverses that. This behavior and + this option are superseded by `-pedantic', which works as it does + for GNU C. + + `-frepo' + Enable automatic template instantiation at link time. This option + also implies `-fno-implicit-templates'. *Note Template + Instantiation::, for more information. + + `-fno-rtti' + Disable generation of information about every class with virtual + functions for use by the C++ runtime type identification features + (`dynamic_cast' and `typeid'). If you don't use those parts of + the language, you can save some space by using this flag. Note + that exception handling uses the same information, but it will + generate it as needed. + + `-fstats' + Emit statistics about front-end processing at the end of the + compilation. This information is generally only useful to the G++ + development team. + + `-ftemplate-depth-N' + Set the maximum instantiation depth for template classes to N. A + limit on the template instantiation depth is needed to detect + endless recursions during template class instantiation. ANSI/ISO + C++ conforming programs must not rely on a maximum depth greater + than 17. + + `-fuse-cxa-atexit' + Register destructors for objects with static storage duration with + the `__cxa_atexit' function rather than the `atexit' function. + This option is required for fully standards-compliant handling of + static destructors, but will only work if your C library supports + `__cxa_atexit'. + + `-fvtable-gc' + Emit special relocations for vtables and virtual function + references so that the linker can identify unused virtual + functions and zero out vtable slots that refer to them. This is + most useful with `-ffunction-sections' and `-Wl,--gc-sections', in + order to also discard the functions themselves. + + This optimization requires GNU as and GNU ld. Not all systems + support this option. `-Wl,--gc-sections' is ignored without + `-static'. + + `-fno-weak' + Do not use weak symbol support, even if it is provided by the + linker. By default, G++ will use weak symbols if they are + available. This option exists only for testing, and should not be + used by end-users; it will result in inferior code and has no + benefits. This option may be removed in a future release of G++. + + `-nostdinc++' + Do not search for header files in the standard directories + specific to C++, but do still search the other standard + directories. (This option is used when building the C++ library.) + + In addition, these optimization, warning, and code generation options + have meanings only for C++ programs: + + `-fno-default-inline' + Do not assume `inline' for functions defined inside a class scope. + *Note Options That Control Optimization: Optimize Options. Note + that these functions will have linkage like inline functions; they + just won't be inlined by default. + + `-Wabi (C++ only)' + Warn when G++ generates code that is probably not compatible with + the vendor-neutral C++ ABI. Although an effort has been made to + warn about all such cases, there are probably some cases that are + not warned about, even though G++ is generating incompatible code. + There may also be cases where warnings are emitted even though + the code that is generated will be compatible. + + You should rewrite your code to avoid these warnings if you are + concerned about the fact that code generated by G++ may not be + binary compatible with code generated by other compilers. + + The known incompatibilites at this point include: + + * Incorrect handling of tail-padding for bit-fields. G++ may + attempt to pack data into the same byte as a base class. For + example: + + struct A { virtual void f(); int f1 : 1; }; + struct B : public A { int f2 : 1; }; + + In this case, G++ will place `B::f2' into the same byte + as`A::f1'; other compilers will not. You can avoid this + problem by explicitly padding `A' so that its size is a + multiple of the byte size on your platform; that will cause + G++ and other compilers to layout `B' identically. + + * Incorrect handling of tail-padding for virtual bases. G++ + does not use tail padding when laying out virtual bases. For + example: + + struct A { virtual void f(); char c1; }; + struct B { B(); char c2; }; + struct C : public A, public virtual B {}; + + In this case, G++ will not place `B' into the tail-padding for + `A'; other compilers will. You can avoid this problem by + explicitly padding `A' so that its size is a multiple of its + alignment (ignoring virtual base classes); that will cause + G++ and other compilers to layout `C' identically. + + + `-Wctor-dtor-privacy (C++ only)' + Warn when a class seems unusable, because all the constructors or + destructors in a class are private and the class has no friends or + public static member functions. + + `-Wnon-virtual-dtor (C++ only)' + Warn when a class declares a non-virtual destructor that should + probably be virtual, because it looks like the class will be used + polymorphically. + + `-Wreorder (C++ only)' + Warn when the order of member initializers given in the code does + not match the order in which they must be executed. For instance: + + struct A { + int i; + int j; + A(): j (0), i (1) { } + }; + + Here the compiler will warn that the member initializers for `i' + and `j' will be rearranged to match the declaration order of the + members. + + The following `-W...' options are not affected by `-Wall'. + + `-Weffc++ (C++ only)' + Warn about violations of the following style guidelines from Scott + Meyers' `Effective C++' book: + + * Item 11: Define a copy constructor and an assignment + operator for classes with dynamically allocated memory. + + * Item 12: Prefer initialization to assignment in constructors. + + * Item 14: Make destructors virtual in base classes. + + * Item 15: Have `operator=' return a reference to `*this'. + + * Item 23: Don't try to return a reference when you must + return an object. + + + and about violations of the following style guidelines from Scott + Meyers' `More Effective C++' book: + + * Item 6: Distinguish between prefix and postfix forms of + increment and decrement operators. + + * Item 7: Never overload `&&', `||', or `,'. + + + If you use this option, you should be aware that the standard + library headers do not obey all of these guidelines; you can use + `grep -v' to filter out those warnings. + + `-Wno-deprecated (C++ only)' + Do not warn about usage of deprecated features. *Note Deprecated + Features::. + + `-Wno-non-template-friend (C++ only)' + Disable warnings when non-templatized friend functions are declared + within a template. With the advent of explicit template + specification support in G++, if the name of the friend is an + unqualified-id (i.e., `friend foo(int)'), the C++ language + specification demands that the friend declare or define an + ordinary, nontemplate function. (Section 14.5.3). Before G++ + implemented explicit specification, unqualified-ids could be + interpreted as a particular specialization of a templatized + function. Because this non-conforming behavior is no longer the + default behavior for G++, `-Wnon-template-friend' allows the + compiler to check existing code for potential trouble spots, and + is on by default. This new compiler behavior can be turned off + with `-Wno-non-template-friend' which keeps the conformant + compiler code but disables the helpful warning. + + `-Wold-style-cast (C++ only)' + Warn if an old-style (C-style) cast to a non-void type is used + within a C++ program. The new-style casts (`static_cast', + `reinterpret_cast', and `const_cast') are less vulnerable to + unintended effects, and much easier to grep for. + + `-Woverloaded-virtual (C++ only)' + Warn when a function declaration hides virtual functions from a + base class. For example, in: + + struct A { + virtual void f(); + }; + + struct B: public A { + void f(int); + }; + + the `A' class version of `f' is hidden in `B', and code like this: + + B* b; + b->f(); + + will fail to compile. + + `-Wno-pmf-conversions (C++ only)' + Disable the diagnostic for converting a bound pointer to member + function to a plain pointer. + + `-Wsign-promo (C++ only)' + Warn when overload resolution chooses a promotion from unsigned or + enumeral type to a signed type over a conversion to an unsigned + type of the same size. Previous versions of G++ would try to + preserve unsignedness, but the standard mandates the current + behavior. + + `-Wsynth (C++ only)' + Warn when G++'s synthesis behavior does not match that of cfront. + For instance: + + struct A { + operator int (); + A& operator = (int); + }; + + main () + { + A a,b; + a = b; + } + + In this example, G++ will synthesize a default `A& operator = + (const A&);', while cfront will use the user-defined `operator ='. + +  + File: gcc.info, Node: Objective-C Dialect Options, Next: Language Independent Options, Prev: C++ Dialect Options, Up: Invoking GCC + + Options Controlling Objective-C Dialect + ======================================= + + This section describes the command-line options that are only + meaningful for Objective-C programs; but you can also use most of the + GNU compiler options regardless of what language your program is in. + For example, you might compile a file `some_class.m' like this: + + gcc -g -fgnu-runtime -O -c some_class.m + + In this example, only `-fgnu-runtime' is an option meant only for + Objective-C programs; you can use the other options with any language + supported by GCC. + + Here is a list of options that are _only_ for compiling Objective-C + programs: + + `-fconstant-string-class=CLASS-NAME' + Use CLASS-NAME as the name of the class to instantiate for each + literal string specified with the syntax `@"..."'. The default + class name is `NXConstantString'. + + `-fgnu-runtime' + Generate object code compatible with the standard GNU Objective-C + runtime. This is the default for most types of systems. + + `-fnext-runtime' + Generate output compatible with the NeXT runtime. This is the + default for NeXT-based systems, including Darwin and Mac OS X. + + `-gen-decls' + Dump interface declarations for all classes seen in the source + file to a file named `SOURCENAME.decl'. + + `-Wno-protocol' + Do not warn if methods required by a protocol are not implemented + in the class adopting it. + + `-Wselector' + Warn if a selector has multiple methods of different types defined. + + +  + File: gcc.info, Node: Language Independent Options, Next: Warning Options, Prev: Objective-C Dialect Options, Up: Invoking GCC + + Options to Control Diagnostic Messages Formatting + ================================================= + + Traditionally, diagnostic messages have been formatted irrespective + of the output device's aspect (e.g. its width, ...). The options + described below can be used to control the diagnostic messages + formatting algorithm, e.g. how many characters per line, how often + source location information should be reported. Right now, only the + C++ front end can honor these options. However it is expected, in the + near future, that the remaining front ends would be able to digest them + correctly. + + `-fmessage-length=N' + Try to format error messages so that they fit on lines of about N + characters. The default is 72 characters for `g++' and 0 for the + rest of the front ends supported by GCC. If N is zero, then no + line-wrapping will be done; each error message will appear on a + single line. + + `-fdiagnostics-show-location=once' + Only meaningful in line-wrapping mode. Instructs the diagnostic + messages reporter to emit _once_ source location information; that + is, in case the message is too long to fit on a single physical + line and has to be wrapped, the source location won't be emitted + (as prefix) again, over and over, in subsequent continuation + lines. This is the default behavior. + + `-fdiagnostics-show-location=every-line' + Only meaningful in line-wrapping mode. Instructs the diagnostic + messages reporter to emit the same source location information (as + prefix) for physical lines that result from the process of breaking + a message which is too long to fit on a single line. + + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-20 gcc-3.2.3/gcc/doc/gcc.info-20 *** gcc-3.2.2/gcc/doc/gcc.info-20 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-20 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1063 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Bug Reporting, Next: gccbug, Prev: Bug Lists, Up: Bugs + + How to Report Bugs + ================== + + The fundamental principle of reporting bugs usefully is this: + *report all the facts*. If you are not sure whether to state a fact or + leave it out, state it! + + Often people omit facts because they think they know what causes the + problem and they conclude that some details don't matter. Thus, you + might assume that the name of the variable you use in an example does + not matter. Well, probably it doesn't, but one cannot be sure. + Perhaps the bug is a stray memory reference which happens to fetch from + the location where that name is stored in memory; perhaps, if the name + were different, the contents of that location would fool the compiler + into doing the right thing despite the bug. Play it safe and give a + specific, complete example. That is the easiest thing for you to do, + and the most helpful. + + Keep in mind that the purpose of a bug report is to enable someone to + fix the bug if it is not known. It isn't very important what happens if + the bug is already known. Therefore, always write your bug reports on + the assumption that the bug is not known. + + Sometimes people give a few sketchy facts and ask, "Does this ring a + bell?" This cannot help us fix a bug, so it is basically useless. We + respond by asking for enough details to enable us to investigate. You + might as well expedite matters by sending them to begin with. + + Try to make your bug report self-contained. If we have to ask you + for more information, it is best if you include all the previous + information in your response, as well as the information that was + missing. + + Please report each bug in a separate message. This makes it easier + for us to track which bugs have been fixed and to forward your bugs + reports to the appropriate maintainer. + + To enable someone to investigate the bug, you should include all + these things: + + * The version of GCC. You can get this by running it with the `-v' + option. + + Without this, we won't know whether there is any point in looking + for the bug in the current version of GCC. + + * A complete input file that will reproduce the bug. If the bug is + in the C preprocessor, send a source file and any header files + that it requires. If the bug is in the compiler proper (`cc1'), + send the preprocessor output generated by adding `-save-temps' to + the compilation command (*note Debugging Options::). When you do + this, use the same `-I', `-D' or `-U' options that you used in + actual compilation. Then send the INPUT.i or INPUT.ii files + generated. + + A single statement is not enough of an example. In order to + compile it, it must be embedded in a complete file of compiler + input; and the bug might depend on the details of how this is done. + + Without a real example one can compile, all anyone can do about + your bug report is wish you luck. It would be futile to try to + guess how to provoke the bug. For example, bugs in register + allocation and reloading frequently depend on every little detail + of the function they happen in. + + Even if the input file that fails comes from a GNU program, you + should still send the complete test case. Don't ask the GCC + maintainers to do the extra work of obtaining the program in + question--they are all overworked as it is. Also, the problem may + depend on what is in the header files on your system; it is + unreliable for the GCC maintainers to try the problem with the + header files available to them. By sending CPP output, you can + eliminate this source of uncertainty and save us a certain + percentage of wild goose chases. + + * The command arguments you gave GCC to compile that example and + observe the bug. For example, did you use `-O'? To guarantee you + won't omit something important, list all the options. + + If we were to try to guess the arguments, we would probably guess + wrong and then we would not encounter the bug. + + * The type of machine you are using, and the operating system name + and version number. + + * The operands you gave to the `configure' command when you installed + the compiler. + + * A complete list of any modifications you have made to the compiler + source. (We don't promise to investigate the bug unless it + happens in an unmodified compiler. But if you've made + modifications and don't tell us, then you are sending us on a wild + goose chase.) + + Be precise about these changes. A description in English is not + enough--send a context diff for them. + + Adding files of your own (such as a machine description for a + machine we don't support) is a modification of the compiler source. + + * Details of any other deviations from the standard procedure for + installing GCC. + + * A description of what behavior you observe that you believe is + incorrect. For example, "The compiler gets a fatal signal," or, + "The assembler instruction at line 208 in the output is incorrect." + + Of course, if the bug is that the compiler gets a fatal signal, + then one can't miss it. But if the bug is incorrect output, the + maintainer might not notice unless it is glaringly wrong. None of + us has time to study all the assembler code from a 50-line C + program just on the chance that one instruction might be wrong. + We need _you_ to do this part! + + Even if the problem you experience is a fatal signal, you should + still say so explicitly. Suppose something strange is going on, + such as, your copy of the compiler is out of synch, or you have + encountered a bug in the C library on your system. (This has + happened!) Your copy might crash and the copy here would not. If + you said to expect a crash, then when the compiler here fails to + crash, we would know that the bug was not happening. If you don't + say to expect a crash, then we would not know whether the bug was + happening. We would not be able to draw any conclusion from our + observations. + + If the problem is a diagnostic when compiling GCC with some other + compiler, say whether it is a warning or an error. + + Often the observed symptom is incorrect output when your program + is run. Sad to say, this is not enough information unless the + program is short and simple. None of us has time to study a large + program to figure out how it would work if compiled correctly, + much less which line of it was compiled wrong. So you will have + to do that. Tell us which source line it is, and what incorrect + result happens when that line is executed. A person who + understands the program can find this as easily as finding a bug + in the program itself. + + * If you send examples of assembler code output from GCC, please use + `-g' when you make them. The debugging information includes + source line numbers which are essential for correlating the output + with the input. + + * If you wish to mention something in the GCC source, refer to it by + context, not by line number. + + The line numbers in the development sources don't match those in + your sources. Your line numbers would convey no useful + information to the maintainers. + + * Additional information from a debugger might enable someone to + find a problem on a machine which he does not have available. + However, you need to think when you collect this information if + you want it to have any chance of being useful. + + For example, many people send just a backtrace, but that is never + useful by itself. A simple backtrace with arguments conveys little + about GCC because the compiler is largely data-driven; the same + functions are called over and over for different RTL insns, doing + different things depending on the details of the insn. + + Most of the arguments listed in the backtrace are useless because + they are pointers to RTL list structure. The numeric values of the + pointers, which the debugger prints in the backtrace, have no + significance whatever; all that matters is the contents of the + objects they point to (and most of the contents are other such + pointers). + + In addition, most compiler passes consist of one or more loops that + scan the RTL insn sequence. The most vital piece of information + about such a loop--which insn it has reached--is usually in a + local variable, not in an argument. + + What you need to provide in addition to a backtrace are the values + of the local variables for several stack frames up. When a local + variable or an argument is an RTX, first print its value and then + use the GDB command `pr' to print the RTL expression that it points + to. (If GDB doesn't run on your machine, use your debugger to call + the function `debug_rtx' with the RTX as an argument.) In + general, whenever a variable is a pointer, its value is no use + without the data it points to. + + Here are some things that are not necessary: + + * A description of the envelope of the bug. + + Often people who encounter a bug spend a lot of time investigating + which changes to the input file will make the bug go away and which + changes will not affect it. + + This is often time consuming and not very useful, because the way + we will find the bug is by running a single example under the + debugger with breakpoints, not by pure deduction from a series of + examples. You might as well save your time for something else. + + Of course, if you can find a simpler example to report _instead_ of + the original one, that is a convenience. Errors in the output + will be easier to spot, running under the debugger will take less + time, etc. Most GCC bugs involve just one function, so the most + straightforward way to simplify an example is to delete all the + function definitions except the one where the bug occurs. Those + earlier in the file may be replaced by external declarations if + the crucial function depends on them. (Exception: inline + functions may affect compilation of functions defined later in the + file.) + + However, simplification is not vital; if you don't want to do this, + report the bug anyway and send the entire test case you used. + + * In particular, some people insert conditionals `#ifdef BUG' around + a statement which, if removed, makes the bug not happen. These + are just clutter; we won't pay any attention to them anyway. + Besides, you should send us cpp output, and that can't have + conditionals. + + * A patch for the bug. + + A patch for the bug is useful if it is a good one. But don't omit + the necessary information, such as the test case, on the + assumption that a patch is all we need. We might see problems + with your patch and decide to fix the problem another way, or we + might not understand it at all. + + Sometimes with a program as complicated as GCC it is very hard to + construct an example that will make the program follow a certain + path through the code. If you don't send the example, we won't be + able to construct one, so we won't be able to verify that the bug + is fixed. + + And if we can't understand what bug you are trying to fix, or why + your patch should be an improvement, we won't install it. A test + case will help us to understand. + + See `http://gcc.gnu.org/contribute.html' for guidelines on how to + make it easy for us to understand and install your patches. + + * A guess about what the bug is or what it depends on. + + Such guesses are usually wrong. Even I can't guess right about + such things without first using the debugger to find the facts. + + * A core dump file. + + We have no way of examining a core dump for your type of machine + unless we have an identical system--and if we do have one, we + should be able to reproduce the crash ourselves. + +  + File: gcc.info, Node: gccbug, Prev: Bug Reporting, Up: Bugs + + The gccbug script + ================= + + To simplify creation of bug reports, and to allow better tracking of + reports, we use the GNATS bug tracking system. Part of that system is + the `gccbug' script. This is a Unix shell script, so you need a shell + to run it. It is normally installed in the same directory where `gcc' + is installed. + + The gccbug script is derived from send-pr, *note Creating new + Problem Reports: (send-pr)using send-pr.. When invoked, it starts a + text editor so you can fill out the various fields of the report. When + the you quit the editor, the report is automatically send to the bug + reporting address. + + A number of fields in this bug report form are specific to GCC, and + are explained at `http://gcc.gnu.org/gnats.html'. + +  + File: gcc.info, Node: Service, Next: Contributing, Prev: Bugs, Up: Top + + How To Get Help with GCC + ************************ + + If you need help installing, using or changing GCC, there are two + ways to find it: + + * Send a message to a suitable network mailing list. First try + (for help installing or using GCC), and if + that brings no response, try . For help changing + GCC, ask . If you think you have found a bug in + GCC, please report it following the instructions at *note Bug + Reporting::. + + * Look in the service directory for someone who might help you for a + fee. The service directory is found at + `http://www.gnu.org/prep/service.html'. + +  + File: gcc.info, Node: Contributing, Next: VMS, Prev: Service, Up: Top + + Contributing to GCC Development + ******************************* + + If you would like to help pretest GCC releases to assure they work + well, our current development sources are available by CVS (see + `http://gcc.gnu.org/cvs.html'). Source and binary snapshots are also + available for FTP; see `http://gcc.gnu.org/snapshots.html'. + + If you would like to work on improvements to GCC, please read the + advice at these URLs: + + `http://gcc.gnu.org/contribute.html' + `http://gcc.gnu.org/contributewhy.html' + + for information on how to make useful contributions and avoid + duplication of effort. Suggested projects are listed at + `http://gcc.gnu.org/projects/'. + +  + File: gcc.info, Node: VMS, Next: Funding, Prev: Contributing, Up: Top + + Using GCC on VMS + **************** + + Here is how to use GCC on VMS. + + * Menu: + + * Include Files and VMS:: Where the preprocessor looks for the include files. + * Global Declarations:: How to do globaldef, globalref and globalvalue with + GCC. + * VMS Misc:: Misc information. + +  + File: gcc.info, Node: Include Files and VMS, Next: Global Declarations, Up: VMS + + Include Files and VMS + ===================== + + Due to the differences between the filesystems of Unix and VMS, GCC + attempts to translate file names in `#include' into names that VMS will + understand. The basic strategy is to prepend a prefix to the + specification of the include file, convert the whole filename to a VMS + filename, and then try to open the file. GCC tries various prefixes + one by one until one of them succeeds: + + 1. The first prefix is the `GNU_CC_INCLUDE:' logical name: this is + where GNU C header files are traditionally stored. If you wish to + store header files in non-standard locations, then you can assign + the logical `GNU_CC_INCLUDE' to be a search list, where each + element of the list is suitable for use with a rooted logical. + + 2. The next prefix tried is `SYS$SYSROOT:[SYSLIB.]'. This is where + VAX-C header files are traditionally stored. + + 3. If the include file specification by itself is a valid VMS + filename, the preprocessor then uses this name with no prefix in + an attempt to open the include file. + + 4. If the file specification is not a valid VMS filename (i.e. does + not contain a device or a directory specifier, and contains a `/' + character), the preprocessor tries to convert it from Unix syntax + to VMS syntax. + + Conversion works like this: the first directory name becomes a + device, and the rest of the directories are converted into + VMS-format directory names. For example, the name `X11/foobar.h' + is translated to `X11:[000000]foobar.h' or `X11:foobar.h', + whichever one can be opened. This strategy allows you to assign a + logical name to point to the actual location of the header files. + + 5. If none of these strategies succeeds, the `#include' fails. + + Include directives of the form: + + #include foobar + + are a common source of incompatibility between VAX-C and GCC. VAX-C + treats this much like a standard `#include ' directive. That + is incompatible with the ISO C behavior implemented by GCC: to expand + the name `foobar' as a macro. Macro expansion should eventually yield + one of the two standard formats for `#include': + + #include "FILE" + #include + + If you have this problem, the best solution is to modify the source + to convert the `#include' directives to one of the two standard forms. + That will work with either compiler. If you want a quick and dirty fix, + define the file names as macros with the proper expansion, like this: + + #define stdio + + This will work, as long as the name doesn't conflict with anything else + in the program. + + Another source of incompatibility is that VAX-C assumes that: + + #include "foobar" + + is actually asking for the file `foobar.h'. GCC does not make this + assumption, and instead takes what you ask for literally; it tries to + read the file `foobar'. The best way to avoid this problem is to + always specify the desired file extension in your include directives. + + GCC for VMS is distributed with a set of include files that is + sufficient to compile most general purpose programs. Even though the + GCC distribution does not contain header files to define constants and + structures for some VMS system-specific functions, there is no reason + why you cannot use GCC with any of these functions. You first may have + to generate or create header files, either by using the public domain + utility `UNSDL' (which can be found on a DECUS tape), or by extracting + the relevant modules from one of the system macro libraries, and using + an editor to construct a C header file. + + A `#include' file name cannot contain a DECNET node name. The + preprocessor reports an I/O error if you attempt to use a node name, + whether explicitly, or implicitly via a logical name. + +  + File: gcc.info, Node: Global Declarations, Next: VMS Misc, Prev: Include Files and VMS, Up: VMS + + Global Declarations and VMS + =========================== + + GCC does not provide the `globalref', `globaldef' and `globalvalue' + keywords of VAX-C. You can get the same effect with an obscure feature + of GAS, the GNU assembler. (This requires GAS version 1.39 or later.) + The following macros allow you to use this feature in a fairly natural + way: + + #ifdef __GNUC__ + #define GLOBALREF(TYPE,NAME) \ + TYPE NAME \ + asm ("_$$PsectAttributes_GLOBALSYMBOL$$" #NAME) + #define GLOBALDEF(TYPE,NAME,VALUE) \ + TYPE NAME \ + asm ("_$$PsectAttributes_GLOBALSYMBOL$$" #NAME) \ + = VALUE + #define GLOBALVALUEREF(TYPE,NAME) \ + const TYPE NAME[1] \ + asm ("_$$PsectAttributes_GLOBALVALUE$$" #NAME) + #define GLOBALVALUEDEF(TYPE,NAME,VALUE) \ + const TYPE NAME[1] \ + asm ("_$$PsectAttributes_GLOBALVALUE$$" #NAME) \ + = {VALUE} + #else + #define GLOBALREF(TYPE,NAME) \ + globalref TYPE NAME + #define GLOBALDEF(TYPE,NAME,VALUE) \ + globaldef TYPE NAME = VALUE + #define GLOBALVALUEDEF(TYPE,NAME,VALUE) \ + globalvalue TYPE NAME = VALUE + #define GLOBALVALUEREF(TYPE,NAME) \ + globalvalue TYPE NAME + #endif + + (The `_$$PsectAttributes_GLOBALSYMBOL' prefix at the start of the name + is removed by the assembler, after it has modified the attributes of + the symbol). These macros are provided in the VMS binaries + distribution in a header file `GNU_HACKS.H'. An example of the usage + is: + + GLOBALREF (int, ijk); + GLOBALDEF (int, jkl, 0); + + The macros `GLOBALREF' and `GLOBALDEF' cannot be used + straightforwardly for arrays, since there is no way to insert the array + dimension into the declaration at the right place. However, you can + declare an array with these macros if you first define a typedef for the + array type, like this: + + typedef int intvector[10]; + GLOBALREF (intvector, foo); + + Array and structure initializers will also break the macros; you can + define the initializer to be a macro of its own, or you can expand the + `GLOBALDEF' macro by hand. You may find a case where you wish to use + the `GLOBALDEF' macro with a large array, but you are not interested in + explicitly initializing each element of the array. In such cases you + can use an initializer like: `{0,}', which will initialize the entire + array to `0'. + + A shortcoming of this implementation is that a variable declared with + `GLOBALVALUEREF' or `GLOBALVALUEDEF' is always an array. For example, + the declaration: + + GLOBALVALUEREF(int, ijk); + + declares the variable `ijk' as an array of type `int [1]'. This is + done because a globalvalue is actually a constant; its "value" is what + the linker would normally consider an address. That is not how an + integer value works in C, but it is how an array works. So treating + the symbol as an array name gives consistent results--with the + exception that the value seems to have the wrong type. *Don't try to + access an element of the array.* It doesn't have any elements. The + array "address" may not be the address of actual storage. + + The fact that the symbol is an array may lead to warnings where the + variable is used. Insert type casts to avoid the warnings. Here is an + example; it takes advantage of the ISO C feature allowing macros that + expand to use the same name as the macro itself. + + GLOBALVALUEREF (int, ss$_normal); + GLOBALVALUEDEF (int, xyzzy,123); + #ifdef __GNUC__ + #define ss$_normal ((int) ss$_normal) + #define xyzzy ((int) xyzzy) + #endif + + Don't use `globaldef' or `globalref' with a variable whose type is + an enumeration type; this is not implemented. Instead, make the + variable an integer, and use a `globalvaluedef' for each of the + enumeration values. An example of this would be: + + #ifdef __GNUC__ + GLOBALDEF (int, color, 0); + GLOBALVALUEDEF (int, RED, 0); + GLOBALVALUEDEF (int, BLUE, 1); + GLOBALVALUEDEF (int, GREEN, 3); + #else + enum globaldef color {RED, BLUE, GREEN = 3}; + #endif + +  + File: gcc.info, Node: VMS Misc, Prev: Global Declarations, Up: VMS + + Other VMS Issues + ================ + + GCC automatically arranges for `main' to return 1 by default if you + fail to specify an explicit return value. This will be interpreted by + VMS as a status code indicating a normal successful completion. + Version 1 of GCC did not provide this default. + + GCC on VMS works only with the GNU assembler, GAS. You need version + 1.37 or later of GAS in order to produce value debugging information for + the VMS debugger. Use the ordinary VMS linker with the object files + produced by GAS. + + Under previous versions of GCC, the generated code would occasionally + give strange results when linked to the sharable `VAXCRTL' library. + Now this should work. + + A caveat for use of `const' global variables: the `const' modifier + must be specified in every external declaration of the variable in all + of the source files that use that variable. Otherwise the linker will + issue warnings about conflicting attributes for the variable. Your + program will still work despite the warnings, but the variable will be + placed in writable storage. + + Although the VMS linker does distinguish between upper and lower case + letters in global symbols, most VMS compilers convert all such symbols + into upper case and most run-time library routines also have upper case + names. To be able to reliably call such routines, GCC (by means of the + assembler GAS) converts global symbols into upper case like other VMS + compilers. However, since the usual practice in C is to distinguish + case, GCC (via GAS) tries to preserve usual C behavior by augmenting + each name that is not all lower case. This means truncating the name + to at most 23 characters and then adding more characters at the end + which encode the case pattern of those 23. Names which contain at + least one dollar sign are an exception; they are converted directly into + upper case without augmentation. + + Name augmentation yields bad results for programs that use + precompiled libraries (such as Xlib) which were generated by another + compiler. You can use the compiler option `/NOCASE_HACK' to inhibit + augmentation; it makes external C functions and variables + case-independent as is usual on VMS. Alternatively, you could write + all references to the functions and variables in such libraries using + lower case; this will work on VMS, but is not portable to other + systems. The compiler option `/NAMES' also provides control over + global name handling. + + Function and variable names are handled somewhat differently with + G++. The GNU C++ compiler performs "name mangling" on function names, + which means that it adds information to the function name to describe + the data types of the arguments that the function takes. One result of + this is that the name of a function can become very long. Since the + VMS linker only recognizes the first 31 characters in a name, special + action is taken to ensure that each function and variable has a unique + name that can be represented in 31 characters. + + If the name (plus a name augmentation, if required) is less than 32 + characters in length, then no special action is performed. If the name + is longer than 31 characters, the assembler (GAS) will generate a hash + string based upon the function name, truncate the function name to 23 + characters, and append the hash string to the truncated name. If the + `/VERBOSE' compiler option is used, the assembler will print both the + full and truncated names of each symbol that is truncated. + + The `/NOCASE_HACK' compiler option should not be used when you are + compiling programs that use libg++. libg++ has several instances of + objects (i.e. `Filebuf' and `filebuf') which become indistinguishable + in a case-insensitive environment. This leads to cases where you need + to inhibit augmentation selectively (if you were using libg++ and Xlib + in the same program, for example). There is no special feature for + doing this, but you can get the result by defining a macro for each + mixed case symbol for which you wish to inhibit augmentation. The + macro should expand into the lower case equivalent of itself. For + example: + + #define StuDlyCapS studlycaps + + These macro definitions can be placed in a header file to minimize + the number of changes to your source code. + +  + File: gcc.info, Node: Funding, Next: GNU Project, Prev: VMS, Up: Top + + Funding Free Software + ********************* + + If you want to have more free software a few years from now, it makes + sense for you to help encourage people to contribute funds for its + development. The most effective approach known is to encourage + commercial redistributors to donate. + + Users of free software systems can boost the pace of development by + encouraging for-a-fee distributors to donate part of their selling price + to free software developers--the Free Software Foundation, and others. + + The way to convince distributors to do this is to demand it and + expect it from them. So when you compare distributors, judge them + partly by how much they give to free software development. Show + distributors they must compete to be the one who gives the most. + + To make this approach work, you must insist on numbers that you can + compare, such as, "We will donate ten dollars to the Frobnitz project + for each disk sold." Don't be satisfied with a vague promise, such as + "A portion of the profits are donated," since it doesn't give a basis + for comparison. + + Even a precise fraction "of the profits from this disk" is not very + meaningful, since creative accounting and unrelated business decisions + can greatly alter what fraction of the sales price counts as profit. + If the price you pay is $50, ten percent of the profit is probably less + than a dollar; it might be a few cents, or nothing at all. + + Some redistributors do development work themselves. This is useful + too; but to keep everyone honest, you need to inquire how much they do, + and what kind. Some kinds of development make much more long-term + difference than others. For example, maintaining a separate version of + a program contributes very little; maintaining the standard version of a + program for the whole community contributes much. Easy new ports + contribute little, since someone else would surely do them; difficult + ports such as adding a new CPU to the GNU Compiler Collection + contribute more; major new features or packages contribute the most. + + By establishing the idea that supporting further development is "the + proper thing to do" when distributing free software for a fee, we can + assure a steady flow of resources into making more free software. + + Copyright (C) 1994 Free Software Foundation, Inc. + Verbatim copying and redistribution of this section is permitted + without royalty; alteration is not permitted. + +  + File: gcc.info, Node: GNU Project, Next: Copying, Prev: Funding, Up: Top + + The GNU Project and GNU/Linux + ***************************** + + The GNU Project was launched in 1984 to develop a complete Unix-like + operating system which is free software: the GNU system. (GNU is a + recursive acronym for "GNU's Not Unix"; it is pronounced "guh-NEW".) + Variants of the GNU operating system, which use the kernel Linux, are + now widely used; though these systems are often referred to as "Linux", + they are more accurately called GNU/Linux systems. + + For more information, see: + `http://www.gnu.org/' + `http://www.gnu.org/gnu/linux-and-gnu.html' + +  + File: gcc.info, Node: Copying, Next: GNU Free Documentation License, Prev: GNU Project, Up: Top + + GNU GENERAL PUBLIC LICENSE + ************************** + + Version 2, June 1991 + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + ======== + + The licenses for most software are designed to take away your + freedom to share and change it. By contrast, the GNU General Public + License is intended to guarantee your freedom to share and change free + software--to make sure the software is free for all its users. This + General Public License applies to most of the Free Software + Foundation's software and to any other program whose authors commit to + using it. (Some other Free Software Foundation software is covered by + the GNU Library General Public License instead.) You can apply it to + your programs, too. + + When we speak of free software, we are referring to freedom, not + price. Our General Public Licenses are designed to make sure that you + have the freedom to distribute copies of free software (and charge for + this service if you wish), that you receive source code or can get it + if you want it, that you can change the software or use pieces of it in + new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid + anyone to deny you these rights or to ask you to surrender the rights. + These restrictions translate to certain responsibilities for you if you + distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether + gratis or for a fee, you must give the recipients all the rights that + you have. You must make sure that they, too, receive or can get the + source code. And you must show them these terms so they know their + rights. + + We protect your rights with two steps: (1) copyright the software, + and (2) offer you this license which gives you legal permission to copy, + distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain + that everyone understands that there is no warranty for this free + software. If the software is modified by someone else and passed on, we + want its recipients to know that what they have is not the original, so + that any problems introduced by others will not reflect on the original + authors' reputations. + + Finally, any free program is threatened constantly by software + patents. We wish to avoid the danger that redistributors of a free + program will individually obtain patent licenses, in effect making the + program proprietary. To prevent this, we have made it clear that any + patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and + modification follow. + + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + 0. This License applies to any program or other work which contains a + notice placed by the copyright holder saying it may be distributed + under the terms of this General Public License. The "Program", + below, refers to any such program or work, and a "work based on + the Program" means either the Program or any derivative work under + copyright law: that is to say, a work containing the Program or a + portion of it, either verbatim or with modifications and/or + translated into another language. (Hereinafter, translation is + included without limitation in the term "modification".) Each + licensee is addressed as "you". + + Activities other than copying, distribution and modification are + not covered by this License; they are outside its scope. The act + of running the Program is not restricted, and the output from the + Program is covered only if its contents constitute a work based on + the Program (independent of having been made by running the + Program). Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's + source code as you receive it, in any medium, provided that you + conspicuously and appropriately publish on each copy an appropriate + copyright notice and disclaimer of warranty; keep intact all the + notices that refer to this License and to the absence of any + warranty; and give any other recipients of the Program a copy of + this License along with the Program. + + You may charge a fee for the physical act of transferring a copy, + and you may at your option offer warranty protection in exchange + for a fee. + + 2. You may modify your copy or copies of the Program or any portion + of it, thus forming a work based on the Program, and copy and + distribute such modifications or work under the terms of Section 1 + above, provided that you also meet all of these conditions: + + a. You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b. You must cause any work that you distribute or publish, that + in whole or in part contains or is derived from the Program + or any part thereof, to be licensed as a whole at no charge + to all third parties under the terms of this License. + + c. If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display + an announcement including an appropriate copyright notice and + a notice that there is no warranty (or else, saying that you + provide a warranty) and that users may redistribute the + program under these conditions, and telling the user how to + view a copy of this License. (Exception: if the Program + itself is interactive but does not normally print such an + announcement, your work based on the Program is not required + to print an announcement.) + + These requirements apply to the modified work as a whole. If + identifiable sections of that work are not derived from the + Program, and can be reasonably considered independent and separate + works in themselves, then this License, and its terms, do not + apply to those sections when you distribute them as separate + works. But when you distribute the same sections as part of a + whole which is a work based on the Program, the distribution of + the whole must be on the terms of this License, whose permissions + for other licensees extend to the entire whole, and thus to each + and every part regardless of who wrote it. + + Thus, it is not the intent of this section to claim rights or + contest your rights to work written entirely by you; rather, the + intent is to exercise the right to control the distribution of + derivative or collective works based on the Program. + + In addition, mere aggregation of another work not based on the + Program with the Program (or with a work based on the Program) on + a volume of a storage or distribution medium does not bring the + other work under the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, + under Section 2) in object code or executable form under the terms + of Sections 1 and 2 above provided that you also do one of the + following: + + a. Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of + Sections 1 and 2 above on a medium customarily used for + software interchange; or, + + b. Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a + medium customarily used for software interchange; or, + + c. Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with + such an offer, in accord with Subsection b above.) + + The source code for a work means the preferred form of the work for + making modifications to it. For an executable work, complete + source code means all the source code for all modules it contains, + plus any associated interface definition files, plus the scripts + used to control compilation and installation of the executable. + However, as a special exception, the source code distributed need + not include anything that is normally distributed (in either + source or binary form) with the major components (compiler, + kernel, and so on) of the operating system on which the executable + runs, unless that component itself accompanies the executable. + + If distribution of executable or object code is made by offering + access to copy from a designated place, then offering equivalent + access to copy the source code from the same place counts as + distribution of the source code, even though third parties are not + compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program + except as expressly provided under this License. Any attempt + otherwise to copy, modify, sublicense or distribute the Program is + void, and will automatically terminate your rights under this + License. However, parties who have received copies, or rights, + from you under this License will not have their licenses + terminated so long as such parties remain in full compliance. + + 5. You are not required to accept this License, since you have not + signed it. However, nothing else grants you permission to modify + or distribute the Program or its derivative works. These actions + are prohibited by law if you do not accept this License. + Therefore, by modifying or distributing the Program (or any work + based on the Program), you indicate your acceptance of this + License to do so, and all its terms and conditions for copying, + distributing or modifying the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the + Program), the recipient automatically receives a license from the + original licensor to copy, distribute or modify the Program + subject to these terms and conditions. You may not impose any + further restrictions on the recipients' exercise of the rights + granted herein. You are not responsible for enforcing compliance + by third parties to this License. + + 7. If, as a consequence of a court judgment or allegation of patent + infringement or for any other reason (not limited to patent + issues), conditions are imposed on you (whether by court order, + agreement or otherwise) that contradict the conditions of this + License, they do not excuse you from the conditions of this + License. If you cannot distribute so as to satisfy simultaneously + your obligations under this License and any other pertinent + obligations, then as a consequence you may not distribute the + Program at all. For example, if a patent license would not permit + royalty-free redistribution of the Program by all those who + receive copies directly or indirectly through you, then the only + way you could satisfy both it and this License would be to refrain + entirely from distribution of the Program. + + If any portion of this section is held invalid or unenforceable + under any particular circumstance, the balance of the section is + intended to apply and the section as a whole is intended to apply + in other circumstances. + + It is not the purpose of this section to induce you to infringe any + patents or other property right claims or to contest validity of + any such claims; this section has the sole purpose of protecting + the integrity of the free software distribution system, which is + implemented by public license practices. Many people have made + generous contributions to the wide range of software distributed + through that system in reliance on consistent application of that + system; it is up to the author/donor to decide if he or she is + willing to distribute software through any other system and a + licensee cannot impose that choice. + + This section is intended to make thoroughly clear what is believed + to be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in + certain countries either by patents or by copyrighted interfaces, + the original copyright holder who places the Program under this + License may add an explicit geographical distribution limitation + excluding those countries, so that distribution is permitted only + in or among countries not thus excluded. In such case, this + License incorporates the limitation as if written in the body of + this License. + + 9. The Free Software Foundation may publish revised and/or new + versions of the General Public License from time to time. Such + new versions will be similar in spirit to the present version, but + may differ in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If the + Program specifies a version number of this License which applies + to it and "any later version", you have the option of following + the terms and conditions either of that version or of any later + version published by the Free Software Foundation. If the Program + does not specify a version number of this License, you may choose + any version ever published by the Free Software Foundation. + + 10. If you wish to incorporate parts of the Program into other free + programs whose distribution conditions are different, write to the + author to ask for permission. For software which is copyrighted + by the Free Software Foundation, write to the Free Software + Foundation; we sometimes make exceptions for this. Our decision + will be guided by the two goals of preserving the free status of + all derivatives of our free software and of promoting the sharing + and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO + WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE + LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT + HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT + WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT + NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND + FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE + QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE + PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY + SERVICING, REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN + WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY + MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE + LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, + INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR + INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF + DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU + OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY + OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + ============================================= + + If you develop a new program, and you want it to be of the greatest + possible use to the public, the best way to achieve this is to make it + free software which everyone can redistribute and change under these + terms. + + To do so, attach the following notices to the program. It is safest + to attach them to the start of each source file to most effectively + convey the exclusion of warranty; and each file should have at least + the "copyright" line and a pointer to where the full notice is found. + + ONE LINE TO GIVE THE PROGRAM'S NAME AND A BRIEF IDEA OF WHAT IT DOES. + Copyright (C) YEAR NAME OF AUTHOR + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place - Suite 330, + Boston, MA 02111-1307, USA. + + Also add information on how to contact you by electronic and paper + mail. + + If the program is interactive, make it output a short notice like + this when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) YEAR NAME OF AUTHOR + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details + type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + + The hypothetical commands `show w' and `show c' should show the + appropriate parts of the General Public License. Of course, the + commands you use may be called something other than `show w' and `show + c'; they could even be mouse-clicks or menu items--whatever suits your + program. + + You should also get your employer (if you work as a programmer) or + your school, if any, to sign a "copyright disclaimer" for the program, + if necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + SIGNATURE OF TY COON, 1 April 1989 + Ty Coon, President of Vice + + This General Public License does not permit incorporating your + program into proprietary programs. If your program is a subroutine + library, you may consider it more useful to permit linking proprietary + applications with the library. If this is what you want to do, use the + GNU Library General Public License instead of this License. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-21 gcc-3.2.3/gcc/doc/gcc.info-21 *** gcc-3.2.2/gcc/doc/gcc.info-21 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-21 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1228 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: GNU Free Documentation License, Next: Contributors, Prev: Copying, Up: Top + + GNU Free Documentation License + ****************************** + + Version 1.1, March 2000 + Copyright (C) 2000 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or other + written document "free" in the sense of freedom: to assure everyone + the effective freedom to copy and redistribute it, with or without + modifying it, either commercially or noncommercially. Secondarily, + this License preserves for the author and publisher a way to get + credit for their work, while not being considered responsible for + modifications made by others. + + This License is a kind of "copyleft", which means that derivative + works of the document must themselves be free in the same sense. + It complements the GNU General Public License, which is a copyleft + license designed for free software. + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same freedoms + that the software does. But this License is not limited to + software manuals; it can be used for any textual work, regardless + of subject matter or whether it is published as a printed book. + We recommend this License principally for works whose purpose is + instruction or reference. + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be distributed + under the terms of this License. The "Document", below, refers to + any such manual or work. Any member of the public is a licensee, + and is addressed as "you". + + A "Modified Version" of the Document means any work containing the + Document or a portion of it, either copied verbatim, or with + modifications and/or translated into another language. + + A "Secondary Section" is a named appendix or a front-matter + section of the Document that deals exclusively with the + relationship of the publishers or authors of the Document to the + Document's overall subject (or to related matters) and contains + nothing that could fall directly within that overall subject. + (For example, if the Document is in part a textbook of + mathematics, a Secondary Section may not explain any mathematics.) + The relationship could be a matter of historical connection with + the subject or with related matters, or of legal, commercial, + philosophical, ethical or political position regarding them. + + The "Invariant Sections" are certain Secondary Sections whose + titles are designated, as being those of Invariant Sections, in + the notice that says that the Document is released under this + License. + + The "Cover Texts" are certain short passages of text that are + listed, as Front-Cover Texts or Back-Cover Texts, in the notice + that says that the Document is released under this License. + + A "Transparent" copy of the Document means a machine-readable copy, + represented in a format whose specification is available to the + general public, whose contents can be viewed and edited directly + and straightforwardly with generic text editors or (for images + composed of pixels) generic paint programs or (for drawings) some + widely available drawing editor, and that is suitable for input to + text formatters or for automatic translation to a variety of + formats suitable for input to text formatters. A copy made in an + otherwise Transparent file format whose markup has been designed + to thwart or discourage subsequent modification by readers is not + Transparent. A copy that is not "Transparent" is called "Opaque". + + Examples of suitable formats for Transparent copies include plain + ASCII without markup, Texinfo input format, LaTeX input format, + SGML or XML using a publicly available DTD, and + standard-conforming simple HTML designed for human modification. + Opaque formats include PostScript, PDF, proprietary formats that + can be read and edited only by proprietary word processors, SGML + or XML for which the DTD and/or processing tools are not generally + available, and the machine-generated HTML produced by some word + processors for output purposes only. + + The "Title Page" means, for a printed book, the title page itself, + plus such following pages as are needed to hold, legibly, the + material this License requires to appear in the title page. For + works in formats which do not have any title page as such, "Title + Page" means the text near the most prominent appearance of the + work's title, preceding the beginning of the body of the text. + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that you + add no other conditions whatsoever to those of this License. You + may not use technical measures to obstruct or control the reading + or further copying of the copies you make or distribute. However, + you may accept compensation in exchange for copies. If you + distribute a large enough number of copies you must also follow + the conditions in section 3. + + You may also lend copies, under the same conditions stated above, + and you may publicly display copies. + + 3. COPYING IN QUANTITY + + If you publish printed copies of the Document numbering more than + 100, and the Document's license notice requires Cover Texts, you + must enclose the copies in covers that carry, clearly and legibly, + all these Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also clearly + and legibly identify you as the publisher of these copies. The + front cover must present the full title with all words of the + title equally prominent and visible. You may add other material + on the covers in addition. Copying with changes limited to the + covers, as long as they preserve the title of the Document and + satisfy these conditions, can be treated as verbatim copying in + other respects. + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + If you publish or distribute Opaque copies of the Document + numbering more than 100, you must either include a + machine-readable Transparent copy along with each Opaque copy, or + state in or with each Opaque copy a publicly-accessible + computer-network location containing a complete Transparent copy + of the Document, free of added material, which the general + network-using public has access to download anonymously at no + charge using public-standard network protocols. If you use the + latter option, you must take reasonably prudent steps, when you + begin distribution of Opaque copies in quantity, to ensure that + this Transparent copy will remain thus accessible at the stated + location until at least one year after the last time you + distribute an Opaque copy (directly or through your agents or + retailers) of that edition to the public. + + It is requested, but not required, that you contact the authors of + the Document well before redistributing any large number of + copies, to give them a chance to provide you with an updated + version of the Document. + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document + under the conditions of sections 2 and 3 above, provided that you + release the Modified Version under precisely this License, with + the Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version to + whoever possesses a copy of it. In addition, you must do these + things in the Modified Version: + + A. Use in the Title Page (and on the covers, if any) a title + distinct from that of the Document, and from those of + previous versions (which should, if there were any, be listed + in the History section of the Document). You may use the + same title as a previous version if the original publisher of + that version gives permission. + + B. List on the Title Page, as authors, one or more persons or + entities responsible for authorship of the modifications in + the Modified Version, together with at least five of the + principal authors of the Document (all of its principal + authors, if it has less than five). + + C. State on the Title page the name of the publisher of the + Modified Version, as the publisher. + + D. Preserve all the copyright notices of the Document. + + E. Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + F. Include, immediately after the copyright notices, a license + notice giving the public permission to use the Modified + Version under the terms of this License, in the form shown in + the Addendum below. + + G. Preserve in that license notice the full lists of Invariant + Sections and required Cover Texts given in the Document's + license notice. + + H. Include an unaltered copy of this License. + + I. Preserve the section entitled "History", and its title, and + add to it an item stating at least the title, year, new + authors, and publisher of the Modified Version as given on + the Title Page. If there is no section entitled "History" in + the Document, create one stating the title, year, authors, + and publisher of the Document as given on its Title Page, + then add an item describing the Modified Version as stated in + the previous sentence. + + J. Preserve the network location, if any, given in the Document + for public access to a Transparent copy of the Document, and + likewise the network locations given in the Document for + previous versions it was based on. These may be placed in + the "History" section. You may omit a network location for a + work that was published at least four years before the + Document itself, or if the original publisher of the version + it refers to gives permission. + + K. In any section entitled "Acknowledgments" or "Dedications", + preserve the section's title, and preserve in the section all + the substance and tone of each of the contributor + acknowledgments and/or dedications given therein. + + L. Preserve all the Invariant Sections of the Document, + unaltered in their text and in their titles. Section numbers + or the equivalent are not considered part of the section + titles. + + M. Delete any section entitled "Endorsements". Such a section + may not be included in the Modified Version. + + N. Do not retitle any existing section as "Endorsements" or to + conflict in title with any Invariant Section. + + If the Modified Version includes new front-matter sections or + appendices that qualify as Secondary Sections and contain no + material copied from the Document, you may at your option + designate some or all of these sections as invariant. To do this, + add their titles to the list of Invariant Sections in the Modified + Version's license notice. These titles must be distinct from any + other section titles. + + You may add a section entitled "Endorsements", provided it contains + nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + + You may add a passage of up to five words as a Front-Cover Text, + and a passage of up to 25 words as a Back-Cover Text, to the end + of the list of Cover Texts in the Modified Version. Only one + passage of Front-Cover Text and one of Back-Cover Text may be + added by (or through arrangements made by) any one entity. If the + Document already includes a cover text for the same cover, + previously added by you or by arrangement made by the same entity + you are acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + + The author(s) and publisher(s) of the Document do not by this + License give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version. + + 5. COMBINING DOCUMENTS + + You may combine the Document with other documents released under + this License, under the terms defined in section 4 above for + modified versions, provided that you include in the combination + all of the Invariant Sections of all of the original documents, + unmodified, and list them all as Invariant Sections of your + combined work in its license notice. + + The combined work need only contain one copy of this License, and + multiple identical Invariant Sections may be replaced with a single + copy. If there are multiple Invariant Sections with the same name + but different contents, make the title of each such section unique + by adding at the end of it, in parentheses, the name of the + original author or publisher of that section if known, or else a + unique number. Make the same adjustment to the section titles in + the list of Invariant Sections in the license notice of the + combined work. + + In the combination, you must combine any sections entitled + "History" in the various original documents, forming one section + entitled "History"; likewise combine any sections entitled + "Acknowledgments", and any sections entitled "Dedications". You + must delete all sections entitled "Endorsements." + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other + documents released under this License, and replace the individual + copies of this License in the various documents with a single copy + that is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + + You may extract a single document from such a collection, and + distribute it individually under this License, provided you insert + a copy of this License into the extracted document, and follow + this License in all other respects regarding verbatim copying of + that document. + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with other + separate and independent documents or works, in or on a volume of + a storage or distribution medium, does not as a whole count as a + Modified Version of the Document, provided no compilation + copyright is claimed for the compilation. Such a compilation is + called an "aggregate", and this License does not apply to the + other self-contained works thus compiled with the Document, on + account of their being thus compiled, if they are not themselves + derivative works of the Document. + + If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may be + placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section + 4. Replacing Invariant Sections with translations requires special + permission from their copyright holders, but you may include + translations of some or all Invariant Sections in addition to the + original versions of these Invariant Sections. You may include a + translation of this License provided that you also include the + original English version of this License. In case of a + disagreement between the translation and the original English + version of this License, the original English version will prevail. + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document + except as expressly provided for under this License. Any other + attempt to copy, modify, sublicense or distribute the Document is + void, and will automatically terminate your rights under this + License. However, parties who have received copies, or rights, + from you under this License will not have their licenses + terminated so long as such parties remain in full compliance. + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software Foundation may publish new, revised versions of + the GNU Free Documentation License from time to time. Such new + versions will be similar in spirit to the present version, but may + differ in detail to address new problems or concerns. See + `http://www.gnu.org/copyleft/'. + + Each version of the License is given a distinguishing version + number. If the Document specifies that a particular numbered + version of this License "or any later version" applies to it, you + have the option of following the terms and conditions either of + that specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by the + Free Software Foundation. + + ADDENDUM: How to use this License for your documents + ==================================================== + + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and license + notices just after the title page: + + Copyright (C) YEAR YOUR NAME. + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 + or any later version published by the Free Software Foundation; + with the Invariant Sections being LIST THEIR TITLES, with the + Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + A copy of the license is included in the section entitled ``GNU + Free Documentation License''. + + If you have no Invariant Sections, write "with no Invariant Sections" + instead of saying which ones are invariant. If you have no Front-Cover + Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being + LIST"; likewise for Back-Cover Texts. + + If your document contains nontrivial examples of program code, we + recommend releasing these examples in parallel under your choice of + free software license, such as the GNU General Public License, to + permit their use in free software. + +  + File: gcc.info, Node: Contributors, Next: Option Index, Prev: GNU Free Documentation License, Up: Top + + Contributors to GCC + ******************* + + The GCC project would like to thank its many contributors. Without + them the project would not have been nearly as successful as it has + been. Any omissions in this list are accidental. Feel free to contact + if you have been left out or some of your + contributions are not listed. Please keep this list in alphabetical + order. + + * Analog Devices helped implement the support for complex data types + and iterators. + + * John David Anglin for threading-related fixes and improvements to + libstdc++-v3, and the HP-UX port. + + * James van Artsdalen wrote the code that makes efficient use of the + Intel 80387 register stack. + + * Alasdair Baird for various bugfixes. + + * Gerald Baumgartner added the signature extension to the C++ front + end. + + * Godmar Back for his Java improvements and encouragement. + + * Scott Bambrough for help porting the Java compiler. + + * Jon Beniston for his Win32 port of Java. + + * Geoff Berry for his Java object serialization work and various + patches. + + * Eric Blake for helping to make GCJ and libgcj conform to the + specifications. + + * Hans-J. Boehm for his garbage collector, IA-64 libffi port, and + other Java work. + + * Neil Booth for work on cpplib, lang hooks, debug hooks and other + miscellaneous clean-ups. + + * Per Bothner for his direction via the steering committee and + various improvements to our infrastructure for supporting new + languages. Chill front end implementation. Initial + implementations of cpplib, fix-header, config.guess, libio, and + past C++ library (libg++) maintainer. Dreaming up, designing and + implementing much of GCJ. + + * Devon Bowen helped port GCC to the Tahoe. + + * Don Bowman for mips-vxworks contributions. + + * Dave Brolley for work on cpplib and Chill. + + * Robert Brown implemented the support for Encore 32000 systems. + + * Christian Bruel for improvements to local store elimination. + + * Herman A.J. ten Brugge for various fixes. + + * Joerg Brunsmann for Java compiler hacking and help with the GCJ + FAQ. + + * Joe Buck for his direction via the steering committee. + + * Craig Burley for leadership of the Fortran effort. + + * Stephan Buys for contributing Doxygen notes for libstdc++. + + * Paolo Carlini for libstdc++ work: lots of efficiency improvements + to the string class, hard detective work on the frustrating + localization issues, and keeping up with the problem reports. + + * John Carr for his alias work, SPARC hacking, infrastructure + improvements, previous contributions to the steering committee, + loop optimizations, etc. + + * Steve Chamberlain for support for the Hitachi SH and H8 processors + and the PicoJava processor, and for GCJ config fixes. + + * Glenn Chambers for help with the GCJ FAQ. + + * John-Marc Chandonia for various libgcj patches. + + * Scott Christley for his Objective-C contributions. + + * Eric Christopher for his Java porting help and clean-ups. + + * Branko Cibej for more warning contributions. + + * The GNU Classpath project for all of their merged runtime code. + + * Nick Clifton for arm, mcore, fr30, v850, m32r work, `--help', and + other random hacking. + + * Michael Cook for libstdc++ cleanup patches to reduce warnings. + + * Ralf Corsepius for SH testing and minor bugfixing. + + * Stan Cox for care and feeding of the x86 port and lots of behind + the scenes hacking. + + * Alex Crain provided changes for the 3b1. + + * Ian Dall for major improvements to the NS32k port. + + * Dario Dariol contributed the four varieties of sample programs + that print a copy of their source. + + * Russell Davidson for fstream and stringstream fixes in libstdc++. + + * Mo DeJong for GCJ and libgcj bug fixes. + + * Gabriel Dos Reis for contributions to g++, contributions and + maintenance of GCC diagnostics infrastructure, libstdc++-v3, + including valarray<>, complex<>, maintaining the numerics library + (including that pesky :-) and keeping up-to-date anything + to do with numbers. + + * Ulrich Drepper for his work on glibc, testing of GCC using glibc, + ISO C99 support, CFG dumping support, etc., plus support of the + C++ runtime libraries including for all kinds of C interface + issues, contributing and maintaining complex<>, sanity checking + and disbursement, configuration architecture, libio maintenance, + and early math work. + + * Richard Earnshaw for his ongoing work with the ARM. + + * David Edelsohn for his direction via the steering committee, + ongoing work with the RS6000/PowerPC port, help cleaning up Haifa + loop changes, and for doing the entire AIX port of libstdc++ with + his bare hands. + + * Kevin Ediger for the floating point formatting of num_put::do_put + in libstdc++. + + * Phil Edwards for libstdc++ work including configuration hackery, + documentation maintainer, chief breaker of the web pages, the + occasional iostream bugfix, and work on shared library symbol + versioning. + + * Paul Eggert for random hacking all over GCC. + + * Mark Elbrecht for various DJGPP improvements, and for libstdc++ + configuration support for locales and fstream-related fixes. + + * Vadim Egorov for libstdc++ fixes in strings, streambufs, and + iostreams. + + * Ben Elliston for his work to move the Objective-C runtime into its + own subdirectory and for his work on autoconf. + + * Marc Espie for OpenBSD support. + + * Doug Evans for much of the global optimization framework, arc, + m32r, and SPARC work. + + * Fred Fish for BeOS support and Ada fixes. + + * Ivan Fontes Garcia for the Portugese translation of the GCJ FAQ. + + * Peter Gerwinski for various bugfixes and the Pascal front end. + + * Kaveh Ghazi for his direction via the steering committee and + amazing work to make `-W -Wall' useful. + + * John Gilmore for a donation to the FSF earmarked improving GNU + Java. + + * Judy Goldberg for c++ contributions. + + * Torbjorn Granlund for various fixes and the c-torture testsuite, + multiply- and divide-by-constant optimization, improved long long + support, improved leaf function register allocation, and his + direction via the steering committee. + + * Anthony Green for his `-Os' contributions and Java front end work. + + * Stu Grossman for gdb hacking, allowing GCJ developers to debug our + code. + + * Michael K. Gschwind contributed the port to the PDP-11. + + * Ron Guilmette implemented the `protoize' and `unprotoize' tools, + the support for Dwarf symbolic debugging information, and much of + the support for System V Release 4. He has also worked heavily on + the Intel 386 and 860 support. + + * Bruno Haible for improvements in the runtime overhead for EH, new + warnings and assorted bugfixes. + + * Andrew Haley for his amazing Java compiler and library efforts. + + * Chris Hanson assisted in making GCC work on HP-UX for the 9000 + series 300. + + * Michael Hayes for various thankless work he's done trying to get + the c30/c40 ports functional. Lots of loop and unroll + improvements and fixes. + + * Kate Hedstrom for staking the g77 folks with an initial testsuite. + + * Richard Henderson for his ongoing SPARC, alpha, and ia32 work, loop + opts, and generally fixing lots of old problems we've ignored for + years, flow rewrite and lots of further stuff, including reviewing + tons of patches. + + * Nobuyuki Hikichi of Software Research Associates, Tokyo, + contributed the support for the Sony NEWS machine. + + * Manfred Hollstein for his ongoing work to keep the m88k alive, lots + of testing an bugfixing, particularly of our configury code. + + * Steve Holmgren for MachTen patches. + + * Jan Hubicka for his x86 port improvements. + + * Christian Iseli for various bugfixes. + + * Kamil Iskra for general m68k hacking. + + * Lee Iverson for random fixes and MIPS testing. + + * Andreas Jaeger for various fixes to the MIPS port + + * Jakub Jelinek for his SPARC work and sibling call optimizations as + well as lots of bug fixes and test cases, and for improving the + Java build system. + + * Janis Johnson for ia64 testing and fixes and for her quality + improvement sidetracks. + + * J. Kean Johnston for OpenServer support. + + * Tim Josling for the sample language treelang based originally on + Richard Kenner's ""toy" language". + + * Nicolai Josuttis for additional libstdc++ documentation. + + * Klaus Kaempf for his ongoing work to make alpha-vms a viable + target. + + * David Kashtan of SRI adapted GCC to VMS. + + * Ryszard Kabatek for many, many libstdc++ bugfixes and + optimizations of strings, especially member functions, and for + auto_ptr fixes. + + * Geoffrey Keating for his ongoing work to make the PPC work for + GNU/Linux and his automatic regression tester. + + * Brendan Kehoe for his ongoing work with g++ and for a lot of early + work in just about every part of libstdc++. + + * Oliver M. Kellogg of Deutsche Aerospace contributed the port to the + MIL-STD-1750A. + + * Richard Kenner of the New York University Ultracomputer Research + Laboratory wrote the machine descriptions for the AMD 29000, the + DEC Alpha, the IBM RT PC, and the IBM RS/6000 as well as the + support for instruction attributes. He also made changes to + better support RISC processors including changes to common + subexpression elimination, strength reduction, function calling + sequence handling, and condition code support, in addition to + generalizing the code for frame pointer elimination and delay slot + scheduling. Richard Kenner was also the head maintainer of GCC + for several years. + + * Mumit Khan for various contributions to the Cygwin and Mingw32 + ports and maintaining binary releases for Windows hosts, and for + massive libstdc++ porting work to Cygwin/Mingw32. + + * Robin Kirkham for cpu32 support. + + * Mark Klein for PA improvements. + + * Thomas Koenig for various bugfixes. + + * Bruce Korb for the new and improved fixincludes code. + + * Benjamin Kosnik for his g++ work and for leading the libstdc++-v3 + effort. + + * Charles LaBrec contributed the support for the Integrated Solutions + 68020 system. + + * Jeff Law for his direction via the steering committee, + coordinating the entire egcs project and GCC 2.95, rolling out + snapshots and releases, handling merges from GCC2, reviewing tons + of patches that might have fallen through the cracks else, and + random but extensive hacking. + + * Marc Lehmann for his direction via the steering committee and + helping with analysis and improvements of x86 performance. + + * Ted Lemon wrote parts of the RTL reader and printer. + + * Kriang Lerdsuwanakij for improvements to demangler and various c++ + fixes. + + * Warren Levy for tremendous work on libgcj (Java Runtime Library) + and random work on the Java front end. + + * Alain Lichnewsky ported GCC to the MIPS CPU. + + * Oskar Liljeblad for hacking on AWT and his many Java bug reports + and patches. + + * Robert Lipe for OpenServer support, new testsuites, testing, etc. + + * Weiwen Liu for testing and various bugfixes. + + * Dave Love for his ongoing work with the Fortran front end and + runtime libraries. + + * Martin von Lo"wis for internal consistency checking infrastructure, + various C++ improvements including namespace support, and tons of + assistance with libstdc++/compiler merges. + + * H.J. Lu for his previous contributions to the steering committee, + many x86 bug reports, prototype patches, and keeping the GNU/Linux + ports working. + + * Greg McGary for random fixes and (someday) bounded pointers. + + * Andrew MacLeod for his ongoing work in building a real EH system, + various code generation improvements, work on the global + optimizer, etc. + + * Vladimir Makarov for hacking some ugly i960 problems, PowerPC + hacking improvements to compile-time performance, overall + knowledge and direction in the area of instruction scheduling, and + design and implementation of the automaton based instruction + scheduler. + + * Bob Manson for his behind the scenes work on dejagnu. + + * Philip Martin for lots of libstdc++ string and vector iterator + fixes and improvements, and string clean up and testsuites. + + * All of the Mauve project contributors, for Java test code. + + * Bryce McKinlay for numerous GCJ and libgcj fixes and improvements. + + * Adam Megacz for his work on the Win32 port of GCJ. + + * Michael Meissner for LRS framework, ia32, m32r, v850, m88k, MIPS, + powerpc, haifa, ECOFF debug support, and other assorted hacking. + + * Jason Merrill for his direction via the steering committee and + leading the g++ effort. + + * David Miller for his direction via the steering committee, lots of + SPARC work, improvements in jump.c and interfacing with the Linux + kernel developers. + + * Gary Miller ported GCC to Charles River Data Systems machines. + + * Alfred Minarik for libstdc++ string and ios bugfixes, and turning + the entire libstdc++ testsuite namespace-compatible. + + * Mark Mitchell for his direction via the steering committee, + mountains of C++ work, load/store hoisting out of loops, alias + analysis improvements, ISO C `restrict' support, and serving as + release manager for GCC 3.x. + + * Alan Modra for various GNU/Linux bits and testing. + + * Toon Moene for his direction via the steering committee, Fortran + maintenance, and his ongoing work to make us make Fortran run fast. + + * Jason Molenda for major help in the care and feeding of all the + services on the gcc.gnu.org (formerly egcs.cygnus.com) + machine--mail, web services, ftp services, etc etc. Doing all + this work on scrap paper and the backs of envelopes would have + been... difficult. + + * Catherine Moore for fixing various ugly problems we have sent her + way, including the haifa bug which was killing the Alpha & PowerPC + Linux kernels. + + * Mike Moreton for his various Java patches. + + * David Mosberger-Tang for various Alpha improvements. + + * Stephen Moshier contributed the floating point emulator that + assists in cross-compilation and permits support for floating + point numbers wider than 64 bits and for ISO C99 support. + + * Bill Moyer for his behind the scenes work on various issues. + + * Philippe De Muyter for his work on the m68k port. + + * Joseph S. Myers for his work on the PDP-11 port, format checking + and ISO C99 support, and continuous emphasis on (and contributions + to) documentation. + + * Nathan Myers for his work on libstdc++-v3: architecture and + authorship through the first three snapshots, including + implementation of locale infrastructure, string, shadow C headers, + and the initial project documentation (DESIGN, CHECKLIST, and so + forth). Later, more work on MT-safe string and shadow headers. + + * Felix Natter for documentation on porting libstdc++. + + * NeXT, Inc. donated the front end that supports the Objective-C + language. + + * Hans-Peter Nilsson for the CRIS and MMIX ports, improvements to + the search engine setup, various documentation fixes and other + small fixes. + + * Geoff Noer for this work on getting cygwin native builds working. + + * David O'Brien for the FreeBSD/alpha, FreeBSD/AMD x86-64, + FreeBSD/ARM, FreeBSD/PowerPC, and FreeBSD/SPARC64 ports and + related infrastructure improvements. + + * Alexandre Oliva for various build infrastructure improvements, + scripts and amazing testing work, including keeping libtool issues + sane and happy. + + * Melissa O'Neill for various NeXT fixes. + + * Rainer Orth for random MIPS work, including improvements to our o32 + ABI support, improvements to dejagnu's MIPS support, Java + configuration clean-ups and porting work, etc. + + * Paul Petersen wrote the machine description for the Alliant FX/8. + + * Alexandre Petit-Bianco for implementing much of the Java compiler + and continued Java maintainership. + + * Matthias Pfaller for major improvements to the NS32k port. + + * Gerald Pfeifer for his direction via the steering committee, + pointing out lots of problems we need to solve, maintenance of the + web pages, and taking care of documentation maintenance in general. + + * Ovidiu Predescu for his work on the Objective-C front end and + runtime libraries. + + * Ken Raeburn for various improvements to checker, MIPS ports and + various cleanups in the compiler. + + * Rolf W. Rasmussen for hacking on AWT. + + * David Reese of Sun Microsystems contributed to the Solaris on + PowerPC port. + + * Joern Rennecke for maintaining the sh port, loop, regmove & reload + hacking. + + * Loren J. Rittle for improvements to libstdc++-v3 including the + FreeBSD port, threading fixes, thread-related configury changes, + critical threading documentation, and solutions to really tricky + I/O problems. + + * Craig Rodrigues for processing tons of bug reports. + + * Gavin Romig-Koch for lots of behind the scenes MIPS work. + + * Ken Rose for fixes to our delay slot filling code. + + * Paul Rubin wrote most of the preprocessor. + + * Chip Salzenberg for libstdc++ patches and improvements to locales, + traits, Makefiles, libio, libtool hackery, and "long long" support. + + * Juha Sarlin for improvements to the H8 code generator. + + * Greg Satz assisted in making GCC work on HP-UX for the 9000 series + 300. + + * Bradley Schatz for his work on the GCJ FAQ. + + * Peter Schauer wrote the code to allow debugging to work on the + Alpha. + + * William Schelter did most of the work on the Intel 80386 support. + + * Bernd Schmidt for various code generation improvements and major + work in the reload pass as well a serving as release manager for + GCC 2.95.3. + + * Peter Schmid for constant testing of libstdc++ - especially + application testing, going above and beyond what was requested for + the release criteria - and libstdc++ header file tweaks. + + * Jason Schroeder for jcf-dump patches. + + * Andreas Schwab for his work on the m68k port. + + * Joel Sherrill for his direction via the steering committee, RTEMS + contributions and RTEMS testing. + + * Nathan Sidwell for many C++ fixes/improvements. + + * Jeffrey Siegal for helping RMS with the original design of GCC, + some code which handles the parse tree and RTL data structures, + constant folding and help with the original VAX & m68k ports. + + * Kenny Simpson for prompting libstdc++ fixes due to defect reports + from the LWG (thereby keeping us in line with updates from the + ISO). + + * Franz Sirl for his ongoing work with making the PPC port stable + for linux. + + * Andrey Slepuhin for assorted AIX hacking. + + * Christopher Smith did the port for Convex machines. + + * Randy Smith finished the Sun FPA support. + + * Scott Snyder for queue, iterator, istream, and string fixes and + libstdc++ testsuite entries. + + * Brad Spencer for contributions to the GLIBCPP_FORCE_NEW technique. + + * Richard Stallman, for writing the original gcc and launching the + GNU project. + + * Jan Stein of the Chalmers Computer Society provided support for + Genix, as well as part of the 32000 machine description. + + * Nigel Stephens for various mips16 related fixes/improvements. + + * Jonathan Stone wrote the machine description for the Pyramid + computer. + + * Graham Stott for various infrastructure improvements. + + * John Stracke for his Java HTTP protocol fixes. + + * Mike Stump for his Elxsi port, g++ contributions over the years + and more recently his vxworks contributions + + * Jeff Sturm for Java porting help, bug fixes, and encouragement. + + * Shigeya Suzuki for this fixes for the bsdi platforms. + + * Ian Lance Taylor for his mips16 work, general configury hacking, + fixincludes, etc. + + * Holger Teutsch provided the support for the Clipper CPU. + + * Gary Thomas for his ongoing work to make the PPC work for + GNU/Linux. + + * Philipp Thomas for random bugfixes throughout the compiler + + * Jason Thorpe for thread support in libstdc++ on NetBSD. + + * Kresten Krab Thorup wrote the run time support for the Objective-C + language and the fantastic Java bytecode interpreter. + + * Michael Tiemann for random bugfixes, the first instruction + scheduler, initial C++ support, function integration, NS32k, SPARC + and M88k machine description work, delay slot scheduling. + + * Andreas Tobler for his work porting libgcj to Darwin. + + * Teemu Torma for thread safe exception handling support. + + * Leonard Tower wrote parts of the parser, RTL generator, and RTL + definitions, and of the VAX machine description. + + * Tom Tromey for internationalization support and for his many Java + contributions and libgcj maintainership. + + * Lassi Tuura for improvements to config.guess to determine HP + processor types. + + * Petter Urkedal for libstdc++ CXXFLAGS, math, and algorithms fixes. + + * Brent Verner for work with the libstdc++ cshadow files and their + associated configure steps. + + * Todd Vierling for contributions for NetBSD ports. + + * Jonathan Wakely for contributing libstdc++ Doxygen notes and XHTML + guidance. + + * Dean Wakerley for converting the install documentation from HTML + to texinfo in time for GCC 3.0. + + * Krister Walfridsson for random bugfixes. + + * Stephen M. Webb for time and effort on making libstdc++ shadow + files work with the tricky Solaris 8+ headers, and for pushing the + build-time header tree. + + * John Wehle for various improvements for the x86 code generator, + related infrastructure improvements to help x86 code generation, + value range propagation and other work, WE32k port. + + * Zack Weinberg for major work on cpplib and various other bugfixes. + + * Matt Welsh for help with Linux Threads support in GCJ. + + * Urban Widmark for help fixing java.io. + + * Mark Wielaard for new Java library code and his work integrating + with Classpath. + + * Dale Wiles helped port GCC to the Tahoe. + + * Bob Wilson from Tensilica, Inc. for the Xtensa port. + + * Jim Wilson for his direction via the steering committee, tackling + hard problems in various places that nobody else wanted to work + on, strength reduction and other loop optimizations. + + * Carlo Wood for various fixes. + + * Tom Wood for work on the m88k port. + + * Masanobu Yuhara of Fujitsu Laboratories implemented the machine + description for the Tron architecture (specifically, the Gmicro). + + * Kevin Zachmann helped ported GCC to the Tahoe. + + * Gilles Zunino for help porting Java to Irix. + + + We'd also like to thank the folks who have contributed time and + energy in testing GCC: + + * Michael Abd-El-Malek + + * Thomas Arend + + * Bonzo Armstrong + + * Steven Ashe + + * Chris Baldwin + + * David Billinghurst + + * Jim Blandy + + * Stephane Bortzmeyer + + * Horst von Brand + + * Frank Braun + + * Rodney Brown + + * Joe Buck + + * Craig Burley + + * Sidney Cadot + + * Bradford Castalia + + * Ralph Doncaster + + * Ulrich Drepper + + * David Edelsohn + + * Richard Emberson + + * Levente Farkas + + * Graham Fawcett + + * Robert A. French + + * Jo"rgen Freyh + + * Mark K. Gardner + + * Charles-Antoine Gauthier + + * Yung Shing Gene + + * Kaveh Ghazi + + * David Gilbert + + * Simon Gornall + + * Fred Gray + + * John Griffin + + * Patrik Hagglund + + * Phil Hargett + + * Amancio Hasty + + * Bryan W. Headley + + * Kate Hedstrom + + * Richard Henderson + + * Kevin B. Hendricks + + * Manfred Hollstein + + * Kamil Iskra + + * Joep Jansen + + * Christian Joensson + + * David Kidd + + * Tobias Kuipers + + * Anand Krishnaswamy + + * Jeff Law + + * Robert Lipe + + * llewelly + + * Damon Love + + * Dave Love + + * H.J. Lu + + * Brad Lucier + + * Mumit Khan + + * Matthias Klose + + * Martin Knoblauch + + * Jesse Macnish + + * David Miller + + * Toon Moene + + * Stefan Morrell + + * Anon A. Mous + + * Matthias Mueller + + * Pekka Nikander + + * Alexandre Oliva + + * Jon Olson + + * Magnus Persson + + * Chris Pollard + + * Richard Polton + + * David Rees + + * Paul Reilly + + * Tom Reilly + + * Loren J. Rittle + + * Torsten Rueger + + * Danny Sadinoff + + * Marc Schifer + + * Peter Schmid + + * David Schuler + + * Vin Shelton + + * Franz Sirl + + * Tim Souder + + * Mike Stump + + * Adam Sulmicki + + * George Talbot + + * Gregory Warnes + + * Carlo Wood + + * David E. Young + + * And many others + + And finally we'd like to thank everyone who uses the compiler, + submits bug reports and generally reminds us why we're doing this work + in the first place. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-22 gcc-3.2.3/gcc/doc/gcc.info-22 *** gcc-3.2.2/gcc/doc/gcc.info-22 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-22 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,1224 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Option Index, Next: Index, Prev: Contributors, Up: Top + + Option Index + ************ + + GCC's command line options are indexed here without any initial `-' + or `--'. Where an option has both positive and negative forms (such as + `-fOPTION' and `-fno-OPTION'), relevant entries in the manual are + indexed under the most appropriate form; it may sometimes be useful to + look up both forms. + + * Menu: + + * ###: Overall Options. + * $: Preprocessor Options. + * A: Preprocessor Options. + * A-: Preprocessor Options. + * ansi <1>: Non-bugs. + * ansi <2>: Other Builtins. + * ansi <3>: Preprocessor Options. + * ansi <4>: C Dialect Options. + * ansi: Standards. + * aux-info: C Dialect Options. + * b: Target Options. + * B: Directory Options. + * bcopy-builtin: PDP-11 Options. + * c: Link Options. + * C: Preprocessor Options. + * c: Overall Options. + * D: Preprocessor Options. + * d: Debugging Options. + * da: Debugging Options. + * dA: Debugging Options. + * dB: Debugging Options. + * db: Debugging Options. + * dC: Debugging Options. + * dc: Debugging Options. + * dD <1>: Preprocessor Options. + * dD: Debugging Options. + * dd: Debugging Options. + * dE: Debugging Options. + * de: Debugging Options. + * dF: Debugging Options. + * df: Debugging Options. + * dG: Debugging Options. + * dg: Debugging Options. + * dh: Debugging Options. + * dI: Preprocessor Options. + * di: Debugging Options. + * dj: Debugging Options. + * dk: Debugging Options. + * dL: Debugging Options. + * dl: Debugging Options. + * dM: Preprocessor Options. + * dm: Debugging Options. + * dM: Debugging Options. + * dN <1>: Preprocessor Options. + * dN: Debugging Options. + * dn: Debugging Options. + * do: Debugging Options. + * dP: Debugging Options. + * dp: Debugging Options. + * dR: Debugging Options. + * dr: Debugging Options. + * dS: Debugging Options. + * ds: Debugging Options. + * dt: Debugging Options. + * dumpmachine: Debugging Options. + * dumpspecs: Debugging Options. + * dumpversion: Debugging Options. + * dv: Debugging Options. + * dw: Debugging Options. + * dx: Debugging Options. + * dX: Debugging Options. + * dy: Debugging Options. + * dz: Debugging Options. + * E <1>: Link Options. + * E: Overall Options. + * EB <1>: ARC Options. + * EB: MIPS Options. + * EL <1>: ARC Options. + * EL: MIPS Options. + * falign-functions: Optimize Options. + * falign-jumps: Optimize Options. + * falign-labels: Optimize Options. + * falign-loops: Optimize Options. + * fallow-single-precision: C Dialect Options. + * falt-external-templates <1>: Template Instantiation. + * falt-external-templates: C++ Dialect Options. + * fargument-alias: Code Gen Options. + * fargument-noalias: Code Gen Options. + * fargument-noalias-global: Code Gen Options. + * fbounds-check: Optimize Options. + * fbranch-probabilities: Optimize Options. + * fcall-saved <1>: Interoperation. + * fcall-saved: Code Gen Options. + * fcall-used: Code Gen Options. + * fcaller-saves: Optimize Options. + * fcheck-new: C++ Dialect Options. + * fcond-mismatch: C Dialect Options. + * fconserve-space: C++ Dialect Options. + * fconstant-string-class: Objective-C Dialect Options. + * fcse-follow-jumps: Optimize Options. + * fcse-skip-blocks: Optimize Options. + * fdata-sections: Optimize Options. + * fdelayed-branch: Optimize Options. + * fdelete-null-pointer-checks: Optimize Options. + * fdiagnostics-show-location: Language Independent Options. + * fdollars-in-identifiers <1>: Interoperation. + * fdollars-in-identifiers: C++ Dialect Options. + * fdump-class-hierarchy: Debugging Options. + * fdump-translation-unit: Debugging Options. + * fdump-tree: Debugging Options. + * fdump-unnumbered: Debugging Options. + * fexceptions: Code Gen Options. + * fexpensive-optimizations: Optimize Options. + * fexternal-templates <1>: Template Instantiation. + * fexternal-templates: C++ Dialect Options. + * ffast-math: Optimize Options. + * ffixed: Code Gen Options. + * ffloat-store <1>: Disappointments. + * ffloat-store: Optimize Options. + * ffor-scope: C++ Dialect Options. + * fforce-addr: Optimize Options. + * fforce-mem: Optimize Options. + * ffreestanding <1>: Function Attributes. + * ffreestanding <2>: C Dialect Options. + * ffreestanding: Standards. + * ffunction-sections: Optimize Options. + * fgcse: Optimize Options. + * fgcse-lm: Optimize Options. + * fgcse-sm: Optimize Options. + * fgnu-runtime: Objective-C Dialect Options. + * fhosted: C Dialect Options. + * finhibit-size-directive: Code Gen Options. + * finline-functions: Optimize Options. + * finline-limit: Optimize Options. + * finstrument-functions <1>: Function Attributes. + * finstrument-functions: Code Gen Options. + * fkeep-inline-functions <1>: Inline. + * fkeep-inline-functions: Optimize Options. + * fkeep-static-consts: Optimize Options. + * fleading-underscore: Code Gen Options. + * fmem-report: Debugging Options. + * fmessage-length: Language Independent Options. + * fmove-all-movables: Optimize Options. + * fms-extensions: C++ Dialect Options. + * fnext-runtime: Objective-C Dialect Options. + * fno-access-control: C++ Dialect Options. + * fno-asm: C Dialect Options. + * fno-branch-count-reg: Optimize Options. + * fno-builtin <1>: Other Builtins. + * fno-builtin: C Dialect Options. + * fno-common <1>: Variable Attributes. + * fno-common: Code Gen Options. + * fno-const-strings: C++ Dialect Options. + * fno-cprop-registers: Optimize Options. + * fno-default-inline <1>: Inline. + * fno-default-inline <2>: Optimize Options. + * fno-default-inline: C++ Dialect Options. + * fno-defer-pop: Optimize Options. + * fno-elide-constructors: C++ Dialect Options. + * fno-enforce-eh-specs: C++ Dialect Options. + * fno-for-scope: C++ Dialect Options. + * fno-function-cse: Optimize Options. + * fno-gnu-keywords: C++ Dialect Options. + * fno-gnu-linker: Code Gen Options. + * fno-guess-branch-probability: Optimize Options. + * fno-ident: Code Gen Options. + * fno-implement-inlines <1>: C++ Interface. + * fno-implement-inlines: C++ Dialect Options. + * fno-implicit-inline-templates: C++ Dialect Options. + * fno-implicit-templates <1>: Template Instantiation. + * fno-implicit-templates: C++ Dialect Options. + * fno-inline: Optimize Options. + * fno-math-errno: Optimize Options. + * fno-nonansi-builtins: C++ Dialect Options. + * fno-operator-names: C++ Dialect Options. + * fno-optional-diags: C++ Dialect Options. + * fno-peephole: Optimize Options. + * fno-peephole2: Optimize Options. + * fno-rtti: C++ Dialect Options. + * fno-sched-interblock: Optimize Options. + * fno-sched-spec: Optimize Options. + * fno-show-column: Preprocessor Options. + * fno-signed-bitfields: C Dialect Options. + * fno-stack-limit: Code Gen Options. + * fno-trapping-math: Optimize Options. + * fno-unsigned-bitfields: C Dialect Options. + * fno-weak: C++ Dialect Options. + * fnon-call-exceptions: Code Gen Options. + * fomit-frame-pointer: Optimize Options. + * foptimize-register-move: Optimize Options. + * foptimize-sibling-calls: Optimize Options. + * fpack-struct: Code Gen Options. + * fpcc-struct-return <1>: Incompatibilities. + * fpcc-struct-return: Code Gen Options. + * fpermissive: C++ Dialect Options. + * fPIC: Code Gen Options. + * fpic: Code Gen Options. + * fprefetch-loop-arrays: Optimize Options. + * fpreprocessed: Preprocessor Options. + * fpretend-float: Debugging Options. + * fprofile-arcs <1>: Other Builtins. + * fprofile-arcs: Debugging Options. + * freduce-all-givs: Optimize Options. + * freg-struct-return: Code Gen Options. + * fregmove: Optimize Options. + * frename-registers: Optimize Options. + * frepo <1>: Template Instantiation. + * frepo: C++ Dialect Options. + * frerun-cse-after-loop: Optimize Options. + * frerun-loop-opt: Optimize Options. + * fsched-spec-load: Optimize Options. + * fsched-spec-load-dangerous: Optimize Options. + * fsched-verbose: Debugging Options. + * fschedule-insns: Optimize Options. + * fschedule-insns2: Optimize Options. + * fshared-data: Code Gen Options. + * fshort-double: Code Gen Options. + * fshort-enums <1>: Non-bugs. + * fshort-enums <2>: Type Attributes. + * fshort-enums: Code Gen Options. + * fshort-wchar: Code Gen Options. + * fsigned-bitfields <1>: Non-bugs. + * fsigned-bitfields: C Dialect Options. + * fsigned-char: C Dialect Options. + * fsingle-precision-constant: Optimize Options. + * fssa: Optimize Options. + * fssa-ccp: Optimize Options. + * fssa-dce: Optimize Options. + * fstack-check: Code Gen Options. + * fstack-limit-register: Code Gen Options. + * fstack-limit-symbol: Code Gen Options. + * fstats: C++ Dialect Options. + * fstrength-reduce: Optimize Options. + * fstrict-aliasing: Optimize Options. + * fsyntax-only: Warning Options. + * ftabstop: Preprocessor Options. + * ftemplate-depth: C++ Dialect Options. + * ftest-coverage: Debugging Options. + * fthread-jumps: Optimize Options. + * ftime-report: Debugging Options. + * ftrapv: Optimize Options. + * funroll-all-loops: Optimize Options. + * funroll-loops <1>: Non-bugs. + * funroll-loops: Optimize Options. + * funsafe-math-optimizations: Optimize Options. + * funsigned-bitfields <1>: Non-bugs. + * funsigned-bitfields: C Dialect Options. + * funsigned-char: C Dialect Options. + * funwind-tables: Code Gen Options. + * fuse-cxa-atexit: C++ Dialect Options. + * fverbose-asm: Code Gen Options. + * fvolatile: Code Gen Options. + * fvolatile-global: Code Gen Options. + * fvolatile-static: Code Gen Options. + * fvtable-gc: C++ Dialect Options. + * fwritable-strings <1>: Incompatibilities. + * fwritable-strings: C Dialect Options. + * G <1>: System V Options. + * G <2>: MIPS Options. + * G <3>: RS/6000 and PowerPC Options. + * G: M32R/D Options. + * g: Debugging Options. + * gcc: Preprocessor Options. + * gcoff: Debugging Options. + * gdwarf: Debugging Options. + * gdwarf+: Debugging Options. + * gdwarf-2: Debugging Options. + * gen-decls: Objective-C Dialect Options. + * ggdb: Debugging Options. + * gstabs: Debugging Options. + * gstabs+: Debugging Options. + * gvms: Debugging Options. + * gxcoff: Debugging Options. + * gxcoff+: Debugging Options. + * H: Preprocessor Options. + * h: Preprocessor Options. + * help <1>: Preprocessor Options. + * help: Overall Options. + * I <1>: Directory Options. + * I: Preprocessor Options. + * I- <1>: Directory Options. + * I-: Preprocessor Options. + * idirafter: Preprocessor Options. + * imacros: Preprocessor Options. + * include: Preprocessor Options. + * iprefix: Preprocessor Options. + * isystem: Preprocessor Options. + * iwithprefix: Preprocessor Options. + * iwithprefixbefore: Preprocessor Options. + * L: Directory Options. + * l: Link Options. + * lobjc: Link Options. + * M: Preprocessor Options. + * m1: SH Options. + * m10: PDP-11 Options. + * m128bit-long-double: i386 and x86-64 Options. + * m16-bit: CRIS Options. + * m2: SH Options. + * m210: MCore Options. + * m29000: AMD29K Options. + * m29050: AMD29K Options. + * m3: SH Options. + * m31: S/390 and zSeries Options. + * m32 <1>: i386 and x86-64 Options. + * m32: SPARC Options. + * m32-bit: CRIS Options. + * m32032: NS32K Options. + * m32081: NS32K Options. + * m32332: NS32K Options. + * m32381: NS32K Options. + * m32532: NS32K Options. + * m32r: M32R/D Options. + * m32rx: M32R/D Options. + * m340: MCore Options. + * m386: i386 and x86-64 Options. + * m3dnow: i386 and x86-64 Options. + * m3e: SH Options. + * m4: SH Options. + * m4-nofpu: SH Options. + * m4-single: SH Options. + * m4-single-only: SH Options. + * m40: PDP-11 Options. + * m45: PDP-11 Options. + * m4650: MIPS Options. + * m486: i386 and x86-64 Options. + * m4byte-functions: MCore Options. + * m5200: M680x0 Options. + * m64 <1>: S/390 and zSeries Options. + * m64 <2>: i386 and x86-64 Options. + * m64: SPARC Options. + * m68000: M680x0 Options. + * m68020: M680x0 Options. + * m68020-40: M680x0 Options. + * m68020-60: M680x0 Options. + * m68030: M680x0 Options. + * m68040: M680x0 Options. + * m68060: M680x0 Options. + * m6811: M68hc1x Options. + * m6812: M68hc1x Options. + * m68881: M680x0 Options. + * m68hc11: M68hc1x Options. + * m68hc12: M68hc1x Options. + * m8-bit: CRIS Options. + * m88000: M88K Options. + * m88100: M88K Options. + * m88110: M88K Options. + * m96bit-long-double: i386 and x86-64 Options. + * mabi-mmixware: MMIX Options. + * mabi=32: MIPS Options. + * mabi=64: MIPS Options. + * mabi=altivec: RS/6000 and PowerPC Options. + * mabi=eabi: MIPS Options. + * mabi=gnu: MMIX Options. + * mabi=n32: MIPS Options. + * mabi=no-altivec: RS/6000 and PowerPC Options. + * mabi=o64: MIPS Options. + * mabicalls: MIPS Options. + * mabort-on-noreturn: ARM Options. + * mabshi: PDP-11 Options. + * mac0: PDP-11 Options. + * maccumulate-outgoing-args: i386 and x86-64 Options. + * mads: RS/6000 and PowerPC Options. + * maix-struct-return: RS/6000 and PowerPC Options. + * maix32: RS/6000 and PowerPC Options. + * maix64: RS/6000 and PowerPC Options. + * malign-300: H8/300 Options. + * malign-double: i386 and x86-64 Options. + * malign-int: M680x0 Options. + * malignment-traps: ARM Options. + * malpha-as: DEC Alpha Options. + * maltivec: RS/6000 and PowerPC Options. + * mam33: MN10300 Options. + * maout: CRIS Options. + * mapcs: ARM Options. + * mapcs-26: ARM Options. + * mapcs-32: ARM Options. + * mapcs-frame: ARM Options. + * mapp-regs: SPARC Options. + * march <1>: CRIS Options. + * march <2>: HPPA Options. + * march <3>: i386 and x86-64 Options. + * march <4>: MIPS Options. + * march: ARM Options. + * margcount: Convex Options. + * masm-compat: Intel 960 Options. + * masm-optimize: D30V Options. + * masm=DIALECT: i386 and x86-64 Options. + * mauto-incdec: M68hc1x Options. + * mauto-pic: IA-64 Options. + * mb: SH Options. + * mb-step: IA-64 Options. + * mbackchain: S/390 and zSeries Options. + * mbase-addresses: MMIX Options. + * mbcopy: PDP-11 Options. + * mbig <1>: TMS320C3x/C4x Options. + * mbig: RS/6000 and PowerPC Options. + * mbig-endian <1>: Xtensa Options. + * mbig-endian <2>: IA-64 Options. + * mbig-endian <3>: MCore Options. + * mbig-endian <4>: RS/6000 and PowerPC Options. + * mbig-endian: ARM Options. + * mbig-memory: TMS320C3x/C4x Options. + * mbig-pic: M88K Options. + * mbig-switch <1>: V850 Options. + * mbig-switch: HPPA Options. + * mbigtable: SH Options. + * mbit-align: RS/6000 and PowerPC Options. + * mbitfield <1>: NS32K Options. + * mbitfield: M680x0 Options. + * mbk: TMS320C3x/C4x Options. + * mbooleans: Xtensa Options. + * mbranch-cheap: PDP-11 Options. + * mbranch-cost: D30V Options. + * mbranch-expensive: PDP-11 Options. + * mbranch-predict: MMIX Options. + * mbroken-saverestore: SPARC Options. + * mbsd: ARM Options. + * mbuild-constants: DEC Alpha Options. + * mbw: AMD29K Options. + * mbwx: DEC Alpha Options. + * mc1: Convex Options. + * mc2: Convex Options. + * mc300: Clipper Options. + * mc32: Convex Options. + * mc34: Convex Options. + * mc38: Convex Options. + * mc400: Clipper Options. + * mc68000: M680x0 Options. + * mc68020: M680x0 Options. + * mca: Intel 960 Options. + * mcall-aix: RS/6000 and PowerPC Options. + * mcall-gnu: RS/6000 and PowerPC Options. + * mcall-lib-mul: RT Options. + * mcall-linux: RS/6000 and PowerPC Options. + * mcall-netbsd: RS/6000 and PowerPC Options. + * mcall-prologues: AVR Options. + * mcall-solaris: RS/6000 and PowerPC Options. + * mcall-sysv: RS/6000 and PowerPC Options. + * mcall-sysv-eabi: RS/6000 and PowerPC Options. + * mcall-sysv-noeabi: RS/6000 and PowerPC Options. + * mcallee-super-interworking: ARM Options. + * mcaller-super-interworking: ARM Options. + * mcallgraph-data: MCore Options. + * mcc-init: CRIS Options. + * mcf: Intel 960 Options. + * mcheck-zero-division: M88K Options. + * mcix: DEC Alpha Options. + * mcmodel=embmedany: SPARC Options. + * mcmodel=kernel: i386 and x86-64 Options. + * mcmodel=large: i386 and x86-64 Options. + * mcmodel=medany: SPARC Options. + * mcmodel=medium: i386 and x86-64 Options. + * mcmodel=medlow: SPARC Options. + * mcmodel=medmid: SPARC Options. + * mcmodel=small: i386 and x86-64 Options. + * mcode-align: Intel 960 Options. + * mcode-model=large: M32R/D Options. + * mcode-model=medium: M32R/D Options. + * mcode-model=small: M32R/D Options. + * mcomplex-addr: Intel 960 Options. + * mcond-exec: D30V Options. + * mconst-align: CRIS Options. + * mconstant-gp: IA-64 Options. + * mcpu <1>: CRIS Options. + * mcpu <2>: ARC Options. + * mcpu <3>: TMS320C3x/C4x Options. + * mcpu <4>: DEC Alpha Options. + * mcpu <5>: i386 and x86-64 Options. + * mcpu <6>: MIPS Options. + * mcpu <7>: RS/6000 and PowerPC Options. + * mcpu <8>: ARM Options. + * mcpu: SPARC Options. + * mcpu32: M680x0 Options. + * mcypress: SPARC Options. + * MD: Preprocessor Options. + * mdalign: SH Options. + * mdata: ARC Options. + * mdata-align: CRIS Options. + * mdb: TMS320C3x/C4x Options. + * mdebug: S/390 and zSeries Options. + * mdec-asm: PDP-11 Options. + * mdensity: Xtensa Options. + * mdisable-fpregs: HPPA Options. + * mdisable-indexing: HPPA Options. + * mdiv: MCore Options. + * mdouble-float: MIPS Options. + * mdp-isr-reload: TMS320C3x/C4x Options. + * mdw: AMD29K Options. + * mdwarf2-asm: IA-64 Options. + * meabi: RS/6000 and PowerPC Options. + * melf <1>: MMIX Options. + * melf: CRIS Options. + * melinux: CRIS Options. + * melinux-stacksize: CRIS Options. + * memb: RS/6000 and PowerPC Options. + * membedded-data: MIPS Options. + * membedded-pic: MIPS Options. + * mentry: MIPS Options. + * mep: V850 Options. + * mepsilon: MMIX Options. + * metrax100: CRIS Options. + * metrax4: CRIS Options. + * mexplicit-relocs: DEC Alpha Options. + * mextmem: D30V Options. + * mextmemory: D30V Options. + * MF: Preprocessor Options. + * mfast-fix: TMS320C3x/C4x Options. + * mfast-indirect-calls: HPPA Options. + * mfaster-structs: SPARC Options. + * mfix: DEC Alpha Options. + * mfix7000: MIPS Options. + * mfixed-range: IA-64 Options. + * mflat: SPARC Options. + * mfloat-ieee: DEC Alpha Options. + * mfloat-vax: DEC Alpha Options. + * mfloat32: PDP-11 Options. + * mfloat64: PDP-11 Options. + * mflush-func: MIPS Options. + * mfmovd: SH Options. + * mfp: ARM Options. + * mfp-arg-in-fpregs: RT Options. + * mfp-arg-in-gregs: RT Options. + * mfp-reg: DEC Alpha Options. + * mfp-rounding-mode: DEC Alpha Options. + * mfp-trap-mode: DEC Alpha Options. + * mfp32: MIPS Options. + * mfp64: MIPS Options. + * mfpa: M680x0 Options. + * mfpe: ARM Options. + * mfpu <1>: PDP-11 Options. + * mfpu: SPARC Options. + * mfull-fp-blocks: RT Options. + * mfull-toc: RS/6000 and PowerPC Options. + * mfused-madd <1>: Xtensa Options. + * mfused-madd <2>: MIPS Options. + * mfused-madd: RS/6000 and PowerPC Options. + * mg: VAX Options. + * MG: Preprocessor Options. + * mgas <1>: DEC Alpha Options. + * mgas <2>: HPPA Options. + * mgas: MIPS Options. + * mgnu: VAX Options. + * mgnu-as: IA-64 Options. + * mgnu-ld: IA-64 Options. + * mgotplt: CRIS Options. + * mgp32: MIPS Options. + * mgp64: MIPS Options. + * mgpopt: MIPS Options. + * mh: H8/300 Options. + * mhalf-pic: MIPS Options. + * mhandle-large-shift: M88K Options. + * mhard-float <1>: Xtensa Options. + * mhard-float <2>: S/390 and zSeries Options. + * mhard-float <3>: MIPS Options. + * mhard-float <4>: RS/6000 and PowerPC Options. + * mhard-float <5>: ARM Options. + * mhard-float: SPARC Options. + * mhard-quad-float: SPARC Options. + * mhardlit: MCore Options. + * mhc-struct-return <1>: Interoperation. + * mhc-struct-return: RT Options. + * mhimem: NS32K Options. + * mhitachi: SH Options. + * mic-compat: Intel 960 Options. + * mic2.0-compat: Intel 960 Options. + * mic3.0-compat: Intel 960 Options. + * midentify-revision: M88K Options. + * mieee <1>: SH Options. + * mieee: DEC Alpha Options. + * mieee-conformant: DEC Alpha Options. + * mieee-fp: i386 and x86-64 Options. + * mieee-with-inexact: DEC Alpha Options. + * mimpure-text: AMD29K Options. + * min-line-mul: RT Options. + * minit-stack: AVR Options. + * minline-all-stringops: i386 and x86-64 Options. + * minline-divide-max-throughput: IA-64 Options. + * minline-divide-min-latency: IA-64 Options. + * mint16: PDP-11 Options. + * mint32 <1>: PDP-11 Options. + * mint32: H8/300 Options. + * mint64: MIPS Options. + * mintel-asm: Intel 960 Options. + * mips1: MIPS Options. + * mips16: MIPS Options. + * mips2: MIPS Options. + * mips3: MIPS Options. + * mips4: MIPS Options. + * misize: SH Options. + * mjump-in-delay: HPPA Options. + * mka: Intel 960 Options. + * mkb: Intel 960 Options. + * mkernel-registers: AMD29K Options. + * mknuthdiv: MMIX Options. + * ml: SH Options. + * mlarge: AMD29K Options. + * mlarge-data: DEC Alpha Options. + * mleaf-procedures: Intel 960 Options. + * mlibfuncs: MMIX Options. + * mlinker-opt: HPPA Options. + * mlinux: CRIS Options. + * mlittle: RS/6000 and PowerPC Options. + * mlittle-endian <1>: Xtensa Options. + * mlittle-endian <2>: IA-64 Options. + * mlittle-endian <3>: MCore Options. + * mlittle-endian <4>: RS/6000 and PowerPC Options. + * mlittle-endian <5>: ARM Options. + * mlittle-endian: SPARC Options. + * mlive-g0: SPARC Options. + * mlong-calls <1>: V850 Options. + * mlong-calls <2>: MIPS Options. + * mlong-calls: ARM Options. + * mlong-double-64: Intel 960 Options. + * mlong-load-store: HPPA Options. + * mlong32 <1>: MIPS Options. + * mlong32: Convex Options. + * mlong64 <1>: MIPS Options. + * mlong64: Convex Options. + * mlongcalls: Xtensa Options. + * mloop-unsigned: TMS320C3x/C4x Options. + * MM: Preprocessor Options. + * mmac16: Xtensa Options. + * mmad: MIPS Options. + * mmangle-cpu: ARC Options. + * mmax: DEC Alpha Options. + * mmax-stack-frame: CRIS Options. + * mmc: Intel 960 Options. + * mmcu: AVR Options. + * MMD: Preprocessor Options. + * mmemcpy: MIPS Options. + * mmemory-latency: DEC Alpha Options. + * mmemparm: TMS320C3x/C4x Options. + * mminimal-toc: RS/6000 and PowerPC Options. + * mminimum-fp-blocks: RT Options. + * mminmax: Xtensa Options. + * mmips-as: MIPS Options. + * mmips-tfile: MIPS Options. + * mmmx: i386 and x86-64 Options. + * mmpyi: TMS320C3x/C4x Options. + * mmul16: Xtensa Options. + * mmul32: Xtensa Options. + * mmult-bug: MN10300 Options. + * mmulti-add: NS32K Options. + * mmultiple: RS/6000 and PowerPC Options. + * mmvcle: S/390 and zSeries Options. + * mmvme: RS/6000 and PowerPC Options. + * mnbw: AMD29K Options. + * mndw: AMD29K Options. + * mnew-mnemonics: RS/6000 and PowerPC Options. + * mno-3dnow: i386 and x86-64 Options. + * mno-4byte-functions: MCore Options. + * mno-abicalls: MIPS Options. + * mno-abshi: PDP-11 Options. + * mno-ac0: PDP-11 Options. + * mno-align-double: i386 and x86-64 Options. + * mno-align-int: M680x0 Options. + * mno-align-stringops: i386 and x86-64 Options. + * mno-alignment-traps: ARM Options. + * mno-altivec: RS/6000 and PowerPC Options. + * mno-am33: MN10300 Options. + * mno-app-regs: SPARC Options. + * mno-asm-optimize: D30V Options. + * mno-backchain: S/390 and zSeries Options. + * mno-base-addresses: MMIX Options. + * mno-bit-align: RS/6000 and PowerPC Options. + * mno-bk: TMS320C3x/C4x Options. + * mno-booleans: Xtensa Options. + * mno-branch-predict: MMIX Options. + * mno-bwx: DEC Alpha Options. + * mno-callgraph-data: MCore Options. + * mno-check-zero-division: M88K Options. + * mno-cix: DEC Alpha Options. + * mno-code-align: Intel 960 Options. + * mno-complex-addr: Intel 960 Options. + * mno-const-align: CRIS Options. + * mno-crt0: MN10300 Options. + * mno-data-align: CRIS Options. + * mno-db: TMS320C3x/C4x Options. + * mno-debug: S/390 and zSeries Options. + * mno-density: Xtensa Options. + * mno-div: MCore Options. + * mno-dwarf2-asm: IA-64 Options. + * mno-eabi: RS/6000 and PowerPC Options. + * mno-embedded-data: MIPS Options. + * mno-embedded-pic: MIPS Options. + * mno-ep: V850 Options. + * mno-epsilon: MMIX Options. + * mno-explicit-relocs: DEC Alpha Options. + * mno-fancy-math-387: i386 and x86-64 Options. + * mno-fast-fix: TMS320C3x/C4x Options. + * mno-faster-structs: SPARC Options. + * mno-fix: DEC Alpha Options. + * mno-flat: SPARC Options. + * mno-float32: PDP-11 Options. + * mno-float64: PDP-11 Options. + * mno-fp-in-toc: RS/6000 and PowerPC Options. + * mno-fp-regs: DEC Alpha Options. + * mno-fp-ret-in-387: i386 and x86-64 Options. + * mno-fpu: SPARC Options. + * mno-fused-madd <1>: Xtensa Options. + * mno-fused-madd <2>: MIPS Options. + * mno-fused-madd: RS/6000 and PowerPC Options. + * mno-gnu-as: IA-64 Options. + * mno-gnu-ld: IA-64 Options. + * mno-gotplt: CRIS Options. + * mno-gpopt: MIPS Options. + * mno-half-pic: MIPS Options. + * mno-hardlit: MCore Options. + * mno-ieee-fp: i386 and x86-64 Options. + * mno-impure-text: AMD29K Options. + * mno-int16: PDP-11 Options. + * mno-int32: PDP-11 Options. + * mno-interrupts: AVR Options. + * mno-knuthdiv: MMIX Options. + * mno-leaf-procedures: Intel 960 Options. + * mno-libfuncs: MMIX Options. + * mno-long-calls <1>: V850 Options. + * mno-long-calls <2>: MIPS Options. + * mno-long-calls: ARM Options. + * mno-longcalls: Xtensa Options. + * mno-loop-unsigned: TMS320C3x/C4x Options. + * mno-mac16: Xtensa Options. + * mno-mad: MIPS Options. + * mno-max: DEC Alpha Options. + * mno-memcpy: MIPS Options. + * mno-minmax: Xtensa Options. + * mno-mips-tfile: MIPS Options. + * mno-mips16: MIPS Options. + * mno-mmx: i386 and x86-64 Options. + * mno-mpyi: TMS320C3x/C4x Options. + * mno-mul16: Xtensa Options. + * mno-mul32: Xtensa Options. + * mno-mult-bug: MN10300 Options. + * mno-multiple: RS/6000 and PowerPC Options. + * mno-multm: AMD29K Options. + * mno-mvcle: S/390 and zSeries Options. + * mno-nsa: Xtensa Options. + * mno-ocs-debug-info: M88K Options. + * mno-ocs-frame-position: M88K Options. + * mno-optimize-arg-area: M88K Options. + * mno-parallel-insns: TMS320C3x/C4x Options. + * mno-parallel-mpy: TMS320C3x/C4x Options. + * mno-pic: IA-64 Options. + * mno-power: RS/6000 and PowerPC Options. + * mno-power2: RS/6000 and PowerPC Options. + * mno-powerpc: RS/6000 and PowerPC Options. + * mno-powerpc-gfxopt: RS/6000 and PowerPC Options. + * mno-powerpc-gpopt: RS/6000 and PowerPC Options. + * mno-powerpc64: RS/6000 and PowerPC Options. + * mno-prolog-function: V850 Options. + * mno-prologue-epilogue: CRIS Options. + * mno-prototype: RS/6000 and PowerPC Options. + * mno-push-args: i386 and x86-64 Options. + * mno-register-names: IA-64 Options. + * mno-regnames: RS/6000 and PowerPC Options. + * mno-relax-immediate: MCore Options. + * mno-relocatable: RS/6000 and PowerPC Options. + * mno-relocatable-lib: RS/6000 and PowerPC Options. + * mno-reuse-arg-regs: AMD29K Options. + * mno-rnames: MIPS Options. + * mno-rptb: TMS320C3x/C4x Options. + * mno-rpts: TMS320C3x/C4x Options. + * mno-sched-prolog: ARM Options. + * mno-sdata <1>: IA-64 Options. + * mno-sdata: RS/6000 and PowerPC Options. + * mno-serialize-volatile <1>: Interoperation. + * mno-serialize-volatile <2>: Xtensa Options. + * mno-serialize-volatile: M88K Options. + * mno-sext: Xtensa Options. + * mno-short-load-bytes: ARM Options. + * mno-short-load-words: ARM Options. + * mno-side-effects: CRIS Options. + * mno-slow-bytes: MCore Options. + * mno-small-exec: S/390 and zSeries Options. + * mno-soft-float: DEC Alpha Options. + * mno-space-regs: HPPA Options. + * mno-split: PDP-11 Options. + * mno-split-addresses: MIPS Options. + * mno-sse: i386 and x86-64 Options. + * mno-stack-align: CRIS Options. + * mno-stack-bias: SPARC Options. + * mno-stack-check: AMD29K Options. + * mno-stats: MIPS Options. + * mno-storem-bug: AMD29K Options. + * mno-strict-align <1>: Intel 960 Options. + * mno-strict-align <2>: RS/6000 and PowerPC Options. + * mno-strict-align: M680x0 Options. + * mno-string: RS/6000 and PowerPC Options. + * mno-sum-in-toc: RS/6000 and PowerPC Options. + * mno-svr3-shlib: i386 and x86-64 Options. + * mno-symrename: ARM Options. + * mno-tablejump: AVR Options. + * mno-tail-call: Intel 960 Options. + * mno-target-align: Xtensa Options. + * mno-text-section-literals: Xtensa Options. + * mno-toc: RS/6000 and PowerPC Options. + * mno-toplevel-symbols: MMIX Options. + * mno-unaligned-doubles: SPARC Options. + * mno-underscores: M88K Options. + * mno-uninit-const-in-rodata: MIPS Options. + * mno-update: RS/6000 and PowerPC Options. + * mno-volatile-asm-stop: IA-64 Options. + * mno-wide-bitfields: MCore Options. + * mno-xl-call: RS/6000 and PowerPC Options. + * mno-zero-extend: MMIX Options. + * mnoargcount: Convex Options. + * mnobitfield <1>: NS32K Options. + * mnobitfield: M680x0 Options. + * mnohc-struct-return: RT Options. + * mnohimem: NS32K Options. + * mnomacsave: SH Options. + * mnomulti-add: NS32K Options. + * mnop-fun-dllimport: ARM Options. + * mnoregparam: NS32K Options. + * mnormal: AMD29K Options. + * mnosb: NS32K Options. + * mnsa: Xtensa Options. + * mnumerics: Intel 960 Options. + * mocs-debug-info: M88K Options. + * mocs-frame-position: M88K Options. + * mold-align: Intel 960 Options. + * mold-mnemonics: RS/6000 and PowerPC Options. + * momit-leaf-frame-pointer: i386 and x86-64 Options. + * monchip: D30V Options. + * moptimize-arg-area: M88K Options. + * MP: Preprocessor Options. + * mpa-risc-1-0: HPPA Options. + * mpa-risc-1-1: HPPA Options. + * mpa-risc-2-0: HPPA Options. + * mpadstruct: SH Options. + * mparallel-insns: TMS320C3x/C4x Options. + * mparallel-mpy: TMS320C3x/C4x Options. + * mparanoid: TMS320C3x/C4x Options. + * mpcrel: M680x0 Options. + * mpdebug: CRIS Options. + * mpe: RS/6000 and PowerPC Options. + * mpentium: i386 and x86-64 Options. + * mpentiumpro: i386 and x86-64 Options. + * mpic-register: ARM Options. + * mpoke-function-name: ARM Options. + * mportable-runtime: HPPA Options. + * mpower: RS/6000 and PowerPC Options. + * mpower2: RS/6000 and PowerPC Options. + * mpowerpc: RS/6000 and PowerPC Options. + * mpowerpc-gfxopt: RS/6000 and PowerPC Options. + * mpowerpc-gpopt: RS/6000 and PowerPC Options. + * mpowerpc64: RS/6000 and PowerPC Options. + * mprefergot: SH Options. + * mpreferred-stack-boundary: i386 and x86-64 Options. + * mprolog-function: V850 Options. + * mprologue-epilogue: CRIS Options. + * mprototype: RS/6000 and PowerPC Options. + * mpush-args: i386 and x86-64 Options. + * MQ: Preprocessor Options. + * mregister-names: IA-64 Options. + * mregnames: RS/6000 and PowerPC Options. + * mregparam: NS32K Options. + * mregparm <1>: TMS320C3x/C4x Options. + * mregparm: i386 and x86-64 Options. + * mrelax <1>: SH Options. + * mrelax <2>: H8/300 Options. + * mrelax <3>: MN10300 Options. + * mrelax: MN10200 Options. + * mrelax-immediate: MCore Options. + * mrelocatable: RS/6000 and PowerPC Options. + * mrelocatable-lib: RS/6000 and PowerPC Options. + * mreuse-arg-regs: AMD29K Options. + * mrnames: MIPS Options. + * mrodata: ARC Options. + * mrptb: TMS320C3x/C4x Options. + * mrpts: TMS320C3x/C4x Options. + * mrtd <1>: Function Attributes. + * mrtd <2>: NS32K Options. + * mrtd <3>: i386 and x86-64 Options. + * mrtd: M680x0 Options. + * ms: H8/300 Options. + * ms2600: H8/300 Options. + * msa: Intel 960 Options. + * msb <1>: NS32K Options. + * msb: Intel 960 Options. + * mschedule: HPPA Options. + * msda: V850 Options. + * msdata <1>: IA-64 Options. + * msdata: RS/6000 and PowerPC Options. + * msdata-data: RS/6000 and PowerPC Options. + * msdata=default: RS/6000 and PowerPC Options. + * msdata=eabi: RS/6000 and PowerPC Options. + * msdata=none <1>: RS/6000 and PowerPC Options. + * msdata=none: M32R/D Options. + * msdata=sdata: M32R/D Options. + * msdata=sysv: RS/6000 and PowerPC Options. + * msdata=use: M32R/D Options. + * mserialize-volatile <1>: Xtensa Options. + * mserialize-volatile: M88K Options. + * msext: Xtensa Options. + * mshort <1>: M68hc1x Options. + * mshort: M680x0 Options. + * mshort-data: M88K Options. + * mshort-load-bytes: ARM Options. + * mshort-load-words: ARM Options. + * msim <1>: Xstormy16 Options. + * msim: RS/6000 and PowerPC Options. + * msingle-float: MIPS Options. + * msingle-pic-base: ARM Options. + * msize: AVR Options. + * mslow-bytes: MCore Options. + * msmall <1>: TMS320C3x/C4x Options. + * msmall: AMD29K Options. + * msmall-data: DEC Alpha Options. + * msmall-exec: S/390 and zSeries Options. + * msmall-memory: TMS320C3x/C4x Options. + * msoft-float <1>: Xtensa Options. + * msoft-float <2>: PDP-11 Options. + * msoft-float <3>: S/390 and zSeries Options. + * msoft-float <4>: NS32K Options. + * msoft-float <5>: DEC Alpha Options. + * msoft-float <6>: Intel 960 Options. + * msoft-float <7>: HPPA Options. + * msoft-float <8>: i386 and x86-64 Options. + * msoft-float <9>: MIPS Options. + * msoft-float <10>: RS/6000 and PowerPC Options. + * msoft-float <11>: ARM Options. + * msoft-float <12>: AMD29K Options. + * msoft-float <13>: SPARC Options. + * msoft-float: M680x0 Options. + * msoft-quad-float: SPARC Options. + * msoft-reg-count: M68hc1x Options. + * mspace <1>: V850 Options. + * mspace: SH Options. + * msparclite: SPARC Options. + * msplit: PDP-11 Options. + * msplit-addresses: MIPS Options. + * msse: i386 and x86-64 Options. + * mstack-align: CRIS Options. + * mstack-bias: SPARC Options. + * mstack-check: AMD29K Options. + * mstats: MIPS Options. + * mstorem-bug: AMD29K Options. + * mstrict-align <1>: Intel 960 Options. + * mstrict-align <2>: RS/6000 and PowerPC Options. + * mstrict-align: M680x0 Options. + * mstring: RS/6000 and PowerPC Options. + * mstructure-size-boundary: ARM Options. + * msupersparc: SPARC Options. + * msvr3: M88K Options. + * msvr3-shlib: i386 and x86-64 Options. + * msvr4: M88K Options. + * msvr4-struct-return: RS/6000 and PowerPC Options. + * MT: Preprocessor Options. + * mtail-call: Intel 960 Options. + * mtarget-align: Xtensa Options. + * mtda: V850 Options. + * mtext: ARC Options. + * mtext-section-literals: Xtensa Options. + * mthreads: i386 and x86-64 Options. + * mthumb: ARM Options. + * mthumb-interwork: ARM Options. + * mti: TMS320C3x/C4x Options. + * mtiny-stack: AVR Options. + * mtoc: RS/6000 and PowerPC Options. + * mtoplevel-symbols: MMIX Options. + * mtpcs-frame: ARM Options. + * mtpcs-leaf-frame: ARM Options. + * mtrap-large-shift: M88K Options. + * mtrap-precision: DEC Alpha Options. + * mtune <1>: CRIS Options. + * mtune <2>: DEC Alpha Options. + * mtune <3>: MIPS Options. + * mtune <4>: RS/6000 and PowerPC Options. + * mtune <5>: ARM Options. + * mtune: SPARC Options. + * munaligned-doubles: SPARC Options. + * muninit-const-in-rodata: MIPS Options. + * munix: VAX Options. + * munix-asm: PDP-11 Options. + * mupdate: RS/6000 and PowerPC Options. + * muse-div-instruction: M88K Options. + * muser-registers: AMD29K Options. + * musermode: SH Options. + * mv8: SPARC Options. + * mv850: V850 Options. + * mversion-03.00: M88K Options. + * mvms-return-codes: DEC Alpha/VMS Options. + * mvolatile-asm-stop: IA-64 Options. + * mvolatile-cache: Convex Options. + * mvolatile-nocache: Convex Options. + * mvxworks: RS/6000 and PowerPC Options. + * mwarn-passed-structs: M88K Options. + * mwide-bitfields: MCore Options. + * mwords-little-endian: ARM Options. + * mxl-call: RS/6000 and PowerPC Options. + * mxopen: ARM Options. + * myellowknife: RS/6000 and PowerPC Options. + * mzda: V850 Options. + * mzero-extend: MMIX Options. + * no-crt0: MIPS Options. + * no-integrated-cpp: C Dialect Options. + * no-red-zone: i386 and x86-64 Options. + * noasmopt: Interoperation. + * nocpp: MIPS Options. + * nodefaultlibs: Link Options. + * nostartfiles: Link Options. + * nostdinc: Preprocessor Options. + * nostdinc++ <1>: Preprocessor Options. + * nostdinc++: C++ Dialect Options. + * nostdlib: Link Options. + * o: Preprocessor Options. + * O: Optimize Options. + * o: Overall Options. + * O0: Optimize Options. + * O1: Optimize Options. + * O2: Optimize Options. + * O3: Optimize Options. + * Os: Optimize Options. + * P: Preprocessor Options. + * p: Debugging Options. + * param: Optimize Options. + * pass-exit-codes: Overall Options. + * pedantic <1>: Warnings and Errors. + * pedantic <2>: Alternate Keywords. + * pedantic <3>: C Extensions. + * pedantic <4>: Preprocessor Options. + * pedantic <5>: Warning Options. + * pedantic: Standards. + * pedantic-errors <1>: Warnings and Errors. + * pedantic-errors <2>: Non-bugs. + * pedantic-errors <3>: Actual Bugs. + * pedantic-errors <4>: Preprocessor Options. + * pedantic-errors <5>: Warning Options. + * pedantic-errors: Standards. + * pg: Debugging Options. + * pipe: Overall Options. + * print-file-name: Debugging Options. + * print-libgcc-file-name: Debugging Options. + * print-multi-directory: Debugging Options. + * print-multi-lib: Debugging Options. + * print-prog-name: Debugging Options. + * print-search-dirs: Debugging Options. + * pthread: RS/6000 and PowerPC Options. + * Q: Debugging Options. + * Qn: System V Options. + * Qy: System V Options. + * remap: Preprocessor Options. + * s: Link Options. + * S <1>: Link Options. + * S: Overall Options. + * save-temps: Debugging Options. + * shared: Link Options. + * shared-libgcc: Link Options. + * sim: CRIS Options. + * sim2: CRIS Options. + * specs: Directory Options. + * static: Link Options. + * static-libgcc: Link Options. + * std <1>: Non-bugs. + * std <2>: Other Builtins. + * std <3>: C Dialect Options. + * std: Standards. + * std=: Preprocessor Options. + * symbolic: Link Options. + * target-help <1>: Preprocessor Options. + * target-help: Overall Options. + * time: Debugging Options. + * traditional <1>: Non-bugs. + * traditional <2>: Incompatibilities. + * traditional <3>: Preprocessor Options. + * traditional <4>: C Dialect Options. + * traditional: Standards. + * traditional-cpp: C Dialect Options. + * trigraphs <1>: Preprocessor Options. + * trigraphs: C Dialect Options. + * u: Link Options. + * U: Preprocessor Options. + * undef: Preprocessor Options. + * V: Target Options. + * v <1>: Preprocessor Options. + * v: Overall Options. + * version <1>: Preprocessor Options. + * version: Overall Options. + * W: Incompatibilities. + * w: Preprocessor Options. + * W: Warning Options. + * w: Warning Options. + * Wa: Assembler Options. + * Wabi: C++ Dialect Options. + * Waggregate-return: Warning Options. + * Wall <1>: Standard Libraries. + * Wall <2>: Preprocessor Options. + * Wall: Warning Options. + * Wbad-function-cast: Warning Options. + * Wcast-align: Warning Options. + * Wcast-qual: Warning Options. + * Wchar-subscripts: Warning Options. + * Wcomment <1>: Preprocessor Options. + * Wcomment: Warning Options. + * Wcomments: Preprocessor Options. + * Wconversion <1>: Protoize Caveats. + * Wconversion: Warning Options. + * Wctor-dtor-privacy: C++ Dialect Options. + * Wdisabled-optimization: Warning Options. + * Wdiv-by-zero: Warning Options. + * Weffc++: C++ Dialect Options. + * Werror <1>: Preprocessor Options. + * Werror: Warning Options. + * Werror-implicit-function-declaration: Warning Options. + * Wfloat-equal: Warning Options. + * Wformat <1>: Function Attributes. + * Wformat: Warning Options. + * Wformat-nonliteral <1>: Function Attributes. + * Wformat-nonliteral: Warning Options. + * Wformat-security: Warning Options. + * Wformat=2: Warning Options. + * Wimplicit: Warning Options. + * Wimplicit-function-declaration: Warning Options. + * Wimplicit-int: Warning Options. + * Wimport: Preprocessor Options. + * Winline <1>: Inline. + * Winline: Warning Options. + * Wl: Link Options. + * Wlarger-than: Warning Options. + * Wlong-long: Warning Options. + * Wmain: Warning Options. + * Wmissing-braces: Warning Options. + * Wmissing-declarations: Warning Options. + * Wmissing-format-attribute: Warning Options. + * Wmissing-noreturn: Warning Options. + * Wmissing-prototypes: Warning Options. + * Wmultichar: Warning Options. + * Wnested-externs: Warning Options. + * Wno-deprecated: C++ Dialect Options. + * Wno-deprecated-declarations: Warning Options. + * Wno-div-by-zero: Warning Options. + * Wno-format-extra-args: Warning Options. + * Wno-format-y2k: Warning Options. + * Wno-import: Warning Options. + * Wno-long-long: Warning Options. + * Wno-multichar: Warning Options. + * Wno-non-template-friend: C++ Dialect Options. + * Wno-pmf-conversions <1>: Bound member functions. + * Wno-pmf-conversions: C++ Dialect Options. + * Wno-protocol: Objective-C Dialect Options. + * Wnon-virtual-dtor: C++ Dialect Options. + * Wold-style-cast: C++ Dialect Options. + * Woverloaded-virtual: C++ Dialect Options. + * Wp: Preprocessor Options. + * Wpacked: Warning Options. + * Wpadded: Warning Options. + * Wparentheses: Warning Options. + * Wpointer-arith <1>: Pointer Arith. + * Wpointer-arith: Warning Options. + * Wredundant-decls: Warning Options. + * Wreorder <1>: Warning Options. + * Wreorder: C++ Dialect Options. + * Wreturn-type: Warning Options. + * Wselector: Objective-C Dialect Options. + * Wsequence-point: Warning Options. + * Wshadow: Warning Options. + * Wsign-compare: Warning Options. + * Wsign-promo: C++ Dialect Options. + * Wstrict-prototypes: Warning Options. + * Wswitch: Warning Options. + * Wsynth: C++ Dialect Options. + * Wsystem-headers <1>: Preprocessor Options. + * Wsystem-headers: Warning Options. + * Wtraditional <1>: Preprocessor Options. + * Wtraditional: Warning Options. + * Wtrigraphs <1>: Preprocessor Options. + * Wtrigraphs: Warning Options. + * Wundef <1>: Preprocessor Options. + * Wundef: Warning Options. + * Wuninitialized: Warning Options. + * Wunknown-pragmas: Warning Options. + * Wunreachable-code: Warning Options. + * Wunused: Warning Options. + * Wunused-function: Warning Options. + * Wunused-label: Warning Options. + * Wunused-parameter: Warning Options. + * Wunused-value: Warning Options. + * Wunused-variable: Warning Options. + * Wwrite-strings: Warning Options. + * x <1>: Preprocessor Options. + * x: Overall Options. + * Xlinker: Link Options. + * Ym: System V Options. + * YP: System V Options. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-23 gcc-3.2.3/gcc/doc/gcc.info-23 *** gcc-3.2.2/gcc/doc/gcc.info-23 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-23 Tue Apr 22 07:07:15 2003 *************** *** 0 **** --- 1,749 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Index, Prev: Option Index, Up: Top + + Index + ***** + + * Menu: + + * ! in constraint: Multi-Alternative. + * # in constraint: Modifiers. + * #pragma: Pragmas. + * #pragma implementation: C++ Interface. + * #pragma implementation, implied: C++ Interface. + * #pragma interface: C++ Interface. + * #pragma, reason for not using: Function Attributes. + * $: Dollar Signs. + * % in constraint: Modifiers. + * %include: Spec Files. + * %include_noerr: Spec Files. + * %rename: Spec Files. + * & in constraint: Modifiers. + * ': Incompatibilities. + * * in constraint: Modifiers. + * + in constraint: Modifiers. + * -lgcc, use with -nodefaultlibs: Link Options. + * -lgcc, use with -nostdlib: Link Options. + * -nodefaultlibs and unresolved references: Link Options. + * -nostdlib and unresolved references: Link Options. + * .sdata/.sdata2 references (PowerPC): RS/6000 and PowerPC Options. + * //: C++ Comments. + * 0 in constraint: Simple Constraints. + * < in constraint: Simple Constraints. + * in constraint: Simple Constraints. + * >?: Min and Max. + * ? in constraint: Multi-Alternative. + * ?: extensions <1>: Conditionals. + * ?: extensions: Lvalues. + * ?: side effect: Conditionals. + * \a: C Dialect Options. + * \x: C Dialect Options. + * _ in variables in macros: Typeof. + * __builtin_apply: Constructing Calls. + * __builtin_apply_args: Constructing Calls. + * __builtin_choose_expr: Other Builtins. + * __builtin_constant_p: Other Builtins. + * __builtin_expect: Other Builtins. + * __builtin_frame_address: Return Address. + * __builtin_isgreater: Other Builtins. + * __builtin_isgreaterequal: Other Builtins. + * __builtin_isless: Other Builtins. + * __builtin_islessequal: Other Builtins. + * __builtin_islessgreater: Other Builtins. + * __builtin_isunordered: Other Builtins. + * __builtin_prefetch: Other Builtins. + * __builtin_return: Constructing Calls. + * __builtin_return_address: Return Address. + * __builtin_types_compatible_p: Other Builtins. + * __complex__ keyword: Complex. + * __extension__: Alternate Keywords. + * __func__ identifier: Function Names. + * __FUNCTION__ identifier: Function Names. + * __imag__ keyword: Complex. + * __PRETTY_FUNCTION__ identifier: Function Names. + * __real__ keyword: Complex. + * __STDC_HOSTED__: Standards. + * _Complex keyword: Complex. + * _Exit: Other Builtins. + * _exit: Other Builtins. + * ABI: Compatibility. + * abort: Other Builtins. + * abs: Other Builtins. + * accessing volatiles: Volatiles. + * Ada: G++ and GCC. + * address constraints: Simple Constraints. + * address of a label: Labels as Values. + * address_operand: Simple Constraints. + * alias attribute: Function Attributes. + * aliasing of parameters: Code Gen Options. + * aligned attribute <1>: Type Attributes. + * aligned attribute: Variable Attributes. + * alignment: Alignment. + * Alliant: Interoperation. + * alloca: Other Builtins. + * alloca vs variable-length arrays: Variable Length. + * alternate keywords: Alternate Keywords. + * always_inline function attribute: Function Attributes. + * AMD x86-64 Options: i386 and x86-64 Options. + * AMD1: Standards. + * AMD29K options: AMD29K Options. + * ANSI C: Standards. + * ANSI C standard: Standards. + * ANSI C89: Standards. + * ANSI support: C Dialect Options. + * ANSI X3.159-1989: Standards. + * apostrophes: Incompatibilities. + * application binary interface: Compatibility. + * ARC Options: ARC Options. + * arguments in frame (88k): M88K Options. + * ARM [Annotated C++ Reference Manual]: Backwards Compatibility. + * ARM options: ARM Options. + * arrays of length zero: Zero Length. + * arrays of variable length: Variable Length. + * arrays, non-lvalue: Subscripting. + * asm constraints: Constraints. + * asm expressions: Extended Asm. + * assembler instructions: Extended Asm. + * assembler names for identifiers: Asm Labels. + * assembler syntax, 88k: M88K Options. + * assembly code, invalid: Bug Criteria. + * attribute of types: Type Attributes. + * attribute of variables: Variable Attributes. + * attribute syntax: Attribute Syntax. + * autoincrement/decrement addressing: Simple Constraints. + * automatic inline for C++ member fns: Inline. + * AVR Options: AVR Options. + * backtrace for bug reports: Bug Reporting. + * Backwards Compatibility: Backwards Compatibility. + * bcmp: Other Builtins. + * binary compatibility: Compatibility. + * bit shift overflow (88k): M88K Options. + * bound pointer to member function: Bound member functions. + * bug criteria: Bug Criteria. + * bug report mailing lists: Bug Lists. + * bugs: Bugs. + * bugs, known: Trouble. + * built-in functions <1>: Other Builtins. + * built-in functions: C Dialect Options. + * byte writes (29k): AMD29K Options. + * bzero: Other Builtins. + * C compilation options: Invoking GCC. + * C intermediate output, nonexistent: G++ and GCC. + * C language extensions: C Extensions. + * C language, traditional: C Dialect Options. + * C standard: Standards. + * C standards: Standards. + * c++: Invoking G++. + * C++: G++ and GCC. + * C++ comments: C++ Comments. + * C++ compilation options: Invoking GCC. + * C++ interface and implementation headers: C++ Interface. + * C++ language extensions: C++ Extensions. + * C++ member fns, automatically inline: Inline. + * C++ misunderstandings: C++ Misunderstandings. + * C++ options, command line: C++ Dialect Options. + * C++ pragmas, effect on inlining: C++ Interface. + * C++ source file suffixes: Invoking G++. + * C++ static data, declaring and defining: Static Definitions. + * C89: Standards. + * C90: Standards. + * C94: Standards. + * C95: Standards. + * C99: Standards. + * C9X: Standards. + * C_INCLUDE_PATH: Environment Variables. + * calling functions through the function vector on the H8/300 processors: Function Attributes. + * case labels in initializers: Designated Inits. + * case ranges: Case Ranges. + * case sensitivity and VMS: VMS Misc. + * cast to a union: Cast to Union. + * casts as lvalues: Lvalues. + * cimag: Other Builtins. + * cimagf: Other Builtins. + * cimagl: Other Builtins. + * code generation conventions: Code Gen Options. + * code, mixed with declarations: Mixed Declarations. + * command options: Invoking GCC. + * comments, C++ style: C++ Comments. + * comparison of signed and unsigned values, warning: Warning Options. + * compiler bugs, reporting: Bug Reporting. + * compiler compared to C++ preprocessor: G++ and GCC. + * compiler options, C++: C++ Dialect Options. + * compiler options, Objective-C: Objective-C Dialect Options. + * compiler version, specifying: Target Options. + * COMPILER_PATH: Environment Variables. + * complex conjugation: Complex. + * complex numbers: Complex. + * compound expressions as lvalues: Lvalues. + * compound literals: Compound Literals. + * computed gotos: Labels as Values. + * conditional expressions as lvalues: Lvalues. + * conditional expressions, extensions: Conditionals. + * conflicting types: Disappointments. + * conj: Other Builtins. + * conjf: Other Builtins. + * conjl: Other Builtins. + * const applied to function: Function Attributes. + * const function attribute: Function Attributes. + * constants in constraints: Simple Constraints. + * constraint modifier characters: Modifiers. + * constraint, matching: Simple Constraints. + * constraints, asm: Constraints. + * constraints, machine specific: Machine Constraints. + * constructing calls: Constructing Calls. + * constructor expressions: Compound Literals. + * constructor function attribute: Function Attributes. + * contributors: Contributors. + * Convex options: Convex Options. + * core dump: Bug Criteria. + * cos: Other Builtins. + * cosf: Other Builtins. + * cosl: Other Builtins. + * CPATH: Environment Variables. + * CPLUS_INCLUDE_PATH: Environment Variables. + * creal: Other Builtins. + * crealf: Other Builtins. + * creall: Other Builtins. + * CRIS Options: CRIS Options. + * cross compiling: Target Options. + * D30V Options: D30V Options. + * DBX: Interoperation. + * deallocating variable length arrays: Variable Length. + * debug_rtx: Bug Reporting. + * debugging information options: Debugging Options. + * debugging, 88k OCS: M88K Options. + * declaration scope: Incompatibilities. + * declarations inside expressions: Statement Exprs. + * declarations, mixed with code: Mixed Declarations. + * declaring attributes of functions: Function Attributes. + * declaring static data in C++: Static Definitions. + * defining static data in C++: Static Definitions. + * dependencies for make as output: Environment Variables. + * dependencies, make: Preprocessor Options. + * DEPENDENCIES_OUTPUT: Environment Variables. + * deprecated attribute.: Function Attributes. + * designated initializers: Designated Inits. + * designator lists: Designated Inits. + * designators: Designated Inits. + * destructor function attribute: Function Attributes. + * diagnostic messages: Language Independent Options. + * dialect options: C Dialect Options. + * digits in constraint: Simple Constraints. + * directory options: Directory Options. + * divide instruction, 88k: M88K Options. + * dollar signs in identifier names: Dollar Signs. + * double-word arithmetic: Long Long. + * downward funargs: Nested Functions. + * DW bit (29k): AMD29K Options. + * E in constraint: Simple Constraints. + * earlyclobber operand: Modifiers. + * eight bit data on the H8/300 and H8/300H: Function Attributes. + * environment variables: Environment Variables. + * error messages: Warnings and Errors. + * escape sequences, traditional: C Dialect Options. + * escaped newlines: Escaped Newlines. + * exclamation point: Multi-Alternative. + * exit: Other Builtins. + * exit status and VMS: VMS Misc. + * explicit register variables: Explicit Reg Vars. + * expressions containing statements: Statement Exprs. + * expressions, compound, as lvalues: Lvalues. + * expressions, conditional, as lvalues: Lvalues. + * expressions, constructor: Compound Literals. + * extended asm: Extended Asm. + * extensible constraints: Simple Constraints. + * extensions, ?: <1>: Conditionals. + * extensions, ?:: Lvalues. + * extensions, C language: C Extensions. + * extensions, C++ language: C++ Extensions. + * external declaration scope: Incompatibilities. + * F in constraint: Simple Constraints. + * fabs: Other Builtins. + * fabsf: Other Builtins. + * fabsl: Other Builtins. + * fatal signal: Bug Criteria. + * FDL, GNU Free Documentation License: GNU Free Documentation License. + * ffs: Other Builtins. + * file name suffix: Overall Options. + * file names: Link Options. + * flexible array members: Zero Length. + * float as function value type: Incompatibilities. + * floating point precision <1>: Disappointments. + * floating point precision: Optimize Options. + * format function attribute: Function Attributes. + * format_arg function attribute: Function Attributes. + * Fortran: G++ and GCC. + * forwarding calls: Constructing Calls. + * fprintf: Other Builtins. + * fprintf_unlocked: Other Builtins. + * fputs: Other Builtins. + * fputs_unlocked: Other Builtins. + * freestanding environment: Standards. + * freestanding implementation: Standards. + * fscanf, and constant strings: Incompatibilities. + * function addressability on the M32R/D: Function Attributes. + * function attributes: Function Attributes. + * function pointers, arithmetic: Pointer Arith. + * function prototype declarations: Function Prototypes. + * function without a prologue/epilogue code: Function Attributes. + * function, size of pointer to: Pointer Arith. + * functions called via pointer on the RS/6000 and PowerPC: Function Attributes. + * functions in arbitrary sections: Function Attributes. + * functions that are passed arguments in registers on the 386: Function Attributes. + * functions that behave like malloc: Function Attributes. + * functions that do not pop the argument stack on the 386: Function Attributes. + * functions that do pop the argument stack on the 386: Function Attributes. + * functions that have no side effects: Function Attributes. + * functions that never return: Function Attributes. + * functions that pop the argument stack on the 386: Function Attributes. + * functions which are exported from a dll on PowerPC Windows NT: Function Attributes. + * functions which are imported from a dll on PowerPC Windows NT: Function Attributes. + * functions which specify exception handling on PowerPC Windows NT: Function Attributes. + * functions with printf, scanf, strftime or strfmon style arguments: Function Attributes. + * g in constraint: Simple Constraints. + * G in constraint: Simple Constraints. + * g++: Invoking G++. + * G++: G++ and GCC. + * GCC: G++ and GCC. + * GCC command options: Invoking GCC. + * gcc-bugs@gcc.gnu.org or bug-gcc@gnu.org: Bug Lists. + * GCC_EXEC_PREFIX: Environment Variables. + * gccbug script: gccbug. + * generalized lvalues: Lvalues. + * global offset table: Code Gen Options. + * global register after longjmp: Global Reg Vars. + * global register variables: Global Reg Vars. + * GLOBALDEF: Global Declarations. + * GLOBALREF: Global Declarations. + * GLOBALVALUEDEF: Global Declarations. + * GLOBALVALUEREF: Global Declarations. + * GNAT: G++ and GCC. + * goto with computed label: Labels as Values. + * gp-relative references (MIPS): MIPS Options. + * gprof: Debugging Options. + * grouping options: Invoking GCC. + * H in constraint: Simple Constraints. + * hardware models and configurations, specifying: Submodel Options. + * header files and VMS: Include Files and VMS. + * hex floats: Hex Floats. + * hosted environment <1>: C Dialect Options. + * hosted environment: Standards. + * hosted implementation: Standards. + * HPPA Options: HPPA Options. + * I in constraint: Simple Constraints. + * i in constraint: Simple Constraints. + * i386 Options: i386 and x86-64 Options. + * IA-64 Options: IA-64 Options. + * IBM RS/6000 and PowerPC Options: RS/6000 and PowerPC Options. + * IBM RT options: RT Options. + * IBM RT PC: Interoperation. + * identifier names, dollar signs in: Dollar Signs. + * identifiers, names in assembler code: Asm Labels. + * identifying source, compiler (88k): M88K Options. + * imaxabs: Other Builtins. + * implementation-defined behavior, C language: C Implementation. + * implied #pragma implementation: C++ Interface. + * include files and VMS: Include Files and VMS. + * incompatibilities of GCC: Incompatibilities. + * increment operators: Bug Criteria. + * index: Other Builtins. + * indirect calls on ARM: Function Attributes. + * init_priority attribute: C++ Attributes. + * initializations in expressions: Compound Literals. + * initializers with labeled elements: Designated Inits. + * initializers, non-constant: Initializers. + * inline automatic for C++ member fns: Inline. + * inline functions: Inline. + * inline functions, omission of: Inline. + * inlining and C++ pragmas: C++ Interface. + * installation trouble: Trouble. + * integrating function code: Inline. + * Intel 386 Options: i386 and x86-64 Options. + * interface and implementation headers, C++: C++ Interface. + * intermediate C version, nonexistent: G++ and GCC. + * interrupt handler functions: Function Attributes. + * interrupt handler functions on the H8/300 and SH processors: Function Attributes. + * introduction: Top. + * invalid assembly code: Bug Criteria. + * invalid input: Bug Criteria. + * invoking g++: Invoking G++. + * ISO 9899: Standards. + * ISO C: Standards. + * ISO C standard: Standards. + * ISO C89: Standards. + * ISO C90: Standards. + * ISO C94: Standards. + * ISO C95: Standards. + * ISO C99: Standards. + * ISO C9X: Standards. + * ISO support: C Dialect Options. + * ISO/IEC 9899: Standards. + * Java: G++ and GCC. + * java_interface attribute: C++ Attributes. + * kernel and user registers (29k): AMD29K Options. + * keywords, alternate: Alternate Keywords. + * known causes of trouble: Trouble. + * labeled elements in initializers: Designated Inits. + * labels as values: Labels as Values. + * labs: Other Builtins. + * LANG: Environment Variables. + * language dialect options: C Dialect Options. + * large bit shifts (88k): M88K Options. + * LC_ALL: Environment Variables. + * LC_CTYPE: Environment Variables. + * LC_MESSAGES: Environment Variables. + * length-zero arrays: Zero Length. + * Libraries: Link Options. + * LIBRARY_PATH: Environment Variables. + * link options: Link Options. + * LL integer suffix: Long Long. + * llabs: Other Builtins. + * load address instruction: Simple Constraints. + * local labels: Local Labels. + * local variables in macros: Typeof. + * local variables, specifying registers: Local Reg Vars. + * locale: Environment Variables. + * locale definition: Environment Variables. + * long long data types: Long Long. + * longjmp: Global Reg Vars. + * longjmp and automatic variables: C Dialect Options. + * longjmp incompatibilities: Incompatibilities. + * longjmp warnings: Warning Options. + * lvalues, generalized: Lvalues. + * m in constraint: Simple Constraints. + * M32R/D options: M32R/D Options. + * M680x0 options: M680x0 Options. + * M68hc1x options: M68hc1x Options. + * M88k options: M88K Options. + * machine dependent options: Submodel Options. + * machine specific constraints: Machine Constraints. + * macro with variable arguments: Variadic Macros. + * macros containing asm: Extended Asm. + * macros, inline alternative: Inline. + * macros, local labels: Local Labels. + * macros, local variables in: Typeof. + * macros, statements in expressions: Statement Exprs. + * macros, types of arguments: Typeof. + * main and the exit status: VMS Misc. + * make: Preprocessor Options. + * malloc attribute: Function Attributes. + * matching constraint: Simple Constraints. + * maximum operator: Min and Max. + * MCore options: MCore Options. + * member fns, automatically inline: Inline. + * memcmp: Other Builtins. + * memcpy: Other Builtins. + * memory model (29k): AMD29K Options. + * memory references in constraints: Simple Constraints. + * memset: Other Builtins. + * message formatting: Language Independent Options. + * messages, warning: Warning Options. + * messages, warning and error: Warnings and Errors. + * middle-operands, omitted: Conditionals. + * minimum operator: Min and Max. + * MIPS options: MIPS Options. + * misunderstandings in C++: C++ Misunderstandings. + * mixed declarations and code: Mixed Declarations. + * mktemp, and constant strings: Incompatibilities. + * MMIX Options: MMIX Options. + * MN10200 options: MN10200 Options. + * MN10300 options: MN10300 Options. + * mode attribute: Variable Attributes. + * modifiers in constraints: Modifiers. + * multi-line string literals: Multi-line Strings. + * multiple alternative constraints: Multi-Alternative. + * multiprecision arithmetic: Long Long. + * n in constraint: Simple Constraints. + * name augmentation: VMS Misc. + * names used in assembler code: Asm Labels. + * naming convention, implementation headers: C++ Interface. + * nested functions: Nested Functions. + * newlines (escaped): Escaped Newlines. + * no_instrument_function function attribute: Function Attributes. + * nocommon attribute: Variable Attributes. + * noinline function attribute: Function Attributes. + * non-constant initializers: Initializers. + * non-static inline function: Inline. + * noreturn function attribute: Function Attributes. + * NS32K options: NS32K Options. + * o in constraint: Simple Constraints. + * OBJC_INCLUDE_PATH: Environment Variables. + * Objective-C: G++ and GCC. + * Objective-C options, command line: Objective-C Dialect Options. + * OCS (88k): M88K Options. + * offsettable address: Simple Constraints. + * old-style function definitions: Function Prototypes. + * omitted middle-operands: Conditionals. + * open coding: Inline. + * operand constraints, asm: Constraints. + * optimize options: Optimize Options. + * options to control diagnostics formatting: Language Independent Options. + * options to control warnings: Warning Options. + * options, C++: C++ Dialect Options. + * options, code generation: Code Gen Options. + * options, debugging: Debugging Options. + * options, dialect: C Dialect Options. + * options, directory search: Directory Options. + * options, GCC command: Invoking GCC. + * options, grouping: Invoking GCC. + * options, linking: Link Options. + * options, Objective-C: Objective-C Dialect Options. + * options, optimization: Optimize Options. + * options, order: Invoking GCC. + * options, preprocessor: Preprocessor Options. + * order of evaluation, side effects: Non-bugs. + * order of options: Invoking GCC. + * other register constraints: Simple Constraints. + * output file option: Overall Options. + * overloaded virtual fn, warning: C++ Dialect Options. + * p in constraint: Simple Constraints. + * packed attribute: Variable Attributes. + * parameter forward declaration: Variable Length. + * parameters, aliased: Code Gen Options. + * PDP-11 Options: PDP-11 Options. + * PIC: Code Gen Options. + * pmf: Bound member functions. + * pointer arguments: Function Attributes. + * pointer to member function: Bound member functions. + * portions of temporary objects, pointers to: Temporaries. + * pragma, extern_prefix: Tru64 Pragmas. + * pragma, long_calls: ARM Pragmas. + * pragma, long_calls_off: ARM Pragmas. + * pragma, mark: Darwin Pragmas. + * pragma, no_long_calls: ARM Pragmas. + * pragma, options align: Darwin Pragmas. + * pragma, reason for not using: Function Attributes. + * pragma, redefine_extname: Solaris Pragmas. + * pragma, segment: Darwin Pragmas. + * pragma, unused: Darwin Pragmas. + * pragmas: Pragmas. + * pragmas in C++, effect on inlining: C++ Interface. + * pragmas, interface and implementation: C++ Interface. + * pragmas, warning of unknown: Warning Options. + * preprocessing numbers: Incompatibilities. + * preprocessing tokens: Incompatibilities. + * preprocessor options: Preprocessor Options. + * printf: Other Builtins. + * printf_unlocked: Other Builtins. + * processor selection (29k): AMD29K Options. + * prof: Debugging Options. + * promotion of formal parameters: Function Prototypes. + * pure function attribute: Function Attributes. + * push address instruction: Simple Constraints. + * qsort, and global register variables: Global Reg Vars. + * question mark: Multi-Alternative. + * r in constraint: Simple Constraints. + * r0-relative references (88k): M88K Options. + * ranges in case statements: Case Ranges. + * read-only strings: Incompatibilities. + * register positions in frame (88k): M88K Options. + * register variable after longjmp: Global Reg Vars. + * registers: Extended Asm. + * registers for local variables: Local Reg Vars. + * registers in constraints: Simple Constraints. + * registers, global allocation: Explicit Reg Vars. + * registers, global variables in: Global Reg Vars. + * reordering, warning <1>: Warning Options. + * reordering, warning: C++ Dialect Options. + * reporting bugs: Bugs. + * rest argument (in macro): Variadic Macros. + * restricted pointers: Restricted Pointers. + * restricted references: Restricted Pointers. + * restricted this pointer: Restricted Pointers. + * return value of main: VMS Misc. + * rindex: Other Builtins. + * RS/6000 and PowerPC Options: RS/6000 and PowerPC Options. + * RT options: RT Options. + * RT PC: Interoperation. + * RTTI: Vague Linkage. + * run-time options: Code Gen Options. + * s in constraint: Simple Constraints. + * S/390 and zSeries Options: S/390 and zSeries Options. + * scanf, and constant strings: Incompatibilities. + * scope of a variable length array: Variable Length. + * scope of declaration: Disappointments. + * scope of external declarations: Incompatibilities. + * search path: Directory Options. + * section function attribute: Function Attributes. + * section variable attribute: Variable Attributes. + * sequential consistency on 88k: M88K Options. + * setjmp: Global Reg Vars. + * setjmp incompatibilities: Incompatibilities. + * shared strings: Incompatibilities. + * shared variable attribute: Variable Attributes. + * shared VMS run time system: VMS Misc. + * side effect in ?:: Conditionals. + * side effects, macro argument: Statement Exprs. + * side effects, order of evaluation: Non-bugs. + * signal handler functions on the AVR processors: Function Attributes. + * signed and unsigned values, comparison warning: Warning Options. + * simple constraints: Simple Constraints. + * sin: Other Builtins. + * sinf: Other Builtins. + * sinl: Other Builtins. + * sizeof: Typeof. + * smaller data references: M32R/D Options. + * smaller data references (88k): M88K Options. + * smaller data references (MIPS): MIPS Options. + * smaller data references (PowerPC): RS/6000 and PowerPC Options. + * SPARC options: SPARC Options. + * Spec Files: Spec Files. + * specified registers: Explicit Reg Vars. + * specifying compiler version and target machine: Target Options. + * specifying hardware config: Submodel Options. + * specifying machine version: Target Options. + * specifying registers for local variables: Local Reg Vars. + * sqrt: Other Builtins. + * sqrtf: Other Builtins. + * sqrtl: Other Builtins. + * sscanf, and constant strings: Incompatibilities. + * stack checks (29k): AMD29K Options. + * statements inside expressions: Statement Exprs. + * static data in C++, declaring and defining: Static Definitions. + * stdarg.h and RT PC: RT Options. + * storem bug (29k): AMD29K Options. + * strcat: Other Builtins. + * strchr: Other Builtins. + * strcmp: Other Builtins. + * strcpy: Other Builtins. + * strcspn: Other Builtins. + * string constants: Incompatibilities. + * strlen: Other Builtins. + * strncat: Other Builtins. + * strncmp: Other Builtins. + * strncpy: Other Builtins. + * strpbrk: Other Builtins. + * strrchr: Other Builtins. + * strspn: Other Builtins. + * strstr: Other Builtins. + * struct: Unnamed Fields. + * structure passing (88k): M88K Options. + * structures: Incompatibilities. + * structures, constructor expression: Compound Literals. + * submodel options: Submodel Options. + * subscripting: Subscripting. + * subscripting and function values: Subscripting. + * suffixes for C++ source: Invoking G++. + * SUNPRO_DEPENDENCIES: Environment Variables. + * suppressing warnings: Warning Options. + * surprises in C++: C++ Misunderstandings. + * SVr4: M88K Options. + * syntax checking: Warning Options. + * synthesized methods, warning: C++ Dialect Options. + * system headers, warnings from: Warning Options. + * target machine, specifying: Target Options. + * target options: Target Options. + * TC1: Standards. + * TC2: Standards. + * Technical Corrigenda: Standards. + * Technical Corrigendum 1: Standards. + * Technical Corrigendum 2: Standards. + * template instantiation: Template Instantiation. + * temporaries, lifetime of: Temporaries. + * thunks: Nested Functions. + * tiny data section on the H8/300H: Function Attributes. + * TMPDIR: Environment Variables. + * TMS320C3x/C4x Options: TMS320C3x/C4x Options. + * traditional C language: C Dialect Options. + * type alignment: Alignment. + * type attributes: Type Attributes. + * type_info: Vague Linkage. + * typedef names as function parameters: Incompatibilities. + * typeof: Typeof. + * ULL integer suffix: Long Long. + * Ultrix calling convention: Interoperation. + * undefined behavior: Bug Criteria. + * undefined function value: Bug Criteria. + * underscores in variables in macros: Typeof. + * underscores, avoiding (88k): M88K Options. + * union: Unnamed Fields. + * union, casting to a: Cast to Union. + * unions: Incompatibilities. + * unknown pragmas, warning: Warning Options. + * unresolved references and -nodefaultlibs: Link Options. + * unresolved references and -nostdlib: Link Options. + * unused attribute.: Function Attributes. + * used attribute.: Function Attributes. + * V in constraint: Simple Constraints. + * V850 Options: V850 Options. + * vague linkage: Vague Linkage. + * value after longjmp: Global Reg Vars. + * varargs.h and RT PC: RT Options. + * variable addressability on the M32R/D: Variable Attributes. + * variable alignment: Alignment. + * variable attributes: Variable Attributes. + * variable number of arguments: Variadic Macros. + * variable-length array scope: Variable Length. + * variable-length arrays: Variable Length. + * variables in specified registers: Explicit Reg Vars. + * variables, local, in macros: Typeof. + * variadic macros: Variadic Macros. + * VAX calling convention: Interoperation. + * VAX options: VAX Options. + * VAXCRTL: VMS Misc. + * VLAs: Variable Length. + * VMS and case sensitivity: VMS Misc. + * VMS and include files: Include Files and VMS. + * void pointers, arithmetic: Pointer Arith. + * void, size of pointer to: Pointer Arith. + * volatile access: Volatiles. + * volatile applied to function: Function Attributes. + * volatile read: Volatiles. + * volatile write: Volatiles. + * vtable: Vague Linkage. + * warning for comparison of signed and unsigned values: Warning Options. + * warning for overloaded virtual fn: C++ Dialect Options. + * warning for reordering of member initializers <1>: Warning Options. + * warning for reordering of member initializers: C++ Dialect Options. + * warning for synthesized methods: C++ Dialect Options. + * warning for unknown pragmas: Warning Options. + * warning messages: Warning Options. + * warnings from system headers: Warning Options. + * warnings vs errors: Warnings and Errors. + * weak attribute: Function Attributes. + * whitespace: Incompatibilities. + * X in constraint: Simple Constraints. + * X3.159-1989: Standards. + * x86-64 Options: i386 and x86-64 Options. + * Xstormy16 Options: Xstormy16 Options. + * Xtensa Options: Xtensa Options. + * zero division on 88k: M88K Options. + * zero-length arrays: Zero Length. + + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-3 gcc-3.2.3/gcc/doc/gcc.info-3 *** gcc-3.2.2/gcc/doc/gcc.info-3 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-3 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,796 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Warning Options, Next: Debugging Options, Prev: Language Independent Options, Up: Invoking GCC + + Options to Request or Suppress Warnings + ======================================= + + Warnings are diagnostic messages that report constructions which are + not inherently erroneous but which are risky or suggest there may have + been an error. + + You can request many specific warnings with options beginning `-W', + for example `-Wimplicit' to request warnings on implicit declarations. + Each of these specific warning options also has a negative form + beginning `-Wno-' to turn off warnings; for example, `-Wno-implicit'. + This manual lists only one of the two forms, whichever is not the + default. + + The following options control the amount and kinds of warnings + produced by GCC; for further, language-specific options also refer to + *Note C++ Dialect Options:: and *Note Objective-C Dialect Options::. + + `-fsyntax-only' + Check the code for syntax errors, but don't do anything beyond + that. + + `-pedantic' + Issue all the warnings demanded by strict ISO C and ISO C++; + reject all programs that use forbidden extensions, and some other + programs that do not follow ISO C and ISO C++. For ISO C, follows + the version of the ISO C standard specified by any `-std' option + used. + + Valid ISO C and ISO C++ programs should compile properly with or + without this option (though a rare few will require `-ansi' or a + `-std' option specifying the required version of ISO C). However, + without this option, certain GNU extensions and traditional C and + C++ features are supported as well. With this option, they are + rejected. + + `-pedantic' does not cause warning messages for use of the + alternate keywords whose names begin and end with `__'. Pedantic + warnings are also disabled in the expression that follows + `__extension__'. However, only system header files should use + these escape routes; application programs should avoid them. + *Note Alternate Keywords::. + + Some users try to use `-pedantic' to check programs for strict ISO + C conformance. They soon find that it does not do quite what they + want: it finds some non-ISO practices, but not all--only those for + which ISO C _requires_ a diagnostic, and some others for which + diagnostics have been added. + + A feature to report any failure to conform to ISO C might be + useful in some instances, but would require considerable + additional work and would be quite different from `-pedantic'. We + don't have plans to support such a feature in the near future. + + Where the standard specified with `-std' represents a GNU extended + dialect of C, such as `gnu89' or `gnu99', there is a corresponding + "base standard", the version of ISO C on which the GNU extended + dialect is based. Warnings from `-pedantic' are given where they + are required by the base standard. (It would not make sense for + such warnings to be given only for features not in the specified + GNU C dialect, since by definition the GNU dialects of C include + all features the compiler supports with the given option, and + there would be nothing to warn about.) + + `-pedantic-errors' + Like `-pedantic', except that errors are produced rather than + warnings. + + `-w' + Inhibit all warning messages. + + `-Wno-import' + Inhibit warning messages about the use of `#import'. + + `-Wchar-subscripts' + Warn if an array subscript has type `char'. This is a common cause + of error, as programmers often forget that this type is signed on + some machines. + + `-Wcomment' + Warn whenever a comment-start sequence `/*' appears in a `/*' + comment, or whenever a Backslash-Newline appears in a `//' comment. + + `-Wformat' + Check calls to `printf' and `scanf', etc., to make sure that the + arguments supplied have types appropriate to the format string + specified, and that the conversions specified in the format string + make sense. This includes standard functions, and others + specified by format attributes (*note Function Attributes::), in + the `printf', `scanf', `strftime' and `strfmon' (an X/Open + extension, not in the C standard) families. + + The formats are checked against the format features supported by + GNU libc version 2.2. These include all ISO C89 and C99 features, + as well as features from the Single Unix Specification and some + BSD and GNU extensions. Other library implementations may not + support all these features; GCC does not support warning about + features that go beyond a particular library's limitations. + However, if `-pedantic' is used with `-Wformat', warnings will be + given about format features not in the selected standard version + (but not for `strfmon' formats, since those are not in any version + of the C standard). *Note Options Controlling C Dialect: C + Dialect Options. + + `-Wformat' is included in `-Wall'. For more control over some + aspects of format checking, the options `-Wno-format-y2k', + `-Wno-format-extra-args', `-Wformat-nonliteral', + `-Wformat-security' and `-Wformat=2' are available, but are not + included in `-Wall'. + + `-Wno-format-y2k' + If `-Wformat' is specified, do not warn about `strftime' formats + which may yield only a two-digit year. + + `-Wno-format-extra-args' + If `-Wformat' is specified, do not warn about excess arguments to a + `printf' or `scanf' format function. The C standard specifies + that such arguments are ignored. + + Where the unused arguments lie between used arguments that are + specified with `$' operand number specifications, normally + warnings are still given, since the implementation could not know + what type to pass to `va_arg' to skip the unused arguments. + However, in the case of `scanf' formats, this option will suppress + the warning if the unused arguments are all pointers, since the + Single Unix Specification says that such unused arguments are + allowed. + + `-Wformat-nonliteral' + If `-Wformat' is specified, also warn if the format string is not a + string literal and so cannot be checked, unless the format function + takes its format arguments as a `va_list'. + + `-Wformat-security' + If `-Wformat' is specified, also warn about uses of format + functions that represent possible security problems. At present, + this warns about calls to `printf' and `scanf' functions where the + format string is not a string literal and there are no format + arguments, as in `printf (foo);'. This may be a security hole if + the format string came from untrusted input and contains `%n'. + (This is currently a subset of what `-Wformat-nonliteral' warns + about, but in future warnings may be added to `-Wformat-security' + that are not included in `-Wformat-nonliteral'.) + + `-Wformat=2' + Enable `-Wformat' plus format checks not included in `-Wformat'. + Currently equivalent to `-Wformat -Wformat-nonliteral + -Wformat-security'. + + `-Wimplicit-int' + Warn when a declaration does not specify a type. + + `-Wimplicit-function-declaration' + `-Werror-implicit-function-declaration' + Give a warning (or error) whenever a function is used before being + declared. + + `-Wimplicit' + Same as `-Wimplicit-int' and `-Wimplicit-function-declaration'. + + `-Wmain' + Warn if the type of `main' is suspicious. `main' should be a + function with external linkage, returning int, taking either zero + arguments, two, or three arguments of appropriate types. + + `-Wmissing-braces' + Warn if an aggregate or union initializer is not fully bracketed. + In the following example, the initializer for `a' is not fully + bracketed, but that for `b' is fully bracketed. + + int a[2][2] = { 0, 1, 2, 3 }; + int b[2][2] = { { 0, 1 }, { 2, 3 } }; + + `-Wparentheses' + Warn if parentheses are omitted in certain contexts, such as when + there is an assignment in a context where a truth value is + expected, or when operators are nested whose precedence people + often get confused about. + + Also warn about constructions where there may be confusion to which + `if' statement an `else' branch belongs. Here is an example of + such a case: + + { + if (a) + if (b) + foo (); + else + bar (); + } + + In C, every `else' branch belongs to the innermost possible `if' + statement, which in this example is `if (b)'. This is often not + what the programmer expected, as illustrated in the above example + by indentation the programmer chose. When there is the potential + for this confusion, GCC will issue a warning when this flag is + specified. To eliminate the warning, add explicit braces around + the innermost `if' statement so there is no way the `else' could + belong to the enclosing `if'. The resulting code would look like + this: + + { + if (a) + { + if (b) + foo (); + else + bar (); + } + } + + `-Wsequence-point' + Warn about code that may have undefined semantics because of + violations of sequence point rules in the C standard. + + The C standard defines the order in which expressions in a C + program are evaluated in terms of "sequence points", which + represent a partial ordering between the execution of parts of the + program: those executed before the sequence point, and those + executed after it. These occur after the evaluation of a full + expression (one which is not part of a larger expression), after + the evaluation of the first operand of a `&&', `||', `? :' or `,' + (comma) operator, before a function is called (but after the + evaluation of its arguments and the expression denoting the called + function), and in certain other places. Other than as expressed + by the sequence point rules, the order of evaluation of + subexpressions of an expression is not specified. All these rules + describe only a partial order rather than a total order, since, + for example, if two functions are called within one expression + with no sequence point between them, the order in which the + functions are called is not specified. However, the standards + committee have ruled that function calls do not overlap. + + It is not specified when between sequence points modifications to + the values of objects take effect. Programs whose behavior + depends on this have undefined behavior; the C standard specifies + that "Between the previous and next sequence point an object shall + have its stored value modified at most once by the evaluation of + an expression. Furthermore, the prior value shall be read only to + determine the value to be stored.". If a program breaks these + rules, the results on any particular implementation are entirely + unpredictable. + + Examples of code with undefined behavior are `a = a++;', `a[n] = + b[n++]' and `a[i++] = i;'. Some more complicated cases are not + diagnosed by this option, and it may give an occasional false + positive result, but in general it has been found fairly effective + at detecting this sort of problem in programs. + + The present implementation of this option only works for C + programs. A future implementation may also work for C++ programs. + + The C standard is worded confusingly, therefore there is some + debate over the precise meaning of the sequence point rules in + subtle cases. Links to discussions of the problem, including + proposed formal definitions, may be found on our readings page, at + `http://gcc.gnu.org/readings.html'. + + `-Wreturn-type' + Warn whenever a function is defined with a return-type that + defaults to `int'. Also warn about any `return' statement with no + return-value in a function whose return-type is not `void'. + + For C++, a function without return type always produces a + diagnostic message, even when `-Wno-return-type' is specified. + The only exceptions are `main' and functions defined in system + headers. + + `-Wswitch' + Warn whenever a `switch' statement has an index of enumeral type + and lacks a `case' for one or more of the named codes of that + enumeration. (The presence of a `default' label prevents this + warning.) `case' labels outside the enumeration range also + provoke warnings when this option is used. + + `-Wtrigraphs' + Warn if any trigraphs are encountered that might change the + meaning of the program (trigraphs within comments are not warned + about). + + `-Wunused-function' + Warn whenever a static function is declared but not defined or a + non\-inline static function is unused. + + `-Wunused-label' + Warn whenever a label is declared but not used. + + To suppress this warning use the `unused' attribute (*note + Variable Attributes::). + + `-Wunused-parameter' + Warn whenever a function parameter is unused aside from its + declaration. + + To suppress this warning use the `unused' attribute (*note + Variable Attributes::). + + `-Wunused-variable' + Warn whenever a local variable or non-constant static variable is + unused aside from its declaration + + To suppress this warning use the `unused' attribute (*note + Variable Attributes::). + + `-Wunused-value' + Warn whenever a statement computes a result that is explicitly not + used. + + To suppress this warning cast the expression to `void'. + + `-Wunused' + All all the above `-Wunused' options combined. + + In order to get a warning about an unused function parameter, you + must either specify `-W -Wunused' or separately specify + `-Wunused-parameter'. + + `-Wuninitialized' + Warn if an automatic variable is used without first being + initialized or if a variable may be clobbered by a `setjmp' call. + + These warnings are possible only in optimizing compilation, + because they require data flow information that is computed only + when optimizing. If you don't specify `-O', you simply won't get + these warnings. + + These warnings occur only for variables that are candidates for + register allocation. Therefore, they do not occur for a variable + that is declared `volatile', or whose address is taken, or whose + size is other than 1, 2, 4 or 8 bytes. Also, they do not occur for + structures, unions or arrays, even when they are in registers. + + Note that there may be no warning about a variable that is used + only to compute a value that itself is never used, because such + computations may be deleted by data flow analysis before the + warnings are printed. + + These warnings are made optional because GCC is not smart enough + to see all the reasons why the code might be correct despite + appearing to have an error. Here is one example of how this can + happen: + + { + int x; + switch (y) + { + case 1: x = 1; + break; + case 2: x = 4; + break; + case 3: x = 5; + } + foo (x); + } + + If the value of `y' is always 1, 2 or 3, then `x' is always + initialized, but GCC doesn't know this. Here is another common + case: + + { + int save_y; + if (change_y) save_y = y, y = new_y; + ... + if (change_y) y = save_y; + } + + This has no bug because `save_y' is used only if it is set. + + This option also warns when a non-volatile automatic variable + might be changed by a call to `longjmp'. These warnings as well + are possible only in optimizing compilation. + + The compiler sees only the calls to `setjmp'. It cannot know + where `longjmp' will be called; in fact, a signal handler could + call it at any point in the code. As a result, you may get a + warning even when there is in fact no problem because `longjmp' + cannot in fact be called at the place which would cause a problem. + + Some spurious warnings can be avoided if you declare all the + functions you use that never return as `noreturn'. *Note Function + Attributes::. + + `-Wreorder (C++ only)' + Warn when the order of member initializers given in the code does + not match the order in which they must be executed. For instance: + + `-Wunknown-pragmas' + Warn when a #pragma directive is encountered which is not + understood by GCC. If this command line option is used, warnings + will even be issued for unknown pragmas in system header files. + This is not the case if the warnings were only enabled by the + `-Wall' command line option. + + `-Wall' + All of the above `-W' options combined. This enables all the + warnings about constructions that some users consider + questionable, and that are easy to avoid (or modify to prevent the + warning), even in conjunction with macros. + + `-Wdiv-by-zero' + Warn about compile-time integer division by zero. This is + default. To inhibit the warning messages, use `-Wno-div-by-zero'. + Floating point division by zero is not warned about, as it can be + a legitimate way of obtaining infinities and NaNs. + + `-Wmultichar' + Warn if a multicharacter constant (`'FOOF'') is used. This is + default. To inhibit the warning messages, use `-Wno-multichar'. + Usually they indicate a typo in the user's code, as they have + implementation-defined values, and should not be used in portable + code. + + `-Wsystem-headers' + Print warning messages for constructs found in system header files. + Warnings from system headers are normally suppressed, on the + assumption that they usually do not indicate real problems and + would only make the compiler output harder to read. Using this + command line option tells GCC to emit warnings from system headers + as if they occurred in user code. However, note that using + `-Wall' in conjunction with this option will _not_ warn about + unknown pragmas in system headers--for that, `-Wunknown-pragmas' + must also be used. + + The following `-W...' options are not implied by `-Wall'. Some of + them warn about constructions that users generally do not consider + questionable, but which occasionally you might wish to check for; + others warn about constructions that are necessary or hard to avoid in + some cases, and there is no simple way to modify the code to suppress + the warning. + + `-W' + Print extra warning messages for these events: + + * A function can return either with or without a value. + (Falling off the end of the function body is considered + returning without a value.) For example, this function would + evoke such a warning: + + foo (a) + { + if (a > 0) + return a; + } + + * An expression-statement or the left-hand side of a comma + expression contains no side effects. To suppress the + warning, cast the unused expression to void. For example, an + expression such as `x[i,j]' will cause a warning, but + `x[(void)i,j]' will not. + + * An unsigned value is compared against zero with `<' or `<='. + + * A comparison like `x<=y<=z' appears; this is equivalent to + `(x<=y ? 1 : 0) <= z', which is a different interpretation + from that of ordinary mathematical notation. + + * Storage-class specifiers like `static' are not the first + things in a declaration. According to the C Standard, this + usage is obsolescent. + + * The return type of a function has a type qualifier such as + `const'. Such a type qualifier has no effect, since the + value returned by a function is not an lvalue. (But don't + warn about the GNU extension of `volatile void' return types. + That extension will be warned about if `-pedantic' is + specified.) + + * If `-Wall' or `-Wunused' is also specified, warn about unused + arguments. + + * A comparison between signed and unsigned values could produce + an incorrect result when the signed value is converted to + unsigned. (But don't warn if `-Wno-sign-compare' is also + specified.) + + * An aggregate has a partly bracketed initializer. For + example, the following code would evoke such a warning, + because braces are missing around the initializer for `x.h': + + struct s { int f, g; }; + struct t { struct s h; int i; }; + struct t x = { 1, 2, 3 }; + + * An aggregate has an initializer which does not initialize all + members. For example, the following code would cause such a + warning, because `x.h' would be implicitly initialized to + zero: + + struct s { int f, g, h; }; + struct s x = { 3, 4 }; + + `-Wfloat-equal' + Warn if floating point values are used in equality comparisons. + + The idea behind this is that sometimes it is convenient (for the + programmer) to consider floating-point values as approximations to + infinitely precise real numbers. If you are doing this, then you + need to compute (by analysing the code, or in some other way) the + maximum or likely maximum error that the computation introduces, + and allow for it when performing comparisons (and when producing + output, but that's a different problem). In particular, instead + of testing for equality, you would check to see whether the two + values have ranges that overlap; and this is done with the + relational operators, so equality comparisons are probably + mistaken. + + `-Wtraditional (C only)' + Warn about certain constructs that behave differently in + traditional and ISO C. Also warn about ISO C constructs that have + no traditional C equivalent, and/or problematic constructs which + should be avoided. + + * Macro parameters that appear within string literals in the + macro body. In traditional C macro replacement takes place + within string literals, but does not in ISO C. + + * In traditional C, some preprocessor directives did not exist. + Traditional preprocessors would only consider a line to be a + directive if the `#' appeared in column 1 on the line. + Therefore `-Wtraditional' warns about directives that + traditional C understands but would ignore because the `#' + does not appear as the first character on the line. It also + suggests you hide directives like `#pragma' not understood by + traditional C by indenting them. Some traditional + implementations would not recognize `#elif', so it suggests + avoiding it altogether. + + * A function-like macro that appears without arguments. + + * The unary plus operator. + + * The `U' integer constant suffix, or the `F' or `L' floating + point constant suffixes. (Traditional C does support the `L' + suffix on integer constants.) Note, these suffixes appear in + macros defined in the system headers of most modern systems, + e.g. the `_MIN'/`_MAX' macros in `'. Use of these + macros in user code might normally lead to spurious warnings, + however gcc's integrated preprocessor has enough context to + avoid warning in these cases. + + * A function declared external in one block and then used after + the end of the block. + + * A `switch' statement has an operand of type `long'. + + * A non-`static' function declaration follows a `static' one. + This construct is not accepted by some traditional C + compilers. + + * The ISO type of an integer constant has a different width or + signedness from its traditional type. This warning is only + issued if the base of the constant is ten. I.e. hexadecimal + or octal values, which typically represent bit patterns, are + not warned about. + + * Usage of ISO string concatenation is detected. + + * Initialization of automatic aggregates. + + * Identifier conflicts with labels. Traditional C lacks a + separate namespace for labels. + + * Initialization of unions. If the initializer is zero, the + warning is omitted. This is done under the assumption that + the zero initializer in user code appears conditioned on e.g. + `__STDC__' to avoid missing initializer warnings and relies + on default initialization to zero in the traditional C case. + + * Conversions by prototypes between fixed/floating point values + and vice versa. The absence of these prototypes when + compiling with traditional C would cause serious problems. + This is a subset of the possible conversion warnings, for the + full set use `-Wconversion'. + + `-Wundef' + Warn if an undefined identifier is evaluated in an `#if' directive. + + `-Wshadow' + Warn whenever a local variable shadows another local variable, + parameter or global variable or whenever a built-in function is + shadowed. + + `-Wlarger-than-LEN' + Warn whenever an object of larger than LEN bytes is defined. + + `-Wpointer-arith' + Warn about anything that depends on the "size of" a function type + or of `void'. GNU C assigns these types a size of 1, for + convenience in calculations with `void *' pointers and pointers to + functions. + + `-Wbad-function-cast (C only)' + Warn whenever a function call is cast to a non-matching type. For + example, warn if `int malloc()' is cast to `anything *'. + + `-Wcast-qual' + Warn whenever a pointer is cast so as to remove a type qualifier + from the target type. For example, warn if a `const char *' is + cast to an ordinary `char *'. + + `-Wcast-align' + Warn whenever a pointer is cast such that the required alignment + of the target is increased. For example, warn if a `char *' is + cast to an `int *' on machines where integers can only be accessed + at two- or four-byte boundaries. + + `-Wwrite-strings' + When compiling C, give string constants the type `const + char[LENGTH]' so that copying the address of one into a + non-`const' `char *' pointer will get a warning; when compiling + C++, warn about the deprecated conversion from string constants to + `char *'. These warnings will help you find at compile time code + that can try to write into a string constant, but only if you have + been very careful about using `const' in declarations and + prototypes. Otherwise, it will just be a nuisance; this is why we + did not make `-Wall' request these warnings. + + `-Wconversion' + Warn if a prototype causes a type conversion that is different + from what would happen to the same argument in the absence of a + prototype. This includes conversions of fixed point to floating + and vice versa, and conversions changing the width or signedness + of a fixed point argument except when the same as the default + promotion. + + Also, warn if a negative integer constant expression is implicitly + converted to an unsigned type. For example, warn about the + assignment `x = -1' if `x' is unsigned. But do not warn about + explicit casts like `(unsigned) -1'. + + `-Wsign-compare' + Warn when a comparison between signed and unsigned values could + produce an incorrect result when the signed value is converted to + unsigned. This warning is also enabled by `-W'; to get the other + warnings of `-W' without this warning, use `-W -Wno-sign-compare'. + + `-Waggregate-return' + Warn if any functions that return structures or unions are defined + or called. (In languages where you can return an array, this also + elicits a warning.) + + `-Wstrict-prototypes (C only)' + Warn if a function is declared or defined without specifying the + argument types. (An old-style function definition is permitted + without a warning if preceded by a declaration which specifies the + argument types.) + + `-Wmissing-prototypes (C only)' + Warn if a global function is defined without a previous prototype + declaration. This warning is issued even if the definition itself + provides a prototype. The aim is to detect global functions that + fail to be declared in header files. + + `-Wmissing-declarations' + Warn if a global function is defined without a previous + declaration. Do so even if the definition itself provides a + prototype. Use this option to detect global functions that are + not declared in header files. + + `-Wmissing-noreturn' + Warn about functions which might be candidates for attribute + `noreturn'. Note these are only possible candidates, not absolute + ones. Care should be taken to manually verify functions actually + do not ever return before adding the `noreturn' attribute, + otherwise subtle code generation bugs could be introduced. You + will not get a warning for `main' in hosted C environments. + + `-Wmissing-format-attribute' + If `-Wformat' is enabled, also warn about functions which might be + candidates for `format' attributes. Note these are only possible + candidates, not absolute ones. GCC will guess that `format' + attributes might be appropriate for any function that calls a + function like `vprintf' or `vscanf', but this might not always be + the case, and some functions for which `format' attributes are + appropriate may not be detected. This option has no effect unless + `-Wformat' is enabled (possibly by `-Wall'). + + `-Wno-deprecated-declarations' + Do not warn about uses of functions, variables, and types marked as + deprecated by using the `deprecated' attribute. (*note Function + Attributes::, *note Variable Attributes::, *note Type + Attributes::.) + + `-Wpacked' + Warn if a structure is given the packed attribute, but the packed + attribute has no effect on the layout or size of the structure. + Such structures may be mis-aligned for little benefit. For + instance, in this code, the variable `f.x' in `struct bar' will be + misaligned even though `struct bar' does not itself have the + packed attribute: + + struct foo { + int x; + char a, b, c, d; + } __attribute__((packed)); + struct bar { + char z; + struct foo f; + }; + + `-Wpadded' + Warn if padding is included in a structure, either to align an + element of the structure or to align the whole structure. + Sometimes when this happens it is possible to rearrange the fields + of the structure to reduce the padding and so make the structure + smaller. + + `-Wredundant-decls' + Warn if anything is declared more than once in the same scope, + even in cases where multiple declaration is valid and changes + nothing. + + `-Wnested-externs (C only)' + Warn if an `extern' declaration is encountered within a function. + + `-Wunreachable-code' + Warn if the compiler detects that code will never be executed. + + This option is intended to warn when the compiler detects that at + least a whole line of source code will never be executed, because + some condition is never satisfied or because it is after a + procedure that never returns. + + It is possible for this option to produce a warning even though + there are circumstances under which part of the affected line can + be executed, so care should be taken when removing + apparently-unreachable code. + + For instance, when a function is inlined, a warning may mean that + the line is unreachable in only one inlined copy of the function. + + This option is not made part of `-Wall' because in a debugging + version of a program there is often substantial code which checks + correct functioning of the program and is, hopefully, unreachable + because the program does work. Another common use of unreachable + code is to provide behavior which is selectable at compile-time. + + `-Winline' + Warn if a function can not be inlined and it was declared as + inline. + + `-Wlong-long' + Warn if `long long' type is used. This is default. To inhibit + the warning messages, use `-Wno-long-long'. Flags `-Wlong-long' + and `-Wno-long-long' are taken into account only when `-pedantic' + flag is used. + + `-Wdisabled-optimization' + Warn if a requested optimization pass is disabled. This warning + does not generally indicate that there is anything wrong with your + code; it merely indicates that GCC's optimizers were unable to + handle the code effectively. Often, the problem is that your code + is too big or too complex; GCC will refuse to optimize programs + when the optimization itself is likely to take inordinate amounts + of time. + + `-Werror' + Make all warnings into errors. + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-4 gcc-3.2.3/gcc/doc/gcc.info-4 *** gcc-3.2.2/gcc/doc/gcc.info-4 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-4 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,1209 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Debugging Options, Next: Optimize Options, Prev: Warning Options, Up: Invoking GCC + + Options for Debugging Your Program or GCC + ========================================= + + GCC has various special options that are used for debugging either + your program or GCC: + + `-g' + Produce debugging information in the operating system's native + format (stabs, COFF, XCOFF, or DWARF). GDB can work with this + debugging information. + + On most systems that use stabs format, `-g' enables use of extra + debugging information that only GDB can use; this extra information + makes debugging work better in GDB but will probably make other + debuggers crash or refuse to read the program. If you want to + control for certain whether to generate the extra information, use + `-gstabs+', `-gstabs', `-gxcoff+', `-gxcoff', `-gdwarf-1+', + `-gdwarf-1', or `-gvms' (see below). + + Unlike most other C compilers, GCC allows you to use `-g' with + `-O'. The shortcuts taken by optimized code may occasionally + produce surprising results: some variables you declared may not + exist at all; flow of control may briefly move where you did not + expect it; some statements may not be executed because they + compute constant results or their values were already at hand; + some statements may execute in different places because they were + moved out of loops. + + Nevertheless it proves possible to debug optimized output. This + makes it reasonable to use the optimizer for programs that might + have bugs. + + The following options are useful when GCC is generated with the + capability for more than one debugging format. + + `-ggdb' + Produce debugging information for use by GDB. This means to use + the most expressive format available (DWARF 2, stabs, or the + native format if neither of those are supported), including GDB + extensions if at all possible. + + `-gstabs' + Produce debugging information in stabs format (if that is + supported), without GDB extensions. This is the format used by + DBX on most BSD systems. On MIPS, Alpha and System V Release 4 + systems this option produces stabs debugging output which is not + understood by DBX or SDB. On System V Release 4 systems this + option requires the GNU assembler. + + `-gstabs+' + Produce debugging information in stabs format (if that is + supported), using GNU extensions understood only by the GNU + debugger (GDB). The use of these extensions is likely to make + other debuggers crash or refuse to read the program. + + `-gcoff' + Produce debugging information in COFF format (if that is + supported). This is the format used by SDB on most System V + systems prior to System V Release 4. + + `-gxcoff' + Produce debugging information in XCOFF format (if that is + supported). This is the format used by the DBX debugger on IBM + RS/6000 systems. + + `-gxcoff+' + Produce debugging information in XCOFF format (if that is + supported), using GNU extensions understood only by the GNU + debugger (GDB). The use of these extensions is likely to make + other debuggers crash or refuse to read the program, and may cause + assemblers other than the GNU assembler (GAS) to fail with an + error. + + `-gdwarf' + Produce debugging information in DWARF version 1 format (if that is + supported). This is the format used by SDB on most System V + Release 4 systems. + + `-gdwarf+' + Produce debugging information in DWARF version 1 format (if that is + supported), using GNU extensions understood only by the GNU + debugger (GDB). The use of these extensions is likely to make + other debuggers crash or refuse to read the program. + + `-gdwarf-2' + Produce debugging information in DWARF version 2 format (if that is + supported). This is the format used by DBX on IRIX 6. + + `-gvms' + Produce debugging information in VMS debug format (if that is + supported). This is the format used by DEBUG on VMS systems. + + `-gLEVEL' + `-ggdbLEVEL' + `-gstabsLEVEL' + `-gcoffLEVEL' + `-gxcoffLEVEL' + `-gvmsLEVEL' + Request debugging information and also use LEVEL to specify how + much information. The default level is 2. + + Level 1 produces minimal information, enough for making backtraces + in parts of the program that you don't plan to debug. This + includes descriptions of functions and external variables, but no + information about local variables and no line numbers. + + Level 3 includes extra information, such as all the macro + definitions present in the program. Some debuggers support macro + expansion when you use `-g3'. + + Note that in order to avoid confusion between DWARF1 debug level 2, + and DWARF2, neither `-gdwarf' nor `-gdwarf-2' accept a + concatenated debug level. Instead use an additional `-gLEVEL' + option to change the debug level for DWARF1 or DWARF2. + + `-p' + Generate extra code to write profile information suitable for the + analysis program `prof'. You must use this option when compiling + the source files you want data about, and you must also use it when + linking. + + `-pg' + Generate extra code to write profile information suitable for the + analysis program `gprof'. You must use this option when compiling + the source files you want data about, and you must also use it when + linking. + + `-Q' + Makes the compiler print out each function name as it is compiled, + and print some statistics about each pass when it finishes. + + `-ftime-report' + Makes the compiler print some statistics about the time consumed + by each pass when it finishes. + + `-fmem-report' + Makes the compiler print some statistics about permanent memory + allocation when it finishes. + + `-fprofile-arcs' + Instrument "arcs" during compilation to generate coverage data or + for profile-directed block ordering. During execution the program + records how many times each branch is executed and how many times + it is taken. When the compiled program exits it saves this data + to a file called `SOURCENAME.da' for each source file. + + For profile-directed block ordering, compile the program with + `-fprofile-arcs' plus optimization and code generation options, + generate the arc profile information by running the program on a + selected workload, and then compile the program again with the same + optimization and code generation options plus + `-fbranch-probabilities' (*note Options that Control Optimization: + Optimize Options.). + + The other use of `-fprofile-arcs' is for use with `gcov', when it + is used with the `-ftest-coverage' option. + + With `-fprofile-arcs', for each function of your program GCC + creates a program flow graph, then finds a spanning tree for the + graph. Only arcs that are not on the spanning tree have to be + instrumented: the compiler adds code to count the number of times + that these arcs are executed. When an arc is the only exit or + only entrance to a block, the instrumentation code can be added to + the block; otherwise, a new basic block must be created to hold + the instrumentation code. + + `-ftest-coverage' + Create data files for the `gcov' code-coverage utility (*note + `gcov'--a Test Coverage Program: Gcov.). The data file names + begin with the name of your source file: + + `SOURCENAME.bb' + A mapping from basic blocks to line numbers, which `gcov' + uses to associate basic block execution counts with line + numbers. + + `SOURCENAME.bbg' + A list of all arcs in the program flow graph. This allows + `gcov' to reconstruct the program flow graph, so that it can + compute all basic block and arc execution counts from the + information in the `SOURCENAME.da' file. + + Use `-ftest-coverage' with `-fprofile-arcs'; the latter option + adds instrumentation to the program, which then writes execution + counts to another data file: + + `SOURCENAME.da' + Runtime arc execution counts, used in conjunction with the arc + information in the file `SOURCENAME.bbg'. + + Coverage data will map better to the source files if + `-ftest-coverage' is used without optimization. + + `-dLETTERS' + Says to make debugging dumps during compilation at times specified + by LETTERS. This is used for debugging the compiler. The file + names for most of the dumps are made by appending a pass number + and a word to the source file name (e.g. `foo.c.00.rtl' or + `foo.c.01.sibling'). Here are the possible letters for use in + LETTERS, and their meanings: + + `A' + Annotate the assembler output with miscellaneous debugging + information. + + `b' + Dump after computing branch probabilities, to `FILE.14.bp'. + + `B' + Dump after block reordering, to `FILE.29.bbro'. + + `c' + Dump after instruction combination, to the file + `FILE.16.combine'. + + `C' + Dump after the first if conversion, to the file `FILE.17.ce'. + + `d' + Dump after delayed branch scheduling, to `FILE.31.dbr'. + + `D' + Dump all macro definitions, at the end of preprocessing, in + addition to normal output. + + `e' + Dump after SSA optimizations, to `FILE.04.ssa' and + `FILE.07.ussa'. + + `E' + Dump after the second if conversion, to `FILE.26.ce2'. + + `f' + Dump after life analysis, to `FILE.15.life'. + + `F' + Dump after purging `ADDRESSOF' codes, to `FILE.09.addressof'. + + `g' + Dump after global register allocation, to `FILE.21.greg'. + + `h' + Dump after finalization of EH handling code, to `FILE.02.eh'. + + `k' + Dump after reg-to-stack conversion, to `FILE.28.stack'. + + `o' + Dump after post-reload optimizations, to `FILE.22.postreload'. + + `G' + Dump after GCSE, to `FILE.10.gcse'. + + `i' + Dump after sibling call optimizations, to `FILE.01.sibling'. + + `j' + Dump after the first jump optimization, to `FILE.03.jump'. + + `k' + Dump after conversion from registers to stack, to + `FILE.32.stack'. + + `l' + Dump after local register allocation, to `FILE.20.lreg'. + + `L' + Dump after loop optimization, to `FILE.11.loop'. + + `M' + Dump after performing the machine dependent reorganisation + pass, to `FILE.30.mach'. + + `n' + Dump after register renumbering, to `FILE.25.rnreg'. + + `N' + Dump after the register move pass, to `FILE.18.regmove'. + + `r' + Dump after RTL generation, to `FILE.00.rtl'. + + `R' + Dump after the second scheduling pass, to `FILE.27.sched2'. + + `s' + Dump after CSE (including the jump optimization that + sometimes follows CSE), to `FILE.08.cse'. + + `S' + Dump after the first scheduling pass, to `FILE.19.sched'. + + `t' + Dump after the second CSE pass (including the jump + optimization that sometimes follows CSE), to `FILE.12.cse2'. + + `w' + Dump after the second flow pass, to `FILE.23.flow2'. + + `X' + Dump after SSA dead code elimination, to `FILE.06.ssadce'. + + `z' + Dump after the peephole pass, to `FILE.24.peephole2'. + + `a' + Produce all the dumps listed above. + + `m' + Print statistics on memory usage, at the end of the run, to + standard error. + + `p' + Annotate the assembler output with a comment indicating which + pattern and alternative was used. The length of each + instruction is also printed. + + `P' + Dump the RTL in the assembler output as a comment before each + instruction. Also turns on `-dp' annotation. + + `v' + For each of the other indicated dump files (except for + `FILE.00.rtl'), dump a representation of the control flow + graph suitable for viewing with VCG to `FILE.PASS.vcg'. + + `x' + Just generate RTL for a function instead of compiling it. + Usually used with `r'. + + `y' + Dump debugging information during parsing, to standard error. + + `-fdump-unnumbered' + When doing debugging dumps (see `-d' option above), suppress + instruction numbers and line number note output. This makes it + more feasible to use diff on debugging dumps for compiler + invocations with different options, in particular with and without + `-g'. + + `-fdump-translation-unit (C and C++ only)' + `-fdump-translation-unit-OPTIONS (C and C++ only)' + Dump a representation of the tree structure for the entire + translation unit to a file. The file name is made by appending + `.tu' to the source file name. If the `-OPTIONS' form is used, + OPTIONS controls the details of the dump as described for the + `-fdump-tree' options. + + `-fdump-class-hierarchy (C++ only)' + `-fdump-class-hierarchy-OPTIONS (C++ only)' + Dump a representation of each class's hierarchy and virtual + function table layout to a file. The file name is made by + appending `.class' to the source file name. If the `-OPTIONS' + form is used, OPTIONS controls the details of the dump as + described for the `-fdump-tree' options. + + `-fdump-tree-SWITCH (C++ only)' + `-fdump-tree-SWITCH-OPTIONS (C++ only)' + Control the dumping at various stages of processing the + intermediate language tree to a file. The file name is generated + by appending a switch specific suffix to the source file name. If + the `-OPTIONS' form is used, OPTIONS is a list of `-' separated + options that control the details of the dump. Not all options are + applicable to all dumps, those which are not meaningful will be + ignored. The following options are available + + `address' + Print the address of each node. Usually this is not + meaningful as it changes according to the environment and + source file. Its primary use is for tying up a dump file with + a debug environment. + + `slim' + Inhibit dumping of members of a scope or body of a function + merely because that scope has been reached. Only dump such + items when they are directly reachable by some other path. + + `all' + Turn on all options. + + The following tree dumps are possible: + `original' + Dump before any tree based optimization, to `FILE.original'. + + `optimized' + Dump after all tree based optimization, to `FILE.optimized'. + + `inlined' + Dump after function inlining, to `FILE.inlined'. + + `-fsched-verbose=N' + On targets that use instruction scheduling, this option controls + the amount of debugging output the scheduler prints. This + information is written to standard error, unless `-dS' or `-dR' is + specified, in which case it is output to the usual dump listing + file, `.sched' or `.sched2' respectively. However for N greater + than nine, the output is always printed to standard error. + + For N greater than zero, `-fsched-verbose' outputs the same + information as `-dRS'. For N greater than one, it also output + basic block probabilities, detailed ready list information and + unit/insn info. For N greater than two, it includes RTL at abort + point, control-flow and regions info. And for N over four, + `-fsched-verbose' also includes dependence info. + + `-fpretend-float' + When running a cross-compiler, pretend that the target machine + uses the same floating point format as the host machine. This + causes incorrect output of the actual floating constants, but the + actual instruction sequence will probably be the same as GCC would + make when running on the target machine. + + `-save-temps' + Store the usual "temporary" intermediate files permanently; place + them in the current directory and name them based on the source + file. Thus, compiling `foo.c' with `-c -save-temps' would produce + files `foo.i' and `foo.s', as well as `foo.o'. This creates a + preprocessed `foo.i' output file even though the compiler now + normally uses an integrated preprocessor. + + `-time' + Report the CPU time taken by each subprocess in the compilation + sequence. For C source files, this is the compiler proper and + assembler (plus the linker if linking is done). The output looks + like this: + + # cc1 0.12 0.01 + # as 0.00 0.01 + + The first number on each line is the "user time," that is time + spent executing the program itself. The second number is "system + time," time spent executing operating system routines on behalf of + the program. Both numbers are in seconds. + + `-print-file-name=LIBRARY' + Print the full absolute name of the library file LIBRARY that + would be used when linking--and don't do anything else. With this + option, GCC does not compile or link anything; it just prints the + file name. + + `-print-multi-directory' + Print the directory name corresponding to the multilib selected by + any other switches present in the command line. This directory is + supposed to exist in `GCC_EXEC_PREFIX'. + + `-print-multi-lib' + Print the mapping from multilib directory names to compiler + switches that enable them. The directory name is separated from + the switches by `;', and each switch starts with an `@' instead of + the `-', without spaces between multiple switches. This is + supposed to ease shell-processing. + + `-print-prog-name=PROGRAM' + Like `-print-file-name', but searches for a program such as `cpp'. + + `-print-libgcc-file-name' + Same as `-print-file-name=libgcc.a'. + + This is useful when you use `-nostdlib' or `-nodefaultlibs' but + you do want to link with `libgcc.a'. You can do + + gcc -nostdlib FILES... `gcc -print-libgcc-file-name` + + `-print-search-dirs' + Print the name of the configured installation directory and a list + of program and library directories gcc will search--and don't do + anything else. + + This is useful when gcc prints the error message `installation + problem, cannot exec cpp0: No such file or directory'. To resolve + this you either need to put `cpp0' and the other compiler + components where gcc expects to find them, or you can set the + environment variable `GCC_EXEC_PREFIX' to the directory where you + installed them. Don't forget the trailing '/'. *Note Environment + Variables::. + + `-dumpmachine' + Print the compiler's target machine (for example, + `i686-pc-linux-gnu')--and don't do anything else. + + `-dumpversion' + Print the compiler version (for example, `3.0')--and don't do + anything else. + + `-dumpspecs' + Print the compiler's built-in specs--and don't do anything else. + (This is used when GCC itself is being built.) *Note Spec Files::. + +  + File: gcc.info, Node: Optimize Options, Next: Preprocessor Options, Prev: Debugging Options, Up: Invoking GCC + + Options That Control Optimization + ================================= + + These options control various sorts of optimizations: + + `-O' + `-O1' + Optimize. Optimizing compilation takes somewhat more time, and a + lot more memory for a large function. + + Without `-O', the compiler's goal is to reduce the cost of + compilation and to make debugging produce the expected results. + Statements are independent: if you stop the program with a + breakpoint between statements, you can then assign a new value to + any variable or change the program counter to any other statement + in the function and get exactly the results you would expect from + the source code. + + With `-O', the compiler tries to reduce code size and execution + time, without performing any optimizations that take a great deal + of compilation time. + + `-O2' + Optimize even more. GCC performs nearly all supported + optimizations that do not involve a space-speed tradeoff. The + compiler does not perform loop unrolling or function inlining when + you specify `-O2'. As compared to `-O', this option increases + both compilation time and the performance of the generated code. + + `-O2' turns on all optional optimizations except for loop + unrolling, function inlining, and register renaming. It also + turns on the `-fforce-mem' option on all machines and frame + pointer elimination on machines where doing so does not interfere + with debugging. + + Please note the warning under `-fgcse' about invoking `-O2' on + programs that use computed gotos. + + `-O3' + Optimize yet more. `-O3' turns on all optimizations specified by + `-O2' and also turns on the `-finline-functions' and + `-frename-registers' options. + + `-O0' + Do not optimize. + + `-Os' + Optimize for size. `-Os' enables all `-O2' optimizations that do + not typically increase code size. It also performs further + optimizations designed to reduce code size. + + If you use multiple `-O' options, with or without level numbers, + the last such option is the one that is effective. + + Options of the form `-fFLAG' specify machine-independent flags. + Most flags have both positive and negative forms; the negative form of + `-ffoo' would be `-fno-foo'. In the table below, only one of the forms + is listed--the one which is not the default. You can figure out the + other form by either removing `no-' or adding it. + + `-ffloat-store' + Do not store floating point variables in registers, and inhibit + other options that might change whether a floating point value is + taken from a register or memory. + + This option prevents undesirable excess precision on machines such + as the 68000 where the floating registers (of the 68881) keep more + precision than a `double' is supposed to have. Similarly for the + x86 architecture. For most programs, the excess precision does + only good, but a few programs rely on the precise definition of + IEEE floating point. Use `-ffloat-store' for such programs, after + modifying them to store all pertinent intermediate computations + into variables. + + `-fno-default-inline' + Do not make member functions inline by default merely because they + are defined inside the class scope (C++ only). Otherwise, when + you specify `-O', member functions defined inside class scope are + compiled inline by default; i.e., you don't need to add `inline' + in front of the member function name. + + `-fno-defer-pop' + Always pop the arguments to each function call as soon as that + function returns. For machines which must pop arguments after a + function call, the compiler normally lets arguments accumulate on + the stack for several function calls and pops them all at once. + + `-fforce-mem' + Force memory operands to be copied into registers before doing + arithmetic on them. This produces better code by making all memory + references potential common subexpressions. When they are not + common subexpressions, instruction combination should eliminate + the separate register-load. The `-O2' option turns on this option. + + `-fforce-addr' + Force memory address constants to be copied into registers before + doing arithmetic on them. This may produce better code just as + `-fforce-mem' may. + + `-fomit-frame-pointer' + Don't keep the frame pointer in a register for functions that + don't need one. This avoids the instructions to save, set up and + restore frame pointers; it also makes an extra register available + in many functions. *It also makes debugging impossible on some + machines.* + + On some machines, such as the VAX, this flag has no effect, because + the standard calling sequence automatically handles the frame + pointer and nothing is saved by pretending it doesn't exist. The + machine-description macro `FRAME_POINTER_REQUIRED' controls + whether a target machine supports this flag. *Note Register + Usage: (gccint)Registers. + + `-foptimize-sibling-calls' + Optimize sibling and tail recursive calls. + + `-ftrapv' + This option generates traps for signed overflow on addition, + subtraction, multiplication operations. + + `-fno-inline' + Don't pay attention to the `inline' keyword. Normally this option + is used to keep the compiler from expanding any functions inline. + Note that if you are not optimizing, no functions can be expanded + inline. + + `-finline-functions' + Integrate all simple functions into their callers. The compiler + heuristically decides which functions are simple enough to be worth + integrating in this way. + + If all calls to a given function are integrated, and the function + is declared `static', then the function is normally not output as + assembler code in its own right. + + `-finline-limit=N' + By default, gcc limits the size of functions that can be inlined. + This flag allows the control of this limit for functions that are + explicitly marked as inline (ie marked with the inline keyword or + defined within the class definition in c++). N is the size of + functions that can be inlined in number of pseudo instructions + (not counting parameter handling). The default value of N is 600. + Increasing this value can result in more inlined code at the cost + of compilation time and memory consumption. Decreasing usually + makes the compilation faster and less code will be inlined (which + presumably means slower programs). This option is particularly + useful for programs that use inlining heavily such as those based + on recursive templates with C++. + + _Note:_ pseudo instruction represents, in this particular context, + an abstract measurement of function's size. In no way, it + represents a count of assembly instructions and as such its exact + meaning might change from one release to an another. + + `-fkeep-inline-functions' + Even if all calls to a given function are integrated, and the + function is declared `static', nevertheless output a separate + run-time callable version of the function. This switch does not + affect `extern inline' functions. + + `-fkeep-static-consts' + Emit variables declared `static const' when optimization isn't + turned on, even if the variables aren't referenced. + + GCC enables this option by default. If you want to force the + compiler to check if the variable was referenced, regardless of + whether or not optimization is turned on, use the + `-fno-keep-static-consts' option. + + `-fmerge-constants' + Attempt to merge identical constants (string constants and + floating point constants) accross compilation units. + + This option is default for optimized compilation if assembler and + linker support it. Use `-fno-merge-constants' to inhibit this + behavior. + + `-fmerge-all-constants' + Attempt to merge identical constants and identical variables. + + This option implies `-fmerge-constants'. In addition to + `-fmerge-constants' this considers e.g. even constant initialized + arrays or initialized constant variables with integral or floating + point types. Languages like C or C++ require each non-automatic + variable to have distinct location, so using this option will + result in non-conforming behavior. + + `-fno-branch-count-reg' + Do not use "decrement and branch" instructions on a count register, + but instead generate a sequence of instructions that decrement a + register, compare it against zero, then branch based upon the + result. This option is only meaningful on architectures that + support such instructions, which include x86, PowerPC, IA-64 and + S/390. + + `-fno-function-cse' + Do not put function addresses in registers; make each instruction + that calls a constant function contain the function's address + explicitly. + + This option results in less efficient code, but some strange hacks + that alter the assembler output may be confused by the + optimizations performed when this option is not used. + + `-ffast-math' + Sets `-fno-math-errno', `-funsafe-math-optimizations', and + `-fno-trapping-math'. + + This option causes the preprocessor macro `__FAST_MATH__' to be + defined. + + This option should never be turned on by any `-O' option since it + can result in incorrect output for programs which depend on an + exact implementation of IEEE or ISO rules/specifications for math + functions. + + `-fno-math-errno' + Do not set ERRNO after calling math functions that are executed + with a single instruction, e.g., sqrt. A program that relies on + IEEE exceptions for math error handling may want to use this flag + for speed while maintaining IEEE arithmetic compatibility. + + This option should never be turned on by any `-O' option since it + can result in incorrect output for programs which depend on an + exact implementation of IEEE or ISO rules/specifications for math + functions. + + The default is `-fmath-errno'. + + `-funsafe-math-optimizations' + Allow optimizations for floating-point arithmetic that (a) assume + that arguments and results are valid and (b) may violate IEEE or + ANSI standards. When used at link-time, it may include libraries + or startup files that change the default FPU control word or other + similar optimizations. + + This option should never be turned on by any `-O' option since it + can result in incorrect output for programs which depend on an + exact implementation of IEEE or ISO rules/specifications for math + functions. + + The default is `-fno-unsafe-math-optimizations'. + + `-fno-trapping-math' + Compile code assuming that floating-point operations cannot + generate user-visible traps. Setting this option may allow faster + code if one relies on "non-stop" IEEE arithmetic, for example. + + This option should never be turned on by any `-O' option since it + can result in incorrect output for programs which depend on an + exact implementation of IEEE or ISO rules/specifications for math + functions. + + The default is `-ftrapping-math'. + + `-fbounds-check' + For front-ends that support it, generate additional code to check + that indices used to access arrays are within the declared range. + This is currenly only supported by the Java and Fortran 77 + front-ends, where this option defaults to true and false + respectively. + + + The following options control specific optimizations. The `-O2' + option turns on all of these optimizations except `-funroll-loops' and + `-funroll-all-loops'. On most machines, the `-O' option turns on the + `-fthread-jumps' and `-fdelayed-branch' options, but specific machines + may handle it differently. + + You can use the following flags in the rare cases when "fine-tuning" + of optimizations to be performed is desired. + + Not all of the optimizations performed by GCC have `-f' options to + control them. + + `-fstrength-reduce' + Perform the optimizations of loop strength reduction and + elimination of iteration variables. + + `-fthread-jumps' + Perform optimizations where we check to see if a jump branches to a + location where another comparison subsumed by the first is found. + If so, the first branch is redirected to either the destination of + the second branch or a point immediately following it, depending + on whether the condition is known to be true or false. + + `-fcse-follow-jumps' + In common subexpression elimination, scan through jump instructions + when the target of the jump is not reached by any other path. For + example, when CSE encounters an `if' statement with an `else' + clause, CSE will follow the jump when the condition tested is + false. + + `-fcse-skip-blocks' + This is similar to `-fcse-follow-jumps', but causes CSE to follow + jumps which conditionally skip over blocks. When CSE encounters a + simple `if' statement with no else clause, `-fcse-skip-blocks' + causes CSE to follow the jump around the body of the `if'. + + `-frerun-cse-after-loop' + Re-run common subexpression elimination after loop optimizations + has been performed. + + `-frerun-loop-opt' + Run the loop optimizer twice. + + `-fgcse' + Perform a global common subexpression elimination pass. This pass + also performs global constant and copy propagation. + + _Note:_ When compiling a program using computed gotos, a GCC + extension, you may get better runtime performance if you disable + the global common subexpression elmination pass by adding + `-fno-gcse' to the command line. + + `-fgcse-lm' + When `-fgcse-lm' is enabled, global common subexpression + elimination will attempt to move loads which are only killed by + stores into themselves. This allows a loop containing a + load/store sequence to be changed to a load outside the loop, and + a copy/store within the loop. + + `-fgcse-sm' + When `-fgcse-sm' is enabled, A store motion pass is run after + global common subexpression elimination. This pass will attempt + to move stores out of loops. When used in conjunction with + `-fgcse-lm', loops containing a load/store sequence can be changed + to a load before the loop and a store after the loop. + + `-fdelete-null-pointer-checks' + Use global dataflow analysis to identify and eliminate useless + checks for null pointers. The compiler assumes that dereferencing + a null pointer would have halted the program. If a pointer is + checked after it has already been dereferenced, it cannot be null. + + In some environments, this assumption is not true, and programs can + safely dereference null pointers. Use + `-fno-delete-null-pointer-checks' to disable this optimization for + programs which depend on that behavior. + + `-fexpensive-optimizations' + Perform a number of minor optimizations that are relatively + expensive. + + `-foptimize-register-move' + `-fregmove' + Attempt to reassign register numbers in move instructions and as + operands of other simple instructions in order to maximize the + amount of register tying. This is especially helpful on machines + with two-operand instructions. GCC enables this optimization by + default with `-O2' or higher. + + Note `-fregmove' and `-foptimize-register-move' are the same + optimization. + + `-fdelayed-branch' + If supported for the target machine, attempt to reorder + instructions to exploit instruction slots available after delayed + branch instructions. + + `-fschedule-insns' + If supported for the target machine, attempt to reorder + instructions to eliminate execution stalls due to required data + being unavailable. This helps machines that have slow floating + point or memory load instructions by allowing other instructions + to be issued until the result of the load or floating point + instruction is required. + + `-fschedule-insns2' + Similar to `-fschedule-insns', but requests an additional pass of + instruction scheduling after register allocation has been done. + This is especially useful on machines with a relatively small + number of registers and where memory load instructions take more + than one cycle. + + `-fno-sched-interblock' + Don't schedule instructions across basic blocks. This is normally + enabled by default when scheduling before register allocation, i.e. + with `-fschedule-insns' or at `-O2' or higher. + + `-fno-sched-spec' + Don't allow speculative motion of non-load instructions. This is + normally enabled by default when scheduling before register + allocation, i.e. with `-fschedule-insns' or at `-O2' or higher. + + `-fsched-spec-load' + Allow speculative motion of some load instructions. This only + makes sense when scheduling before register allocation, i.e. with + `-fschedule-insns' or at `-O2' or higher. + + `-fsched-spec-load-dangerous' + Allow speculative motion of more load instructions. This only + makes sense when scheduling before register allocation, i.e. with + `-fschedule-insns' or at `-O2' or higher. + + `-ffunction-sections' + `-fdata-sections' + Place each function or data item into its own section in the output + file if the target supports arbitrary sections. The name of the + function or the name of the data item determines the section's name + in the output file. + + Use these options on systems where the linker can perform + optimizations to improve locality of reference in the instruction + space. HPPA processors running HP-UX and Sparc processors running + Solaris 2 have linkers with such optimizations. Other systems + using the ELF object format as well as AIX may have these + optimizations in the future. + + Only use these options when there are significant benefits from + doing so. When you specify these options, the assembler and + linker will create larger object and executable files and will + also be slower. You will not be able to use `gprof' on all + systems if you specify this option and you may have problems with + debugging if you specify both this option and `-g'. + + `-fcaller-saves' + Enable values to be allocated in registers that will be clobbered + by function calls, by emitting extra instructions to save and + restore the registers around such calls. Such allocation is done + only when it seems to result in better code than would otherwise + be produced. + + This option is always enabled by default on certain machines, + usually those which have no call-preserved registers to use + instead. + + For all machines, optimization level 2 and higher enables this + flag by default. + + `-funroll-loops' + Unroll loops whose number of iterations can be determined at + compile time or upon entry to the loop. `-funroll-loops' implies + both `-fstrength-reduce' and `-frerun-cse-after-loop'. This + option makes code larger, and may or may not make it run faster. + + `-funroll-all-loops' + Unroll all loops, even if their number of iterations is uncertain + when the loop is entered. This usually makes programs run more + slowly. `-funroll-all-loops' implies the same options as + `-funroll-loops', + + `-fprefetch-loop-arrays' + If supported by the target machine, generate instructions to + prefetch memory to improve the performance of loops that access + large arrays. + + `-fmove-all-movables' + Forces all invariant computations in loops to be moved outside the + loop. + + `-freduce-all-givs' + Forces all general-induction variables in loops to be + strength-reduced. + + _Note:_ When compiling programs written in Fortran, + `-fmove-all-movables' and `-freduce-all-givs' are enabled by + default when you use the optimizer. + + These options may generate better or worse code; results are highly + dependent on the structure of loops within the source code. + + These two options are intended to be removed someday, once they + have helped determine the efficacy of various approaches to + improving loop optimizations. + + Please let us ( and ) know how + use of these options affects the performance of your production + code. We're very interested in code that runs _slower_ when these + options are _enabled_. + + `-fno-peephole' + `-fno-peephole2' + Disable any machine-specific peephole optimizations. The + difference between `-fno-peephole' and `-fno-peephole2' is in how + they are implemented in the compiler; some targets use one, some + use the other, a few use both. + + `-fbranch-probabilities' + After running a program compiled with `-fprofile-arcs' (*note + Options for Debugging Your Program or `gcc': Debugging Options.), + you can compile it a second time using `-fbranch-probabilities', + to improve optimizations based on the number of times each branch + was taken. When the program compiled with `-fprofile-arcs' exits + it saves arc execution counts to a file called `SOURCENAME.da' for + each source file The information in this data file is very + dependent on the structure of the generated code, so you must use + the same source code and the same optimization options for both + compilations. + + With `-fbranch-probabilities', GCC puts a `REG_EXEC_COUNT' note on + the first instruction of each basic block, and a `REG_BR_PROB' + note on each `JUMP_INSN' and `CALL_INSN'. These can be used to + improve optimization. Currently, they are only used in one place: + in `reorg.c', instead of guessing which path a branch is mostly to + take, the `REG_BR_PROB' values are used to exactly determine which + path is taken more often. + + `-fno-guess-branch-probability' + Do not guess branch probabilities using a randomized model. + + Sometimes gcc will opt to use a randomized model to guess branch + probabilities, when none are available from either profiling + feedback (`-fprofile-arcs') or `__builtin_expect'. This means that + different runs of the compiler on the same program may produce + different object code. + + In a hard real-time system, people don't want different runs of the + compiler to produce code that has different behavior; minimizing + non-determinism is of paramount import. This switch allows users + to reduce non-determinism, possibly at the expense of inferior + optimization. + + `-fstrict-aliasing' + Allows the compiler to assume the strictest aliasing rules + applicable to the language being compiled. For C (and C++), this + activates optimizations based on the type of expressions. In + particular, an object of one type is assumed never to reside at + the same address as an object of a different type, unless the + types are almost the same. For example, an `unsigned int' can + alias an `int', but not a `void*' or a `double'. A character type + may alias any other type. + + Pay special attention to code like this: + union a_union { + int i; + double d; + }; + + int f() { + a_union t; + t.d = 3.0; + return t.i; + } + The practice of reading from a different union member than the one + most recently written to (called "type-punning") is common. Even + with `-fstrict-aliasing', type-punning is allowed, provided the + memory is accessed through the union type. So, the code above + will work as expected. However, this code might not: + int f() { + a_union t; + int* ip; + t.d = 3.0; + ip = &t.i; + return *ip; + } + + Every language that wishes to perform language-specific alias + analysis should define a function that computes, given an `tree' + node, an alias set for the node. Nodes in different alias sets + are not allowed to alias. For an example, see the C front-end + function `c_get_alias_set'. + + `-falign-functions' + `-falign-functions=N' + Align the start of functions to the next power-of-two greater than + N, skipping up to N bytes. For instance, `-falign-functions=32' + aligns functions to the next 32-byte boundary, but + `-falign-functions=24' would align to the next 32-byte boundary + only if this can be done by skipping 23 bytes or less. + + `-fno-align-functions' and `-falign-functions=1' are equivalent + and mean that functions will not be aligned. + + Some assemblers only support this flag when N is a power of two; + in that case, it is rounded up. + + If N is not specified, use a machine-dependent default. + + `-falign-labels' + `-falign-labels=N' + Align all branch targets to a power-of-two boundary, skipping up to + N bytes like `-falign-functions'. This option can easily make + code slower, because it must insert dummy operations for when the + branch target is reached in the usual flow of the code. + + If `-falign-loops' or `-falign-jumps' are applicable and are + greater than this value, then their values are used instead. + + If N is not specified, use a machine-dependent default which is + very likely to be `1', meaning no alignment. + + `-falign-loops' + `-falign-loops=N' + Align loops to a power-of-two boundary, skipping up to N bytes + like `-falign-functions'. The hope is that the loop will be + executed many times, which will make up for any execution of the + dummy operations. + + If N is not specified, use a machine-dependent default. + + `-falign-jumps' + `-falign-jumps=N' + Align branch targets to a power-of-two boundary, for branch targets + where the targets can only be reached by jumping, skipping up to N + bytes like `-falign-functions'. In this case, no dummy operations + need be executed. + + If N is not specified, use a machine-dependent default. + + `-fssa' + Perform optimizations in static single assignment form. Each + function's flow graph is translated into SSA form, optimizations + are performed, and the flow graph is translated back from SSA + form. Users should not specify this option, since it is not yet + ready for production use. + + `-fssa-ccp' + Perform Sparse Conditional Constant Propagation in SSA form. + Requires `-fssa'. Like `-fssa', this is an experimental feature. + + `-fssa-dce' + Perform aggressive dead-code elimination in SSA form. Requires + `-fssa'. Like `-fssa', this is an experimental feature. + + `-fsingle-precision-constant' + Treat floating point constant as single precision constant instead + of implicitly converting it to double precision constant. + + `-frename-registers' + Attempt to avoid false dependencies in scheduled code by making use + of registers left over after register allocation. This + optimization will most benefit processors with lots of registers. + It can, however, make debugging impossible, since variables will + no longer stay in a "home register". + + `-fno-cprop-registers' + After register allocation and post-register allocation instruction + splitting, we perform a copy-propagation pass to try to reduce + scheduling dependencies and occasionally eliminate the copy. + + `--param NAME=VALUE' + In some places, GCC uses various constants to control the amount of + optimization that is done. For example, GCC will not inline + functions that contain more that a certain number of instructions. + You can control some of these constants on the command-line using + the `--param' option. + + In each case, the VALUE is an integer. The allowable choices for + NAME are given in the following table: + + `max-delay-slot-insn-search' + The maximum number of instructions to consider when looking + for an instruction to fill a delay slot. If more than this + arbitrary number of instructions is searched, the time + savings from filling the delay slot will be minimal so stop + searching. Increasing values mean more aggressive + optimization, making the compile time increase with probably + small improvement in executable run time. + + `max-delay-slot-live-search' + When trying to fill delay slots, the maximum number of + instructions to consider when searching for a block with + valid live register information. Increasing this arbitrarily + chosen value means more aggressive optimization, increasing + the compile time. This parameter should be removed when the + delay slot code is rewritten to maintain the control-flow + graph. + + `max-gcse-memory' + The approximate maximum amount of memory that will be + allocated in order to perform the global common subexpression + elimination optimization. If more memory than specified is + required, the optimization will not be done. + + `max-gcse-passes' + The maximum number of passes of GCSE to run. + + `max-pending-list-length' + The maximum number of pending dependencies scheduling will + allow before flushing the current state and starting over. + Large functions with few branches or calls can create + excessively large lists which needlessly consume memory and + resources. + + `max-inline-insns' + If an function contains more than this many instructions, it + will not be inlined. This option is precisely equivalent to + `-finline-limit'. + + diff -Nrc3pad gcc-3.2.2/gcc/doc/gcc.info-5 gcc-3.2.3/gcc/doc/gcc.info-5 *** gcc-3.2.2/gcc/doc/gcc.info-5 Thu Jan 1 00:00:00 1970 --- gcc-3.2.3/gcc/doc/gcc.info-5 Tue Apr 22 07:07:14 2003 *************** *** 0 **** --- 1,812 ---- + This is doc/gcc.info, produced by makeinfo version 4.5 from + doc/gcc.texi. + + INFO-DIR-SECTION Programming + START-INFO-DIR-ENTRY + * gcc: (gcc). The GNU Compiler Collection. + END-INFO-DIR-ENTRY + This file documents the use of the GNU compilers. + + Published by the Free Software Foundation + 59 Temple Place - Suite 330 + Boston, MA 02111-1307 USA + + Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, + 1999, 2000, 2001, 2002 Free Software Foundation, Inc. + + Permission is granted to copy, distribute and/or modify this document + under the terms of the GNU Free Documentation License, Version 1.1 or + any later version published by the Free Software Foundation; with the + Invariant Sections being "GNU General Public License" and "Funding Free + Software", the Front-Cover texts being (a) (see below), and with the + Back-Cover Texts being (b) (see below). A copy of the license is + included in the section entitled "GNU Free Documentation License". + + (a) The FSF's Front-Cover Text is: + + A GNU Manual + + (b) The FSF's Back-Cover Text is: + + You have freedom to copy and modify this GNU Manual, like GNU + software. Copies published by the Free Software Foundation raise + funds for GNU development. + +  + File: gcc.info, Node: Preprocessor Options, Next: Assembler Options, Prev: Optimize Options, Up: Invoking GCC + + Options Controlling the Preprocessor + ==================================== + + These options control the C preprocessor, which is run on each C + source file before actual compilation. + + If you use the `-E' option, nothing is done except preprocessing. + Some of these options make sense only together with `-E' because they + cause the preprocessor output to be unsuitable for actual compilation. + + You can use `-Wp,OPTION' to bypass the compiler driver and pass + OPTION directly through to the preprocessor. If OPTION contains + commas, it is split into multiple options at the commas. However, many + options are modified, translated or interpreted by the compiler driver + before being passed to the preprocessor, and `-Wp' forcibly bypasses + this phase. The preprocessor's direct interface is undocumented and + subject to change, so whenever possible you should avoid using `-Wp' + and let the driver handle the options instead. + + `-D NAME' + Predefine NAME as a macro, with definition `1'. + + `-D NAME=DEFINITION' + Predefine NAME as a macro, with definition DEFINITION. There are + no restrictions on the contents of DEFINITION, but if you are + invoking the preprocessor from a shell or shell-like program you + may need to use the shell's quoting syntax to protect characters + such as spaces that have a meaning in the shell syntax. + + If you wish to define a function-like macro on the command line, + write its argument list with surrounding parentheses before the + equals sign (if any). Parentheses are meaningful to most shells, + so you will need to quote the option. With `sh' and `csh', + `-D'NAME(ARGS...)=DEFINITION'' works. + + `-D' and `-U' options are processed in the order they are given on + the command line. All `-imacros FILE' and `-include FILE' options + are processed after all `-D' and `-U' options. + + `-U NAME' + Cancel any previous definition of NAME, either built in or + provided with a `-D' option. + + `-undef' + Do not predefine any system-specific macros. The common predefined + macros remain defined. + + `-I DIR' + Add the directory DIR to the list of directories to be searched + for header files. Directories named by `-I' are searched before + the standard system include directories. + + It is dangerous to specify a standard system include directory in + an `-I' option. This defeats the special treatment of system + headers . It can also defeat the repairs to buggy system headers + which GCC makes when it is installed. + + `-o FILE' + Write output to FILE. This is the same as specifying FILE as the + second non-option argument to `cpp'. `gcc' has a different + interpretation of a second non-option argument, so you must use + `-o' to specify the output file. + + `-Wall' + Turns on all optional warnings which are desirable for normal + code. At present this is `-Wcomment' and `-Wtrigraphs'. Note that + many of the preprocessor's warnings are on by default and have no + options to control them. + + `-Wcomment' + `-Wcomments' + Warn whenever a comment-start sequence `/*' appears in a `/*' + comment, or whenever a backslash-newline appears in a `//' comment. + (Both forms have the same effect.) + + `-Wtrigraphs' + Warn if any trigraphs are encountered. This option used to take + effect only if `-trigraphs' was also specified, but now works + independently. Warnings are not given for trigraphs within + comments, as they do not affect the meaning of the program. + + `-Wtraditional' + Warn about certain constructs that behave differently in + traditional and ISO C. Also warn about ISO C constructs that have + no traditional C equivalent, and problematic constructs which + should be avoided. + + `-Wimport' + Warn the first time `#import' is used. + + `-Wundef' + Warn whenever an identifier which is not a macro is encountered in + an `#if' directive, outside of `defined'. Such identifiers are + replaced with zero. + + `-Werror' + Make all warnings into hard errors. Source code which triggers + warnings will be rejected. + + `-Wsystem-headers' + Issue warnings for code in system headers. These are normally + unhelpful in finding bugs in your own code, therefore suppressed. + If you are responsible for the system library, you may want to see + them. + + `-w' + Suppress all warnings, including those which GNU CPP issues by + default. + + `-pedantic' + Issue all the mandatory diagnostics listed in the C standard. + Some of them are left out by default, since they trigger + frequently on harmless code. + + `-pedantic-errors' + Issue all the mandatory diagnostics, and make all mandatory + diagnostics into errors. This includes mandatory diagnostics that + GCC issues without `-pedantic' but treats as warnings. + + `-M' + Instead of outputting the result of preprocessing, output a rule + suitable for `make' describing the dependencies of the main source + file. The preprocessor outputs one `make' rule containing the + object file name for that source file, a colon, and the names of + all the included files, including those coming from `-include' or + `-imacros' command line options. + + Unless specified explicitly (with `-MT' or `-MQ'), the object file + name consists of the basename of the source file with any suffix + replaced with object file suffix. If there are many included + files then the rule is split into several lines using `\'-newline. + The rule has no commands. + + This option does not suppress the preprocessor's debug output, + such as `-dM'. To avoid mixing such debug output with the + dependency rules you should explicitly specify the dependency + output file with `-MF', or use an environment variable like + `DEPENDENCIES_OUTPUT' (*note DEPENDENCIES_OUTPUT::). Debug output + will still be sent to the regular output stream as normal. + + Passing `-M' to the driver implies `-E'. + + `-MM' + Like `-M' but do not mention header files that are found in system + header directories, nor header files that are included, directly + or indirectly, from such a header. + + This implies that the choice of angle brackets or double quotes in + an `#include' directive does not in itself determine whether that + header will appear in `-MM' dependency output. This is a slight + change in semantics from GCC versions 3.0 and earlier. + + `-MF FILE' + When used with `-M' or `-MM', specifies a file to write the + dependencies to. If no `-MF' switch is given the preprocessor + sends the rules to the same place it would have sent preprocessed + output. + + When used with the driver options `-MD' or `-MMD', `-MF' overrides + the default dependency output file. + + `-MG' + When used with `-M' or `-MM', `-MG' says to treat missing header + files as generated files and assume they live in the same + directory as the source file. It suppresses preprocessed output, + as a missing header file is ordinarily an error. + + This feature is used in automatic updating of makefiles. + + `-MP' + This option instructs CPP to add a phony target for each dependency + other than the main file, causing each to depend on nothing. These + dummy rules work around errors `make' gives if you remove header + files without updating the `Makefile' to match. + + This is typical output: + + test.o: test.c test.h + + test.h: + + `-MT TARGET' + Change the target of the rule emitted by dependency generation. By + default CPP takes the name of the main input file, including any + path, deletes any file suffix such as `.c', and appends the + platform's usual object suffix. The result is the target. + + An `-MT' option will set the target to be exactly the string you + specify. If you want multiple targets, you can specify them as a + single argument to `-MT', or use multiple `-MT' options. + + For example, `-MT '$(objpfx)foo.o'' might give + + $(objpfx)foo.o: foo.c + + `-MQ TARGET' + Same as `-MT', but it quotes any characters which are special to + Make. `-MQ '$(objpfx)foo.o'' gives + + $$(objpfx)foo.o: foo.c + + The default target is automatically quoted, as if it were given + with `-MQ'. + + `-MD' + `-MD' is equivalent to `-M -MF FILE', except that `-E' is not + implied. The driver determines FILE based on whether an `-o' + option is given. If it is, the driver uses its argument but with + a suffix of `.d', otherwise it take the basename of the input file + and applies a `.d' suffix. + + If `-MD' is used in conjunction with `-E', any `-o' switch is + understood to specify the dependency output file (but *note + -MF::), but if used without `-E', each `-o' is understood to + specify a target object file. + + Since `-E' is not implied, `-MD' can be used to generate a + dependency output file as a side-effect of the compilation process. + + `-MMD' + Like `-MD' except mention only user header files, not system + -header files. + + `-x c' + `-x c++' + `-x objective-c' + `-x assembler-with-cpp' + Specify the source language: C, C++, Objective-C, or assembly. + This has nothing to do with standards conformance or extensions; + it merely selects which base syntax to expect. If you give none + of these options, cpp will deduce the language from the extension + of the source file: `.c', `.cc', `.m', or `.S'. Some other common + extensions for C++ and assembly are also recognized. If cpp does + not recognize the extension, it will treat the file as C; this is + the most generic mode. + + *Note:* Previous versions of cpp accepted a `-lang' option which + selected both the language and the standards conformance level. + This option has been removed, because it conflicts with the `-l' + option. + + `-std=STANDARD' + `-ansi' + Specify the standard to which the code should conform. Currently + cpp only knows about the standards for C; other language standards + will be added in the future. + + STANDARD may be one of: + `iso9899:1990' + `c89' + The ISO C standard from 1990. `c89' is the customary + shorthand for this version of the standard. + + The `-ansi' option is equivalent to `-std=c89'. + + `iso9899:199409' + The 1990 C standard, as amended in 1994. + + `iso9899:1999' + `c99' + `iso9899:199x' + `c9x' + The revised ISO C standard, published in December 1999. + Before publication, this was known as C9X. + + `gnu89' + The 1990 C standard plus GNU extensions. This is the default. + + `gnu99' + `gnu9x' + The 1999 C standard plus GNU extensions. + + `-I-' + Split the include path. Any directories specified with `-I' + options before `-I-' are searched only for headers requested with + `#include "FILE"'; they are not searched for `#include '. + If additional directories are specified with `-I' options after + the `-I-', those directories are searched for all `#include' + directives. + + In addition, `-I-' inhibits the use of the directory of the current + file directory as the first search directory for `#include "FILE"'. + + `-nostdinc' + Do not search the standard system directories for header files. + Only the directories you have specified with `-I' options (and the + directory of the current file, if appropriate) are searched. + + `-nostdinc++' + Do not search for header files in the C++-specific standard + directories, but do still search the other standard directories. + (This option is used when building the C++ library.) + + `-include FILE' + Process FILE as if `#include "file"' appeared as the first line of + the primary source file. However, the first directory searched + for FILE is the preprocessor's working directory _instead of_ the + directory containing the main source file. If not found there, it + is searched for in the remainder of the `#include "..."' search + chain as normal. + + If multiple `-include' options are given, the files are included + in the order they appear on the command line. + + `-imacros FILE' + Exactly like `-include', except that any output produced by + scanning FILE is thrown away. Macros it defines remain defined. + This allows you to acquire all the macros from a header without + also processing its declarations. + + All files specified by `-imacros' are processed before all files + specified by `-include'. + + `-idirafter DIR' + Search DIR for header files, but do it _after_ all directories + specified with `-I' and the standard system directories have been + exhausted. DIR is treated as a system include directory. + + `-iprefix PREFIX' + Specify PREFIX as the prefix for subsequent `-iwithprefix' + options. If the prefix represents a directory, you should include + the final `/'. + + `-iwithprefix DIR' + `-iwithprefixbefore DIR' + Append DIR to the prefix specified previously with `-iprefix', and + add the resulting directory to the include search path. + `-iwithprefixbefore' puts it in the same place `-I' would; + `-iwithprefix' puts it where `-idirafter' would. + + Use of these options is discouraged. + + `-isystem DIR' + Search DIR for header files, after all directories specified by + `-I' but before the standard system directories. Mark it as a + system directory, so that it gets the same special treatment as is + applied to the standard system directories. + + `-fpreprocessed' + Indicate to the preprocessor that the input file has already been + preprocessed. This suppresses things like macro expansion, + trigraph conversion, escaped newline splicing, and processing of + most directives. The preprocessor still recognizes and removes + comments, so that you can pass a file preprocessed with `-C' to + the compiler without problems. In this mode the integrated + preprocessor is little more than a tokenizer for the front ends. + + `-fpreprocessed' is implicit if the input file has one of the + extensions `.i', `.ii' or `.mi'. These are the extensions that + GCC uses for preprocessed files created by `-save-temps'. + + `-ftabstop=WIDTH' + Set the distance between tab stops. This helps the preprocessor + report correct column numbers in warnings or errors, even if tabs + appear on the line. If the value is less than 1 or greater than + 100, the option is ignored. The default is 8. + + `-fno-show-column' + Do not print column numbers in diagnostics. This may be necessary + if diagnostics are being scanned by a program that does not + understand the column numbers, such as `dejagnu'. + + `-A PREDICATE=ANSWER' + Make an assertion with the predicate PREDICATE and answer ANSWER. + This form is preferred to the older form `-A PREDICATE(ANSWER)', + which is still supported, because it does not use shell special + characters. + + `-A -PREDICATE=ANSWER' + Cancel an assertion with the predicate PREDICATE and answer ANSWER. + + `-A-' + Cancel all predefined assertions and all assertions preceding it on + the command line. Also, undefine all predefined macros and all + macros preceding it on the command line. (This is a historical + wart and may change in the future.) + + `-dCHARS' + CHARS is a sequence of one or more of the following characters, + and must not be preceded by a space. Other characters are + interpreted by the compiler proper, or reserved for future + versions of GCC, and so are silently ignored. If you specify + characters whose behavior conflicts, the result is undefined. + + `M' + Instead of the normal output, generate a list of `#define' + directives for all the macros defined during the execution of + the preprocessor, including predefined macros. This gives + you a way of finding out what is predefined in your version + of the preprocessor. Assuming you have no file `foo.h', the + command + + touch foo.h; cpp -dM foo.h + + will show all the predefined macros. + + `D' + Like `M' except in two respects: it does _not_ include the + predefined macros, and it outputs _both_ the `#define' + directives and the result of preprocessing. Both kinds of + output go to the standard output file. + + `N' + Like `D', but emit only the macro names, not their expansions. + + `I' + Output `#include' directives in addition to the result of + preprocessing. + + `-P' + Inhibit generation of linemarkers in the output from the + preprocessor. This might be useful when running the preprocessor + on something that is not C code, and will be sent to a program + which might be confused by the linemarkers. + + `-C' + Do not discard comments. All comments are passed through to the + output file, except for comments in processed directives, which + are deleted along with the directive. + + You should be prepared for side effects when using `-C'; it causes + the preprocessor to treat comments as tokens in their own right. + For example, comments appearing at the start of what would be a + directive line have the effect of turning that line into an + ordinary source line, since the first token on the line is no + longer a `#'. + + `-gcc' + Define the macros __GNUC__, __GNUC_MINOR__ and + __GNUC_PATCHLEVEL__. These are defined automatically when you use + `gcc -E'; you can turn them off in that case with `-no-gcc'. + + `-traditional' + Try to imitate the behavior of old-fashioned C, as opposed to ISO + C. + + `-trigraphs' + Process trigraph sequences. These are three-character sequences, + all starting with `??', that are defined by ISO C to stand for + single characters. For example, `??/' stands for `\', so `'??/n'' + is a character constant for a newline. By default, GCC ignores + trigraphs, but in standard-conforming modes it converts them. See + the `-std' and `-ansi' options. + + The nine trigraphs and their replacements are + + Trigraph: ??( ??) ??< ??> ??= ??/ ??' ??! ??- + Replacement: [ ] { } # \ ^ | ~ + + `-remap' + Enable special code to work around file systems which only permit + very short file names, such as MS-DOS. + + `-$' + Forbid the use of `$' in identifiers. The C standard allows + implementations to define extra characters that can appear in + identifiers. By default GNU CPP permits `$', a common extension. + + `-h' + `--help' + `--target-help' + Print text describing all the command line options instead of + preprocessing anything. + + `-v' + Verbose mode. Print out GNU CPP's version number at the beginning + of execution, and report the final form of the include path. + + `-H' + Print the name of each header file used, in addition to other + normal activities. Each name is indented to show how deep in the + `#include' stack it is. + + `-version' + `--version' + Print out GNU CPP's version number. With one dash, proceed to + preprocess as normal. With two dashes, exit immediately. + +  + File: gcc.info, Node: Assembler Options, Next: Link Options, Prev: Preprocessor Options,