summaryrefslogtreecommitdiffstats
path: root/contrib
diff options
context:
space:
mode:
authorRalf Corsepius <ralf.corsepius@rtems.org>2009-10-15 16:43:24 +0000
committerRalf Corsepius <ralf.corsepius@rtems.org>2009-10-15 16:43:24 +0000
commit7be223ee7f2ec36cec5690cb2fd3f6ac58550552 (patch)
tree4aaaec87a84fdaeea93293ff3e15799634f4c334 /contrib
parentUpdate to gcc-4.4.2. (diff)
downloadrtems-7be223ee7f2ec36cec5690cb2fd3f6ac58550552.tar.bz2
New.
Diffstat (limited to 'contrib')
-rw-r--r--contrib/crossrpms/patches/gcc-core-4.4.2-rtems4.10-20091015.diff28448
1 files changed, 28448 insertions, 0 deletions
diff --git a/contrib/crossrpms/patches/gcc-core-4.4.2-rtems4.10-20091015.diff b/contrib/crossrpms/patches/gcc-core-4.4.2-rtems4.10-20091015.diff
new file mode 100644
index 0000000000..5bf09dc051
--- /dev/null
+++ b/contrib/crossrpms/patches/gcc-core-4.4.2-rtems4.10-20091015.diff
@@ -0,0 +1,28448 @@
+diff -Naur gcc-4.4.2.orig/configure gcc-4.4.2-rtems4.10-20091015/configure
+--- gcc-4.4.2.orig/configure 2009-04-25 06:10:29.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/configure 2009-10-15 18:36:00.000000000 +0200
+@@ -2267,6 +2267,7 @@
+ noconfigdirs="$noconfigdirs target-newlib target-libiberty target-libgloss ${libgcj} target-libmudflap"
+ ;;
+ *-*-rtems*)
++ skipdirs="$skipdirs target-libiberty"
+ noconfigdirs="$noconfigdirs target-libgloss ${libgcj}"
+ ;;
+ # The tpf target doesn't support gdb yet.
+@@ -6259,7 +6260,7 @@
+ # to it. This is right: we don't want to search that directory
+ # for binaries, but we want the header files in there, so add
+ # them explicitly.
+- FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -isystem $$r/$(HOST_SUBDIR)/gcc/include'
++ FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -isystem $$r/$(HOST_SUBDIR)/gcc/include -isystem $$r/$(HOST_SUBDIR)/gcc/include-fixed'
+
+ # Someone might think of using the pre-installed headers on
+ # Canadian crosses, in case the installed compiler is not fully
+diff -Naur gcc-4.4.2.orig/configure.ac gcc-4.4.2-rtems4.10-20091015/configure.ac
+--- gcc-4.4.2.orig/configure.ac 2009-04-25 06:10:29.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/configure.ac 2009-10-15 18:36:00.000000000 +0200
+@@ -502,6 +502,7 @@
+ noconfigdirs="$noconfigdirs target-newlib target-libiberty target-libgloss ${libgcj} target-libmudflap"
+ ;;
+ *-*-rtems*)
++ skipdirs="$skipdirs target-libiberty"
+ noconfigdirs="$noconfigdirs target-libgloss ${libgcj}"
+ ;;
+ # The tpf target doesn't support gdb yet.
+@@ -2560,7 +2561,7 @@
+ # to it. This is right: we don't want to search that directory
+ # for binaries, but we want the header files in there, so add
+ # them explicitly.
+- FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -isystem $$r/$(HOST_SUBDIR)/gcc/include'
++ FLAGS_FOR_TARGET=$FLAGS_FOR_TARGET' -isystem $$r/$(HOST_SUBDIR)/gcc/include -isystem $$r/$(HOST_SUBDIR)/gcc/include-fixed'
+
+ # Someone might think of using the pre-installed headers on
+ # Canadian crosses, in case the installed compiler is not fully
+diff -Naur gcc-4.4.2.orig/gcc/config/avr/t-rtems gcc-4.4.2-rtems4.10-20091015/gcc/config/avr/t-rtems
+--- gcc-4.4.2.orig/gcc/config/avr/t-rtems 2004-11-23 04:44:03.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/avr/t-rtems 2009-10-15 18:36:00.000000000 +0200
+@@ -1,3 +1,4 @@
+ # Multilibs for avr RTEMS targets.
+
+-# ATM, this is just a stub
++# RTEMS uses _exit from newlib
++LIB1ASMFUNCS := $(filter-out _exit,$(LIB1ASMFUNCS))
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/arithmetic.c gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/arithmetic.c
+--- gcc-4.4.2.orig/gcc/config/lm32/arithmetic.c 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/arithmetic.c 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,305 @@
++/* Fixed-point arithmetic for Lattice Mico32.
++ Contributed by Jon Beniston <jon@beniston.com>
++
++ Copyright (C) 2008 Free Software Foundation, Inc.
++
++ This file 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.
++
++ In addition to the permissions in the GNU General Public License, the
++ Free Software Foundation gives you unlimited permission to link the
++ compiled version of this file into combinations with other programs,
++ and to distribute those combinations without any restriction coming
++ from the use of this file. (The General Public License restrictions
++ do apply in other respects; for example, they cover modification of
++ the file, and distribution when not linked into a combine
++ executable.)
++
++ This file 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; see the file COPYING. If not, write to
++ the Free Software Foundation, 51 Franklin Street, Fifth Floor,
++ Boston, MA 02110-1301, USA. */
++
++typedef unsigned long UQItype __attribute__ ((mode (QI)));
++typedef long SItype __attribute__ ((mode (SI)));
++typedef unsigned long USItype __attribute__ ((mode (SI)));
++
++/* Prototypes */
++
++USItype __mulsi3 (USItype a, USItype b);
++
++USItype __udivmodsi4 (USItype num, USItype den, int modwanted);
++SItype __divsi3 (SItype a, SItype b);
++SItype __modsi3 (SItype a, SItype b);
++USItype __udivsi3 (USItype a, USItype b);
++USItype __umodsi3 (USItype a, USItype b);
++
++SItype __ashlsi3 (SItype a, SItype b);
++SItype __ashrsi3 (SItype a, SItype b);
++USItype __lshrsi3 (USItype a, USItype b);
++
++/* Multiplication */
++
++#ifdef L_mulsi3
++USItype
++__mulsi3 (USItype a, USItype b)
++{
++ USItype result;
++
++ result = 0;
++
++ if (a==0)
++ return 0;
++
++ while (b!=0)
++ {
++ if (b & 1)
++ result += a;
++ a <<= 1;
++ b >>= 1;
++ }
++
++ return result;
++}
++#endif
++
++/* Division */
++
++#ifdef L_udivmodsi4
++USItype
++__udivmodsi4 (USItype num, USItype den, int modwanted)
++{
++ USItype bit = 1;
++ USItype res = 0;
++
++ while (den < num && bit && !(den & (1L<<31)))
++ {
++ den <<=1;
++ bit <<=1;
++ }
++ while (bit)
++ {
++ if (num >= den)
++ {
++ num -= den;
++ res |= bit;
++ }
++ bit >>=1;
++ den >>=1;
++ }
++ if (modwanted)
++ return num;
++ return res;
++}
++#endif
++
++#ifdef L_divsi3
++
++static const UQItype __divsi3_table[] = {
++ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 2, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 3, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 4, 2, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 5, 2, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 6, 3, 2, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 7, 3, 2, 1, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0, 0,
++ 0, 8, 4, 2, 2, 1, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0,
++ 0, 9, 4, 3, 2, 1, 1, 1, 1, 1, 0, 0, 0, 0, 0, 0,
++ 0, 10, 5, 3, 2, 2, 1, 1, 1, 1, 1, 0, 0, 0, 0, 0,
++ 0, 11, 5, 3, 2, 2, 1, 1, 1, 1, 1, 1, 0, 0, 0, 0,
++ 0, 12, 6, 4, 3, 2, 2, 1, 1, 1, 1, 1, 1, 0, 0, 0,
++ 0, 13, 6, 4, 3, 2, 2, 1, 1, 1, 1, 1, 1, 1, 0, 0,
++ 0, 14, 7, 4, 3, 2, 2, 2, 1, 1, 1, 1, 1, 1, 1, 0,
++ 0, 15, 7, 5, 3, 3, 2, 2, 1, 1, 1, 1, 1, 1, 1, 1,
++};
++
++SItype
++__divsi3 (SItype a, SItype b)
++{
++ int neg = 0;
++ SItype res;
++ int cfg;
++
++ if (b == 0)
++ {
++ /* Raise divide by zero exception */
++ int eba;
++ __asm__ __volatile__ ("rcsr %0, EBA" : "=r" (eba));
++ eba += 32 * 5;
++ __asm__ __volatile__ ("mv ea, ra");
++ __asm__ __volatile__ ("b %0" : : "r" (eba));
++ }
++
++ if (((USItype)(a | b)) < 16)
++ {
++ res = __divsi3_table[(a << 4) + b];
++ }
++ else
++ {
++
++ if (a < 0)
++ {
++ a = -a;
++ neg = !neg;
++ }
++
++ if (b < 0)
++ {
++ b = -b;
++ neg = !neg;
++ }
++
++ __asm__ ("rcsr %0, CFG" : "=r" (cfg));
++ if (cfg & 2)
++ __asm__ ("divu %0, %1, %2" : "=r" (res) : "r" (a), "r" (b));
++ else
++ res = __udivmodsi4 (a, b, 0);
++
++ if (neg)
++ res = -res;
++ }
++
++ return res;
++}
++#endif
++
++#ifdef L_modsi3
++SItype
++__modsi3 (SItype a, SItype b)
++{
++ int neg = 0;
++ SItype res;
++ int cfg;
++
++ if (b == 0)
++ {
++ /* Raise divide by zero exception */
++ int eba, sr;
++ /* Save interrupt enable */
++ __asm__ __volatile__ ("rcsr %0, IE" : "=r" (sr));
++ sr = (sr & 1) << 1;
++ __asm__ __volatile__ ("wcsr IE, %0" : : "r" (sr));
++ /* Branch to exception handler */
++ __asm__ __volatile__ ("rcsr %0, EBA" : "=r" (eba));
++ eba += 32 * 5;
++ __asm__ __volatile__ ("mv ea, ra");
++ __asm__ __volatile__ ("b %0" : : "r" (eba));
++ }
++
++ if (a < 0)
++ {
++ a = -a;
++ neg = 1;
++ }
++
++ if (b < 0)
++ b = -b;
++
++ __asm__ ("rcsr %0, CFG" : "=r" (cfg));
++ if (cfg & 2)
++ __asm__ ("modu %0, %1, %2" : "=r" (res) : "r" (a), "r" (b));
++ else
++ res = __udivmodsi4 (a, b, 1);
++
++ if (neg)
++ res = -res;
++
++ return res;
++}
++#endif
++
++#ifdef L_udivsi3
++USItype
++__udivsi3 (USItype a, USItype b)
++{
++ if (b == 0)
++ {
++ /* Raise divide by zero exception */
++ int eba, sr;
++ /* Save interrupt enable */
++ __asm__ __volatile__ ("rcsr %0, IE" : "=r" (sr));
++ sr = (sr & 1) << 1;
++ __asm__ __volatile__ ("wcsr IE, %0" : : "r" (sr));
++ /* Branch to exception handler */
++ __asm__ __volatile__ ("rcsr %0, EBA" : "=r" (eba));
++ eba += 32 * 5;
++ __asm__ __volatile__ ("mv ea, ra");
++ __asm__ __volatile__ ("b %0" : : "r" (eba));
++ }
++
++ return __udivmodsi4 (a, b, 0);
++}
++#endif
++
++#ifdef L_umodsi3
++USItype
++__umodsi3 (USItype a, USItype b)
++{
++ if (b == 0)
++ {
++ /* Raise divide by zero exception */
++ int eba, sr;
++ /* Save interrupt enable */
++ __asm__ __volatile__ ("rcsr %0, IE" : "=r" (sr));
++ sr = (sr & 1) << 1;
++ __asm__ __volatile__ ("wcsr IE, %0" : : "r" (sr));
++ /* Branch to exception handler */
++ __asm__ __volatile__ ("rcsr %0, EBA" : "=r" (eba));
++ eba += 32 * 5;
++ __asm__ __volatile__ ("mv ea, ra");
++ __asm__ __volatile__ ("b %0" : : "r" (eba));
++ }
++
++ return __udivmodsi4 (a, b, 1);
++}
++#endif
++
++#if 0
++
++/* Shifts - Optimized versions implemented in assembly. Use these if code space is preferred to performance. */
++
++#ifdef L_ashlsi3
++SItype
++__ashlsi3 (SItype a, SItype b)
++{
++ int i;
++
++ for (i = (b & 0x1f); i > 0; --i)
++ a += a;
++ return a;
++}
++#endif
++
++#ifdef L_ashrsi3
++SItype
++__ashrsi3 (SItype a, SItype b)
++{
++ int i;
++
++ for (i = (b & 0x1f); i > 0; --i)
++ __asm__ ("sri %0, %0, 1" : "=r" (a) : "0" (a));
++ return a;
++}
++#endif
++
++#ifdef L_lshrsi3
++USItype
++__lshrsi3 (USItype a, USItype b)
++{
++ int i;
++
++ for (i = (b & 0x1f); i > 0; --i)
++ __asm__ ("srui %0, %0, 1" : "=r" (a) : "0" (a));
++ return a;
++}
++#endif
++
++#endif
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/crti.S gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/crti.S
+--- gcc-4.4.2.orig/gcc/config/lm32/crti.S 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/crti.S 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,45 @@
++# crti.S for Lattice Mico32
++# Contributed by Jon Beniston <jon@beniston.com>
++#
++# Copyright (C) 2008 Free Software Foundation, Inc.
++#
++# This file 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.
++#
++# In addition to the permissions in the GNU General Public License, the
++# Free Software Foundation gives you unlimited permission to link the
++# compiled version of this file into combinations with other programs,
++# and to distribute those combinations without any restriction coming
++# from the use of this file. (The General Public License restrictions
++# do apply in other respects; for example, they cover modification of
++# the file, and distribution when not linked into a combine
++# executable.)
++#
++# This file 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; see the file COPYING. If not, write to
++# the Free Software Foundation, 51 Franklin Street, Fifth Floor,
++# Boston, MA 02110-1301, USA.
++#
++
++ .section .init
++ .global _init
++ .type _init,@function
++ .align 4
++_init:
++ addi sp, sp, -4
++ sw (sp+4), ra
++
++ .section .fini
++ .global _fini
++ .type _fini,@function
++ .align 4
++_fini:
++ addi sp, sp, -4
++ sw (sp+4), ra
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/crtn.S gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/crtn.S
+--- gcc-4.4.2.orig/gcc/config/lm32/crtn.S 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/crtn.S 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,42 @@
++# crtn.S for Lattice Mico32
++# Contributed by Jon Beniston <jon@beniston.com>
++#
++# Copyright (C) 2008 Free Software Foundation, Inc.
++#
++# This file 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.
++#
++# In addition to the permissions in the GNU General Public License, the
++# Free Software Foundation gives you unlimited permission to link the
++# compiled version of this file into combinations with other programs,
++# and to distribute those combinations without any restriction coming
++# from the use of this file. (The General Public License restrictions
++# do apply in other respects; for example, they cover modification of
++# the file, and distribution when not linked into a combine
++# executable.)
++#
++# This file 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; see the file COPYING. If not, write to
++# the Free Software Foundation, 51 Franklin Street, Fifth Floor,
++# Boston, MA 02110-1301, USA.
++#
++
++ .section .init
++
++ lw ra, (sp+4)
++ addi sp, sp, 4
++ ret
++
++ .section .fini
++
++ lw ra, (sp+4)
++ addi sp, sp, 4
++ ret
++
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lib1funcs.S gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lib1funcs.S
+--- gcc-4.4.2.orig/gcc/config/lm32/lib1funcs.S 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lib1funcs.S 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,429 @@
++# lib1funcs.S for Lattice Mico32
++# Contributed by Jon Beniston <jon@beniston.com>
++#
++# Copyright (C) 2008 Free Software Foundation, Inc.
++#
++# This file 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.
++#
++# In addition to the permissions in the GNU General Public License, the
++# Free Software Foundation gives you unlimited permission to link the
++# compiled version of this file into combinations with other programs,
++# and to distribute those combinations without any restriction coming
++# from the use of this file. (The General Public License restrictions
++# do apply in other respects; for example, they cover modification of
++# the file, and distribution when not linked into a combine
++# executable.)
++#
++# This file 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; see the file COPYING. If not, write to
++# the Free Software Foundation, 51 Franklin Street, Fifth Floor,
++# Boston, MA 02110-1301, USA.
++#
++
++/* Arithmetic left shift */
++
++ .text
++
++ .global __ashlsi3
++ .type __ashlsi3,@function
++ .align 4
++
++__ashlsi3:
++ /* Only use 5 LSBs, as that's all the h/w shifter uses */
++ andi r2, r2, 0x1f
++ /* Get address of offset into unrolled shift loop to jump to */
++#ifdef __PIC__
++ orhi r3, r0, gotoffhi16(__ashlsi3_table)
++ addi r3, r3, gotofflo16(__ashlsi3_table)
++ add r3, r3, gp
++#else
++ mvhi r3, hi(__ashlsi3_table)
++ ori r3, r3, lo(__ashlsi3_table)
++#endif
++ add r2, r2, r2
++ add r2, r2, r2
++ add r3, r3, r2
++ lw r3, (r3+0)
++ b r3
++
++__ashlsi3_31:
++ add r1, r1, r1
++__ashlsi3_30:
++ add r1, r1, r1
++__ashlsi3_29:
++ add r1, r1, r1
++__ashlsi3_28:
++ add r1, r1, r1
++__ashlsi3_27:
++ add r1, r1, r1
++__ashlsi3_26:
++ add r1, r1, r1
++__ashlsi3_25:
++ add r1, r1, r1
++__ashlsi3_24:
++ add r1, r1, r1
++__ashlsi3_23:
++ add r1, r1, r1
++__ashlsi3_22:
++ add r1, r1, r1
++__ashlsi3_21:
++ add r1, r1, r1
++__ashlsi3_20:
++ add r1, r1, r1
++__ashlsi3_19:
++ add r1, r1, r1
++__ashlsi3_18:
++ add r1, r1, r1
++__ashlsi3_17:
++ add r1, r1, r1
++__ashlsi3_16:
++ add r1, r1, r1
++__ashlsi3_15:
++ add r1, r1, r1
++__ashlsi3_14:
++ add r1, r1, r1
++__ashlsi3_13:
++ add r1, r1, r1
++__ashlsi3_12:
++ add r1, r1, r1
++__ashlsi3_11:
++ add r1, r1, r1
++__ashlsi3_10:
++ add r1, r1, r1
++__ashlsi3_9:
++ add r1, r1, r1
++__ashlsi3_8:
++ add r1, r1, r1
++__ashlsi3_7:
++ add r1, r1, r1
++__ashlsi3_6:
++ add r1, r1, r1
++__ashlsi3_5:
++ add r1, r1, r1
++__ashlsi3_4:
++ add r1, r1, r1
++__ashlsi3_3:
++ add r1, r1, r1
++__ashlsi3_2:
++ add r1, r1, r1
++__ashlsi3_1:
++ add r1, r1, r1
++__ashlsi3_0:
++ ret
++
++#ifdef __PIC__
++ .section .data
++#else
++ .section .rodata
++#endif
++
++ .align 4
++
++__ashlsi3_table:
++ .word __ashlsi3_0
++ .word __ashlsi3_1
++ .word __ashlsi3_2
++ .word __ashlsi3_3
++ .word __ashlsi3_4
++ .word __ashlsi3_5
++ .word __ashlsi3_6
++ .word __ashlsi3_7
++ .word __ashlsi3_8
++ .word __ashlsi3_9
++ .word __ashlsi3_10
++ .word __ashlsi3_11
++ .word __ashlsi3_12
++ .word __ashlsi3_13
++ .word __ashlsi3_14
++ .word __ashlsi3_15
++ .word __ashlsi3_16
++ .word __ashlsi3_17
++ .word __ashlsi3_18
++ .word __ashlsi3_19
++ .word __ashlsi3_20
++ .word __ashlsi3_21
++ .word __ashlsi3_22
++ .word __ashlsi3_23
++ .word __ashlsi3_24
++ .word __ashlsi3_25
++ .word __ashlsi3_26
++ .word __ashlsi3_27
++ .word __ashlsi3_28
++ .word __ashlsi3_29
++ .word __ashlsi3_30
++ .word __ashlsi3_31
++
++/* Logical right shift */
++
++ .text
++
++ .global __lshrsi3
++ .type __lshrsi3,@function
++ .align 4
++
++__lshrsi3:
++ /* Only use 5 LSBs, as that's all the h/w shifter uses */
++ andi r2, r2, 0x1f
++ /* Get address of offset into unrolled shift loop to jump to */
++#ifdef __PIC__
++ orhi r3, r0, gotoffhi16(__lshrsi3_table)
++ addi r3, r3, gotofflo16(__lshrsi3_table)
++ add r3, r3, gp
++#else
++ mvhi r3, hi(__lshrsi3_table)
++ ori r3, r3, lo(__lshrsi3_table)
++#endif
++ add r2, r2, r2
++ add r2, r2, r2
++ add r3, r3, r2
++ lw r3, (r3+0)
++ b r3
++
++__lshrsi3_31:
++ srui r1, r1, 1
++__lshrsi3_30:
++ srui r1, r1, 1
++__lshrsi3_29:
++ srui r1, r1, 1
++__lshrsi3_28:
++ srui r1, r1, 1
++__lshrsi3_27:
++ srui r1, r1, 1
++__lshrsi3_26:
++ srui r1, r1, 1
++__lshrsi3_25:
++ srui r1, r1, 1
++__lshrsi3_24:
++ srui r1, r1, 1
++__lshrsi3_23:
++ srui r1, r1, 1
++__lshrsi3_22:
++ srui r1, r1, 1
++__lshrsi3_21:
++ srui r1, r1, 1
++__lshrsi3_20:
++ srui r1, r1, 1
++__lshrsi3_19:
++ srui r1, r1, 1
++__lshrsi3_18:
++ srui r1, r1, 1
++__lshrsi3_17:
++ srui r1, r1, 1
++__lshrsi3_16:
++ srui r1, r1, 1
++__lshrsi3_15:
++ srui r1, r1, 1
++__lshrsi3_14:
++ srui r1, r1, 1
++__lshrsi3_13:
++ srui r1, r1, 1
++__lshrsi3_12:
++ srui r1, r1, 1
++__lshrsi3_11:
++ srui r1, r1, 1
++__lshrsi3_10:
++ srui r1, r1, 1
++__lshrsi3_9:
++ srui r1, r1, 1
++__lshrsi3_8:
++ srui r1, r1, 1
++__lshrsi3_7:
++ srui r1, r1, 1
++__lshrsi3_6:
++ srui r1, r1, 1
++__lshrsi3_5:
++ srui r1, r1, 1
++__lshrsi3_4:
++ srui r1, r1, 1
++__lshrsi3_3:
++ srui r1, r1, 1
++__lshrsi3_2:
++ srui r1, r1, 1
++__lshrsi3_1:
++ srui r1, r1, 1
++__lshrsi3_0:
++ ret
++
++#ifdef __PIC__
++ .section .data
++#else
++ .section .rodata
++#endif
++
++ .align 4
++
++__lshrsi3_table:
++ .word __lshrsi3_0
++ .word __lshrsi3_1
++ .word __lshrsi3_2
++ .word __lshrsi3_3
++ .word __lshrsi3_4
++ .word __lshrsi3_5
++ .word __lshrsi3_6
++ .word __lshrsi3_7
++ .word __lshrsi3_8
++ .word __lshrsi3_9
++ .word __lshrsi3_10
++ .word __lshrsi3_11
++ .word __lshrsi3_12
++ .word __lshrsi3_13
++ .word __lshrsi3_14
++ .word __lshrsi3_15
++ .word __lshrsi3_16
++ .word __lshrsi3_17
++ .word __lshrsi3_18
++ .word __lshrsi3_19
++ .word __lshrsi3_20
++ .word __lshrsi3_21
++ .word __lshrsi3_22
++ .word __lshrsi3_23
++ .word __lshrsi3_24
++ .word __lshrsi3_25
++ .word __lshrsi3_26
++ .word __lshrsi3_27
++ .word __lshrsi3_28
++ .word __lshrsi3_29
++ .word __lshrsi3_30
++ .word __lshrsi3_31
++
++/* Arithmetic right shift */
++
++ .text
++
++ .global __ashrsi3
++ .type __ashrsi3,@function
++ .align 4
++
++__ashrsi3:
++ /* Only use 5 LSBs, as that's all the h/w shifter uses */
++ andi r2, r2, 0x1f
++ /* Get address of offset into unrolled shift loop to jump to */
++#ifdef __PIC__
++ orhi r3, r0, gotoffhi16(__ashrsi3_table)
++ addi r3, r3, gotofflo16(__ashrsi3_table)
++ add r3, r3, gp
++#else
++ mvhi r3, hi(__ashrsi3_table)
++ ori r3, r3, lo(__ashrsi3_table)
++#endif
++ add r2, r2, r2
++ add r2, r2, r2
++ add r3, r3, r2
++ lw r3, (r3+0)
++ b r3
++
++__ashrsi3_31:
++ sri r1, r1, 1
++__ashrsi3_30:
++ sri r1, r1, 1
++__ashrsi3_29:
++ sri r1, r1, 1
++__ashrsi3_28:
++ sri r1, r1, 1
++__ashrsi3_27:
++ sri r1, r1, 1
++__ashrsi3_26:
++ sri r1, r1, 1
++__ashrsi3_25:
++ sri r1, r1, 1
++__ashrsi3_24:
++ sri r1, r1, 1
++__ashrsi3_23:
++ sri r1, r1, 1
++__ashrsi3_22:
++ sri r1, r1, 1
++__ashrsi3_21:
++ sri r1, r1, 1
++__ashrsi3_20:
++ sri r1, r1, 1
++__ashrsi3_19:
++ sri r1, r1, 1
++__ashrsi3_18:
++ sri r1, r1, 1
++__ashrsi3_17:
++ sri r1, r1, 1
++__ashrsi3_16:
++ sri r1, r1, 1
++__ashrsi3_15:
++ sri r1, r1, 1
++__ashrsi3_14:
++ sri r1, r1, 1
++__ashrsi3_13:
++ sri r1, r1, 1
++__ashrsi3_12:
++ sri r1, r1, 1
++__ashrsi3_11:
++ sri r1, r1, 1
++__ashrsi3_10:
++ sri r1, r1, 1
++__ashrsi3_9:
++ sri r1, r1, 1
++__ashrsi3_8:
++ sri r1, r1, 1
++__ashrsi3_7:
++ sri r1, r1, 1
++__ashrsi3_6:
++ sri r1, r1, 1
++__ashrsi3_5:
++ sri r1, r1, 1
++__ashrsi3_4:
++ sri r1, r1, 1
++__ashrsi3_3:
++ sri r1, r1, 1
++__ashrsi3_2:
++ sri r1, r1, 1
++__ashrsi3_1:
++ sri r1, r1, 1
++__ashrsi3_0:
++ ret
++
++#ifdef __PIC__
++ .section .data
++#else
++ .section .rodata
++#endif
++
++ .align 4
++
++__ashrsi3_table:
++ .word __ashrsi3_0
++ .word __ashrsi3_1
++ .word __ashrsi3_2
++ .word __ashrsi3_3
++ .word __ashrsi3_4
++ .word __ashrsi3_5
++ .word __ashrsi3_6
++ .word __ashrsi3_7
++ .word __ashrsi3_8
++ .word __ashrsi3_9
++ .word __ashrsi3_10
++ .word __ashrsi3_11
++ .word __ashrsi3_12
++ .word __ashrsi3_13
++ .word __ashrsi3_14
++ .word __ashrsi3_15
++ .word __ashrsi3_16
++ .word __ashrsi3_17
++ .word __ashrsi3_18
++ .word __ashrsi3_19
++ .word __ashrsi3_20
++ .word __ashrsi3_21
++ .word __ashrsi3_22
++ .word __ashrsi3_23
++ .word __ashrsi3_24
++ .word __ashrsi3_25
++ .word __ashrsi3_26
++ .word __ashrsi3_27
++ .word __ashrsi3_28
++ .word __ashrsi3_29
++ .word __ashrsi3_30
++ .word __ashrsi3_31
++
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lm32.c gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.c
+--- gcc-4.4.2.orig/gcc/config/lm32/lm32.c 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.c 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,869 @@
++/* Subroutines used for code generation on the Lattice Mico32 architecture.
++ Contributed by Jon Beniston <jon@beniston.com>
++
++ Copyright (C) 2008 Free Software Foundation, Inc.
++
++ This file is part of GCC.
++
++ GCC 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 3, or (at your
++ option) any later version.
++
++ GCC 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 GCC; see the file COPYING3. If not see
++ <http://www.gnu.org/licenses/>. */
++
++#include "config.h"
++#include "system.h"
++#include "coretypes.h"
++#include "tm.h"
++#include "rtl.h"
++#include "regs.h"
++#include "hard-reg-set.h"
++#include "basic-block.h"
++#include "real.h"
++#include "insn-config.h"
++#include "conditions.h"
++#include "insn-flags.h"
++#include "insn-attr.h"
++#include "insn-codes.h"
++#include "recog.h"
++#include "output.h"
++#include "tree.h"
++#include "expr.h"
++#include "flags.h"
++#include "reload.h"
++#include "tm_p.h"
++#include "function.h"
++#include "toplev.h"
++#include "optabs.h"
++#include "libfuncs.h"
++#include "ggc.h"
++#include "target.h"
++#include "target-def.h"
++#include "langhooks.h"
++#include "tm-constrs.h"
++#include "df.h"
++
++struct lm32_frame_info
++{
++ HOST_WIDE_INT total_size; /* number of bytes that the entire frame takes up. */
++ HOST_WIDE_INT callee_size; /* number of bytes to save callee save registers */
++ HOST_WIDE_INT pretend_size; /* number of bytes we push and pretend caller did. */
++ HOST_WIDE_INT args_size; /* number of bytes that outgoing arguments take up. */
++ HOST_WIDE_INT locals_size; /* number of bytes that local variables take up. */
++ unsigned int reg_save_mask; /* mask of saved registers. */
++};
++
++/* Prototypes for static functions */
++static rtx emit_add (rtx dest, rtx src0, rtx src1);
++static void expand_save_restore (struct lm32_frame_info *info, int op);
++static void abort_with_insn (rtx insn, const char *reason);
++static void stack_adjust (HOST_WIDE_INT amount);
++static bool lm32_in_small_data_p (const_tree);
++static void lm32_setup_incoming_varargs (CUMULATIVE_ARGS *cum, enum machine_mode mode,
++ tree type, int *pretend_size, int no_rtl);
++
++/* Detemines if given constant can be used as a displacement */
++#define OFFSET_INT(X) (((X) > -32768) && ((X) < 32768))
++
++#undef TARGET_ADDRESS_COST
++#define TARGET_ADDRESS_COST hook_int_rtx_bool_0
++#undef TARGET_IN_SMALL_DATA_P
++#define TARGET_IN_SMALL_DATA_P lm32_in_small_data_p
++#undef TARGET_PROMOTE_FUNCTION_ARGS
++#define TARGET_PROMOTE_FUNCTION_ARGS hook_bool_const_tree_true
++#undef TARGET_PROMOTE_FUNCTION_RETURN
++#define TARGET_PROMOTE_FUNCTION_RETURN hook_bool_const_tree_true
++#undef TARGET_SETUP_INCOMING_VARARGS
++#define TARGET_SETUP_INCOMING_VARARGS lm32_setup_incoming_varargs
++#undef TARGET_PROMOTE_PROTOTYPES
++#define TARGET_PROMOTE_PROTOTYPES hook_bool_const_tree_true
++
++struct gcc_target targetm = TARGET_INITIALIZER;
++
++/* Current frame information calculated by lm32_compute_frame_size. */
++static struct lm32_frame_info current_frame_info;
++
++rtx lm32_compare_op0;
++rtx lm32_compare_op1;
++
++/* Return non-zero if the specified return type should be returned in memory */
++int
++lm32_return_in_memory (tree type)
++{
++ HOST_WIDE_INT size;
++
++ if (!AGGREGATE_TYPE_P (type))
++ {
++ /* All simple types are returned in registers. */
++ return 0;
++ }
++
++ size = int_size_in_bytes (type);
++ if (size >=0 && size <= UNITS_PER_WORD)
++ {
++ /* If it can fit in one register */
++ return 0;
++ }
++
++ return 1;
++}
++
++/* Determine if given constant can be used as a register displacement */
++int
++const_ok_for_base_offset (rtx op, enum machine_mode mode ATTRIBUTE_UNUSED)
++{
++ int val;
++
++ val = INTVAL (op);
++ return OFFSET_INT (val);
++}
++
++/* Generate an emit a word sized add instruction */
++static rtx
++emit_add (rtx dest, rtx src0, rtx src1)
++{
++ rtx insn;
++ insn = emit_insn (gen_addsi3 (dest, src0, src1));
++ return insn;
++}
++
++/* Generate the code to compare (and possibly branch) two integer values
++ TEST_CODE is the comparison code we are trying to emulate
++ (or implement directly)
++ RESULT is where to store the result of the comparison,
++ or null to emit a branch
++ CMP0 CMP1 are the two comparison operands
++ DESTINATION is the destination of the branch, or null to only compare
++ */
++
++void
++gen_int_relational (enum rtx_code code, /* relational test (EQ, etc) */
++ rtx result, /* result to store comp. or 0 if branch */
++ rtx cmp0, /* first operand to compare */
++ rtx cmp1, /* second operand to compare */
++ rtx destination) /* destination of the branch, or 0 if compare */
++{
++ enum machine_mode mode;
++ int branch_p;
++
++ mode = GET_MODE (cmp0);
++ if (mode == VOIDmode)
++ mode = GET_MODE (cmp1);
++
++ /* Is this a branch or compare */
++ branch_p = (destination != 0);
++
++ /* Instruction set doesn't support LE or LT, so swap operands and use GE, GT */
++ switch (code)
++ {
++ case LE:
++ case LT:
++ case LEU:
++ case LTU:
++ code = swap_condition (code);
++ rtx temp = cmp0;
++ cmp0 = cmp1;
++ cmp1 = temp;
++ break;
++ default:
++ break;
++ }
++
++ if (branch_p)
++ {
++ rtx insn;
++
++ /* Operands must be in registers */
++ if (!register_operand (cmp0, mode))
++ cmp0 = force_reg (mode, cmp0);
++ if (!register_operand (cmp1, mode))
++ cmp1 = force_reg (mode, cmp1);
++
++ /* Generate conditional branch instruction */
++ rtx cond = gen_rtx_fmt_ee (code, mode, cmp0, cmp1);
++ rtx label = gen_rtx_LABEL_REF (VOIDmode, destination);
++ insn = gen_rtx_SET (VOIDmode, pc_rtx,
++ gen_rtx_IF_THEN_ELSE (VOIDmode,
++ cond, label, pc_rtx));
++ emit_jump_insn (insn);
++ }
++ else
++ {
++ /* We can't have const_ints in cmp0, other than 0 */
++ if ((GET_CODE (cmp0) == CONST_INT) && (INTVAL (cmp0) != 0))
++ cmp0 = force_reg (mode, cmp0);
++
++ /* If the comparison is against an int not in legal range
++ move it into a register */
++ if (GET_CODE (cmp1) == CONST_INT)
++ {
++ HOST_WIDE_INT value = INTVAL (cmp1);
++ switch (code)
++ {
++ case EQ: case NE: case LE: case LT: case GE: case GT:
++ if (!MEDIUM_INT(value))
++ cmp1 = force_reg (mode, cmp1);
++ break;
++ case LEU: case LTU: case GEU: case GTU:
++ if (!MEDIUM_UINT(value))
++ cmp1 = force_reg (mode, cmp1);
++ break;
++ default:
++ abort ();
++ }
++ }
++
++ /* Generate compare instruction */
++ emit_move_insn (result, gen_rtx_fmt_ee (code, mode, cmp0, cmp1));
++ }
++}
++
++/* Generate and emit RTL to save or restore callee save registers */
++static void
++expand_save_restore (struct lm32_frame_info *info, int op)
++{
++ unsigned int reg_save_mask = info->reg_save_mask;
++ int regno;
++ HOST_WIDE_INT offset;
++ rtx insn;
++
++ /* Callee saves are below locals and above outgoing arguments */
++ offset = info->args_size + info->callee_size;
++ for (regno = 0; regno <= 31; regno++)
++ {
++ if ((reg_save_mask & (1 << regno)) != 0)
++ {
++ if (op == 0)
++ {
++ insn = emit_move_insn (gen_rtx_MEM (word_mode,
++ gen_rtx_PLUS (Pmode,
++ stack_pointer_rtx,
++ GEN_INT (offset))),
++ gen_rtx_REG (word_mode, regno));
++ }
++ else
++ {
++ insn = emit_move_insn (gen_rtx_REG (word_mode, regno),
++ gen_rtx_MEM (word_mode,
++ gen_rtx_PLUS (Pmode,
++ stack_pointer_rtx,
++ GEN_INT (offset))));
++ }
++
++ /* only prologue instructions which set the sp fp or save a
++ register should be marked as frame related */
++ if (op==0)
++ RTX_FRAME_RELATED_P (insn) = 1;
++ offset -= UNITS_PER_WORD;
++ }
++ }
++}
++
++static void
++stack_adjust (HOST_WIDE_INT amount)
++{
++ rtx insn;
++
++ if (!MEDIUM_INT (amount))
++ {
++ /* r10 is caller saved so it can be used as a temp reg */
++ rtx r10;
++ r10 = gen_rtx_REG (word_mode, 10);
++ insn = emit_move_insn (r10, GEN_INT (amount));
++ if (amount < 0)
++ RTX_FRAME_RELATED_P (insn) = 1;
++ insn = emit_add (stack_pointer_rtx, stack_pointer_rtx, r10);
++ if (amount < 0)
++ RTX_FRAME_RELATED_P (insn) = 1;
++ }
++ else
++ {
++ insn = emit_add (stack_pointer_rtx,
++ stack_pointer_rtx,
++ GEN_INT (amount));
++ if (amount < 0)
++ RTX_FRAME_RELATED_P (insn) = 1;
++ }
++}
++
++
++/* Create and emit instructions for a functions prologue */
++void
++lm32_expand_prologue (void)
++{
++ rtx insn;
++
++ lm32_compute_frame_size (get_frame_size ());
++
++ if (current_frame_info.total_size > 0)
++ {
++ /* Add space on stack new frame */
++ stack_adjust (-current_frame_info.total_size);
++
++ /* Save callee save registers */
++ if (current_frame_info.reg_save_mask != 0)
++ expand_save_restore (&current_frame_info, 0);
++
++ /* Setup frame pointer if it's needed */
++ if (frame_pointer_needed == 1)
++ {
++ /* Load offset - Don't use total_size, as that includes pretend_size, which isn't part of this frame? */
++ insn = emit_move_insn (frame_pointer_rtx, GEN_INT ( current_frame_info.args_size
++ + current_frame_info.callee_size
++ + current_frame_info.locals_size));
++ RTX_FRAME_RELATED_P (insn) = 1;
++
++ /* Add in sp */
++ insn = emit_add (frame_pointer_rtx,
++ frame_pointer_rtx,
++ stack_pointer_rtx);
++ RTX_FRAME_RELATED_P (insn) = 1;
++ }
++
++ /* Prevent prologue from being scheduled into function body */
++ emit_insn (gen_blockage ());
++ }
++}
++
++/* Create an emit instructions for a functions epilogue */
++void
++lm32_expand_epilogue (void)
++{
++ rtx ra_rtx = gen_rtx_REG (Pmode, RA_REGNUM);
++
++ lm32_compute_frame_size (get_frame_size ());
++
++ if (current_frame_info.total_size > 0)
++ {
++ /* Prevent stack code from being reordered */
++ emit_insn (gen_blockage ());
++
++ /* Restore callee save registers */
++ if (current_frame_info.reg_save_mask != 0)
++ expand_save_restore (&current_frame_info, 1);
++
++ /* Deallocate stack */
++ stack_adjust (current_frame_info.total_size);
++
++ /* Return to calling function */
++ emit_jump_insn (gen_return_internalsi (ra_rtx));
++ }
++ else
++ {
++ /* Return to calling function */
++ emit_jump_insn (gen_return_internalsi (ra_rtx));
++ }
++}
++
++/* Return the bytes needed to compute the frame pointer from the current
++ stack pointer. */
++HOST_WIDE_INT
++lm32_compute_frame_size (int size)
++{
++ int regno;
++ HOST_WIDE_INT total_size, locals_size, args_size, pretend_size, callee_size;
++ unsigned int reg_save_mask;
++
++ locals_size = size;
++ args_size = crtl->outgoing_args_size;
++ pretend_size = crtl->args.pretend_args_size;
++ callee_size = 0;
++ reg_save_mask = 0;
++
++ /* Build mask that actually determines which regsiters we save
++ and calculate size required to store them in the stack. */
++ for (regno = 1; regno < SP_REGNUM; regno++)
++ {
++ if (df_regs_ever_live_p(regno) && !call_used_regs[regno])
++ {
++ reg_save_mask |= 1 << regno;
++ callee_size += UNITS_PER_WORD;
++ }
++ }
++ if (df_regs_ever_live_p(RA_REGNUM) || !current_function_is_leaf || !optimize)
++ {
++ reg_save_mask |= 1 << RA_REGNUM;
++ callee_size += UNITS_PER_WORD;
++ }
++ if (!(reg_save_mask & (1 << FP_REGNUM)) && frame_pointer_needed)
++ {
++ reg_save_mask |= 1 << FP_REGNUM;
++ callee_size += UNITS_PER_WORD;
++ }
++
++ /* Compute total frame size */
++ total_size = pretend_size + args_size + locals_size + callee_size;
++
++ /* Align frame to appropriate boundary */
++ total_size = (total_size+3) & ~3;
++
++ /* Save computed information. */
++ current_frame_info.total_size = total_size;
++ current_frame_info.callee_size = callee_size;
++ current_frame_info.pretend_size = pretend_size;
++ current_frame_info.locals_size = locals_size;
++ current_frame_info.args_size = args_size;
++ current_frame_info.reg_save_mask = reg_save_mask;
++
++ return total_size;
++}
++
++void
++lm32_print_operand (FILE *file, rtx op, int letter)
++{
++ register enum rtx_code code;
++
++ if (! op)
++ {
++ error ("PRINT_OPERAND null pointer");
++ abort ();
++ }
++
++ code = GET_CODE (op);
++
++ if (code == SIGN_EXTEND)
++ op = XEXP (op, 0), code = GET_CODE (op);
++ else if (code == REG || code == SUBREG)
++ {
++ int regnum;
++
++ if (code == REG)
++ regnum = REGNO (op);
++ else
++ regnum = true_regnum (op);
++
++ if ( (letter == 'H' && !WORDS_BIG_ENDIAN)
++ || (letter == 'L' && WORDS_BIG_ENDIAN))
++ {
++ abort();
++ regnum++;
++ }
++
++ fprintf (file, "%s", reg_names[regnum]);
++ }
++ else if (code == MEM)
++ output_address (XEXP (op, 0));
++ else if (letter == 'z' && GET_CODE (op) == CONST_INT && INTVAL (op) == 0)
++ fprintf (file, "%s", reg_names[0]);
++ else if (GET_CODE (op) == CONST_DOUBLE)
++ {
++ if ((CONST_DOUBLE_LOW (op) != 0) || (CONST_DOUBLE_HIGH (op) != 0))
++ output_operand_lossage ("Only 0.0 can be loaded as an immediate");
++ else
++ fprintf (file, "0");
++ }
++ else if (code == EQ)
++ fprintf (file, "e ");
++ else if (code == NE)
++ fprintf (file, "ne ");
++ else if (code == GT)
++ fprintf (file, "g ");
++ else if (code == GTU)
++ fprintf (file, "gu ");
++ else if (code == LT)
++ fprintf (file, "l ");
++ else if (code == LTU)
++ fprintf (file, "lu ");
++ else if (code == GE)
++ fprintf (file, "ge ");
++ else if (code == GEU)
++ fprintf (file, "geu");
++ else if (code == LE)
++ fprintf (file, "le ");
++ else if (code == LEU)
++ fprintf (file, "leu");
++ else
++ output_addr_const (file, op);
++}
++
++/* A C compound statement to output to stdio stream STREAM the
++ assembler syntax for an instruction operand that is a memory
++ reference whose address is ADDR. ADDR is an RTL expression.
++
++ On some machines, the syntax for a symbolic address depends on
++ the section that the address refers to. On these machines,
++ define the macro `ENCODE_SECTION_INFO' to store the information
++ into the `symbol_ref', and then check for it here. */
++
++void
++lm32_print_operand_address (FILE *file, rtx addr)
++{
++ switch (GET_CODE (addr))
++ {
++ case REG:
++ fprintf (file, "(%s+0)", reg_names [REGNO (addr)]);
++ break;
++
++ case MEM:
++ output_address (XEXP (addr, 0));
++ break;
++
++ case PLUS:
++ {
++ rtx arg0 = XEXP (addr, 0);
++ rtx arg1 = XEXP (addr, 1);
++
++ if (GET_CODE (arg0) == REG && CONSTANT_P (arg1))
++ {
++ if (GET_CODE(arg1) == CONST_INT)
++ fprintf (file, "(%s+%ld)", reg_names [REGNO (arg0)], INTVAL (arg1));
++ else
++ {
++ fprintf (file, "(%s+", reg_names [REGNO (arg0)]);
++ output_addr_const (file, arg1);
++ fprintf (file, ")");
++ }
++ }
++ else if (CONSTANT_P (arg0) && CONSTANT_P (arg1))
++ output_addr_const (file, addr);
++ else
++ abort_with_insn (addr, "bad operand");
++ }
++ break;
++
++ case SYMBOL_REF:
++ if (SYMBOL_REF_SMALL_P (addr))
++ {
++ fprintf (file, "gp(");
++ output_addr_const (file, addr);
++ fprintf (file, ")");
++ }
++ else
++ abort_with_insn (addr, "can't use non gp relative absolute address");
++ break;
++
++ default:
++ abort_with_insn (addr, "invalid addressing mode");
++ break;
++ }
++}
++
++/* Determine where to put an argument to a function.
++ Value is zero to push the argument on the stack,
++ or a hard register in which to store the argument.
++
++ MODE is the argument's machine mode.
++ TYPE is the data type of the argument (as a tree).
++ This is null for libcalls where that information may
++ not be available.
++ CUM is a variable of type CUMULATIVE_ARGS which gives info about
++ the preceding args and about the function being called.
++ NAMED is nonzero if this argument is a named parameter
++ (otherwise it is an extra parameter matching an ellipsis). */
++
++rtx
++lm32_function_arg (CUMULATIVE_ARGS cum, enum machine_mode mode,
++ tree type, int named)
++{
++ if (mode == VOIDmode)
++ /* Compute operand 2 of the call insn. */
++ return GEN_INT (0);
++
++ if (targetm.calls.must_pass_in_stack (mode, type))
++ return NULL_RTX;
++
++ if (!named || (cum + LM32_NUM_REGS2(mode, type) > LM32_NUM_ARG_REGS))
++ return NULL_RTX;
++
++ return gen_rtx_REG (mode, cum + LM32_FIRST_ARG_REG);
++}
++
++HOST_WIDE_INT
++lm32_compute_initial_elimination_offset (int from, int to)
++{
++ HOST_WIDE_INT offset = 0;
++
++ switch (from)
++ {
++ /*case FRAME_POINTER_REGNUM: - Same as ARG_POINTER_REGNUM */
++ case ARG_POINTER_REGNUM:
++ switch (to)
++ {
++ case FRAME_POINTER_REGNUM:
++ offset = 0;
++ break;
++ case STACK_POINTER_REGNUM:
++ offset = lm32_compute_frame_size (get_frame_size ()) - current_frame_info.pretend_size;
++ break;
++ default:
++ abort ();
++ }
++ break;
++ default:
++ abort ();
++ }
++
++ return offset;
++}
++
++static void
++lm32_setup_incoming_varargs (CUMULATIVE_ARGS *cum, enum machine_mode mode,
++ tree type, int *pretend_size, int no_rtl)
++{
++ int first_anon_arg;
++ tree fntype;
++ int stdarg_p;
++
++ fntype = TREE_TYPE (current_function_decl);
++ stdarg_p = (TYPE_ARG_TYPES (fntype) != 0
++ && (TREE_VALUE (tree_last (TYPE_ARG_TYPES (fntype)))
++ != void_type_node));
++
++ if (stdarg_p)
++ first_anon_arg = *cum + LM32_FIRST_ARG_REG;
++ else
++ {
++ /* this is the common case, we have been passed details setup
++ for the last named argument, we want to skip over the
++ registers, if any used in passing this named paramter in
++ order to determine which is the first registers used to pass
++ anonymous arguments */
++ int size;
++
++ if (mode==BLKmode)
++ size = int_size_in_bytes (type);
++ else
++ size = GET_MODE_SIZE (mode);
++
++ first_anon_arg = *cum + LM32_FIRST_ARG_REG + ((size + UNITS_PER_WORD - 1) / UNITS_PER_WORD);
++ }
++
++ if ((first_anon_arg < (LM32_FIRST_ARG_REG + LM32_NUM_ARG_REGS)) && !no_rtl)
++ {
++ int first_reg_offset = first_anon_arg;
++ int size = LM32_FIRST_ARG_REG + LM32_NUM_ARG_REGS - first_anon_arg;
++ rtx regblock;
++
++ regblock = gen_rtx_MEM (BLKmode,
++ plus_constant (arg_pointer_rtx,
++ FIRST_PARM_OFFSET (0)));
++ move_block_from_reg (first_reg_offset, regblock, size);
++
++ *pretend_size = size * UNITS_PER_WORD;
++ }
++}
++
++/* Abort after printing out a specific insn. */
++static void
++abort_with_insn (rtx insn, const char *reason)
++{
++ error (reason);
++ debug_rtx (insn);
++ abort ();
++}
++
++/* Override command line options */
++void
++lm32_override_options (void)
++{
++ /* We must have sign-extend enabled if barrel-shift isn't */
++ if (!MASK_BARREL_SHIFT_ENABLED)
++ {
++ warning (0, "neither -mbarrel-shift-enabled nor -msign-extend-enabled specified. Assuming -msign-extend-enabled");
++ target_flags |= MASK_SIGN_EXTEND_ENABLED;
++ }
++}
++
++/* Return nonzero if this function is known to have a null epilogue.
++ This allows the optimizer to omit jumps to jumps if no stack
++ was created. */
++int
++lm32_can_use_return (void)
++{
++ if (!reload_completed)
++ return 0;
++
++ if (df_regs_ever_live_p(RA_REGNUM) || crtl->profile)
++ return 0;
++
++ if (lm32_compute_frame_size (get_frame_size ()) != 0)
++ return 0;
++
++ return 1;
++}
++
++/* Support function to determine the return address of the function
++ 'count' frames back up the stack. */
++rtx
++lm32_return_addr_rtx (int count, rtx frame)
++{
++ rtx r;
++ if (count == 0)
++ {
++ /* *mjs* This test originally used leaf_function_p (), we now use
++ the regs_ever_live test which I *think* is more accurate. */
++ if (!df_regs_ever_live_p(RA_REGNUM))
++ {
++ r = gen_rtx_REG (Pmode, RA_REGNUM);
++ }
++ else
++ {
++ r = gen_rtx_MEM (Pmode,
++ gen_rtx_PLUS (Pmode, frame,
++ GEN_INT(- 2 * UNITS_PER_WORD)));
++ set_mem_alias_set (r, get_frame_alias_set ());
++ }
++ }
++ else if (flag_omit_frame_pointer)
++ r = NULL_RTX;
++ else
++ {
++ r = gen_rtx_MEM (Pmode,
++ gen_rtx_PLUS (Pmode, frame,
++ GEN_INT(- 2 * UNITS_PER_WORD)));
++ set_mem_alias_set (r, get_frame_alias_set ());
++ }
++ return r;
++}
++
++/* Return true if EXP should be placed in the small data section. */
++
++static bool
++lm32_in_small_data_p (const_tree exp)
++{
++ /* We want to merge strings, so we never consider them small data. */
++ if (TREE_CODE (exp) == STRING_CST)
++ return false;
++
++ /* Functions are never in the small data area. Duh. */
++ if (TREE_CODE (exp) == FUNCTION_DECL)
++ return false;
++
++ if (TREE_CODE (exp) == VAR_DECL && DECL_SECTION_NAME (exp))
++ {
++ const char *section = TREE_STRING_POINTER (DECL_SECTION_NAME (exp));
++ if (strcmp (section, ".sdata") == 0
++ || strcmp (section, ".sbss") == 0)
++ return true;
++ }
++ else
++ {
++ HOST_WIDE_INT size = int_size_in_bytes (TREE_TYPE (exp));
++
++ /* If this is an incomplete type with size 0, then we can't put it
++ in sdata because it might be too big when completed. */
++ if (size > 0 && (unsigned HOST_WIDE_INT) size <= g_switch_value)
++ return true;
++ }
++
++ return false;
++}
++
++/* Emit straight-line code to move LENGTH bytes from SRC to DEST.
++ Assume that the areas do not overlap. */
++
++static void
++lm32_block_move_inline (rtx dest, rtx src, HOST_WIDE_INT length, HOST_WIDE_INT alignment)
++{
++ HOST_WIDE_INT offset, delta;
++ unsigned HOST_WIDE_INT bits;
++ int i;
++ enum machine_mode mode;
++ rtx *regs;
++
++ /* Work out how many bits to move at a time. */
++ switch (alignment)
++ {
++ case 1:
++ bits = 8;
++ break;
++ case 2:
++ bits = 16;
++ break;
++ case 4:
++ bits = 32;
++ break;
++ default:
++ abort ();
++ }
++
++ mode = mode_for_size (bits, MODE_INT, 0);
++ delta = bits / BITS_PER_UNIT;
++
++ /* Allocate a buffer for the temporary registers. */
++ regs = alloca (sizeof (rtx) * length / delta);
++
++ /* Load as many BITS-sized chunks as possible. */
++ for (offset = 0, i = 0; offset + delta <= length; offset += delta, i++)
++ {
++ regs[i] = gen_reg_rtx (mode);
++ emit_move_insn (regs[i], adjust_address (src, mode, offset));
++ }
++
++ /* Copy the chunks to the destination. */
++ for (offset = 0, i = 0; offset + delta <= length; offset += delta, i++)
++ emit_move_insn (adjust_address (dest, mode, offset), regs[i]);
++
++ /* Mop up any left-over bytes. */
++ if (offset < length)
++ {
++ src = adjust_address (src, BLKmode, offset);
++ dest = adjust_address (dest, BLKmode, offset);
++ move_by_pieces (dest, src, length - offset,
++ MIN (MEM_ALIGN (src), MEM_ALIGN (dest)), 0);
++ }
++}
++
++/* Expand string/block move operations.
++
++ operands[0] is the pointer to the destination.
++ operands[1] is the pointer to the source.
++ operands[2] is the number of bytes to move.
++ operands[3] is the alignment. */
++
++int
++lm32_expand_block_move (rtx *operands)
++{
++ if ((GET_CODE (operands[2]) == CONST_INT) && (INTVAL (operands[2]) <= 32))
++ {
++ lm32_block_move_inline (operands[0], operands[1], INTVAL (operands[2]), INTVAL (operands[3]));
++ return 1;
++ }
++ return 0;
++}
++
++/* Return TRUE if X references a SYMBOL_REF or LABEL_REF whose symbol
++ isn't protected by a PIC unspec. */
++int
++nonpic_symbol_mentioned_p (rtx x)
++{
++ register const char *fmt;
++ register int i;
++
++ if (GET_CODE (x) == SYMBOL_REF || GET_CODE (x) == LABEL_REF
++ || GET_CODE (x) == PC)
++ return 1;
++
++ /* We don't want to look into the possible MEM location of a
++ CONST_DOUBLE, since we're not going to use it, in general. */
++ if (GET_CODE (x) == CONST_DOUBLE)
++ return 0;
++
++ if (GET_CODE (x) == UNSPEC)
++ return 0;
++
++ fmt = GET_RTX_FORMAT (GET_CODE (x));
++ for (i = GET_RTX_LENGTH (GET_CODE (x)) - 1; i >= 0; i--)
++ {
++ if (fmt[i] == 'E')
++ {
++ register int j;
++
++ for (j = XVECLEN (x, i) - 1; j >= 0; j--)
++ if (nonpic_symbol_mentioned_p (XVECEXP (x, i, j)))
++ return 1;
++ }
++ else if (fmt[i] == 'e' && nonpic_symbol_mentioned_p (XEXP (x, i)))
++ return 1;
++ }
++
++ return 0;
++}
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lm32.h gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.h
+--- gcc-4.4.2.orig/gcc/config/lm32/lm32.h 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.h 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,657 @@
++/* Definitions of target machine for GNU compiler, Lattice Mico32 architecture.
++ Contributed by Jon Beniston <jon@beniston.com>
++
++ Copyright (C) 2008 Free Software Foundation, Inc.
++
++ This file is part of GCC.
++
++ GCC 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 3, or (at your
++ option) any later version.
++
++ GCC 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 GCC; see the file COPYING3. If not see
++ <http://www.gnu.org/licenses/>. */
++
++/*-------------------------------*/
++/* Run-time Target Specification */
++/*-------------------------------*/
++
++/* Print subsidiary information on the compiler version in use. */
++#ifndef TARGET_VERSION
++#define TARGET_VERSION fprintf (stderr, " (LatticeMico32)")
++#endif
++
++/* Target CPU builtins. */
++#define TARGET_CPU_CPP_BUILTINS() \
++ do \
++ { \
++ builtin_define ("__lm32__"); \
++ builtin_define_std ("lm32"); \
++ builtin_assert ("cpu=lm32"); \
++ builtin_assert ("machine=lm32"); \
++ } \
++ while (0)
++
++#define CPP_SPEC "\
++%{mmultiply-enabled:-D__multiply_enabled__} \
++%{mdivide-enabled:-D__divide_enabled__} \
++%{mbarrel-shift-enabled:-D__barrel_shift_enabled__} \
++%{msign-extend-enabled:-D__sign_extend_enabled__} \
++%{muser-enabled:-D__user_enabled__} \
++"
++
++#undef ASM_SPEC
++#define ASM_SPEC "\
++%{mmultiply-enabled} \
++%{mdivide-enabled} \
++%{mbarrel-shift-enabled} \
++%{msign-extend-enabled} \
++%{muser-extend-enabled} \
++%{v} \
++"
++
++/* Let link script define all link options.
++ Default to using simulator link script. */
++
++#undef STARTFILE_SPEC
++#define STARTFILE_SPEC ""
++#undef ENDFILE_SPEC
++#define ENDFILE_SPEC ""
++#undef LIB_SPEC
++#define LIB_SPEC "%{!T*:-T sim.ld}"
++
++#define OVERRIDE_OPTIONS lm32_override_options()
++
++extern int target_flags;
++
++/* Add -G xx support. */
++
++#undef SWITCH_TAKES_ARG
++#define SWITCH_TAKES_ARG(CHAR) \
++(DEFAULT_SWITCH_TAKES_ARG (CHAR) || (CHAR) == 'G')
++
++#undef CC1_SPEC
++#define CC1_SPEC "%{G*}"
++
++extern struct rtx_def *lm32_compare_op0;
++extern struct rtx_def *lm32_compare_op1;
++
++/*---------------------------------*/
++/* Target machine storage layout. */
++/*---------------------------------*/
++
++#define BITS_BIG_ENDIAN 0
++#define BYTES_BIG_ENDIAN 1
++#define WORDS_BIG_ENDIAN 1
++#define LIBGCC2_WORDS_BIG_ENDIAN 1
++
++#define BITS_PER_UNIT 8
++#define BITS_PER_WORD 32
++#define UNITS_PER_WORD 4
++
++#define POINTER_SIZE 32
++
++#define PROMOTE_MODE(MODE,UNSIGNEDP,TYPE) \
++do { \
++ if (GET_MODE_CLASS (MODE) == MODE_INT \
++ && GET_MODE_SIZE (MODE) < UNITS_PER_WORD) \
++ (MODE) = word_mode; \
++} while (0)
++
++#define PARM_BOUNDARY 32
++
++#define STACK_BOUNDARY 32
++
++#define BIGGEST_ALIGNMENT 64
++
++#define FUNCTION_BOUNDARY 32
++
++#define EMPTY_FIELD_BOUNDARY 32
++
++#define STRICT_ALIGNMENT 1
++
++#define TARGET_FLOAT_FORMAT IEEE_FLOAT_FORMAT
++
++/* Make strings word-aligned so strcpy from constants will be faster. */
++#define CONSTANT_ALIGNMENT(EXP, ALIGN) \
++ (TREE_CODE (EXP) == STRING_CST \
++ && (ALIGN) < BITS_PER_WORD ? BITS_PER_WORD : (ALIGN))
++
++/* Make arrays and structures word-aligned to allow faster copying etc. */
++#define DATA_ALIGNMENT(TYPE, ALIGN) \
++ ((((ALIGN) < BITS_PER_WORD) \
++ && (TREE_CODE (TYPE) == ARRAY_TYPE \
++ || TREE_CODE (TYPE) == UNION_TYPE \
++ || TREE_CODE (TYPE) == RECORD_TYPE)) ? BITS_PER_WORD : (ALIGN))
++
++/* We need this for the same reason as DATA_ALIGNMENT, namely to cause
++ character arrays to be word-aligned so that `strcpy' calls that copy
++ constants to character arrays can be done inline, and 'strcmp' can be
++ optimised to use word loads. */
++#define LOCAL_ALIGNMENT(TYPE, ALIGN) \
++ DATA_ALIGNMENT (TYPE, ALIGN)
++
++/*----------------------------------------*/
++/* Layout of source language data types. */
++/*----------------------------------------*/
++
++#define INT_TYPE_SIZE 32
++#define SHORT_TYPE_SIZE 16
++#define LONG_TYPE_SIZE 32
++#define LONG_LONG_TYPE_SIZE 64
++
++#define FLOAT_TYPE_SIZE 32
++#define DOUBLE_TYPE_SIZE 64
++#define LONG_DOUBLE_TYPE_SIZE 64
++
++#define DEFAULT_SIGNED_CHAR 0
++
++#define SIZE_TYPE "unsigned int"
++
++#define PTRDIFF_TYPE "int"
++
++/*---------------------------*/
++/* Standard register usage. */
++/*---------------------------*/
++
++#define FIRST_PSEUDO_REGISTER 32
++
++#define RV_REGNUM 1
++#define GP_REGNUM 26
++#define FP_REGNUM 27
++#define SP_REGNUM 28
++#define RA_REGNUM 29
++
++#define G_REG_P(X) ((X)<32)
++#define PSEUDO_REG_P(X) ((X)>=FIRST_PSEUDO_REGISTER)
++
++#define FIXED_REGISTERS \
++{ 1, 0, 0, 0, 0, 0, 0, 0, \
++ 0, 0, 0, 0, 0, 0, 0, 0, \
++ 0, 0, 0, 0, 0, 0, 0, 0, \
++ 0, 0, 1, 0, 1, 0, 1, 1}
++
++#define CALL_USED_REGISTERS \
++{ 1, 1, 1, 1, 1, 1, 1, 1, \
++ 1, 1, 1, 0, 0, 0, 0, 0, \
++ 0, 0, 0, 0, 0, 0, 0, 0, \
++ 0, 0, 1, 0, 1, 0, 1, 1}
++
++#define HARD_REGNO_NREGS(REGNO, MODE) \
++ ((GET_MODE_SIZE (MODE) + UNITS_PER_WORD - 1) / UNITS_PER_WORD)
++
++#define HARD_REGNO_MODE_OK(REGNO, MODE) G_REG_P(REGNO)
++
++#define MODES_TIEABLE_P(MODE1, MODE2) \
++( GET_MODE_CLASS (MODE1) == MODE_INT \
++ && GET_MODE_CLASS (MODE2) == MODE_INT \
++ && GET_MODE_SIZE (MODE1) <= UNITS_PER_WORD \
++ && GET_MODE_SIZE (MODE2) <= UNITS_PER_WORD)
++
++#define AVOID_CCMODE_COPIES
++
++/*----------------------------------*/
++/* Register classes and constants. */
++/*----------------------------------*/
++
++enum reg_class {
++ NO_REGS,
++ GENERAL_REGS,
++ ALL_REGS,
++ LIM_REG_CLASSES
++};
++
++#define N_REG_CLASSES (int) LIM_REG_CLASSES
++
++#define REG_CLASS_NAMES { "NO_REGS", "GENERAL_REGS", "ALL_REGS" }
++
++#define REG_CLASS_CONTENTS \
++{ {0x00000000}, \
++ {0xffffffff}, \
++ {0xffffffff} \
++}
++
++#define REGNO_REG_CLASS(REGNO) \
++ (G_REG_P(REGNO) ? GENERAL_REGS : NO_REGS)
++
++#define CLASS_MAX_NREGS(CLASS, MODE) \
++ ((GET_MODE_SIZE (MODE) + UNITS_PER_WORD - 1) / UNITS_PER_WORD)
++
++#define INDEX_REG_CLASS NO_REGS
++
++#define BASE_REG_CLASS GENERAL_REGS
++
++#define REG_CLASS_FROM_LETTER(C) NO_REGS
++
++#ifdef REG_OK_STRICT
++#define REGNO_OK_FOR_BASE_P(REGNO) \
++(G_REG_P (REGNO) || G_REG_P (reg_renumber[REGNO]))
++#else
++#define REGNO_OK_FOR_BASE_P(REGNO) \
++(G_REG_P (REGNO) || PSEUDO_REG_P (REGNO))
++#endif
++
++#define REGNO_OK_FOR_INDEX_P(REGNO) 0
++
++#define PREFERRED_RELOAD_CLASS(X,CLASS) (CLASS)
++
++/* The letters I, J, K, L, M, N, O, P in a register constraint string
++ can be used to stand for particular ranges of immediate operands.
++ This macro defines what the ranges are.
++ C is the letter, and VALUE is a constant value.
++ Return 1 if VALUE is in the range specified by C.
++
++ Lattice usage:
++
++ J - 0
++ K - 16-bit signed
++ L - 16-bit unsigned
++ M - 32-bit signed
++ */
++#define MEDIUM_INT(X) ((((HOST_WIDE_INT)(X)) >= -32768) && (((HOST_WIDE_INT)(X)) < 32768))
++#define MEDIUM_UINT(X) (((unsigned HOST_WIDE_INT)(X)) < 65536)
++#define LARGE_INT(X) \
++((X) >= (-(HOST_WIDE_INT) 0x7fffffff - 1) \
++ && (X) <= (unsigned HOST_WIDE_INT) 0xffffffff)
++
++#define CONST_OK_FOR_LETTER_P(VALUE, C) \
++( (C) == 'J' ? (VALUE) == 0 \
++ : (C) == 'K' ? MEDIUM_INT (VALUE) \
++ : (C) == 'L' ? MEDIUM_UINT (VALUE) \
++ : (C) == 'M' ? LARGE_INT (VALUE) \
++ : 0 \
++)
++
++#define CONST_DOUBLE_OK_FOR_LETTER_P(VALUE, C) 0
++
++/*----------------------------------------*/
++/* Stack Layout and Calling Conventions. */
++/*----------------------------------------*/
++
++#define STACK_GROWS_DOWNWARD 1
++
++#define FRAME_GROWS_DOWNWARD 1
++
++#define STACK_POINTER_OFFSET (UNITS_PER_WORD)
++
++#define STARTING_FRAME_OFFSET (UNITS_PER_WORD)
++
++#define FIRST_PARM_OFFSET(FNDECL) (UNITS_PER_WORD)
++
++#define STACK_POINTER_REGNUM SP_REGNUM
++
++#define FRAME_POINTER_REGNUM FP_REGNUM
++
++#define ARG_POINTER_REGNUM FRAME_POINTER_REGNUM
++
++#define FRAME_POINTER_REQUIRED (cfun->calls_alloca)
++
++#define RETURN_ADDR_RTX(count, frame) \
++ lm32_return_addr_rtx (count, frame)
++
++/* FIXME! */
++#define STATIC_CHAIN_REGNUM 3
++
++#define ELIMINABLE_REGS \
++{{ FRAME_POINTER_REGNUM, STACK_POINTER_REGNUM }, \
++ { ARG_POINTER_REGNUM, STACK_POINTER_REGNUM }, \
++}
++
++#define CAN_ELIMINATE(FROM, TO) \
++ (((TO) == STACK_POINTER_REGNUM && frame_pointer_needed) ? 0 : 1)
++
++#define INITIAL_ELIMINATION_OFFSET(FROM, TO, OFFSET) \
++ (OFFSET) = lm32_compute_initial_elimination_offset (FROM, TO)
++
++/*-----------------------------*/
++/* Function argument passing. */
++/*-----------------------------*/
++
++#define ACCUMULATE_OUTGOING_ARGS 1
++
++#define RETURN_POPS_ARGS(DECL, FUNTYPE, SIZE) 0
++
++/*--------------------------------*/
++/* Passing Arguments in Registers */
++/*--------------------------------*/
++
++/* The first argument register */
++#define LM32_FIRST_ARG_REG 1
++
++/* The number of (integer) argument register available. */
++#define LM32_NUM_ARG_REGS 8
++
++#define FUNCTION_ARG(CUM, MODE, TYPE, NAMED) \
++ lm32_function_arg ((CUM), (MODE), (TYPE), (NAMED))
++
++#define CUMULATIVE_ARGS int
++
++#define INIT_CUMULATIVE_ARGS(CUM,FNTYPE,LIBNAME,INDIRECT,N_NAMED_ARGS) \
++ (CUM) = 0
++
++#define FUNCTION_ARG_ADVANCE(CUM, MODE, TYPE, NAMED) \
++ (CUM) += LM32_NUM_REGS2 (MODE, TYPE)
++
++#define FUNCTION_ARG_REGNO_P(r) (((r) >= 1) && ((r) <= LM32_NUM_ARG_REGS))
++
++/*--------------------*/
++/* Function results. */
++/*--------------------*/
++
++#define FUNCTION_VALUE(VALTYPE, FUNC) \
++ gen_rtx_REG ((INTEGRAL_TYPE_P (VALTYPE) \
++ && TYPE_PRECISION (VALTYPE) < BITS_PER_WORD) \
++ ? word_mode \
++ : TYPE_MODE (VALTYPE), \
++ RV_REGNUM)
++
++#define LIBCALL_VALUE(MODE) gen_rtx_REG (MODE, RV_REGNUM)
++
++#define FUNCTION_VALUE_REGNO_P(N) ((N) == RV_REGNUM)
++
++#define RETURN_IN_MEMORY(TYPE) lm32_return_in_memory (TYPE)
++
++#define DEFAULT_PCC_STRUCT_RETURN 0
++
++/* Convert from bytes to ints. */
++#define LM32_NUM_INTS(X) (((X) + UNITS_PER_WORD - 1) / UNITS_PER_WORD)
++
++/* The number of (integer) registers required to hold a quantity of
++ type MODE. */
++#define LM32_NUM_REGS(MODE) LM32_NUM_INTS (GET_MODE_SIZE (MODE))
++
++/* The number of (integer) registers required to hold a quantity of
++ TYPE MODE. */
++#define LM32_NUM_REGS2(MODE, TYPE) \
++ LM32_NUM_INTS ((MODE) == BLKmode ? \
++ int_size_in_bytes (TYPE) : GET_MODE_SIZE (MODE))
++
++#define STRUCT_VALUE 0
++
++/*---------------------------*/
++/* Function entry and exit. */
++/*---------------------------*/
++
++/*-------------*/
++/* Profiling. */
++/*-------------*/
++
++#define FUNCTION_PROFILER(FILE, LABELNO)
++
++/*---------------*/
++/* Trampolines. */
++/*---------------*/
++
++#define INITIALIZE_TRAMPOLINE
++#define TRAMPOLINE_SIZE 0
++
++/*---------------------*/
++/* Addressing Modes. */
++/*---------------------*/
++
++#define CONSTANT_ADDRESS_P(X) \
++ ((GET_CODE (X) == LABEL_REF || GET_CODE (X) == SYMBOL_REF \
++ || GET_CODE (X) == CONST_INT || GET_CODE (X) == HIGH \
++ || (GET_CODE (X) == CONST)))
++
++#define MAX_REGS_PER_ADDRESS 1
++
++#ifdef REG_OK_STRICT
++#define REG_OK_FOR_FRAME_PTR_P(X) (REGNO (X) == FRAME_POINTER_REGNUM)
++#else
++#define REG_OK_FOR_FRAME_PTR_P(X) (REGNO (X) == FRAME_POINTER_REGNUM)
++#endif
++
++#define RTX_OK_FOR_BASE_P(X) (REG_P (X) && REG_OK_FOR_BASE_P (X))
++#define RTX_OK_FOR_STACK_P(X) (REG_P (X) && (REGNO (X) == STACK_POINTER_REGNUM))
++#define CONST_OK_FOR_BASE_OFFSET(X, MODE) const_ok_for_base_offset ((X), (MODE))
++
++#define LEGITIMATE_BASE_INDEX_P(ADDR, MODE) \
++( GET_CODE (ADDR)==PLUS \
++ && RTX_OK_FOR_BASE_P (XEXP (ADDR, 0)) \
++ && GET_CODE (XEXP (ADDR, 1)) == CONST_INT \
++ && CONST_OK_FOR_BASE_OFFSET (XEXP ((ADDR), 1), (MODE)))
++
++#define LEGITIMATE_GPREL_P(ADDR) \
++( GET_CODE (ADDR) == SYMBOL_REF \
++ && SYMBOL_REF_SMALL_P (ADDR))
++
++#ifdef REG_OK_STRICT
++#define REG_OK_FOR_BASE_P(X) (G_REG_P (REGNO (X)))
++#else
++#define REG_OK_FOR_BASE_P(X) (G_REG_P (REGNO (X)) || PSEUDO_REG_P (REGNO (X)))
++#endif
++
++#ifdef REG_OK_STRICT
++#define REG_OK_FOR_INDEX_P(X) (G_REG_P (REGNO (X)))
++#else
++#define REG_OK_FOR_INDEX_P(X) (G_REG_P (REGNO (X)) || PSEUDO_REG_P (REGNO (X)))
++#endif
++
++#define GO_IF_LEGITIMATE_ADDRESS(m,x,l) \
++{ \
++ if (RTX_OK_FOR_BASE_P (x)) goto l; /* (rM) */ \
++ else if (LEGITIMATE_BASE_INDEX_P (x, m)) goto l; /* (rM)+literal) */ \
++ else if (LEGITIMATE_GPREL_P (x)) goto l; \
++}
++
++#define ARM_LEGITIMIZE_ADDRESS(X, OLDX, MODE, WIN) \
++do { \
++ if (flag_pic) \
++ X = lm32_legitimize_pic_address (OLDX, MODE, NULL_RTX); \
++} while (0)
++
++#define GO_IF_MODE_DEPENDENT_ADDRESS(ADDR, LABEL) \
++ if (GET_CODE (ADDR) == PLUS) goto LABEL; \
++
++#define LEGITIMATE_CONSTANT_P(X) 1
++
++/*-------------------------*/
++/* Condition Code Status. */
++/*-------------------------*/
++
++#define REVERSIBLE_CC_MODE(MODE) 1
++
++/*---------*/
++/* Costs. */
++/*---------*/
++
++#define SLOW_BYTE_ACCESS 1
++
++#define NO_FUNCTION_CSE
++
++#define BRANCH_COST(speed_p, predictable_p) 4
++
++#define MOVE_RATIO(speed) (speed ? 24 : 3)
++
++/*------------*/
++/* Sections. */
++/*------------*/
++
++#define TEXT_SECTION_ASM_OP "\t.section\t.text"
++#define DATA_SECTION_ASM_OP "\t.section\t.data"
++#define SDATA_SECTION_ASM_OP "\t.section\t.sdata,\"aw\""
++#define BSS_SECTION_ASM_OP "\t.section\t.bss"
++#define SBSS_SECTION_ASM_OP "\t.section\t.sbss,\"aw\""
++
++/*-------*/
++/* PIC. */
++/*-------*/
++
++#define PIC_OFFSET_TABLE_REGNUM (flag_pic ? GP_REGNUM : INVALID_REGNUM)
++
++#define JUMP_TABLES_IN_TEXT_SECTION (flag_pic)
++
++#define LEGITIMATE_PIC_OPERAND_P(X) \
++ (!(nonpic_symbol_mentioned_p (X)))
++
++/*-------------*/
++/* Assembler. */
++/*-------------*/
++
++#define ASM_COMMENT_START "#"
++
++#define ASM_APP_ON "#APP\n"
++
++#define ASM_APP_OFF "#NO_APP\n"
++
++#define ASM_OUTPUT_DEF(FILE,LABEL1,LABEL2) \
++ do { \
++ fputc ( '\t', FILE); \
++ assemble_name (FILE, LABEL1); \
++ fputs ( " = ", FILE); \
++ assemble_name (FILE, LABEL2); \
++ fputc ( '\n', FILE); \
++ } while (0)
++
++/* Override default implementation in elfos.h to support -G. */
++#undef ASM_OUTPUT_ALIGNED_LOCAL
++#define ASM_OUTPUT_ALIGNED_LOCAL(FILE, NAME, SIZE, ALIGN) \
++do { \
++ if ((SIZE) <= g_switch_value) \
++ switch_to_section (sbss_section); \
++ else \
++ switch_to_section (bss_section); \
++ ASM_OUTPUT_TYPE_DIRECTIVE (FILE, NAME, "object"); \
++ if (!flag_inhibit_size_directive) \
++ ASM_OUTPUT_SIZE_DIRECTIVE (FILE, NAME, SIZE); \
++ ASM_OUTPUT_ALIGN ((FILE), exact_log2((ALIGN) / BITS_PER_UNIT)); \
++ ASM_OUTPUT_LABEL(FILE, NAME); \
++ ASM_OUTPUT_SKIP((FILE), (SIZE) ? (SIZE) : 1); \
++} while (0)
++
++/* Override default implementation in elfos.h to support -G. */
++#undef ASM_OUTPUT_ALIGNED_COMMON
++#define ASM_OUTPUT_ALIGNED_COMMON(FILE, NAME, SIZE, ALIGN) \
++do \
++{ \
++ if ((SIZE) <= g_switch_value) \
++ { \
++ switch_to_section (sbss_section); \
++ (*targetm.asm_out.globalize_label) (FILE, NAME); \
++ ASM_OUTPUT_TYPE_DIRECTIVE (FILE, NAME, "object"); \
++ if (!flag_inhibit_size_directive) \
++ ASM_OUTPUT_SIZE_DIRECTIVE (FILE, NAME, SIZE); \
++ ASM_OUTPUT_ALIGN ((FILE), exact_log2((ALIGN) / BITS_PER_UNIT)); \
++ ASM_OUTPUT_LABEL(FILE, NAME); \
++ ASM_OUTPUT_SKIP((FILE), (SIZE) ? (SIZE) : 1); \
++ } \
++ else \
++ { \
++ switch_to_section (bss_section); \
++ fprintf ((FILE), "%s", COMMON_ASM_OP); \
++ assemble_name ((FILE), (NAME)); \
++ fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n", (SIZE), (ALIGN) / BITS_PER_UNIT); \
++ } \
++} \
++while (0)
++
++#define ASM_OUTPUT_LABEL(FILE, NAME) \
++ do { assemble_name (FILE, NAME); fputs (":\n", FILE); } while (0)
++
++#define ASM_OUTPUT_LABELREF(FILE,NAME) \
++ do { \
++ const char *xname = (NAME); \
++ if (xname[0] == '@') \
++ xname += 1; \
++ if (xname[0] == '*') \
++ xname += 1; \
++ fputs (xname, FILE); \
++ } while (0)
++
++#define ASM_OUTPUT_SYMBOL_REF(STREAM, SYMBOL) \
++ do { \
++ assemble_name (STREAM, XSTR (SYMBOL, 0)); \
++ } while (0)
++
++#define GLOBAL_ASM_OP "\t.global\t"
++
++#define REGISTER_NAMES \
++{ \
++ "r0", "r1", "r2", "r3", "r4", "r5", "r6", "r7", \
++ "r8", "r9", "r10", "r11", "r12", "r13", "r14", "r15", \
++ "r16", "r17", "r18", "r19", "r20", "r21", "r22", "r23", \
++ "r24", "r25", "gp", "fp", "sp", "ra", "ea", "ba"}
++
++#define PRINT_OPERAND_PUNCT_VALID_P(CHAR) \
++ (((CHAR) == '&') || ((CHAR) == '@') || ((CHAR) == '*'))
++
++#define PRINT_OPERAND(FILE, X, CODE) \
++ lm32_print_operand (FILE, X, CODE)
++
++#define PRINT_OPERAND_ADDRESS(FILE, ADDR) \
++ lm32_print_operand_address (FILE, ADDR)
++
++#ifndef LOCAL_LABEL_PREFIX
++#define LOCAL_LABEL_PREFIX "."
++#endif
++
++#define ASM_OUTPUT_ALIGN(FILE,LOG) \
++ do { if ((LOG) != 0) fprintf (FILE, "\t.align %d\n", (1 << (LOG))); } while (0)
++
++#define ASM_OUTPUT_ADDR_VEC_ELT(FILE, VALUE) \
++do { \
++ char label[64]; \
++ ASM_GENERATE_INTERNAL_LABEL (label, "L", VALUE); \
++ fprintf (FILE, "\n\t.word\t"); \
++ assemble_name (FILE, label); \
++ fprintf (FILE, "\n"); \
++} while (0)
++
++#define ASM_OUTPUT_ADDR_DIFF_ELT(FILE, BODY, VALUE, REL) \
++do { \
++ char label[64]; \
++ fprintf (FILE, "\t.word\t("); \
++ ASM_GENERATE_INTERNAL_LABEL (label, "L", VALUE); \
++ assemble_name (FILE, label); \
++ fprintf (FILE, "-"); \
++ ASM_GENERATE_INTERNAL_LABEL (label, "L", REL); \
++ assemble_name (FILE, label); \
++ fprintf (FILE, ")\n"); \
++} while (0)
++
++/*-------------*/
++/* Debugging. */
++/*-------------*/
++
++#define DBX_REGISTER_NUMBER(REGNO) (REGNO)
++
++#define CAN_DEBUG_WITHOUT_FP
++
++#define DEFAULT_GDB_EXTENSIONS 1
++
++/*--------*/
++/* Misc. */
++/*--------*/
++
++#define CASE_VECTOR_MODE Pmode
++
++#define WORD_REGISTER_OPERATIONS
++
++#define LOAD_EXTEND_OP(MODE) ZERO_EXTEND
++
++#define SHORT_IMMEDIATES_SIGN_EXTEND
++
++#define MOVE_MAX UNITS_PER_WORD
++#define MAX_MOVE_MAX 4
++
++#define SHIFT_COUNT_TRUNCATED 1
++
++#define TRULY_NOOP_TRUNCATION(OUTPREC, INPREC) 1
++
++#define Pmode SImode
++
++#define FUNCTION_MODE SImode
++
++#ifndef NO_IMPLICIT_EXTERN_C
++#define NO_IMPLICIT_EXTERN_C
++#endif
++
++#define STORE_FLAG_VALUE 1
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lm32.md gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.md
+--- gcc-4.4.2.orig/gcc/config/lm32/lm32.md 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.md 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,1233 @@
++;; Machine description of the Lattice Mico32 architecture for GNU C compiler.
++;; Contributed by Jon Beniston <jon@beniston.com>
++
++;; This file is part of GCC.
++
++;; GCC 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 3, or (at your
++;; option) any later version.
++
++;; GCC 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 GCC; see the file COPYING3. If not see
++;; <http://www.gnu.org/licenses/>.
++
++;; Include predicate definitions
++(include "predicates.md")
++
++;; Register numbers
++(define_constants
++ [(RA_REGNUM 29) ; return address register.
++ ]
++)
++
++;; LM32 specific volatile operations
++(define_constants
++ [(UNSPECV_BLOCKAGE 1)] ; use to prevent scheduler from optimising accross bounaries
++)
++
++;; LM32 specific operations
++(define_constants
++ [(UNSPEC_GOT 2)
++ (UNSPEC_GOTOFF_HI16 3)
++ (UNSPEC_GOTOFF_LO16 4)]
++)
++
++;; ---------------------------------
++;; instruction types
++;; ---------------------------------
++
++(define_attr "type"
++ "unknown,load,store,arith,compare,shift,multiply,divide,call,icall,ubranch,uibranch,cbranch"
++ (const_string "unknown"))
++
++;; ---------------------------------
++;; instruction lengths
++;; ---------------------------------
++
++; All instructions are 4 bytes
++; Except for branches that are out of range, and have to be implemented
++; as two instructions
++(define_attr "length" ""
++ (cond [
++ (eq_attr "type" "cbranch")
++ (if_then_else
++ (lt (abs (minus (match_dup 2) (pc)))
++ (const_int 32768)
++ )
++ (const_int 4)
++ (const_int 8)
++ )
++ ]
++ (const_int 4))
++)
++
++;; ---------------------------------
++;; scheduling
++;; ---------------------------------
++
++(define_automaton "lm32")
++
++(define_cpu_unit "x" "lm32")
++(define_cpu_unit "m" "lm32")
++(define_cpu_unit "w" "lm32")
++
++(define_insn_reservation "singlecycle" 1
++ (eq_attr "type" "store,arith,call,icall,ubranch,uibranch,cbranch")
++ "x")
++
++(define_insn_reservation "twocycle" 2
++ (eq_attr "type" "compare,shift,divide")
++ "x,m")
++
++(define_insn_reservation "threecycle" 3
++ (eq_attr "type" "load,multiply")
++ "x,m,w")
++
++;; ---------------------------------
++;; mov
++;; ---------------------------------
++
++(define_expand "movqi"
++ [(set (match_operand:QI 0 "general_operand" "")
++ (match_operand:QI 1 "general_operand" ""))]
++ ""
++ "
++{
++ if (can_create_pseudo_p ())
++ {
++ if (GET_CODE (operand0) == MEM)
++ {
++ /* Source operand for store must be in a register */
++ operands[1] = force_reg (QImode, operands[1]);
++ }
++ }
++ if ( GET_CODE (operands[1]) == CONST_INT
++ && GET_CODE (operands[0]) == REG)
++ {
++ operands[0] = gen_rtx_SUBREG (SImode, operands[0], 0);
++ emit_insn (gen_movsi (operands[0], operands[1]));
++ DONE;
++ }
++}")
++
++(define_expand "movhi"
++ [(set (match_operand:HI 0 "general_operand" "")
++ (match_operand:HI 1 "general_operand" ""))]
++ ""
++ "
++{
++ if (can_create_pseudo_p ())
++ {
++ if (GET_CODE (operands[0]) == MEM)
++ {
++ /* Source operand for store must be in a register */
++ operands[1] = force_reg (HImode, operands[1]);
++ }
++ }
++ if (GET_CODE (operands[1]) == CONST_INT)
++ {
++ operands[0] = gen_rtx_SUBREG (SImode, operands[0], 0);
++ if (MEDIUM_INT (INTVAL (operands[1])))
++ emit_insn (gen_movsi_kimm (operands[0], operands[1]));
++ else if (MEDIUM_UINT (INTVAL (operands[1])))
++ emit_insn (gen_movsi_limm (operands[0], operands[1]));
++ else
++ {
++ emit_insn (gen_movsi_imm_hi (operands[0], GEN_INT (INTVAL (operands[1]))));
++ emit_insn (gen_movsi_imm_lo (operands[0], operands[0], GEN_INT (INTVAL (operands[1]))));
++ }
++ DONE;
++ }
++}")
++
++(define_expand "movsi"
++ [(set (match_operand:SI 0 "general_operand" "")
++ (match_operand:SI 1 "general_operand" ""))]
++ ""
++ "
++{
++ if (can_create_pseudo_p ())
++ {
++ if (GET_CODE (operands[0]) == MEM
++ || (GET_CODE (operands[0]) == SUBREG
++ && GET_CODE (SUBREG_REG (operands[0])) == MEM))
++ {
++ /* Source operand for store must be in a register */
++ operands[1] = force_reg (SImode, operands[1]);
++ }
++ }
++
++ if (flag_pic && symbolic_operand (operands[1], SImode))
++ {
++ if (GET_CODE (operands[1]) == LABEL_REF
++ || (GET_CODE (operands[1]) == SYMBOL_REF
++ && SYMBOL_REF_LOCAL_P (operands[1])
++ && !SYMBOL_REF_WEAK (operands[1])))
++ {
++ emit_insn (gen_movsi_gotoff_hi16 (operands[0], operands[1]));
++ emit_insn (gen_addsi3 (operands[0], operands[0], pic_offset_table_rtx));
++ emit_insn (gen_movsi_gotoff_lo16 (operands[0], operands[0], operands[1]));
++ }
++ else
++ {
++ emit_insn (gen_movsi_got (operands[0], operands[1]));
++ }
++ crtl->uses_pic_offset_table = 1;
++ DONE;
++ }
++ else if (flag_pic && GET_CODE (operands[1]) == CONST)
++ {
++ rtx op = XEXP (operands[1], 0);
++ if (GET_CODE (op) == PLUS)
++ {
++ rtx arg0 = XEXP (op, 0);
++ rtx arg1 = XEXP (op, 1);
++ if (GET_CODE (arg0) == LABEL_REF
++ || (GET_CODE (arg0) == SYMBOL_REF
++ && SYMBOL_REF_LOCAL_P (arg0)
++ && !SYMBOL_REF_WEAK (arg0)))
++ {
++ emit_insn (gen_movsi_gotoff_hi16 (operands[0], arg0));
++ emit_insn (gen_addsi3 (operands[0], operands[0], pic_offset_table_rtx));
++ emit_insn (gen_movsi_gotoff_lo16 (operands[0], operands[0], arg0));
++ }
++ else
++ {
++ emit_insn (gen_movsi_got (operands[0], arg0));
++ }
++ emit_insn (gen_addsi3 (operands[0], operands[0], arg1));
++ crtl->uses_pic_offset_table = 1;
++ DONE;
++ }
++ }
++ else if (!flag_pic && ( GET_CODE (operands[1]) == SYMBOL_REF
++ && SYMBOL_REF_SMALL_P (operands[1])
++ )
++ )
++ {
++ emit_insn (gen_movsi_reloc_gprel (operands[0], operands[1]));
++ DONE;
++ }
++ else if (!flag_pic && ( GET_CODE (operands[1]) == LABEL_REF
++ || GET_CODE (operands[1]) == SYMBOL_REF
++ || GET_CODE (operands[1]) == CONST
++ )
++ )
++ {
++ emit_insn (gen_movsi_reloc_hi (operands[0], operands[1]));
++ emit_insn (gen_movsi_reloc_lo (operands[0], operands[0], operands[1]));
++ DONE;
++ }
++ else if (GET_CODE (operands[1]) == CONST_INT)
++ {
++ if (MEDIUM_INT (INTVAL (operands[1])))
++ emit_insn (gen_movsi_kimm (operands[0], operands[1]));
++ else if (MEDIUM_UINT (INTVAL (operands[1])))
++ emit_insn (gen_movsi_limm (operands[0], operands[1]));
++ else
++ {
++ emit_insn (gen_movsi_imm_hi (operands[0], GEN_INT (INTVAL (operands[1]))));
++ emit_insn (gen_movsi_imm_lo (operands[0], operands[0], GEN_INT (INTVAL (operands[1]))));
++ }
++ DONE;
++ }
++}")
++
++;;(define_expand "movmemsi"
++;; [(parallel [(set (match_operand:BLK 0 "general_operand" "")
++;; (match_operand:BLK 1 "general_operand" ""))
++;; (use (match_operand:SI 2 "" ""))
++;; (use (match_operand:SI 3 "const_int_operand" ""))])]
++;; ""
++;;{
++;; if (!lm32_expand_block_move (operands))
++;; FAIL;
++;; DONE;
++;;})
++
++;; ---------------------------------
++;; load/stores/moves
++;; ---------------------------------
++
++(define_insn "movsi_kimm"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (match_operand:SI 1 "constant_K_operand" "K"))]
++ ""
++ "addi %0, r0, %1"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_limm"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (match_operand:SI 1 "constant_L_operand" "L"))]
++ ""
++ "ori %0, r0, %1"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_imm_hi"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (high:SI (match_operand:SI 1 "immediate_operand" "i")))]
++ ""
++ "orhi %0, r0, hi(%1)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_imm_lo"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (lo_sum:SI (match_operand:SI 1 "register_operand" "0")
++ (match_operand:SI 2 "immediate_operand" "i")))]
++ ""
++ "ori %0, %0, lo(%2)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_reloc_gprel"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (match_operand:SI 1 "reloc_operand" "i"))]
++ "GET_CODE (operands[1]) == SYMBOL_REF && SYMBOL_REF_SMALL_P (operands[1])"
++ "mva %0, gp(%1)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_got"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (unspec:SI [(match_operand 1 "" "")] UNSPEC_GOT))]
++ "flag_pic"
++ "lw %0, (gp+got(%1))"
++ [(set_attr "type" "load")]
++)
++
++(define_insn "movsi_gotoff_hi16"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (unspec:SI [(match_operand 1 "" "")] UNSPEC_GOTOFF_HI16))]
++ "flag_pic"
++ "orhi %0, r0, gotoffhi16(%1)"
++ [(set_attr "type" "load")]
++)
++
++(define_insn "movsi_gotoff_lo16"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (unspec:SI [(plus:SI (match_operand:SI 1 "register_operand" "0")
++ (match_operand 2 "" ""))] UNSPEC_GOTOFF_LO16))]
++ "flag_pic"
++ "addi %0, %1, gotofflo16(%2)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_reloc_hi"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (high:SI (match_operand:SI 1 "reloc_operand" "i")))]
++ "!flag_pic"
++ "orhi %0, r0, hi(%1)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "movsi_reloc_lo"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (lo_sum:SI (match_operand:SI 1 "register_operand" "0")
++ (match_operand:SI 2 "reloc_operand" "i")))]
++ "!flag_pic"
++ "ori %0, %0, lo(%2)"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "*movqi_insn"
++ [(set (match_operand:QI 0 "register_or_memory_operand" "=r,r,m")
++ (match_operand:QI 1 "register_or_memory_operand" "m,r,r"))]
++ ""
++ "@
++ lbu %0, %1
++ or %0, %1, r0
++ sb %0, %1"
++ [(set_attr "type" "load,arith,store")]
++)
++
++(define_insn "*movhi_insn"
++ [(set (match_operand:HI 0 "register_or_memory_operand" "=r,r,m")
++ (match_operand:HI 1 "register_or_memory_operand" "m,r,r"))]
++ ""
++ "@
++ lhu %0, %1
++ or %0, %1, r0
++ sh %0, %1"
++ [(set_attr "type" "load,arith,store")]
++)
++
++(define_insn "*movsi_insn"
++ [(set (match_operand:SI 0 "register_or_memory_operand" "=r,r,m")
++ (match_operand:SI 1 "register_or_memory_operand" "m,r,r"))]
++ ""
++ "@
++ lw %0, %1
++ or %0, %1, r0
++ sw %0, %1"
++ [(set_attr "type" "load,arith,store")]
++)
++
++;; ---------------------------------
++;; sign and zero extension
++;; ---------------------------------
++
++(define_insn "*extendqihi2"
++ [(set (match_operand:HI 0 "register_operand" "=r,r")
++ (sign_extend:HI (match_operand:QI 1 "register_or_memory_operand" "m,r")))]
++ "TARGET_SIGN_EXTEND_ENABLED || (GET_CODE (operands[1]) != REG)"
++ "@
++ lb %0, %1
++ sextb %0, %1"
++ [(set_attr "type" "load,arith")]
++)
++
++(define_insn "zero_extendqihi2"
++ [(set (match_operand:HI 0 "register_operand" "=r,r")
++ (zero_extend:HI (match_operand:QI 1 "register_or_memory_operand" "m,r")))]
++ ""
++ "@
++ lbu %0, %1
++ andi %0, %1, 0xff"
++ [(set_attr "type" "load,arith")]
++)
++
++(define_insn "*extendqisi2"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (sign_extend:SI (match_operand:QI 1 "register_or_memory_operand" "m,r")))]
++ "TARGET_SIGN_EXTEND_ENABLED || (GET_CODE (operands[1]) != REG)"
++ "@
++ lb %0, %1
++ sextb %0, %1"
++ [(set_attr "type" "load,arith")]
++)
++
++(define_insn "zero_extendqisi2"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (zero_extend:SI (match_operand:QI 1 "register_or_memory_operand" "m,r")))]
++ ""
++ "@
++ lbu %0, %1
++ andi %0, %1, 0xff"
++ [(set_attr "type" "load,arith")]
++)
++
++(define_insn "*extendhisi2"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (sign_extend:SI (match_operand:HI 1 "register_or_memory_operand" "m,r")))]
++ "TARGET_SIGN_EXTEND_ENABLED || (GET_CODE (operands[1]) != REG)"
++ "@
++ lh %0, %1
++ sexth %0, %1"
++ [(set_attr "type" "load,arith")]
++)
++
++(define_insn "zero_extendhisi2"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (zero_extend:SI (match_operand:HI 1 "register_or_memory_operand" "m,r")))]
++ ""
++ "@
++ lhu %0, %1
++ andi %0, %1, 0xffff"
++ [(set_attr "type" "load,arith")]
++)
++
++;; ---------------------------------
++;; compare
++;; ---------------------------------
++
++(define_expand "cmpsi"
++ [(set (cc0)
++ (compare:CC (match_operand:SI 0 "register_operand" "")
++ (match_operand:SI 1 "register_or_K_operand" "")))]
++ ""
++ "
++{
++ lm32_compare_op0 = operands[0];
++ lm32_compare_op1 = operands[1];
++ DONE;
++}")
++
++
++(define_expand "tstsi"
++ [(set (cc0)
++ (match_operand:SI 0 "register_operand" ""))]
++ ""
++ "
++{
++ lm32_compare_op0 = operands[0];
++ lm32_compare_op1 = const0_rtx;
++ DONE;
++}")
++
++(define_expand "seq"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (eq:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (EQ, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*seq"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (eq:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ ""
++ "@
++ cmpe %0, %z1, %2
++ cmpei %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "sne"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (ne:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (NE, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*sne"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (ne:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ ""
++ "@
++ cmpne %0, %z1, %2
++ cmpnei %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "sgt"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (gt:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (GT, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*sgt"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (gt:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ ""
++ "@
++ cmpg %0, %z1, %2
++ cmpgi %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "slt"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (lt:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (LT, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_expand "sge"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (ge:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (GE, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*sge"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (ge:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ ""
++ "@
++ cmpge %0, %z1, %2
++ cmpgei %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "sle"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (le:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (LE, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_expand "sgtu"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (gtu:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (GTU, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*sgtu"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (gtu:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,L")))]
++ ""
++ "@
++ cmpgu %0, %z1, %2
++ cmpgui %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "sltu"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (ltu:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (LTU, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_expand "sgeu"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (geu:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (GEU, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++(define_insn "*sgeu"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (geu:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,L")))]
++ ""
++ "@
++ cmpgeu %0, %z1, %2
++ cmpgeui %0, %z1, %2"
++ [(set_attr "type" "compare")]
++)
++
++(define_expand "sleu"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (leu:SI (match_dup 1)
++ (match_dup 2)))]
++ ""
++{
++ operands[1] = lm32_compare_op0;
++ operands[2] = lm32_compare_op1;
++ gen_int_relational (LEU, operands[0], operands[1], operands[2], NULL_RTX);
++ DONE;
++})
++
++;; ---------------------------------
++;; unconditional branch
++;; ---------------------------------
++
++(define_insn "jump"
++ [(set (pc) (label_ref (match_operand 0 "" "")))]
++ ""
++ "bi %0"
++ [(set_attr "type" "ubranch")]
++)
++
++(define_expand "indirect_jump"
++ [(set (pc) (match_operand 0 "register_operand" ""))]
++ ""
++ "
++{
++ emit_jump_insn (gen_indirect_jumpsi (operands[0]));
++ DONE;
++}")
++
++(define_insn "indirect_jumpsi"
++ [(set (pc) (match_operand:SI 0 "register_operand" "r"))]
++ ""
++ "b %0"
++ [(set_attr "type" "uibranch")]
++)
++
++;; ---------------------------------
++;; conditional branch
++;; ---------------------------------
++
++(define_expand "beq"
++ [(set (pc)
++ (if_then_else (eq:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (EQ, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bne"
++ [(set (pc)
++ (if_then_else (ne:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (NE, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bgt"
++ [(set (pc)
++ (if_then_else (gt:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (GT, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bge"
++ [(set (pc)
++ (if_then_else (ge:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (GE, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "ble"
++ [(set (pc)
++ (if_then_else (le:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (LE, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "blt"
++ [(set (pc)
++ (if_then_else (lt:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (LT, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bgtu"
++ [(set (pc)
++ (if_then_else (gtu:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (GTU, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bgeu"
++ [(set (pc)
++ (if_then_else (geu:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (GEU, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bleu"
++ [(set (pc)
++ (if_then_else (leu:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (LEU, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_expand "bltu"
++ [(set (pc)
++ (if_then_else (ltu:CC (cc0)
++ (const_int 0))
++ (label_ref (match_operand 0 "" ""))
++ (pc)))]
++ ""
++ "
++{
++ gen_int_relational (LTU, NULL_RTX, lm32_compare_op0, lm32_compare_op1, operands[0]);
++ DONE;
++}")
++
++(define_insn "*beq"
++ [(set (pc)
++ (if_then_else (eq:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "be %z0,%z1,%2"
++ : "bne %z0,%z1,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++(define_insn "*bne"
++ [(set (pc)
++ (if_then_else (ne:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "bne %z0,%z1,%2"
++ : "be %z0,%z1,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++(define_insn "*bgt"
++ [(set (pc)
++ (if_then_else (gt:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "bg %z0,%z1,%2"
++ : "bge %z1,%z0,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++(define_insn "*bge"
++ [(set (pc)
++ (if_then_else (ge:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "bge %z0,%z1,%2"
++ : "bg %z1,%z0,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++(define_insn "*bgtu"
++ [(set (pc)
++ (if_then_else (gtu:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "bgu %z0,%z1,%2"
++ : "bgeu %z1,%z0,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++(define_insn "*bgeu"
++ [(set (pc)
++ (if_then_else (geu:SI (match_operand:SI 0 "register_or_zero_operand" "rJ")
++ (match_operand:SI 1 "register_or_zero_operand" "rJ"))
++ (label_ref (match_operand 2 "" ""))
++ (pc)))]
++ ""
++{
++ return get_attr_length (insn) == 4
++ ? "bgeu %z0,%z1,%2"
++ : "bgu %z1,%z0,8\n\tbi %2";
++}
++ [(set_attr "type" "cbranch")])
++
++;; ---------------------------------
++;; call
++;; ---------------------------------
++
++(define_expand "call"
++ [(parallel [(call (match_operand 0 "memory_operand" "m")
++ (match_operand 1 "" ""))
++ (clobber (reg:SI RA_REGNUM))
++ ])]
++ ""
++ "
++{
++ rtx addr = XEXP (operands[0], 0);
++ if (!CONSTANT_ADDRESS_P (addr))
++ {
++ emit_call_insn (gen_call_via_regsi (addr, operands[1]));
++ DONE;
++ }
++}")
++
++(define_insn "call_via_regsi"
++ [(call (mem:SI (match_operand:SI 0 "register_operand" "r"))
++ (match_operand 1 "" ""))
++ (clobber (reg:SI RA_REGNUM))]
++ ""
++ "call %0"
++ [(set_attr "type" "icall")]
++)
++
++(define_insn "*call_via_labelsi"
++ [(call (mem:SI (match_operand:SI 0 "symbolic_operand" "X"))
++ (match_operand 1 "" ""))
++ (clobber (reg:SI RA_REGNUM))]
++ ""
++ "calli %0"
++ [(set_attr "type" "call")]
++)
++
++(define_expand "call_value"
++ [(parallel [(set (match_operand 0 "register_operand" "=r")
++ (call (match_operand 1 "memory_operand" "m")
++ (match_operand 2 "" "")))
++ (clobber (reg:SI RA_REGNUM))
++ ])]
++ ""
++ "
++{
++ rtx addr = XEXP (operands[1], 0);
++ if (!CONSTANT_ADDRESS_P (addr))
++ {
++ emit_call_insn (gen_call_value_via_regsi (operands[0], addr, operands[2]));
++ DONE;
++ }
++}")
++
++(define_insn "call_value_via_regsi"
++ [(set (match_operand 0 "register_operand" "=r")
++ (call (mem:SI (match_operand:SI 1 "register_operand" "r"))
++ (match_operand 2 "" "")))
++ (clobber (reg:SI RA_REGNUM))]
++ ""
++ "call %1"
++ [(set_attr "type" "icall")]
++)
++
++(define_insn "*call_value_via_labelsi"
++ [(set (match_operand 0 "register_operand" "=r")
++ (call (mem:SI (match_operand:SI 1 "symbolic_operand" "X"))
++ (match_operand 2 "" "")))
++ (clobber (reg:SI RA_REGNUM))]
++ ""
++ "calli %1"
++ [(set_attr "type" "call")]
++)
++
++(define_insn "return_internalsi"
++ [(use (match_operand:SI 0 "register_operand" "r"))
++ (return)]
++ ""
++ "b %0"
++ [(set_attr "type" "uibranch")]
++)
++
++(define_insn "return"
++ [(return)]
++ "lm32_can_use_return ()"
++ "ret"
++ [(set_attr "type" "uibranch")]
++)
++
++;; ---------------------------------
++;; switch/case statements
++;; ---------------------------------
++
++(define_expand "tablejump"
++ [(set (pc) (match_operand 0 "register_operand" ""))
++ (use (label_ref (match_operand 1 "" "")))]
++ ""
++ "
++{
++ rtx target = operands[0];
++ if (flag_pic)
++ {
++ /* For PIC, the table entry is relative to the start of the table. */
++ rtx label = gen_reg_rtx (SImode);
++ target = gen_reg_rtx (SImode);
++ emit_move_insn (label, gen_rtx_LABEL_REF (SImode, operands[1]));
++ emit_insn (gen_addsi3 (target, operands[0], label));
++ }
++ emit_jump_insn (gen_tablejumpsi (target, operands[1]));
++ DONE;
++}")
++
++(define_insn "tablejumpsi"
++ [(set (pc) (match_operand:SI 0 "register_operand" "r"))
++ (use (label_ref (match_operand 1 "" "")))]
++ ""
++ "b %0"
++ [(set_attr "type" "ubranch")]
++)
++
++;; ---------------------------------
++;; arithmetic
++;; ---------------------------------
++
++(define_insn "addsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (plus:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ ""
++ "@
++ add %0, %z1, %2
++ addi %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "subsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (minus:SI (match_operand:SI 1 "register_or_zero_operand" "rJ")
++ (match_operand:SI 2 "register_or_zero_operand" "rJ")))]
++ ""
++ "sub %0, %z1, %z2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "mulsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (mult:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_K_operand" "r,K")))]
++ "TARGET_MULTIPLY_ENABLED"
++ "@
++ mul %0, %z1, %2
++ muli %0, %z1, %2"
++ [(set_attr "type" "multiply")]
++)
++
++(define_insn "udivsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (udiv:SI (match_operand:SI 1 "register_or_zero_operand" "rJ")
++ (match_operand:SI 2 "register_operand" "r")))]
++ "TARGET_DIVIDE_ENABLED"
++ "divu %0, %z1, %2"
++ [(set_attr "type" "divide")]
++)
++
++(define_insn "umodsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (umod:SI (match_operand:SI 1 "register_or_zero_operand" "rJ")
++ (match_operand:SI 2 "register_operand" "r")))]
++ "TARGET_DIVIDE_ENABLED"
++ "modu %0, %z1, %2"
++ [(set_attr "type" "divide")]
++)
++
++;; ---------------------------------
++;; negation and inversion
++;; ---------------------------------
++
++(define_insn "negsi2"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (neg:SI (match_operand:SI 1 "register_or_zero_operand" "rJ")))]
++ ""
++ "sub %0, r0, %z1"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "one_cmplsi2"
++ [(set (match_operand:SI 0 "register_operand" "=r")
++ (not:SI (match_operand:SI 1 "register_or_zero_operand" "rJ")))]
++ ""
++ "not %0, %z1"
++ [(set_attr "type" "arith")]
++)
++
++;; ---------------------------------
++;; logical
++;; ---------------------------------
++
++(define_insn "andsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (and:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ ""
++ "@
++ and %0, %z1, %2
++ andi %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "iorsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (ior:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ ""
++ "@
++ or %0, %z1, %2
++ ori %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "xorsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (xor:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ ""
++ "@
++ xor %0, %z1, %2
++ xori %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "*norsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (not:SI (ior:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L"))))]
++ ""
++ "@
++ nor %0, %z1, %2
++ nori %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++(define_insn "*xnorsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (not:SI (xor:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L"))))]
++ ""
++ "@
++ xnor %0, %z1, %2
++ xnori %0, %z1, %2"
++ [(set_attr "type" "arith")]
++)
++
++;; ---------------------------------
++;; shifts
++;; ---------------------------------
++
++(define_insn "ashlsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (ashift:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ "TARGET_BARREL_SHIFT_ENABLED"
++ "@
++ sl %0, %z1, %2
++ sli %0, %z1, %2"
++ [(set_attr "type" "shift")]
++)
++
++(define_insn "ashrsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (ashiftrt:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ "TARGET_BARREL_SHIFT_ENABLED"
++ "@
++ sr %0, %z1, %2
++ sri %0, %z1, %2"
++ [(set_attr "type" "shift")]
++)
++
++(define_insn "lshrsi3"
++ [(set (match_operand:SI 0 "register_operand" "=r,r")
++ (lshiftrt:SI (match_operand:SI 1 "register_or_zero_operand" "rJ,rJ")
++ (match_operand:SI 2 "register_or_L_operand" "r,L")))]
++ "TARGET_BARREL_SHIFT_ENABLED"
++ "@
++ sru %0, %z1, %2
++ srui %0, %z1, %2"
++ [(set_attr "type" "shift")]
++)
++
++;; ---------------------------------
++;; function entry / exit
++;; ---------------------------------
++
++(define_expand "prologue"
++ [(const_int 1)]
++ ""
++ "
++{
++ lm32_expand_prologue ();
++ DONE;
++}")
++
++(define_expand "epilogue"
++ [(return)]
++ ""
++ "
++{
++ lm32_expand_epilogue ();
++ DONE;
++}")
++
++;; ---------------------------------
++;; nop
++;; ---------------------------------
++
++(define_insn "nop"
++ [(const_int 0)]
++ ""
++ "nop"
++ [(set_attr "type" "arith")]
++)
++
++;; ---------------------------------
++;; blockage
++;; ---------------------------------
++
++;; used to stop the scheduler from
++;; scheduling code across certain boundaries
++
++(define_insn "blockage"
++ [(unspec_volatile [(const_int 0)] UNSPECV_BLOCKAGE)]
++ ""
++ ""
++ [(set_attr "length" "0")]
++)
++
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lm32.opt gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.opt
+--- gcc-4.4.2.orig/gcc/config/lm32/lm32.opt 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32.opt 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,40 @@
++; Options for the Lattice Mico32 port of the compiler.
++; Contributed by Jon Beniston <jon@beniston.com>
++;
++; Copyright (C) 2008 Free Software Foundation, Inc.
++;
++; This file is part of GCC.
++;
++; GCC 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 3, or (at your
++; option) any later version.
++;
++; GCC 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 GCC; see the file COPYING3. If not see
++; <http://www.gnu.org/licenses/>.
++
++mmultiply-enabled
++Target Report Mask(MULTIPLY_ENABLED)
++Enable multiply instructions
++
++mdivide-enabled
++Target Report Mask(DIVIDE_ENABLED)
++Enable divide and modulus instructions
++
++mbarrel-shift-enabled
++Target Report Mask(BARREL_SHIFT_ENABLED)
++Enable barrel shift instructions
++
++msign-extend-enabled
++Target Report Mask(SIGN_EXTEND_ENABLED)
++Enable sign extend instructions
++
++muser-enabled
++Target Report Mask(USER_ENABLED)
++Enable user-defined instructions
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/lm32-protos.h gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32-protos.h
+--- gcc-4.4.2.orig/gcc/config/lm32/lm32-protos.h 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/lm32-protos.h 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,52 @@
++/* Prototypes of target machine functions, Lattice Mico32 architecture.
++ Contributed by Jon Beniston <jon@beniston.com>
++
++ Copyright (C) 2008 Free Software Foundation, Inc.
++
++ This file is part of GCC.
++
++ GCC 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 3, or (at your
++ option) any later version.
++
++ GCC 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 GCC; see the file COPYING3. If not see
++ <http://www.gnu.org/licenses/>. */
++
++extern int lm32_return_in_memory (tree type);
++extern void lm32_declare_object (FILE *stream, char *name, char *init_string,
++ char *final_string, int size);
++extern int symbolic_operand (rtx op, enum machine_mode mode ATTRIBUTE_UNUSED);
++extern int register_or_zero_operand (rtx op, enum machine_mode mode);
++extern int register_or_K_operand (rtx op, enum machine_mode mode);
++extern int constant_K_operand (rtx op, enum machine_mode mode ATTRIBUTE_UNUSED);
++extern int register_or_L_operand (rtx op, enum machine_mode mode);
++extern int constant_L_operand (rtx op, enum machine_mode mode ATTRIBUTE_UNUSED);
++extern int register_or_memory_operand (rtx op, enum machine_mode mode);
++extern int register_operand (rtx op, enum machine_mode mode);
++extern int const_ok_for_base_offset (rtx op, enum machine_mode mode);
++extern void lm32_expand_prologue (void);
++extern void lm32_expand_epilogue (void);
++extern HOST_WIDE_INT lm32_compute_frame_size (int size);
++extern void lm32_print_operand (FILE *file, rtx op, int letter);
++extern void lm32_print_operand_address (FILE *file, rtx addr);
++extern rtx lm32_function_arg (CUMULATIVE_ARGS cum, enum machine_mode mode,
++ tree type, int named);
++extern void lm32_override_options (void);
++extern HOST_WIDE_INT lm32_compute_initial_elimination_offset (int from,
++ int to);
++extern int lm32_can_use_return (void);
++extern rtx lm32_return_addr_rtx (int count, rtx frame);
++#ifdef RTX_CODE
++extern void gen_int_relational (enum rtx_code code, rtx result, rtx cmp0,
++ rtx cmp1, rtx destination);
++#endif
++extern int lm32_expand_block_move (rtx *);
++extern int nonpic_symbol_mentioned_p (rtx);
++extern rtx lm32_legitimize_pic_address (rtx, enum machine_mode, rtx);
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/predicates.md gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/predicates.md
+--- gcc-4.4.2.orig/gcc/config/lm32/predicates.md 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/predicates.md 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,58 @@
++;; Predicate definitions for Lattice Mico32.
++;; Contributed by Jon Beniston <jon@beniston.com>
++;;
++;; Copyright (C) 2008 Free Software Foundation, Inc.
++;;
++;; This file is part of GCC.
++;;
++;; GCC 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 3, or (at your
++;; option) any later version.
++;;
++;; GCC 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 GCC; see the file COPYING3. If not see
++;; <http://www.gnu.org/licenses/>.
++
++(define_predicate "const0_operand"
++ (and (match_code "const_int,const_double,const_vector")
++ (match_test "op == CONST0_RTX (GET_MODE (op))")))
++
++(define_predicate "constant_K_operand"
++ (and (match_code "const_int")
++ (match_test "MEDIUM_INT (INTVAL (op))")))
++
++(define_predicate "constant_L_operand"
++ (and (match_code "const_int")
++ (match_test "MEDIUM_UINT (INTVAL (op))")))
++
++(define_predicate "register_or_zero_operand"
++ (ior (match_operand 0 "register_operand")
++ (match_operand 0 "const0_operand")))
++
++(define_predicate "register_or_memory_operand"
++ (ior (match_operand 0 "register_operand")
++ (match_operand 0 "memory_operand")))
++
++(define_predicate "register_or_K_operand"
++ (ior (match_operand 0 "register_operand")
++ (match_operand 0 "constant_K_operand")))
++
++(define_predicate "register_or_L_operand"
++ (ior (match_operand 0 "register_operand")
++ (match_operand 0 "constant_L_operand")))
++
++(define_predicate "reloc_operand"
++ (ior (ior (match_code "label_ref")
++ (match_code "symbol_ref"))
++ (match_code "const")))
++
++(define_predicate "symbolic_operand"
++ (ior (match_code "label_ref")
++ (match_code "symbol_ref")))
++
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/rtems.h gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/rtems.h
+--- gcc-4.4.2.orig/gcc/config/lm32/rtems.h 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/rtems.h 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,32 @@
++/* Definitions for rtems targeting a lm32 using ELF.
++ Copyright (C) 2009, Free Software Foundation, Inc.
++
++This file is part of GCC.
++
++GCC 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 3, or (at your option)
++any later version.
++
++GCC 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 GCC; see the file COPYING3. If not see
++<http://www.gnu.org/licenses/>. */
++
++/* Target OS builtins. */
++#undef TARGET_OS_CPP_BUILTINS
++#define TARGET_OS_CPP_BUILTINS() \
++ do \
++ { \
++ builtin_define ("__rtems__"); \
++ builtin_define ("__USE_INIT_FINI__"); \
++ builtin_assert ("system=rtems"); \
++ } \
++ while (0)
++
++/* Use the default */
++#undef LINK_GCC_C_SEQUENCE_SPEC
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/sfp-machine.h gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/sfp-machine.h
+--- gcc-4.4.2.orig/gcc/config/lm32/sfp-machine.h 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/sfp-machine.h 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,51 @@
++#define _FP_W_TYPE_SIZE 32
++#define _FP_W_TYPE unsigned long
++#define _FP_WS_TYPE signed long
++#define _FP_I_TYPE long
++
++#define _FP_MUL_MEAT_S(R,X,Y) \
++ _FP_MUL_MEAT_1_wide(_FP_WFRACBITS_S,R,X,Y,umul_ppmm)
++#define _FP_MUL_MEAT_D(R,X,Y) \
++ _FP_MUL_MEAT_2_wide(_FP_WFRACBITS_D,R,X,Y,umul_ppmm)
++#define _FP_MUL_MEAT_Q(R,X,Y) \
++ _FP_MUL_MEAT_4_wide(_FP_WFRACBITS_Q,R,X,Y,umul_ppmm)
++
++#define _FP_DIV_MEAT_S(R,X,Y) _FP_DIV_MEAT_1_loop(S,R,X,Y)
++#define _FP_DIV_MEAT_D(R,X,Y) _FP_DIV_MEAT_2_udiv(D,R,X,Y)
++#define _FP_DIV_MEAT_Q(R,X,Y) _FP_DIV_MEAT_4_udiv(Q,R,X,Y)
++
++#define _FP_NANFRAC_S ((_FP_QNANBIT_S << 1) - 1)
++#define _FP_NANFRAC_D ((_FP_QNANBIT_D << 1) - 1), -1
++#define _FP_NANFRAC_Q ((_FP_QNANBIT_Q << 1) - 1), -1, -1, -1
++#define _FP_NANSIGN_S 0
++#define _FP_NANSIGN_D 0
++#define _FP_NANSIGN_Q 0
++
++#define _FP_KEEPNANFRACP 1
++
++/* Someone please check this. */
++#define _FP_CHOOSENAN(fs, wc, R, X, Y, OP) \
++ do { \
++ if ((_FP_FRAC_HIGH_RAW_##fs(X) & _FP_QNANBIT_##fs) \
++ && !(_FP_FRAC_HIGH_RAW_##fs(Y) & _FP_QNANBIT_##fs)) \
++ { \
++ R##_s = Y##_s; \
++ _FP_FRAC_COPY_##wc(R,Y); \
++ } \
++ else \
++ { \
++ R##_s = X##_s; \
++ _FP_FRAC_COPY_##wc(R,X); \
++ } \
++ R##_c = FP_CLS_NAN; \
++ } while (0)
++
++#define __LITTLE_ENDIAN 1234
++#define __BIG_ENDIAN 4321
++
++#define __BYTE_ORDER __BIG_ENDIAN
++
++/* Define ALIASNAME as a strong alias for NAME. */
++# define strong_alias(name, aliasname) _strong_alias(name, aliasname)
++# define _strong_alias(name, aliasname) \
++ extern __typeof (name) aliasname __attribute__ ((alias (#name)));
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/t-fprules-softfp gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/t-fprules-softfp
+--- gcc-4.4.2.orig/gcc/config/lm32/t-fprules-softfp 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/t-fprules-softfp 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,5 @@
++softfp_float_modes := sf df
++softfp_int_modes := si di
++softfp_extensions := sfdf
++softfp_truncations := dfsf
++softfp_machine_header := lm32/sfp-machine.h
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/t-lm32 gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/t-lm32
+--- gcc-4.4.2.orig/gcc/config/lm32/t-lm32 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/t-lm32 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,19 @@
++LIB1ASMSRC = lm32/lib1funcs.S
++LIB1ASMFUNCS = _ashlsi3 _ashrsi3 _lshrsi3
++
++LM32_LIB1CSRC = $(srcdir)/config/lm32/arithmetic.c
++LIB2FUNCS_EXTRA = _mulsi3.c \
++ _udivmodsi4.c _divsi3.c _modsi3.c _udivsi3.c _umodsi3.c
++# Size optimised versions: _ashlsi3.c _ashrsi3.c _lshrsi3.c
++
++# The fixed-point arithmetic code is in one file
++# similar to libgcc2.c (or the old libgcc1.c). We need to
++# "split it up" with one file per define.
++$(LIB2FUNCS_EXTRA): $(LM32_LIB1CSRC)
++ name=`echo $@ | sed -e 's,.*/,,' | sed -e 's,.c$$,,'`; \
++ echo "#define L$$name" > tmp-$@ \
++ && echo '#include "$<"' >> tmp-$@ \
++ && mv -f tmp-$@ $@
++
++MULTILIB_OPTIONS = mmultiply-enabled mbarrel-shift-enabled
++# Don't bother building multilib with mdivide-enabled, not much of a gain
+diff -Naur gcc-4.4.2.orig/gcc/config/lm32/uclinux-elf.h gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/uclinux-elf.h
+--- gcc-4.4.2.orig/gcc/config/lm32/uclinux-elf.h 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/lm32/uclinux-elf.h 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,85 @@
++/* Definitions for LM32 running Linux-based GNU systems using ELF
++ Copyright (C) 1993, 1994, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
++ 2008 Free Software Foundation, Inc.
++ Contributed by Philip Blundell <philb@gnu.org>
++
++ This file is part of GCC.
++
++ GCC 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 3, or (at your
++ option) any later version.
++
++ GCC 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 GCC; see the file COPYING3. If not see
++ <http://www.gnu.org/licenses/>. */
++
++/* elfos.h should have already been included. Now just override
++ any conflicting definitions and add any extras. */
++
++/* Run-time Target Specification. */
++#undef TARGET_VERSION
++#define TARGET_VERSION fputs (" (LM32 GNU/Linux with ELF)", stderr);
++
++/* Do not assume anything about header files. */
++#undef NO_IMPLICIT_EXTERN_C
++#define NO_IMPLICIT_EXTERN_C
++
++/* The GNU C++ standard library requires that these macros be defined. */
++#undef CPLUSPLUS_CPP_SPEC
++#define CPLUSPLUS_CPP_SPEC "-D_GNU_SOURCE %(cpp)"
++
++/* Now we define the strings used to build the spec file. */
++#undef LIB_SPEC
++#define LIB_SPEC \
++ "%{pthread:-lpthread} \
++ %{shared:-lc} \
++ %{!shared:-lc} "
++
++#define LIBGCC_SPEC "-lgcc"
++
++/* Provide a STARTFILE_SPEC appropriate for GNU/Linux. Here we add
++ the GNU/Linux magical crtbegin.o file (see crtstuff.c) which
++ provides part of the support for getting C++ file-scope static
++ object constructed before entering `main'. */
++
++#undef STARTFILE_SPEC
++#define STARTFILE_SPEC \
++ "%{!shared: \
++ %{pg:gcrt1.o%s} %{!pg:%{p:gcrt1.o%s} \
++ %{!p:%{profile:gcrt1.o%s} \
++ %{!profile:crt1.o%s}}}} \
++ crti.o%s %{!shared:crtbegin.o%s} %{shared:crtbeginS.o%s}"
++
++/* Provide a ENDFILE_SPEC appropriate for GNU/Linux. Here we tack on
++ the GNU/Linux magical crtend.o file (see crtstuff.c) which
++ provides part of the support for getting C++ file-scope static
++ object constructed before entering `main', followed by a normal
++ GNU/Linux "finalizer" file, `crtn.o'. */
++
++#undef ENDFILE_SPEC
++#define ENDFILE_SPEC \
++ "%{!shared:crtend.o%s} %{shared:crtendS.o%s} crtn.o%s"
++
++#undef LINK_SPEC
++#define LINK_SPEC "%{h*} %{version:-v} \
++ %{b} %{Wl,*:%*} \
++ %{static:-Bstatic} \
++ %{shared:-shared} \
++ %{symbolic:-Bsymbolic} \
++ %{rdynamic:-export-dynamic} \
++ %{!dynamic-linker:-dynamic-linker /lib/ld-linux.so.2}"
++
++#define TARGET_OS_CPP_BUILTINS() LINUX_TARGET_OS_CPP_BUILTINS()
++
++#define LINK_GCC_C_SEQUENCE_SPEC \
++ "%{static:--start-group} %G %L %{static:--end-group}%{!static:%G}"
++
++#undef CC1_SPEC
++#define CC1_SPEC "%{G*} %{!fno-PIC:-fPIC}"
++
+diff -Naur gcc-4.4.2.orig/gcc/config/mips/elf.h gcc-4.4.2-rtems4.10-20091015/gcc/config/mips/elf.h
+--- gcc-4.4.2.orig/gcc/config/mips/elf.h 2007-08-02 12:49:31.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/mips/elf.h 2009-10-15 18:36:00.000000000 +0200
+@@ -48,6 +48,4 @@
+ #undef ENDFILE_SPEC
+ #define ENDFILE_SPEC "crtend%O%s crtn%O%s"
+
+-#define NO_IMPLICIT_EXTERN_C 1
+-
+ #define HANDLE_PRAGMA_PACK_PUSH_POP 1
+diff -Naur gcc-4.4.2.orig/gcc/config/rs6000/rtems.h gcc-4.4.2-rtems4.10-20091015/gcc/config/rs6000/rtems.h
+--- gcc-4.4.2.orig/gcc/config/rs6000/rtems.h 2007-08-02 12:49:31.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/rs6000/rtems.h 2009-10-15 18:36:00.000000000 +0200
+@@ -49,8 +49,18 @@
+ %{mcpu=604: %{!Dppc*: %{!Dmpc*: -Dmpc604} } } \
+ %{mcpu=750: %{!Dppc*: %{!Dmpc*: -Dmpc750} } } \
+ %{mcpu=821: %{!Dppc*: %{!Dmpc*: -Dmpc821} } } \
+-%{mcpu=860: %{!Dppc*: %{!Dmpc*: -Dmpc860} } }"
++%{mcpu=860: %{!Dppc*: %{!Dmpc*: -Dmpc860} } } \
++%{mcpu=8540: %{!Dppc*: %{!Dmpc*: -Dppc8540} } }"
+
+ #undef SUBSUBTARGET_EXTRA_SPECS
+ #define SUBSUBTARGET_EXTRA_SPECS \
+ { "cpp_os_rtems", CPP_OS_RTEMS_SPEC }
++
++#undef SUBSUBTARGET_OVERRIDE_OPTIONS
++#define SUBSUBTARGET_OVERRIDE_OPTIONS \
++ do { \
++ if (TARGET_E500) \
++ { \
++ rs6000_float_gprs = 1; \
++ } \
++ } while(0)
+diff -Naur gcc-4.4.2.orig/gcc/config/rs6000/t-rtems gcc-4.4.2-rtems4.10-20091015/gcc/config/rs6000/t-rtems
+--- gcc-4.4.2.orig/gcc/config/rs6000/t-rtems 2009-03-25 13:54:16.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config/rs6000/t-rtems 2009-10-15 18:36:00.000000000 +0200
+@@ -1,12 +1,12 @@
+ # Multilibs for powerpc RTEMS targets.
+
+ MULTILIB_OPTIONS = \
+-mcpu=403/mcpu=505/mcpu=601/mcpu=603e/mcpu=604/mcpu=860/mcpu=7400 \
++mcpu=403/mcpu=505/mcpu=601/mcpu=603e/mcpu=604/mcpu=860/mcpu=7400/mcpu=8540 \
+ Dmpc8260 \
+ msoft-float
+
+ MULTILIB_DIRNAMES = \
+-m403 m505 m601 m603e m604 m860 m7400 \
++m403 m505 m601 m603e m604 m860 m7400 m8540 \
+ mpc8260 \
+ nof
+
+@@ -29,6 +29,10 @@
+ # Map 750 to .
+ MULTILIB_MATCHES += mcpu?750=
+
++# Map e500, 8548 to 8540
++MULTILIB_MATCHES += mcpu?8540=mcpu?e500
++MULTILIB_MATCHES += mcpu?8540=mcpu?8548
++
+ # Soft-float only, default implies msoft-float
+ # NOTE: Must match with MULTILIB_MATCHES_FLOAT and MULTILIB_MATCHES
+ MULTILIB_SOFTFLOAT_ONLY = \
+@@ -62,3 +66,4 @@
+ MULTILIB_EXCEPTIONS += *mcpu=750/Dmpc*
+ MULTILIB_EXCEPTIONS += *mcpu=860/Dmpc*
+ MULTILIB_EXCEPTIONS += *mcpu=7400/Dmpc*
++MULTILIB_EXCEPTIONS += *mcpu=8540/Dmpc*
+diff -Naur gcc-4.4.2.orig/gcc/config.gcc gcc-4.4.2-rtems4.10-20091015/gcc/config.gcc
+--- gcc-4.4.2.orig/gcc/config.gcc 2009-09-13 15:01:13.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config.gcc 2009-10-15 18:36:00.000000000 +0200
+@@ -1364,6 +1364,23 @@
+ out_file=iq2000/iq2000.c
+ md_file=iq2000/iq2000.md
+ ;;
++lm32-*-elf*)
++ tm_file="dbxelf.h elfos.h ${tm_file}"
++ tmake_file="lm32/t-lm32"
++ tmake_file="${tmake_file} lm32/t-fprules-softfp soft-fp/t-softfp"
++ ;;
++lm32-*-rtems*)
++ tm_file="dbxelf.h elfos.h ${tm_file} lm32/rtems.h rtems.h"
++ tmake_file="lm32/t-lm32"
++ tmake_file="${tmake_file} lm32/t-fprules-softfp soft-fp/t-softfp"
++ tmake_file="${tmake_file} t-rtems"
++ extra_parts="crtbegin.o crtend.o crti.o crtn.o"
++ ;;
++lm32-*-uclinux*)
++ tm_file="dbxelf.h elfos.h ${tm_file} linux.h lm32/uclinux-elf.h"
++ tmake_file="lm32/t-lm32"
++ tmake_file="${tmake_file} lm32/t-fprules-softfp soft-fp/t-softfp"
++ ;;
+ m32r-*-elf*)
+ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
+ extra_parts="crtinit.o crtfini.o"
+diff -Naur gcc-4.4.2.orig/gcc/config.gcc.orig gcc-4.4.2-rtems4.10-20091015/gcc/config.gcc.orig
+--- gcc-4.4.2.orig/gcc/config.gcc.orig 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/config.gcc.orig 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,3183 @@
++# GCC target-specific configuration file.
++# Copyright 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
++# 2008, 2009 Free Software Foundation, Inc.
++
++#This file is part of GCC.
++
++#GCC 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 3, or (at your option) any later
++#version.
++
++#GCC 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 GCC; see the file COPYING3. If not see
++#<http://www.gnu.org/licenses/>.
++
++# This is the GCC target-specific configuration file
++# where a configuration type is mapped to different system-specific
++# definitions and files. This is invoked by the autoconf-generated
++# configure script. Putting it in a separate shell file lets us skip
++# running autoconf when modifying target-specific information.
++
++# When you change the cases in the OS or target switches, consider
++# updating ../libgcc/config.host also.
++
++# This file switches on the shell variable ${target}, and also uses the
++# following shell variables:
++#
++# with_* Various variables as set by configure.
++#
++# enable_threads Either the name, yes or no depending on whether
++# threads support was requested.
++#
++# default_use_cxa_atexit
++# The default value for the $enable___cxa_atexit
++# variable. enable___cxa_atexit needs to be set to
++# "yes" for the correct operation of C++ destructors
++# but it relies upon the presence of a non-standard C
++# library function called __cxa_atexit.
++# Since not all C libraries provide __cxa_atexit the
++# default value of $default_use_cxa_atexit is set to
++# "no" except for targets which are known to be OK.
++#
++# gas_flag Either yes or no depending on whether GNU as was
++# requested.
++#
++# gnu_ld_flag Either yes or no depending on whether GNU ld was
++# requested.
++
++# This file sets the following shell variables for use by the
++# autoconf-generated configure script:
++#
++# cpu_type The name of the cpu, if different from the first
++# chunk of the canonical target name.
++#
++# tm_defines List of target macros to define for all compilations.
++#
++# tm_file A list of target macro files, if different from
++# "$cpu_type/$cpu_type.h". Usually it's constructed
++# per target in a way like this:
++# tm_file="${tm_file} dbxelf.h elfos.h svr4.h ${cpu_type.h}/elf.h"
++# Note that the preferred order is:
++# - specific target header "${cpu_type}/${cpu_type.h}"
++# - generic headers like dbxelf.h elfos.h, etc.
++# - specializing target headers like ${cpu_type.h}/elf.h
++# This helps to keep OS specific stuff out of the CPU
++# defining header ${cpu_type}/${cpu_type.h}.
++#
++# It is possible to include automatically-generated
++# build-directory files by prefixing them with "./".
++# All other files should relative to $srcdir/config.
++#
++# tm_p_file Location of file with declarations for functions
++# in $out_file.
++#
++# out_file The name of the machine description C support
++# file, if different from "$cpu_type/$cpu_type.c".
++#
++# md_file The name of the machine-description file, if
++# different from "$cpu_type/$cpu_type.md".
++#
++# tmake_file A list of machine-description-specific
++# makefile-fragments, if different from
++# "$cpu_type/t-$cpu_type".
++#
++# extra_modes The name of the file containing a list of extra
++# machine modes, if necessary and different from
++# "$cpu_type/$cpu_type-modes.def".
++#
++# extra_objs List of extra objects that should be linked into
++# the compiler proper (cc1, cc1obj, cc1plus)
++# depending on target.
++#
++# extra_gcc_objs List of extra objects that should be linked into
++# the compiler driver (gcc) depending on target.
++#
++# extra_headers List of used header files from the directory
++# config/${cpu_type}.
++#
++# use_gcc_tgmath If set, add tgmath.h to the list of used header
++# files.
++#
++# extra_passes List of extra executables compiled for this target
++# machine, used for compiling from source to object.
++#
++# extra_parts List of extra object files that should be compiled
++# for this target machine.
++#
++# extra_programs Like extra_passes, but these are used when linking.
++#
++# extra_options List of target-dependent .opt files.
++#
++# c_target_objs List of extra target-dependent objects that be
++# linked into the C compiler only.
++#
++# cxx_target_objs List of extra target-dependent objects that be
++# linked into the C++ compiler only.
++#
++# fortran_target_objs List of extra target-dependent objects that be
++# linked into the fortran compiler only.
++#
++# target_gtfiles List of extra source files with type information.
++#
++# xm_defines List of macros to define when compiling for the
++# target machine.
++#
++# xm_file List of files to include when compiling for the
++# target machine.
++#
++# use_collect2 Set to yes or no, depending on whether collect2
++# will be used.
++#
++# target_cpu_default Set to override the default target model.
++#
++# gdb_needs_out_file_path
++# Set to yes if gdb needs a dir command with
++# `dirname $out_file`.
++#
++# thread_file Set to control which thread package to use.
++#
++# gas Set to yes or no depending on whether the target
++# system normally uses GNU as.
++#
++# need_64bit_hwint Set to yes if HOST_WIDE_INT must be 64 bits wide
++# for this target. This is true if this target
++# supports "long" or "wchar_t" wider than 32 bits,
++# or BITS_PER_WORD is wider than 32 bits.
++# The setting made here must match the one made in
++# other locations such as libcpp/configure.ac
++#
++# configure_default_options
++# Set to an initializer for configure_default_options
++# in configargs.h, based on --with-cpu et cetera.
++#
++# use_fixproto Set to "yes" if fixproto should be run normally,
++# "no" if fixproto should never be run.
++
++# The following variables are used in each case-construct to build up the
++# outgoing variables:
++#
++# gnu_ld Set to yes or no depending on whether the target
++# system normally uses GNU ld.
++
++out_file=
++tmake_file=
++extra_headers=
++use_gcc_tgmath=yes
++extra_passes=
++extra_parts=
++extra_programs=
++extra_objs=
++extra_gcc_objs=
++extra_options=
++c_target_objs=
++cxx_target_objs=
++fortran_target_objs=
++tm_defines=
++xm_defines=
++# Set this to force installation and use of collect2.
++use_collect2=
++# Set this to override the default target model.
++target_cpu_default=
++# Set this if gdb needs a dir command with `dirname $out_file`
++gdb_needs_out_file_path=
++# Set this to control which thread package will be used.
++thread_file=
++# Reinitialize these from the flag values every loop pass, since some
++# configure entries modify them.
++gas="$gas_flag"
++gnu_ld="$gnu_ld_flag"
++default_use_cxa_atexit=no
++target_gtfiles=
++need_64bit_hwint=
++
++# Default to not using fixproto. Targets which need fixproto should
++# specifically set this to 'yes'.
++use_fixproto=no
++
++# Don't carry these over build->host->target. Please.
++xm_file=
++md_file=
++
++# Obsolete configurations.
++case ${target} in
++# Avoid generic cases below matching.
++ h8300-*-rtems* | h8300-*-elf* \
++ | sh-*-elf* | sh-*-symbianelf* | sh-*-linux* | sh-*-netbsdelf* \
++ | sh-*-rtems* | sh-wrs-vxworks) ;;
++ arm-*-coff* \
++ | armel-*-coff* \
++ | h8300-*-* \
++ | i[34567]86-*-aout* \
++ | i[34567]86-*-coff* \
++ | m68k-*-aout* \
++ | m68k-*-coff* \
++ | sh-*-* \
++ | pdp11-*-bsd \
++ | rs6000-ibm-aix4.[12]* \
++ | powerpc-ibm-aix4.[12]* \
++ )
++ if test "x$enable_obsolete" != xyes; then
++ echo "*** Configuration ${target} is obsolete." >&2
++ echo "*** Specify --enable-obsolete to build it anyway." >&2
++ echo "*** Support will be REMOVED in the next major release of GCC," >&2
++ echo "*** unless a maintainer comes forward." >&2
++ exit 1
++ fi;;
++esac
++
++# Unsupported targets list. Do not put an entry in this list unless
++# it would otherwise be caught by a more permissive pattern. The list
++# should be in alphabetical order.
++case ${target} in
++ i[34567]86-go32-* \
++ | i[34567]86-*-go32* \
++ | mips64orion*-*-rtems* \
++ | sparc-hal-solaris2* \
++ | thumb-*-* \
++ | *-*-linux*aout* \
++ | *-*-linux*coff* \
++ | *-*-linux*libc1* \
++ | *-*-linux*oldld* \
++ | *-*-rtemsaout* \
++ | *-*-rtemscoff* \
++ | *-*-solaris2.[0-6] \
++ | *-*-solaris2.[0-6].* \
++ | *-*-sysv* \
++ | vax-*-vms* \
++ )
++ echo "*** Configuration ${target} not supported" 1>&2
++ exit 1
++ ;;
++esac
++
++# Set default cpu_type, tm_file, tm_p_file and xm_file so it can be
++# updated in each machine entry. Also set default extra_headers for some
++# machines.
++tm_p_file=
++cpu_type=`echo ${target} | sed 's/-.*$//'`
++cpu_is_64bit=
++case ${target} in
++m32c*-*-*)
++ cpu_type=m32c
++ tmake_file=m32c/t-m32c
++ ;;
++alpha*-*-*)
++ cpu_type=alpha
++ need_64bit_hwint=yes
++ ;;
++am33_2.0-*-linux*)
++ cpu_type=mn10300
++ ;;
++arm*-*-*)
++ cpu_type=arm
++ extra_headers="mmintrin.h arm_neon.h"
++ c_target_objs="arm-c.o"
++ cxx_target_objs="arm-c.o"
++ ;;
++bfin*-*)
++ cpu_type=bfin
++ ;;
++crisv32-*)
++ cpu_type=cris
++ ;;
++frv*) cpu_type=frv
++ ;;
++fido-*-*)
++ cpu_type=m68k
++ extra_headers=math-68881.h
++ ;;
++i[34567]86-*-*)
++ cpu_type=i386
++ c_target_objs="i386-c.o"
++ cxx_target_objs="i386-c.o"
++ extra_headers="cpuid.h mmintrin.h mm3dnow.h xmmintrin.h emmintrin.h
++ pmmintrin.h tmmintrin.h ammintrin.h smmintrin.h
++ nmmintrin.h bmmintrin.h mmintrin-common.h
++ wmmintrin.h immintrin.h x86intrin.h avxintrin.h
++ cross-stdarg.h"
++ ;;
++x86_64-*-*)
++ cpu_type=i386
++ c_target_objs="i386-c.o"
++ cxx_target_objs="i386-c.o"
++ extra_headers="cpuid.h mmintrin.h mm3dnow.h xmmintrin.h emmintrin.h
++ pmmintrin.h tmmintrin.h ammintrin.h smmintrin.h
++ nmmintrin.h bmmintrin.h mmintrin-common.h
++ wmmintrin.h immintrin.h x86intrin.h avxintrin.h
++ cross-stdarg.h"
++ need_64bit_hwint=yes
++ ;;
++ia64-*-*)
++ extra_headers=ia64intrin.h
++ need_64bit_hwint=yes
++ ;;
++hppa*-*-*)
++ cpu_type=pa
++ ;;
++m32r*-*-*)
++ cpu_type=m32r
++ ;;
++m68k-*-*)
++ extra_headers=math-68881.h
++ ;;
++mips*-*-*)
++ cpu_type=mips
++ need_64bit_hwint=yes
++ extra_headers="loongson.h"
++ ;;
++picochip-*-*)
++ cpu_type=picochip
++ ;;
++powerpc*-*-*)
++ cpu_type=rs6000
++ extra_headers="ppc-asm.h altivec.h spe.h ppu_intrinsics.h paired.h spu2vmx.h vec_types.h si2vmx.h"
++ need_64bit_hwint=yes
++ case x$with_cpu in
++ xpowerpc64|xdefault64|x6[23]0|x970|xG5|xpower[34567]|xpower6x|xrs64a|xcell)
++ cpu_is_64bit=yes
++ ;;
++ esac
++ ;;
++rs6000*-*-*)
++ need_64bit_hwint=yes
++ ;;
++score*-*-*)
++ cpu_type=score
++ ;;
++sparc*-*-*)
++ cpu_type=sparc
++ need_64bit_hwint=yes
++ ;;
++spu*-*-*)
++ cpu_type=spu
++ need_64bit_hwint=yes
++ ;;
++s390*-*-*)
++ cpu_type=s390
++ need_64bit_hwint=yes
++ ;;
++# Note the 'l'; we need to be able to match e.g. "shle" or "shl".
++sh[123456789lbe]*-*-* | sh-*-*)
++ cpu_type=sh
++ need_64bit_hwint=yes
++ ;;
++esac
++
++tm_file=${cpu_type}/${cpu_type}.h
++if test -f ${srcdir}/config/${cpu_type}/${cpu_type}-protos.h
++then
++ tm_p_file=${cpu_type}/${cpu_type}-protos.h
++fi
++extra_modes=
++if test -f ${srcdir}/config/${cpu_type}/${cpu_type}-modes.def
++then
++ extra_modes=${cpu_type}/${cpu_type}-modes.def
++fi
++if test -f ${srcdir}/config/${cpu_type}/${cpu_type}.opt
++then
++ extra_options="${extra_options} ${cpu_type}/${cpu_type}.opt"
++fi
++
++case ${target} in
++i[34567]86-*-*)
++ if test "x$enable_cld" = xyes; then
++ tm_defines="${tm_defines} USE_IX86_CLD=1"
++ fi
++ ;;
++x86_64-*-*)
++ tm_file="i386/biarch64.h ${tm_file}"
++ if test "x$enable_cld" = xyes; then
++ tm_defines="${tm_defines} USE_IX86_CLD=1"
++ fi
++ ;;
++esac
++
++# On a.out targets, we need to use collect2.
++case ${target} in
++*-*-*aout*)
++ use_collect2=yes
++ ;;
++esac
++
++# Common parts for widely ported systems.
++case ${target} in
++*-*-darwin*)
++ tm_file="${tm_file} darwin.h"
++ case ${target} in
++ *-*-darwin[912]*)
++ tm_file="${tm_file} darwin9.h"
++ ;;
++ esac
++ tm_file="${tm_file} ${cpu_type}/darwin.h"
++ tm_p_file="${tm_p_file} darwin-protos.h"
++ tmake_file="t-darwin ${cpu_type}/t-darwin t-slibgcc-darwin"
++ target_gtfiles="\$(srcdir)/config/darwin.c"
++ extra_options="${extra_options} darwin.opt"
++ c_target_objs="${c_target_objs} darwin-c.o"
++ cxx_target_objs="${cxx_target_objs} darwin-c.o"
++ fortran_target_objs="darwin-f.o"
++ extra_objs="darwin.o"
++ extra_gcc_objs="darwin-driver.o"
++ default_use_cxa_atexit=yes
++ case ${enable_threads} in
++ "" | yes | posix) thread_file='posix' ;;
++ esac
++ ;;
++*-*-freebsd[12] | *-*-freebsd[12].* | *-*-freebsd*aout*)
++ # This is the place-holder for the generic a.out configuration
++ # of FreeBSD. No actual configuration resides here since
++ # there was only ever a bare-bones ix86 configuration for
++ # a.out and it exists solely in the machine-specific section.
++ # This place-holder must exist to avoid dropping into
++ # the generic ELF configuration of FreeBSD (i.e. it must be
++ # ordered before that section).
++ ;;
++*-*-freebsd*)
++ # This is the generic ELF configuration of FreeBSD. Later
++ # machine-specific sections may refine and add to this
++ # configuration.
++ #
++ # Due to tm_file entry ordering issues that vary between cpu
++ # architectures, we only define fbsd_tm_file to allow the
++ # machine-specific section to dictate the final order of all
++ # entries of tm_file with the minor exception that components
++ # of the tm_file set here will always be of the form:
++ #
++ # freebsd<version_number>.h [freebsd-<conf_option>.h ...] freebsd-spec.h freebsd.h
++ #
++ # The machine-specific section should not tamper with this
++ # ordering but may order all other entries of tm_file as it
++ # pleases around the provided core setting.
++ gas=yes
++ gnu_ld=yes
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o"
++ fbsd_major=`echo ${target} | sed -e 's/.*freebsd//g' | sed -e 's/\..*//g'`
++ tm_defines="${tm_defines} FBSD_MAJOR=${fbsd_major}"
++ tmake_file="t-slibgcc-elf-ver t-freebsd"
++ case ${enable_threads} in
++ no)
++ fbsd_tm_file="${fbsd_tm_file} freebsd-nthr.h"
++ ;;
++ "" | yes | posix)
++ thread_file='posix'
++ tmake_file="${tmake_file} t-freebsd-thread"
++ # Before 5.0, FreeBSD can't bind shared libraries to -lc
++ # when "optionally" threaded via weak pthread_* checks.
++ case ${target} in
++ *-*-freebsd[34] | *-*-freebsd[34].*)
++ tmake_file="${tmake_file} t-slibgcc-nolc-override"
++ ;;
++ esac
++ ;;
++ *)
++ echo 'Unknown thread configuration for FreeBSD'
++ exit 1
++ ;;
++ esac
++ fbsd_tm_file="${fbsd_tm_file} freebsd-spec.h freebsd.h"
++ ;;
++*-*-linux* | frv-*-*linux* | *-*-kfreebsd*-gnu | *-*-knetbsd*-gnu | *-*-gnu* | *-*-kopensolaris*-gnu)
++ extra_parts="crtbegin.o crtbeginS.o crtbeginT.o crtend.o crtendS.o"
++ gas=yes
++ gnu_ld=yes
++ case ${enable_threads} in
++ "" | yes | posix) thread_file='posix' ;;
++ esac
++ tmake_file="t-slibgcc-elf-ver t-linux"
++ case $target in
++ *-*-linux* | frv-*-*linux* | *-*-kfreebsd*-gnu | *-*-knetbsd*-gnu | *-*-kopensolaris*-gnu)
++ :;;
++ *-*-gnu*)
++ tmake_file="$tmake_file t-gnu";;
++ esac
++ # glibc / uclibc switch. uclibc isn't usable for GNU/Hurd and neither for
++ # GNU/k*BSD.
++ case $target in
++ *linux*)
++ extra_options="$extra_options linux.opt";;
++ *)
++ tm_defines="$tm_defines OPTION_GLIBC=1";;
++ esac
++ case ${target} in
++ *-*-*uclibc*)
++ tm_defines="${tm_defines} UCLIBC_DEFAULT=1"
++ ;;
++ *)
++ tm_defines="${tm_defines} UCLIBC_DEFAULT=0"
++ ;;
++ esac
++ # Assume that glibc or uClibc are being used and so __cxa_atexit is provided.
++ default_use_cxa_atexit=yes
++ use_gcc_tgmath=no
++ ;;
++*-*-netbsd*)
++ tmake_file="t-slibgcc-elf-ver t-libc-ok t-netbsd t-libgcc-pic"
++ gas=yes
++ gnu_ld=yes
++
++ # NetBSD 2.0 and later get POSIX threads enabled by default.
++ # Allow them to be explicitly enabled on any other version.
++ case ${enable_threads} in
++ "")
++ case ${target} in
++ *-*-netbsd[2-9]* | *-*-netbsdelf[2-9]*)
++ thread_file='posix'
++ tm_defines="${tm_defines} NETBSD_ENABLE_PTHREADS"
++ ;;
++ esac
++ ;;
++ yes | posix)
++ thread_file='posix'
++ tm_defines="${tm_defines} NETBSD_ENABLE_PTHREADS"
++ ;;
++ esac
++
++ # NetBSD 1.7 and later are set up to use GCC's crtstuff for
++ # ELF configurations. We will clear extra_parts in the
++ # a.out configurations.
++ case ${target} in
++ *-*-netbsd*1.[7-9]* | *-*-netbsd[2-9]* | *-*-netbsdelf[2-9]*)
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtbeginT.o"
++ ;;
++ esac
++
++ # NetBSD 2.0 and later provide __cxa_atexit(), which we use by
++ # default (unless overridden by --disable-__cxa_atexit).
++ case ${target} in
++ *-*-netbsd[2-9]* | *-*-netbsdelf[2-9]*)
++ default_use_cxa_atexit=yes
++ ;;
++ esac
++ ;;
++*-*-openbsd*)
++ tmake_file="t-libc-ok t-openbsd t-libgcc-pic"
++ case ${enable_threads} in
++ yes)
++ thread_file='posix'
++ tmake_file="${tmake_file} t-openbsd-thread"
++ ;;
++ esac
++ case ${target} in
++ *-*-openbsd2.*|*-*-openbsd3.[012])
++ tm_defines="${tm_defines} HAS_LIBC_R=1" ;;
++ esac
++ ;;
++*-*-rtems*)
++ case ${enable_threads} in
++ yes) thread_file='rtems' ;;
++ esac
++ ;;
++*-*-vxworks*)
++ tmake_file=t-vxworks
++ xm_defines=POSIX
++ extra_options="${extra_options} vxworks.opt"
++ extra_objs=vxworks.o
++ case ${enable_threads} in
++ no) ;;
++ "" | yes | vxworks) thread_file='vxworks' ;;
++ *) echo 'Unknown thread configuration for VxWorks'; exit 1 ;;
++ esac
++ ;;
++*-*-elf)
++ # Assume that newlib is being used and so __cxa_atexit is provided.
++ default_use_cxa_atexit=yes
++ ;;
++esac
++
++case ${target} in
++# Support site-specific machine types.
++*local*)
++ rest=`echo ${target} | sed -e "s/$cpu_type-//"`
++ tm_file=${cpu_type}/$rest.h
++ if test -f $srcdir/config/${cpu_type}/xm-$rest.h
++ then xm_file=${cpu_type}/xm-$rest.h
++ fi
++ if test -f $srcdir/config/${cpu_type}/t-$rest
++ then tmake_file=${cpu_type}/t-$rest
++ fi
++ ;;
++alpha*-*-linux*)
++ tm_file="${tm_file} alpha/elf.h alpha/linux.h alpha/linux-elf.h"
++ target_cpu_default="MASK_GAS"
++ tmake_file="${tmake_file} alpha/t-crtfm alpha/t-alpha alpha/t-ieee alpha/t-linux"
++ ;;
++alpha*-*-gnu*)
++ tm_file="$tm_file alpha/elf.h alpha/linux.h alpha/linux-elf.h gnu.h alpha/gnu.h"
++ target_cpu_default="MASK_GAS"
++ tmake_file="${tmake_file} alpha/t-crtfm alpha/t-alpha alpha/t-ieee"
++ ;;
++alpha*-*-freebsd*)
++ tm_file="${tm_file} ${fbsd_tm_file} alpha/elf.h alpha/freebsd.h"
++ target_cpu_default="MASK_GAS"
++ tmake_file="${tmake_file} alpha/t-crtfm alpha/t-alpha alpha/t-ieee"
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtbeginT.o"
++ ;;
++alpha*-*-netbsd*)
++ tm_file="${tm_file} netbsd.h alpha/elf.h netbsd-elf.h alpha/netbsd.h"
++ target_cpu_default="MASK_GAS"
++ tmake_file="${tmake_file} alpha/t-alpha alpha/t-ieee"
++ ;;
++alpha*-*-openbsd*)
++ tm_defines="${tm_defines} OBSD_NO_DYNAMIC_LIBRARIES OBSD_HAS_DECLARE_FUNCTION_NAME OBSD_HAS_DECLARE_FUNCTION_SIZE OBSD_HAS_DECLARE_OBJECT"
++ tm_file="alpha/alpha.h openbsd.h alpha/openbsd.h"
++ # default x-alpha is only appropriate for dec-osf.
++ target_cpu_default="MASK_GAS"
++ tmake_file="alpha/t-alpha alpha/t-ieee"
++ ;;
++alpha*-dec-osf[45]*)
++ if test x$stabs = xyes
++ then
++ tm_file="${tm_file} dbx.h"
++ fi
++ if test x$gas != xyes
++ then
++ extra_passes="mips-tfile mips-tdump"
++ fi
++ use_collect2=yes
++ tmake_file="alpha/t-alpha alpha/t-ieee alpha/t-crtfm alpha/t-osf4"
++ tm_file="${tm_file} alpha/osf.h"
++ extra_headers=va_list.h
++ case ${target} in
++ *-*-osf4*)
++ # Define TARGET_SUPPORT_ARCH except on 4.0a.
++ case ${target} in
++ *-*-osf4.0a) ;;
++ *) tm_defines="${tm_defines} TARGET_SUPPORT_ARCH=1"
++ esac
++ ;;
++ *-*-osf5*)
++ tm_file="${tm_file} alpha/osf5.h"
++ tm_defines="${tm_defines} TARGET_SUPPORT_ARCH=1"
++ ;;
++ esac
++ case ${enable_threads} in
++ "" | yes | posix)
++ thread_file='posix'
++ tmake_file="${tmake_file} alpha/t-osf-pthread"
++ ;;
++ esac
++ ;;
++alpha64-dec-*vms*)
++ tm_file="${tm_file} alpha/vms.h alpha/vms64.h"
++ xm_file="alpha/xm-vms.h"
++ tmake_file="alpha/t-alpha alpha/t-vms alpha/t-vms64 alpha/t-ieee"
++ prefix=/gnu
++ local_prefix=/gnu
++ ;;
++alpha*-dec-*vms*)
++ tm_file="${tm_file} alpha/vms.h"
++ xm_file=alpha/xm-vms.h
++ tmake_file="alpha/t-alpha alpha/t-vms alpha/t-ieee"
++ prefix=/gnu
++ local_prefix=/gnu
++ ;;
++arc-*-elf*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ extra_parts="crtinit.o crtfini.o"
++ ;;
++arm-*-coff* | armel-*-coff*)
++ tm_file="arm/semi.h arm/aout.h arm/arm.h arm/coff.h dbxcoff.h"
++ tmake_file="arm/t-arm arm/t-arm-coff"
++ ;;
++arm-wrs-vxworks)
++ tm_file="elfos.h arm/elf.h arm/aout.h ${tm_file} vx-common.h vxworks.h arm/vxworks.h"
++ tmake_file="${tmake_file} arm/t-arm arm/t-vxworks"
++ ;;
++arm*-*-freebsd*)
++ tm_file="dbxelf.h elfos.h ${fbsd_tm_file} arm/elf.h arm/aout.h arm/freebsd.h arm/arm.h"
++ tmake_file="${tmake_file} arm/t-arm arm/t-strongarm-elf"
++ ;;
++arm*-*-netbsdelf*)
++ tm_file="dbxelf.h elfos.h netbsd.h netbsd-elf.h arm/elf.h arm/aout.h arm/arm.h arm/netbsd-elf.h"
++ tmake_file="${tmake_file} arm/t-arm arm/t-netbsd"
++ ;;
++arm*-*-netbsd*)
++ tm_file="arm/aout.h arm/arm.h netbsd.h netbsd-aout.h arm/netbsd.h"
++ tmake_file="t-netbsd arm/t-arm arm/t-netbsd"
++ extra_parts=""
++ use_collect2=yes
++ ;;
++arm*-*-linux*) # ARM GNU/Linux with ELF
++ tm_file="dbxelf.h elfos.h linux.h arm/elf.h arm/linux-gas.h arm/linux-elf.h"
++ case $target in
++ arm*b-*)
++ tm_defines="${tm_defines} TARGET_BIG_ENDIAN_DEFAULT=1"
++ ;;
++ esac
++ tmake_file="${tmake_file} t-linux arm/t-arm"
++ case ${target} in
++ arm*-*-linux-*eabi)
++ tm_file="$tm_file arm/bpabi.h arm/linux-eabi.h"
++ tmake_file="$tmake_file arm/t-arm-elf arm/t-bpabi arm/t-linux-eabi"
++ # The BPABI long long divmod functions return a 128-bit value in
++ # registers r0-r3. Correctly modeling that requires the use of
++ # TImode.
++ need_64bit_hwint=yes
++ # The EABI requires the use of __cxa_atexit.
++ default_use_cxa_atexit=yes
++ ;;
++ *)
++ tmake_file="$tmake_file arm/t-linux"
++ ;;
++ esac
++ tm_file="$tm_file arm/aout.h arm/arm.h"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-*-uclinux*) # ARM ucLinux
++ tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/linux-gas.h arm/uclinux-elf.h"
++ tmake_file="arm/t-arm arm/t-arm-elf"
++ case ${target} in
++ arm*-*-uclinux*eabi)
++ tm_file="$tm_file arm/bpabi.h arm/uclinux-eabi.h"
++ tmake_file="$tmake_file arm/t-bpabi"
++ # The BPABI long long divmod functions return a 128-bit value in
++ # registers r0-r3. Correctly modeling that requires the use of
++ # TImode.
++ need_64bit_hwint=yes
++ # The EABI requires the use of __cxa_atexit.
++ default_use_cxa_atexit=yes
++ esac
++ tm_file="$tm_file arm/aout.h arm/arm.h"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-*-ecos-elf)
++ tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/aout.h arm/arm.h arm/ecos-elf.h"
++ tmake_file="arm/t-arm arm/t-arm-elf"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-*-eabi* | arm*-*-symbianelf* )
++ # The BPABI long long divmod functions return a 128-bit value in
++ # registers r0-r3. Correctly modeling that requires the use of
++ # TImode.
++ need_64bit_hwint=yes
++ default_use_cxa_atexit=yes
++ tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/bpabi.h"
++ tmake_file="arm/t-arm arm/t-arm-elf"
++ case ${target} in
++ arm*-*-eabi*)
++ tm_file="$tm_file arm/eabi.h"
++ tmake_file="${tmake_file} arm/t-bpabi"
++ extra_options="${extra_options} arm/eabi.opt"
++ ;;
++ arm*-*-symbianelf*)
++ tm_file="${tm_file} arm/symbian.h"
++ # We do not include t-bpabi for Symbian OS because the system
++ # provides its own implementation of the BPABI functions.
++ tmake_file="${tmake_file} arm/t-symbian"
++ ;;
++ esac
++ tm_file="${tm_file} arm/aout.h arm/arm.h"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-*-rtems*)
++ tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/aout.h arm/arm.h arm/rtems-elf.h rtems.h"
++ tmake_file="arm/t-arm arm/t-arm-elf t-rtems arm/t-rtems"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-*-elf)
++ tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/aout.h arm/arm.h"
++ tmake_file="arm/t-arm arm/t-arm-elf"
++ tmake_file="${tmake_file} arm/t-arm-softfp soft-fp/t-softfp"
++ ;;
++arm*-wince-pe*)
++ tm_file="arm/semi.h arm/aout.h arm/arm.h arm/coff.h dbxcoff.h arm/pe.h arm/wince-pe.h"
++ tmake_file="arm/t-arm arm/t-wince-pe"
++ extra_options="${extra_options} arm/pe.opt"
++ extra_objs="pe.o"
++ ;;
++arm-*-pe*)
++ tm_file="arm/semi.h arm/aout.h arm/arm.h arm/coff.h dbxcoff.h arm/pe.h"
++ tmake_file="arm/t-arm arm/t-pe"
++ extra_options="${extra_options} arm/pe.opt"
++ extra_objs="pe.o"
++ ;;
++avr-*-rtems*)
++ tm_file="avr/avr.h dbxelf.h avr/rtems.h rtems.h"
++ tmake_file="avr/t-avr t-rtems avr/t-rtems"
++ ;;
++avr-*-*)
++ tm_file="avr/avr.h dbxelf.h"
++ ;;
++bfin*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h bfin/elf.h"
++ tmake_file=bfin/t-bfin-elf
++ use_collect2=no
++ ;;
++bfin*-uclinux*)
++ tm_file="${tm_file} dbxelf.h elfos.h bfin/elf.h linux.h bfin/uclinux.h"
++ tmake_file=bfin/t-bfin-uclinux
++ tm_defines="${tm_defines} UCLIBC_DEFAULT=1"
++ extra_options="${extra_options} linux.opt"
++ use_collect2=no
++ ;;
++bfin*-linux-uclibc*)
++ tm_file="${tm_file} dbxelf.h elfos.h bfin/elf.h linux.h bfin/linux.h ./linux-sysroot-suffix.h"
++ tmake_file="t-slibgcc-elf-ver bfin/t-bfin-linux"
++ extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"
++ use_collect2=no
++ ;;
++bfin*-rtems*)
++ tm_file="${tm_file} dbxelf.h elfos.h bfin/elf.h bfin/rtems.h rtems.h"
++ tmake_file="bfin/t-bfin t-rtems bfin/t-rtems"
++ ;;
++bfin*-*)
++ tm_file="${tm_file} dbxelf.h elfos.h bfin/elf.h"
++ tmake_file=bfin/t-bfin
++ use_collect2=no
++ ;;
++crisv32-*-elf | crisv32-*-none)
++ tm_file="dbxelf.h elfos.h ${tm_file}"
++ tmake_file="cris/t-cris"
++ target_cpu_default=32
++ gas=yes
++ extra_options="${extra_options} cris/elf.opt"
++ ;;
++cris-*-elf | cris-*-none)
++ tm_file="dbxelf.h elfos.h ${tm_file}"
++ tmake_file="cris/t-cris cris/t-elfmulti"
++ gas=yes
++ extra_options="${extra_options} cris/elf.opt"
++ ;;
++crisv32-*-linux* | cris-*-linux*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} linux.h cris/linux.h"
++ # We need to avoid using t-linux, so override default tmake_file
++ tmake_file="cris/t-cris t-slibgcc-elf-ver cris/t-linux"
++ extra_options="${extra_options} cris/linux.opt"
++ case $target in
++ cris-*-*)
++ target_cpu_default=10
++ ;;
++ crisv32-*-*)
++ target_cpu_default=32
++ ;;
++ esac
++ ;;
++crx-*-elf)
++ tm_file="elfos.h ${tm_file}"
++ extra_parts="crtbegin.o crtend.o"
++ use_collect2=no
++ ;;
++fr30-*-elf)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ tmake_file=fr30/t-fr30
++ extra_parts="crti.o crtn.o crtbegin.o crtend.o"
++ ;;
++frv-*-elf)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} frv/frv-abi.h"
++ tmake_file=frv/t-frv
++ ;;
++frv-*-*linux*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} \
++ linux.h frv/linux.h frv/frv-abi.h"
++ tmake_file="${tmake_file} frv/t-frv frv/t-linux"
++ ;;
++h8300-*-rtems*)
++ tmake_file="h8300/t-h8300 h8300/t-elf t-rtems h8300/t-rtems"
++ tm_file="h8300/h8300.h dbxelf.h elfos.h h8300/elf.h h8300/rtems.h rtems.h"
++ ;;
++h8300-*-elf*)
++ tmake_file="h8300/t-h8300 h8300/t-elf"
++ tm_file="h8300/h8300.h dbxelf.h elfos.h h8300/elf.h"
++ ;;
++h8300-*-*)
++ tm_file="h8300/h8300.h dbxcoff.h h8300/coff.h"
++ ;;
++hppa*64*-*-linux*)
++ target_cpu_default="MASK_PA_11|MASK_PA_20"
++ tm_file="pa/pa64-start.h ${tm_file} dbxelf.h elfos.h svr4.h linux.h \
++ pa/pa-linux.h pa/pa64-regs.h pa/pa-64.h pa/pa64-linux.h"
++ tmake_file="${tmake_file} pa/t-linux64"
++ gas=yes gnu_ld=yes
++ need_64bit_hwint=yes
++ ;;
++hppa*-*-linux*)
++ target_cpu_default="MASK_PA_11|MASK_NO_SPACE_REGS"
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h pa/pa-linux.h \
++ pa/pa32-regs.h pa/pa32-linux.h"
++ tmake_file="${tmake_file} pa/t-linux"
++ # Set the libgcc version number
++ if test x$sjlj = x1; then
++ tmake_file="$tmake_file pa/t-slibgcc-sjlj-ver"
++ else
++ tmake_file="$tmake_file pa/t-slibgcc-dwarf-ver"
++ fi
++ ;;
++# port not yet contributed.
++#hppa*-*-openbsd*)
++# target_cpu_default="MASK_PA_11"
++# ;;
++hppa[12]*-*-hpux10*)
++ case ${target} in
++ hppa1.1-*-* | hppa2*-*-*)
++ target_cpu_default="MASK_PA_11"
++ ;;
++ esac
++ tm_file="${tm_file} pa/pa32-regs.h dbxelf.h pa/som.h \
++ pa/pa-hpux.h pa/pa-hpux10.h"
++ extra_options="${extra_options} pa/pa-hpux.opt"
++ case ${target} in
++ *-*-hpux10.[1-9]*)
++ tm_file="${tm_file} pa/pa-hpux1010.h"
++ extra_options="${extra_options} pa/pa-hpux1010.opt"
++ ;;
++ esac
++ tmake_file="pa/t-pa-hpux10 pa/t-pa-hpux pa/t-hpux-shlib"
++ case ${enable_threads} in
++ "")
++ if test x$have_pthread_h = xyes ; then
++ tmake_file="${tmake_file} pa/t-dce-thr"
++ fi
++ ;;
++ yes | dce)
++ tmake_file="${tmake_file} pa/t-dce-thr"
++ ;;
++ esac
++ # Set the libgcc version number
++ if test x$sjlj = x1; then
++ tmake_file="$tmake_file pa/t-slibgcc-sjlj-ver"
++ else
++ tmake_file="$tmake_file pa/t-slibgcc-dwarf-ver"
++ fi
++ use_collect2=yes
++ gas=yes
++ ;;
++hppa*64*-*-hpux11*)
++ target_cpu_default="MASK_PA_11|MASK_PA_20"
++ if test x$gnu_ld = xyes
++ then
++ target_cpu_default="${target_cpu_default}|MASK_GNU_LD"
++ fi
++ tm_file="pa/pa64-start.h ${tm_file} dbxelf.h elfos.h \
++ pa/pa64-regs.h pa/pa-hpux.h pa/pa-hpux1010.h \
++ pa/pa-hpux11.h"
++ case ${target} in
++ *-*-hpux11.[1-9]*)
++ tm_file="${tm_file} pa/pa-hpux1111.h pa/pa-64.h pa/pa64-hpux.h"
++ extra_options="${extra_options} pa/pa-hpux1111.opt"
++ ;;
++ *)
++ tm_file="${tm_file} pa/pa-64.h pa/pa64-hpux.h"
++ ;;
++ esac
++ extra_options="${extra_options} pa/pa-hpux.opt \
++ pa/pa-hpux1010.opt pa/pa64-hpux.opt"
++ need_64bit_hwint=yes
++ tmake_file="pa/t-pa64 pa/t-pa-hpux pa/t-hpux-shlib"
++ # Set the libgcc version number
++ if test x$sjlj = x1; then
++ tmake_file="$tmake_file pa/t-slibgcc-sjlj-ver"
++ else
++ tmake_file="$tmake_file pa/t-slibgcc-dwarf-ver"
++ fi
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtbeginT.o \
++ libgcc_stub.a"
++ case x${enable_threads} in
++ x | xyes | xposix )
++ thread_file=posix
++ ;;
++ esac
++ gas=yes
++ ;;
++hppa[12]*-*-hpux11*)
++ case ${target} in
++ hppa1.1-*-* | hppa2*-*-*)
++ target_cpu_default="MASK_PA_11"
++ ;;
++ esac
++ tm_file="${tm_file} pa/pa32-regs.h dbxelf.h pa/som.h \
++ pa/pa-hpux.h pa/pa-hpux1010.h pa/pa-hpux11.h"
++ extra_options="${extra_options} pa/pa-hpux.opt pa/pa-hpux1010.opt"
++ case ${target} in
++ *-*-hpux11.[1-9]*)
++ tm_file="${tm_file} pa/pa-hpux1111.h"
++ extra_options="${extra_options} pa/pa-hpux1111.opt"
++ ;;
++ esac
++ tmake_file="pa/t-pa-hpux11 pa/t-pa-hpux pa/t-hpux-shlib"
++ # Set the libgcc version number
++ if test x$sjlj = x1; then
++ tmake_file="$tmake_file pa/t-slibgcc-sjlj-ver"
++ else
++ tmake_file="$tmake_file pa/t-slibgcc-dwarf-ver"
++ fi
++ case x${enable_threads} in
++ x | xyes | xposix )
++ thread_file=posix
++ ;;
++ esac
++ use_collect2=yes
++ gas=yes
++ ;;
++i[34567]86-*-darwin*)
++ need_64bit_hwint=yes
++
++ # This is so that '.../configure && make' doesn't fail due to
++ # config.guess deciding that the configuration is i386-*-darwin* and
++ # then this file using that to set --with-cpu=i386 which has no -m64
++ # support.
++ with_cpu=${with_cpu:-generic}
++ tmake_file="${tmake_file} i386/t-crtpc i386/t-crtfm"
++ ;;
++x86_64-*-darwin*)
++ with_cpu=${with_cpu:-generic}
++ tmake_file="${tmake_file} t-darwin ${cpu_type}/t-darwin64 t-slibgcc-darwin i386/t-crtpc i386/t-crtfm"
++ tm_file="${tm_file} ${cpu_type}/darwin64.h"
++ ;;
++i[34567]86-*-elf*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h i386/i386elf.h"
++ tmake_file="${tmake_file} i386/t-i386elf t-svr4"
++ ;;
++x86_64-*-elf*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h i386/i386elf.h i386/x86-64.h"
++ tmake_file="${tmake_file} i386/t-i386elf t-svr4"
++ ;;
++i[34567]86-*-aout*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h i386/gstabs.h i386/i386-aout.h"
++ ;;
++i[34567]86-*-freebsd*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h ${fbsd_tm_file} i386/freebsd.h"
++ ;;
++x86_64-*-freebsd*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h ${fbsd_tm_file} i386/x86-64.h i386/freebsd.h i386/freebsd64.h"
++ tmake_file="${tmake_file} i386/t-crtstuff"
++ ;;
++i[34567]86-*-netbsdelf*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h netbsd.h netbsd-elf.h i386/netbsd-elf.h"
++ ;;
++i[34567]86-*-netbsd*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h i386/gstabs.h netbsd.h netbsd-aout.h i386/netbsd.h"
++ tmake_file="${tmake_file} t-netbsd"
++ extra_parts=""
++ use_collect2=yes
++ ;;
++x86_64-*-netbsd*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h netbsd.h netbsd-elf.h i386/x86-64.h i386/netbsd64.h"
++ tmake_file="${tmake_file} i386/t-crtstuff"
++ ;;
++i[34567]86-*-openbsd2.*|i[34567]86-*openbsd3.[0123])
++ tm_file="i386/i386.h i386/unix.h i386/bsd.h i386/gas.h i386/gstabs.h openbsd-oldgas.h openbsd.h i386/openbsd.h"
++ # needed to unconfuse gdb
++ tmake_file="${tmake_file} t-libc-ok t-openbsd i386/t-openbsd"
++ # we need collect2 until our bug is fixed...
++ use_collect2=yes
++ ;;
++i[34567]86-*-openbsd*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h"
++ tm_file="${tm_file} openbsd.h i386/openbsdelf.h"
++ gas=yes
++ gnu_ld=yes
++ ;;
++i[34567]86-*-coff*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h dbxcoff.h i386/i386-coff.h"
++ ;;
++i[34567]86-*-linux* | i[34567]86-*-kfreebsd*-gnu | i[34567]86-*-knetbsd*-gnu | i[34567]86-*-gnu* | i[34567]86-*-kopensolaris*-gnu)
++ # Intel 80386's running GNU/*
++ # with ELF format using glibc 2
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h svr4.h linux.h"
++ case ${target} in
++ i[34567]86-*-linux*)
++ if test x$enable_targets = xall; then
++ tm_file="${tm_file} i386/x86-64.h i386/linux64.h"
++ tm_defines="${tm_defines} TARGET_BI_ARCH=1"
++ tmake_file="${tmake_file} i386/t-linux64"
++ need_64bit_hwint=yes
++ case X"${with_cpu}" in
++ Xgeneric|Xcore2|Xnocona|Xx86-64|Xamdfam10|Xbarcelona|Xk8|Xopteron|Xathlon64|Xathlon-fx)
++ ;;
++ X)
++ if test x$with_cpu_64 = x; then
++ with_cpu_64=generic
++ fi
++ ;;
++ *)
++ echo "Unsupported CPU used in --with-cpu=$with_cpu, supported values:" 1>&2
++ echo "generic core2 nocona x86-64 amdfam10 barcelona k8 opteron athlon64 athlon-fx" 1>&2
++ exit 1
++ ;;
++ esac
++ else
++ tm_file="${tm_file} i386/linux.h"
++ fi
++ ;;
++ i[34567]86-*-knetbsd*-gnu) tm_file="${tm_file} i386/linux.h knetbsd-gnu.h i386/knetbsd-gnu.h" ;;
++ i[34567]86-*-kfreebsd*-gnu) tm_file="${tm_file} i386/linux.h kfreebsd-gnu.h i386/kfreebsd-gnu.h" ;;
++ i[34567]86-*-kopensolaris*-gnu) tm_file="${tm_file} i386/linux.h kopensolaris-gnu.h i386/kopensolaris-gnu.h" ;;
++ i[34567]86-*-gnu*) tm_file="$tm_file i386/linux.h gnu.h i386/gnu.h";;
++ esac
++ tmake_file="${tmake_file} i386/t-crtstuff i386/t-crtpc i386/t-crtfm t-dfprules"
++ ;;
++x86_64-*-linux* | x86_64-*-kfreebsd*-gnu | x86_64-*-knetbsd*-gnu)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h svr4.h linux.h \
++ i386/x86-64.h i386/linux64.h"
++ case ${target} in
++ x86_64-*-kfreebsd*-gnu) tm_file="${tm_file} kfreebsd-gnu.h" ;;
++ x86_64-*-knetbsd*-gnu) tm_file="${tm_file} knetbsd-gnu.h" ;;
++ esac
++ tmake_file="${tmake_file} i386/t-linux64 i386/t-crtstuff i386/t-crtpc i386/t-crtfm t-dfprules"
++ ;;
++i[34567]86-pc-msdosdjgpp*)
++ xm_file=i386/xm-djgpp.h
++ tm_file="dbxcoff.h ${tm_file} i386/unix.h i386/bsd.h i386/gas.h i386/djgpp.h"
++ tmake_file="${tmake_file} i386/t-djgpp"
++ extra_options="${extra_options} i386/djgpp.opt"
++ gnu_ld=yes
++ gas=yes
++ ;;
++i[34567]86-*-lynxos*)
++ xm_defines=POSIX
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h i386/lynx.h lynx.h"
++ tmake_file="${tmake_file} i386/t-crtstuff t-lynx"
++ extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"
++ extra_options="${extra_options} lynx.opt"
++ thread_file=lynx
++ gnu_ld=yes
++ gas=yes
++ ;;
++i[3456x]86-*-netware*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h svr4.h tm-dwarf2.h i386/netware.h"
++ tmake_file="${tmake_file} i386/t-netware"
++ extra_objs=netware.o
++ case /${with_ld} in
++ */nwld)
++ extra_objs="$extra_objs nwld.o"
++ tm_file="${tm_file} i386/nwld.h"
++ tmake_file="${tmake_file} i386/t-nwld"
++ extra_parts="crt0.o libgcc.def libc.def libcpre.def posixpre.def"
++ ;;
++ esac
++ case x${enable_threads} in
++ x | xyes | xposix) thread_file='posix';;
++ xnks) thread_file='nks';;
++ xno) ;;
++ *) echo 'Unknown thread configuration for NetWare' >&2; exit 1;;
++ esac
++ ;;
++i[34567]86-*-nto-qnx*)
++ tm_file="${tm_file} i386/att.h dbxelf.h tm-dwarf2.h elfos.h svr4.h i386/unix.h i386/nto.h"
++ tmake_file="${tmake_file} i386/t-nto"
++ gnu_ld=yes
++ gas=yes
++ ;;
++i[34567]86-*-rtems*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h i386/i386elf.h i386/rtemself.h rtems.h"
++ extra_parts="crtbegin.o crtend.o crti.o crtn.o"
++ tmake_file="${tmake_file} i386/t-rtems-i386 i386/t-crtstuff t-rtems"
++ ;;
++i[34567]86-*-solaris2*)
++ tm_file="${tm_file} i386/unix.h i386/att.h dbxelf.h elfos.h svr4.h i386/sysv4.h sol2.h"
++ case ${target} in
++ *-*-solaris2.1[0-9]*)
++ tm_file="${tm_file} sol2-10.h"
++ ;;
++ esac
++ tm_file="${tm_file} i386/sol2.h"
++ tmake_file="${tmake_file} t-sol2 t-svr4"
++ c_target_objs="${c_target_objs} sol2-c.o"
++ cxx_target_objs="${cxx_target_objs} sol2-c.o"
++ extra_objs="sol2.o"
++ tm_p_file="${tm_p_file} sol2-protos.h"
++ if test x$gnu_ld = xyes; then
++ tmake_file="$tmake_file t-slibgcc-elf-ver"
++ tm_defines="${tm_defines} TARGET_GNU_LD=1"
++ else
++ tmake_file="$tmake_file t-slibgcc-sld"
++ fi
++ if test x$gas = xyes; then
++ tm_file="usegas.h ${tm_file}"
++ fi
++ tm_file="$tm_file tm-dwarf2.h"
++ case ${target} in
++ *-*-solaris2.1[0-9]*)
++ tm_file="${tm_file} i386/x86-64.h i386/sol2-10.h"
++ tm_defines="${tm_defines} TARGET_BI_ARCH=1"
++ tmake_file="$tmake_file i386/t-sol2-10"
++ # i386/t-crtstuff only affects libgcc. Its inclusion
++ # depends on a runtime test and is thus performed in
++ # libgcc/configure.ac instead.
++ need_64bit_hwint=yes
++ case X"${with_cpu}" in
++ Xgeneric|Xcore2|Xnocona|Xx86-64|Xamdfam10|Xbarcelona|Xk8|Xopteron|Xathlon64|Xathlon-fx)
++ ;;
++ X)
++ if test x$with_cpu_64 = x; then
++ with_cpu_64=generic
++ fi
++ ;;
++ *)
++ echo "Unsupported CPU used in --with-cpu=$with_cpu, supported values:" 1>&2
++ echo "generic core2 nocona x86-64 amdfam10 barcelona k8 opteron athlon64 athlon-fx" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++ esac
++ case ${enable_threads}:${have_pthread_h}:${have_thread_h} in
++ "":yes:* | yes:yes:* )
++ thread_file=posix
++ ;;
++ "":*:yes | yes:*:yes )
++ thread_file=solaris
++ ;;
++ esac
++ ;;
++i[4567]86-wrs-vxworks|i[4567]86-wrs-vxworksae)
++ tm_file="${tm_file} i386/unix.h i386/att.h elfos.h svr4.h vx-common.h"
++ case ${target} in
++ *-vxworksae*)
++ tm_file="${tm_file} vxworksae.h i386/vx-common.h i386/vxworksae.h"
++ tmake_file="${tmake_file} i386/t-vxworks i386/t-vxworksae"
++ ;;
++ *)
++ tm_file="${tm_file} vxworks.h i386/vx-common.h i386/vxworks.h"
++ tmake_file="${tmake_file} i386/t-vxworks"
++ ;;
++ esac
++ ;;
++i[34567]86-*-pe | i[34567]86-*-cygwin*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h dbxcoff.h i386/cygming.h i386/cygwin.h"
++ xm_file=i386/xm-cygwin.h
++ # This has to match the logic for DWARF2_UNWIND_INFO in gcc/config/i386/cygming.h
++ if test x$sjlj = x0; then
++ tmake_eh_file="i386/t-dw2-eh"
++ else
++ tmake_eh_file="i386/t-sjlj-eh"
++ fi
++ tmake_file="${tmake_file} ${tmake_eh_file} i386/t-cygming i386/t-cygwin"
++ target_gtfiles="\$(srcdir)/config/i386/winnt.c"
++ extra_options="${extra_options} i386/cygming.opt"
++ extra_objs="winnt.o winnt-stubs.o"
++ c_target_objs="${c_target_objs} cygwin2.o msformat-c.o"
++ cxx_target_objs="${cxx_target_objs} cygwin2.o winnt-cxx.o msformat-c.o"
++ extra_gcc_objs=cygwin1.o
++ if test x$enable_threads = xyes; then
++ thread_file='posix'
++ fi
++ ;;
++i[34567]86-*-mingw* | x86_64-*-mingw*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h dbxcoff.h i386/cygming.h i386/mingw32.h"
++ xm_file=i386/xm-mingw32.h
++ case ${target} in
++ x86_64-*-*)
++ need_64bit_hwint=yes
++ ;;
++ *)
++ ;;
++ esac
++ # This has to match the logic for DWARF2_UNWIND_INFO in gcc/config/i386/cygming.h
++ if test x$sjlj = x0; then
++ tmake_eh_file="i386/t-dw2-eh"
++ else
++ tmake_eh_file="i386/t-sjlj-eh"
++ fi
++ tmake_file="${tmake_file} ${tmake_eh_file} i386/t-cygming i386/t-mingw32"
++ target_gtfiles="\$(srcdir)/config/i386/winnt.c"
++ extra_options="${extra_options} i386/cygming.opt i386/mingw.opt"
++ extra_objs="winnt.o winnt-stubs.o"
++ c_target_objs="${c_target_objs} msformat-c.o"
++ cxx_target_objs="${cxx_target_objs} winnt-cxx.o msformat-c.o"
++ default_use_cxa_atexit=yes
++ case ${enable_threads} in
++ "" | yes | win32)
++ thread_file='win32'
++ tmake_file="${tmake_file} i386/t-gthr-win32"
++ ;;
++ esac
++ case ${target} in
++ x86_64-*-mingw*)
++ tmake_file="${tmake_file} i386/t-crtfm"
++ ;;
++ *)
++ ;;
++ esac
++ case ${target} in
++ *mingw32crt*)
++ tm_file="${tm_file} i386/crtdll.h"
++ ;;
++ *mingw32msv* | *mingw*)
++ ;;
++ esac
++ ;;
++i[34567]86-*-interix3*)
++ tm_file="${tm_file} i386/unix.h i386/bsd.h i386/gas.h i386/i386-interix.h i386/i386-interix3.h interix.h interix3.h"
++ tmake_file="${tmake_file} i386/t-interix"
++ extra_objs=winnt.o
++ target_gtfiles="\$(srcdir)/config/i386/winnt.c"
++ if test x$enable_threads = xyes ; then
++ thread_file='posix'
++ fi
++ if test x$stabs = xyes ; then
++ tm_file="${tm_file} dbxcoff.h"
++ fi
++ ;;
++ia64*-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h ia64/sysv4.h ia64/elf.h"
++ tmake_file="ia64/t-ia64"
++ target_cpu_default="0"
++ if test x$gas = xyes
++ then
++ target_cpu_default="${target_cpu_default}|MASK_GNU_AS"
++ fi
++ if test x$gnu_ld = xyes
++ then
++ target_cpu_default="${target_cpu_default}|MASK_GNU_LD"
++ fi
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtfastmath.o"
++ ;;
++ia64*-*-freebsd*)
++ tm_file="${tm_file} dbxelf.h elfos.h ${fbsd_tm_file} ia64/sysv4.h ia64/freebsd.h"
++ target_cpu_default="MASK_GNU_AS|MASK_GNU_LD"
++ tmake_file="${tmake_file} ia64/t-ia64"
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtfastmath.o"
++ ;;
++ia64*-*-linux*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h ia64/sysv4.h ia64/linux.h"
++ tmake_file="${tmake_file} ia64/t-ia64 t-libunwind ia64/t-glibc"
++ if test x$with_system_libunwind != xyes ; then
++ tmake_file="${tmake_file} t-libunwind-elf ia64/t-glibc-libunwind"
++ fi
++ target_cpu_default="MASK_GNU_AS|MASK_GNU_LD"
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtfastmath.o"
++ ;;
++ia64*-*-hpux*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h ia64/sysv4.h ia64/hpux.h"
++ tmake_file="ia64/t-ia64 ia64/t-hpux"
++ target_cpu_default="MASK_GNU_AS"
++ case x$enable_threads in
++ x | xyes | xposix )
++ thread_file=posix
++ ;;
++ esac
++ use_collect2=no
++ c_target_objs="ia64-c.o"
++ cxx_target_objs="ia64-c.o"
++ extra_options="${extra_options} ia64/ilp32.opt"
++ ;;
++iq2000*-*-elf*)
++ tm_file="svr4.h elfos.h iq2000/iq2000.h"
++ tmake_file=iq2000/t-iq2000
++ out_file=iq2000/iq2000.c
++ md_file=iq2000/iq2000.md
++ ;;
++m32r-*-elf*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ extra_parts="crtinit.o crtfini.o"
++ ;;
++m32rle-*-elf*)
++ tm_file="dbxelf.h elfos.h svr4.h m32r/little.h ${tm_file}"
++ extra_parts="crtinit.o crtfini.o m32rx/crtinit.o m32rx/crtfini.o"
++ ;;
++m32r-*-rtems*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} m32r/rtems.h rtems.h"
++ tmake_file="m32r/t-m32r t-rtems"
++ extra_parts="crtinit.o crtfini.o"
++ ;;
++m32r-*-linux*)
++ tm_file="dbxelf.h elfos.h svr4.h linux.h ${tm_file} m32r/linux.h"
++ # We override the tmake_file for linux -- why?
++ tmake_file="t-slibgcc-elf-ver m32r/t-linux"
++ gnu_ld=yes
++ if test x$enable_threads = xyes; then
++ thread_file='posix'
++ fi
++ ;;
++m32rle-*-linux*)
++ tm_file="dbxelf.h elfos.h svr4.h linux.h m32r/little.h ${tm_file} m32r/linux.h"
++ # We override the tmake_file for linux -- why?
++ tmake_file="t-slibgcc-elf-ver m32r/t-linux"
++ gnu_ld=yes
++ if test x$enable_threads = xyes; then
++ thread_file='posix'
++ fi
++ ;;
++# m68hc11 and m68hc12 share the same machine description.
++m68hc11-*-*|m6811-*-*)
++ tm_file="dbxelf.h elfos.h usegas.h m68hc11/m68hc11.h"
++ tm_p_file="m68hc11/m68hc11-protos.h"
++ md_file="m68hc11/m68hc11.md"
++ out_file="m68hc11/m68hc11.c"
++ tmake_file="m68hc11/t-m68hc11"
++ ;;
++m68hc12-*-*|m6812-*-*)
++ tm_file="m68hc11/m68hc12.h dbxelf.h elfos.h usegas.h m68hc11/m68hc11.h"
++ tm_p_file="m68hc11/m68hc11-protos.h"
++ md_file="m68hc11/m68hc11.md"
++ out_file="m68hc11/m68hc11.c"
++ tmake_file="m68hc11/t-m68hc11"
++ extra_options="${extra_options} m68hc11/m68hc11.opt"
++ ;;
++m68k-*-aout*)
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ tmake_file="m68k/t-floatlib m68k/t-m68kbare m68k/t-mlibs"
++ tm_file="${tm_file} m68k/m68k-none.h m68k/m68kemb.h m68k/m68k-aout.h libgloss.h"
++ ;;
++m68k-*-coff*)
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ tmake_file="m68k/t-floatlib m68k/t-m68kbare m68k/t-mlibs"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ tm_file="${tm_file} m68k/m68k-none.h m68k/m68kemb.h dbxcoff.h m68k/coff.h dbx.h"
++ ;;
++m68k-*-elf* | fido-*-elf*)
++ case ${target} in
++ fido-*-elf*)
++ # Check that $with_cpu makes sense.
++ case $with_cpu in
++ "" | "fidoa")
++ ;;
++ *)
++ echo "Cannot accept --with-cpu=$with_cpu"
++ exit 1
++ ;;
++ esac
++ with_cpu=fidoa
++ ;;
++ *)
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ ;;
++ esac
++ tm_file="${tm_file} m68k/m68k-none.h m68k/m68kelf.h dbxelf.h elfos.h m68k/m68kemb.h m68k/m68020-elf.h"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ tmake_file="m68k/t-floatlib m68k/t-m68kbare m68k/t-m68kelf"
++ # Add multilibs for targets other than fido.
++ case ${target} in
++ fido-*-elf*)
++ ;;
++ *)
++ tmake_file="$tmake_file m68k/t-mlibs"
++ ;;
++ esac
++ extra_parts="crtbegin.o crtend.o"
++ ;;
++m68k*-*-netbsdelf*)
++ default_m68k_cpu=68020
++ default_cf_cpu=5475
++ tm_file="${tm_file} dbxelf.h elfos.h netbsd.h netbsd-elf.h m68k/netbsd-elf.h"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ ;;
++m68k*-*-openbsd*)
++ default_m68k_cpu=68020
++ default_cf_cpu=5475
++ # needed to unconfuse gdb
++ tm_defines="${tm_defines} OBSD_OLD_GAS"
++ tm_file="${tm_file} openbsd.h m68k/openbsd.h"
++ tmake_file="t-libc-ok t-openbsd m68k/t-openbsd"
++ # we need collect2 until our bug is fixed...
++ use_collect2=yes
++ ;;
++m68k-*-uclinuxoldabi*) # Motorola m68k/ColdFire running uClinux
++ # with uClibc, using the original
++ # m68k-elf-based ABI
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ tm_file="${tm_file} m68k/m68k-none.h m68k/m68kelf.h dbxelf.h elfos.h m68k/uclinux-oldabi.h"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ tmake_file="m68k/t-floatlib m68k/t-uclinux"
++ ;;
++m68k-*-uclinux*) # Motorola m68k/ColdFire running uClinux
++ # with uClibc, using the new GNU/Linux-style
++ # ABI.
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h flat.h m68k/linux.h m68k/uclinux.h ./sysroot-suffix.h"
++ tm_defines="${tm_defines} MOTOROLA=1 UCLIBC_DEFAULT=1"
++ extra_options="${extra_options} linux.opt"
++ tmake_file="m68k/t-floatlib m68k/t-uclinux m68k/t-mlibs"
++ ;;
++m68k-*-linux*) # Motorola m68k's running GNU/Linux
++ # with ELF format using glibc 2
++ # aka the GNU/Linux C library 6.
++ default_m68k_cpu=68020
++ default_cf_cpu=5475
++ with_arch=${with_arch:-m68k}
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h m68k/linux.h ./sysroot-suffix.h"
++ extra_options="${extra_options} m68k/ieee.opt"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ tmake_file="${tmake_file} m68k/t-floatlib m68k/t-linux m68k/t-mlibs"
++ # if not configured with --enable-sjlj-exceptions, bump the
++ # libgcc version number
++ if test x$sjlj != x1; then
++ tmake_file="$tmake_file m68k/t-slibgcc-elf-ver"
++ fi
++ ;;
++m68k-*-rtems*)
++ default_m68k_cpu=68020
++ default_cf_cpu=5206
++ tmake_file="m68k/t-floatlib m68k/t-m68kbare m68k/t-crtstuff t-rtems m68k/t-rtems m68k/t-mlibs"
++ tm_file="${tm_file} m68k/m68k-none.h m68k/m68kelf.h dbxelf.h elfos.h m68k/m68kemb.h m68k/m68020-elf.h m68k/rtemself.h rtems.h"
++ tm_defines="${tm_defines} MOTOROLA=1"
++ extra_parts="crtbegin.o crtend.o"
++ ;;
++mcore-*-elf)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} mcore/mcore-elf.h"
++ tmake_file=mcore/t-mcore
++ inhibit_libc=true
++ ;;
++mcore-*-pe*)
++ tm_file="svr3.h dbxcoff.h ${tm_file} mcore/mcore-pe.h"
++ tmake_file=mcore/t-mcore-pe
++ inhibit_libc=true
++ ;;
++mips-sgi-irix[56]*)
++ tm_file="elfos.h ${tm_file} mips/iris.h"
++ tmake_file="mips/t-iris mips/t-slibgcc-irix"
++ target_cpu_default="MASK_ABICALLS"
++ case ${target} in
++ *-*-irix5*)
++ tm_file="${tm_file} mips/iris5.h"
++ ;;
++
++ *-*-irix6*)
++ tm_file="${tm_file} mips/iris6.h"
++ tmake_file="${tmake_file} mips/t-iris6"
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=3 MIPS_ABI_DEFAULT=ABI_N32"
++ ;;
++ esac
++ if test "x$stabs" = xyes
++ then
++ tm_file="${tm_file} dbx.h mips/dbxmdebug.h"
++ fi
++ if test "x$gnu_ld" = xyes
++ then
++ tm_defines="${tm_defines} IRIX_USING_GNU_LD"
++ fi
++ case ${enable_threads}:${have_pthread_h} in
++ "":yes | yes:yes ) thread_file=posix ;;
++ esac
++ ;;
++mips*-*-netbsd*) # NetBSD/mips, either endian.
++ target_cpu_default="MASK_ABICALLS"
++ tm_file="elfos.h ${tm_file} mips/elf.h netbsd.h netbsd-elf.h mips/netbsd.h"
++ ;;
++mips64*-*-linux* | mipsisa64*-*-linux*)
++ tm_file="dbxelf.h elfos.h svr4.h linux.h ${tm_file} mips/linux.h mips/linux64.h"
++ tmake_file="${tmake_file} mips/t-linux64 mips/t-libgcc-mips16"
++ tm_defines="${tm_defines} MIPS_ABI_DEFAULT=ABI_N32"
++ case ${target} in
++ mips64el-st-linux-gnu)
++ tm_file="${tm_file} mips/st.h"
++ tmake_file="${tmake_file} mips/t-st"
++ ;;
++ mips64octeon*-*-linux*)
++ tm_defines="${tm_defines} MIPS_CPU_STRING_DEFAULT=\\\"octeon\\\""
++ target_cpu_default=MASK_SOFT_FLOAT_ABI
++ ;;
++ mipsisa64r2*-*-linux*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=65"
++ ;;
++ esac
++ gnu_ld=yes
++ gas=yes
++ test x$with_llsc != x || with_llsc=yes
++ ;;
++mips*-*-linux*) # Linux MIPS, either endian.
++ tm_file="dbxelf.h elfos.h svr4.h linux.h ${tm_file} mips/linux.h"
++ tmake_file="${tmake_file} mips/t-libgcc-mips16"
++ case ${target} in
++ mipsisa32r2*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=33"
++ ;;
++ mipsisa32*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=32"
++ esac
++ test x$with_llsc != x || with_llsc=yes
++ ;;
++mips*-*-openbsd*)
++ tm_defines="${tm_defines} OBSD_HAS_DECLARE_FUNCTION_NAME OBSD_HAS_DECLARE_OBJECT OBSD_HAS_CORRECT_SPECS"
++ target_cpu_default="MASK_ABICALLS"
++ tm_file="mips/mips.h openbsd.h mips/openbsd.h mips/sdb.h"
++ case ${target} in
++ mips*el-*-openbsd*)
++ tm_defines="${tm_defines} TARGET_ENDIAN_DEFAULT=0";;
++ *) tm_defines="${tm_defines} TARGET_ENDIAN_DEFAULT=MASK_BIG_ENDIAN";;
++ esac
++ ;;
++mips*-sde-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h mips/sde.h"
++ tmake_file="mips/t-sde mips/t-libgcc-mips16"
++ case "${with_newlib}" in
++ yes)
++ # newlib / libgloss.
++ ;;
++ *)
++ # MIPS toolkit libraries.
++ tm_file="$tm_file mips/sdemtk.h"
++ tmake_file="$tmake_file mips/t-sdemtk"
++ extra_options="$extra_options mips/sdemtk.opt"
++ case ${enable_threads} in
++ "" | yes | mipssde)
++ thread_file='mipssde'
++ ;;
++ esac
++ ;;
++ esac
++ case ${target} in
++ mipsisa32r2*)
++ tm_defines="MIPS_ISA_DEFAULT=33 MIPS_ABI_DEFAULT=ABI_32"
++ ;;
++ mipsisa32*)
++ tm_defines="MIPS_ISA_DEFAULT=32 MIPS_ABI_DEFAULT=ABI_32"
++ ;;
++ mipsisa64r2*)
++ tm_defines="MIPS_ISA_DEFAULT=65 MIPS_ABI_DEFAULT=ABI_N32"
++ ;;
++ mipsisa64*)
++ tm_defines="MIPS_ISA_DEFAULT=64 MIPS_ABI_DEFAULT=ABI_N32"
++ ;;
++ esac
++ ;;
++mipsisa32-*-elf* | mipsisa32el-*-elf* | \
++mipsisa32r2-*-elf* | mipsisa32r2el-*-elf* | \
++mipsisa64-*-elf* | mipsisa64el-*-elf* | \
++mipsisa64r2-*-elf* | mipsisa64r2el-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h"
++ tmake_file="mips/t-isa3264 mips/t-libgcc-mips16"
++ case ${target} in
++ mipsisa32r2*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=33"
++ ;;
++ mipsisa32*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=32"
++ ;;
++ mipsisa64r2*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=65"
++ ;;
++ mipsisa64*)
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=64"
++ ;;
++ esac
++ case ${target} in
++ mipsisa32*-*-elfoabi*)
++ tm_defines="${tm_defines} MIPS_ABI_DEFAULT=ABI_32"
++ tm_file="${tm_file} mips/elfoabi.h"
++ ;;
++ mipsisa64*-*-elfoabi*)
++ tm_defines="${tm_defines} MIPS_ABI_DEFAULT=ABI_O64"
++ tm_file="${tm_file} mips/elfoabi.h"
++ ;;
++ *-*-elf*)
++ tm_defines="${tm_defines} MIPS_ABI_DEFAULT=ABI_EABI"
++ ;;
++ esac
++ ;;
++mipsisa64sr71k-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h"
++ tmake_file=mips/t-sr71k
++ target_cpu_default="MASK_64BIT|MASK_FLOAT64"
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=64 MIPS_CPU_STRING_DEFAULT=\\\"sr71000\\\" MIPS_ABI_DEFAULT=ABI_EABI"
++ ;;
++mipsisa64sb1-*-elf* | mipsisa64sb1el-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h"
++ tmake_file="mips/t-elf mips/t-libgcc-mips16 mips/t-sb1"
++ target_cpu_default="MASK_64BIT|MASK_FLOAT64"
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=64 MIPS_CPU_STRING_DEFAULT=\\\"sb1\\\" MIPS_ABI_DEFAULT=ABI_O64"
++ ;;
++mips-*-elf* | mipsel-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h"
++ tmake_file="mips/t-elf mips/t-libgcc-mips16"
++ ;;
++mips64-*-elf* | mips64el-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elf.h"
++ tmake_file="mips/t-elf mips/t-libgcc-mips16"
++ target_cpu_default="MASK_64BIT|MASK_FLOAT64"
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=3 MIPS_ABI_DEFAULT=ABI_O64"
++ ;;
++mips64vr-*-elf* | mips64vrel-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/vr.h mips/elf.h"
++ tmake_file=mips/t-vr
++ ;;
++mips64orion-*-elf* | mips64orionel-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/elforion.h mips/elf.h"
++ tmake_file="mips/t-elf mips/t-libgcc-mips16"
++ target_cpu_default="MASK_64BIT|MASK_FLOAT64"
++ tm_defines="${tm_defines} MIPS_ISA_DEFAULT=3 MIPS_ABI_DEFAULT=ABI_O64"
++ ;;
++mips*-*-rtems*)
++ tm_file="elfos.h ${tm_file} mips/elf.h mips/rtems.h rtems.h"
++ tmake_file="mips/t-elf mips/t-libgcc-mips16 t-rtems mips/t-rtems"
++ ;;
++mips-wrs-vxworks)
++ tm_file="elfos.h ${tm_file} svr4.h mips/elf.h vx-common.h vxworks.h mips/vxworks.h"
++ tmake_file="${tmake_file} mips/t-vxworks"
++ ;;
++mipstx39-*-elf* | mipstx39el-*-elf*)
++ tm_file="elfos.h ${tm_file} mips/r3900.h mips/elf.h"
++ tmake_file="mips/t-r3900 mips/t-libgcc-mips16"
++ ;;
++mmix-knuth-mmixware)
++ need_64bit_hwint=yes
++ ;;
++mn10300-*-*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ if test x$stabs = xyes
++ then
++ tm_file="${tm_file} dbx.h"
++ fi
++ use_collect2=no
++ ;;
++pdp11-*-bsd)
++ tm_file="${tm_file} pdp11/2bsd.h"
++ use_fixproto=yes
++ ;;
++pdp11-*-*)
++ ;;
++picochip-*)
++ # Nothing special
++ ;;
++# port not yet contributed
++#powerpc-*-openbsd*)
++# tmake_file="${tmake_file} rs6000/t-fprules rs6000/t-fprules-fpbit "
++# extra_headers=
++# ;;
++powerpc64-*-linux*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h"
++ test x$with_cpu != x || cpu_is_64bit=yes
++ test x$cpu_is_64bit != xyes || tm_file="${tm_file} rs6000/default64.h"
++ tm_file="rs6000/biarch64.h ${tm_file} rs6000/linux64.h"
++ if test x${enable_secureplt} = xyes; then
++ tm_file="rs6000/secureplt.h ${tm_file}"
++ fi
++ extra_options="${extra_options} rs6000/sysv4.opt rs6000/linux64.opt"
++ tmake_file="t-dfprules rs6000/t-fprules ${tmake_file} rs6000/t-ppccomm rs6000/t-linux64 rs6000/t-fprules-softfp soft-fp/t-softfp"
++ ;;
++powerpc64-*-gnu*)
++ tm_file="${cpu_type}/${cpu_type}.h elfos.h svr4.h freebsd-spec.h gnu.h rs6000/sysv4.h rs6000/linux64.h rs6000/gnu.h"
++ extra_options="${extra_options} rs6000/sysv4.opt rs6000/linux64.opt"
++ tmake_file="rs6000/t-fprules t-slibgcc-elf-ver t-gnu rs6000/t-linux64 rs6000/t-fprules-softfp soft-fp/t-softfp"
++ ;;
++powerpc-*-darwin*)
++ extra_options="${extra_options} rs6000/darwin.opt"
++ extra_parts="crt2.o"
++ case ${target} in
++ *-darwin1[0-9]* | *-darwin[8-9]*)
++ tmake_file="${tmake_file} rs6000/t-darwin8"
++ tm_file="${tm_file} rs6000/darwin8.h"
++ ;;
++ *-darwin7*)
++ tm_file="${tm_file} rs6000/darwin7.h"
++ ;;
++ *-darwin[0-6]*)
++ ;;
++ esac
++ extra_headers=altivec.h
++ ;;
++powerpc64-*-darwin*)
++ tm_file="${tm_file} ${cpu_type}/darwin8.h ${cpu_type}/darwin64.h"
++ extra_options="${extra_options} ${cpu_type}/darwin.opt"
++ # We're omitting t-darwin8 to avoid building any multilibs
++ extra_headers=altivec.h
++ ;;
++powerpc*-*-freebsd*)
++ tm_file="${tm_file} dbxelf.h elfos.h ${fbsd_tm_file} rs6000/sysv4.h rs6000/freebsd.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ ;;
++powerpc-*-netbsd*)
++ tm_file="${tm_file} dbxelf.h elfos.h netbsd.h netbsd-elf.h freebsd-spec.h rs6000/sysv4.h rs6000/netbsd.h"
++ tmake_file="${tmake_file} rs6000/t-netbsd"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ ;;
++powerpc-*-eabispe*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h rs6000/eabispe.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-spe rs6000/t-ppccomm"
++ ;;
++powerpc-*-eabisimaltivec*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h rs6000/eabisim.h rs6000/eabialtivec.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcendian rs6000/t-ppccomm"
++ ;;
++powerpc-*-eabisim*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h rs6000/eabisim.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ ;;
++powerpc-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ ;;
++powerpc-*-eabialtivec*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h rs6000/eabialtivec.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcendian rs6000/t-ppccomm"
++ ;;
++powerpc-xilinx-eabi*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/singlefp.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ ;;
++powerpc-*-eabi*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ ;;
++powerpc-*-rtems*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/e500.h rs6000/rtems.h rtems.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-rtems t-rtems rs6000/t-ppccomm"
++ ;;
++powerpc-*-linux*altivec*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/linux.h rs6000/linuxaltivec.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-softfp soft-fp/t-softfp rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
++ ;;
++powerpc-*-linux*spe*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/linux.h rs6000/linuxspe.h rs6000/e500.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="t-dfprules rs6000/t-fprules rs6000/t-fprules-softfp soft-fp/t-softfp rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
++ ;;
++powerpc-*-linux*paired*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/linux.h rs6000/750cl.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-softfp soft-fp/t-softfp rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
++ ;;
++powerpc-*-linux*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="t-dfprules rs6000/t-fprules rs6000/t-ppcos ${tmake_file} rs6000/t-ppccomm"
++ case ${enable_targets}:${cpu_is_64bit} in
++ *powerpc64* | all:* | *:yes)
++ if test x$cpu_is_64bit = xyes; then
++ tm_file="${tm_file} rs6000/default64.h"
++ fi
++ tm_file="rs6000/biarch64.h ${tm_file} rs6000/linux64.h"
++ tmake_file="$tmake_file rs6000/t-linux64"
++ extra_options="${extra_options} rs6000/linux64.opt"
++ ;;
++ *)
++ tm_file="${tm_file} rs6000/linux.h"
++ ;;
++ esac
++ tmake_file="${tmake_file} rs6000/t-fprules-softfp soft-fp/t-softfp"
++ if test x${enable_secureplt} = xyes; then
++ tm_file="rs6000/secureplt.h ${tm_file}"
++ fi
++ ;;
++powerpc-*-gnu-gnualtivec*)
++ tm_file="${cpu_type}/${cpu_type}.h elfos.h svr4.h freebsd-spec.h gnu.h rs6000/sysv4.h rs6000/linux.h rs6000/linuxaltivec.h rs6000/gnu.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcos t-slibgcc-elf-ver t-gnu rs6000/t-ppccomm"
++ if test x$enable_threads = xyes; then
++ thread_file='posix'
++ fi
++ ;;
++powerpc-*-gnu*)
++ tm_file="${cpu_type}/${cpu_type}.h elfos.h svr4.h freebsd-spec.h gnu.h rs6000/sysv4.h rs6000/linux.h rs6000/gnu.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcos t-slibgcc-elf-ver t-gnu rs6000/t-ppccomm"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ if test x$enable_threads = xyes; then
++ thread_file='posix'
++ fi
++ ;;
++powerpc-wrs-vxworks|powerpc-wrs-vxworksae)
++ tm_file="${tm_file} elfos.h svr4.h freebsd-spec.h rs6000/sysv4.h"
++ tmake_file="${tmake_file} rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppccomm rs6000/t-vxworks"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ extra_headers=ppc-asm.h
++ case ${target} in
++ *-vxworksae*)
++ tm_file="${tm_file} vx-common.h vxworksae.h rs6000/vxworks.h rs6000/e500.h rs6000/vxworksae.h"
++ tmake_file="${tmake_file} rs6000/t-vxworksae"
++ ;;
++ *-vxworks*)
++ tm_file="${tm_file} vx-common.h vxworks.h rs6000/vxworks.h rs6000/e500.h"
++ ;;
++ esac
++ ;;
++powerpc-*-lynxos*)
++ xm_defines=POSIX
++ tm_file="${tm_file} dbxelf.h elfos.h rs6000/sysv4.h rs6000/lynx.h lynx.h"
++ tmake_file="t-lynx rs6000/t-lynx"
++ extra_options="${extra_options} rs6000/sysv4.opt lynx.opt"
++ extra_parts="crtbegin.o crtbeginS.o crtend.o crtendS.o"
++ extra_options="${extra_options} lynx.opt"
++ thread_file=lynx
++ gnu_ld=yes
++ gas=yes
++ ;;
++powerpcle-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/sysv4le.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ ;;
++powerpcle-*-eabisim*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/sysv4le.h rs6000/eabi.h rs6000/e500.h rs6000/eabisim.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ ;;
++powerpcle-*-eabi*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/sysv4le.h rs6000/eabi.h rs6000/e500.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ ;;
++powerpc-xilinx-eabi*)
++ tm_file="${tm_file} dbxelf.h elfos.h usegas.h svr4.h freebsd-spec.h rs6000/sysv4.h rs6000/eabi.h rs6000/singlefp.h rs6000/xfpu.h"
++ extra_options="${extra_options} rs6000/sysv4.opt"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-ppcgas rs6000/t-ppccomm"
++ ;;
++rs6000-ibm-aix4.[12]* | powerpc-ibm-aix4.[12]*)
++ tm_file="${tm_file} rs6000/aix.h rs6000/aix41.h rs6000/xcoff.h"
++ tmake_file="rs6000/t-fprules rs6000/t-fprules-fpbit rs6000/t-newas"
++ extra_options="${extra_options} rs6000/aix41.opt"
++ use_collect2=yes
++ extra_headers=
++ use_fixproto=yes
++ ;;
++rs6000-ibm-aix4.[3456789]* | powerpc-ibm-aix4.[3456789]*)
++ tm_file="rs6000/biarch64.h ${tm_file} rs6000/aix.h rs6000/aix43.h rs6000/xcoff.h"
++ tmake_file=rs6000/t-aix43
++ extra_options="${extra_options} rs6000/aix64.opt"
++ use_collect2=yes
++ thread_file='aix'
++ extra_headers=
++ ;;
++rs6000-ibm-aix5.1.* | powerpc-ibm-aix5.1.*)
++ tm_file="rs6000/biarch64.h ${tm_file} rs6000/aix.h rs6000/aix51.h rs6000/xcoff.h"
++ extra_options="${extra_options} rs6000/aix64.opt"
++ tmake_file=rs6000/t-aix43
++ use_collect2=yes
++ thread_file='aix'
++ extra_headers=
++ ;;
++rs6000-ibm-aix5.2.* | powerpc-ibm-aix5.2.*)
++ tm_file="${tm_file} rs6000/aix.h rs6000/aix52.h rs6000/xcoff.h"
++ tmake_file=rs6000/t-aix52
++ extra_options="${extra_options} rs6000/aix64.opt"
++ use_collect2=yes
++ thread_file='aix'
++ extra_headers=
++ ;;
++rs6000-ibm-aix5.3.* | powerpc-ibm-aix5.3.*)
++ tm_file="${tm_file} rs6000/aix.h rs6000/aix53.h rs6000/xcoff.h"
++ tmake_file=rs6000/t-aix52
++ extra_options="${extra_options} rs6000/aix64.opt"
++ use_collect2=yes
++ thread_file='aix'
++ extra_headers=altivec.h
++ ;;
++rs6000-ibm-aix[6789].* | powerpc-ibm-aix[6789].*)
++ tm_file="${tm_file} rs6000/aix.h rs6000/aix61.h rs6000/xcoff.h"
++ tmake_file=rs6000/t-aix52
++ extra_options="${extra_options} rs6000/aix64.opt"
++ use_collect2=yes
++ thread_file='aix'
++ extra_headers=altivec.h
++ ;;
++s390-*-linux*)
++ tm_file="s390/s390.h dbxelf.h elfos.h svr4.h linux.h s390/linux.h"
++ tmake_file="${tmake_file} t-dfprules s390/t-crtstuff s390/t-linux"
++ ;;
++s390x-*-linux*)
++ tm_file="s390/s390x.h s390/s390.h dbxelf.h elfos.h svr4.h linux.h s390/linux.h"
++ tm_p_file=s390/s390-protos.h
++ md_file=s390/s390.md
++ extra_modes=s390/s390-modes.def
++ out_file=s390/s390.c
++ tmake_file="${tmake_file} t-dfprules s390/t-crtstuff s390/t-linux s390/t-linux64"
++ ;;
++s390x-ibm-tpf*)
++ tm_file="s390/s390x.h s390/s390.h dbxelf.h elfos.h svr4.h s390/tpf.h"
++ tm_p_file=s390/s390-protos.h
++ md_file=s390/s390.md
++ extra_modes=s390/s390-modes.def
++ out_file=s390/s390.c
++ extra_parts="crtbeginS.o crtendS.o"
++ tmake_file="s390/t-crtstuff s390/t-tpf"
++ thread_file='tpf'
++ extra_options="${extra_options} s390/tpf.opt"
++ ;;
++score-*-elf)
++ tm_file="dbxelf.h elfos.h score/elf.h score/score.h"
++ tmake_file=score/t-score-elf
++ extra_objs="score7.o score3.o"
++ ;;
++sh-*-elf* | sh[12346l]*-*-elf* | \
++sh-*-symbianelf* | sh[12346l]*-*-symbianelf* | \
++ sh-*-linux* | sh[2346lbe]*-*-linux* | \
++ sh-*-netbsdelf* | shl*-*-netbsdelf* | sh5-*-netbsd* | sh5l*-*-netbsd* | \
++ sh64-*-netbsd* | sh64l*-*-netbsd*)
++ tmake_file="${tmake_file} sh/t-sh sh/t-elf"
++ if test x${with_endian} = x; then
++ case ${target} in
++ sh[1234]*be-*-* | sh[1234]*eb-*-*) with_endian=big ;;
++ shbe-*-* | sheb-*-*) with_endian=big,little ;;
++ sh[1234]l* | sh[34]*-*-linux*) with_endian=little ;;
++ shl* | sh64l* | sh*-*-linux* | \
++ sh5l* | sh-superh-elf) with_endian=little,big ;;
++ sh[1234]*-*-*) with_endian=big ;;
++ *) with_endian=big,little ;;
++ esac
++ fi
++ case ${with_endian} in
++ big|little) tmake_file="${tmake_file} sh/t-1e" ;;
++ big,little|little,big) ;;
++ *) echo "with_endian=${with_endian} not supported."; exit 1 ;;
++ esac
++ case ${with_endian} in
++ little*) tm_file="sh/little.h ${tm_file}" ;;
++ esac
++ tm_file="${tm_file} dbxelf.h elfos.h"
++ case ${target} in
++ sh*-*-netbsd*) ;;
++ *) tm_file="${tm_file} svr4.h" ;;
++ esac
++ tm_file="${tm_file} sh/elf.h"
++ case ${target} in
++ sh*-*-linux*) tmake_file="${tmake_file} sh/t-linux"
++ tm_file="${tm_file} linux.h sh/linux.h" ;;
++ sh*-*-netbsd*) tm_file="${tm_file} netbsd.h netbsd-elf.h sh/netbsd-elf.h" ;;
++ sh*-superh-elf) if test x$with_libgloss != xno; then
++ with_libgloss=yes
++ tm_file="${tm_file} sh/newlib.h"
++ fi
++ tm_file="${tm_file} sh/embed-elf.h sh/superh.h"
++ tmake_file="${tmake_file} sh/t-superh"
++ extra_options="${extra_options} sh/superh.opt" ;;
++ *) if test x$with_newlib = xyes \
++ && test x$with_libgloss = xyes; then
++ tm_file="${tm_file} sh/newlib.h"
++ fi
++ tm_file="${tm_file} sh/embed-elf.h" ;;
++ esac
++ case ${target} in
++ sh5*-*-netbsd*)
++ # SHmedia, 32-bit ABI
++ tmake_file="${tmake_file} sh/t-sh64 sh/t-netbsd"
++ ;;
++ sh64*-netbsd*)
++ # SHmedia, 64-bit ABI
++ tmake_file="${tmake_file} sh/t-sh64 sh/t-netbsd sh/t-netbsd-sh5-64"
++ ;;
++ *-*-netbsd)
++ tmake_file="${tmake_file} sh/t-netbsd"
++ ;;
++ sh64*-*-linux*)
++ tmake_file="${tmake_file} sh/t-sh64 sh/t-linux64"
++ tm_file="${tm_file} sh/sh64.h"
++ extra_headers="shmedia.h ushmedia.h sshmedia.h"
++ ;;
++ sh64*)
++ tmake_file="${tmake_file} sh/t-sh64"
++ tm_file="${tm_file} sh/sh64.h"
++ extra_headers="shmedia.h ushmedia.h sshmedia.h"
++ ;;
++ *-*-symbianelf*)
++ tmake_file="sh/t-symbian"
++ tm_file="sh/symbian-pre.h sh/little.h ${tm_file} sh/symbian-post.h"
++ extra_objs="symbian.o"
++ extra_parts="crt1.o crti.o crtn.o crtbegin.o crtend.o crtbeginS.o crtendS.o"
++ ;;
++ esac
++ # sed el/eb endian suffixes away to avoid confusion with sh[23]e
++ case `echo ${target} | sed 's/e[lb]-/-/'` in
++ sh64*-*-netbsd*) sh_cpu_target=sh5-64media ;;
++ sh64* | sh5*-*-netbsd*) sh_cpu_target=sh5-32media ;;
++ sh4a_single_only*) sh_cpu_target=sh4a-single-only ;;
++ sh4a_single*) sh_cpu_target=sh4a-single ;;
++ sh4a_nofpu*) sh_cpu_target=sh4a-nofpu ;;
++ sh4al) sh_cpu_target=sh4al ;;
++ sh4a*) sh_cpu_target=sh4a ;;
++ sh4_single_only*) sh_cpu_target=sh4-single-only ;;
++ sh4_single*) sh_cpu_target=sh4-single ;;
++ sh4_nofpu*) sh_cpu_target=sh4-nofpu ;;
++ sh4* | sh-superh-*) sh_cpu_target=sh4 ;;
++ sh3e*) sh_cpu_target=sh3e ;;
++ sh*-*-netbsd* | sh3*) sh_cpu_target=sh3 ;;
++ sh2a_single_only*) sh_cpu_target=sh2a-single-only ;;
++ sh2a_single*) sh_cpu_target=sh2a-single ;;
++ sh2a_nofpu*) sh_cpu_target=sh2a-nofpu ;;
++ sh2a*) sh_cpu_target=sh2a ;;
++ sh2e*) sh_cpu_target=sh2e ;;
++ sh2*) sh_cpu_target=sh2 ;;
++ *) sh_cpu_target=sh1 ;;
++ esac
++ # did the user say --without-fp ?
++ if test x$with_fp = xno; then
++ case ${sh_cpu_target} in
++ sh5-*media) sh_cpu_target=${sh_cpu_target}-nofpu ;;
++ sh4al | sh1) ;;
++ sh4a* ) sh_cpu_target=sh4a-nofpu ;;
++ sh4*) sh_cpu_target=sh4-nofpu ;;
++ sh3*) sh_cpu_target=sh3 ;;
++ sh2a*) sh_cpu_target=sh2a-nofpu ;;
++ sh2*) sh_cpu_target=sh2 ;;
++ *) echo --without-fp not available for $target: ignored
++ esac
++ tm_defines="$tm_defines STRICT_NOFPU=1"
++ fi
++ sh_cpu_default="`echo $with_cpu|sed s/^m/sh/|tr A-Z_ a-z-`"
++ case $sh_cpu_default in
++ sh5-64media-nofpu | sh5-64media | \
++ sh5-32media-nofpu | sh5-32media | sh5-compact-nofpu | sh5-compact | \
++ sh2a-single-only | sh2a-single | sh2a-nofpu | sh2a | \
++ sh4a-single-only | sh4a-single | sh4a-nofpu | sh4a | sh4al | \
++ sh4-single-only | sh4-single | sh4-nofpu | sh4 | sh4-300 | \
++ sh3e | sh3 | sh2e | sh2 | sh1) ;;
++ "") sh_cpu_default=${sh_cpu_target} ;;
++ *) echo "with_cpu=$with_cpu not supported"; exit 1 ;;
++ esac
++ sh_multilibs=${with_multilib_list}
++ if test x${sh_multilibs} = x ; then
++ case ${target} in
++ sh64-superh-linux* | \
++ sh[1234]*) sh_multilibs=${sh_cpu_target} ;;
++ sh64* | sh5*) sh_multilibs=m5-32media,m5-32media-nofpu,m5-compact,m5-compact-nofpu,m5-64media,m5-64media-nofpu ;;
++ sh-superh-*) sh_multilibs=m4,m4-single,m4-single-only,m4-nofpu ;;
++ sh*-*-linux*) sh_multilibs=m1,m3e,m4 ;;
++ sh*-*-netbsd*) sh_multilibs=m3,m3e,m4 ;;
++ *) sh_multilibs=m1,m2,m2e,m4,m4-single,m4-single-only,m2a,m2a-single ;;
++ esac
++ if test x$with_fp = xno; then
++ sh_multilibs="`echo $sh_multilibs|sed -e s/m4/sh4-nofpu/ -e s/,m4-[^,]*//g -e s/,m[23]e// -e s/m2a,m2a-single/m2a-nofpu/ -e s/m5-..m....,//g`"
++ fi
++ fi
++ target_cpu_default=SELECT_`echo ${sh_cpu_default}|tr abcdefghijklmnopqrstuvwxyz- ABCDEFGHIJKLMNOPQRSTUVWXYZ_`
++ tm_defines=${tm_defines}' SH_MULTILIB_CPU_DEFAULT=\"'`echo $sh_cpu_default|sed s/sh/m/`'\"'
++ sh_multilibs=`echo $sh_multilibs,$sh_cpu_default | sed -e 's/[ ,/][ ,]*/ /g' -e 's/ $//' -e 's/^m/sh/' -e 's/ m/ sh/g' | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ_ abcdefghijklmnopqrstuvwxyz-`
++ for sh_multilib in ${sh_multilibs}; do
++ case ${sh_multilib} in
++ sh1 | sh2 | sh2e | sh3 | sh3e | \
++ sh4 | sh4-single | sh4-single-only | sh4-nofpu | sh4-300 |\
++ sh4a | sh4a-single | sh4a-single-only | sh4a-nofpu | sh4al | \
++ sh2a | sh2a-single | sh2a-single-only | sh2a-nofpu | \
++ sh5-64media | sh5-64media-nofpu | \
++ sh5-32media | sh5-32media-nofpu | \
++ sh5-compact | sh5-compact-nofpu)
++ tmake_file="${tmake_file} sh/t-mlib-${sh_multilib}"
++ tm_defines="$tm_defines SUPPORT_`echo $sh_multilib|tr abcdefghijklmnopqrstuvwxyz- ABCDEFGHIJKLMNOPQRSTUVWXYZ_`=1"
++ ;;
++ *)
++ echo "with_multilib_list=${sh_multilib} not supported."
++ exit 1
++ ;;
++ esac
++ done
++ if test x${enable_incomplete_targets} = xyes ; then
++ tm_defines="$tm_defines SUPPORT_SH1=1 SUPPORT_SH2E=1 SUPPORT_SH4=1 SUPPORT_SH4_SINGLE=1 SUPPORT_SH2A=1 SUPPORT_SH2A_SINGLE=1 SUPPORT_SH5_32MEDIA=1 SUPPORT_SH5_32MEDIA_NOFPU=1 SUPPORT_SH5_64MEDIA=1 SUPPORT_SH5_64MEDIA_NOFPU=1"
++ fi
++ ;;
++sh-*-rtems*)
++ tmake_file="sh/t-sh sh/t-elf t-rtems sh/t-rtems"
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sh/elf.h sh/embed-elf.h sh/rtemself.h rtems.h"
++ ;;
++sh-wrs-vxworks)
++ tmake_file="$tmake_file sh/t-sh sh/t-elf sh/t-vxworks"
++ tm_file="${tm_file} elfos.h svr4.h sh/elf.h sh/embed-elf.h vx-common.h vxworks.h sh/vxworks.h"
++ ;;
++sh-*-*)
++ tm_file="${tm_file} dbxcoff.h sh/coff.h"
++ ;;
++sparc-*-netbsdelf*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h netbsd.h netbsd-elf.h sparc/netbsd-elf.h"
++ extra_options="${extra_options} sparc/long-double-switch.opt"
++ ;;
++sparc64-*-openbsd*)
++ tm_file="sparc/openbsd1-64.h ${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sparc/sp64-elf.h openbsd.h sparc/openbsd64.h"
++ extra_options="${extra_options} sparc/little-endian.opt"
++ gas=yes gnu_ld=yes
++ with_cpu=ultrasparc
++ ;;
++sparc-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sparc/sp-elf.h"
++ tmake_file="sparc/t-elf sparc/t-crtfm"
++ extra_parts="crti.o crtn.o crtbegin.o crtend.o"
++ ;;
++sparc-*-linux*) # SPARC's running GNU/Linux, libc6
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h linux.h"
++ extra_options="${extra_options} sparc/long-double-switch.opt"
++ tmake_file="${tmake_file} sparc/t-linux"
++ if test x$enable_targets = xall; then
++ tm_file="sparc/biarch64.h ${tm_file} sparc/linux64.h"
++ tmake_file="${tmake_file} sparc/t-linux64"
++ else
++ tm_file="${tm_file} sparc/linux.h"
++ fi
++ tmake_file="${tmake_file} sparc/t-crtfm"
++ ;;
++sparc-*-rtems*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sparc/sp-elf.h sparc/rtemself.h rtems.h"
++ tmake_file="sparc/t-elf sparc/t-crtfm t-rtems"
++ extra_parts="crti.o crtn.o crtbegin.o crtend.o"
++ ;;
++sparc64-*-solaris2* | sparcv9-*-solaris2*)
++ tm_file="sparc/biarch64.h ${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sol2.h"
++ case ${target} in
++ *-*-solaris2.1[0-9]*)
++ tm_file="${tm_file} sol2-10.h"
++ ;;
++ esac
++ tm_file="${tm_file} sparc/sol2.h sparc/sol2-64.h sparc/sol2-bi.h"
++ if test x$gnu_ld = xyes; then
++ tm_file="${tm_file} sparc/sol2-gld.h sparc/sol2-gld-bi.h"
++ fi
++ if test x$gas = xyes; then
++ tm_file="${tm_file} sparc/sol2-gas.h sparc/sol2-gas-bi.h"
++ fi
++ tm_file="${tm_file} tm-dwarf2.h"
++ tmake_file="t-sol2 sparc/t-sol2 sparc/t-sol2-64 sparc/t-crtfm"
++ if test x$gnu_ld = xyes; then
++ tmake_file="$tmake_file t-slibgcc-elf-ver"
++ else
++ tmake_file="$tmake_file t-slibgcc-sld"
++ fi
++ c_target_objs="sol2-c.o"
++ cxx_target_objs="sol2-c.o"
++ extra_objs="sol2.o"
++ tm_p_file="${tm_p_file} sol2-protos.h"
++ extra_parts="crt1.o crti.o crtn.o gcrt1.o crtbegin.o crtend.o"
++ case ${enable_threads}:${have_pthread_h}:${have_thread_h} in
++ "":yes:* | yes:yes:* ) thread_file=posix ;;
++ "":*:yes | yes:*:yes ) thread_file=solaris ;;
++ esac
++ ;;
++sparc-*-solaris2*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sol2.h"
++ case ${target} in
++ *-*-solaris2.1[0-9]*)
++ tm_file="${tm_file} sol2-10.h"
++ ;;
++ esac
++ tm_file="${tm_file} sparc/sol2.h"
++ if test x$gnu_ld = xyes; then
++ tm_file="${tm_file} sparc/sol2-gld.h"
++ fi
++ if test x$gas = xyes; then
++ tm_file="${tm_file} sparc/sol2-gas.h"
++ fi
++ tmake_file="t-sol2 sparc/t-sol2 sparc/t-crtfm"
++ if test x$gnu_ld = xyes; then
++ tmake_file="$tmake_file t-slibgcc-elf-ver"
++ else
++ tmake_file="$tmake_file t-slibgcc-sld"
++ fi
++ tm_file="sparc/biarch64.h ${tm_file} sparc/sol2-bi.h"
++ if test x$gnu_ld = xyes; then
++ tm_file="${tm_file} sparc/sol2-gld-bi.h"
++ fi
++ if test x$gas = xyes; then
++ tm_file="${tm_file} sparc/sol2-gas-bi.h"
++ fi
++ tm_file="${tm_file} tm-dwarf2.h"
++ tmake_file="$tmake_file sparc/t-sol2-64"
++ test x$with_cpu != x || with_cpu=v9
++ c_target_objs="sol2-c.o"
++ cxx_target_objs="sol2-c.o"
++ extra_objs="sol2.o"
++ tm_p_file="${tm_p_file} sol2-protos.h"
++ extra_parts="crt1.o crti.o crtn.o gcrt1.o gmon.o crtbegin.o crtend.o"
++ case ${enable_threads}:${have_pthread_h}:${have_thread_h} in
++ "":yes:* | yes:yes:* )
++ thread_file=posix
++ ;;
++ "":*:yes | yes:*:yes )
++ thread_file=solaris
++ ;;
++ esac
++ ;;
++sparc-wrs-vxworks)
++ tm_file="${tm_file} elfos.h svr4.h sparc/sysv4.h vx-common.h vxworks.h sparc/vxworks.h"
++ tmake_file="${tmake_file} sparc/t-vxworks"
++ ;;
++sparc64-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h sparc/sp64-elf.h"
++ extra_options="${extra_options} sparc/little-endian.opt"
++ tmake_file="${tmake_file} sparc/t-crtfm"
++ extra_parts="crtbegin.o crtend.o"
++ ;;
++sparc64-*-freebsd*|ultrasparc-*-freebsd*)
++ tm_file="${tm_file} ${fbsd_tm_file} dbxelf.h elfos.h sparc/sysv4.h sparc/freebsd.h"
++ extra_options="${extra_options} sparc/long-double-switch.opt"
++ tmake_file="${tmake_file} sparc/t-crtfm"
++ case "x$with_cpu" in
++ xultrasparc) ;;
++ x) with_cpu=ultrasparc ;;
++ *) echo "$with_cpu not supported for freebsd target"; exit 1 ;;
++ esac
++ ;;
++sparc64-*-linux*) # 64-bit SPARC's running GNU/Linux
++ tm_file="sparc/biarch64.h ${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h linux.h sparc/linux64.h"
++ extra_options="${extra_options} sparc/long-double-switch.opt"
++ tmake_file="${tmake_file} sparc/t-linux sparc/t-linux64 sparc/t-crtfm"
++ ;;
++sparc64-*-netbsd*)
++ tm_file="sparc/biarch64.h ${tm_file}"
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h sparc/sysv4.h netbsd.h netbsd-elf.h sparc/netbsd-elf.h"
++ extra_options="${extra_options} sparc/long-double-switch.opt"
++ tmake_file="${tmake_file} sparc/t-netbsd64"
++ ;;
++spu-*-elf*)
++ tm_file="dbxelf.h elfos.h spu/spu-elf.h spu/spu.h"
++ tmake_file="spu/t-spu-elf"
++ extra_headers="spu_intrinsics.h spu_internals.h vmx2spu.h spu_mfcio.h vec_types.h"
++ extra_modes=spu/spu-modes.def
++ c_target_objs="${c_target_objs} spu-c.o"
++ cxx_target_objs="${cxx_target_objs} spu-c.o"
++ ;;
++v850e1-*-*)
++ target_cpu_default="TARGET_CPU_v850e1"
++ tm_file="dbxelf.h elfos.h svr4.h v850/v850.h"
++ tm_p_file=v850/v850-protos.h
++ tmake_file=v850/t-v850e
++ md_file=v850/v850.md
++ out_file=v850/v850.c
++ extra_options="${extra_options} v850/v850.opt"
++ if test x$stabs = xyes
++ then
++ tm_file="${tm_file} dbx.h"
++ fi
++ use_collect2=no
++ c_target_objs="v850-c.o"
++ cxx_target_objs="v850-c.o"
++ ;;
++v850e-*-*)
++ target_cpu_default="TARGET_CPU_v850e"
++ tm_file="dbxelf.h elfos.h svr4.h v850/v850.h"
++ tm_p_file=v850/v850-protos.h
++ tmake_file=v850/t-v850e
++ md_file=v850/v850.md
++ out_file=v850/v850.c
++ extra_options="${extra_options} v850/v850.opt"
++ if test x$stabs = xyes
++ then
++ tm_file="${tm_file} dbx.h"
++ fi
++ use_collect2=no
++ c_target_objs="v850-c.o"
++ cxx_target_objs="v850-c.o"
++ ;;
++v850-*-*)
++ target_cpu_default="TARGET_CPU_generic"
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ tmake_file=v850/t-v850
++ if test x$stabs = xyes
++ then
++ tm_file="${tm_file} dbx.h"
++ fi
++ use_collect2=no
++ c_target_objs="v850-c.o"
++ cxx_target_objs="v850-c.o"
++ ;;
++vax-*-netbsdelf*)
++ tm_file="${tm_file} elfos.h netbsd.h netbsd-elf.h vax/elf.h vax/netbsd-elf.h"
++ ;;
++vax-*-netbsd*)
++ tm_file="${tm_file} netbsd.h netbsd-aout.h vax/netbsd.h"
++ tmake_file=t-netbsd
++ extra_parts=""
++ use_collect2=yes
++ ;;
++vax-*-openbsd*)
++ tm_file="vax/vax.h vax/openbsd1.h openbsd.h vax/openbsd.h"
++ use_collect2=yes
++ ;;
++xstormy16-*-elf)
++ # For historical reasons, the target files omit the 'x'.
++ tm_file="dbxelf.h elfos.h svr4.h stormy16/stormy16.h"
++ tm_p_file=stormy16/stormy16-protos.h
++ md_file=stormy16/stormy16.md
++ out_file=stormy16/stormy16.c
++ extra_options=stormy16/stormy16.opt
++ tmake_file="stormy16/t-stormy16"
++ extra_parts="crtbegin.o crtend.o"
++ ;;
++xtensa*-*-elf*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h xtensa/elf.h"
++ tmake_file="xtensa/t-xtensa xtensa/t-elf"
++ ;;
++xtensa*-*-linux*)
++ tm_file="${tm_file} dbxelf.h elfos.h svr4.h linux.h xtensa/linux.h"
++ tmake_file="${tmake_file} xtensa/t-xtensa xtensa/t-linux"
++ ;;
++am33_2.0-*-linux*)
++ tm_file="mn10300/mn10300.h dbxelf.h elfos.h linux.h mn10300/linux.h"
++ tmake_file="${tmake_file} mn10300/t-linux"
++ gas=yes gnu_ld=yes
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o"
++ use_collect2=no
++ ;;
++m32c-*-rtems*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file} m32c/rtems.h rtems.h"
++ tmake_file="${tmake_file} t-rtems"
++ c_target_objs="m32c-pragma.o"
++ cxx_target_objs="m32c-pragma.o"
++ ;;
++m32c-*-elf*)
++ tm_file="dbxelf.h elfos.h svr4.h ${tm_file}"
++ c_target_objs="m32c-pragma.o"
++ cxx_target_objs="m32c-pragma.o"
++ ;;
++*)
++ echo "*** Configuration ${target} not supported" 1>&2
++ exit 1
++ ;;
++esac
++
++case ${target} in
++i[34567]86-*-linux* | x86_64-*-linux*)
++ tmake_file="${tmake_file} i386/t-pmm_malloc i386/t-i386"
++ ;;
++i[34567]86-*-* | x86_64-*-*)
++ tmake_file="${tmake_file} i386/t-gmm_malloc i386/t-i386"
++ ;;
++esac
++
++# Support for --with-cpu and related options (and a few unrelated options,
++# too).
++case ${with_cpu} in
++ yes | no)
++ echo "--with-cpu must be passed a value" 1>&2
++ exit 1
++ ;;
++esac
++
++# If there is no $with_cpu option, try to infer one from ${target}.
++# This block sets nothing except for with_cpu.
++if test x$with_cpu = x ; then
++ case ${target} in
++ i386-*-*)
++ with_cpu=i386
++ ;;
++ i486-*-*)
++ with_cpu=i486
++ ;;
++ i586-*-*)
++ case ${target_noncanonical} in
++ k6_2-*)
++ with_cpu=k6-2
++ ;;
++ k6_3-*)
++ with_cpu=k6-3
++ ;;
++ k6-*)
++ with_cpu=k6
++ ;;
++ pentium_mmx-*|winchip_c6-*|winchip2-*|c3-*)
++ with_cpu=pentium-mmx
++ ;;
++ *)
++ with_cpu=pentium
++ ;;
++ esac
++ ;;
++ i686-*-* | i786-*-*)
++ case ${target_noncanonical} in
++ amdfam10-*|barcelona-*)
++ with_cpu=amdfam10
++ ;;
++ k8-*|opteron-*|athlon_64-*)
++ with_cpu=k8
++ ;;
++ athlon_xp-*|athlon_mp-*|athlon_4-*)
++ with_cpu=athlon-4
++ ;;
++ athlon_tbird-*|athlon-*)
++ with_cpu=athlon
++ ;;
++ geode-*)
++ with_cpu=geode
++ ;;
++ pentium2-*)
++ with_cpu=pentium2
++ ;;
++ pentium3-*|pentium3m-*)
++ with_cpu=pentium3
++ ;;
++ pentium4-*|pentium4m-*)
++ with_cpu=pentium4
++ ;;
++ prescott-*)
++ with_cpu=prescott
++ ;;
++ nocona-*)
++ with_cpu=nocona
++ ;;
++ core2-*)
++ with_cpu=core2
++ ;;
++ pentium_m-*)
++ with_cpu=pentium-m
++ ;;
++ pentiumpro-*)
++ with_cpu=pentiumpro
++ ;;
++ *)
++ with_cpu=generic
++ ;;
++ esac
++ ;;
++ x86_64-*-*)
++ case ${target_noncanonical} in
++ amdfam10-*|barcelona-*)
++ with_cpu=amdfam10
++ ;;
++ k8-*|opteron-*|athlon_64-*)
++ with_cpu=k8
++ ;;
++ nocona-*)
++ with_cpu=nocona
++ ;;
++ core2-*)
++ with_cpu=core2
++ ;;
++ *)
++ with_cpu=generic
++ ;;
++ esac
++ ;;
++ alphaev6[78]*-*-*)
++ with_cpu=ev67
++ ;;
++ alphaev6*-*-*)
++ with_cpu=ev6
++ ;;
++ alphapca56*-*-*)
++ with_cpu=pca56
++ ;;
++ alphaev56*-*-*)
++ with_cpu=ev56
++ ;;
++ alphaev5*-*-*)
++ with_cpu=ev5
++ ;;
++ frv-*-*linux* | frv400-*-*linux*)
++ with_cpu=fr400
++ ;;
++ frv550-*-*linux*)
++ with_cpu=fr550
++ ;;
++ m68k*-*-*)
++ case "$with_arch" in
++ "cf")
++ with_cpu=${default_cf_cpu}
++ ;;
++ "" | "m68k")
++ with_cpu=m${default_m68k_cpu}
++ ;;
++ esac
++ ;;
++ mips*-*-vxworks)
++ with_arch=mips2
++ ;;
++ sparc*-*-*)
++ with_cpu="`echo ${target} | sed 's/-.*$//'`"
++ ;;
++ esac
++
++ # Avoid overriding --with-cpu-32 and --with-cpu-64 values.
++ case ${target} in
++ i[34567]86-*-*|x86_64-*-*)
++ if test x$with_cpu != x; then
++ if test x$with_cpu_32 != x || test x$with_cpu_64 != x; then
++ if test x$with_cpu_32 = x; then
++ with_cpu_32=$with_cpu
++ fi
++ if test x$with_cpu_64 = x; then
++ with_cpu_64=$with_cpu
++ fi
++ with_cpu=
++ fi
++ fi
++ ;;
++ esac
++fi
++
++# Similarly for --with-schedule.
++if test x$with_schedule = x; then
++ case ${target} in
++ hppa1*)
++ # Override default PA8000 scheduling model.
++ with_schedule=7100LC
++ ;;
++ esac
++fi
++
++# Validate and mark as valid any --with options supported
++# by this target. In order to use a particular --with option
++# you must list it in supported_defaults; validating the value
++# is optional. This case statement should set nothing besides
++# supported_defaults.
++
++supported_defaults=
++case "${target}" in
++ alpha*-*-*)
++ supported_defaults="cpu tune"
++ for which in cpu tune; do
++ eval "val=\$with_$which"
++ case "$val" in
++ "" \
++ | ev4 | ev45 | 21064 | ev5 | 21164 | ev56 | 21164a \
++ | pca56 | 21164PC | 21164pc | ev6 | 21264 | ev67 \
++ | 21264a)
++ ;;
++ *)
++ echo "Unknown CPU used in --with-$which=$val" 1>&2
++ exit 1
++ ;;
++ esac
++ done
++ ;;
++
++ arm*-*-*)
++ supported_defaults="arch cpu float tune fpu abi mode"
++ for which in cpu tune; do
++ # See if it matches any of the entries in arm-cores.def
++ eval "val=\$with_$which"
++ if [ x"$val" = x ] \
++ || grep "^ARM_CORE(\"$val\"," \
++ ${srcdir}/config/arm/arm-cores.def \
++ > /dev/null; then
++ # Ok
++ new_val=`grep "^ARM_CORE(\"$val\"," \
++ ${srcdir}/config/arm/arm-cores.def | \
++ sed -e 's/^[^,]*,[ ]*//' | \
++ sed -e 's/,.*$//'`
++ eval "target_${which}_cname=$new_val"
++ echo "For $val real value is $new_val"
++ true
++ else
++ echo "Unknown CPU used in --with-$which=$val" 1>&2
++ exit 1
++ fi
++ done
++
++ case "$with_arch" in
++ "" \
++ | armv[23456] | armv2a | armv3m | armv4t | armv5t \
++ | armv5te | armv6j |armv6k | armv6z | armv6zk | armv6-m \
++ | armv7 | armv7-a | armv7-r | armv7-m \
++ | iwmmxt | ep9312)
++ # OK
++ ;;
++ *)
++ echo "Unknown arch used in --with-arch=$with_arch" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case "$with_float" in
++ "" \
++ | soft | hard | softfp)
++ # OK
++ ;;
++ *)
++ echo "Unknown floating point type used in --with-float=$with_float" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case "$with_fpu" in
++ "" \
++ | fpa | fpe2 | fpe3 | maverick | vfp | vfp3 | neon )
++ # OK
++ ;;
++ *)
++ echo "Unknown fpu used in --with-fpu=$with_fpu" 2>&1
++ exit 1
++ ;;
++ esac
++
++ case "$with_abi" in
++ "" \
++ | apcs-gnu | atpcs | aapcs | iwmmxt | aapcs-linux )
++ #OK
++ ;;
++ *)
++ echo "Unknown ABI used in --with-abi=$with_abi"
++ exit 1
++ ;;
++ esac
++
++ case "$with_mode" in
++ "" \
++ | arm | thumb )
++ #OK
++ ;;
++ *)
++ echo "Unknown mode used in --with-mode=$with_mode"
++ exit 1
++ ;;
++ esac
++
++ if test "x$with_arch" != x && test "x$with_cpu" != x; then
++ echo "Warning: --with-arch overrides --with-cpu=$with_cpu" 1>&2
++ fi
++ ;;
++
++ fr*-*-*linux*)
++ supported_defaults=cpu
++ case "$with_cpu" in
++ fr400) ;;
++ fr550) ;;
++ *)
++ echo "Unknown cpu used in --with-cpu=$with_cpu" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++
++ fido-*-* | m68k*-*-*)
++ supported_defaults="arch cpu"
++ case "$with_arch" in
++ "" | "m68k"| "cf")
++ m68k_arch_family="$with_arch"
++ ;;
++ *)
++ echo "Invalid --with-arch=$with_arch" 1>&2
++ exit 1
++ ;;
++ esac
++
++ # We always have a $with_cpu setting here.
++ case "$with_cpu" in
++ "m68000" | "m68010" | "m68020" | "m68030" | "m68040" | "m68060")
++ m68k_cpu_ident=$with_cpu
++ ;;
++ "m68020-40")
++ m68k_cpu_ident=m68020
++ tm_defines="$tm_defines M68K_DEFAULT_TUNE=u68020_40"
++ ;;
++ "m68020-60")
++ m68k_cpu_ident=m68020
++ tm_defines="$tm_defines M68K_DEFAULT_TUNE=u68020_60"
++ ;;
++ *)
++ # We need the C identifier rather than the string.
++ m68k_cpu_ident=`awk -v arg="\"$with_cpu\"" \
++ 'BEGIN { FS="[ \t]*[,()][ \t]*" }; \
++ $1 == "M68K_DEVICE" && $2 == arg { print $3 }' \
++ ${srcdir}/config/m68k/m68k-devices.def`
++ if [ x"$m68k_cpu_ident" = x ] ; then
++ echo "Unknown CPU used in --with-cpu=$with_cpu" 1>&2
++ exit 1
++ fi
++ with_cpu="mcpu=$with_cpu"
++ ;;
++ esac
++ ;;
++
++ hppa*-*-*)
++ supported_defaults="arch schedule"
++
++ case "$with_arch" in
++ "" | 1.0 | 1.1 | 2.0)
++ # OK
++ ;;
++ *)
++ echo "Unknown architecture used in --with-arch=$with_arch" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case "$with_schedule" in
++ "" | 700 | 7100 | 7100LC | 7200 | 7300 | 8000)
++ # OK
++ ;;
++ *)
++ echo "Unknown processor used in --with-schedule=$with_schedule." 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++
++ i[34567]86-*-* | x86_64-*-*)
++ supported_defaults="arch arch_32 arch_64 cpu cpu_32 cpu_64 tune tune_32 tune_64"
++ for which in arch arch_32 arch_64 cpu cpu_32 cpu_64 tune tune_32 tune_64; do
++ eval "val=\$with_$which"
++ case ${val} in
++ i386 | i486 \
++ | i586 | pentium | pentium-mmx | winchip-c6 | winchip2 \
++ | c3 | c3-2 | i686 | pentiumpro | pentium2 | pentium3 \
++ | pentium4 | k6 | k6-2 | k6-3 | athlon | athlon-tbird \
++ | athlon-4 | athlon-xp | athlon-mp | geode \
++ | prescott | pentium-m | pentium4m | pentium3m)
++ case "${target}" in
++ x86_64-*-*)
++ case "x$which" in
++ *_32)
++ ;;
++ *)
++ echo "CPU given in --with-$which=$val doesn't support 64bit mode." 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++ esac
++ # OK
++ ;;
++ "" | amdfam10 | barcelona | k8 | opteron | athlon64 | athlon-fx | nocona | core2 | generic)
++ # OK
++ ;;
++ *)
++ echo "Unknown CPU given in --with-$which=$val." 1>&2
++ exit 1
++ ;;
++ esac
++ done
++ ;;
++
++ mips*-*-*)
++ supported_defaults="abi arch float tune divide llsc mips-plt"
++
++ case ${with_float} in
++ "" | soft | hard)
++ # OK
++ ;;
++ *)
++ echo "Unknown floating point type used in --with-float=$with_float" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case ${with_abi} in
++ "" | 32 | o64 | n32 | 64 | eabi)
++ # OK
++ ;;
++ *)
++ echo "Unknown ABI used in --with-abi=$with_abi" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case ${with_divide} in
++ "" | breaks | traps)
++ # OK
++ ;;
++ *)
++ echo "Unknown division check type use in --with-divide=$with_divide" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case ${with_llsc} in
++ yes)
++ with_llsc=llsc
++ ;;
++ no)
++ with_llsc="no-llsc"
++ ;;
++ "")
++ # OK
++ ;;
++ *)
++ echo "Unknown llsc type used in --with-llsc" 1>&2
++ exit 1
++ ;;
++ esac
++
++ case ${with_mips_plt} in
++ yes)
++ with_mips_plt=plt
++ ;;
++ no)
++ with_mips_plt=no-plt
++ ;;
++ "")
++ ;;
++ *)
++ echo "Unknown --with-mips-plt argument: $with_mips_plt" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++
++ powerpc*-*-* | rs6000-*-*)
++ supported_defaults="cpu float tune"
++
++ for which in cpu tune; do
++ eval "val=\$with_$which"
++ case ${val} in
++ default32 | default64)
++ with_which="with_$which"
++ eval $with_which=
++ ;;
++ 405cr)
++ tm_defines="${tm_defines} CONFIG_PPC405CR"
++ eval "with_$which=405"
++ ;;
++ "" | common \
++ | power | power[234567] | power6x | powerpc | powerpc64 \
++ | rios | rios1 | rios2 | rsc | rsc1 | rs64a \
++ | 401 | 403 | 405 | 405fp | 440 | 440fp | 464 | 464fp \
++ | 505 | 601 | 602 | 603 | 603e | ec603e | 604 \
++ | 604e | 620 | 630 | 740 | 750 | 7400 | 7450 \
++ | e300c[23] | 854[08] | e500mc \
++ | 801 | 821 | 823 | 860 | 970 | G3 | G4 | G5 | cell)
++ # OK
++ ;;
++ *)
++ echo "Unknown cpu used in --with-$which=$val." 1>&2
++ exit 1
++ ;;
++ esac
++ done
++ ;;
++
++ s390*-*-*)
++ supported_defaults="arch mode tune"
++
++ for which in arch tune; do
++ eval "val=\$with_$which"
++ case ${val} in
++ "" | g5 | g6 | z900 | z990 | z9-109 | z9-ec | z10)
++ # OK
++ ;;
++ *)
++ echo "Unknown cpu used in --with-$which=$val." 1>&2
++ exit 1
++ ;;
++ esac
++ done
++
++ case ${with_mode} in
++ "" | esa | zarch)
++ # OK
++ ;;
++ *)
++ echo "Unknown architecture mode used in --with-mode=$with_mode." 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++
++ sh[123456ble]-*-* | sh-*-*)
++ supported_defaults="cpu"
++ case "`echo $with_cpu | tr ABCDEFGHIJKLMNOPQRSTUVWXYZ_ abcdefghijklmnopqrstuvwxyz- | sed s/sh/m/`" in
++ "" | m1 | m2 | m2e | m3 | m3e | m4 | m4-single | m4-single-only | m4-nofpu )
++ # OK
++ ;;
++ m2a | m2a-single | m2a-single-only | m2a-nofpu)
++ ;;
++ m4a | m4a-single | m4a-single-only | m4a-nofpu | m4al)
++ ;;
++ *)
++ echo "Unknown CPU used in --with-cpu=$with_cpu, known values:" 1>&2
++ echo "m1 m2 m2e m3 m3e m4 m4-single m4-single-only m4-nofpu" 1>&2
++ echo "m4a m4a-single m4a-single-only m4a-nofpu m4al" 1>&2
++ echo "m2a m2a-single m2a-single-only m2a-nofpu" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++ sparc*-*-*)
++ supported_defaults="cpu float tune"
++
++ for which in cpu tune; do
++ eval "val=\$with_$which"
++ case ${val} in
++ "" | sparc | sparcv9 | sparc64 | sparc86x \
++ | v7 | cypress | v8 | supersparc | sparclite | f930 \
++ | f934 | hypersparc | sparclite86x | sparclet | tsc701 \
++ | v9 | ultrasparc | ultrasparc3 | niagara | niagara2)
++ # OK
++ ;;
++ *)
++ echo "Unknown cpu used in --with-$which=$val" 1>&2
++ exit 1
++ ;;
++ esac
++ done
++
++ case ${with_float} in
++ "" | soft | hard)
++ # OK
++ ;;
++ *)
++ echo "Unknown floating point type used in --with-float=$with_float" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++
++ spu-*-*)
++ supported_defaults="arch tune"
++
++ for which in arch tune; do
++ eval "val=\$with_$which"
++ case ${val} in
++ "" | cell | celledp)
++ # OK
++ ;;
++ *)
++ echo "Unknown cpu used in --with-$which=$val." 1>&2
++ exit 1
++ ;;
++ esac
++ done
++ ;;
++
++ v850*-*-*)
++ supported_defaults=cpu
++ case ${with_cpu} in
++ "" | v850e | v850e1)
++ # OK
++ ;;
++ *)
++ echo "Unknown cpu used in --with-cpu=$with_cpu" 1>&2
++ exit 1
++ ;;
++ esac
++ ;;
++esac
++
++# Set some miscellaneous flags for particular targets.
++target_cpu_default2=
++case ${target} in
++ alpha*-*-*)
++ if test x$gas = xyes
++ then
++ target_cpu_default2="MASK_GAS"
++ fi
++ ;;
++
++ arm*-*-*)
++ if test x$target_cpu_cname = x
++ then
++ target_cpu_default2=TARGET_CPU_generic
++ else
++ target_cpu_default2=TARGET_CPU_$target_cpu_cname
++ fi
++ ;;
++
++ hppa*-*-*)
++ target_cpu_default2="MASK_BIG_SWITCH"
++ if test x$gas = xyes
++ then
++ target_cpu_default2="${target_cpu_default2}|MASK_GAS|MASK_JUMP_IN_DELAY"
++ fi
++ ;;
++
++ fido*-*-* | m68k*-*-*)
++ target_cpu_default2=$m68k_cpu_ident
++ if [ x"$m68k_arch_family" != x ]; then
++ tmake_file="m68k/t-$m68k_arch_family $tmake_file"
++ fi
++ ;;
++
++ i[34567]86-*-darwin* | x86_64-*-darwin*)
++ tmake_file="${tmake_file} i386/t-fprules-softfp soft-fp/t-softfp"
++ ;;
++ i[34567]86-*-linux* | x86_64-*-linux* | i[34567]86-*-kfreebsd*-gnu | x86_64-*-kfreebsd*-gnu)
++ tmake_file="${tmake_file} i386/t-fprules-softfp soft-fp/t-softfp i386/t-linux"
++ ;;
++ ia64*-*-linux*)
++ tmake_file="${tmake_file} ia64/t-fprules-softfp soft-fp/t-softfp"
++ ;;
++
++ mips*-*-*)
++ if test x$gnu_ld = xyes
++ then
++ target_cpu_default2="MASK_SPLIT_ADDRESSES"
++ fi
++ case ${target} in
++ mips*el-*-*)
++ tm_defines="TARGET_ENDIAN_DEFAULT=0 $tm_defines"
++ ;;
++ esac
++ if test "x$enable_gofast" = xyes
++ then
++ tm_defines="US_SOFTWARE_GOFAST $tm_defines"
++ tmake_file="mips/t-gofast $tmake_file"
++ else
++ tmake_file="mips/t-mips $tmake_file"
++ fi
++ ;;
++
++ powerpc*-*-* | rs6000-*-*)
++ # FIXME: The PowerPC port uses the value set at compile time,
++ # although it's only cosmetic.
++ if test "x$with_cpu" != x
++ then
++ target_cpu_default2="\\\"$with_cpu\\\""
++ fi
++ out_file=rs6000/rs6000.c
++ c_target_objs="${c_target_objs} rs6000-c.o"
++ cxx_target_objs="${cxx_target_objs} rs6000-c.o"
++ tmake_file="rs6000/t-rs6000 ${tmake_file}"
++
++ if test x$enable_e500_double = xyes
++ then
++ tm_file="$tm_file rs6000/e500-double.h"
++ fi
++ ;;
++
++ sh[123456ble]*-*-* | sh-*-*)
++ c_target_objs="${c_target_objs} sh-c.o"
++ cxx_target_objs="${cxx_target_objs} sh-c.o"
++ ;;
++
++ sparc*-*-*)
++ # Some standard aliases.
++ case x$with_cpu in
++ xsparc)
++ with_cpu=v7
++ ;;
++ xsparcv9 | xsparc64)
++ with_cpu=v9
++ ;;
++ esac
++
++ # The SPARC port checks this value at compile-time.
++ target_cpu_default2="TARGET_CPU_$with_cpu"
++ ;;
++ v850*-*-*)
++ # FIXME: The v850 is "special" in that it does not support
++ # runtime CPU selection, only --with-cpu.
++ case "x$with_cpu" in
++ x)
++ ;;
++ xv850e)
++ target_cpu_default2="TARGET_CPU_$with_cpu"
++ ;;
++ esac
++ ;;
++esac
++
++t=
++all_defaults="abi cpu cpu_32 cpu_64 arch arch_32 arch_64 tune tune_32 tune_64 schedule float mode fpu divide llsc mips-plt"
++for option in $all_defaults
++do
++ eval "val=\$with_"`echo $option | sed s/-/_/g`
++ if test -n "$val"; then
++ case " $supported_defaults " in
++ *" $option "*)
++ ;;
++ *)
++ echo "This target does not support --with-$option." 2>&1
++ echo "Valid --with options are: $supported_defaults" 2>&1
++ exit 1
++ ;;
++ esac
++
++ if test "x$t" = x
++ then
++ t="{ \"$option\", \"$val\" }"
++ else
++ t="${t}, { \"$option\", \"$val\" }"
++ fi
++ fi
++done
++
++if test "x$t" = x
++then
++ configure_default_options="{ { NULL, NULL} }"
++else
++ configure_default_options="{ ${t} }"
++fi
++
++if test "$target_cpu_default2" != ""
++then
++ if test "$target_cpu_default" != ""
++ then
++ target_cpu_default="(${target_cpu_default}|${target_cpu_default2})"
++ else
++ target_cpu_default=$target_cpu_default2
++ fi
++fi
+diff -Naur gcc-4.4.2.orig/gcc/doc/contrib.texi gcc-4.4.2-rtems4.10-20091015/gcc/doc/contrib.texi
+--- gcc-4.4.2.orig/gcc/doc/contrib.texi 2009-02-20 16:20:38.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/doc/contrib.texi 2009-10-15 18:36:00.000000000 +0200
+@@ -55,7 +55,7 @@
+ Wolfgang Bangerth for processing tons of bug reports.
+
+ @item
+-Jon Beniston for his Microsoft Windows port of Java.
++Jon Beniston for his Microsoft Windows port of Java and port to Lattice Mico32.
+
+ @item
+ Daniel Berlin for better DWARF2 support, faster/better optimizations,
+diff -Naur gcc-4.4.2.orig/gcc/doc/install.texi gcc-4.4.2-rtems4.10-20091015/gcc/doc/install.texi
+--- gcc-4.4.2.orig/gcc/doc/install.texi 2009-09-12 20:57:06.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/gcc/doc/install.texi 2009-10-15 18:36:00.000000000 +0200
+@@ -2658,6 +2658,10 @@
+ @item
+ @uref{#iq2000-x-elf,,iq2000-*-elf}
+ @item
++@uref{#lm32-x-elf,,lm32-*-elf}
++@item
++@uref{#lm32-x-uclinux,,lm32-*-uclinux}
++@item
+ @uref{#m32c-x-elf,,m32c-*-elf}
+ @item
+ @uref{#m32r-x-elf,,m32r-*-elf}
+@@ -3450,6 +3454,20 @@
+ @html
+ <hr />
+ @end html
++@heading @anchor{lm32-x-elf}lm32-*-elf
++Lattice Mico32 processor.
++This configuration is intended for embedded systems.
++
++@html
++<hr />
++@end html
++@heading @anchor{lm32-x-uclinux}lm32-*-uclinux
++Lattice Mico32 processor.
++This configuration is intended for embedded systems running uClinux.
++
++@html
++<hr />
++@end html
+ @heading @anchor{m32c-x-elf}m32c-*-elf
+ Renesas M32C processor.
+ This configuration is intended for embedded systems.
+diff -Naur gcc-4.4.2.orig/gcc/doc/install.texi.orig gcc-4.4.2-rtems4.10-20091015/gcc/doc/install.texi.orig
+--- gcc-4.4.2.orig/gcc/doc/install.texi.orig 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/doc/install.texi.orig 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,4324 @@
++\input texinfo.tex @c -*-texinfo-*-
++@c @ifnothtml
++@c %**start of header
++@setfilename gccinstall.info
++@settitle Installing GCC
++@setchapternewpage odd
++@c %**end of header
++@c @end ifnothtml
++
++@include gcc-common.texi
++
++@c Specify title for specific html page
++@ifset indexhtml
++@settitle Installing GCC
++@end ifset
++@ifset specifichtml
++@settitle Host/Target specific installation notes for GCC
++@end ifset
++@ifset prerequisiteshtml
++@settitle Prerequisites for GCC
++@end ifset
++@ifset downloadhtml
++@settitle Downloading GCC
++@end ifset
++@ifset configurehtml
++@settitle Installing GCC: Configuration
++@end ifset
++@ifset buildhtml
++@settitle Installing GCC: Building
++@end ifset
++@ifset testhtml
++@settitle Installing GCC: Testing
++@end ifset
++@ifset finalinstallhtml
++@settitle Installing GCC: Final installation
++@end ifset
++@ifset binarieshtml
++@settitle Installing GCC: Binaries
++@end ifset
++@ifset oldhtml
++@settitle Installing GCC: Old documentation
++@end ifset
++@ifset gfdlhtml
++@settitle Installing GCC: GNU Free Documentation License
++@end ifset
++
++@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
++@c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
++@c *** Converted to texinfo by Dean Wakerley, dean@wakerley.com
++
++@c IMPORTANT: whenever you modify this file, run `install.texi2html' to
++@c test the generation of HTML documents for the gcc.gnu.org web pages.
++@c
++@c Do not use @footnote{} in this file as it breaks install.texi2html!
++
++@c Include everything if we're not making html
++@ifnothtml
++@set indexhtml
++@set specifichtml
++@set prerequisiteshtml
++@set downloadhtml
++@set configurehtml
++@set buildhtml
++@set testhtml
++@set finalinstallhtml
++@set binarieshtml
++@set oldhtml
++@set gfdlhtml
++@end ifnothtml
++
++@c Part 2 Summary Description and Copyright
++@copying
++Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997,
++1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007,
++2008 Free Software Foundation, Inc.
++@sp 1
++Permission is granted to copy, distribute and/or modify this document
++under the terms of the GNU Free Documentation License, Version 1.2 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 ``@uref{./gfdl.html,,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.
++@end copying
++@ifinfo
++@insertcopying
++@end ifinfo
++@dircategory Software development
++@direntry
++* gccinstall: (gccinstall). Installing the GNU Compiler Collection.
++@end direntry
++
++@c Part 3 Titlepage and Copyright
++@titlepage
++@title Installing GCC
++@versionsubtitle
++
++@c The following two commands start the copyright page.
++@page
++@vskip 0pt plus 1filll
++@insertcopying
++@end titlepage
++
++@c Part 4 Top node, Master Menu, and/or Table of Contents
++@ifinfo
++@node Top, , , (dir)
++@comment node-name, next, Previous, up
++
++@menu
++* Installing GCC:: This document describes the generic installation
++ procedure for GCC as well as detailing some target
++ specific installation instructions.
++
++* Specific:: Host/target specific installation notes for GCC.
++* Binaries:: Where to get pre-compiled binaries.
++
++* Old:: Old installation documentation.
++
++* GNU Free Documentation License:: How you can copy and share this manual.
++* Concept Index:: This index has two entries.
++@end menu
++@end ifinfo
++
++@iftex
++@contents
++@end iftex
++
++@c Part 5 The Body of the Document
++@c ***Installing GCC**********************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Installing GCC, Binaries, , Top
++@end ifnothtml
++@ifset indexhtml
++@ifnothtml
++@chapter Installing GCC
++@end ifnothtml
++
++The latest version of this document is always available at
++@uref{http://gcc.gnu.org/install/,,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.
++
++@emph{Before} starting the build/install procedure please check the
++@ifnothtml
++@ref{Specific, host/target specific installation notes}.
++@end ifnothtml
++@ifhtml
++@uref{specific.html,,host/target specific installation notes}.
++@end ifhtml
++We recommend you browse the entire generic installation instructions before
++you proceed.
++
++Lists of successful builds for released versions of GCC are
++available at @uref{http://gcc.gnu.org/buildstat.html}.
++These lists are updated as new information becomes available.
++
++The installation procedure itself is broken into five steps.
++
++@ifinfo
++@menu
++* Prerequisites::
++* Downloading the source::
++* Configuration::
++* Building::
++* Testing:: (optional)
++* Final install::
++@end menu
++@end ifinfo
++@ifhtml
++@enumerate
++@item
++@uref{prerequisites.html,,Prerequisites}
++@item
++@uref{download.html,,Downloading the source}
++@item
++@uref{configure.html,,Configuration}
++@item
++@uref{build.html,,Building}
++@item
++@uref{test.html,,Testing} (optional)
++@item
++@uref{finalinstall.html,,Final install}
++@end enumerate
++@end ifhtml
++
++Please note that GCC does not support @samp{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.
++
++@ifhtml
++There are also some @uref{old.html,,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.
++@end ifhtml
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++
++@insertcopying
++@end ifhtml
++@end ifset
++
++@c ***Prerequisites**************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Prerequisites, Downloading the source, , Installing GCC
++@end ifnothtml
++@ifset prerequisiteshtml
++@ifnothtml
++@chapter Prerequisites
++@end ifnothtml
++@cindex Prerequisites
++
++GCC requires that various tools and packages be available for use in the
++build procedure. Modifying GCC sources requires additional tools
++described below.
++
++@heading Tools/packages necessary for building GCC
++@table @asis
++@item ISO C90 compiler
++Necessary to bootstrap GCC, although versions of GCC prior
++to 3.4 also allow bootstrapping with a traditional (K&R) C compiler.
++
++To build all languages in a cross-compiler or other configuration where
++3-stage bootstrap is not performed, you need to start with an existing
++GCC binary (version 2.95 or later) because source code for language
++frontends other than C might use GCC extensions.
++
++@item GNAT
++
++In order to build the Ada compiler (GNAT) you must already have GNAT
++installed because portions of the Ada frontend are written in Ada (with
++GNAT extensions.) Refer to the Ada installation instructions for more
++specific information.
++
++@item A ``working'' POSIX compatible shell, or GNU bash
++
++Necessary when running @command{configure} because some
++@command{/bin/sh} shells have bugs and may crash when configuring the
++target libraries. In other cases, @command{/bin/sh} or @command{ksh}
++have disastrous corner-case performance problems. This
++can cause target @command{configure} runs to literally take days to
++complete in some cases.
++
++So on some platforms @command{/bin/ksh} is sufficient, on others it
++isn't. See the host/target specific instructions for your platform, or
++use @command{bash} to be sure. Then set @env{CONFIG_SHELL} in your
++environment to your ``good'' shell prior to running
++@command{configure}/@command{make}.
++
++@command{zsh} is not a fully compliant POSIX shell and will not
++work when configuring GCC@.
++
++@item A POSIX or SVR4 awk
++
++Necessary for creating some of the generated source files for GCC@.
++If in doubt, use a recent GNU awk version, as some of the older ones
++are broken. GNU awk version 3.1.5 is known to work.
++
++@item GNU binutils
++
++Necessary in some circumstances, optional in others. See the
++host/target specific instructions for your platform for the exact
++requirements.
++
++@item gzip version 1.2.4 (or later) or
++@itemx bzip2 version 1.0.2 (or later)
++
++Necessary to uncompress GCC @command{tar} files when source code is
++obtained via FTP mirror sites.
++
++@item GNU make version 3.80 (or later)
++
++You must have GNU make installed to build GCC@.
++
++@item GNU tar version 1.14 (or later)
++
++Necessary (only on some platforms) to untar the source code. Many
++systems' @command{tar} programs will also work, only try GNU
++@command{tar} if you have problems.
++
++@item GNU Multiple Precision Library (GMP) version 4.1 (or later)
++
++Necessary to build GCC@. If you do not have it installed in your
++library search path, you will have to configure with the
++@option{--with-gmp} configure option. See also @option{--with-gmp-lib}
++and @option{--with-gmp-include}. Alternatively, if a GMP source
++distribution is found in a subdirectory of your GCC sources named
++@file{gmp}, it will be built together with GCC@.
++
++@item MPFR Library version 2.3.2 (or later)
++
++Necessary to build GCC@. It can be downloaded from
++@uref{http://www.mpfr.org/}. The version of MPFR that is bundled with
++GMP 4.1.x contains numerous bugs. Although GCC may appear to function
++with the buggy versions of MPFR, there are a few bugs that will not be
++fixed when using this version. It is strongly recommended to upgrade
++to the recommended version of MPFR.
++
++The @option{--with-mpfr} configure option should be used if your MPFR
++Library is not installed in your default library search path. See also
++@option{--with-mpfr-lib} and @option{--with-mpfr-include}.
++Alternatively, if a MPFR source distribution is found in a subdirectory
++of your GCC sources named @file{mpfr}, it will be built together with
++GCC@.
++
++@item Parma Polyhedra Library (PPL) version 0.10
++
++Necessary to build GCC with the Graphite loop optimizations.
++It can be downloaded from @uref{http://www.cs.unipr.it/ppl/Download/}.
++
++The @option{--with-ppl} configure option should be used if PPL is not
++installed in your default library search path.
++
++@item CLooG-PPL version 0.15
++
++Necessary to build GCC with the Graphite loop optimizations. It can
++be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}.
++The code in @file{cloog-ppl-0.15.tar.gz} comes from a branch of CLooG
++available from @uref{http://repo.or.cz/w/cloog-ppl.git}. CLooG-PPL
++should be configured with @option{--with-ppl}.
++
++The @option{--with-cloog} configure option should be used if CLooG is
++not installed in your default library search path.
++
++@item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
++
++Necessary to build libgcj, the GCJ runtime.
++
++@end table
++
++
++@heading Tools/packages necessary for modifying GCC
++@table @asis
++@item autoconf version 2.59
++@itemx GNU m4 version 1.4 (or later)
++
++Necessary when modifying @file{configure.ac}, @file{aclocal.m4}, etc.@:
++to regenerate @file{configure} and @file{config.in} files.
++
++@item automake version 1.9.6
++
++Necessary when modifying a @file{Makefile.am} file to regenerate its
++associated @file{Makefile.in}.
++
++Much of GCC does not use automake, so directly edit the @file{Makefile.in}
++file. Specifically this applies to the @file{gcc}, @file{intl},
++@file{libcpp}, @file{libiberty}, @file{libobjc} directories as well
++as any of their subdirectories.
++
++For directories that use automake, GCC requires the latest release in
++the 1.9.x series, which is currently 1.9.6. When regenerating a directory
++to a newer version, please update all the directories using an older 1.9.x
++to the latest released version.
++
++@item gettext version 0.14.5 (or later)
++
++Needed to regenerate @file{gcc.pot}.
++
++@item gperf version 2.7.2 (or later)
++
++Necessary when modifying @command{gperf} input files, e.g.@:
++@file{gcc/cp/cfns.gperf} to regenerate its associated header file, e.g.@:
++@file{gcc/cp/cfns.h}.
++
++@item DejaGnu 1.4.4
++@itemx Expect
++@itemx Tcl
++
++Necessary to run the GCC testsuite; see the section on testing for details.
++
++@item autogen version 5.5.4 (or later) and
++@itemx guile version 1.4.1 (or later)
++
++Necessary to regenerate @file{fixinc/fixincl.x} from
++@file{fixinc/inclhack.def} and @file{fixinc/*.tpl}.
++
++Necessary to run @samp{make check} for @file{fixinc}.
++
++Necessary to regenerate the top level @file{Makefile.in} file from
++@file{Makefile.tpl} and @file{Makefile.def}.
++
++@item Flex version 2.5.4 (or later)
++
++Necessary when modifying @file{*.l} files.
++
++Necessary to build GCC during development because the generated output
++files are not included in the SVN repository. They are included in
++releases.
++
++@item Texinfo version 4.7 (or later)
++
++Necessary for running @command{makeinfo} when modifying @file{*.texi}
++files to test your changes.
++
++Necessary for running @command{make dvi} or @command{make pdf} to
++create printable documentation in DVI or PDF format. Texinfo version
++4.8 or later is required for @command{make pdf}.
++
++Necessary to build GCC documentation during development because the
++generated output files are not included in the SVN repository. They are
++included in releases.
++
++@item @TeX{} (any working version)
++
++Necessary for running @command{texi2dvi} and @command{texi2pdf}, which
++are used when running @command{make dvi} or @command{make pdf} to create
++DVI or PDF files, respectively.
++
++@item SVN (any version)
++@itemx SSH (any version)
++
++Necessary to access the SVN repository. Public releases and weekly
++snapshots of the development sources are also available via FTP@.
++
++@item Perl version 5.6.1 (or later)
++
++Necessary when regenerating @file{Makefile} dependencies in libiberty.
++Necessary when regenerating @file{libiberty/functions.texi}.
++Necessary when generating manpages from Texinfo manuals.
++Necessary when targetting Darwin, building libstdc++,
++and not using @option{--disable-symvers}.
++Used by various scripts to generate some files included in SVN (mainly
++Unicode-related and rarely changing) from source tables.
++
++@item GNU diffutils version 2.7 (or later)
++
++Useful when submitting patches for the GCC source code.
++
++@item patch version 2.5.4 (or later)
++
++Necessary when applying patches, created with @command{diff}, to one's
++own sources.
++
++@item ecj1
++@itemx gjavah
++
++If you wish to modify @file{.java} files in libjava, you will need to
++configure with @option{--enable-java-maintainer-mode}, and you will need
++to have executables named @command{ecj1} and @command{gjavah} in your path.
++The @command{ecj1} executable should run the Eclipse Java compiler via
++the GCC-specific entry point. You can download a suitable jar from
++@uref{ftp://sourceware.org/pub/java/}, or by running the script
++@command{contrib/download_ecj}.
++
++@item antlr.jar version 2.7.1 (or later)
++@itemx antlr binary
++
++If you wish to build the @command{gjdoc} binary in libjava, you will
++need to have a @file{antlr.jar} library available. The library is
++searched in system locations but can be configured with
++@option{--with-antlr-jar=} instead. When configuring with
++@option{--enable-java-maintainer-mode}, you will need to have one of
++the executables named @command{cantlr}, @command{runantlr} or
++@command{antlr} in your path.
++
++@end table
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Downloading the source**************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Downloading the source, Configuration, Prerequisites, Installing GCC
++@end ifnothtml
++@ifset downloadhtml
++@ifnothtml
++@chapter Downloading GCC
++@end ifnothtml
++@cindex Downloading GCC
++@cindex Downloading the Source
++
++GCC is distributed via @uref{http://gcc.gnu.org/svn.html,,SVN} and FTP
++tarballs compressed with @command{gzip} or
++@command{bzip2}. It is possible to download a full distribution or specific
++components.
++
++Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
++for information on how to obtain GCC@.
++
++The full distribution includes the C, C++, Objective-C, Fortran, Java,
++and Ada (in the 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, the 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
++(@file{bfd}, @file{binutils}, @file{gas}, @file{gprof}, @file{ld},
++@file{opcodes}, @dots{}) to the directory containing the GCC sources.
++
++Likewise, the GMP and MPFR libraries can be automatically built together
++with GCC. Unpack the GMP and/or MPFR source distributions in the
++directory containing the GCC sources and rename their directories to
++@file{gmp} and @file{mpfr}, respectively (or use symbolic links with the
++same name).
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Configuration***********************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Configuration, Building, Downloading the source, Installing GCC
++@end ifnothtml
++@ifset configurehtml
++@ifnothtml
++@chapter Installing GCC: Configuration
++@end ifnothtml
++@cindex Configuration
++@cindex 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 @var{srcdir} to refer to the toplevel source directory for
++GCC; we use @var{objdir} to refer to the toplevel build/object directory.
++
++If you obtained the sources via SVN, @var{srcdir} must refer to the top
++@file{gcc} directory, the one where the @file{MAINTAINERS} can be found,
++and not its @file{gcc} subdirectory, otherwise the build will fail.
++
++If either @var{srcdir} or @var{objdir} is located on an automounted NFS
++file system, the shell's built-in @command{pwd} command will return
++temporary pathnames. Using these can lead to various sorts of build
++problems. To avoid this issue, set the @env{PWDCMD} environment
++variable to an automounter-aware @command{pwd} command, e.g.,
++@command{pawd} or @samp{amq -w}, during the configuration and build
++phases.
++
++First, we @strong{highly} recommend that GCC be built into a
++separate directory than the sources which does @strong{not} reside
++within the source tree. This is how we generally build GCC; building
++where @var{srcdir} == @var{objdir} should still work, but doesn't
++get extensive testing; building where @var{objdir} is a subdirectory
++of @var{srcdir} is unsupported.
++
++If you have previously built GCC in the same directory for a
++different target machine, do @samp{make distclean} to delete all files
++that might be invalid. One of the files this deletes is @file{Makefile};
++if @samp{make distclean} complains that @file{Makefile} does not exist
++or issues a message like ``don't know how to make distclean'' it probably
++means that the directory is already suitably clean. However, with the
++recommended method of building in a separate @var{objdir}, you should
++simply use a different @var{objdir} for each target.
++
++Second, when configuring a native system, either @command{cc} or
++@command{gcc} must be in your path or you must set @env{CC} in
++your environment before running configure. Otherwise the configuration
++scripts may fail.
++
++@ignore
++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
++@ifnothtml
++@ref{Specific, host/target specific installation notes}.
++@end ifnothtml
++@ifhtml
++@uref{specific.html,,host/target specific installation notes}.
++@end ifhtml
++@end ignore
++
++To configure GCC:
++
++@smallexample
++ % mkdir @var{objdir}
++ % cd @var{objdir}
++ % @var{srcdir}/configure [@var{options}] [@var{target}]
++@end smallexample
++
++@heading Distributor options
++
++If you will be distributing binary versions of GCC, with modifications
++to the source code, you should use the options described in this
++section to make clear that your version contains modifications.
++
++@table @code
++@item --with-pkgversion=@var{version}
++Specify a string that identifies your package. You may wish
++to include a build number or build date. This version string will be
++included in the output of @command{gcc --version}. This suffix does
++not replace the default version string, only the @samp{GCC} part.
++
++The default value is @samp{GCC}.
++
++@item --with-bugurl=@var{url}
++Specify the URL that users should visit if they wish to report a bug.
++You are of course welcome to forward bugs reported to you to the FSF,
++if you determine that they are not bugs in your modifications.
++
++The default value refers to the FSF's GCC bug tracker.
++
++@end table
++
++@heading Target specification
++@itemize @bullet
++@item
++GCC has code to correctly determine the correct value for @var{target}
++for nearly all native systems. Therefore, we highly recommend you not
++provide a configure target when configuring a native compiler.
++
++@item
++@var{target} must be specified as @option{--target=@var{target}}
++when configuring a cross compiler; examples of valid targets would be
++m68k-coff, sh-elf, etc.
++
++@item
++Specifying just @var{target} instead of @option{--target=@var{target}}
++implies that the host defaults to @var{target}.
++@end itemize
++
++
++@heading Options specification
++
++Use @var{options} to override several configure time options for
++GCC@. A list of supported @var{options} follows; @samp{configure
++--help} may list other options, but those not listed below may not
++work and should not normally be used.
++
++Note that each @option{--enable} option has a corresponding
++@option{--disable} option and that each @option{--with} option has a
++corresponding @option{--without} option.
++
++@table @code
++@item --prefix=@var{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
++@file{/usr/local}.
++
++We @strong{highly} recommend against @var{dirname} being the same or a
++subdirectory of @var{objdir} or vice versa. If specifying a directory
++beneath a user's home directory tree, some shells will not expand
++@var{dirname} correctly if it contains the @samp{~} metacharacter; use
++@env{$HOME} instead.
++
++The following standard @command{autoconf} options are supported. Normally you
++should not need to use these options.
++@table @code
++@item --exec-prefix=@var{dirname}
++Specify the toplevel installation directory for architecture-dependent
++files. The default is @file{@var{prefix}}.
++
++@item --bindir=@var{dirname}
++Specify the installation directory for the executables called by users
++(such as @command{gcc} and @command{g++}). The default is
++@file{@var{exec-prefix}/bin}.
++
++@item --libdir=@var{dirname}
++Specify the installation directory for object code libraries and
++internal data files of GCC@. The default is @file{@var{exec-prefix}/lib}.
++
++@item --libexecdir=@var{dirname}
++Specify the installation directory for internal executables of GCC@.
++The default is @file{@var{exec-prefix}/libexec}.
++
++@item --with-slibdir=@var{dirname}
++Specify the installation directory for the shared libgcc library. The
++default is @file{@var{libdir}}.
++
++@item --infodir=@var{dirname}
++Specify the installation directory for documentation in info format.
++The default is @file{@var{prefix}/info}.
++
++@item --datadir=@var{dirname}
++Specify the installation directory for some architecture-independent
++data files referenced by GCC@. The default is @file{@var{prefix}/share}.
++
++@item --mandir=@var{dirname}
++Specify the installation directory for manual pages. The default is
++@file{@var{prefix}/man}. (Note that the manual pages are only extracts from
++the full GCC manuals, which are provided in Texinfo format. The manpages
++are derived by an automatic conversion process from parts of the full
++manual.)
++
++@item --with-gxx-include-dir=@var{dirname}
++Specify
++the installation directory for G++ header files. The default is
++@file{@var{prefix}/include/c++/@var{version}}.
++
++@end table
++
++@item --program-prefix=@var{prefix}
++GCC supports some transformations of the names of its programs when
++installing them. This option prepends @var{prefix} to the names of
++programs to install in @var{bindir} (see above). For example, specifying
++@option{--program-prefix=foo-} would result in @samp{gcc}
++being installed as @file{/usr/local/bin/foo-gcc}.
++
++@item --program-suffix=@var{suffix}
++Appends @var{suffix} to the names of programs to install in @var{bindir}
++(see above). For example, specifying @option{--program-suffix=-3.1}
++would result in @samp{gcc} being installed as
++@file{/usr/local/bin/gcc-3.1}.
++
++@item --program-transform-name=@var{pattern}
++Applies the @samp{sed} script @var{pattern} to be applied to the names
++of programs to install in @var{bindir} (see above). @var{pattern} has to
++consist of one or more basic @samp{sed} editing commands, separated by
++semicolons. For example, if you want the @samp{gcc} program name to be
++transformed to the installed program @file{/usr/local/bin/myowngcc} and
++the @samp{g++} program name to be transformed to
++@file{/usr/local/bin/gspecial++} without changing other program names,
++you could use the pattern
++@option{--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, @var{prefix} (and
++@var{suffix}) are prepended (appended) before further transformations
++can happen with a special transformation script @var{pattern}.
++
++As currently implemented, this option only takes 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
++@samp{i686-pc-linux-gnu-gcc}. All of the above transformations happen
++before the target alias is prepended to the name---so, specifying
++@option{--program-prefix=foo-} and @option{program-suffix=-3.1}, the
++resulting binary would be installed as
++@file{/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.
++
++@item --with-local-prefix=@var{dirname}
++Specify the
++installation directory for local include files. The default is
++@file{/usr/local}. Specify this option if you want the compiler to
++search directory @file{@var{dirname}/include} for locally installed
++header files @emph{instead} of @file{/usr/local/include}.
++
++You should specify @option{--with-local-prefix} @strong{only} if your
++site has a different convention (not @file{/usr/local}) for where to put
++site-specific files.
++
++The default value for @option{--with-local-prefix} is @file{/usr/local}
++regardless of the value of @option{--prefix}. Specifying
++@option{--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 @option{--prefix} is to specify where to @emph{install
++GCC}. The local header files in @file{/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 @option{--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 searched before the GCC-prefix
++include directory. Another characteristic of system include directories
++is that pedantic warnings are turned off for headers in these directories.
++
++Some autoconf macros add @option{-I @var{directory}} options to the
++compiler command line, to ensure that directories containing installed
++packages' headers are searched. When @var{directory} is one of GCC's
++system include directories, GCC will ignore the option so that system
++directories continue to be processed in the correct order. This
++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
++@env{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 @file{/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
++@option{--program-prefix}, @option{--program-suffix} and
++@option{--program-transform-name} options to install multiple versions
++into a single directory, but it may be simpler to use different prefixes
++and the @option{--with-local-prefix} option to specify the location of the
++site-specific files for each version. It will then be necessary for
++users to specify explicitly the location of local site libraries
++(e.g., with @env{LIBRARY_PATH}).
++
++The same value can be used for both @option{--with-local-prefix} and
++@option{--prefix} provided it is not @file{/usr}. This can be used
++to avoid the default search of @file{/usr/local/include}.
++
++@strong{Do not} specify @file{/usr} as the @option{--with-local-prefix}!
++The directory you use for @option{--with-local-prefix} @strong{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 @command{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.
++
++@item --enable-shared[=@var{package}[,@dots{}]]
++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.
++
++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
++@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
++@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
++@samp{ada}, @samp{libada}, @samp{libjava} and @samp{libobjc}.
++Note @samp{libiberty} does not support shared libraries at all.
++
++Use @option{--disable-shared} to build only static libraries. Note that
++@option{--disable-shared} does not accept a list of package names as
++argument, only @option{--enable-shared} does.
++
++@item @anchor{with-gnu-as}--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 the
++assembler found is not actually the GNU assembler. (Confusion may also
++result if the compiler finds the GNU assembler but has not been
++configured with @option{--with-gnu-as}.) If you have more than one
++assembler installed on your system, you may want to use this option in
++connection with @option{--with-as=@var{pathname}} or
++@option{--with-build-time-tools=@var{pathname}}.
++
++The following systems are the only ones where it makes a difference
++whether you use the GNU assembler. On any other system,
++@option{--with-gnu-as} has no effect.
++
++@itemize @bullet
++@item @samp{hppa1.0-@var{any}-@var{any}}
++@item @samp{hppa1.1-@var{any}-@var{any}}
++@item @samp{sparc-sun-solaris2.@var{any}}
++@item @samp{sparc64-@var{any}-solaris2.@var{any}}
++@end itemize
++
++@item @anchor{with-as}--with-as=@var{pathname}
++Specify that the compiler should use the assembler pointed to by
++@var{pathname}, rather than the one found by the standard rules to find
++an assembler, which are:
++@itemize @bullet
++@item
++Unless GCC is being built with a cross compiler, check the
++@file{@var{libexec}/gcc/@var{target}/@var{version}} directory.
++@var{libexec} defaults to @file{@var{exec-prefix}/libexec};
++@var{exec-prefix} defaults to @var{prefix}, which
++defaults to @file{/usr/local} unless overridden by the
++@option{--prefix=@var{pathname}} switch described above. @var{target}
++is the target system triple, such as @samp{sparc-sun-solaris2.7}, and
++@var{version} denotes the GCC version, such as 3.0.
++
++@item
++If the target system is the same that you are building on, check
++operating system specific directories (e.g.@: @file{/usr/ccs/bin} on
++Sun Solaris 2).
++
++@item
++Check in the @env{PATH} for a tool whose name is prefixed by the
++target system triple.
++
++@item
++Check in the @env{PATH} for a tool whose name is not prefixed by the
++target system triple, if the host and target system triple are
++the same (in other words, we use a host tool if it can be used for
++the target as well).
++@end itemize
++
++You may want to use @option{--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.
++
++@item @anchor{with-gnu-ld}--with-gnu-ld
++Same as @uref{#with-gnu-as,,@option{--with-gnu-as}}
++but for the linker.
++
++@item --with-ld=@var{pathname}
++Same as @uref{#with-as,,@option{--with-as}}
++but for the linker.
++
++@item --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 @option{--with-stabs} when you configure GCC@.
++
++No matter which default you choose when you configure GCC, the user
++can use the @option{-gcoff} and @option{-gstabs+} options to specify explicitly
++the debug format for a particular compilation.
++
++@option{--with-stabs} is meaningful on the ISC system on the 386, also, if
++@option{--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.
++
++@option{--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.
++
++@item --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., @option{--disable-softfloat}):
++@table @code
++@item arc-*-elf*
++biendian.
++
++@item arm-*-*
++fpu, 26bit, underscore, interwork, biendian, nofmult.
++
++@item m68*-*-*
++softfloat, m68881, m68000, m68020.
++
++@item mips*-*-*
++single-float, biendian, softfloat.
++
++@item powerpc*-*-*, rs6000*-*-*
++aix64, pthread, softfloat, powercpu, powerpccpu, powerpcos, biendian,
++sysv, aix.
++
++@end table
++
++@item --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, @option{--enable-threads} is an
++alias for @option{--enable-threads=single}.
++
++@item --disable-threads
++Specify that threading support should be disabled for the system.
++This is an alias for @option{--enable-threads=single}.
++
++@item --enable-threads=@var{lib}
++Specify that
++@var{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 @var{lib} are:
++
++@table @code
++@item aix
++AIX thread support.
++@item dce
++DCE thread support.
++@item gnat
++Ada tasking support. For non-Ada programs, this setting is equivalent
++to @samp{single}. When used in conjunction with the Ada run time, it
++causes GCC to use the same thread primitives as Ada uses. This option
++is necessary when using both Ada and the back end exception handling,
++which is the default for most Ada targets.
++@item mach
++Generic MACH thread support, known to work on NeXTSTEP@. (Please note
++that the file needed to support this configuration, @file{gthr-mach.h}, is
++missing and thus this setting will cause a known bootstrap failure.)
++@item no
++This is an alias for @samp{single}.
++@item posix
++Generic POSIX/Unix98 thread support.
++@item posix95
++Generic POSIX/Unix95 thread support.
++@item rtems
++RTEMS thread support.
++@item single
++Disable thread support, should work for all platforms.
++@item solaris
++Sun Solaris 2 thread support.
++@item vxworks
++VxWorks thread support.
++@item win32
++Microsoft Win32 API thread support.
++@item nks
++Novell Kernel Services thread support.
++@end table
++
++@item --enable-tls
++Specify that the target supports TLS (Thread Local Storage). Usually
++configure can correctly determine if TLS is supported. In cases where
++it guesses incorrectly, TLS can be explicitly enabled or disabled with
++@option{--enable-tls} or @option{--disable-tls}. This can happen if
++the assembler supports TLS but the C library does not, or if the
++assumptions made by the configure test are incorrect.
++
++@item --disable-tls
++Specify that the target does not support TLS.
++This is an alias for @option{--enable-tls=no}.
++
++@item --with-cpu=@var{cpu}
++@itemx --with-cpu-32=@var{cpu}
++@itemx --with-cpu-64=@var{cpu}
++Specify which cpu variant the compiler should generate code for by default.
++@var{cpu} will be used as the default value of the @option{-mcpu=} switch.
++This option is only supported on some targets, including ARM, i386, M68k,
++PowerPC, and SPARC@. The @option{--with-cpu-32} and
++@option{--with-cpu-64} options specify separate default CPUs for
++32-bit and 64-bit modes; these options are only supported for i386 and
++x86-64.
++
++@item --with-schedule=@var{cpu}
++@itemx --with-arch=@var{cpu}
++@itemx --with-arch-32=@var{cpu}
++@itemx --with-arch-64=@var{cpu}
++@itemx --with-tune=@var{cpu}
++@itemx --with-tune-32=@var{cpu}
++@itemx --with-tune-64=@var{cpu}
++@itemx --with-abi=@var{abi}
++@itemx --with-fpu=@var{type}
++@itemx --with-float=@var{type}
++These configure options provide default values for the @option{-mschedule=},
++@option{-march=}, @option{-mtune=}, @option{-mabi=}, and @option{-mfpu=}
++options and for @option{-mhard-float} or @option{-msoft-float}. As with
++@option{--with-cpu}, which switches will be accepted and acceptable values
++of the arguments depend on the target.
++
++@item --with-mode=@var{mode}
++Specify if the compiler should default to @option{-marm} or @option{-mthumb}.
++This option is only supported on ARM targets.
++
++@item --with-divide=@var{type}
++Specify how the compiler should generate code for checking for
++division by zero. This option is only supported on the MIPS target.
++The possibilities for @var{type} are:
++@table @code
++@item traps
++Division by zero checks use conditional traps (this is the default on
++systems that support conditional traps).
++@item breaks
++Division by zero checks use the break instruction.
++@end table
++
++@c If you make --with-llsc the default for additional targets,
++@c update the --with-llsc description in the MIPS section below.
++
++@item --with-llsc
++On MIPS targets, make @option{-mllsc} the default when no
++@option{-mno-lsc} option is passed. This is the default for
++Linux-based targets, as the kernel will emulate them if the ISA does
++not provide them.
++
++@item --without-llsc
++On MIPS targets, make @option{-mno-llsc} the default when no
++@option{-mllsc} option is passed.
++
++@item --with-mips-plt
++On MIPS targets, make use of copy relocations and PLTs.
++These features are extensions to the traditional
++SVR4-based MIPS ABIs and require support from GNU binutils
++and the runtime C library.
++
++@item --enable-__cxa_atexit
++Define if you want to use __cxa_atexit, rather than atexit, to
++register C++ destructors for local statics and global objects.
++This is essential for fully standards-compliant handling of
++destructors, but requires __cxa_atexit in libc. This option is currently
++only available on systems with GNU libc. When enabled, this will cause
++@option{-fuse-cxa-atexit} to be passed by default.
++
++@item --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.
++
++@item --disable-cpp
++Specify that a user visible @command{cpp} program should not be installed.
++
++@item --with-cpp-install-dir=@var{dirname}
++Specify that the user visible @command{cpp} program should be installed
++in @file{@var{prefix}/@var{dirname}/cpp}, in addition to @var{bindir}.
++
++@item --enable-initfini-array
++Force the use of sections @code{.init_array} and @code{.fini_array}
++(instead of @code{.init} and @code{.fini}) for constructors and
++destructors. Option @option{--disable-initfini-array} has the
++opposite effect. If neither option is specified, the configure script
++will try to guess whether the @code{.init_array} and
++@code{.fini_array} sections are supported and, if they are, use them.
++
++@item --enable-maintainer-mode
++The build rules that
++regenerate the GCC master message catalog @file{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 @option{--enable-maintainer-mode} will enable
++this. Note that you need a recent version of the @code{gettext} tools
++to do so.
++
++@item --disable-bootstrap
++For a native build, the default configuration is to perform
++a 3-stage bootstrap of the compiler when @samp{make} is invoked,
++testing that GCC can compile itself correctly. If you want to disable
++this process, you can configure with @option{--disable-bootstrap}.
++
++@item --enable-bootstrap
++In special cases, you may want to perform a 3-stage build
++even if the target and host triplets are different.
++This could happen when the host can run code compiled for
++the target (e.g.@: host is i686-linux, target is i486-linux).
++Starting from GCC 4.2, to do this you have to configure explicitly
++with @option{--enable-bootstrap}.
++
++@item --enable-generated-files-in-srcdir
++Neither the .c and .h files that are generated from Bison and flex nor the
++info manuals and man pages that are built from the .texi files are present
++in the SVN development tree. When building GCC from that development tree,
++or from one of our snapshots, those generated files are placed in your
++build directory, which allows for the source to be in a readonly
++directory.
++
++If you configure with @option{--enable-generated-files-in-srcdir} then those
++generated files will go into the source directory. This is mainly intended
++for generating release or prerelease tarballs of the GCC sources, since it
++is not a requirement that the users of source releases to have flex, Bison,
++or makeinfo.
++
++@item --enable-version-specific-runtime-libs
++Specify
++that runtime libraries should be installed in the compiler specific
++subdirectory (@file{@var{libdir}/gcc}) rather than the usual places. In
++addition, @samp{libstdc++}'s include files will be installed into
++@file{@var{libdir}} unless you overruled it by using
++@option{--with-gxx-include-dir=@var{dirname}}. Using this option is
++particularly useful if you intend to use several versions of GCC in
++parallel. This is currently supported by @samp{libgfortran},
++@samp{libjava}, @samp{libmudflap}, @samp{libstdc++}, and @samp{libobjc}.
++
++@item --enable-languages=@var{lang1},@var{lang2},@dots{}
++Specify that only a particular subset of compilers and
++their runtime libraries should be built. For a list of valid values for
++@var{langN} you can issue the following command in the
++@file{gcc} directory of your GCC source tree:@*
++@smallexample
++grep language= */config-lang.in
++@end smallexample
++Currently, you can use any of the following:
++@code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran}, @code{java},
++@code{objc}, @code{obj-c++}.
++Building the Ada compiler has special requirements, see below.
++If you do not pass this flag, or specify the option @code{all}, then all
++default languages available in the @file{gcc} sub-tree will be configured.
++Ada and Objective-C++ are not default languages; the rest are.
++Re-defining @code{LANGUAGES} when calling @samp{make} @strong{does not}
++work anymore, as those language sub-directories might not have been
++configured!
++
++@item --enable-stage1-languages=@var{lang1},@var{lang2},@dots{}
++Specify that a particular subset of compilers and their runtime
++libraries should be built with the system C compiler during stage 1 of
++the bootstrap process, rather than only in later stages with the
++bootstrapped C compiler. The list of valid values is the same as for
++@option{--enable-languages}, and the option @code{all} will select all
++of the languages enabled by @option{--enable-languages}. This option is
++primarily useful for GCC development; for instance, when a development
++version of the compiler cannot bootstrap due to compiler bugs, or when
++one is debugging front ends other than the C front end. When this
++option is used, one can then build the target libraries for the
++specified languages with the stage-1 compiler by using @command{make
++stage1-bubble all-target}, or run the testsuite on the stage-1 compiler
++for the specified languages using @command{make stage1-start check-gcc}.
++
++@item --disable-libada
++Specify that the run-time libraries and tools used by GNAT should not
++be built. This can be useful for debugging, or for compatibility with
++previous Ada build procedures, when it was required to explicitly
++do a @samp{make -C gcc gnatlib_and_tools}.
++
++@item --disable-libssp
++Specify that the run-time libraries for stack smashing protection
++should not be built.
++
++@item --disable-libgomp
++Specify that the run-time libraries used by GOMP should not be built.
++
++@item --with-dwarf2
++Specify that the compiler should
++use DWARF 2 debugging information as the default.
++
++@item --enable-targets=all
++@itemx --enable-targets=@var{target_list}
++Some GCC targets, e.g.@: powerpc64-linux, build bi-arch compilers.
++These are compilers that are able to generate either 64-bit or 32-bit
++code. Typically, the corresponding 32-bit target, e.g.@:
++powerpc-linux for powerpc64-linux, only generates 32-bit code. This
++option enables the 32-bit target to be a bi-arch compiler, which is
++useful when you want a bi-arch compiler that defaults to 32-bit, and
++you are building a bi-arch or multi-arch binutils in a combined tree.
++Currently, this option only affects sparc-linux, powerpc-linux and
++x86-linux.
++
++@item --enable-secureplt
++This option enables @option{-msecure-plt} by default for powerpc-linux.
++@ifnothtml
++@xref{RS/6000 and PowerPC Options,, RS/6000 and PowerPC Options, gcc,
++Using the GNU Compiler Collection (GCC)},
++@end ifnothtml
++@ifhtml
++See ``RS/6000 and PowerPC Options'' in the main manual
++@end ifhtml
++
++@item --enable-cld
++This option enables @option{-mcld} by default for 32-bit x86 targets.
++@ifnothtml
++@xref{i386 and x86-64 Options,, i386 and x86-64 Options, gcc,
++Using the GNU Compiler Collection (GCC)},
++@end ifnothtml
++@ifhtml
++See ``i386 and x86-64 Options'' in the main manual
++@end ifhtml
++
++@item --enable-win32-registry
++@itemx --enable-win32-registry=@var{key}
++@itemx --disable-win32-registry
++The @option{--enable-win32-registry} option enables Microsoft Windows-hosted GCC
++to look up installations paths in the registry using the following key:
++
++@smallexample
++@code{HKEY_LOCAL_MACHINE\SOFTWARE\Free Software Foundation\@var{key}}
++@end smallexample
++
++@var{key} defaults to GCC version number, and can be overridden by the
++@option{--enable-win32-registry=@var{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 @option{--disable-win32-registry}
++option. This option has no effect on the other hosts.
++
++@item --nfp
++Specify that the machine does not have a floating point unit. This
++option only applies to @samp{m68k-sun-sunos@var{n}}. On any other
++system, @option{--nfp} has no effect.
++
++@item --enable-werror
++@itemx --disable-werror
++@itemx --enable-werror=yes
++@itemx --enable-werror=no
++When you specify this option, it controls whether certain files in the
++compiler are built with @option{-Werror} in bootstrap stage2 and later.
++If you don't specify it, @option{-Werror} is turned on for the main
++development trunk. However it defaults to off for release branches and
++final releases. The specific files which get @option{-Werror} are
++controlled by the Makefiles.
++
++@item --enable-checking
++@itemx --enable-checking=@var{list}
++When you specify this option, the compiler is built to perform internal
++consistency checks of the requested complexity. This does not change the
++generated code, but adds error checking within the compiler. This will
++slow down the compiler and may only work properly if you are building
++the compiler with GCC@. This is @samp{yes} by default when building
++from SVN or snapshots, but @samp{release} for releases. The default
++for building the stage1 compiler is @samp{yes}. More control
++over the checks may be had by specifying @var{list}. The categories of
++checks available are @samp{yes} (most common checks
++@samp{assert,misc,tree,gc,rtlflag,runtime}), @samp{no} (no checks at
++all), @samp{all} (all but @samp{valgrind}), @samp{release} (cheapest
++checks @samp{assert,runtime}) or @samp{none} (same as @samp{no}).
++Individual checks can be enabled with these flags @samp{assert},
++@samp{df}, @samp{fold}, @samp{gc}, @samp{gcac} @samp{misc}, @samp{rtl},
++@samp{rtlflag}, @samp{runtime}, @samp{tree}, and @samp{valgrind}.
++
++The @samp{valgrind} check requires the external @command{valgrind}
++simulator, available from @uref{http://valgrind.org/}. The
++@samp{df}, @samp{rtl}, @samp{gcac} and @samp{valgrind} checks are very expensive.
++To disable all checking, @samp{--disable-checking} or
++@samp{--enable-checking=none} must be explicitly requested. Disabling
++assertions will make the compiler and runtime slightly faster but
++increase the risk of undetected internal errors causing wrong code to be
++generated.
++
++@item --disable-stage1-checking
++@item --enable-stage1-checking
++@itemx --enable-stage1-checking=@var{list}
++If no @option{--enable-checking} option is specified the stage1
++compiler will be built with @samp{yes} checking enabled, otherwise
++the stage1 checking flags are the same as specified by
++@option{--enable-checking}. To build the stage1 compiler with
++different checking options use @option{--enable-stage1-checking}.
++The list of checking options is the same as for @option{--enable-checking}.
++If your system is too slow or too small to bootstrap a released compiler
++with checking for stage1 enabled, you can use @samp{--disable-stage1-checking}
++to disable checking for the stage1 compiler.
++
++@item --enable-coverage
++@itemx --enable-coverage=@var{level}
++With this option, the compiler is built to collect self coverage
++information, every time it is run. This is for internal development
++purposes, and only works when the compiler is being built with gcc. The
++@var{level} argument controls whether the compiler is built optimized or
++not, values are @samp{opt} and @samp{noopt}. For coverage analysis you
++want to disable optimization, for performance analysis you want to
++enable optimization. When coverage is enabled, the default level is
++without optimization.
++
++@item --enable-gather-detailed-mem-stats
++When this option is specified more detailed information on memory
++allocation is gathered. This information is printed when using
++@option{-fmem-report}.
++
++@item --with-gc
++@itemx --with-gc=@var{choice}
++With this option you can specify the garbage collector implementation
++used during the compilation process. @var{choice} can be one of
++@samp{page} and @samp{zone}, where @samp{page} is the default.
++
++@item --enable-nls
++@itemx --disable-nls
++The @option{--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 @option{--disable-nls} option disables NLS@.
++
++@item --with-included-gettext
++If NLS is enabled, the @option{--with-included-gettext} option causes the build
++procedure to prefer its copy of GNU @command{gettext}.
++
++@item --with-catgets
++If NLS is enabled, and if the host lacks @code{gettext} but has the
++inferior @code{catgets} interface, the GCC build procedure normally
++ignores @code{catgets} and instead uses GCC's copy of the GNU
++@code{gettext} library. The @option{--with-catgets} option causes the
++build procedure to use the host's @code{catgets} in this situation.
++
++@item --with-libiconv-prefix=@var{dir}
++Search for libiconv header files in @file{@var{dir}/include} and
++libiconv library files in @file{@var{dir}/lib}.
++
++@item --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.
++
++@item --enable-decimal-float
++@itemx --enable-decimal-float=yes
++@itemx --enable-decimal-float=no
++@itemx --enable-decimal-float=bid
++@itemx --enable-decimal-float=dpd
++@itemx --disable-decimal-float
++Enable (or disable) support for the C decimal floating point extension
++that is in the IEEE 754-2008 standard. This is enabled by default only
++on PowerPC, i386, and x86_64 GNU/Linux systems. Other systems may also
++support it, but require the user to specifically enable it. You can
++optionally control which decimal floating point format is used (either
++@samp{bid} or @samp{dpd}). The @samp{bid} (binary integer decimal)
++format is default on i386 and x86_64 systems, and the @samp{dpd}
++(densely packed decimal) format is default on PowerPC systems.
++
++@item --enable-fixed-point
++@itemx --disable-fixed-point
++Enable (or disable) support for C fixed-point arithmetic.
++This option is enabled by default for some targets (such as MIPS) which
++have hardware-support for fixed-point operations. On other targets, you
++may enable this option manually.
++
++@item --with-long-double-128
++Specify if @code{long double} type should be 128-bit by default on selected
++GNU/Linux architectures. If using @code{--without-long-double-128},
++@code{long double} will be by default 64-bit, the same as @code{double} type.
++When neither of these configure options are used, the default will be
++128-bit @code{long double} when built against GNU C Library 2.4 and later,
++64-bit @code{long double} otherwise.
++
++@item --with-gmp=@var{pathname}
++@itemx --with-gmp-include=@var{pathname}
++@itemx --with-gmp-lib=@var{pathname}
++@itemx --with-mpfr=@var{pathname}
++@itemx --with-mpfr-include=@var{pathname}
++@itemx --with-mpfr-lib=@var{pathname}
++If you do not have GMP (the GNU Multiple Precision library) and the
++MPFR Libraries installed in a standard location and you want to build
++GCC, you can explicitly specify the directory where they are installed
++(@samp{--with-gmp=@var{gmpinstalldir}},
++@samp{--with-mpfr=@var{mpfrinstalldir}}). The
++@option{--with-gmp=@var{gmpinstalldir}} option is shorthand for
++@option{--with-gmp-lib=@var{gmpinstalldir}/lib} and
++@option{--with-gmp-include=@var{gmpinstalldir}/include}. Likewise the
++@option{--with-mpfr=@var{mpfrinstalldir}} option is shorthand for
++@option{--with-mpfr-lib=@var{mpfrinstalldir}/lib} and
++@option{--with-mpfr-include=@var{mpfrinstalldir}/include}. If these
++shorthand assumptions are not correct, you can use the explicit
++include and lib options directly.
++
++@item --with-ppl=@var{pathname}
++@itemx --with-ppl-include=@var{pathname}
++@itemx --with-ppl-lib=@var{pathname}
++@itemx --with-cloog=@var{pathname}
++@itemx --with-cloog-include=@var{pathname}
++@itemx --with-cloog-lib=@var{pathname}
++If you do not have PPL (the Parma Polyhedra Library) and the CLooG
++libraries installed in a standard location and you want to build GCC,
++you can explicitly specify the directory where they are installed
++(@samp{--with-ppl=@var{pplinstalldir}},
++@samp{--with-cloog=@var{clooginstalldir}}). The
++@option{--with-ppl=@var{pplinstalldir}} option is shorthand for
++@option{--with-ppl-lib=@var{pplinstalldir}/lib} and
++@option{--with-ppl-include=@var{pplinstalldir}/include}. Likewise the
++@option{--with-cloog=@var{clooginstalldir}} option is shorthand for
++@option{--with-cloog-lib=@var{clooginstalldir}/lib} and
++@option{--with-cloog-include=@var{clooginstalldir}/include}. If these
++shorthand assumptions are not correct, you can use the explicit
++include and lib options directly.
++
++@item --with-host-libstdcxx=@var{linker-args}
++If you are linking with a static copy of PPL, you can use this option
++to specify how the linker should find the standard C++ library used
++internally by PPL. Typical values of @var{linker-args} might be
++@samp{-lstdc++} or @samp{-Wl,-Bstatic,-lstdc++,-Bdynamic -lm}. If you are
++linking with a shared copy of PPL, you probably do not need this
++option; shared library dependencies will cause the linker to search
++for the standard C++ library automatically.
++
++@item --with-debug-prefix-map=@var{map}
++Convert source directory names using @option{-fdebug-prefix-map} when
++building runtime libraries. @samp{@var{map}} is a space-separated
++list of maps of the form @samp{@var{old}=@var{new}}.
++
++@end table
++
++@subheading Cross-Compiler-Specific Options
++The following options only apply to building cross compilers.
++@table @code
++@item --with-sysroot
++@itemx --with-sysroot=@var{dir}
++Tells GCC to consider @var{dir} as the root of a tree that contains a
++(subset of) the root filesystem of the target operating system.
++Target system headers, libraries and run-time object files will be
++searched in there. The specified directory is not copied into the
++install tree, unlike the options @option{--with-headers} and
++@option{--with-libs} that this option obsoletes. The default value,
++in case @option{--with-sysroot} is not given an argument, is
++@option{$@{gcc_tooldir@}/sys-root}. If the specified directory is a
++subdirectory of @option{$@{exec_prefix@}}, then it will be found relative to
++the GCC binaries if the installation tree is moved.
++
++@item --with-build-sysroot
++@itemx --with-build-sysroot=@var{dir}
++Tells GCC to consider @var{dir} as the system root (see
++@option{--with-sysroot}) while building target libraries, instead of
++the directory specified with @option{--with-sysroot}. This option is
++only useful when you are already using @option{--with-sysroot}. You
++can use @option{--with-build-sysroot} when you are configuring with
++@option{--prefix} set to a directory that is different from the one in
++which you are installing GCC and your target libraries.
++
++This option affects the system root for the compiler used to build
++target libraries (which runs on the build system); it does not affect
++the compiler which is used to build GCC itself.
++
++@item --with-headers
++@itemx --with-headers=@var{dir}
++Deprecated in favor of @option{--with-sysroot}.
++Specifies that target headers are available when building a cross compiler.
++The @var{dir} argument specifies a directory which has the target include
++files. These include files will be copied into the @file{gcc} install
++directory. @emph{This option with the @var{dir} argument is required} when
++building a cross compiler, if @file{@var{prefix}/@var{target}/sys-include}
++doesn't pre-exist. If @file{@var{prefix}/@var{target}/sys-include} does
++pre-exist, the @var{dir} argument may be omitted. @command{fixincludes}
++will be run on these files to make them compatible with GCC@.
++
++@item --without-headers
++Tells GCC not use any target headers from a libc when building a cross
++compiler. When crossing to GNU/Linux, you need the headers so GCC
++can build the exception handling for libgcc.
++
++@item --with-libs
++@itemx --with-libs=``@var{dir1} @var{dir2} @dots{} @var{dirN}''
++Deprecated in favor of @option{--with-sysroot}.
++Specifies a list of directories which contain the target runtime
++libraries. These libraries will be copied into the @file{gcc} install
++directory. If the directory list is omitted, this option has no
++effect.
++
++@item --with-newlib
++Specifies that @samp{newlib} is
++being used as the target C library. This causes @code{__eprintf} to be
++omitted from @file{libgcc.a} on the assumption that it will be provided by
++@samp{newlib}.
++
++@item --with-build-time-tools=@var{dir}
++Specifies where to find the set of target tools (assembler, linker, etc.)
++that will be used while building GCC itself. This option can be useful
++if the directory layouts are different between the system you are building
++GCC on, and the system where you will deploy it.
++
++For example, on a @option{ia64-hp-hpux} system, you may have the GNU
++assembler and linker in @file{/usr/bin}, and the native tools in a
++different path, and build a toolchain that expects to find the
++native tools in @file{/usr/bin}.
++
++When you use this option, you should ensure that @var{dir} includes
++@command{ar}, @command{as}, @command{ld}, @command{nm},
++@command{ranlib} and @command{strip} if necessary, and possibly
++@command{objdump}. Otherwise, GCC may use an inconsistent set of
++tools.
++@end table
++
++@subheading Java-Specific Options
++
++The following option applies to the build of the Java front end.
++
++@table @code
++@item --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
++machine. In general, if the Java front end is enabled, the GCJ
++libraries will be enabled too, unless they're known to not work on
++the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
++may need to port it; in this case, before modifying the top-level
++@file{configure.in} so that @samp{libgcj} is enabled by default on this platform,
++you may use @option{--enable-libgcj} to override the default.
++
++@end table
++
++The following options apply to building @samp{libgcj}.
++
++@subsubheading General Options
++
++@table @code
++@item --enable-java-maintainer-mode
++By default the @samp{libjava} build will not attempt to compile the
++@file{.java} source files to @file{.class}. Instead, it will use the
++@file{.class} files from the source tree. If you use this option you
++must have executables named @command{ecj1} and @command{gjavah} in your path
++for use by the build. You must use this option if you intend to
++modify any @file{.java} files in @file{libjava}.
++
++@item --with-java-home=@var{dirname}
++This @samp{libjava} option overrides the default value of the
++@samp{java.home} system property. It is also used to set
++@samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
++default @samp{java.home} is set to @file{@var{prefix}} and
++@samp{sun.boot.class.path} to
++@file{@var{datadir}/java/libgcj-@var{version}.jar}.
++
++@item --with-ecj-jar=@var{filename}
++This option can be used to specify the location of an external jar
++file containing the Eclipse Java compiler. A specially modified
++version of this compiler is used by @command{gcj} to parse
++@file{.java} source files. If this option is given, the
++@samp{libjava} build will create and install an @file{ecj1} executable
++which uses this jar file at runtime.
++
++If this option is not given, but an @file{ecj.jar} file is found in
++the topmost source tree at configure time, then the @samp{libgcj}
++build will create and install @file{ecj1}, and will also install the
++discovered @file{ecj.jar} into a suitable place in the install tree.
++
++If @file{ecj1} is not installed, then the user will have to supply one
++on his path in order for @command{gcj} to properly parse @file{.java}
++source files. A suitable jar is available from
++@uref{ftp://sourceware.org/pub/java/}.
++
++@item --disable-getenv-properties
++Don't set system properties from @env{GCJ_PROPERTIES}.
++
++@item --enable-hash-synchronization
++Use a global hash table for monitor locks. Ordinarily,
++@samp{libgcj}'s @samp{configure} script automatically makes
++the correct choice for this option for your platform. Only use
++this if you know you need the library to be configured differently.
++
++@item --enable-interpreter
++Enable the Java interpreter. The interpreter is automatically
++enabled by default on all platforms that support it. This option
++is really only useful if you want to disable the interpreter
++(using @option{--disable-interpreter}).
++
++@item --disable-java-net
++Disable java.net. This disables the native part of java.net only,
++using non-functional stubs for native method implementations.
++
++@item --disable-jvmpi
++Disable JVMPI support.
++
++@item --disable-libgcj-bc
++Disable BC ABI compilation of certain parts of libgcj. By default,
++some portions of libgcj are compiled with @option{-findirect-dispatch}
++and @option{-fno-indirect-classes}, allowing them to be overridden at
++run-time.
++
++If @option{--disable-libgcj-bc} is specified, libgcj is built without
++these options. This allows the compile-time linker to resolve
++dependencies when statically linking to libgcj. However it makes it
++impossible to override the affected portions of libgcj at run-time.
++
++@item --enable-reduced-reflection
++Build most of libgcj with @option{-freduced-reflection}. This reduces
++the size of libgcj at the expense of not being able to do accurate
++reflection on the classes it contains. This option is safe if you
++know that code using libgcj will never use reflection on the standard
++runtime classes in libgcj (including using serialization, RMI or CORBA).
++
++@item --with-ecos
++Enable runtime eCos target support.
++
++@item --without-libffi
++Don't use @samp{libffi}. This will disable the interpreter and JNI
++support as well, as these require @samp{libffi} to work.
++
++@item --enable-libgcj-debug
++Enable runtime debugging code.
++
++@item --enable-libgcj-multifile
++If specified, causes all @file{.java} source files to be
++compiled into @file{.class} files in one invocation of
++@samp{gcj}. This can speed up build time, but is more
++resource-intensive. If this option is unspecified or
++disabled, @samp{gcj} is invoked once for each @file{.java}
++file to compile into a @file{.class} file.
++
++@item --with-libiconv-prefix=DIR
++Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
++
++@item --enable-sjlj-exceptions
++Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
++@samp{configure} ordinarily picks the correct value based on the platform.
++Only use this option if you are sure you need a different setting.
++
++@item --with-system-zlib
++Use installed @samp{zlib} rather than that included with GCC@.
++
++@item --with-win32-nlsapi=ansi, unicows or unicode
++Indicates how MinGW @samp{libgcj} translates between UNICODE
++characters and the Win32 API@.
++
++@item --enable-java-home
++If enabled, this creates a JPackage compatible SDK environment during install.
++Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
++be specified.
++
++@item --with-arch-directory=ARCH
++Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
++environment created when --enable-java-home is passed. Typical names for this
++directory include i386, amd64, ia64, etc.
++
++@item --with-os-directory=DIR
++Specifies the OS directory for the SDK include directory. This is set to auto
++detect, and is typically 'linux'.
++
++@item --with-origin-name=NAME
++Specifies the JPackage origin name. This defaults to the 'gcj' in
++java-1.5.0-gcj.
++
++@item --with-arch-suffix=SUFFIX
++Specifies the suffix for the sdk directory. Defaults to the empty string.
++Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
++
++@item --with-jvm-root-dir=DIR
++Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
++
++@item --with-jvm-jar-dir=DIR
++Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
++
++@item --with-python-dir=DIR
++Specifies where to install the Python modules used for aot-compile. DIR should
++not include the prefix used in installation. For example, if the Python modules
++are to be installed in /usr/lib/python2.5/site-packages, then
++--with-python-dir=/lib/python2.5/site-packages should be passed. If this is
++not specified, then the Python modules are installed in $(prefix)/share/python.
++
++@item --enable-aot-compile-rpm
++Adds aot-compile-rpm to the list of installed scripts.
++
++@table @code
++@item ansi
++Use the single-byte @code{char} and the Win32 A functions natively,
++translating to and from UNICODE when using these functions. If
++unspecified, this is the default.
++
++@item unicows
++Use the @code{WCHAR} and Win32 W functions natively. Adds
++@code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
++@file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
++running built executables. @file{libunicows.a}, an open-source
++import library around Microsoft's @code{unicows.dll}, is obtained from
++@uref{http://libunicows.sourceforge.net/}, which also gives details
++on getting @file{unicows.dll} from Microsoft.
++
++@item unicode
++Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
++add @code{-lunicows} to @file{libgcj.spec}. The built executables will
++only run on Microsoft Windows NT and above.
++@end table
++@end table
++
++@subsubheading AWT-Specific Options
++
++@table @code
++@item --with-x
++Use the X Window System.
++
++@item --enable-java-awt=PEER(S)
++Specifies the AWT peer library or libraries to build alongside
++@samp{libgcj}. If this option is unspecified or disabled, AWT
++will be non-functional. Current valid values are @option{gtk} and
++@option{xlib}. Multiple libraries should be separated by a
++comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
++
++@item --enable-gtk-cairo
++Build the cairo Graphics2D implementation on GTK@.
++
++@item --enable-java-gc=TYPE
++Choose garbage collector. Defaults to @option{boehm} if unspecified.
++
++@item --disable-gtktest
++Do not try to compile and run a test GTK+ program.
++
++@item --disable-glibtest
++Do not try to compile and run a test GLIB program.
++
++@item --with-libart-prefix=PFX
++Prefix where libart is installed (optional).
++
++@item --with-libart-exec-prefix=PFX
++Exec prefix where libart is installed (optional).
++
++@item --disable-libarttest
++Do not try to compile and run a test libart program.
++
++@end table
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Building****************************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Building, Testing, Configuration, Installing GCC
++@end ifnothtml
++@ifset buildhtml
++@ifnothtml
++@chapter Building
++@end ifnothtml
++@cindex Installing GCC: Building
++
++Now that GCC is configured, you are ready to build the compiler and
++runtime libraries.
++
++Some commands executed when making the compiler may fail (return a
++nonzero status) and be ignored by @command{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. Developers should attempt to fix
++any warnings encountered, however they can temporarily continue past
++warnings-as-errors by specifying the configure flag
++@option{--disable-werror}.
++
++On certain old systems, defining certain environment variables such as
++@env{CC} can interfere with the functioning of @command{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 @command{fixincludes} if the
++System V file system doesn't support symbolic links. These problems
++result in a failure to fix the declaration of @code{size_t} in
++@file{sys/types.h}. If you find that @code{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@.
++
++Similarly, when building from SVN or snapshots, or if you modify
++@file{*.l} files, you need the Flex lexical analyzer generator
++installed. If you do not modify @file{*.l} files, releases contain
++the Flex-generated files and you do not need Flex installed to build
++them. There is still one Flex-based lexical analyzer (part of the
++build machinery, not of GCC itself) that is used even if you only
++build the C front end.
++
++When building from SVN or snapshots, or if you modify Texinfo
++documentation, you need version 4.7 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.
++
++@section Building a native compiler
++
++For a native build, the default configuration is to perform
++a 3-stage bootstrap of the compiler when @samp{make} is invoked.
++This will build the entire GCC system and ensure that it compiles
++itself correctly. It can be disabled with the @option{--disable-bootstrap}
++parameter to @samp{configure}, but bootstrapping is suggested because
++the compiler will be tested more completely and could also have
++better performance.
++
++The bootstrapping process will complete the following steps:
++
++@itemize @bullet
++@item
++Build tools necessary to build the compiler.
++
++@item
++Perform a 3-stage bootstrap of the compiler. This includes building
++three times the target tools for use by the compiler such as binutils
++(bfd, binutils, gas, gprof, ld, and opcodes) if they have been
++individually linked or moved into the top level GCC source tree before
++configuring.
++
++@item
++Perform a comparison test of the stage2 and stage3 compilers.
++
++@item
++Build runtime libraries using the stage3 compiler from the previous step.
++
++@end itemize
++
++If you are short on disk space you might consider @samp{make
++bootstrap-lean} instead. The sequence of compilation is the
++same described above, but 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 wish to use non-default GCC flags when compiling the stage2
++and stage3 compilers, set @code{BOOT_CFLAGS} on the command line when
++doing @samp{make}. For example, 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.)
++
++@smallexample
++ make BOOT_CFLAGS='-O' bootstrap
++@end smallexample
++
++You can place non-default optimization flags into @code{BOOT_CFLAGS}; they
++are less well tested here than the default of @samp{-g -O2}, but should
++still work. In a few cases, you may find that you need to specify special
++flags such as @option{-msoft-float} here to complete the bootstrap; or,
++if the native compiler miscompiles the stage1 compiler, you may need
++to work around this, by choosing @code{BOOT_CFLAGS} to avoid the parts
++of the stage1 compiler that were miscompiled, or by using @samp{make
++bootstrap4} to increase the number of stages of bootstrap.
++
++@code{BOOT_CFLAGS} does not apply to bootstrapped target libraries.
++Since these are always compiled with the compiler currently being
++bootstrapped, you can use @code{CFLAGS_FOR_TARGET} to modify their
++compilation flags, as for non-bootstrapped target libraries.
++Again, if the native compiler miscompiles the stage1 compiler, you may
++need to work around this by avoiding non-working parts of the stage1
++compiler. Use @code{STAGE1_LIBCFLAGS} to this end.
++
++If you used the flag @option{--enable-languages=@dots{}} 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 @env{LANGUAGES} when calling @samp{make}
++@strong{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 @file{Makefile}.)
++
++If you do not want to bootstrap your compiler, you can configure with
++@option{--disable-bootstrap}. In particular cases, you may want to
++bootstrap your compiler even if the target system is not the same as
++the one you are building on: for example, you could build a
++@code{powerpc-unknown-linux-gnu} toolchain on a
++@code{powerpc64-unknown-linux-gnu} host. In this case, pass
++@option{--enable-bootstrap} to the configure script.
++
++
++@section Building a cross compiler
++
++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.
++
++If the cross compiler is to be built with support for the Java
++programming language and the ability to compile .java source files is
++desired, the installed native compiler used to build the cross
++compiler needs to be the same GCC version as the cross compiler. In
++addition the cross compiler needs to be configured with
++@option{--with-ecj-jar=@dots{}}.
++
++Assuming you have already installed a native copy of GCC and configured
++your cross compiler, issue the command @command{make}, which performs the
++following steps:
++
++@itemize @bullet
++@item
++Build host tools necessary to build the compiler.
++
++@item
++Build target tools for use by the compiler such as binutils (bfd,
++binutils, gas, gprof, ld, and opcodes)
++if they have been individually linked or moved into the top level GCC source
++tree before configuring.
++
++@item
++Build the compiler (single stage only).
++
++@item
++Build runtime libraries using the compiler from the previous step.
++@end itemize
++
++Note that if an error occurs in any step the make process will exit.
++
++If you are not building GNU binutils in the same source tree as GCC,
++you will need a cross-assembler and cross-linker installed before
++configuring GCC@. Put them in the directory
++@file{@var{prefix}/@var{target}/bin}. Here is a table of the tools
++you should put in this directory:
++
++@table @file
++@item as
++This should be the cross-assembler.
++
++@item ld
++This should be the cross-linker.
++
++@item ar
++This should be the cross-archiver: a program which can manipulate
++archive files (linker libraries) in the target machine's format.
++
++@item ranlib
++This should be a program to construct a symbol table in an archive file.
++@end table
++
++The installation of GCC 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.
++Configure it with the same @option{--host} and @option{--target}
++options that you use for configuring GCC, then build and install
++them. They install their executables automatically into the proper
++directory. Alas, they do not support all the targets that GCC
++supports.
++
++If you are not building a C library in the same source tree as GCC,
++you should also provide the target libraries and headers before
++configuring GCC, specifying the directories with
++@option{--with-sysroot} or @option{--with-headers} and
++@option{--with-libs}. Many targets also require ``start files'' such
++as @file{crt0.o} and
++@file{crtn.o} which are linked into each executable. There may be several
++alternatives for @file{crt0.o}, for use with profiling or other
++compilation options. Check your target's definition of
++@code{STARTFILE_SPEC} to find out what start files it uses.
++
++@section Building in parallel
++
++GNU Make 3.79 and above, which is necessary to build GCC, support
++building in parallel. To activate this, you can use @samp{make -j 2}
++instead of @samp{make}. You can also specify a bigger number, and
++in most cases using a value greater than the number of processors in
++your machine will result in fewer and shorter I/O latency hits, thus
++improving overall throughput; this is especially true for slow drives
++and network filesystems.
++
++@section Building the Ada compiler
++
++In order to build GNAT, the Ada compiler, you need a working GNAT
++compiler (GCC version 3.4 or later).
++This includes GNAT tools such as @command{gnatmake} and
++@command{gnatlink}, since the Ada front end is written in Ada and
++uses some GNAT-specific extensions.
++
++In order to build a cross compiler, it is suggested to install
++the new compiler as native first, and then use it to build the cross
++compiler.
++
++@command{configure} does not test whether the GNAT installation works
++and has a sufficiently recent version; if too old a GNAT version is
++installed, the build will fail unless @option{--enable-languages} is
++used to disable building the Ada front end.
++
++@env{ADA_INCLUDE_PATH} and @env{ADA_OBJECT_PATH} environment variables
++must not be set when building the Ada compiler, the Ada tools, or the
++Ada runtime libraries. You can check that your build environment is clean
++by verifying that @samp{gnatls -v} lists only one explicit path in each
++section.
++
++@section Building with profile feedback
++
++It is possible to use profile feedback to optimize the compiler itself. This
++should result in a faster compiler binary. Experiments done on x86 using gcc
++3.3 showed approximately 7 percent speedup on compiling C programs. To
++bootstrap the compiler with profile feedback, use @code{make profiledbootstrap}.
++
++When @samp{make profiledbootstrap} is run, it will first build a @code{stage1}
++compiler. This compiler is used to build a @code{stageprofile} compiler
++instrumented to collect execution counts of instruction and branch
++probabilities. Then runtime libraries are compiled with profile collected.
++Finally a @code{stagefeedback} compiler is built using the information collected.
++
++Unlike standard bootstrap, several additional restrictions apply. The
++compiler used to build @code{stage1} needs to support a 64-bit integral type.
++It is recommended to only use GCC for this. Also parallel make is currently
++not supported since collisions in profile collecting may occur.
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Testing*****************************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Testing, Final install, Building, Installing GCC
++@end ifnothtml
++@ifset testhtml
++@ifnothtml
++@chapter Installing GCC: Testing
++@end ifnothtml
++@cindex Testing
++@cindex Installing GCC: Testing
++@cindex Testsuite
++
++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
++@uref{http://gcc.gnu.org/ml/gcc-testresults/,,gcc-testresults mailing list}.
++Some of these archived results are linked from the build status lists
++at @uref{http://gcc.gnu.org/buildstat.html}, although not everyone who
++reports a successful build runs the testsuites and submits the results.
++This step is optional and may require you to download additional software,
++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 @uref{download.html,,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
++@uref{http://www.gnu.org/software/dejagnu/,,DejaGnu}, Tcl, and Expect;
++the DejaGnu site has links to these.
++
++If the directories where @command{runtest} and @command{expect} were
++installed are not in the @env{PATH}, you may need to set the following
++environment variables appropriately, as in the following example (which
++assumes that DejaGnu has been installed under @file{/usr/local}):
++
++@smallexample
++ TCL_LIBRARY = /usr/local/share/tcl8.0
++ DEJAGNULIBS = /usr/local/share/dejagnu
++@end smallexample
++
++(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.)
++
++
++Finally, you can run the testsuite (which may take a long time):
++@smallexample
++ cd @var{objdir}; make -k check
++@end smallexample
++
++This will test various components of GCC, such as compiler
++front ends and runtime libraries. While running the testsuite, DejaGnu
++might emit some harmless messages resembling
++@samp{WARNING: Couldn't find the global config file.} or
++@samp{WARNING: Couldn't find tool init file} that can be ignored.
++
++If you are testing a cross-compiler, you may want to run the testsuite
++on a simulator as described at @uref{http://gcc.gnu.org/simtest-howto.html}.
++
++@section How can you run the testsuite on selected tests?
++
++In order to run sets of tests selectively, there are targets
++@samp{make check-gcc} and @samp{make check-g++}
++in the @file{gcc} subdirectory of the object directory. You can also
++just run @samp{make check} in a subdirectory of the object directory.
++
++
++A more selective way to just run all @command{gcc} execute tests in the
++testsuite is to use
++
++@smallexample
++ make check-gcc RUNTESTFLAGS="execute.exp @var{other-options}"
++@end smallexample
++
++Likewise, in order to run only the @command{g++} ``old-deja'' tests in
++the testsuite with filenames matching @samp{9805*}, you would use
++
++@smallexample
++ make check-g++ RUNTESTFLAGS="old-deja.exp=9805* @var{other-options}"
++@end smallexample
++
++The @file{*.exp} files are located in the testsuite directories of the GCC
++source, the most important ones being @file{compile.exp},
++@file{execute.exp}, @file{dg.exp} and @file{old-deja.exp}.
++To get a list of the possible @file{*.exp} files, pipe the
++output of @samp{make check} into a file and look at the
++@samp{Running @dots{} .exp} lines.
++
++@section Passing options and running multiple testsuites
++
++You can pass multiple options to the testsuite using the
++@samp{--target_board} option of DejaGNU, either passed as part of
++@samp{RUNTESTFLAGS}, or directly to @command{runtest} if you prefer to
++work outside the makefiles. For example,
++
++@smallexample
++ make check-g++ RUNTESTFLAGS="--target_board=unix/-O3/-fmerge-constants"
++@end smallexample
++
++will run the standard @command{g++} testsuites (``unix'' is the target name
++for a standard native testsuite situation), passing
++@samp{-O3 -fmerge-constants} to the compiler on every test, i.e.,
++slashes separate options.
++
++You can run the testsuites multiple times using combinations of options
++with a syntax similar to the brace expansion of popular shells:
++
++@smallexample
++ @dots{}"--target_board=arm-sim\@{-mhard-float,-msoft-float\@}\@{-O1,-O2,-O3,\@}"
++@end smallexample
++
++(Note the empty option caused by the trailing comma in the final group.)
++The following will run each testsuite eight times using the @samp{arm-sim}
++target, as if you had specified all possible combinations yourself:
++
++@smallexample
++ --target_board=arm-sim/-mhard-float/-O1
++ --target_board=arm-sim/-mhard-float/-O2
++ --target_board=arm-sim/-mhard-float/-O3
++ --target_board=arm-sim/-mhard-float
++ --target_board=arm-sim/-msoft-float/-O1
++ --target_board=arm-sim/-msoft-float/-O2
++ --target_board=arm-sim/-msoft-float/-O3
++ --target_board=arm-sim/-msoft-float
++@end smallexample
++
++They can be combined as many times as you wish, in arbitrary ways. This
++list:
++
++@smallexample
++ @dots{}"--target_board=unix/-Wextra\@{-O3,-fno-strength\@}\@{-fomit-frame,\@}"
++@end smallexample
++
++will generate four combinations, all involving @samp{-Wextra}.
++
++The disadvantage to this method is that the testsuites are run in serial,
++which is a waste on multiprocessor systems. For users with GNU Make and
++a shell which performs brace expansion, you can run the testsuites in
++parallel by having the shell perform the combinations and @command{make}
++do the parallel runs. Instead of using @samp{--target_board}, use a
++special makefile target:
++
++@smallexample
++ make -j@var{N} check-@var{testsuite}//@var{test-target}/@var{option1}/@var{option2}/@dots{}
++@end smallexample
++
++For example,
++
++@smallexample
++ make -j3 check-gcc//sh-hms-sim/@{-m1,-m2,-m3,-m3e,-m4@}/@{,-nofpu@}
++@end smallexample
++
++will run three concurrent ``make-gcc'' testsuites, eventually testing all
++ten combinations as described above. Note that this is currently only
++supported in the @file{gcc} subdirectory. (To see how this works, try
++typing @command{echo} before the example given here.)
++
++
++@section Additional testing for Java Class Libraries
++
++The Java runtime tests can be executed via @samp{make check}
++in the @file{@var{target}/libjava/testsuite} directory in
++the build tree.
++
++The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
++a suite of tests for the Java Class Libraries. This suite can be run
++as part of libgcj testing by placing the Mauve tree within the libjava
++testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
++specifying the location of that tree when invoking @samp{make}, as in
++@samp{make MAUVEDIR=~/mauve check}.
++
++@section How to interpret test results
++
++The result of running the testsuite are various @file{*.sum} and @file{*.log}
++files in the testsuite subdirectories. The @file{*.log} files contain a
++detailed log of the compiler invocations and the corresponding
++results, the @file{*.sum} files summarize the results. These summaries
++contain status codes for all tests:
++
++@itemize @bullet
++@item
++PASS: the test passed as expected
++@item
++XPASS: the test unexpectedly passed
++@item
++FAIL: the test unexpectedly failed
++@item
++XFAIL: the test failed as expected
++@item
++UNSUPPORTED: the test is not supported on this platform
++@item
++ERROR: the testsuite detected an error
++@item
++WARNING: the testsuite detected a possible problem
++@end itemize
++
++It is normal for some tests to report unexpected failures. At the
++current time the testing harness does not allow fine grained control
++over whether or not a test is expected to fail. This problem should
++be fixed in future releases.
++
++
++@section Submitting test results
++
++If you want to report the results to the GCC project, use the
++@file{contrib/test_summary} shell script. Start it in the @var{objdir} with
++
++@smallexample
++ @var{srcdir}/contrib/test_summary -p your_commentary.txt \
++ -m gcc-testresults@@gcc.gnu.org |sh
++@end smallexample
++
++This script uses the @command{Mail} program to send the results, so
++make sure it is in your @env{PATH}. The file @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
++do not edit the testsuite result block or the subject line, as these
++messages may be automatically processed.
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Final install***********************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Final install, , Testing, Installing GCC
++@end ifnothtml
++@ifset finalinstallhtml
++@ifnothtml
++@chapter Installing GCC: Final installation
++@end ifnothtml
++
++Now that GCC has been built (and optionally tested), you can install it with
++@smallexample
++cd @var{objdir}; make install
++@end smallexample
++
++We strongly recommend to install into a target directory where there is
++no previous version of GCC present. Also, the GNAT runtime should not
++be stripped, as this would break certain features of the debugger that
++depend on this debugging information (catching Ada exceptions for
++instance).
++
++That step completes the installation of GCC; user level binaries can
++be found in @file{@var{prefix}/bin} where @var{prefix} is the value
++you specified with the @option{--prefix} to configure (or
++@file{/usr/local} by default). (If you specified @option{--bindir},
++that directory will be used instead; otherwise, if you specified
++@option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
++Headers for the C++ and Java libraries are installed in
++@file{@var{prefix}/include}; libraries in @file{@var{libdir}}
++(normally @file{@var{prefix}/lib}); internal parts of the compiler in
++@file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
++in info format in @file{@var{infodir}} (normally
++@file{@var{prefix}/info}).
++
++When installing cross-compilers, GCC's executables
++are not only installed into @file{@var{bindir}}, that
++is, @file{@var{exec-prefix}/bin}, but additionally into
++@file{@var{exec-prefix}/@var{target-alias}/bin}, if that directory
++exists. Typically, such @dfn{tooldirs} hold target-specific
++binutils, including assembler and linker.
++
++Installation into a temporary staging area or into a @command{chroot}
++jail can be achieved with the command
++
++@smallexample
++make DESTDIR=@var{path-to-rootdir} install
++@end smallexample
++
++@noindent where @var{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 @code{DESTDIR}
++need not exist yet; it will be created if necessary.
++
++There is a subtle point with tooldirs and @code{DESTDIR}:
++If you relocate a cross-compiler installation with
++e.g.@: @samp{DESTDIR=@var{rootdir}}, then the directory
++@file{@var{rootdir}/@var{exec-prefix}/@var{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 @code{DESTDIR} feature.
++
++If you are bootstrapping a released version of GCC then please
++quickly review the build status page for your release, available from
++@uref{http://gcc.gnu.org/buildstat.html}.
++If your system is not listed for the version of GCC that you built,
++send a note to
++@email{gcc@@gcc.gnu.org} indicating
++that you successfully built and installed GCC@.
++Include the following information:
++
++@itemize @bullet
++@item
++Output from running @file{@var{srcdir}/config.guess}. Do not send
++that file itself, just the one-line output from running it.
++
++@item
++The output of @samp{gcc -v} for your newly installed @command{gcc}.
++This tells us which version of GCC you built and the options you passed to
++configure.
++
++@item
++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 @samp{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.
++
++@item
++If the build was for GNU/Linux, also include:
++@itemize @bullet
++@item
++The distribution name and version (e.g., Red Hat 7.1 or Debian 2.2.3);
++this information should be available from @file{/etc/issue}.
++
++@item
++The version of the Linux kernel, available from @samp{uname --version}
++or @samp{uname -a}.
++
++@item
++The version of glibc you used; for RPM-based systems like Red Hat,
++Mandrake, and SuSE type @samp{rpm -q glibc} to get the glibc version,
++and on systems like Debian and Progeny use @samp{dpkg -l libc6}.
++@end itemize
++For other systems, you can include similar information if you think it is
++relevant.
++
++@item
++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.
++@end itemize
++
++We'd also like to know if the
++@ifnothtml
++@ref{Specific, host/target specific installation notes}
++@end ifnothtml
++@ifhtml
++@uref{specific.html,,host/target specific installation notes}
++@end ifhtml
++didn't include your host/target information or if that information is
++incomplete or out of date. Send a note to
++@email{gcc@@gcc.gnu.org} detailing how the information should be changed.
++
++If you find a bug, please report it following the
++@uref{../bugs.html,,bug reporting guidelines}.
++
++If you want to print the GCC manuals, do @samp{cd @var{objdir}; make
++dvi}. You will need to have @command{texi2dvi} (version at least 4.7)
++and @TeX{} installed. This creates a number of @file{.dvi} files in
++subdirectories of @file{@var{objdir}}; these may be converted for
++printing with programs such as @command{dvips}. Alternately, by using
++@samp{make pdf} in place of @samp{make dvi}, you can create documentation
++in the form of @file{.pdf} files; this requires @command{texi2pdf}, which
++is included with Texinfo version 4.8 and later. You can also
++@uref{http://shop.fsf.org/,,buy printed manuals from the
++Free Software Foundation}, though such manuals may not be for the most
++recent version of GCC@.
++
++If you would like to generate online HTML documentation, do @samp{cd
++@var{objdir}; make html} and HTML will be generated for the gcc manuals in
++@file{@var{objdir}/gcc/HTML}.
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Binaries****************************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Binaries, Specific, Installing GCC, Top
++@end ifnothtml
++@ifset binarieshtml
++@ifnothtml
++@chapter Installing GCC: Binaries
++@end ifnothtml
++@cindex Binaries
++@cindex 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.
++
++@itemize
++@item
++AIX:
++@itemize
++@item
++@uref{http://www.bullfreeware.com,,Bull's Freeware and Shareware Archive for AIX};
++
++@item
++@uref{http://pware.hvcc.edu,,Hudson Valley Community College Open Source Software for IBM System p};
++
++@item
++@uref{http://www.perzl.org/aix/,,AIX 5L and 6 Open Source Packages}.
++@end itemize
++
++@item
++DOS---@uref{http://www.delorie.com/djgpp/,,DJGPP}.
++
++@item
++Renesas H8/300[HS]---@uref{http://h8300-hms.sourceforge.net/,,GNU
++Development Tools for the Renesas H8/300[HS] Series}.
++
++@item
++HP-UX:
++@itemize
++@item
++@uref{http://hpux.cs.utah.edu/,,HP-UX Porting Center};
++
++@item
++@uref{ftp://sunsite.informatik.rwth-aachen.de/pub/packages/gcc_hpux/,,Binaries for HP-UX 11.00 at Aachen University of Technology}.
++@end itemize
++
++@item
++Motorola 68HC11/68HC12---@uref{http://www.gnu-m68hc11.org,,GNU
++Development Tools for the Motorola 68HC11/68HC12}.
++
++@item
++@uref{http://www.sco.com/skunkware/devtools/index.html#gcc,,SCO
++OpenServer/Unixware}.
++
++@item
++Solaris 2 (SPARC, Intel)---@uref{http://www.sunfreeware.com/,,Sunfreeware}.
++
++@item
++SGI---@uref{http://freeware.sgi.com/,,SGI Freeware}.
++
++@item
++Microsoft Windows:
++@itemize
++@item
++The @uref{http://sourceware.org/cygwin/,,Cygwin} project;
++@item
++The @uref{http://www.mingw.org/,,MinGW} project.
++@end itemize
++
++@item
++@uref{ftp://ftp.thewrittenword.com/packages/by-name/,,The
++Written Word} offers binaries for
++AIX 4.3.3, 5.1 and 5.2,
++IRIX 6.5,
++Tru64 UNIX 4.0D and 5.1,
++GNU/Linux (i386),
++HP-UX 10.20, 11.00, and 11.11, and
++Solaris/SPARC 2.5.1, 2.6, 7, 8, 9 and 10.
++
++@item
++@uref{http://www.openpkg.org/,,OpenPKG} offers binaries for quite a
++number of platforms.
++
++@item
++The @uref{http://gcc.gnu.org/wiki/GFortranBinaries,,GFortran Wiki} has
++links to GNU Fortran binaries for several platforms.
++@end itemize
++
++In addition to those specific offerings, you can get a binary
++distribution CD-ROM from the
++@uref{http://www.gnu.org/order/order.html,,Free Software Foundation}.
++It contains binaries for a number of platforms, and
++includes not only GCC, but other stuff as well. The current CD does
++not contain the latest version of GCC, but it should allow
++bootstrapping the compiler. An updated version of that disk is in the
++works.
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Specific****************************************************************
++@ifnothtml
++@comment node-name, next, previous, up
++@node Specific, Old, Binaries, Top
++@end ifnothtml
++@ifset specifichtml
++@ifnothtml
++@chapter Host/target specific installation notes for GCC
++@end ifnothtml
++@cindex Specific
++@cindex Specific installation notes
++@cindex Target specific installation
++@cindex Host specific installation
++@cindex Target specific installation notes
++
++Please read this document carefully @emph{before} installing the
++GNU Compiler Collection on your machine.
++
++Note that this list of install notes is @emph{not} a list of supported
++hosts or targets. Not all supported hosts and targets are listed
++here, only the ones that require host-specific or target-specific
++information are.
++
++@ifhtml
++@itemize
++@item
++@uref{#alpha-x-x,,alpha*-*-*}
++@item
++@uref{#alpha-dec-osf,,alpha*-dec-osf*}
++@item
++@uref{#arc-x-elf,,arc-*-elf}
++@item
++@uref{#arm-x-elf,,arm-*-elf}
++@uref{#arm-x-coff,,arm-*-coff}
++@uref{#arm-x-aout,,arm-*-aout}
++@item
++@uref{#avr,,avr}
++@item
++@uref{#bfin,,Blackfin}
++@item
++@uref{#dos,,DOS}
++@item
++@uref{#x-x-freebsd,,*-*-freebsd*}
++@item
++@uref{#h8300-hms,,h8300-hms}
++@item
++@uref{#hppa-hp-hpux,,hppa*-hp-hpux*}
++@item
++@uref{#hppa-hp-hpux10,,hppa*-hp-hpux10}
++@item
++@uref{#hppa-hp-hpux11,,hppa*-hp-hpux11}
++@item
++@uref{#x-x-linux-gnu,,*-*-linux-gnu}
++@item
++@uref{#ix86-x-linux,,i?86-*-linux*}
++@item
++@uref{#ix86-x-solaris210,,i?86-*-solaris2.10}
++@item
++@uref{#ia64-x-linux,,ia64-*-linux}
++@item
++@uref{#ia64-x-hpux,,ia64-*-hpux*}
++@item
++@uref{#x-ibm-aix,,*-ibm-aix*}
++@item
++@uref{#iq2000-x-elf,,iq2000-*-elf}
++@item
++@uref{#m32c-x-elf,,m32c-*-elf}
++@item
++@uref{#m32r-x-elf,,m32r-*-elf}
++@item
++@uref{#m6811-elf,,m6811-elf}
++@item
++@uref{#m6812-elf,,m6812-elf}
++@item
++@uref{#m68k-x-x,,m68k-*-*}
++@item
++@uref{#m68k-uclinux,,m68k-uclinux}
++@item
++@uref{#mips-x-x,,mips-*-*}
++@item
++@uref{#mips-sgi-irix5,,mips-sgi-irix5}
++@item
++@uref{#mips-sgi-irix6,,mips-sgi-irix6}
++@item
++@uref{#powerpc-x-x,,powerpc*-*-*}
++@item
++@uref{#powerpc-x-darwin,,powerpc-*-darwin*}
++@item
++@uref{#powerpc-x-elf,,powerpc-*-elf}
++@item
++@uref{#powerpc-x-linux-gnu,,powerpc*-*-linux-gnu*}
++@item
++@uref{#powerpc-x-netbsd,,powerpc-*-netbsd*}
++@item
++@uref{#powerpc-x-eabisim,,powerpc-*-eabisim}
++@item
++@uref{#powerpc-x-eabi,,powerpc-*-eabi}
++@item
++@uref{#powerpcle-x-elf,,powerpcle-*-elf}
++@item
++@uref{#powerpcle-x-eabisim,,powerpcle-*-eabisim}
++@item
++@uref{#powerpcle-x-eabi,,powerpcle-*-eabi}
++@item
++@uref{#s390-x-linux,,s390-*-linux*}
++@item
++@uref{#s390x-x-linux,,s390x-*-linux*}
++@item
++@uref{#s390x-ibm-tpf,,s390x-ibm-tpf*}
++@item
++@uref{#x-x-solaris2,,*-*-solaris2*}
++@item
++@uref{#sparc-sun-solaris2,,sparc-sun-solaris2*}
++@item
++@uref{#sparc-sun-solaris27,,sparc-sun-solaris2.7}
++@item
++@uref{#sparc-x-linux,,sparc-*-linux*}
++@item
++@uref{#sparc64-x-solaris2,,sparc64-*-solaris2*}
++@item
++@uref{#sparcv9-x-solaris2,,sparcv9-*-solaris2*}
++@item
++@uref{#x-x-vxworks,,*-*-vxworks*}
++@item
++@uref{#x86-64-x-x,,x86_64-*-*, amd64-*-*}
++@item
++@uref{#xtensa-x-elf,,xtensa*-*-elf}
++@item
++@uref{#xtensa-x-linux,,xtensa*-*-linux*}
++@item
++@uref{#windows,,Microsoft Windows}
++@item
++@uref{#x-x-cygwin,,*-*-cygwin}
++@item
++@uref{#x-x-interix,,*-*-interix}
++@item
++@uref{#x-x-mingw,,*-*-mingw}
++@item
++@uref{#os2,,OS/2}
++@item
++@uref{#older,,Older systems}
++@end itemize
++
++@itemize
++@item
++@uref{#elf,,all ELF targets} (SVR4, Solaris 2, etc.)
++@end itemize
++@end ifhtml
++
++
++@html
++<!-- -------- host/target specific issues start here ---------------- -->
++<hr />
++@end html
++@heading @anchor{alpha-x-x}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.
++
++@html
++<hr />
++@end html
++@heading @anchor{alpha-dec-osf}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.
++
++As of GCC 3.2, versions before @code{alpha*-dec-osf4} are no longer
++supported. (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 @option{--with-gc=simple},
++reconfiguring Kernel Virtual Memory and Swap parameters
++per the @command{/usr/sbin/sys_check} Tuning Suggestions,
++or applying the patch in
++@uref{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 @command{mips-tfile}. As a workaround,
++we need to use the old assembler, invoked via the barely documented
++@option{-oldas} option. To bootstrap GCC, you either need to use the
++Compaq C Compiler:
++
++@smallexample
++ % CC=cc @var{srcdir}/configure [@var{options}] [@var{target}]
++@end smallexample
++
++or you can use a copy of GCC 2.95.3 or higher built on Tru64 UNIX V4.0:
++
++@smallexample
++ % CC=gcc -Wa,-oldas @var{srcdir}/configure [@var{options}] [@var{target}]
++@end smallexample
++
++As of GNU binutils 2.11.2, neither GNU @command{as} nor GNU @command{ld}
++are supported on Tru64 UNIX, so you must not configure GCC with
++@option{--with-gnu-as} or @option{--with-gnu-ld}.
++
++GCC writes a @samp{.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 @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.
++
++@samp{make compare} may fail on old versions of DEC Unix unless you add
++@option{-save-temps} to @code{BOOT_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 @code{stage1} and
++@code{stage2} compilations. The option @option{-save-temps} forces a
++fixed name to be used for the assembler input file, instead of a
++randomly chosen name in @file{/tmp}. Do not add @option{-save-temps}
++unless the comparisons fail without that option. If you add
++@option{-save-temps}, you will have to manually delete the @samp{.i} and
++@samp{.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 @option{--with-stabs} option of @file{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 @samp{.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 has the very undesirable
++side-effect that code addresses when @option{-O} is specified are
++different depending on whether or not @option{-g} is also specified.
++
++To avoid this behavior, specify @option{-gstabs+} and use GDB instead of
++DBX@. DEC is now aware of this problem with the assembler and hopes to
++provide a fix shortly.
++
++@html
++<hr />
++@end html
++@heading @anchor{arc-x-elf}arc-*-elf
++Argonaut ARC processor.
++This configuration is intended for embedded systems.
++
++@html
++<hr />
++@end html
++@heading @anchor{arm-x-elf}arm-*-elf
++ARM-family processors. Subtargets that use the ELF object format
++require GNU binutils 2.13 or newer. Such subtargets include:
++@code{arm-*-freebsd}, @code{arm-*-netbsdelf}, @code{arm-*-*linux}
++and @code{arm-*-rtems}.
++
++@html
++<hr />
++@end html
++@heading @anchor{arm-x-coff}arm-*-coff
++ARM-family processors. Note that there are two different varieties
++of PE format subtarget supported: @code{arm-wince-pe} and
++@code{arm-pe} as well as a standard COFF target @code{arm-*-coff}.
++
++@html
++<hr />
++@end html
++@heading @anchor{arm-x-aout}arm-*-aout
++ARM-family processors. These targets support the AOUT file format:
++@code{arm-*-aout}, @code{arm-*-netbsd}.
++
++@html
++<hr />
++@end html
++@heading @anchor{avr}avr
++
++ATMEL AVR-family micro controllers. These are used in embedded
++applications. There are no standard Unix configurations.
++@ifnothtml
++@xref{AVR Options,, AVR Options, gcc, Using the GNU Compiler
++Collection (GCC)},
++@end ifnothtml
++@ifhtml
++See ``AVR Options'' in the main manual
++@end ifhtml
++for the list of supported MCU types.
++
++Use @samp{configure --target=avr --enable-languages="c"} to configure GCC@.
++
++Further installation notes and other useful information about AVR tools
++can also be obtained from:
++
++@itemize @bullet
++@item
++@uref{http://www.nongnu.org/avr/,,http://www.nongnu.org/avr/}
++@item
++@uref{http://www.amelek.gda.pl/avr/,,http://www.amelek.gda.pl/avr/}
++@end itemize
++
++We @emph{strongly} recommend using binutils 2.13 or newer.
++
++The following error:
++@smallexample
++ Error: register required
++@end smallexample
++
++indicates that you should upgrade to a newer version of the binutils.
++
++@html
++<hr />
++@end html
++@heading @anchor{bfin}Blackfin
++
++The Blackfin processor, an Analog Devices DSP.
++@ifnothtml
++@xref{Blackfin Options,, Blackfin Options, gcc, Using the GNU Compiler
++Collection (GCC)},
++@end ifnothtml
++@ifhtml
++See ``Blackfin Options'' in the main manual
++@end ifhtml
++
++More information, and a version of binutils with support for this processor,
++is available at @uref{http://blackfin.uclinux.org}
++
++@html
++<hr />
++@end html
++@heading @anchor{cris}CRIS
++
++CRIS is the CPU architecture in Axis Communications ETRAX system-on-a-chip
++series. These are used in embedded applications.
++
++@ifnothtml
++@xref{CRIS Options,, CRIS Options, gcc, Using the GNU Compiler
++Collection (GCC)},
++@end ifnothtml
++@ifhtml
++See ``CRIS Options'' in the main manual
++@end ifhtml
++for a list of CRIS-specific options.
++
++There are a few different CRIS targets:
++@table @code
++@item cris-axis-elf
++Mainly for monolithic embedded systems. Includes a multilib for the
++@samp{v10} core used in @samp{ETRAX 100 LX}.
++@item cris-axis-linux-gnu
++A GNU/Linux port for the CRIS architecture, currently targeting
++@samp{ETRAX 100 LX} by default.
++@end table
++
++For @code{cris-axis-elf} you need binutils 2.11
++or newer. For @code{cris-axis-linux-gnu} you need binutils 2.12 or newer.
++
++Pre-packaged tools can be obtained from
++@uref{ftp://ftp.axis.com/pub/axis/tools/cris/compiler-kit/}. More
++information about this platform is available at
++@uref{http://developer.axis.com/}.
++
++@html
++<hr />
++@end html
++@heading @anchor{crx}CRX
++
++The CRX CompactRISC architecture is a low-power 32-bit architecture with
++fast context switching and architectural extensibility features.
++
++@ifnothtml
++@xref{CRX Options,, CRX Options, gcc, Using and Porting the GNU Compiler
++Collection (GCC)},
++@end ifnothtml
++
++@ifhtml
++See ``CRX Options'' in the main manual for a list of CRX-specific options.
++@end ifhtml
++
++Use @samp{configure --target=crx-elf --enable-languages=c,c++} to configure
++GCC@ for building a CRX cross-compiler. The option @samp{--target=crx-elf}
++is also used to build the @samp{newlib} C library for CRX.
++
++It is also possible to build libstdc++-v3 for the CRX architecture. This
++needs to be done in a separate step with the following configure settings:
++@samp{gcc/libstdc++-v3/configure --host=crx-elf --with-newlib
++--enable-sjlj-exceptions --enable-cxx-flags='-fexceptions -frtti'}
++
++@html
++<hr />
++@end html
++@heading @anchor{dos}DOS
++
++Please have a look at the @uref{binaries.html,,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.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-freebsd}*-*-freebsd*
++
++The version of binutils installed in @file{/usr/bin} probably works with
++this release of GCC@. However, on FreeBSD 4, bootstrapping against the
++latest FSF binutils is known to improve overall testsuite results; and,
++on FreeBSD/alpha, using binutils 2.14 or later is required to build libjava.
++
++Support for FreeBSD 1 was discontinued in GCC 3.2.
++
++Support for FreeBSD 2 will be discontinued after GCC 3.4. The
++following was true for GCC 3.1 but the current status is unknown.
++For 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 @file{/usr/bin}) and C++ EH failures were noted.
++
++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 @option{-gstabs} instead
++of @option{-g}, if you really want the old debugging format. There are
++no known issues with mixing object files and libraries with different
++debugging formats. Otherwise, this release of GCC should now match more
++of the configuration used in the stock FreeBSD configuration of GCC@. In
++particular, @option{--enable-threads} is now configured by default.
++However, as a general user, do not attempt to replace the system
++compiler with this release. Known to bootstrap and check with good
++results on FreeBSD 4.9-STABLE and 5-CURRENT@. In the past, known to
++bootstrap and check with good results on FreeBSD 3.0, 3.4, 4.0, 4.2,
++4.3, 4.4, 4.5, 4.8-STABLE@.
++
++In principle, @option{--enable-threads} is now compatible with
++@option{--enable-libgcj} on FreeBSD@. However, it has only been built
++and tested on @samp{i386-*-freebsd[45]} and @samp{alpha-*-freebsd[45]}.
++The static
++library may be incorrectly built (symbols are missing at link time).
++There is a rare timing-based startup hang (probably involves an
++assumption about the thread library). Multi-threaded boehm-gc (required for
++libjava) exposes severe threaded signal-handling bugs on FreeBSD before
++4.5-RELEASE@. Other CPU architectures
++supported by FreeBSD will require additional configuration tuning in, at
++the very least, both boehm-gc and libffi.
++
++Shared @file{libgcc_s.so} is now built and installed by default.
++
++@html
++<hr />
++@end html
++@heading @anchor{h8300-hms}h8300-hms
++Renesas H8/300 series of processors.
++
++Please have a look at the @uref{binaries.html,,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.
++
++@html
++<hr />
++@end html
++@heading @anchor{hppa-hp-hpux}hppa*-hp-hpux*
++Support for HP-UX version 9 and older was discontinued in GCC 3.4.
++
++We require using gas/binutils on all hppa platforms. Version 2.19 or
++later is recommended.
++
++It may be helpful to configure GCC with the
++@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
++@option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
++
++The HP assembler should not be used with GCC. It is rarely tested and may
++not work. It shouldn't be used with any languages other than C due to its
++many limitations.
++
++Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
++format which GCC does not know about). It also inserts timestamps
++into each object file it creates, causing the 3-stage comparison test to
++fail during a bootstrap. You should be able to continue by saying
++@samp{make all-host all-target} after getting the failure from @samp{make}.
++
++Various GCC features are not supported. For example, it does not support weak
++symbols or alias definitions. As a result, explicit template instantiations
++are required when using C++. This makes it difficult if not impossible to
++build many C++ applications.
++
++There are two default scheduling models for instructions. These are
++PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
++architecture specified for the target machine when configuring.
++PROCESSOR_8000 is the default. PROCESSOR_7100LC is selected when
++the target is a @samp{hppa1*} machine.
++
++The PROCESSOR_8000 model is not well suited to older processors. Thus,
++it is important to completely specify the machine architecture when
++configuring if you want a model other than PROCESSOR_8000. The macro
++TARGET_SCHED_DEFAULT can be defined in BOOT_CFLAGS if a different
++default scheduling model is desired.
++
++As of GCC 4.0, GCC uses the UNIX 95 namespace for HP-UX 10.10
++through 11.00, and the UNIX 98 namespace for HP-UX 11.11 and later.
++This namespace change might cause problems when bootstrapping with
++an earlier version of GCC or the HP compiler as essentially the same
++namespace is required for an entire build. This problem can be avoided
++in a number of ways. With HP cc, @env{UNIX_STD} can be set to @samp{95}
++or @samp{98}. Another way is to add an appropriate set of predefines
++to @env{CC}. The description for the @option{munix=} option contains
++a list of the predefines used with each standard.
++
++More specific information to @samp{hppa*-hp-hpux*} targets follows.
++
++@html
++<hr />
++@end html
++@heading @anchor{hppa-hp-hpux10}hppa*-hp-hpux10
++
++For hpux10.20, we @emph{highly} recommend you pick up the latest sed patch
++@code{PHCO_19798} from HP@. HP has two sites which provide patches free of
++charge:
++
++@itemize @bullet
++@item
++@html
++<a href="http://us.itrc.hp.com/service/home/home.do">US, Canada, Asia-Pacific, and
++Latin-America</a>
++@end html
++@ifnothtml
++@uref{http://us.itrc.hp.com/service/home/home.do,,} US, Canada, Asia-Pacific,
++and Latin-America.
++@end ifnothtml
++@item
++@uref{http://europe.itrc.hp.com/service/home/home.do,,} Europe.
++@end itemize
++
++The C++ ABI has changed incompatibly in GCC 4.0. COMDAT subspaces are
++used for one-only code and data. This resolves many of the previous
++problems in using C++ on this target. However, the ABI is not compatible
++with the one implemented under HP-UX 11 using secondary definitions.
++
++@html
++<hr />
++@end html
++@heading @anchor{hppa-hp-hpux11}hppa*-hp-hpux11
++
++GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
++be used to compile GCC 3.0 and up.
++
++The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
++and don't build.
++
++Refer to @uref{binaries.html,,binaries} for information about obtaining
++precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
++to build the Ada language as it can't be bootstrapped using C@. Ada is
++only available for the 32-bit PA-RISC runtime.
++
++Starting with GCC 3.4 an ISO C compiler is required to bootstrap. The
++bundled compiler supports only traditional C; you will need either HP's
++unbundled compiler, or a binary distribution of GCC@.
++
++It is possible to build GCC 3.3 starting with the bundled HP compiler,
++but the process requires several steps. GCC 3.3 can then be used to
++build later versions. The fastjar program contains ISO C code and
++can't be built with the HP bundled compiler. This problem can be
++avoided by not building the Java language. For example, use the
++@option{--enable-languages="c,c++,f77,objc"} option in your configure
++command.
++
++There are several possible approaches to building the distribution.
++Binutils can be built first using the HP tools. Then, the GCC
++distribution can be built. The second approach is to build GCC
++first using the HP tools, then build binutils, then rebuild GCC@.
++There have been problems with various binary distributions, so it
++is best not to start from a binary distribution.
++
++On 64-bit capable systems, there are two distinct targets. Different
++installation prefixes must be used if both are to be installed on
++the same system. The @samp{hppa[1-2]*-hp-hpux11*} target generates code
++for the 32-bit PA-RISC runtime architecture and uses the HP linker.
++The @samp{hppa64-hp-hpux11*} target generates 64-bit code for the
++PA-RISC 2.0 architecture.
++
++The script config.guess now selects the target type based on the compiler
++detected during configuration. You must define @env{PATH} or @env{CC} so
++that configure finds an appropriate compiler for the initial bootstrap.
++When @env{CC} is used, the definition should contain the options that are
++needed whenever @env{CC} is used.
++
++Specifically, options that determine the runtime architecture must be
++in @env{CC} to correctly select the target for the build. It is also
++convenient to place many other compiler options in @env{CC}. For example,
++@env{CC="cc -Ac +DA2.0W -Wp,-H16376 -D_CLASSIC_TYPES -D_HPUX_SOURCE"}
++can be used to bootstrap the GCC 3.3 branch with the HP compiler in
++64-bit K&R/bundled mode. The @option{+DA2.0W} option will result in
++the automatic selection of the @samp{hppa64-hp-hpux11*} target. The
++macro definition table of cpp needs to be increased for a successful
++build with the HP compiler. _CLASSIC_TYPES and _HPUX_SOURCE need to
++be defined when building with the bundled compiler, or when using the
++@option{-Ac} option. These defines aren't necessary with @option{-Ae}.
++
++It is best to explicitly configure the @samp{hppa64-hp-hpux11*} target
++with the @option{--with-ld=@dots{}} option. This overrides the standard
++search for ld. The two linkers supported on this target require different
++commands. The default linker is determined during configuration. As a
++result, it's not possible to switch linkers in the middle of a GCC build.
++This has been reported to sometimes occur in unified builds of binutils
++and GCC@.
++
++A recent linker patch must be installed for the correct operation of
++GCC 3.3 and later. @code{PHSS_26559} and @code{PHSS_24304} are the
++oldest linker patches that are known to work. They are for HP-UX
++11.00 and 11.11, respectively. @code{PHSS_24303}, the companion to
++@code{PHSS_24304}, might be usable but it hasn't been tested. These
++patches have been superseded. Consult the HP patch database to obtain
++the currently recommended linker patch for your system.
++
++The patches are necessary for the support of weak symbols on the
++32-bit port, and for the running of initializers and finalizers. Weak
++symbols are implemented using SOM secondary definition symbols. Prior
++to HP-UX 11, there are bugs in the linker support for secondary symbols.
++The patches correct a problem of linker core dumps creating shared
++libraries containing secondary symbols, as well as various other
++linking issues involving secondary symbols.
++
++GCC 3.3 uses the ELF DT_INIT_ARRAY and DT_FINI_ARRAY capabilities to
++run initializers and finalizers on the 64-bit port. The 32-bit port
++uses the linker @option{+init} and @option{+fini} options for the same
++purpose. The patches correct various problems with the +init/+fini
++options, including program core dumps. Binutils 2.14 corrects a
++problem on the 64-bit port resulting from HP's non-standard use of
++the .init and .fini sections for array initializers and finalizers.
++
++Although the HP and GNU linkers are both supported for the
++@samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
++HP linker be used for link editing on this target.
++
++At this time, the GNU linker does not support the creation of long
++branch stubs. As a result, it can't successfully link binaries
++containing branch offsets larger than 8 megabytes. In addition,
++there are problems linking shared libraries, linking executables
++with @option{-static}, and with dwarf2 unwind and exception support.
++It also doesn't provide stubs for internal calls to global functions
++in shared libraries, so these calls can't be overloaded.
++
++The HP dynamic loader does not support GNU symbol versioning, so symbol
++versioning is not supported. It may be necessary to disable symbol
++versioning with @option{--disable-symvers} when using GNU ld.
++
++POSIX threads are the default. The optional DCE thread library is not
++supported, so @option{--enable-threads=dce} does not work.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-linux-gnu}*-*-linux-gnu
++
++Versions of libstdc++-v3 starting with 3.2.1 require bug fixes present
++in glibc 2.2.5 and later. More information is available in the
++libstdc++-v3 documentation.
++
++@html
++<hr />
++@end html
++@heading @anchor{ix86-x-linux}i?86-*-linux*
++
++As of GCC 3.3, binutils 2.13.1 or later is required for this platform.
++See @uref{http://gcc.gnu.org/PR10877,,bug 10877} for more information.
++
++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 @uref{http://www.bitwizard.nl/sig11/,,www.bitwizard.nl}.
++
++@html
++<hr />
++@end html
++@heading @anchor{ix86-x-solaris210}i?86-*-solaris2.10
++Use this for Solaris 10 or later on x86 and x86-64 systems. This
++configuration is supported by GCC 4.0 and later versions only.
++
++It is recommended that you configure GCC to use the GNU assembler in
++@file{/usr/sfw/bin/gas} but the Sun linker, using the options
++@option{--with-gnu-as --with-as=/usr/sfw/bin/gas --without-gnu-ld
++--with-ld=/usr/ccs/bin/ld}.
++
++@html
++<hr />
++@end html
++@heading @anchor{ia64-x-linux}ia64-*-linux
++IA-64 processor (also known as IPF, or Itanium Processor Family)
++running GNU/Linux.
++
++If you are using the installed system libunwind library with
++@option{--with-system-libunwind}, then you must use libunwind 0.98 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.1, 3.0.2, 3.0.1, 3.0, Red Hat 2.96, and Trillian 000717.
++This primarily affects C++ programs and programs that create shared libraries.
++GCC 3.1 or later is recommended for compiling linux, the kernel.
++As of version 3.1 GCC is believed to be fully ABI compliant, and hence no
++more major ABI changes are expected.
++
++@html
++<hr />
++@end html
++@heading @anchor{ia64-x-hpux}ia64-*-hpux*
++Building GCC on this target requires the GNU Assembler. The bundled HP
++assembler will not work. To prevent GCC from using the wrong assembler,
++the option @option{--with-gnu-as} may be necessary.
++
++The GCC libunwind library has not been ported to HPUX@. This means that for
++GCC versions 3.2.3 and earlier, @option{--enable-libunwind-exceptions}
++is required to build GCC@. For GCC 3.3 and later, this is the default.
++For gcc 3.4.3 and later, @option{--enable-libunwind-exceptions} is
++removed and the system libunwind library will always be used.
++
++@html
++<hr />
++<!-- rs6000-ibm-aix*, powerpc-ibm-aix* -->
++@end html
++@heading @anchor{x-ibm-aix}*-ibm-aix*
++Support for AIX version 3 and older was discontinued in GCC 3.4.
++
++``out of memory'' bootstrap failures may indicate a problem with
++process resource limits (ulimit). Hard limits are configured in the
++@file{/etc/security/limits} system configuration file.
++
++To speed up the configuration phases of bootstrapping and installing GCC,
++one may use GNU Bash instead of AIX @command{/bin/sh}, e.g.,
++
++@smallexample
++ % CONFIG_SHELL=/opt/freeware/bin/bash
++ % export CONFIG_SHELL
++@end smallexample
++
++and then proceed as described in @uref{build.html,,the build
++instructions}, where we strongly recommend specifying an absolute path
++to invoke @var{srcdir}/configure.
++
++Because GCC on AIX is built as a 32-bit executable by default,
++(although it can generate 64-bit programs) the GMP and MPFR libraries
++required by gfortran must be 32-bit libraries. Building GMP and MPFR
++as static archive libraries works better than shared libraries.
++
++Errors involving @code{alloca} when building GCC generally are due
++to an incorrect definition of @code{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 @strong{must} be invoked as @command{cc}
++(not @command{xlc}). Once @command{configure} has been informed of
++@command{xlc}, one needs to use @samp{make distclean} to remove the
++configure cache files and ensure that @env{CC} environment variable
++does not provide a definition that will confuse @command{configure}.
++If this error occurs during stage2 or later, then the problem most likely
++is the version of Make (see above).
++
++The native @command{as} and @command{ld} are recommended for bootstrapping
++on AIX 4 and required for bootstrapping on AIX 5L@. The GNU Assembler
++reports that it supports WEAK symbols on AIX 4, which causes GCC to try to
++utilize weak symbol functionality although it is not supported. The GNU
++Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC@.
++The native AIX tools do interoperate with GCC@.
++
++Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
++APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
++fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
++referenced as APAR IY53606 (AIX 5.2) or a APAR IY54774 (AIX 5.1)
++
++@samp{libstdc++} in GCC 3.4 increments the major version number of the
++shared object and GCC installation places the @file{libstdc++.a}
++shared library in a common location which will overwrite the and GCC
++3.3 version of the shared library. Applications either need to be
++re-linked against the new shared library or the GCC 3.1 and GCC 3.3
++versions of the @samp{libstdc++} shared object needs to be available
++to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
++present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
++installed for runtime dynamic loading using the following steps to set
++the @samp{F_LOADONLY} flag in the shared object for @emph{each}
++multilib @file{libstdc++.a} installed:
++
++Extract the shared objects from the currently installed
++@file{libstdc++.a} archive:
++@smallexample
++ % ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
++@end smallexample
++
++Enable the @samp{F_LOADONLY} flag so that the shared object will be
++available for runtime dynamic loading, but not linking:
++@smallexample
++ % strip -e libstdc++.so.4 libstdc++.so.5
++@end smallexample
++
++Archive the runtime-only shared object in the GCC 3.4
++@file{libstdc++.a} archive:
++@smallexample
++ % ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
++@end smallexample
++
++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
++linking such as ``not a COFF file''. The version of the routines shipped
++with AIX 4.3.1 should work for a 32-bit environment. The @option{-g}
++option of the archive command may be used to create archives of 32-bit
++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 @option{-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 from its
++@uref{http://techsupport.services.ibm.com/,,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
++@uref{http://techsupport.services.ibm.com/,,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
++@uref{http://techsupport.services.ibm.com/,,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., @samp{.} vs @samp{,} for
++separating decimal fractions). There have been problems reported where
++GCC does not produce the same floating-point formats that the assembler
++expects. If one encounters this problem, set the @env{LANG}
++environment variable to @samp{C} or @samp{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 @option{-mcpu=@var{cpu_type}}
++switch and using the configure option @option{--with-cpu-@var{cpu_type}}.
++
++@html
++<hr />
++@end html
++@heading @anchor{iq2000-x-elf}iq2000-*-elf
++Vitesse IQ2000 processors. These are used in embedded
++applications. There are no standard Unix configurations.
++
++@html
++<hr />
++@end html
++@heading @anchor{m32c-x-elf}m32c-*-elf
++Renesas M32C processor.
++This configuration is intended for embedded systems.
++
++@html
++<hr />
++@end html
++@heading @anchor{m32r-x-elf}m32r-*-elf
++Renesas M32R processor.
++This configuration is intended for embedded systems.
++
++@html
++<hr />
++@end html
++@heading @anchor{m6811-elf}m6811-elf
++Motorola 68HC11 family micro controllers. These are used in embedded
++applications. There are no standard Unix configurations.
++
++@html
++<hr />
++@end html
++@heading @anchor{m6812-elf}m6812-elf
++Motorola 68HC12 family micro controllers. These are used in embedded
++applications. There are no standard Unix configurations.
++
++@html
++<hr />
++@end html
++@heading @anchor{m68k-x-x}m68k-*-*
++By default, @samp{m68k-*-aout}, @samp{m68k-*-coff*},
++@samp{m68k-*-elf*}, @samp{m68k-*-rtems}, @samp{m68k-*-uclinux} and
++@samp{m68k-*-linux}
++build libraries for both M680x0 and ColdFire processors. If you only
++need the M680x0 libraries, you can omit the ColdFire ones by passing
++@option{--with-arch=m68k} to @command{configure}. Alternatively, you
++can omit the M680x0 libraries by passing @option{--with-arch=cf} to
++@command{configure}. These targets default to 5206 or 5475 code as
++appropriate for the target system when
++configured with @option{--with-arch=cf} and 68020 code otherwise.
++
++The @samp{m68k-*-netbsd} and
++@samp{m68k-*-openbsd} targets also support the @option{--with-arch}
++option. They will generate ColdFire CFV4e code when configured with
++@option{--with-arch=cf} and 68020 code otherwise.
++
++You can override the default processors listed above by configuring
++with @option{--with-cpu=@var{target}}. This @var{target} can either
++be a @option{-mcpu} argument or one of the following values:
++@samp{m68000}, @samp{m68010}, @samp{m68020}, @samp{m68030},
++@samp{m68040}, @samp{m68060}, @samp{m68020-40} and @samp{m68020-60}.
++
++@html
++<hr />
++@end html
++@heading @anchor{m68k-x-uclinux}m68k-*-uclinux
++GCC 4.3 changed the uClinux configuration so that it uses the
++@samp{m68k-linux-gnu} ABI rather than the @samp{m68k-elf} ABI.
++It also added improved support for C++ and flat shared libraries,
++both of which were ABI changes. However, you can still use the
++original ABI by configuring for @samp{m68k-uclinuxoldabi} or
++@samp{m68k-@var{vendor}-uclinuxoldabi}.
++
++@html
++<hr />
++@end html
++@heading @anchor{mips-x-x}mips-*-*
++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.
++
++The libstdc++ atomic locking routines for MIPS targets requires MIPS II
++and later. A patch went in just after the GCC 3.3 release to
++make @samp{mips*-*-*} use the generic implementation instead. You can also
++configure for @samp{mipsel-elf} as a workaround. The
++@samp{mips*-*-linux*} target continues to use the MIPS II routines. More
++work on this is expected in future releases.
++
++@c If you make --with-llsc the default for another target, please also
++@c update the description of the --with-llsc option.
++
++The built-in @code{__sync_*} functions are available on MIPS II and
++later systems and others that support the @samp{ll}, @samp{sc} and
++@samp{sync} instructions. This can be overridden by passing
++@option{--with-llsc} or @option{--without-llsc} when configuring GCC.
++Since the Linux kernel emulates these instructions if they are
++missing, the default for @samp{mips*-*-linux*} targets is
++@option{--with-llsc}. The @option{--with-llsc} and
++@option{--without-llsc} configure options may be overridden at compile
++time by passing the @option{-mllsc} or @option{-mno-llsc} options to
++the compiler.
++
++MIPS systems check for division by zero (unless
++@option{-mno-check-zero-division} is passed to the compiler) by
++generating either a conditional trap or a break instruction. Using
++trap results in smaller code, but is only supported on MIPS II and
++later. Also, some versions of the Linux kernel have a bug that
++prevents trap from generating the proper signal (@code{SIGFPE}). To enable
++the use of break, use the @option{--with-divide=breaks}
++@command{configure} option when configuring GCC@. The default is to
++use traps on systems that support them.
++
++Cross-compilers for the MIPS as target using the MIPS assembler
++currently do not work, because the auxiliary programs
++@file{mips-tdump.c} and @file{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.
++
++The assembler from GNU binutils 2.17 and earlier has a bug in the way
++it sorts relocations for REL targets (o32, o64, EABI). This can cause
++bad code to be generated for simple C++ programs. Also the linker
++from GNU binutils versions prior to 2.17 has a bug which causes the
++runtime linker stubs in very large programs, like @file{libgcj.so}, to
++be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
++made after Nov. 9, 2006) should be free from both of these problems.
++
++@html
++<hr />
++@end html
++@heading @anchor{mips-sgi-irix5}mips-sgi-irix5
++
++In order to compile GCC on an SGI running IRIX 5, the @samp{compiler_dev.hdr}
++subsystem must be installed from the IDO CD-ROM supplied by SGI@.
++It is also available for download from
++@uref{ftp://ftp.sgi.com/sgi/IRIX5.3/iris-development-option-5.3.tardist}.
++
++If you use the MIPS C compiler to bootstrap, it may be necessary
++to increase its table size for switch statements with the
++@option{-Wf,-XNg1500} option. If you use the @option{-O2}
++optimization option, you also need to use @option{-Olimit 3000}.
++
++To enable debugging under IRIX 5, you must use GNU binutils 2.15 or
++later, and use the @option{--with-gnu-ld} @command{configure} option
++when configuring GCC@. You need to use GNU @command{ar} and @command{nm},
++also distributed with GNU binutils.
++
++Some users have reported that @command{/bin/sh} will hang during bootstrap.
++This problem can be avoided by running the commands:
++
++@smallexample
++ % CONFIG_SHELL=/bin/ksh
++ % export CONFIG_SHELL
++@end smallexample
++
++before starting the build.
++
++@html
++<hr />
++@end html
++@heading @anchor{mips-sgi-irix6}mips-sgi-irix6
++
++If you are using SGI's MIPSpro @command{cc} as your bootstrap compiler, you must
++ensure that the N32 ABI is in use. To test this, compile a simple C
++file with @command{cc} and then run @command{file} on the
++resulting object file. The output should look like:
++
++@smallexample
++test.o: ELF N32 MSB @dots{}
++@end smallexample
++
++If you see:
++
++@smallexample
++test.o: ELF 32-bit MSB @dots{}
++@end smallexample
++
++or
++
++@smallexample
++test.o: ELF 64-bit MSB @dots{}
++@end smallexample
++
++then your version of @command{cc} uses the O32 or N64 ABI by default. You
++should set the environment variable @env{CC} to @samp{cc -n32}
++before configuring GCC@.
++
++If you want the resulting @command{gcc} to run on old 32-bit systems
++with the MIPS R4400 CPU, you need to ensure that only code for the @samp{mips3}
++instruction set architecture (ISA) is generated. While GCC 3.x does
++this correctly, both GCC 2.95 and SGI's MIPSpro @command{cc} may change
++the ISA depending on the machine where GCC is built. Using one of them
++as the bootstrap compiler may result in @samp{mips4} code, which won't run at
++all on @samp{mips3}-only systems. For the test program above, you should see:
++
++@smallexample
++test.o: ELF N32 MSB mips-3 @dots{}
++@end smallexample
++
++If you get:
++
++@smallexample
++test.o: ELF N32 MSB mips-4 @dots{}
++@end smallexample
++
++instead, you should set the environment variable @env{CC} to @samp{cc
++-n32 -mips3} or @samp{gcc -mips3} respectively before configuring GCC@.
++
++MIPSpro C 7.4 may cause bootstrap failures, due to a bug when inlining
++@code{memcmp}. Either add @code{-U__INLINE_INTRINSICS} to the @env{CC}
++environment variable as a workaround or upgrade to MIPSpro C 7.4.1m.
++
++GCC on IRIX 6 is usually built to support the N32, O32 and N64 ABIs. If
++you build GCC on a system that doesn't have the N64 libraries installed
++or cannot run 64-bit binaries,
++you need to configure with @option{--disable-multilib} so GCC doesn't
++try to use them. This will disable building the O32 libraries, too.
++Look for @file{/usr/lib64/libc.so.1} to see if you
++have the 64-bit libraries installed.
++
++To enable debugging for the O32 ABI, you must use GNU @command{as} from
++GNU binutils 2.15 or later. You may also use GNU @command{ld}, but
++this is not required and currently causes some problems with Ada.
++
++The @option{--enable-libgcj}
++option is disabled by default: IRIX 6 uses a very low default limit
++(20480) for the command line length. Although @command{libtool} contains a
++workaround for this problem, at least the N64 @samp{libgcj} is known not
++to build despite this, running into an internal error of the native
++@command{ld}. A sure fix is to increase this limit (@samp{ncargs}) to
++its maximum of 262144 bytes. If you have root access, you can use the
++@command{systune} command to do this.
++
++@code{wchar_t} support in @samp{libstdc++} is not available for old
++IRIX 6.5.x releases, @math{x < 19}. The problem cannot be autodetected
++and in order to build GCC for such targets you need to configure with
++@option{--disable-wchar_t}.
++
++See @uref{http://freeware.sgi.com/} for more
++information about using GCC on IRIX platforms.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-x}powerpc-*-*
++
++You can specify a default version for the @option{-mcpu=@var{cpu_type}}
++switch by using the configure option @option{--with-cpu-@var{cpu_type}}.
++
++You will need
++@uref{ftp://ftp.kernel.org/pub/linux/devel/binutils,,binutils 2.15}
++or newer for a working GCC@.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-darwin}powerpc-*-darwin*
++PowerPC running Darwin (Mac OS X kernel).
++
++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
++@uref{http://developer.apple.com/darwin/projects/compiler/} (free
++registration required).
++
++This version of GCC requires at least cctools-590.36. The
++cctools-590.36 package referenced from
++@uref{http://gcc.gnu.org/ml/gcc/2006-03/msg00507.html} will not work
++on systems older than 10.3.9 (aka darwin7.9.0).
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-elf}powerpc-*-elf
++PowerPC system in big endian mode, running System V.4.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-linux-gnu}powerpc*-*-linux-gnu*
++
++PowerPC system in big endian mode running Linux.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-netbsd}powerpc-*-netbsd*
++PowerPC system in big endian mode running NetBSD@.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-eabisim}powerpc-*-eabisim
++Embedded PowerPC system in big endian mode for use in running under the
++PSIM simulator.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpc-x-eabi}powerpc-*-eabi
++Embedded PowerPC system in big endian mode.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpcle-x-elf}powerpcle-*-elf
++PowerPC system in little endian mode, running System V.4.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpcle-x-eabisim}powerpcle-*-eabisim
++Embedded PowerPC system in little endian mode for use in running under
++the PSIM simulator.
++
++@html
++<hr />
++@end html
++@heading @anchor{powerpcle-x-eabi}powerpcle-*-eabi
++Embedded PowerPC system in little endian mode.
++
++@html
++<hr />
++@end html
++@heading @anchor{s390-x-linux}s390-*-linux*
++S/390 system running GNU/Linux for S/390@.
++
++@html
++<hr />
++@end html
++@heading @anchor{s390x-x-linux}s390x-*-linux*
++zSeries system (64-bit) running GNU/Linux for zSeries@.
++
++@html
++<hr />
++@end html
++@heading @anchor{s390x-ibm-tpf}s390x-ibm-tpf*
++zSeries system (64-bit) running TPF@. This platform is
++supported as cross-compilation target only.
++
++@html
++<hr />
++@end html
++@c Please use Solaris 2 to refer to all release of Solaris, starting
++@c with 2.0 until 2.6, 7, 8, etc. Solaris 1 was a marketing name for
++@c SunOS 4 releases which we don't use to avoid confusion. Solaris
++@c alone is too unspecific and must be avoided.
++@heading @anchor{x-x-solaris2}*-*-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 the
++@uref{binaries.html,,binaries page} for details.
++
++The Solaris 2 @command{/bin/sh} will often fail to configure
++@file{libstdc++-v3}, @file{boehm-gc} or @file{libjava}. We therefore
++recommend using the following initial sequence of commands
++
++@smallexample
++ % CONFIG_SHELL=/bin/ksh
++ % export CONFIG_SHELL
++@end smallexample
++
++and proceed as described in @uref{configure.html,,the configure instructions}.
++In addition we strongly recommend specifying an absolute path to invoke
++@var{srcdir}/configure.
++
++Solaris 2 comes with a number of optional OS packages. Some of these
++are needed to use GCC fully, namely @code{SUNWarc},
++@code{SUNWbtool}, @code{SUNWesu}, @code{SUNWhea}, @code{SUNWlibm},
++@code{SUNWsprot}, and @code{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 @command{pkginfo} command. To add an optional package, use the
++@command{pkgadd} command. For further details, see the Solaris 2
++documentation.
++
++Trying to use the linker and other tools in
++@file{/usr/ucb} to install GCC has been observed to cause trouble.
++For example, the linker may hang indefinitely. The fix is to remove
++@file{/usr/ucb} from your @env{PATH}.
++
++The build process works more smoothly with the legacy Sun tools so, if you
++have @file{/usr/xpg4/bin} in your @env{PATH}, we recommend that you place
++@file{/usr/bin} before @file{/usr/xpg4/bin} for the duration of the build.
++
++We recommend the use of GNU binutils 2.14 or later, or the vendor tools
++(Sun @command{as}, Sun @command{ld}). Note that your mileage may vary
++if you use a combination of the GNU tools and the Sun tools: while the
++combination GNU @command{as} + Sun @command{ld} should reasonably work,
++the reverse combination Sun @command{as} + GNU @command{ld} is known to
++cause memory corruption at runtime in some cases for C++ programs.
++
++The stock GNU binutils 2.15 release is broken on this platform because of a
++single bug. It has been fixed on the 2.15 branch in the CVS repository.
++You can obtain a working version by checking out the binutils-2_15-branch
++from the CVS repository or applying the patch
++@uref{http://sourceware.org/ml/binutils-cvs/2004-09/msg00036.html} to the
++release.
++
++We recommend the use of GNU binutils 2.16 or later in conjunction with GCC
++4.x, or the vendor tools (Sun @command{as}, Sun @command{ld}). However,
++for Solaris 10 and above, an additional patch is required in order for the
++GNU linker to be able to cope with a new flavor of shared libraries. You
++can obtain a working version by checking out the binutils-2_16-branch from
++the CVS repository or applying the patch
++@uref{http://sourceware.org/ml/binutils-cvs/2005-07/msg00122.html} to the
++release.
++
++Sun bug 4296832 turns up when compiling X11 headers with GCC 2.95 or
++newer: @command{g++} will complain that types are missing. These headers
++assume that omitting the type means @code{int}; this assumption worked for
++C89 but is wrong for C++, and is now wrong for C99 also.
++
++@command{g++} accepts such (invalid) constructs with the option
++@option{-fpermissive}; it will assume that any missing type is @code{int}
++(as defined by C89).
++
++There are patches for 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.
++
++Sun bug 4927647 sometimes causes random spurious testsuite failures
++related to missing diagnostic output. This bug doesn't affect GCC
++itself, rather it is a kernel bug triggered by the @command{expect}
++program which is used only by the GCC testsuite driver. When the bug
++causes the @command{expect} program to miss anticipated output, extra
++testsuite failures appear.
++
++There are patches for Solaris 8 (117350-12 or newer for SPARC,
++117351-12 or newer for Intel) and Solaris 9 (117171-11 or newer for
++SPARC, 117172-11 or newer for Intel) that address this problem.
++
++@html
++<hr />
++@end html
++@heading @anchor{sparc-sun-solaris2}sparc-sun-solaris2*
++
++When GCC is configured to use binutils 2.14 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.
++
++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 @option{-m64} option enables 64-bit code generation.
++However, if all you want is code tuned for the UltraSPARC CPU, you
++should try the @option{-mtune=ultrasparc} option instead, which produces
++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
++@option{--disable-multilib}, since we will not be able to build the
++64-bit target libraries.
++
++GCC 3.3 and GCC 3.4 trigger code generation bugs in earlier versions of
++the GNU compiler (especially GCC 3.0.x versions), which lead to the
++miscompilation of the stage1 compiler and the subsequent failure of the
++bootstrap process. A workaround is to use GCC 3.2.3 as an intermediary
++stage, i.e.@: to bootstrap that compiler with the base compiler and then
++use it to bootstrap the final compiler.
++
++GCC 3.4 triggers a code generation bug in versions 5.4 (Sun ONE Studio 7)
++and 5.5 (Sun ONE Studio 8) of the Sun compiler, which causes a bootstrap
++failure in form of a miscompilation of the stage1 compiler by the Sun
++compiler. This is Sun bug 4974440. This is fixed with patch 112760-07.
++
++GCC 3.4 changed the default debugging format from STABS to DWARF-2 for
++32-bit code on Solaris 7 and later. If you use the Sun assembler, this
++change apparently runs afoul of Sun bug 4910101 (which is referenced as
++a x86-only problem by Sun, probably because they do not use DWARF-2).
++A symptom of the problem is that you cannot compile C++ programs like
++@command{groff} 1.19.1 without getting messages similar to the following:
++
++@smallexample
++ld: warning: relocation error: R_SPARC_UA32: @dots{}
++ external symbolic relocation against non-allocatable section
++ .debug_info cannot be processed at runtime: relocation ignored.
++@end smallexample
++
++To work around this problem, compile with @option{-gstabs+} instead of
++plain @option{-g}.
++
++When configuring the GNU Multiple Precision Library (GMP) or the MPFR
++library on a Solaris 7 or later system, the canonical target triplet
++must be specified as the @command{build} parameter on the configure
++line. This triplet can be obtained by invoking ./config.guess in
++the toplevel source directory of GCC (and not that of GMP or MPFR).
++For example on a Solaris 7 system:
++
++@smallexample
++ % ./configure --build=sparc-sun-solaris2.7 --prefix=xxx
++@end smallexample
++
++@html
++<hr />
++@end html
++@heading @anchor{sparc-sun-solaris27}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:
++@itemize @bullet
++@item
++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.
++
++@item
++Copy the original, unpatched Solaris 7
++@command{/usr/ccs/bin/as} into
++@command{/usr/local/libexec/gcc/sparc-sun-solaris2.7/3.4/as},
++adjusting the latter name to fit your local conventions and software
++version numbers.
++
++@item
++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
++run code generated by GCC; it doesn't suffice to install it only on
++the hosts that run GCC itself. Second, Sun says that 106950-03 is
++only a partial fix for bug 4210064, but Sun doesn't know whether the
++partial fix is adequate for GCC@. Revision -08 or later should fix
++the bug. The current (as of 2004-05-23) revision is -24, and is included in
++the Solaris 7 Recommended Patch Cluster.
++@end itemize
++
++GCC 3.3 triggers a bug in version 5.0 Alpha 03/27/98 of the Sun assembler,
++which causes a bootstrap failure when linking the 64-bit shared version of
++libgcc. A typical error message is:
++
++@smallexample
++ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o:
++ symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned.
++@end smallexample
++
++This bug has been fixed in the final 5.0 version of the assembler.
++
++A similar problem was reported for version Sun WorkShop 6 99/08/18 of the
++Sun assembler, which causes a bootstrap failure with GCC 4.0.0:
++
++@smallexample
++ld: fatal: relocation error: R_SPARC_DISP32:
++ file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o:
++ symbol <unknown>: offset 0xfccd33ad is non-aligned
++@end smallexample
++
++This bug has been fixed in more recent revisions of the assembler.
++
++@html
++<hr />
++@end html
++@heading @anchor{sparc-x-linux}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 @code{sparc-*-*} targets.
++
++
++@html
++<hr />
++@end html
++@heading @anchor{sparc64-x-solaris2}sparc64-*-solaris2*
++
++When configuring the GNU Multiple Precision Library (GMP) or the
++MPFR library, the canonical target triplet must be specified as
++the @command{build} parameter on the configure line. For example
++on a Solaris 7 system:
++
++@smallexample
++ % ./configure --build=sparc64-sun-solaris2.7 --prefix=xxx
++@end smallexample
++
++The following compiler flags must be specified in the configure
++step in order to bootstrap this target with the Sun compiler:
++
++@smallexample
++ % CC="cc -xarch=v9 -xildoff" @var{srcdir}/configure [@var{options}] [@var{target}]
++@end smallexample
++
++@option{-xarch=v9} specifies the SPARC-V9 architecture to the Sun toolchain
++and @option{-xildoff} turns off the incremental linker.
++
++@html
++<hr />
++@end html
++@heading @anchor{sparcv9-x-solaris2}sparcv9-*-solaris2*
++
++This is a synonym for sparc64-*-solaris2*.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-vxworks}*-*-vxworks*
++Support for VxWorks is in flux. At present GCC supports @emph{only} the
++very recent VxWorks 5.5 (aka Tornado 2.2) release, and only on PowerPC@.
++We welcome patches for other architectures supported by VxWorks 5.5.
++Support for VxWorks AE would also be welcome; we believe this is merely
++a matter of writing an appropriate ``configlette'' (see below). We are
++not interested in supporting older, a.out or COFF-based, versions of
++VxWorks in GCC 3.
++
++VxWorks comes with an older version of GCC installed in
++@file{@var{$WIND_BASE}/host}; we recommend you do not overwrite it.
++Choose an installation @var{prefix} entirely outside @var{$WIND_BASE}.
++Before running @command{configure}, create the directories @file{@var{prefix}}
++and @file{@var{prefix}/bin}. Link or copy the appropriate assembler,
++linker, etc.@: into @file{@var{prefix}/bin}, and set your @var{PATH} to
++include that directory while running both @command{configure} and
++@command{make}.
++
++You must give @command{configure} the
++@option{--with-headers=@var{$WIND_BASE}/target/h} switch so that it can
++find the VxWorks system headers. Since VxWorks is a cross compilation
++target only, you must also specify @option{--target=@var{target}}.
++@command{configure} will attempt to create the directory
++@file{@var{prefix}/@var{target}/sys-include} and copy files into it;
++make sure the user running @command{configure} has sufficient privilege
++to do so.
++
++GCC's exception handling runtime requires a special ``configlette''
++module, @file{contrib/gthr_supp_vxw_5x.c}. Follow the instructions in
++that file to add the module to your kernel build. (Future versions of
++VxWorks will incorporate this module.)
++
++@html
++<hr />
++@end html
++@heading @anchor{x86-64-x-x}x86_64-*-*, amd64-*-*
++
++GCC supports the x86-64 architecture implemented by the AMD64 processor
++(amd64-*-* is an alias for x86_64-*-*) on GNU/Linux, FreeBSD and NetBSD@.
++On GNU/Linux the default is a bi-arch compiler which is able to generate
++both 64-bit x86-64 and 32-bit x86 code (via the @option{-m32} switch).
++
++@html
++<hr />
++@end html
++@heading @anchor{xtensa-x-elf}xtensa*-*-elf
++
++This target is intended for embedded Xtensa systems using the
++@samp{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 @file{include/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.
++
++@html
++<hr />
++@end html
++@heading @anchor{xtensa-x-linux}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
++@option{-fpic} or @option{-fPIC} options are used. In other
++respects, this target is the same as the
++@uref{#xtensa*-*-elf,,@samp{xtensa*-*-elf}} target.
++
++@html
++<hr />
++@end html
++@heading @anchor{windows}Microsoft Windows
++
++@subheading Intel 16-bit versions
++The 16-bit versions of Microsoft Windows, such as Windows 3.1, are not
++supported.
++
++However, the 32-bit port has limited support for Microsoft
++Windows 3.11 in the Win32s environment, as a target only. See below.
++
++@subheading Intel 32-bit versions
++
++The 32-bit versions of Windows, including Windows 95, Windows NT, Windows
++XP, and Windows Vista, are supported by several different target
++platforms. These targets differ in which Windows subsystem they target
++and which C libraries are used.
++
++@itemize
++@item Cygwin @uref{#x-x-cygwin,,*-*-cygwin}: Cygwin provides a user-space
++Linux API emulation layer in the Win32 subsystem.
++@item Interix @uref{#x-x-interix,,*-*-interix}: The Interix subsystem
++provides native support for POSIX.
++@item MinGW @uref{#x-x-mingw,,*-*-mingw}: MinGW is a native GCC port for
++the Win32 subsystem that provides a subset of POSIX.
++@item MKS i386-pc-mks: NuTCracker from MKS. See
++@uref{http://www.mkssoftware.com/} for more information.
++@end itemize
++
++@subheading Intel 64-bit versions
++
++GCC contains support for x86-64 using the mingw-w64
++runtime library, available from @uref{http://mingw-w64.sourceforge.net/}.
++This library should be used with the target triple x86_64-pc-mingw32.
++
++Presently Windows for Itanium is not supported.
++
++@subheading Windows CE
++
++Windows CE is supported as a target only on ARM (arm-wince-pe), Hitachi
++SuperH (sh-wince-pe), and MIPS (mips-wince-pe).
++
++@subheading Other Windows Platforms
++
++GCC no longer supports Windows NT on the Alpha or PowerPC.
++
++GCC no longer supports the Windows POSIX subsystem. However, it does
++support the Interix subsystem. See above.
++
++Old target names including *-*-winnt and *-*-windowsnt are no longer used.
++
++PW32 (i386-pc-pw32) support was never completed, and the project seems to
++be inactive. See @uref{http://pw32.sourceforge.net/} for more information.
++
++UWIN support has been removed due to a lack of maintenance.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-cygwin}*-*-cygwin
++
++Ports of GCC are included with the
++@uref{http://www.cygwin.com/,,Cygwin environment}.
++
++GCC will build under Cygwin without modification; it does not build
++with Microsoft's C++ compiler and there are no plans to make it do so.
++
++Cygwin can be compiled with i?86-pc-cygwin.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-interix}*-*-interix
++
++The Interix target is used by OpenNT, Interix, Services For UNIX (SFU),
++and Subsystem for UNIX-based Applications (SUA). Applications compiled
++with this target run in the Interix subsystem, which is separate from
++the Win32 subsystem. This target was last known to work in GCC 3.3.
++
++For more information, see @uref{http://www.interix.com/}.
++
++@html
++<hr />
++@end html
++@heading @anchor{x-x-mingw32}*-*-mingw32
++
++GCC will build with and support only MinGW runtime 3.12 and later.
++Earlier versions of headers are incompatible with the new default semantics
++of @code{extern inline} in @code{-std=c99} and @code{-std=gnu99} modes.
++
++@html
++<hr />
++@end html
++@heading @anchor{os2}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 @uref{http://www.goof.com/pcg/os2/,,http://www.goof.com/pcg/os2/}.
++
++@html
++<hr />
++@end html
++@heading @anchor{older}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.
++
++Starting with GCC 3.1, each release has a list of ``obsoleted'' systems.
++Support for these systems is still present in that release, but
++@command{configure} will fail unless the @option{--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 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
++require first installing an old version of GCC which did work on that
++system, and using it to compile a more recent GCC, to avoid bugs in the
++vendor compiler. Old releases of GCC 1 and GCC 2 are available in the
++@file{old-releases} directory on the @uref{../mirrors.html,,GCC mirror
++sites}. Header bugs may generally be avoided using
++@command{fixincludes}, but bugs or deficiencies in libraries and the
++operating system may still cause problems.
++
++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
++version before they were removed), patches
++@uref{../contribute.html,,following the usual requirements} would be
++likely to be accepted, since they should not affect the support for more
++modern targets.
++
++For some systems, old versions of GNU binutils may also be useful,
++and are available from @file{pub/binutils/old-releases} on
++@uref{http://sourceware.org/mirrors.html,,sourceware.org 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.
++
++@html
++<hr />
++@end html
++@heading @anchor{elf}all ELF targets (SVR4, Solaris 2, etc.)
++
++C++ support is significantly better on ELF targets if you use the
++@uref{./configure.html#with-gnu-ld,,GNU linker}; duplicate copies of
++inlines, vtables and template instantiations will be discarded
++automatically.
++
++
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***Old documentation******************************************************
++@ifset oldhtml
++@include install-old.texi
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***GFDL********************************************************************
++@ifset gfdlhtml
++@include fdl.texi
++@html
++<hr />
++<p>
++@end html
++@ifhtml
++@uref{./index.html,,Return to the GCC Installation page}
++@end ifhtml
++@end ifset
++
++@c ***************************************************************************
++@c Part 6 The End of the Document
++@ifinfo
++@comment node-name, next, previous, up
++@node Concept Index, , GNU Free Documentation License, Top
++@end ifinfo
++
++@ifinfo
++@unnumbered Concept Index
++
++@printindex cp
++
++@contents
++@end ifinfo
++@bye
+diff -Naur gcc-4.4.2.orig/gcc/doc/invoke.texi gcc-4.4.2-rtems4.10-20091015/gcc/doc/invoke.texi
+--- gcc-4.4.2.orig/gcc/doc/invoke.texi 2009-09-18 23:53:23.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/gcc/doc/invoke.texi 2009-10-15 18:36:00.000000000 +0200
+@@ -606,6 +606,10 @@
+ -mno-sched-prefer-non-control-spec-insns @gol
+ -mno-sched-count-spec-in-critical-path}
+
++@emph{LM32 Options}
++@gccoptlist{-mbarrel-shift-enabled -mdivide-enabled -mmultiply-enabled @gol
++-msign-extend-enabled -muser-enabled}
++
+ @emph{M32R/D Options}
+ @gccoptlist{-m32r2 -m32rx -m32r @gol
+ -mdebug @gol
+@@ -8853,6 +8857,7 @@
+ * i386 and x86-64 Options::
+ * i386 and x86-64 Windows Options::
+ * IA-64 Options::
++* LM32 Options::
+ * M32C Options::
+ * M32R/D Options::
+ * M680x0 Options::
+@@ -11837,6 +11842,35 @@
+
+ @end table
+
++@node LM32 Options
++@subsection LM32 Options
++@cindex LM32 options
++
++These @option{-m} options are defined for the Lattice Mico32 architecture:
++
++@table @gcctabopt
++@item -mbarrel-shift-enabled
++@opindex mbarrel-shift-enabled
++Enable barrel-shift instructions.
++
++@item -mdivide-enabled
++@opindex mdivide-enabled
++Enable divide and modulus instructions.
++
++@item -mmultiply-enabled
++@opindex multiply-enabled
++Enable multiply instructions.
++
++@item -msign-extend-enabled
++@opindex msign-extend-enabled
++Enable sign extend instructions.
++
++@item -muser-enabled
++@opindex muser-enabled
++Enable user-defined instructions.
++
++@end table
++
+ @node M32R/D Options
+ @subsection M32R/D Options
+ @cindex M32R/D options
+diff -Naur gcc-4.4.2.orig/gcc/doc/invoke.texi.orig gcc-4.4.2-rtems4.10-20091015/gcc/doc/invoke.texi.orig
+--- gcc-4.4.2.orig/gcc/doc/invoke.texi.orig 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/gcc/doc/invoke.texi.orig 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,16649 @@
++@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
++@c 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
++@c Free Software Foundation, Inc.
++@c This is part of the GCC manual.
++@c For copying conditions, see the file gcc.texi.
++
++@ignore
++@c man begin INCLUDE
++@include gcc-vers.texi
++@c man end
++
++@c man begin COPYRIGHT
++Copyright @copyright{} 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
++1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
++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.2 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 gfdl(7) man page.
++
++(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.
++@c man end
++@c Set file name and title for the man page.
++@setfilename gcc
++@settitle GNU project C and C++ compiler
++@c man begin SYNOPSIS
++gcc [@option{-c}|@option{-S}|@option{-E}] [@option{-std=}@var{standard}]
++ [@option{-g}] [@option{-pg}] [@option{-O}@var{level}]
++ [@option{-W}@var{warn}@dots{}] [@option{-pedantic}]
++ [@option{-I}@var{dir}@dots{}] [@option{-L}@var{dir}@dots{}]
++ [@option{-D}@var{macro}[=@var{defn}]@dots{}] [@option{-U}@var{macro}]
++ [@option{-f}@var{option}@dots{}] [@option{-m}@var{machine-option}@dots{}]
++ [@option{-o} @var{outfile}] [@@@var{file}] @var{infile}@dots{}
++
++Only the most useful options are listed here; see below for the
++remainder. @samp{g++} accepts mostly the same options as @samp{gcc}.
++@c man end
++@c man begin SEEALSO
++gpl(7), gfdl(7), fsf-funding(7),
++cpp(1), gcov(1), as(1), ld(1), gdb(1), adb(1), dbx(1), sdb(1)
++and the Info entries for @file{gcc}, @file{cpp}, @file{as},
++@file{ld}, @file{binutils} and @file{gdb}.
++@c man end
++@c man begin BUGS
++For instructions on reporting bugs, see
++@w{@value{BUGURL}}.
++@c man end
++@c man begin AUTHOR
++See the Info entry for @command{gcc}, or
++@w{@uref{http://gcc.gnu.org/onlinedocs/gcc/Contributors.html}},
++for contributors to GCC@.
++@c man end
++@end ignore
++
++@node Invoking GCC
++@chapter GCC Command Options
++@cindex GCC command options
++@cindex command options
++@cindex options, GCC command
++
++@c man begin DESCRIPTION
++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 @option{-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.
++
++@cindex C compilation options
++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.
++
++@cindex C++ compilation options
++@xref{Invoking G++,,Compiling C++ Programs}, for a summary of special
++options for compiling C++ programs.
++
++@cindex grouping options
++@cindex options, grouping
++The @command{gcc} program accepts options and file names as operands. Many
++options have multi-letter names; therefore multiple single-letter options
++may @emph{not} be grouped: @option{-dv} is very different from @w{@samp{-d
++-v}}.
++
++@cindex order of options
++@cindex options, order
++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 @option{-L} more
++than once, the directories are searched in the order specified. Also,
++the placement of the @option{-l} option is significant.
++
++Many options have long names starting with @samp{-f} or with
++@samp{-W}---for example,
++@option{-fmove-loop-invariants}, @option{-Wformat} and so on. Most of
++these have both positive and negative forms; the negative form of
++@option{-ffoo} would be @option{-fno-foo}. This manual documents
++only one of these two forms, whichever one is not the default.
++
++@c man end
++
++@xref{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 and Objective-C++ Dialect Options:: Variations on Objective-C
++ and 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.
++* Precompiled Headers:: Compiling a header once, and using it many times.
++* Running Protoize:: Automatically adding or removing function prototypes.
++@end menu
++
++@c man begin OPTIONS
++
++@node Option Summary
++@section Option Summary
++
++Here is a summary of all the options, grouped by type. Explanations are
++in the following sections.
++
++@table @emph
++@item Overall Options
++@xref{Overall Options,,Options Controlling the Kind of Output}.
++@gccoptlist{-c -S -E -o @var{file} -combine -pipe -pass-exit-codes @gol
++-x @var{language} -v -### --help@r{[}=@var{class}@r{[},@dots{}@r{]]} --target-help @gol
++--version -wrapper@@@var{file}}
++
++@item C Language Options
++@xref{C Dialect Options,,Options Controlling C Dialect}.
++@gccoptlist{-ansi -std=@var{standard} -fgnu89-inline @gol
++-aux-info @var{filename} @gol
++-fno-asm -fno-builtin -fno-builtin-@var{function} @gol
++-fhosted -ffreestanding -fopenmp -fms-extensions @gol
++-trigraphs -no-integrated-cpp -traditional -traditional-cpp @gol
++-fallow-single-precision -fcond-mismatch -flax-vector-conversions @gol
++-fsigned-bitfields -fsigned-char @gol
++-funsigned-bitfields -funsigned-char}
++
++@item C++ Language Options
++@xref{C++ Dialect Options,,Options Controlling C++ Dialect}.
++@gccoptlist{-fabi-version=@var{n} -fno-access-control -fcheck-new @gol
++-fconserve-space -ffriend-injection @gol
++-fno-elide-constructors @gol
++-fno-enforce-eh-specs @gol
++-ffor-scope -fno-for-scope -fno-gnu-keywords @gol
++-fno-implicit-templates @gol
++-fno-implicit-inline-templates @gol
++-fno-implement-inlines -fms-extensions @gol
++-fno-nonansi-builtins -fno-operator-names @gol
++-fno-optional-diags -fpermissive @gol
++-frepo -fno-rtti -fstats -ftemplate-depth-@var{n} @gol
++-fno-threadsafe-statics -fuse-cxa-atexit -fno-weak -nostdinc++ @gol
++-fno-default-inline -fvisibility-inlines-hidden @gol
++-fvisibility-ms-compat @gol
++-Wabi -Wctor-dtor-privacy @gol
++-Wnon-virtual-dtor -Wreorder @gol
++-Weffc++ -Wstrict-null-sentinel @gol
++-Wno-non-template-friend -Wold-style-cast @gol
++-Woverloaded-virtual -Wno-pmf-conversions @gol
++-Wsign-promo}
++
++@item Objective-C and Objective-C++ Language Options
++@xref{Objective-C and Objective-C++ Dialect Options,,Options Controlling
++Objective-C and Objective-C++ Dialects}.
++@gccoptlist{-fconstant-string-class=@var{class-name} @gol
++-fgnu-runtime -fnext-runtime @gol
++-fno-nil-receivers @gol
++-fobjc-call-cxx-cdtors @gol
++-fobjc-direct-dispatch @gol
++-fobjc-exceptions @gol
++-fobjc-gc @gol
++-freplace-objc-classes @gol
++-fzero-link @gol
++-gen-decls @gol
++-Wassign-intercept @gol
++-Wno-protocol -Wselector @gol
++-Wstrict-selector-match @gol
++-Wundeclared-selector}
++
++@item Language Independent Options
++@xref{Language Independent Options,,Options to Control Diagnostic Messages Formatting}.
++@gccoptlist{-fmessage-length=@var{n} @gol
++-fdiagnostics-show-location=@r{[}once@r{|}every-line@r{]} @gol
++-fdiagnostics-show-option}
++
++@item Warning Options
++@xref{Warning Options,,Options to Request or Suppress Warnings}.
++@gccoptlist{-fsyntax-only -pedantic -pedantic-errors @gol
++-w -Wextra -Wall -Waddress -Waggregate-return -Warray-bounds @gol
++-Wno-attributes -Wno-builtin-macro-redefined @gol
++-Wc++-compat -Wc++0x-compat -Wcast-align -Wcast-qual @gol
++-Wchar-subscripts -Wclobbered -Wcomment @gol
++-Wconversion -Wcoverage-mismatch -Wno-deprecated @gol
++-Wno-deprecated-declarations -Wdisabled-optimization @gol
++-Wno-div-by-zero -Wempty-body -Wenum-compare -Wno-endif-labels @gol
++-Werror -Werror=* @gol
++-Wfatal-errors -Wfloat-equal -Wformat -Wformat=2 @gol
++-Wno-format-contains-nul -Wno-format-extra-args -Wformat-nonliteral @gol
++-Wformat-security -Wformat-y2k @gol
++-Wframe-larger-than=@var{len} -Wignored-qualifiers @gol
++-Wimplicit -Wimplicit-function-declaration -Wimplicit-int @gol
++-Winit-self -Winline @gol
++-Wno-int-to-pointer-cast -Wno-invalid-offsetof @gol
++-Winvalid-pch -Wlarger-than=@var{len} -Wunsafe-loop-optimizations @gol
++-Wlogical-op -Wlong-long @gol
++-Wmain -Wmissing-braces -Wmissing-field-initializers @gol
++-Wmissing-format-attribute -Wmissing-include-dirs @gol
++-Wmissing-noreturn -Wno-mudflap @gol
++-Wno-multichar -Wnonnull -Wno-overflow @gol
++-Woverlength-strings -Wpacked -Wpacked-bitfield-compat -Wpadded @gol
++-Wparentheses -Wpedantic-ms-format -Wno-pedantic-ms-format @gol
++-Wpointer-arith -Wno-pointer-to-int-cast @gol
++-Wredundant-decls @gol
++-Wreturn-type -Wsequence-point -Wshadow @gol
++-Wsign-compare -Wsign-conversion -Wstack-protector @gol
++-Wstrict-aliasing -Wstrict-aliasing=n @gol
++-Wstrict-overflow -Wstrict-overflow=@var{n} @gol
++-Wswitch -Wswitch-default -Wswitch-enum -Wsync-nand @gol
++-Wsystem-headers -Wtrigraphs -Wtype-limits -Wundef -Wuninitialized @gol
++-Wunknown-pragmas -Wno-pragmas -Wunreachable-code @gol
++-Wunused -Wunused-function -Wunused-label -Wunused-parameter @gol
++-Wunused-value -Wunused-variable @gol
++-Wvariadic-macros -Wvla @gol
++-Wvolatile-register-var -Wwrite-strings}
++
++@item C and Objective-C-only Warning Options
++@gccoptlist{-Wbad-function-cast -Wmissing-declarations @gol
++-Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs @gol
++-Wold-style-declaration -Wold-style-definition @gol
++-Wstrict-prototypes -Wtraditional -Wtraditional-conversion @gol
++-Wdeclaration-after-statement -Wpointer-sign}
++
++@item Debugging Options
++@xref{Debugging Options,,Options for Debugging Your Program or GCC}.
++@gccoptlist{-d@var{letters} -dumpspecs -dumpmachine -dumpversion @gol
++-fdbg-cnt-list -fdbg-cnt=@var{counter-value-list} @gol
++-fdump-noaddr -fdump-unnumbered @gol
++-fdump-translation-unit@r{[}-@var{n}@r{]} @gol
++-fdump-class-hierarchy@r{[}-@var{n}@r{]} @gol
++-fdump-ipa-all -fdump-ipa-cgraph -fdump-ipa-inline @gol
++-fdump-statistics @gol
++-fdump-tree-all @gol
++-fdump-tree-original@r{[}-@var{n}@r{]} @gol
++-fdump-tree-optimized@r{[}-@var{n}@r{]} @gol
++-fdump-tree-cfg -fdump-tree-vcg -fdump-tree-alias @gol
++-fdump-tree-ch @gol
++-fdump-tree-ssa@r{[}-@var{n}@r{]} -fdump-tree-pre@r{[}-@var{n}@r{]} @gol
++-fdump-tree-ccp@r{[}-@var{n}@r{]} -fdump-tree-dce@r{[}-@var{n}@r{]} @gol
++-fdump-tree-gimple@r{[}-raw@r{]} -fdump-tree-mudflap@r{[}-@var{n}@r{]} @gol
++-fdump-tree-dom@r{[}-@var{n}@r{]} @gol
++-fdump-tree-dse@r{[}-@var{n}@r{]} @gol
++-fdump-tree-phiopt@r{[}-@var{n}@r{]} @gol
++-fdump-tree-forwprop@r{[}-@var{n}@r{]} @gol
++-fdump-tree-copyrename@r{[}-@var{n}@r{]} @gol
++-fdump-tree-nrv -fdump-tree-vect @gol
++-fdump-tree-sink @gol
++-fdump-tree-sra@r{[}-@var{n}@r{]} @gol
++-fdump-tree-fre@r{[}-@var{n}@r{]} @gol
++-fdump-tree-vrp@r{[}-@var{n}@r{]} @gol
++-ftree-vectorizer-verbose=@var{n} @gol
++-fdump-tree-storeccp@r{[}-@var{n}@r{]} @gol
++-feliminate-dwarf2-dups -feliminate-unused-debug-types @gol
++-feliminate-unused-debug-symbols -femit-class-debug-always @gol
++-fmem-report -fpre-ipa-mem-report -fpost-ipa-mem-report -fprofile-arcs @gol
++-frandom-seed=@var{string} -fsched-verbose=@var{n} @gol
++-fsel-sched-verbose -fsel-sched-dump-cfg -fsel-sched-pipelining-verbose @gol
++-ftest-coverage -ftime-report -fvar-tracking @gol
++-g -g@var{level} -gcoff -gdwarf-2 @gol
++-ggdb -gstabs -gstabs+ -gvms -gxcoff -gxcoff+ @gol
++-fno-merge-debug-strings -fno-dwarf2-cfi-asm @gol
++-fdebug-prefix-map=@var{old}=@var{new} @gol
++-femit-struct-debug-baseonly -femit-struct-debug-reduced @gol
++-femit-struct-debug-detailed@r{[}=@var{spec-list}@r{]} @gol
++-p -pg -print-file-name=@var{library} -print-libgcc-file-name @gol
++-print-multi-directory -print-multi-lib @gol
++-print-prog-name=@var{program} -print-search-dirs -Q @gol
++-print-sysroot -print-sysroot-headers-suffix @gol
++-save-temps -time}
++
++@item Optimization Options
++@xref{Optimize Options,,Options that Control Optimization}.
++@gccoptlist{
++-falign-functions[=@var{n}] -falign-jumps[=@var{n}] @gol
++-falign-labels[=@var{n}] -falign-loops[=@var{n}] -fassociative-math @gol
++-fauto-inc-dec -fbranch-probabilities -fbranch-target-load-optimize @gol
++-fbranch-target-load-optimize2 -fbtr-bb-exclusive -fcaller-saves @gol
++-fcheck-data-deps -fconserve-stack -fcprop-registers -fcrossjumping @gol
++-fcse-follow-jumps -fcse-skip-blocks -fcx-fortran-rules -fcx-limited-range @gol
++-fdata-sections -fdce -fdce @gol
++-fdelayed-branch -fdelete-null-pointer-checks -fdse -fdse @gol
++-fearly-inlining -fexpensive-optimizations -ffast-math @gol
++-ffinite-math-only -ffloat-store -fforward-propagate @gol
++-ffunction-sections -fgcse -fgcse-after-reload -fgcse-las -fgcse-lm @gol
++-fgcse-sm -fif-conversion -fif-conversion2 -findirect-inlining @gol
++-finline-functions -finline-functions-called-once -finline-limit=@var{n} @gol
++-finline-small-functions -fipa-cp -fipa-cp-clone -fipa-matrix-reorg -fipa-pta @gol
++-fipa-pure-const -fipa-reference -fipa-struct-reorg @gol
++-fipa-type-escape -fira-algorithm=@var{algorithm} @gol
++-fira-region=@var{region} -fira-coalesce -fno-ira-share-save-slots @gol
++-fno-ira-share-spill-slots -fira-verbose=@var{n} @gol
++-fivopts -fkeep-inline-functions -fkeep-static-consts @gol
++-floop-block -floop-interchange -floop-strip-mine @gol
++-fmerge-all-constants -fmerge-constants -fmodulo-sched @gol
++-fmodulo-sched-allow-regmoves -fmove-loop-invariants -fmudflap @gol
++-fmudflapir -fmudflapth -fno-branch-count-reg -fno-default-inline @gol
++-fno-defer-pop -fno-function-cse -fno-guess-branch-probability @gol
++-fno-inline -fno-math-errno -fno-peephole -fno-peephole2 @gol
++-fno-sched-interblock -fno-sched-spec -fno-signed-zeros @gol
++-fno-toplevel-reorder -fno-trapping-math -fno-zero-initialized-in-bss @gol
++-fomit-frame-pointer -foptimize-register-move -foptimize-sibling-calls @gol
++-fpeel-loops -fpredictive-commoning -fprefetch-loop-arrays @gol
++-fprofile-correction -fprofile-dir=@var{path} -fprofile-generate @gol
++-fprofile-generate=@var{path} @gol
++-fprofile-use -fprofile-use=@var{path} -fprofile-values @gol
++-freciprocal-math -fregmove -frename-registers -freorder-blocks @gol
++-freorder-blocks-and-partition -freorder-functions @gol
++-frerun-cse-after-loop -freschedule-modulo-scheduled-loops @gol
++-frounding-math -frtl-abstract-sequences -fsched2-use-superblocks @gol
++-fsched2-use-traces -fsched-spec-load -fsched-spec-load-dangerous @gol
++-fsched-stalled-insns-dep[=@var{n}] -fsched-stalled-insns[=@var{n}] @gol
++-fschedule-insns -fschedule-insns2 -fsection-anchors -fsee @gol
++-fselective-scheduling -fselective-scheduling2 @gol
++-fsel-sched-pipelining -fsel-sched-pipelining-outer-loops @gol
++-fsignaling-nans -fsingle-precision-constant -fsplit-ivs-in-unroller @gol
++-fsplit-wide-types -fstack-protector -fstack-protector-all @gol
++-fstrict-aliasing -fstrict-overflow -fthread-jumps -ftracer @gol
++-ftree-builtin-call-dce -ftree-ccp -ftree-ch -ftree-copy-prop @gol
++-ftree-copyrename -ftree-dce @gol
++-ftree-dominator-opts -ftree-dse -ftree-fre -ftree-loop-im @gol
++-ftree-loop-distribution @gol
++-ftree-loop-ivcanon -ftree-loop-linear -ftree-loop-optimize @gol
++-ftree-parallelize-loops=@var{n} -ftree-pre -ftree-reassoc @gol
++-ftree-sink -ftree-sra -ftree-switch-conversion @gol
++-ftree-ter -ftree-vect-loop-version -ftree-vectorize -ftree-vrp @gol
++-funit-at-a-time -funroll-all-loops -funroll-loops @gol
++-funsafe-loop-optimizations -funsafe-math-optimizations -funswitch-loops @gol
++-fvariable-expansion-in-unroller -fvect-cost-model -fvpt -fweb @gol
++-fwhole-program @gol
++--param @var{name}=@var{value}
++-O -O0 -O1 -O2 -O3 -Os}
++
++@item Preprocessor Options
++@xref{Preprocessor Options,,Options Controlling the Preprocessor}.
++@gccoptlist{-A@var{question}=@var{answer} @gol
++-A-@var{question}@r{[}=@var{answer}@r{]} @gol
++-C -dD -dI -dM -dN @gol
++-D@var{macro}@r{[}=@var{defn}@r{]} -E -H @gol
++-idirafter @var{dir} @gol
++-include @var{file} -imacros @var{file} @gol
++-iprefix @var{file} -iwithprefix @var{dir} @gol
++-iwithprefixbefore @var{dir} -isystem @var{dir} @gol
++-imultilib @var{dir} -isysroot @var{dir} @gol
++-M -MM -MF -MG -MP -MQ -MT -nostdinc @gol
++-P -fworking-directory -remap @gol
++-trigraphs -undef -U@var{macro} -Wp,@var{option} @gol
++-Xpreprocessor @var{option}}
++
++@item Assembler Option
++@xref{Assembler Options,,Passing Options to the Assembler}.
++@gccoptlist{-Wa,@var{option} -Xassembler @var{option}}
++
++@item Linker Options
++@xref{Link Options,,Options for Linking}.
++@gccoptlist{@var{object-file-name} -l@var{library} @gol
++-nostartfiles -nodefaultlibs -nostdlib -pie -rdynamic @gol
++-s -static -static-libgcc -shared -shared-libgcc -symbolic @gol
++-T @var{script} -Wl,@var{option} -Xlinker @var{option} @gol
++-u @var{symbol}}
++
++@item Directory Options
++@xref{Directory Options,,Options for Directory Search}.
++@gccoptlist{-B@var{prefix} -I@var{dir} -iquote@var{dir} -L@var{dir}
++-specs=@var{file} -I- --sysroot=@var{dir}}
++
++@item Target Options
++@c I wrote this xref this way to avoid overfull hbox. -- rms
++@xref{Target Options}.
++@gccoptlist{-V @var{version} -b @var{machine}}
++
++@item Machine Dependent Options
++@xref{Submodel Options,,Hardware Models and Configurations}.
++@c This list is ordered alphanumerically by subsection name.
++@c Try and put the significant identifier (CPU or system) first,
++@c so users have a clue at guessing where the ones they want will be.
++
++@emph{ARC Options}
++@gccoptlist{-EB -EL @gol
++-mmangle-cpu -mcpu=@var{cpu} -mtext=@var{text-section} @gol
++-mdata=@var{data-section} -mrodata=@var{readonly-data-section}}
++
++@emph{ARM Options}
++@gccoptlist{-mapcs-frame -mno-apcs-frame @gol
++-mabi=@var{name} @gol
++-mapcs-stack-check -mno-apcs-stack-check @gol
++-mapcs-float -mno-apcs-float @gol
++-mapcs-reentrant -mno-apcs-reentrant @gol
++-msched-prolog -mno-sched-prolog @gol
++-mlittle-endian -mbig-endian -mwords-little-endian @gol
++-mfloat-abi=@var{name} -msoft-float -mhard-float -mfpe @gol
++-mthumb-interwork -mno-thumb-interwork @gol
++-mcpu=@var{name} -march=@var{name} -mfpu=@var{name} @gol
++-mstructure-size-boundary=@var{n} @gol
++-mabort-on-noreturn @gol
++-mlong-calls -mno-long-calls @gol
++-msingle-pic-base -mno-single-pic-base @gol
++-mpic-register=@var{reg} @gol
++-mnop-fun-dllimport @gol
++-mcirrus-fix-invalid-insns -mno-cirrus-fix-invalid-insns @gol
++-mpoke-function-name @gol
++-mthumb -marm @gol
++-mtpcs-frame -mtpcs-leaf-frame @gol
++-mcaller-super-interworking -mcallee-super-interworking @gol
++-mtp=@var{name} @gol
++-mword-relocations @gol
++-mfix-cortex-m3-ldrd}
++
++@emph{AVR Options}
++@gccoptlist{-mmcu=@var{mcu} -msize -mno-interrupts @gol
++-mcall-prologues -mno-tablejump -mtiny-stack -mint8}
++
++@emph{Blackfin Options}
++@gccoptlist{-mcpu=@var{cpu}@r{[}-@var{sirevision}@r{]} @gol
++-msim -momit-leaf-frame-pointer -mno-omit-leaf-frame-pointer @gol
++-mspecld-anomaly -mno-specld-anomaly -mcsync-anomaly -mno-csync-anomaly @gol
++-mlow-64k -mno-low64k -mstack-check-l1 -mid-shared-library @gol
++-mno-id-shared-library -mshared-library-id=@var{n} @gol
++-mleaf-id-shared-library -mno-leaf-id-shared-library @gol
++-msep-data -mno-sep-data -mlong-calls -mno-long-calls @gol
++-mfast-fp -minline-plt -mmulticore -mcorea -mcoreb -msdram @gol
++-micplb}
++
++@emph{CRIS Options}
++@gccoptlist{-mcpu=@var{cpu} -march=@var{cpu} -mtune=@var{cpu} @gol
++-mmax-stack-frame=@var{n} -melinux-stacksize=@var{n} @gol
++-metrax4 -metrax100 -mpdebug -mcc-init -mno-side-effects @gol
++-mstack-align -mdata-align -mconst-align @gol
++-m32-bit -m16-bit -m8-bit -mno-prologue-epilogue -mno-gotplt @gol
++-melf -maout -melinux -mlinux -sim -sim2 @gol
++-mmul-bug-workaround -mno-mul-bug-workaround}
++
++@emph{CRX Options}
++@gccoptlist{-mmac -mpush-args}
++
++@emph{Darwin Options}
++@gccoptlist{-all_load -allowable_client -arch -arch_errors_fatal @gol
++-arch_only -bind_at_load -bundle -bundle_loader @gol
++-client_name -compatibility_version -current_version @gol
++-dead_strip @gol
++-dependency-file -dylib_file -dylinker_install_name @gol
++-dynamic -dynamiclib -exported_symbols_list @gol
++-filelist -flat_namespace -force_cpusubtype_ALL @gol
++-force_flat_namespace -headerpad_max_install_names @gol
++-iframework @gol
++-image_base -init -install_name -keep_private_externs @gol
++-multi_module -multiply_defined -multiply_defined_unused @gol
++-noall_load -no_dead_strip_inits_and_terms @gol
++-nofixprebinding -nomultidefs -noprebind -noseglinkedit @gol
++-pagezero_size -prebind -prebind_all_twolevel_modules @gol
++-private_bundle -read_only_relocs -sectalign @gol
++-sectobjectsymbols -whyload -seg1addr @gol
++-sectcreate -sectobjectsymbols -sectorder @gol
++-segaddr -segs_read_only_addr -segs_read_write_addr @gol
++-seg_addr_table -seg_addr_table_filename -seglinkedit @gol
++-segprot -segs_read_only_addr -segs_read_write_addr @gol
++-single_module -static -sub_library -sub_umbrella @gol
++-twolevel_namespace -umbrella -undefined @gol
++-unexported_symbols_list -weak_reference_mismatches @gol
++-whatsloaded -F -gused -gfull -mmacosx-version-min=@var{version} @gol
++-mkernel -mone-byte-bool}
++
++@emph{DEC Alpha Options}
++@gccoptlist{-mno-fp-regs -msoft-float -malpha-as -mgas @gol
++-mieee -mieee-with-inexact -mieee-conformant @gol
++-mfp-trap-mode=@var{mode} -mfp-rounding-mode=@var{mode} @gol
++-mtrap-precision=@var{mode} -mbuild-constants @gol
++-mcpu=@var{cpu-type} -mtune=@var{cpu-type} @gol
++-mbwx -mmax -mfix -mcix @gol
++-mfloat-vax -mfloat-ieee @gol
++-mexplicit-relocs -msmall-data -mlarge-data @gol
++-msmall-text -mlarge-text @gol
++-mmemory-latency=@var{time}}
++
++@emph{DEC Alpha/VMS Options}
++@gccoptlist{-mvms-return-codes}
++
++@emph{FR30 Options}
++@gccoptlist{-msmall-model -mno-lsim}
++
++@emph{FRV Options}
++@gccoptlist{-mgpr-32 -mgpr-64 -mfpr-32 -mfpr-64 @gol
++-mhard-float -msoft-float @gol
++-malloc-cc -mfixed-cc -mdword -mno-dword @gol
++-mdouble -mno-double @gol
++-mmedia -mno-media -mmuladd -mno-muladd @gol
++-mfdpic -minline-plt -mgprel-ro -multilib-library-pic @gol
++-mlinked-fp -mlong-calls -malign-labels @gol
++-mlibrary-pic -macc-4 -macc-8 @gol
++-mpack -mno-pack -mno-eflags -mcond-move -mno-cond-move @gol
++-moptimize-membar -mno-optimize-membar @gol
++-mscc -mno-scc -mcond-exec -mno-cond-exec @gol
++-mvliw-branch -mno-vliw-branch @gol
++-mmulti-cond-exec -mno-multi-cond-exec -mnested-cond-exec @gol
++-mno-nested-cond-exec -mtomcat-stats @gol
++-mTLS -mtls @gol
++-mcpu=@var{cpu}}
++
++@emph{GNU/Linux Options}
++@gccoptlist{-muclibc}
++
++@emph{H8/300 Options}
++@gccoptlist{-mrelax -mh -ms -mn -mint32 -malign-300}
++
++@emph{HPPA Options}
++@gccoptlist{-march=@var{architecture-type} @gol
++-mbig-switch -mdisable-fpregs -mdisable-indexing @gol
++-mfast-indirect-calls -mgas -mgnu-ld -mhp-ld @gol
++-mfixed-range=@var{register-range} @gol
++-mjump-in-delay -mlinker-opt -mlong-calls @gol
++-mlong-load-store -mno-big-switch -mno-disable-fpregs @gol
++-mno-disable-indexing -mno-fast-indirect-calls -mno-gas @gol
++-mno-jump-in-delay -mno-long-load-store @gol
++-mno-portable-runtime -mno-soft-float @gol
++-mno-space-regs -msoft-float -mpa-risc-1-0 @gol
++-mpa-risc-1-1 -mpa-risc-2-0 -mportable-runtime @gol
++-mschedule=@var{cpu-type} -mspace-regs -msio -mwsio @gol
++-munix=@var{unix-std} -nolibdld -static -threads}
++
++@emph{i386 and x86-64 Options}
++@gccoptlist{-mtune=@var{cpu-type} -march=@var{cpu-type} @gol
++-mfpmath=@var{unit} @gol
++-masm=@var{dialect} -mno-fancy-math-387 @gol
++-mno-fp-ret-in-387 -msoft-float @gol
++-mno-wide-multiply -mrtd -malign-double @gol
++-mpreferred-stack-boundary=@var{num}
++-mincoming-stack-boundary=@var{num}
++-mcld -mcx16 -msahf -mrecip @gol
++-mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -msse4 -mavx @gol
++-maes -mpclmul @gol
++-msse4a -m3dnow -mpopcnt -mabm -msse5 @gol
++-mthreads -mno-align-stringops -minline-all-stringops @gol
++-minline-stringops-dynamically -mstringop-strategy=@var{alg} @gol
++-mpush-args -maccumulate-outgoing-args -m128bit-long-double @gol
++-m96bit-long-double -mregparm=@var{num} -msseregparm @gol
++-mveclibabi=@var{type} -mpc32 -mpc64 -mpc80 -mstackrealign @gol
++-momit-leaf-frame-pointer -mno-red-zone -mno-tls-direct-seg-refs @gol
++-mcmodel=@var{code-model} @gol
++-m32 -m64 -mlarge-data-threshold=@var{num} @gol
++-mfused-madd -mno-fused-madd -msse2avx}
++
++@emph{IA-64 Options}
++@gccoptlist{-mbig-endian -mlittle-endian -mgnu-as -mgnu-ld -mno-pic @gol
++-mvolatile-asm-stop -mregister-names -mno-sdata @gol
++-mconstant-gp -mauto-pic -minline-float-divide-min-latency @gol
++-minline-float-divide-max-throughput @gol
++-minline-int-divide-min-latency @gol
++-minline-int-divide-max-throughput @gol
++-minline-sqrt-min-latency -minline-sqrt-max-throughput @gol
++-mno-dwarf2-asm -mearly-stop-bits @gol
++-mfixed-range=@var{register-range} -mtls-size=@var{tls-size} @gol
++-mtune=@var{cpu-type} -mt -pthread -milp32 -mlp64 @gol
++-mno-sched-br-data-spec -msched-ar-data-spec -mno-sched-control-spec @gol
++-msched-br-in-data-spec -msched-ar-in-data-spec -msched-in-control-spec @gol
++-msched-ldc -mno-sched-control-ldc -mno-sched-spec-verbose @gol
++-mno-sched-prefer-non-data-spec-insns @gol
++-mno-sched-prefer-non-control-spec-insns @gol
++-mno-sched-count-spec-in-critical-path}
++
++@emph{M32R/D Options}
++@gccoptlist{-m32r2 -m32rx -m32r @gol
++-mdebug @gol
++-malign-loops -mno-align-loops @gol
++-missue-rate=@var{number} @gol
++-mbranch-cost=@var{number} @gol
++-mmodel=@var{code-size-model-type} @gol
++-msdata=@var{sdata-type} @gol
++-mno-flush-func -mflush-func=@var{name} @gol
++-mno-flush-trap -mflush-trap=@var{number} @gol
++-G @var{num}}
++
++@emph{M32C Options}
++@gccoptlist{-mcpu=@var{cpu} -msim -memregs=@var{number}}
++
++@emph{M680x0 Options}
++@gccoptlist{-march=@var{arch} -mcpu=@var{cpu} -mtune=@var{tune}
++-m68000 -m68020 -m68020-40 -m68020-60 -m68030 -m68040 @gol
++-m68060 -mcpu32 -m5200 -m5206e -m528x -m5307 -m5407 @gol
++-mcfv4e -mbitfield -mno-bitfield -mc68000 -mc68020 @gol
++-mnobitfield -mrtd -mno-rtd -mdiv -mno-div -mshort @gol
++-mno-short -mhard-float -m68881 -msoft-float -mpcrel @gol
++-malign-int -mstrict-align -msep-data -mno-sep-data @gol
++-mshared-library-id=n -mid-shared-library -mno-id-shared-library @gol
++-mxgot -mno-xgot}
++
++@emph{M68hc1x Options}
++@gccoptlist{-m6811 -m6812 -m68hc11 -m68hc12 -m68hcs12 @gol
++-mauto-incdec -minmax -mlong-calls -mshort @gol
++-msoft-reg-count=@var{count}}
++
++@emph{MCore Options}
++@gccoptlist{-mhardlit -mno-hardlit -mdiv -mno-div -mrelax-immediates @gol
++-mno-relax-immediates -mwide-bitfields -mno-wide-bitfields @gol
++-m4byte-functions -mno-4byte-functions -mcallgraph-data @gol
++-mno-callgraph-data -mslow-bytes -mno-slow-bytes -mno-lsim @gol
++-mlittle-endian -mbig-endian -m210 -m340 -mstack-increment}
++
++@emph{MIPS Options}
++@gccoptlist{-EL -EB -march=@var{arch} -mtune=@var{arch} @gol
++-mips1 -mips2 -mips3 -mips4 -mips32 -mips32r2 @gol
++-mips64 -mips64r2 @gol
++-mips16 -mno-mips16 -mflip-mips16 @gol
++-minterlink-mips16 -mno-interlink-mips16 @gol
++-mabi=@var{abi} -mabicalls -mno-abicalls @gol
++-mshared -mno-shared -mplt -mno-plt -mxgot -mno-xgot @gol
++-mgp32 -mgp64 -mfp32 -mfp64 -mhard-float -msoft-float @gol
++-msingle-float -mdouble-float -mdsp -mno-dsp -mdspr2 -mno-dspr2 @gol
++-mfpu=@var{fpu-type} @gol
++-msmartmips -mno-smartmips @gol
++-mpaired-single -mno-paired-single -mdmx -mno-mdmx @gol
++-mips3d -mno-mips3d -mmt -mno-mt -mllsc -mno-llsc @gol
++-mlong64 -mlong32 -msym32 -mno-sym32 @gol
++-G@var{num} -mlocal-sdata -mno-local-sdata @gol
++-mextern-sdata -mno-extern-sdata -mgpopt -mno-gopt @gol
++-membedded-data -mno-embedded-data @gol
++-muninit-const-in-rodata -mno-uninit-const-in-rodata @gol
++-mcode-readable=@var{setting} @gol
++-msplit-addresses -mno-split-addresses @gol
++-mexplicit-relocs -mno-explicit-relocs @gol
++-mcheck-zero-division -mno-check-zero-division @gol
++-mdivide-traps -mdivide-breaks @gol
++-mmemcpy -mno-memcpy -mlong-calls -mno-long-calls @gol
++-mmad -mno-mad -mfused-madd -mno-fused-madd -nocpp @gol
++-mfix-r4000 -mno-fix-r4000 -mfix-r4400 -mno-fix-r4400 @gol
++-mfix-r10000 -mno-fix-r10000 -mfix-vr4120 -mno-fix-vr4120 @gol
++-mfix-vr4130 -mno-fix-vr4130 -mfix-sb1 -mno-fix-sb1 @gol
++-mflush-func=@var{func} -mno-flush-func @gol
++-mbranch-cost=@var{num} -mbranch-likely -mno-branch-likely @gol
++-mfp-exceptions -mno-fp-exceptions @gol
++-mvr4130-align -mno-vr4130-align}
++
++@emph{MMIX Options}
++@gccoptlist{-mlibfuncs -mno-libfuncs -mepsilon -mno-epsilon -mabi=gnu @gol
++-mabi=mmixware -mzero-extend -mknuthdiv -mtoplevel-symbols @gol
++-melf -mbranch-predict -mno-branch-predict -mbase-addresses @gol
++-mno-base-addresses -msingle-exit -mno-single-exit}
++
++@emph{MN10300 Options}
++@gccoptlist{-mmult-bug -mno-mult-bug @gol
++-mam33 -mno-am33 @gol
++-mam33-2 -mno-am33-2 @gol
++-mreturn-pointer-on-d0 @gol
++-mno-crt0 -mrelax}
++
++@emph{PDP-11 Options}
++@gccoptlist{-mfpu -msoft-float -mac0 -mno-ac0 -m40 -m45 -m10 @gol
++-mbcopy -mbcopy-builtin -mint32 -mno-int16 @gol
++-mint16 -mno-int32 -mfloat32 -mno-float64 @gol
++-mfloat64 -mno-float32 -mabshi -mno-abshi @gol
++-mbranch-expensive -mbranch-cheap @gol
++-msplit -mno-split -munix-asm -mdec-asm}
++
++@emph{picoChip Options}
++@gccoptlist{-mae=@var{ae_type} -mvliw-lookahead=@var{N}
++-msymbol-as-address -mno-inefficient-warnings}
++
++@emph{PowerPC Options}
++See RS/6000 and PowerPC Options.
++
++@emph{RS/6000 and PowerPC Options}
++@gccoptlist{-mcpu=@var{cpu-type} @gol
++-mtune=@var{cpu-type} @gol
++-mpower -mno-power -mpower2 -mno-power2 @gol
++-mpowerpc -mpowerpc64 -mno-powerpc @gol
++-maltivec -mno-altivec @gol
++-mpowerpc-gpopt -mno-powerpc-gpopt @gol
++-mpowerpc-gfxopt -mno-powerpc-gfxopt @gol
++-mmfcrf -mno-mfcrf -mpopcntb -mno-popcntb -mfprnd -mno-fprnd @gol
++-mcmpb -mno-cmpb -mmfpgpr -mno-mfpgpr -mhard-dfp -mno-hard-dfp @gol
++-mnew-mnemonics -mold-mnemonics @gol
++-mfull-toc -mminimal-toc -mno-fp-in-toc -mno-sum-in-toc @gol
++-m64 -m32 -mxl-compat -mno-xl-compat -mpe @gol
++-malign-power -malign-natural @gol
++-msoft-float -mhard-float -mmultiple -mno-multiple @gol
++-msingle-float -mdouble-float -msimple-fpu @gol
++-mstring -mno-string -mupdate -mno-update @gol
++-mavoid-indexed-addresses -mno-avoid-indexed-addresses @gol
++-mfused-madd -mno-fused-madd -mbit-align -mno-bit-align @gol
++-mstrict-align -mno-strict-align -mrelocatable @gol
++-mno-relocatable -mrelocatable-lib -mno-relocatable-lib @gol
++-mtoc -mno-toc -mlittle -mlittle-endian -mbig -mbig-endian @gol
++-mdynamic-no-pic -maltivec -mswdiv @gol
++-mprioritize-restricted-insns=@var{priority} @gol
++-msched-costly-dep=@var{dependence_type} @gol
++-minsert-sched-nops=@var{scheme} @gol
++-mcall-sysv -mcall-netbsd @gol
++-maix-struct-return -msvr4-struct-return @gol
++-mabi=@var{abi-type} -msecure-plt -mbss-plt @gol
++-misel -mno-isel @gol
++-misel=yes -misel=no @gol
++-mspe -mno-spe @gol
++-mspe=yes -mspe=no @gol
++-mpaired @gol
++-mgen-cell-microcode -mwarn-cell-microcode @gol
++-mvrsave -mno-vrsave @gol
++-mmulhw -mno-mulhw @gol
++-mdlmzb -mno-dlmzb @gol
++-mfloat-gprs=yes -mfloat-gprs=no -mfloat-gprs=single -mfloat-gprs=double @gol
++-mprototype -mno-prototype @gol
++-msim -mmvme -mads -myellowknife -memb -msdata @gol
++-msdata=@var{opt} -mvxworks -G @var{num} -pthread}
++
++@emph{S/390 and zSeries Options}
++@gccoptlist{-mtune=@var{cpu-type} -march=@var{cpu-type} @gol
++-mhard-float -msoft-float -mhard-dfp -mno-hard-dfp @gol
++-mlong-double-64 -mlong-double-128 @gol
++-mbackchain -mno-backchain -mpacked-stack -mno-packed-stack @gol
++-msmall-exec -mno-small-exec -mmvcle -mno-mvcle @gol
++-m64 -m31 -mdebug -mno-debug -mesa -mzarch @gol
++-mtpf-trace -mno-tpf-trace -mfused-madd -mno-fused-madd @gol
++-mwarn-framesize -mwarn-dynamicstack -mstack-size -mstack-guard}
++
++@emph{Score Options}
++@gccoptlist{-meb -mel @gol
++-mnhwloop @gol
++-muls @gol
++-mmac @gol
++-mscore5 -mscore5u -mscore7 -mscore7d}
++
++@emph{SH Options}
++@gccoptlist{-m1 -m2 -m2e -m3 -m3e @gol
++-m4-nofpu -m4-single-only -m4-single -m4 @gol
++-m4a-nofpu -m4a-single-only -m4a-single -m4a -m4al @gol
++-m5-64media -m5-64media-nofpu @gol
++-m5-32media -m5-32media-nofpu @gol
++-m5-compact -m5-compact-nofpu @gol
++-mb -ml -mdalign -mrelax @gol
++-mbigtable -mfmovd -mhitachi -mrenesas -mno-renesas -mnomacsave @gol
++-mieee -mbitops -misize -minline-ic_invalidate -mpadstruct -mspace @gol
++-mprefergot -musermode -multcost=@var{number} -mdiv=@var{strategy} @gol
++-mdivsi3_libfunc=@var{name} -mfixed-range=@var{register-range} @gol
++-madjust-unroll -mindexed-addressing -mgettrcost=@var{number} -mpt-fixed @gol
++-minvalid-symbols}
++
++@emph{SPARC Options}
++@gccoptlist{-mcpu=@var{cpu-type} @gol
++-mtune=@var{cpu-type} @gol
++-mcmodel=@var{code-model} @gol
++-m32 -m64 -mapp-regs -mno-app-regs @gol
++-mfaster-structs -mno-faster-structs @gol
++-mfpu -mno-fpu -mhard-float -msoft-float @gol
++-mhard-quad-float -msoft-quad-float @gol
++-mimpure-text -mno-impure-text -mlittle-endian @gol
++-mstack-bias -mno-stack-bias @gol
++-munaligned-doubles -mno-unaligned-doubles @gol
++-mv8plus -mno-v8plus -mvis -mno-vis
++-threads -pthreads -pthread}
++
++@emph{SPU Options}
++@gccoptlist{-mwarn-reloc -merror-reloc @gol
++-msafe-dma -munsafe-dma @gol
++-mbranch-hints @gol
++-msmall-mem -mlarge-mem -mstdmain @gol
++-mfixed-range=@var{register-range}}
++
++@emph{System V Options}
++@gccoptlist{-Qy -Qn -YP,@var{paths} -Ym,@var{dir}}
++
++@emph{V850 Options}
++@gccoptlist{-mlong-calls -mno-long-calls -mep -mno-ep @gol
++-mprolog-function -mno-prolog-function -mspace @gol
++-mtda=@var{n} -msda=@var{n} -mzda=@var{n} @gol
++-mapp-regs -mno-app-regs @gol
++-mdisable-callt -mno-disable-callt @gol
++-mv850e1 @gol
++-mv850e @gol
++-mv850 -mbig-switch}
++
++@emph{VAX Options}
++@gccoptlist{-mg -mgnu -munix}
++
++@emph{VxWorks Options}
++@gccoptlist{-mrtp -non-static -Bstatic -Bdynamic @gol
++-Xbind-lazy -Xbind-now}
++
++@emph{x86-64 Options}
++See i386 and x86-64 Options.
++
++@emph{i386 and x86-64 Windows Options}
++@gccoptlist{-mconsole -mcygwin -mno-cygwin -mdll
++-mnop-fun-dllimport -mthread -mwin32 -mwindows}
++
++@emph{Xstormy16 Options}
++@gccoptlist{-msim}
++
++@emph{Xtensa Options}
++@gccoptlist{-mconst16 -mno-const16 @gol
++-mfused-madd -mno-fused-madd @gol
++-mserialize-volatile -mno-serialize-volatile @gol
++-mtext-section-literals -mno-text-section-literals @gol
++-mtarget-align -mno-target-align @gol
++-mlongcalls -mno-longcalls}
++
++@emph{zSeries Options}
++See S/390 and zSeries Options.
++
++@item Code Generation Options
++@xref{Code Gen Options,,Options for Code Generation Conventions}.
++@gccoptlist{-fcall-saved-@var{reg} -fcall-used-@var{reg} @gol
++-ffixed-@var{reg} -fexceptions @gol
++-fnon-call-exceptions -funwind-tables @gol
++-fasynchronous-unwind-tables @gol
++-finhibit-size-directive -finstrument-functions @gol
++-finstrument-functions-exclude-function-list=@var{sym},@var{sym},@dots{} @gol
++-finstrument-functions-exclude-file-list=@var{file},@var{file},@dots{} @gol
++-fno-common -fno-ident @gol
++-fpcc-struct-return -fpic -fPIC -fpie -fPIE @gol
++-fno-jump-tables @gol
++-frecord-gcc-switches @gol
++-freg-struct-return -fshort-enums @gol
++-fshort-double -fshort-wchar @gol
++-fverbose-asm -fpack-struct[=@var{n}] -fstack-check @gol
++-fstack-limit-register=@var{reg} -fstack-limit-symbol=@var{sym} @gol
++-fno-stack-limit -fargument-alias -fargument-noalias @gol
++-fargument-noalias-global -fargument-noalias-anything @gol
++-fleading-underscore -ftls-model=@var{model} @gol
++-ftrapv -fwrapv -fbounds-check @gol
++-fvisibility}
++@end table
++
++@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 and Objective-C++ Dialect Options:: Variations on Objective-C
++ and 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.
++@end menu
++
++@node Overall Options
++@section Options Controlling the Kind of Output
++
++Compilation can involve up to four stages: preprocessing, compilation
++proper, assembly and linking, always in that order. GCC is capable of
++preprocessing and compiling several files either into several
++assembler input files, or into one assembler input file; then each
++assembler input file produces an object file, and linking combines all
++the object files (those newly compiled, and those specified as input)
++into an executable file.
++
++@cindex file name suffix
++For any given input file, the file name suffix determines what kind of
++compilation is done:
++
++@table @gcctabopt
++@item @var{file}.c
++C source code which must be preprocessed.
++
++@item @var{file}.i
++C source code which should not be preprocessed.
++
++@item @var{file}.ii
++C++ source code which should not be preprocessed.
++
++@item @var{file}.m
++Objective-C source code. Note that you must link with the @file{libobjc}
++library to make an Objective-C program work.
++
++@item @var{file}.mi
++Objective-C source code which should not be preprocessed.
++
++@item @var{file}.mm
++@itemx @var{file}.M
++Objective-C++ source code. Note that you must link with the @file{libobjc}
++library to make an Objective-C++ program work. Note that @samp{.M} refers
++to a literal capital M@.
++
++@item @var{file}.mii
++Objective-C++ source code which should not be preprocessed.
++
++@item @var{file}.h
++C, C++, Objective-C or Objective-C++ header file to be turned into a
++precompiled header.
++
++@item @var{file}.cc
++@itemx @var{file}.cp
++@itemx @var{file}.cxx
++@itemx @var{file}.cpp
++@itemx @var{file}.CPP
++@itemx @var{file}.c++
++@itemx @var{file}.C
++C++ source code which must be preprocessed. Note that in @samp{.cxx},
++the last two letters must both be literally @samp{x}. Likewise,
++@samp{.C} refers to a literal capital C@.
++
++@item @var{file}.mm
++@itemx @var{file}.M
++Objective-C++ source code which must be preprocessed.
++
++@item @var{file}.mii
++Objective-C++ source code which should not be preprocessed.
++
++@item @var{file}.hh
++@itemx @var{file}.H
++@itemx @var{file}.hp
++@itemx @var{file}.hxx
++@itemx @var{file}.hpp
++@itemx @var{file}.HPP
++@itemx @var{file}.h++
++@itemx @var{file}.tcc
++C++ header file to be turned into a precompiled header.
++
++@item @var{file}.f
++@itemx @var{file}.for
++@itemx @var{file}.ftn
++Fixed form Fortran source code which should not be preprocessed.
++
++@item @var{file}.F
++@itemx @var{file}.FOR
++@itemx @var{file}.fpp
++@itemx @var{file}.FPP
++@itemx @var{file}.FTN
++Fixed form Fortran source code which must be preprocessed (with the traditional
++preprocessor).
++
++@item @var{file}.f90
++@itemx @var{file}.f95
++@itemx @var{file}.f03
++@itemx @var{file}.f08
++Free form Fortran source code which should not be preprocessed.
++
++@item @var{file}.F90
++@itemx @var{file}.F95
++@itemx @var{file}.F03
++@itemx @var{file}.F08
++Free form Fortran source code which must be preprocessed (with the
++traditional preprocessor).
++
++@c FIXME: Descriptions of Java file types.
++@c @var{file}.java
++@c @var{file}.class
++@c @var{file}.zip
++@c @var{file}.jar
++
++@item @var{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 @dfn{specs}.
++
++@item @var{file}.adb
++Ada source code file containing a library unit body (a subprogram or
++package body). Such files are also called @dfn{bodies}.
++
++@c GCC also knows about some suffixes for languages not yet included:
++@c Pascal:
++@c @var{file}.p
++@c @var{file}.pas
++@c Ratfor:
++@c @var{file}.r
++
++@item @var{file}.s
++Assembler code.
++
++@item @var{file}.S
++@itemx @var{file}.sx
++Assembler code which must be preprocessed.
++
++@item @var{other}
++An object file to be fed straight into linking.
++Any file name with no recognized suffix is treated this way.
++@end table
++
++@opindex x
++You can specify the input language explicitly with the @option{-x} option:
++
++@table @gcctabopt
++@item -x @var{language}
++Specify explicitly the @var{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 @option{-x} option. Possible values for @var{language} are:
++@smallexample
++c c-header c-cpp-output
++c++ c++-header c++-cpp-output
++objective-c objective-c-header objective-c-cpp-output
++objective-c++ objective-c++-header objective-c++-cpp-output
++assembler assembler-with-cpp
++ada
++f77 f77-cpp-input f95 f95-cpp-input
++java
++@end smallexample
++
++@item -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 @option{-x}
++has not been used at all).
++
++@item -pass-exit-codes
++@opindex pass-exit-codes
++Normally the @command{gcc} program will exit with the code of 1 if any
++phase of the compiler returns a non-success return code. If you specify
++@option{-pass-exit-codes}, the @command{gcc} program will instead return with
++numerically highest error produced by any phase that returned an error
++indication. The C, C++, and Fortran frontends return 4, if an internal
++compiler error is encountered.
++@end table
++
++If you only want some of the stages of compilation, you can use
++@option{-x} (or filename suffixes) to tell @command{gcc} where to start, and
++one of the options @option{-c}, @option{-S}, or @option{-E} to say where
++@command{gcc} is to stop. Note that some combinations (for example,
++@samp{-x cpp-output -E}) instruct @command{gcc} to do nothing at all.
++
++@table @gcctabopt
++@item -c
++@opindex 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 @samp{.c}, @samp{.i}, @samp{.s}, etc., with @samp{.o}.
++
++Unrecognized input files, not requiring compilation or assembly, are
++ignored.
++
++@item -S
++@opindex 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 @samp{.c}, @samp{.i}, etc., with @samp{.s}.
++
++Input files that don't require compilation are ignored.
++
++@item -E
++@opindex 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.
++
++@cindex output file option
++@item -o @var{file}
++@opindex o
++Place output in file @var{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.
++
++If @option{-o} is not specified, the default is to put an executable
++file in @file{a.out}, the object file for
++@file{@var{source}.@var{suffix}} in @file{@var{source}.o}, its
++assembler file in @file{@var{source}.s}, a precompiled header file in
++@file{@var{source}.@var{suffix}.gch}, and all preprocessed C source on
++standard output.
++
++@item -v
++@opindex 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.
++
++@item -###
++@opindex ###
++Like @option{-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.
++
++@item -pipe
++@opindex 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.
++
++@item -combine
++@opindex combine
++If you are compiling multiple source files, this option tells the driver
++to pass all the source files to the compiler at once (for those
++languages for which the compiler can handle this). This will allow
++intermodule analysis (IMA) to be performed by the compiler. Currently the only
++language for which this is supported is C@. If you pass source files for
++multiple languages to the driver, using this option, the driver will invoke
++the compiler(s) that support IMA once each, passing each compiler all the
++source files appropriate for it. For those languages that do not support
++IMA this option will be ignored, and the compiler will be invoked once for
++each source file in that language. If you use this option in conjunction
++with @option{-save-temps}, the compiler will generate multiple
++pre-processed files
++(one for each source file), but only one (combined) @file{.o} or
++@file{.s} file.
++
++@item --help
++@opindex help
++Print (on the standard output) a description of the command line options
++understood by @command{gcc}. If the @option{-v} option is also specified
++then @option{--help} will also be passed on to the various processes
++invoked by @command{gcc}, so that they can display the command line options
++they accept. If the @option{-Wextra} option has also been specified
++(prior to the @option{--help} option), then command line options which
++have no documentation associated with them will also be displayed.
++
++@item --target-help
++@opindex target-help
++Print (on the standard output) a description of target-specific command
++line options for each tool. For some targets extra target-specific
++information may also be printed.
++
++@item --help=@{@var{class}@r{|[}^@r{]}@var{qualifier}@}@r{[},@dots{}@r{]}
++Print (on the standard output) a description of the command line
++options understood by the compiler that fit into all specified classes
++and qualifiers. These are the supported classes:
++
++@table @asis
++@item @samp{optimizers}
++This will display all of the optimization options supported by the
++compiler.
++
++@item @samp{warnings}
++This will display all of the options controlling warning messages
++produced by the compiler.
++
++@item @samp{target}
++This will display target-specific options. Unlike the
++@option{--target-help} option however, target-specific options of the
++linker and assembler will not be displayed. This is because those
++tools do not currently support the extended @option{--help=} syntax.
++
++@item @samp{params}
++This will display the values recognized by the @option{--param}
++option.
++
++@item @var{language}
++This will display the options supported for @var{language}, where
++@var{language} is the name of one of the languages supported in this
++version of GCC.
++
++@item @samp{common}
++This will display the options that are common to all languages.
++@end table
++
++These are the supported qualifiers:
++
++@table @asis
++@item @samp{undocumented}
++Display only those options which are undocumented.
++
++@item @samp{joined}
++Display options which take an argument that appears after an equal
++sign in the same continuous piece of text, such as:
++@samp{--help=target}.
++
++@item @samp{separate}
++Display options which take an argument that appears as a separate word
++following the original option, such as: @samp{-o output-file}.
++@end table
++
++Thus for example to display all the undocumented target-specific
++switches supported by the compiler the following can be used:
++
++@smallexample
++--help=target,undocumented
++@end smallexample
++
++The sense of a qualifier can be inverted by prefixing it with the
++@samp{^} character, so for example to display all binary warning
++options (i.e., ones that are either on or off and that do not take an
++argument), which have a description the following can be used:
++
++@smallexample
++--help=warnings,^joined,^undocumented
++@end smallexample
++
++The argument to @option{--help=} should not consist solely of inverted
++qualifiers.
++
++Combining several classes is possible, although this usually
++restricts the output by so much that there is nothing to display. One
++case where it does work however is when one of the classes is
++@var{target}. So for example to display all the target-specific
++optimization options the following can be used:
++
++@smallexample
++--help=target,optimizers
++@end smallexample
++
++The @option{--help=} option can be repeated on the command line. Each
++successive use will display its requested class of options, skipping
++those that have already been displayed.
++
++If the @option{-Q} option appears on the command line before the
++@option{--help=} option, then the descriptive text displayed by
++@option{--help=} is changed. Instead of describing the displayed
++options, an indication is given as to whether the option is enabled,
++disabled or set to a specific value (assuming that the compiler
++knows this at the point where the @option{--help=} option is used).
++
++Here is a truncated example from the ARM port of @command{gcc}:
++
++@smallexample
++ % gcc -Q -mabi=2 --help=target -c
++ The following options are target specific:
++ -mabi= 2
++ -mabort-on-noreturn [disabled]
++ -mapcs [disabled]
++@end smallexample
++
++The output is sensitive to the effects of previous command line
++options, so for example it is possible to find out which optimizations
++are enabled at @option{-O2} by using:
++
++@smallexample
++-Q -O2 --help=optimizers
++@end smallexample
++
++Alternatively you can discover which binary optimizations are enabled
++by @option{-O3} by using:
++
++@smallexample
++gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts
++gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts
++diff /tmp/O2-opts /tmp/O3-opts | grep enabled
++@end smallexample
++
++@item --version
++@opindex version
++Display the version number and copyrights of the invoked GCC@.
++
++@item -wrapper
++@opindex wrapper
++Invoke all subcommands under a wrapper program. It takes a single
++comma separated list as an argument, which will be used to invoke
++the wrapper:
++
++@smallexample
++gcc -c t.c -wrapper gdb,--args
++@end smallexample
++
++This will invoke all subprograms of gcc under "gdb --args",
++thus cc1 invocation will be "gdb --args cc1 ...".
++
++@include @value{srcdir}/../libiberty/at-file.texi
++@end table
++
++@node Invoking G++
++@section Compiling C++ Programs
++
++@cindex suffixes for C++ source
++@cindex C++ source file suffixes
++C++ source files conventionally use one of the suffixes @samp{.C},
++@samp{.cc}, @samp{.cpp}, @samp{.CPP}, @samp{.c++}, @samp{.cp}, or
++@samp{.cxx}; C++ header files often use @samp{.hh}, @samp{.hpp},
++@samp{.H}, or (for shared template code) @samp{.tcc}; and
++preprocessed C++ files use the suffix @samp{.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 @command{gcc}).
++
++@findex g++
++@findex c++
++However, the use of @command{gcc} does not add the C++ library.
++@command{g++} is a program that calls GCC and treats @samp{.c},
++@samp{.h} and @samp{.i} files as C++ source files instead of C source
++files unless @option{-x} is used, and automatically specifies linking
++against the C++ library. This program is also useful when
++precompiling a C header file with a @samp{.h} extension for use in C++
++compilations. On many systems, @command{g++} is also installed with
++the name @command{c++}.
++
++@cindex invoking @command{g++}
++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.
++@xref{C Dialect Options,,Options Controlling C Dialect}, for
++explanations of options for languages related to C@.
++@xref{C++ Dialect Options,,Options Controlling C++ Dialect}, for
++explanations of options that are meaningful only for C++ programs.
++
++@node C Dialect Options
++@section Options Controlling C Dialect
++@cindex dialect options
++@cindex language dialect options
++@cindex options, dialect
++
++The following options control the dialect of C (or languages derived
++from C, such as C++, Objective-C and Objective-C++) that the compiler
++accepts:
++
++@table @gcctabopt
++@cindex ANSI support
++@cindex ISO support
++@item -ansi
++@opindex ansi
++In C mode, this is equivalent to @samp{-std=c89}. In C++ mode, it is
++equivalent to @samp{-std=c++98}.
++
++This turns off certain features of GCC that are incompatible with ISO
++C90 (when compiling C code), or of standard C++ (when compiling C++ code),
++such as the @code{asm} and @code{typeof} keywords, and
++predefined macros such as @code{unix} and @code{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 @samp{//} comments as well as
++the @code{inline} keyword.
++
++The alternate keywords @code{__asm__}, @code{__extension__},
++@code{__inline__} and @code{__typeof__} continue to work despite
++@option{-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 @option{-ansi}. Alternate predefined macros
++such as @code{__unix__} and @code{__vax__} are also available, with or
++without @option{-ansi}.
++
++The @option{-ansi} option does not cause non-ISO programs to be
++rejected gratuitously. For that, @option{-pedantic} is required in
++addition to @option{-ansi}. @xref{Warning Options}.
++
++The macro @code{__STRICT_ANSI__} is predefined when the @option{-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 that would normally be built in but do not have semantics
++defined by ISO C (such as @code{alloca} and @code{ffs}) are not built-in
++functions when @option{-ansi} is used. @xref{Other Builtins,,Other
++built-in functions provided by GCC}, for details of the functions
++affected.
++
++@item -std=
++@opindex std
++Determine the language standard. @xref{Standards,,Language Standards
++Supported by GCC}, for details of these standard versions. This option
++is currently only supported when compiling C or C++.
++
++The compiler can accept several base standards, such as @samp{c89} or
++@samp{c++98}, and GNU dialects of those standards, such as
++@samp{gnu89} or @samp{gnu++98}. By specifying a base standard, the
++compiler will accept all programs following that standard and those
++using GNU extensions that do not contradict it. For example,
++@samp{-std=c89} turns off certain features of GCC that are
++incompatible with ISO C90, such as the @code{asm} and @code{typeof}
++keywords, but not other GNU extensions that do not have a meaning in
++ISO C90, such as omitting the middle term of a @code{?:}
++expression. On the other hand, by specifying a GNU dialect of a
++standard, all features the compiler support are enabled, even when
++those features change the meaning of the base standard and some
++strict-conforming programs may be rejected. The particular standard
++is used by @option{-pedantic} to identify which features are GNU
++extensions given that version of the standard. For example
++@samp{-std=gnu89 -pedantic} would warn about C++ style @samp{//}
++comments, while @samp{-std=gnu99 -pedantic} would not.
++
++A value for this option must be provided; possible values are
++
++@table @samp
++@item c89
++@itemx iso9899:1990
++Support all ISO C90 programs (certain GNU extensions that conflict
++with ISO C90 are disabled). Same as @option{-ansi} for C code.
++
++@item iso9899:199409
++ISO C90 as modified in amendment 1.
++
++@item c99
++@itemx c9x
++@itemx iso9899:1999
++@itemx iso9899:199x
++ISO C99. Note that this standard is not yet fully supported; see
++@w{@uref{http://gcc.gnu.org/gcc-4.4/c99status.html}} for more information. The
++names @samp{c9x} and @samp{iso9899:199x} are deprecated.
++
++@item gnu89
++GNU dialect of ISO C90 (including some C99 features). This
++is the default for C code.
++
++@item gnu99
++@itemx gnu9x
++GNU dialect of ISO C99. When ISO C99 is fully implemented in GCC,
++this will become the default. The name @samp{gnu9x} is deprecated.
++
++@item c++98
++The 1998 ISO C++ standard plus amendments. Same as @option{-ansi} for
++C++ code.
++
++@item gnu++98
++GNU dialect of @option{-std=c++98}. This is the default for
++C++ code.
++
++@item c++0x
++The working draft of the upcoming ISO C++0x standard. This option
++enables experimental features that are likely to be included in
++C++0x. The working draft is constantly changing, and any feature that is
++enabled by this flag may be removed from future versions of GCC if it is
++not part of the C++0x standard.
++
++@item gnu++0x
++GNU dialect of @option{-std=c++0x}. This option enables
++experimental features that may be removed in future versions of GCC.
++@end table
++
++@item -fgnu89-inline
++@opindex fgnu89-inline
++The option @option{-fgnu89-inline} tells GCC to use the traditional
++GNU semantics for @code{inline} functions when in C99 mode.
++@xref{Inline,,An Inline Function is As Fast As a Macro}. This option
++is accepted and ignored by GCC versions 4.1.3 up to but not including
++4.3. In GCC versions 4.3 and later it changes the behavior of GCC in
++C99 mode. Using this option is roughly equivalent to adding the
++@code{gnu_inline} function attribute to all inline functions
++(@pxref{Function Attributes}).
++
++The option @option{-fno-gnu89-inline} explicitly tells GCC to use the
++C99 semantics for @code{inline} when in C99 or gnu99 mode (i.e., it
++specifies the default behavior). This option was first supported in
++GCC 4.3. This option is not supported in C89 or gnu89 mode.
++
++The preprocessor macros @code{__GNUC_GNU_INLINE__} and
++@code{__GNUC_STDC_INLINE__} may be used to check which semantics are
++in effect for @code{inline} functions. @xref{Common Predefined
++Macros,,,cpp,The C Preprocessor}.
++
++@item -aux-info @var{filename}
++@opindex aux-info
++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 (@samp{I}, @samp{N} for new or
++@samp{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 (@samp{C} or @samp{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.
++
++@item -fno-asm
++@opindex fno-asm
++Do not recognize @code{asm}, @code{inline} or @code{typeof} as a
++keyword, so that code can use these words as identifiers. You can use
++the keywords @code{__asm__}, @code{__inline__} and @code{__typeof__}
++instead. @option{-ansi} implies @option{-fno-asm}.
++
++In C++, this switch only affects the @code{typeof} keyword, since
++@code{asm} and @code{inline} are standard keywords. You may want to
++use the @option{-fno-gnu-keywords} flag instead, which has the same
++effect. In C99 mode (@option{-std=c99} or @option{-std=gnu99}), this
++switch only affects the @code{asm} and @code{typeof} keywords, since
++@code{inline} is a standard keyword in ISO C99.
++
++@item -fno-builtin
++@itemx -fno-builtin-@var{function}
++@opindex fno-builtin
++@cindex built-in functions
++Don't recognize built-in functions that do not begin with
++@samp{__builtin_} as prefix. @xref{Other Builtins,,Other built-in
++functions provided by GCC}, for details of the functions affected,
++including those which are not built-in functions when @option{-ansi} or
++@option{-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 @code{alloca} may become single
++instructions that adjust the stack directly, and calls to @code{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 addition,
++when a function is recognized as a built-in function, GCC may use
++information about that function to warn about problems with calls to
++that function, or to generate more efficient code, even if the
++resulting code still contains calls to that function. For example,
++warnings are given with @option{-Wformat} for bad calls to
++@code{printf}, when @code{printf} is built in, and @code{strlen} is
++known not to modify global memory.
++
++With the @option{-fno-builtin-@var{function}} option
++only the built-in function @var{function} is
++disabled. @var{function} must not begin with @samp{__builtin_}. If a
++function is named that is not built-in in this version of GCC, this
++option is ignored. There is no corresponding
++@option{-fbuiltin-@var{function}} option; if you wish to enable
++built-in functions selectively when using @option{-fno-builtin} or
++@option{-ffreestanding}, you may define macros such as:
++
++@smallexample
++#define abs(n) __builtin_abs ((n))
++#define strcpy(d, s) __builtin_strcpy ((d), (s))
++@end smallexample
++
++@item -fhosted
++@opindex fhosted
++@cindex hosted environment
++
++Assert that compilation takes place in a hosted environment. This implies
++@option{-fbuiltin}. A hosted environment is one in which the
++entire standard library is available, and in which @code{main} has a return
++type of @code{int}. Examples are nearly everything except a kernel.
++This is equivalent to @option{-fno-freestanding}.
++
++@item -ffreestanding
++@opindex ffreestanding
++@cindex hosted environment
++
++Assert that compilation takes place in a freestanding environment. This
++implies @option{-fno-builtin}. A freestanding environment
++is one in which the standard library may not exist, and program startup may
++not necessarily be at @code{main}. The most obvious example is an OS kernel.
++This is equivalent to @option{-fno-hosted}.
++
++@xref{Standards,,Language Standards Supported by GCC}, for details of
++freestanding and hosted environments.
++
++@item -fopenmp
++@opindex fopenmp
++@cindex openmp parallel
++Enable handling of OpenMP directives @code{#pragma omp} in C/C++ and
++@code{!$omp} in Fortran. When @option{-fopenmp} is specified, the
++compiler generates parallel code according to the OpenMP Application
++Program Interface v2.5 @w{@uref{http://www.openmp.org/}}. This option
++implies @option{-pthread}, and thus is only supported on targets that
++have support for @option{-pthread}.
++
++@item -fms-extensions
++@opindex fms-extensions
++Accept some non-standard constructs used in Microsoft header files.
++
++Some cases of unnamed fields in structures and unions are only
++accepted with this option. @xref{Unnamed Fields,,Unnamed struct/union
++fields within structs/unions}, for details.
++
++@item -trigraphs
++@opindex trigraphs
++Support ISO C trigraphs. The @option{-ansi} option (and @option{-std}
++options for strict ISO C conformance) implies @option{-trigraphs}.
++
++@item -no-integrated-cpp
++@opindex no-integrated-cpp
++Performs a compilation in two passes: preprocessing and compiling. This
++option allows a user supplied "cc1", "cc1plus", or "cc1obj" via the
++@option{-B} option. The user supplied compilation step can then add in
++an additional preprocessing step after normal preprocessing but before
++compiling. The default is to use the integrated cpp (internal cpp)
++
++The semantics of this option will change if "cc1", "cc1plus", and
++"cc1obj" are merged.
++
++@cindex traditional C language
++@cindex C language, traditional
++@item -traditional
++@itemx -traditional-cpp
++@opindex traditional-cpp
++@opindex traditional
++Formerly, these options caused GCC to attempt to emulate a pre-standard
++C compiler. They are now only supported with the @option{-E} switch.
++The preprocessor continues to support a pre-standard mode. See the GNU
++CPP manual for details.
++
++@item -fcond-mismatch
++@opindex 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++.
++
++@item -flax-vector-conversions
++@opindex flax-vector-conversions
++Allow implicit conversions between vectors with differing numbers of
++elements and/or incompatible element types. This option should not be
++used for new code.
++
++@item -funsigned-char
++@opindex funsigned-char
++Let the type @code{char} be unsigned, like @code{unsigned char}.
++
++Each kind of machine has a default for what @code{char} should
++be. It is either like @code{unsigned char} by default or like
++@code{signed char} by default.
++
++Ideally, a portable program should always use @code{signed char} or
++@code{unsigned char} when it depends on the signedness of an object.
++But many programs have been written to use plain @code{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 @code{char} is always a distinct type from each of
++@code{signed char} or @code{unsigned char}, even though its behavior
++is always just like one of those two.
++
++@item -fsigned-char
++@opindex fsigned-char
++Let the type @code{char} be signed, like @code{signed char}.
++
++Note that this is equivalent to @option{-fno-unsigned-char}, which is
++the negative form of @option{-funsigned-char}. Likewise, the option
++@option{-fno-signed-char} is equivalent to @option{-funsigned-char}.
++
++@item -fsigned-bitfields
++@itemx -funsigned-bitfields
++@itemx -fno-signed-bitfields
++@itemx -fno-unsigned-bitfields
++@opindex fsigned-bitfields
++@opindex funsigned-bitfields
++@opindex fno-signed-bitfields
++@opindex fno-unsigned-bitfields
++These options control whether a bit-field is signed or unsigned, when the
++declaration does not use either @code{signed} or @code{unsigned}. By
++default, such a bit-field is signed, because this is consistent: the
++basic integer types such as @code{int} are signed types.
++@end table
++
++@node C++ Dialect Options
++@section Options Controlling C++ Dialect
++
++@cindex compiler options, C++
++@cindex C++ options, command line
++@cindex options, C++
++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 @code{firstClass.C} like this:
++
++@smallexample
++g++ -g -frepo -O -c firstClass.C
++@end smallexample
++
++@noindent
++In this example, only @option{-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 @emph{only} for compiling C++ programs:
++
++@table @gcctabopt
++
++@item -fabi-version=@var{n}
++@opindex fabi-version
++Use version @var{n} of the C++ ABI@. Version 2 is the version of the
++C++ ABI that first appeared in G++ 3.4. Version 1 is the version of
++the C++ ABI that first appeared in G++ 3.2. Version 0 will always be
++the version that conforms most closely to the C++ ABI specification.
++Therefore, the ABI obtained using version 0 will change as ABI bugs
++are fixed.
++
++The default is version 2.
++
++@item -fno-access-control
++@opindex fno-access-control
++Turn off all access checking. This switch is mainly useful for working
++around bugs in the access control code.
++
++@item -fcheck-new
++@opindex fcheck-new
++Check that the pointer returned by @code{operator new} is non-null
++before attempting to modify the storage allocated. This check is
++normally unnecessary because the C++ standard specifies that
++@code{operator new} will only return @code{0} if it is declared
++@samp{throw()}, in which case the compiler will always check the
++return value even without this option. In all other cases, when
++@code{operator new} has a non-empty exception specification, memory
++exhaustion is signalled by throwing @code{std::bad_alloc}. See also
++@samp{new (nothrow)}.
++
++@item -fconserve-space
++@opindex 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 @code{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.
++
++@item -fno-deduce-init-list
++@opindex fno-deduce-init-list
++Disable deduction of a template type parameter as
++std::initializer_list from a brace-enclosed initializer list, i.e.
++
++@smallexample
++template <class T> auto forward(T t) -> decltype (realfn (t))
++@{
++ return realfn (t);
++@}
++
++void f()
++@{
++ forward(@{1,2@}); // call forward<std::initializer_list<int>>
++@}
++@end smallexample
++
++This option is present because this deduction is an extension to the
++current specification in the C++0x working draft, and there was
++some concern about potential overload resolution problems.
++
++@item -ffriend-injection
++@opindex ffriend-injection
++Inject friend functions into the enclosing namespace, so that they are
++visible outside the scope of the class in which they are declared.
++Friend functions were documented to work this way in the old Annotated
++C++ Reference Manual, and versions of G++ before 4.1 always worked
++that way. However, in ISO C++ a friend function which is not declared
++in an enclosing scope can only be found using argument dependent
++lookup. This option causes friends to be injected as they were in
++earlier releases.
++
++This option is for compatibility, and may be removed in a future
++release of G++.
++
++@item -fno-elide-constructors
++@opindex 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.
++
++@item -fno-enforce-eh-specs
++@opindex fno-enforce-eh-specs
++Don't generate code to 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
++@samp{NDEBUG}. This does not give user code permission to throw
++exceptions in violation of the exception specifications; the compiler
++will still optimize based on the specifications, so throwing an
++unexpected exception will result in undefined behavior.
++
++@item -ffor-scope
++@itemx -fno-for-scope
++@opindex ffor-scope
++@opindex fno-for-scope
++If @option{-ffor-scope} is specified, the scope of variables declared in
++a @i{for-init-statement} is limited to the @samp{for} loop itself,
++as specified by the C++ standard.
++If @option{-fno-for-scope} is specified, the scope of variables declared in
++a @i{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.
++
++@item -fno-gnu-keywords
++@opindex fno-gnu-keywords
++Do not recognize @code{typeof} as a keyword, so that code can use this
++word as an identifier. You can use the keyword @code{__typeof__} instead.
++@option{-ansi} implies @option{-fno-gnu-keywords}.
++
++@item -fno-implicit-templates
++@opindex fno-implicit-templates
++Never emit code for non-inline templates which are instantiated
++implicitly (i.e.@: by use); only emit code for explicit instantiations.
++@xref{Template Instantiation}, for more information.
++
++@item -fno-implicit-inline-templates
++@opindex 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.
++
++@item -fno-implement-inlines
++@opindex fno-implement-inlines
++To save space, do not emit out-of-line copies of inline functions
++controlled by @samp{#pragma implementation}. This will cause linker
++errors if these functions are not inlined everywhere they are called.
++
++@item -fms-extensions
++@opindex 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.
++
++@item -fno-nonansi-builtins
++@opindex fno-nonansi-builtins
++Disable built-in declarations of functions that are not mandated by
++ANSI/ISO C@. These include @code{ffs}, @code{alloca}, @code{_exit},
++@code{index}, @code{bzero}, @code{conjf}, and other related functions.
++
++@item -fno-operator-names
++@opindex fno-operator-names
++Do not treat the operator name keywords @code{and}, @code{bitand},
++@code{bitor}, @code{compl}, @code{not}, @code{or} and @code{xor} as
++synonyms as keywords.
++
++@item -fno-optional-diags
++@opindex 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.
++
++@item -fpermissive
++@opindex fpermissive
++Downgrade some diagnostics about nonconformant code from errors to
++warnings. Thus, using @option{-fpermissive} will allow some
++nonconforming code to compile.
++
++@item -frepo
++@opindex frepo
++Enable automatic template instantiation at link time. This option also
++implies @option{-fno-implicit-templates}. @xref{Template
++Instantiation}, for more information.
++
++@item -fno-rtti
++@opindex fno-rtti
++Disable generation of information about every class with virtual
++functions for use by the C++ runtime type identification features
++(@samp{dynamic_cast} and @samp{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. The @samp{dynamic_cast} operator can still be used for casts that
++do not require runtime type information, i.e.@: casts to @code{void *} or to
++unambiguous base classes.
++
++@item -fstats
++@opindex fstats
++Emit statistics about front-end processing at the end of the compilation.
++This information is generally only useful to the G++ development team.
++
++@item -ftemplate-depth-@var{n}
++@opindex ftemplate-depth
++Set the maximum instantiation depth for template classes to @var{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.
++
++@item -fno-threadsafe-statics
++@opindex fno-threadsafe-statics
++Do not emit the extra code to use the routines specified in the C++
++ABI for thread-safe initialization of local statics. You can use this
++option to reduce code size slightly in code that doesn't need to be
++thread-safe.
++
++@item -fuse-cxa-atexit
++@opindex fuse-cxa-atexit
++Register destructors for objects with static storage duration with the
++@code{__cxa_atexit} function rather than the @code{atexit} function.
++This option is required for fully standards-compliant handling of static
++destructors, but will only work if your C library supports
++@code{__cxa_atexit}.
++
++@item -fno-use-cxa-get-exception-ptr
++@opindex fno-use-cxa-get-exception-ptr
++Don't use the @code{__cxa_get_exception_ptr} runtime routine. This
++will cause @code{std::uncaught_exception} to be incorrect, but is necessary
++if the runtime routine is not available.
++
++@item -fvisibility-inlines-hidden
++@opindex fvisibility-inlines-hidden
++This switch declares that the user does not attempt to compare
++pointers to inline methods where the addresses of the two functions
++were taken in different shared objects.
++
++The effect of this is that GCC may, effectively, mark inline methods with
++@code{__attribute__ ((visibility ("hidden")))} so that they do not
++appear in the export table of a DSO and do not require a PLT indirection
++when used within the DSO@. Enabling this option can have a dramatic effect
++on load and link times of a DSO as it massively reduces the size of the
++dynamic export table when the library makes heavy use of templates.
++
++The behavior of this switch is not quite the same as marking the
++methods as hidden directly, because it does not affect static variables
++local to the function or cause the compiler to deduce that
++the function is defined in only one shared object.
++
++You may mark a method as having a visibility explicitly to negate the
++effect of the switch for that method. For example, if you do want to
++compare pointers to a particular inline method, you might mark it as
++having default visibility. Marking the enclosing class with explicit
++visibility will have no effect.
++
++Explicitly instantiated inline methods are unaffected by this option
++as their linkage might otherwise cross a shared library boundary.
++@xref{Template Instantiation}.
++
++@item -fvisibility-ms-compat
++@opindex fvisibility-ms-compat
++This flag attempts to use visibility settings to make GCC's C++
++linkage model compatible with that of Microsoft Visual Studio.
++
++The flag makes these changes to GCC's linkage model:
++
++@enumerate
++@item
++It sets the default visibility to @code{hidden}, like
++@option{-fvisibility=hidden}.
++
++@item
++Types, but not their members, are not hidden by default.
++
++@item
++The One Definition Rule is relaxed for types without explicit
++visibility specifications which are defined in more than one different
++shared object: those declarations are permitted if they would have
++been permitted when this option was not used.
++@end enumerate
++
++In new code it is better to use @option{-fvisibility=hidden} and
++export those classes which are intended to be externally visible.
++Unfortunately it is possible for code to rely, perhaps accidentally,
++on the Visual Studio behavior.
++
++Among the consequences of these changes are that static data members
++of the same type with the same name but defined in different shared
++objects will be different, so changing one will not change the other;
++and that pointers to function members defined in different shared
++objects may not compare equal. When this flag is given, it is a
++violation of the ODR to define types with the same name differently.
++
++@item -fno-weak
++@opindex 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++.
++
++@item -nostdinc++
++@opindex 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.)
++@end table
++
++In addition, these optimization, warning, and code generation options
++have meanings only for C++ programs:
++
++@table @gcctabopt
++@item -fno-default-inline
++@opindex fno-default-inline
++Do not assume @samp{inline} for functions defined inside a class scope.
++@xref{Optimize Options,,Options That Control Optimization}. Note that these
++functions will have linkage like inline functions; they just won't be
++inlined by default.
++
++@item -Wabi @r{(C, Objective-C, C++ and Objective-C++ only)}
++@opindex Wabi
++@opindex Wno-abi
++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 incompatibilities at this point include:
++
++@itemize @bullet
++
++@item
++Incorrect handling of tail-padding for bit-fields. G++ may attempt to
++pack data into the same byte as a base class. For example:
++
++@smallexample
++struct A @{ virtual void f(); int f1 : 1; @};
++struct B : public A @{ int f2 : 1; @};
++@end smallexample
++
++@noindent
++In this case, G++ will place @code{B::f2} into the same byte
++as@code{A::f1}; other compilers will not. You can avoid this problem
++by explicitly padding @code{A} so that its size is a multiple of the
++byte size on your platform; that will cause G++ and other compilers to
++layout @code{B} identically.
++
++@item
++Incorrect handling of tail-padding for virtual bases. G++ does not use
++tail padding when laying out virtual bases. For example:
++
++@smallexample
++struct A @{ virtual void f(); char c1; @};
++struct B @{ B(); char c2; @};
++struct C : public A, public virtual B @{@};
++@end smallexample
++
++@noindent
++In this case, G++ will not place @code{B} into the tail-padding for
++@code{A}; other compilers will. You can avoid this problem by
++explicitly padding @code{A} so that its size is a multiple of its
++alignment (ignoring virtual base classes); that will cause G++ and other
++compilers to layout @code{C} identically.
++
++@item
++Incorrect handling of bit-fields with declared widths greater than that
++of their underlying types, when the bit-fields appear in a union. For
++example:
++
++@smallexample
++union U @{ int i : 4096; @};
++@end smallexample
++
++@noindent
++Assuming that an @code{int} does not have 4096 bits, G++ will make the
++union too small by the number of bits in an @code{int}.
++
++@item
++Empty classes can be placed at incorrect offsets. For example:
++
++@smallexample
++struct A @{@};
++
++struct B @{
++ A a;
++ virtual void f ();
++@};
++
++struct C : public B, public A @{@};
++@end smallexample
++
++@noindent
++G++ will place the @code{A} base class of @code{C} at a nonzero offset;
++it should be placed at offset zero. G++ mistakenly believes that the
++@code{A} data member of @code{B} is already at offset zero.
++
++@item
++Names of template functions whose types involve @code{typename} or
++template template parameters can be mangled incorrectly.
++
++@smallexample
++template <typename Q>
++void f(typename Q::X) @{@}
++
++template <template <typename> class Q>
++void f(typename Q<int>::X) @{@}
++@end smallexample
++
++@noindent
++Instantiations of these templates may be mangled incorrectly.
++
++@end itemize
++
++It also warns psABI related changes. The known psABI changes at this
++point include:
++
++@itemize @bullet
++
++@item
++For SYSV/x86-64, when passing union with long double, it is changed to
++pass in memory as specified in psABI. For example:
++
++@smallexample
++union U @{
++ long double ld;
++ int i;
++@};
++@end smallexample
++
++@noindent
++@code{union U} will always be passed in memory.
++
++@end itemize
++
++@item -Wctor-dtor-privacy @r{(C++ and Objective-C++ only)}
++@opindex Wctor-dtor-privacy
++@opindex Wno-ctor-dtor-privacy
++Warn when a class seems unusable because all the constructors or
++destructors in that class are private, and it has neither friends nor
++public static member functions.
++
++@item -Wnon-virtual-dtor @r{(C++ and Objective-C++ only)}
++@opindex Wnon-virtual-dtor
++@opindex Wno-non-virtual-dtor
++Warn when a class has virtual functions and accessible non-virtual
++destructor, in which case it would be possible but unsafe to delete
++an instance of a derived class through a pointer to the base class.
++This warning is also enabled if -Weffc++ is specified.
++
++@item -Wreorder @r{(C++ and Objective-C++ only)}
++@opindex Wreorder
++@opindex Wno-reorder
++@cindex reordering, warning
++@cindex warning for reordering of member initializers
++Warn when the order of member initializers given in the code does not
++match the order in which they must be executed. For instance:
++
++@smallexample
++struct A @{
++ int i;
++ int j;
++ A(): j (0), i (1) @{ @}
++@};
++@end smallexample
++
++The compiler will rearrange the member initializers for @samp{i}
++and @samp{j} to match the declaration order of the members, emitting
++a warning to that effect. This warning is enabled by @option{-Wall}.
++@end table
++
++The following @option{-W@dots{}} options are not affected by @option{-Wall}.
++
++@table @gcctabopt
++@item -Weffc++ @r{(C++ and Objective-C++ only)}
++@opindex Weffc++
++@opindex Wno-effc++
++Warn about violations of the following style guidelines from Scott Meyers'
++@cite{Effective C++} book:
++
++@itemize @bullet
++@item
++Item 11: Define a copy constructor and an assignment operator for classes
++with dynamically allocated memory.
++
++@item
++Item 12: Prefer initialization to assignment in constructors.
++
++@item
++Item 14: Make destructors virtual in base classes.
++
++@item
++Item 15: Have @code{operator=} return a reference to @code{*this}.
++
++@item
++Item 23: Don't try to return a reference when you must return an object.
++
++@end itemize
++
++Also warn about violations of the following style guidelines from
++Scott Meyers' @cite{More Effective C++} book:
++
++@itemize @bullet
++@item
++Item 6: Distinguish between prefix and postfix forms of increment and
++decrement operators.
++
++@item
++Item 7: Never overload @code{&&}, @code{||}, or @code{,}.
++
++@end itemize
++
++When selecting this option, be aware that the standard library
++headers do not obey all of these guidelines; use @samp{grep -v}
++to filter out those warnings.
++
++@item -Wstrict-null-sentinel @r{(C++ and Objective-C++ only)}
++@opindex Wstrict-null-sentinel
++@opindex Wno-strict-null-sentinel
++Warn also about the use of an uncasted @code{NULL} as sentinel. When
++compiling only with GCC this is a valid sentinel, as @code{NULL} is defined
++to @code{__null}. Although it is a null pointer constant not a null pointer,
++it is guaranteed to be of the same size as a pointer. But this use is
++not portable across different compilers.
++
++@item -Wno-non-template-friend @r{(C++ and Objective-C++ only)}
++@opindex Wno-non-template-friend
++@opindex Wnon-template-friend
++Disable warnings when non-templatized friend functions are declared
++within a template. Since the advent of explicit template specification
++support in G++, if the name of the friend is an unqualified-id (i.e.,
++@samp{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++, @option{-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
++@option{-Wno-non-template-friend} which keeps the conformant compiler code
++but disables the helpful warning.
++
++@item -Wold-style-cast @r{(C++ and Objective-C++ only)}
++@opindex Wold-style-cast
++@opindex Wno-old-style-cast
++Warn if an old-style (C-style) cast to a non-void type is used within
++a C++ program. The new-style casts (@samp{dynamic_cast},
++@samp{static_cast}, @samp{reinterpret_cast}, and @samp{const_cast}) are
++less vulnerable to unintended effects and much easier to search for.
++
++@item -Woverloaded-virtual @r{(C++ and Objective-C++ only)}
++@opindex Woverloaded-virtual
++@opindex Wno-overloaded-virtual
++@cindex overloaded virtual fn, warning
++@cindex warning for overloaded virtual fn
++Warn when a function declaration hides virtual functions from a
++base class. For example, in:
++
++@smallexample
++struct A @{
++ virtual void f();
++@};
++
++struct B: public A @{
++ void f(int);
++@};
++@end smallexample
++
++the @code{A} class version of @code{f} is hidden in @code{B}, and code
++like:
++
++@smallexample
++B* b;
++b->f();
++@end smallexample
++
++will fail to compile.
++
++@item -Wno-pmf-conversions @r{(C++ and Objective-C++ only)}
++@opindex Wno-pmf-conversions
++@opindex Wpmf-conversions
++Disable the diagnostic for converting a bound pointer to member function
++to a plain pointer.
++
++@item -Wsign-promo @r{(C++ and Objective-C++ only)}
++@opindex Wsign-promo
++@opindex Wno-sign-promo
++Warn when overload resolution chooses a promotion from unsigned or
++enumerated 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.
++
++@smallexample
++struct A @{
++ operator int ();
++ A& operator = (int);
++@};
++
++main ()
++@{
++ A a,b;
++ a = b;
++@}
++@end smallexample
++
++In this example, G++ will synthesize a default @samp{A& operator =
++(const A&);}, while cfront will use the user-defined @samp{operator =}.
++@end table
++
++@node Objective-C and Objective-C++ Dialect Options
++@section Options Controlling Objective-C and Objective-C++ Dialects
++
++@cindex compiler options, Objective-C and Objective-C++
++@cindex Objective-C and Objective-C++ options, command line
++@cindex options, Objective-C and Objective-C++
++(NOTE: This manual does not describe the Objective-C and Objective-C++
++languages themselves. See @xref{Standards,,Language Standards
++Supported by GCC}, for references.)
++
++This section describes the command-line options that are only meaningful
++for Objective-C and Objective-C++ programs, but you can also use most of
++the language-independent GNU compiler options.
++For example, you might compile a file @code{some_class.m} like this:
++
++@smallexample
++gcc -g -fgnu-runtime -O -c some_class.m
++@end smallexample
++
++@noindent
++In this example, @option{-fgnu-runtime} is an option meant only for
++Objective-C and Objective-C++ programs; you can use the other options with
++any language supported by GCC@.
++
++Note that since Objective-C is an extension of the C language, Objective-C
++compilations may also use options specific to the C front-end (e.g.,
++@option{-Wtraditional}). Similarly, Objective-C++ compilations may use
++C++-specific options (e.g., @option{-Wabi}).
++
++Here is a list of options that are @emph{only} for compiling Objective-C
++and Objective-C++ programs:
++
++@table @gcctabopt
++@item -fconstant-string-class=@var{class-name}
++@opindex fconstant-string-class
++Use @var{class-name} as the name of the class to instantiate for each
++literal string specified with the syntax @code{@@"@dots{}"}. The default
++class name is @code{NXConstantString} if the GNU runtime is being used, and
++@code{NSConstantString} if the NeXT runtime is being used (see below). The
++@option{-fconstant-cfstrings} option, if also present, will override the
++@option{-fconstant-string-class} setting and cause @code{@@"@dots{}"} literals
++to be laid out as constant CoreFoundation strings.
++
++@item -fgnu-runtime
++@opindex fgnu-runtime
++Generate object code compatible with the standard GNU Objective-C
++runtime. This is the default for most types of systems.
++
++@item -fnext-runtime
++@opindex fnext-runtime
++Generate output compatible with the NeXT runtime. This is the default
++for NeXT-based systems, including Darwin and Mac OS X@. The macro
++@code{__NEXT_RUNTIME__} is predefined if (and only if) this option is
++used.
++
++@item -fno-nil-receivers
++@opindex fno-nil-receivers
++Assume that all Objective-C message dispatches (e.g.,
++@code{[receiver message:arg]}) in this translation unit ensure that the receiver
++is not @code{nil}. This allows for more efficient entry points in the runtime
++to be used. Currently, this option is only available in conjunction with
++the NeXT runtime on Mac OS X 10.3 and later.
++
++@item -fobjc-call-cxx-cdtors
++@opindex fobjc-call-cxx-cdtors
++For each Objective-C class, check if any of its instance variables is a
++C++ object with a non-trivial default constructor. If so, synthesize a
++special @code{- (id) .cxx_construct} instance method that will run
++non-trivial default constructors on any such instance variables, in order,
++and then return @code{self}. Similarly, check if any instance variable
++is a C++ object with a non-trivial destructor, and if so, synthesize a
++special @code{- (void) .cxx_destruct} method that will run
++all such default destructors, in reverse order.
++
++The @code{- (id) .cxx_construct} and/or @code{- (void) .cxx_destruct} methods
++thusly generated will only operate on instance variables declared in the
++current Objective-C class, and not those inherited from superclasses. It
++is the responsibility of the Objective-C runtime to invoke all such methods
++in an object's inheritance hierarchy. The @code{- (id) .cxx_construct} methods
++will be invoked by the runtime immediately after a new object
++instance is allocated; the @code{- (void) .cxx_destruct} methods will
++be invoked immediately before the runtime deallocates an object instance.
++
++As of this writing, only the NeXT runtime on Mac OS X 10.4 and later has
++support for invoking the @code{- (id) .cxx_construct} and
++@code{- (void) .cxx_destruct} methods.
++
++@item -fobjc-direct-dispatch
++@opindex fobjc-direct-dispatch
++Allow fast jumps to the message dispatcher. On Darwin this is
++accomplished via the comm page.
++
++@item -fobjc-exceptions
++@opindex fobjc-exceptions
++Enable syntactic support for structured exception handling in Objective-C,
++similar to what is offered by C++ and Java. This option is
++unavailable in conjunction with the NeXT runtime on Mac OS X 10.2 and
++earlier.
++
++@smallexample
++ @@try @{
++ @dots{}
++ @@throw expr;
++ @dots{}
++ @}
++ @@catch (AnObjCClass *exc) @{
++ @dots{}
++ @@throw expr;
++ @dots{}
++ @@throw;
++ @dots{}
++ @}
++ @@catch (AnotherClass *exc) @{
++ @dots{}
++ @}
++ @@catch (id allOthers) @{
++ @dots{}
++ @}
++ @@finally @{
++ @dots{}
++ @@throw expr;
++ @dots{}
++ @}
++@end smallexample
++
++The @code{@@throw} statement may appear anywhere in an Objective-C or
++Objective-C++ program; when used inside of a @code{@@catch} block, the
++@code{@@throw} may appear without an argument (as shown above), in which case
++the object caught by the @code{@@catch} will be rethrown.
++
++Note that only (pointers to) Objective-C objects may be thrown and
++caught using this scheme. When an object is thrown, it will be caught
++by the nearest @code{@@catch} clause capable of handling objects of that type,
++analogously to how @code{catch} blocks work in C++ and Java. A
++@code{@@catch(id @dots{})} clause (as shown above) may also be provided to catch
++any and all Objective-C exceptions not caught by previous @code{@@catch}
++clauses (if any).
++
++The @code{@@finally} clause, if present, will be executed upon exit from the
++immediately preceding @code{@@try @dots{} @@catch} section. This will happen
++regardless of whether any exceptions are thrown, caught or rethrown
++inside the @code{@@try @dots{} @@catch} section, analogously to the behavior
++of the @code{finally} clause in Java.
++
++There are several caveats to using the new exception mechanism:
++
++@itemize @bullet
++@item
++Although currently designed to be binary compatible with @code{NS_HANDLER}-style
++idioms provided by the @code{NSException} class, the new
++exceptions can only be used on Mac OS X 10.3 (Panther) and later
++systems, due to additional functionality needed in the (NeXT) Objective-C
++runtime.
++
++@item
++As mentioned above, the new exceptions do not support handling
++types other than Objective-C objects. Furthermore, when used from
++Objective-C++, the Objective-C exception model does not interoperate with C++
++exceptions at this time. This means you cannot @code{@@throw} an exception
++from Objective-C and @code{catch} it in C++, or vice versa
++(i.e., @code{throw @dots{} @@catch}).
++@end itemize
++
++The @option{-fobjc-exceptions} switch also enables the use of synchronization
++blocks for thread-safe execution:
++
++@smallexample
++ @@synchronized (ObjCClass *guard) @{
++ @dots{}
++ @}
++@end smallexample
++
++Upon entering the @code{@@synchronized} block, a thread of execution shall
++first check whether a lock has been placed on the corresponding @code{guard}
++object by another thread. If it has, the current thread shall wait until
++the other thread relinquishes its lock. Once @code{guard} becomes available,
++the current thread will place its own lock on it, execute the code contained in
++the @code{@@synchronized} block, and finally relinquish the lock (thereby
++making @code{guard} available to other threads).
++
++Unlike Java, Objective-C does not allow for entire methods to be marked
++@code{@@synchronized}. Note that throwing exceptions out of
++@code{@@synchronized} blocks is allowed, and will cause the guarding object
++to be unlocked properly.
++
++@item -fobjc-gc
++@opindex fobjc-gc
++Enable garbage collection (GC) in Objective-C and Objective-C++ programs.
++
++@item -freplace-objc-classes
++@opindex freplace-objc-classes
++Emit a special marker instructing @command{ld(1)} not to statically link in
++the resulting object file, and allow @command{dyld(1)} to load it in at
++run time instead. This is used in conjunction with the Fix-and-Continue
++debugging mode, where the object file in question may be recompiled and
++dynamically reloaded in the course of program execution, without the need
++to restart the program itself. Currently, Fix-and-Continue functionality
++is only available in conjunction with the NeXT runtime on Mac OS X 10.3
++and later.
++
++@item -fzero-link
++@opindex fzero-link
++When compiling for the NeXT runtime, the compiler ordinarily replaces calls
++to @code{objc_getClass("@dots{}")} (when the name of the class is known at
++compile time) with static class references that get initialized at load time,
++which improves run-time performance. Specifying the @option{-fzero-link} flag
++suppresses this behavior and causes calls to @code{objc_getClass("@dots{}")}
++to be retained. This is useful in Zero-Link debugging mode, since it allows
++for individual class implementations to be modified during program execution.
++
++@item -gen-decls
++@opindex gen-decls
++Dump interface declarations for all classes seen in the source file to a
++file named @file{@var{sourcename}.decl}.
++
++@item -Wassign-intercept @r{(Objective-C and Objective-C++ only)}
++@opindex Wassign-intercept
++@opindex Wno-assign-intercept
++Warn whenever an Objective-C assignment is being intercepted by the
++garbage collector.
++
++@item -Wno-protocol @r{(Objective-C and Objective-C++ only)}
++@opindex Wno-protocol
++@opindex Wprotocol
++If a class is declared to implement a protocol, a warning is issued for
++every method in the protocol that is not implemented by the class. The
++default behavior is to issue a warning for every method not explicitly
++implemented in the class, even if a method implementation is inherited
++from the superclass. If you use the @option{-Wno-protocol} option, then
++methods inherited from the superclass are considered to be implemented,
++and no warning is issued for them.
++
++@item -Wselector @r{(Objective-C and Objective-C++ only)}
++@opindex Wselector
++@opindex Wno-selector
++Warn if multiple methods of different types for the same selector are
++found during compilation. The check is performed on the list of methods
++in the final stage of compilation. Additionally, a check is performed
++for each selector appearing in a @code{@@selector(@dots{})}
++expression, and a corresponding method for that selector has been found
++during compilation. Because these checks scan the method table only at
++the end of compilation, these warnings are not produced if the final
++stage of compilation is not reached, for example because an error is
++found during compilation, or because the @option{-fsyntax-only} option is
++being used.
++
++@item -Wstrict-selector-match @r{(Objective-C and Objective-C++ only)}
++@opindex Wstrict-selector-match
++@opindex Wno-strict-selector-match
++Warn if multiple methods with differing argument and/or return types are
++found for a given selector when attempting to send a message using this
++selector to a receiver of type @code{id} or @code{Class}. When this flag
++is off (which is the default behavior), the compiler will omit such warnings
++if any differences found are confined to types which share the same size
++and alignment.
++
++@item -Wundeclared-selector @r{(Objective-C and Objective-C++ only)}
++@opindex Wundeclared-selector
++@opindex Wno-undeclared-selector
++Warn if a @code{@@selector(@dots{})} expression referring to an
++undeclared selector is found. A selector is considered undeclared if no
++method with that name has been declared before the
++@code{@@selector(@dots{})} expression, either explicitly in an
++@code{@@interface} or @code{@@protocol} declaration, or implicitly in
++an @code{@@implementation} section. This option always performs its
++checks as soon as a @code{@@selector(@dots{})} expression is found,
++while @option{-Wselector} only performs its checks in the final stage of
++compilation. This also enforces the coding style convention
++that methods and selectors must be declared before being used.
++
++@item -print-objc-runtime-info
++@opindex print-objc-runtime-info
++Generate C header describing the largest structure that is passed by
++value, if any.
++
++@end table
++
++@node Language Independent Options
++@section Options to Control Diagnostic Messages Formatting
++@cindex options to control diagnostics formatting
++@cindex diagnostic messages
++@cindex message formatting
++
++Traditionally, diagnostic messages have been formatted irrespective of
++the output device's aspect (e.g.@: its width, @dots{}). 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.
++
++@table @gcctabopt
++@item -fmessage-length=@var{n}
++@opindex fmessage-length
++Try to format error messages so that they fit on lines of about @var{n}
++characters. The default is 72 characters for @command{g++} and 0 for the rest of
++the front ends supported by GCC@. If @var{n} is zero, then no
++line-wrapping will be done; each error message will appear on a single
++line.
++
++@opindex fdiagnostics-show-location
++@item -fdiagnostics-show-location=once
++Only meaningful in line-wrapping mode. Instructs the diagnostic messages
++reporter to emit @emph{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.
++
++@item -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.
++
++@item -fdiagnostics-show-option
++@opindex fdiagnostics-show-option
++This option instructs the diagnostic machinery to add text to each
++diagnostic emitted, which indicates which command line option directly
++controls that diagnostic, when such an option is known to the
++diagnostic machinery.
++
++@item -Wcoverage-mismatch
++@opindex Wcoverage-mismatch
++Warn if feedback profiles do not match when using the
++@option{-fprofile-use} option.
++If a source file was changed between @option{-fprofile-gen} and
++@option{-fprofile-use}, the files with the profile feedback can fail
++to match the source file and GCC can not use the profile feedback
++information. By default, GCC emits an error message in this case.
++The option @option{-Wcoverage-mismatch} emits a warning instead of an
++error. GCC does not use appropriate feedback profiles, so using this
++option can result in poorly optimized code. This option is useful
++only in the case of very minor changes such as bug fixes to an
++existing code-base.
++
++@end table
++
++@node Warning Options
++@section Options to Request or Suppress Warnings
++@cindex options to control warnings
++@cindex warning messages
++@cindex messages, warning
++@cindex suppressing 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.
++
++The following language-independent options do not enable specific
++warnings but control the kinds of diagnostics produced by GCC.
++
++@table @gcctabopt
++@cindex syntax checking
++@item -fsyntax-only
++@opindex fsyntax-only
++Check the code for syntax errors, but don't do anything beyond that.
++
++@item -w
++@opindex w
++Inhibit all warning messages.
++
++@item -Werror
++@opindex Werror
++@opindex Wno-error
++Make all warnings into errors.
++
++@item -Werror=
++@opindex Werror=
++@opindex Wno-error=
++Make the specified warning into an error. The specifier for a warning
++is appended, for example @option{-Werror=switch} turns the warnings
++controlled by @option{-Wswitch} into errors. This switch takes a
++negative form, to be used to negate @option{-Werror} for specific
++warnings, for example @option{-Wno-error=switch} makes
++@option{-Wswitch} warnings not be errors, even when @option{-Werror}
++is in effect. You can use the @option{-fdiagnostics-show-option}
++option to have each controllable warning amended with the option which
++controls it, to determine what to use with this option.
++
++Note that specifying @option{-Werror=}@var{foo} automatically implies
++@option{-W}@var{foo}. However, @option{-Wno-error=}@var{foo} does not
++imply anything.
++
++@item -Wfatal-errors
++@opindex Wfatal-errors
++@opindex Wno-fatal-errors
++This option causes the compiler to abort compilation on the first error
++occurred rather than trying to keep going and printing further error
++messages.
++
++@end table
++
++You can request many specific warnings with options beginning
++@samp{-W}, for example @option{-Wimplicit} to request warnings on
++implicit declarations. Each of these specific warning options also
++has a negative form beginning @samp{-Wno-} to turn off warnings; for
++example, @option{-Wno-implicit}. This manual lists only one of the
++two forms, whichever is not the default. For further,
++language-specific options also refer to @ref{C++ Dialect Options} and
++@ref{Objective-C and Objective-C++ Dialect Options}.
++
++@table @gcctabopt
++@item -pedantic
++@opindex 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 @option{-std} option used.
++
++Valid ISO C and ISO C++ programs should compile properly with or without
++this option (though a rare few will require @option{-ansi} or a
++@option{-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.
++
++@option{-pedantic} does not cause warning messages for use of the
++alternate keywords whose names begin and end with @samp{__}. Pedantic
++warnings are also disabled in the expression that follows
++@code{__extension__}. However, only system header files should use
++these escape routes; application programs should avoid them.
++@xref{Alternate Keywords}.
++
++Some users try to use @option{-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 @emph{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 @option{-pedantic}. We don't have plans to
++support such a feature in the near future.
++
++Where the standard specified with @option{-std} represents a GNU
++extended dialect of C, such as @samp{gnu89} or @samp{gnu99}, there is a
++corresponding @dfn{base standard}, the version of ISO C on which the GNU
++extended dialect is based. Warnings from @option{-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.)
++
++@item -pedantic-errors
++@opindex pedantic-errors
++Like @option{-pedantic}, except that errors are produced rather than
++warnings.
++
++@item -Wall
++@opindex Wall
++@opindex Wno-all
++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. This also
++enables some language-specific warnings described in @ref{C++ Dialect
++Options} and @ref{Objective-C and Objective-C++ Dialect Options}.
++
++@option{-Wall} turns on the following warning flags:
++
++@gccoptlist{-Waddress @gol
++-Warray-bounds @r{(only with} @option{-O2}@r{)} @gol
++-Wc++0x-compat @gol
++-Wchar-subscripts @gol
++-Wimplicit-int @gol
++-Wimplicit-function-declaration @gol
++-Wcomment @gol
++-Wformat @gol
++-Wmain @r{(only for C/ObjC and unless} @option{-ffreestanding}@r{)} @gol
++-Wmissing-braces @gol
++-Wnonnull @gol
++-Wparentheses @gol
++-Wpointer-sign @gol
++-Wreorder @gol
++-Wreturn-type @gol
++-Wsequence-point @gol
++-Wsign-compare @r{(only in C++)} @gol
++-Wstrict-aliasing @gol
++-Wstrict-overflow=1 @gol
++-Wswitch @gol
++-Wtrigraphs @gol
++-Wuninitialized @gol
++-Wunknown-pragmas @gol
++-Wunused-function @gol
++-Wunused-label @gol
++-Wunused-value @gol
++-Wunused-variable @gol
++-Wvolatile-register-var @gol
++}
++
++Note that some warning flags are not implied by @option{-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. Some of them are enabled by @option{-Wextra} but many of
++them must be enabled individually.
++
++@item -Wextra
++@opindex W
++@opindex Wextra
++@opindex Wno-extra
++This enables some extra warning flags that are not enabled by
++@option{-Wall}. (This option used to be called @option{-W}. The older
++name is still supported, but the newer name is more descriptive.)
++
++@gccoptlist{-Wclobbered @gol
++-Wempty-body @gol
++-Wignored-qualifiers @gol
++-Wmissing-field-initializers @gol
++-Wmissing-parameter-type @r{(C only)} @gol
++-Wold-style-declaration @r{(C only)} @gol
++-Woverride-init @gol
++-Wsign-compare @gol
++-Wtype-limits @gol
++-Wuninitialized @gol
++-Wunused-parameter @r{(only with} @option{-Wunused} @r{or} @option{-Wall}@r{)} @gol
++}
++
++The option @option{-Wextra} also prints warning messages for the
++following cases:
++
++@itemize @bullet
++
++@item
++A pointer is compared against integer zero with @samp{<}, @samp{<=},
++@samp{>}, or @samp{>=}.
++
++@item
++(C++ only) An enumerator and a non-enumerator both appear in a
++conditional expression.
++
++@item
++(C++ only) Ambiguous virtual bases.
++
++@item
++(C++ only) Subscripting an array which has been declared @samp{register}.
++
++@item
++(C++ only) Taking the address of a variable which has been declared
++@samp{register}.
++
++@item
++(C++ only) A base class is not initialized in a derived class' copy
++constructor.
++
++@end itemize
++
++@item -Wchar-subscripts
++@opindex Wchar-subscripts
++@opindex Wno-char-subscripts
++Warn if an array subscript has type @code{char}. This is a common cause
++of error, as programmers often forget that this type is signed on some
++machines.
++This warning is enabled by @option{-Wall}.
++
++@item -Wcomment
++@opindex Wcomment
++@opindex Wno-comment
++Warn whenever a comment-start sequence @samp{/*} appears in a @samp{/*}
++comment, or whenever a Backslash-Newline appears in a @samp{//} comment.
++This warning is enabled by @option{-Wall}.
++
++@item -Wformat
++@opindex Wformat
++@opindex Wno-format
++@opindex ffreestanding
++@opindex fno-builtin
++Check calls to @code{printf} and @code{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 (@pxref{Function Attributes}), in the @code{printf},
++@code{scanf}, @code{strftime} and @code{strfmon} (an X/Open extension,
++not in the C standard) families (or other target-specific families).
++Which functions are checked without format attributes having been
++specified depends on the standard version selected, and such checks of
++functions without the attribute specified are disabled by
++@option{-ffreestanding} or @option{-fno-builtin}.
++
++The formats are checked against the format features supported by GNU
++libc version 2.2. These include all ISO C90 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 @option{-pedantic} is used
++with @option{-Wformat}, warnings will be given about format features not
++in the selected standard version (but not for @code{strfmon} formats,
++since those are not in any version of the C standard). @xref{C Dialect
++Options,,Options Controlling C Dialect}.
++
++Since @option{-Wformat} also checks for null format arguments for
++several functions, @option{-Wformat} also implies @option{-Wnonnull}.
++
++@option{-Wformat} is included in @option{-Wall}. For more control over some
++aspects of format checking, the options @option{-Wformat-y2k},
++@option{-Wno-format-extra-args}, @option{-Wno-format-zero-length},
++@option{-Wformat-nonliteral}, @option{-Wformat-security}, and
++@option{-Wformat=2} are available, but are not included in @option{-Wall}.
++
++@item -Wformat-y2k
++@opindex Wformat-y2k
++@opindex Wno-format-y2k
++If @option{-Wformat} is specified, also warn about @code{strftime}
++formats which may yield only a two-digit year.
++
++@item -Wno-format-contains-nul
++@opindex Wno-format-contains-nul
++@opindex Wformat-contains-nul
++If @option{-Wformat} is specified, do not warn about format strings that
++contain NUL bytes.
++
++@item -Wno-format-extra-args
++@opindex Wno-format-extra-args
++@opindex Wformat-extra-args
++If @option{-Wformat} is specified, do not warn about excess arguments to a
++@code{printf} or @code{scanf} format function. The C standard specifies
++that such arguments are ignored.
++
++Where the unused arguments lie between used arguments that are
++specified with @samp{$} operand number specifications, normally
++warnings are still given, since the implementation could not know what
++type to pass to @code{va_arg} to skip the unused arguments. However,
++in the case of @code{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.
++
++@item -Wno-format-zero-length @r{(C and Objective-C only)}
++@opindex Wno-format-zero-length
++@opindex Wformat-zero-length
++If @option{-Wformat} is specified, do not warn about zero-length formats.
++The C standard specifies that zero-length formats are allowed.
++
++@item -Wformat-nonliteral
++@opindex Wformat-nonliteral
++@opindex Wno-format-nonliteral
++If @option{-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 @code{va_list}.
++
++@item -Wformat-security
++@opindex Wformat-security
++@opindex Wno-format-security
++If @option{-Wformat} is specified, also warn about uses of format
++functions that represent possible security problems. At present, this
++warns about calls to @code{printf} and @code{scanf} functions where the
++format string is not a string literal and there are no format arguments,
++as in @code{printf (foo);}. This may be a security hole if the format
++string came from untrusted input and contains @samp{%n}. (This is
++currently a subset of what @option{-Wformat-nonliteral} warns about, but
++in future warnings may be added to @option{-Wformat-security} that are not
++included in @option{-Wformat-nonliteral}.)
++
++@item -Wformat=2
++@opindex Wformat=2
++@opindex Wno-format=2
++Enable @option{-Wformat} plus format checks not included in
++@option{-Wformat}. Currently equivalent to @samp{-Wformat
++-Wformat-nonliteral -Wformat-security -Wformat-y2k}.
++
++@item -Wnonnull @r{(C and Objective-C only)}
++@opindex Wnonnull
++@opindex Wno-nonnull
++Warn about passing a null pointer for arguments marked as
++requiring a non-null value by the @code{nonnull} function attribute.
++
++@option{-Wnonnull} is included in @option{-Wall} and @option{-Wformat}. It
++can be disabled with the @option{-Wno-nonnull} option.
++
++@item -Winit-self @r{(C, C++, Objective-C and Objective-C++ only)}
++@opindex Winit-self
++@opindex Wno-init-self
++Warn about uninitialized variables which are initialized with themselves.
++Note this option can only be used with the @option{-Wuninitialized} option.
++
++For example, GCC will warn about @code{i} being uninitialized in the
++following snippet only when @option{-Winit-self} has been specified:
++@smallexample
++@group
++int f()
++@{
++ int i = i;
++ return i;
++@}
++@end group
++@end smallexample
++
++@item -Wimplicit-int @r{(C and Objective-C only)}
++@opindex Wimplicit-int
++@opindex Wno-implicit-int
++Warn when a declaration does not specify a type.
++This warning is enabled by @option{-Wall}.
++
++@item -Wimplicit-function-declaration @r{(C and Objective-C only)}
++@opindex Wimplicit-function-declaration
++@opindex Wno-implicit-function-declaration
++Give a warning whenever a function is used before being declared. In
++C99 mode (@option{-std=c99} or @option{-std=gnu99}), this warning is
++enabled by default and it is made into an error by
++@option{-pedantic-errors}. This warning is also enabled by
++@option{-Wall}.
++
++@item -Wimplicit
++@opindex Wimplicit
++@opindex Wno-implicit
++Same as @option{-Wimplicit-int} and @option{-Wimplicit-function-declaration}.
++This warning is enabled by @option{-Wall}.
++
++@item -Wignored-qualifiers @r{(C and C++ only)}
++@opindex Wignored-qualifiers
++@opindex Wno-ignored-qualifiers
++Warn if the return type of a function has a type qualifier
++such as @code{const}. For ISO C such a type qualifier has no effect,
++since the value returned by a function is not an lvalue.
++For C++, the warning is only emitted for scalar types or @code{void}.
++ISO C prohibits qualified @code{void} return types on function
++definitions, so such return types always receive a warning
++even without this option.
++
++This warning is also enabled by @option{-Wextra}.
++
++@item -Wmain
++@opindex Wmain
++@opindex Wno-main
++Warn if the type of @samp{main} is suspicious. @samp{main} should be
++a function with external linkage, returning int, taking either zero
++arguments, two, or three arguments of appropriate types. This warning
++is enabled by default in C++ and is enabled by either @option{-Wall}
++or @option{-pedantic}.
++
++@item -Wmissing-braces
++@opindex Wmissing-braces
++@opindex Wno-missing-braces
++Warn if an aggregate or union initializer is not fully bracketed. In
++the following example, the initializer for @samp{a} is not fully
++bracketed, but that for @samp{b} is fully bracketed.
++
++@smallexample
++int a[2][2] = @{ 0, 1, 2, 3 @};
++int b[2][2] = @{ @{ 0, 1 @}, @{ 2, 3 @} @};
++@end smallexample
++
++This warning is enabled by @option{-Wall}.
++
++@item -Wmissing-include-dirs @r{(C, C++, Objective-C and Objective-C++ only)}
++@opindex Wmissing-include-dirs
++@opindex Wno-missing-include-dirs
++Warn if a user-supplied include directory does not exist.
++
++@item -Wparentheses
++@opindex Wparentheses
++@opindex Wno-parentheses
++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 if a comparison like @samp{x<=y<=z} appears; this is
++equivalent to @samp{(x<=y ? 1 : 0) <= z}, which is a different
++interpretation from that of ordinary mathematical notation.
++
++Also warn about constructions where there may be confusion to which
++@code{if} statement an @code{else} branch belongs. Here is an example of
++such a case:
++
++@smallexample
++@group
++@{
++ if (a)
++ if (b)
++ foo ();
++ else
++ bar ();
++@}
++@end group
++@end smallexample
++
++In C/C++, every @code{else} branch belongs to the innermost possible
++@code{if} statement, which in this example is @code{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 @code{if} statement so there is no way the @code{else}
++could belong to the enclosing @code{if}. The resulting code would
++look like this:
++
++@smallexample
++@group
++@{
++ if (a)
++ @{
++ if (b)
++ foo ();
++ else
++ bar ();
++ @}
++@}
++@end group
++@end smallexample
++
++This warning is enabled by @option{-Wall}.
++
++@item -Wsequence-point
++@opindex Wsequence-point
++@opindex Wno-sequence-point
++Warn about code that may have undefined semantics because of violations
++of sequence point rules in the C and C++ standards.
++
++The C and C++ standards defines the order in which expressions in a C/C++
++program are evaluated in terms of @dfn{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
++@code{&&}, @code{||}, @code{? :} or @code{,} (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 and C++ standards specify 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 @code{a = a++;}, @code{a[n]
++= b[n++]} and @code{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 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 the GCC readings page, at
++@w{@uref{http://gcc.gnu.org/readings.html}}.
++
++This warning is enabled by @option{-Wall} for C and C++.
++
++@item -Wreturn-type
++@opindex Wreturn-type
++@opindex Wno-return-type
++Warn whenever a function is defined with a return-type that defaults
++to @code{int}. Also warn about any @code{return} statement with no
++return-value in a function whose return-type is not @code{void}
++(falling off the end of the function body is considered returning
++without a value), and about a @code{return} statement with a
++expression in a function whose return-type is @code{void}.
++
++For C++, a function without return type always produces a diagnostic
++message, even when @option{-Wno-return-type} is specified. The only
++exceptions are @samp{main} and functions defined in system headers.
++
++This warning is enabled by @option{-Wall}.
++
++@item -Wswitch
++@opindex Wswitch
++@opindex Wno-switch
++Warn whenever a @code{switch} statement has an index of enumerated type
++and lacks a @code{case} for one or more of the named codes of that
++enumeration. (The presence of a @code{default} label prevents this
++warning.) @code{case} labels outside the enumeration range also
++provoke warnings when this option is used.
++This warning is enabled by @option{-Wall}.
++
++@item -Wswitch-default
++@opindex Wswitch-default
++@opindex Wno-switch-default
++Warn whenever a @code{switch} statement does not have a @code{default}
++case.
++
++@item -Wswitch-enum
++@opindex Wswitch-enum
++@opindex Wno-switch-enum
++Warn whenever a @code{switch} statement has an index of enumerated type
++and lacks a @code{case} for one or more of the named codes of that
++enumeration. @code{case} labels outside the enumeration range also
++provoke warnings when this option is used.
++
++@item -Wsync-nand @r{(C and C++ only)}
++@opindex Wsync-nand
++@opindex Wno-sync-nand
++Warn when @code{__sync_fetch_and_nand} and @code{__sync_nand_and_fetch}
++built-in functions are used. These functions changed semantics in GCC 4.4.
++
++@item -Wtrigraphs
++@opindex Wtrigraphs
++@opindex Wno-trigraphs
++Warn if any trigraphs are encountered that might change the meaning of
++the program (trigraphs within comments are not warned about).
++This warning is enabled by @option{-Wall}.
++
++@item -Wunused-function
++@opindex Wunused-function
++@opindex Wno-unused-function
++Warn whenever a static function is declared but not defined or a
++non-inline static function is unused.
++This warning is enabled by @option{-Wall}.
++
++@item -Wunused-label
++@opindex Wunused-label
++@opindex Wno-unused-label
++Warn whenever a label is declared but not used.
++This warning is enabled by @option{-Wall}.
++
++To suppress this warning use the @samp{unused} attribute
++(@pxref{Variable Attributes}).
++
++@item -Wunused-parameter
++@opindex Wunused-parameter
++@opindex Wno-unused-parameter
++Warn whenever a function parameter is unused aside from its declaration.
++
++To suppress this warning use the @samp{unused} attribute
++(@pxref{Variable Attributes}).
++
++@item -Wunused-variable
++@opindex Wunused-variable
++@opindex Wno-unused-variable
++Warn whenever a local variable or non-constant static variable is unused
++aside from its declaration.
++This warning is enabled by @option{-Wall}.
++
++To suppress this warning use the @samp{unused} attribute
++(@pxref{Variable Attributes}).
++
++@item -Wunused-value
++@opindex Wunused-value
++@opindex Wno-unused-value
++Warn whenever a statement computes a result that is explicitly not
++used. To suppress this warning cast the unused expression to
++@samp{void}. This includes an expression-statement or the left-hand
++side of a comma expression that contains no side effects. For example,
++an expression such as @samp{x[i,j]} will cause a warning, while
++@samp{x[(void)i,j]} will not.
++
++This warning is enabled by @option{-Wall}.
++
++@item -Wunused
++@opindex Wunused
++@opindex Wno-unused
++All the above @option{-Wunused} options combined.
++
++In order to get a warning about an unused function parameter, you must
++either specify @samp{-Wextra -Wunused} (note that @samp{-Wall} implies
++@samp{-Wunused}), or separately specify @option{-Wunused-parameter}.
++
++@item -Wuninitialized
++@opindex Wuninitialized
++@opindex Wno-uninitialized
++Warn if an automatic variable is used without first being initialized
++or if a variable may be clobbered by a @code{setjmp} call. In C++,
++warn if a non-static reference or non-static @samp{const} member
++appears in a class without constructors.
++
++If you want to warn about code which uses the uninitialized value of the
++variable in its own initializer, use the @option{-Winit-self} option.
++
++These warnings occur for individual uninitialized or clobbered
++elements of structure, union or array variables as well as for
++variables which are uninitialized or clobbered as a whole. They do
++not occur for variables or elements declared @code{volatile}. Because
++these warnings depend on optimization, the exact variables or elements
++for which there are warnings will depend on the precise optimization
++options and version of GCC used.
++
++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:
++
++@smallexample
++@group
++@{
++ int x;
++ switch (y)
++ @{
++ case 1: x = 1;
++ break;
++ case 2: x = 4;
++ break;
++ case 3: x = 5;
++ @}
++ foo (x);
++@}
++@end group
++@end smallexample
++
++@noindent
++If the value of @code{y} is always 1, 2 or 3, then @code{x} is
++always initialized, but GCC doesn't know this. Here is
++another common case:
++
++@smallexample
++@{
++ int save_y;
++ if (change_y) save_y = y, y = new_y;
++ @dots{}
++ if (change_y) y = save_y;
++@}
++@end smallexample
++
++@noindent
++This has no bug because @code{save_y} is used only if it is set.
++
++@cindex @code{longjmp} warnings
++This option also warns when a non-volatile automatic variable might be
++changed by a call to @code{longjmp}. These warnings as well are possible
++only in optimizing compilation.
++
++The compiler sees only the calls to @code{setjmp}. It cannot know
++where @code{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 @code{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 @code{noreturn}. @xref{Function
++Attributes}.
++
++This warning is enabled by @option{-Wall} or @option{-Wextra}.
++
++@item -Wunknown-pragmas
++@opindex Wunknown-pragmas
++@opindex Wno-unknown-pragmas
++@cindex warning for unknown pragmas
++@cindex unknown pragmas, warning
++@cindex pragmas, warning of unknown
++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 @option{-Wall} command line option.
++
++@item -Wno-pragmas
++@opindex Wno-pragmas
++@opindex Wpragmas
++Do not warn about misuses of pragmas, such as incorrect parameters,
++invalid syntax, or conflicts between pragmas. See also
++@samp{-Wunknown-pragmas}.
++
++@item -Wstrict-aliasing
++@opindex Wstrict-aliasing
++@opindex Wno-strict-aliasing
++This option is only active when @option{-fstrict-aliasing} is active.
++It warns about code which might break the strict aliasing rules that the
++compiler is using for optimization. The warning does not catch all
++cases, but does attempt to catch the more common pitfalls. It is
++included in @option{-Wall}.
++It is equivalent to @option{-Wstrict-aliasing=3}
++
++@item -Wstrict-aliasing=n
++@opindex Wstrict-aliasing=n
++@opindex Wno-strict-aliasing=n
++This option is only active when @option{-fstrict-aliasing} is active.
++It warns about code which might break the strict aliasing rules that the
++compiler is using for optimization.
++Higher levels correspond to higher accuracy (fewer false positives).
++Higher levels also correspond to more effort, similar to the way -O works.
++@option{-Wstrict-aliasing} is equivalent to @option{-Wstrict-aliasing=n},
++with n=3.
++
++Level 1: Most aggressive, quick, least accurate.
++Possibly useful when higher levels
++do not warn but -fstrict-aliasing still breaks the code, as it has very few
++false negatives. However, it has many false positives.
++Warns for all pointer conversions between possibly incompatible types,
++even if never dereferenced. Runs in the frontend only.
++
++Level 2: Aggressive, quick, not too precise.
++May still have many false positives (not as many as level 1 though),
++and few false negatives (but possibly more than level 1).
++Unlike level 1, it only warns when an address is taken. Warns about
++incomplete types. Runs in the frontend only.
++
++Level 3 (default for @option{-Wstrict-aliasing}):
++Should have very few false positives and few false
++negatives. Slightly slower than levels 1 or 2 when optimization is enabled.
++Takes care of the common punn+dereference pattern in the frontend:
++@code{*(int*)&some_float}.
++If optimization is enabled, it also runs in the backend, where it deals
++with multiple statement cases using flow-sensitive points-to information.
++Only warns when the converted pointer is dereferenced.
++Does not warn about incomplete types.
++
++@item -Wstrict-overflow
++@itemx -Wstrict-overflow=@var{n}
++@opindex Wstrict-overflow
++@opindex Wno-strict-overflow
++This option is only active when @option{-fstrict-overflow} is active.
++It warns about cases where the compiler optimizes based on the
++assumption that signed overflow does not occur. Note that it does not
++warn about all cases where the code might overflow: it only warns
++about cases where the compiler implements some optimization. Thus
++this warning depends on the optimization level.
++
++An optimization which assumes that signed overflow does not occur is
++perfectly safe if the values of the variables involved are such that
++overflow never does, in fact, occur. Therefore this warning can
++easily give a false positive: a warning about code which is not
++actually a problem. To help focus on important issues, several
++warning levels are defined. No warnings are issued for the use of
++undefined signed overflow when estimating how many iterations a loop
++will require, in particular when determining whether a loop will be
++executed at all.
++
++@table @gcctabopt
++@item -Wstrict-overflow=1
++Warn about cases which are both questionable and easy to avoid. For
++example: @code{x + 1 > x}; with @option{-fstrict-overflow}, the
++compiler will simplify this to @code{1}. This level of
++@option{-Wstrict-overflow} is enabled by @option{-Wall}; higher levels
++are not, and must be explicitly requested.
++
++@item -Wstrict-overflow=2
++Also warn about other cases where a comparison is simplified to a
++constant. For example: @code{abs (x) >= 0}. This can only be
++simplified when @option{-fstrict-overflow} is in effect, because
++@code{abs (INT_MIN)} overflows to @code{INT_MIN}, which is less than
++zero. @option{-Wstrict-overflow} (with no level) is the same as
++@option{-Wstrict-overflow=2}.
++
++@item -Wstrict-overflow=3
++Also warn about other cases where a comparison is simplified. For
++example: @code{x + 1 > 1} will be simplified to @code{x > 0}.
++
++@item -Wstrict-overflow=4
++Also warn about other simplifications not covered by the above cases.
++For example: @code{(x * 10) / 5} will be simplified to @code{x * 2}.
++
++@item -Wstrict-overflow=5
++Also warn about cases where the compiler reduces the magnitude of a
++constant involved in a comparison. For example: @code{x + 2 > y} will
++be simplified to @code{x + 1 >= y}. This is reported only at the
++highest warning level because this simplification applies to many
++comparisons, so this warning level will give a very large number of
++false positives.
++@end table
++
++@item -Warray-bounds
++@opindex Wno-array-bounds
++@opindex Warray-bounds
++This option is only active when @option{-ftree-vrp} is active
++(default for -O2 and above). It warns about subscripts to arrays
++that are always out of bounds. This warning is enabled by @option{-Wall}.
++
++@item -Wno-div-by-zero
++@opindex Wno-div-by-zero
++@opindex Wdiv-by-zero
++Do not warn about compile-time integer division by zero. Floating point
++division by zero is not warned about, as it can be a legitimate way of
++obtaining infinities and NaNs.
++
++@item -Wsystem-headers
++@opindex Wsystem-headers
++@opindex Wno-system-headers
++@cindex warnings from system headers
++@cindex system headers, warnings from
++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 @option{-Wall} in conjunction with this
++option will @emph{not} warn about unknown pragmas in system
++headers---for that, @option{-Wunknown-pragmas} must also be used.
++
++@item -Wfloat-equal
++@opindex Wfloat-equal
++@opindex Wno-float-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 analyzing 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.
++
++@item -Wtraditional @r{(C and Objective-C only)}
++@opindex Wtraditional
++@opindex Wno-traditional
++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.
++
++@itemize @bullet
++@item
++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@.
++
++@item
++In traditional C, some preprocessor directives did not exist.
++Traditional preprocessors would only consider a line to be a directive
++if the @samp{#} appeared in column 1 on the line. Therefore
++@option{-Wtraditional} warns about directives that traditional C
++understands but would ignore because the @samp{#} does not appear as the
++first character on the line. It also suggests you hide directives like
++@samp{#pragma} not understood by traditional C by indenting them. Some
++traditional implementations would not recognize @samp{#elif}, so it
++suggests avoiding it altogether.
++
++@item
++A function-like macro that appears without arguments.
++
++@item
++The unary plus operator.
++
++@item
++The @samp{U} integer constant suffix, or the @samp{F} or @samp{L} floating point
++constant suffixes. (Traditional C does support the @samp{L} suffix on integer
++constants.) Note, these suffixes appear in macros defined in the system
++headers of most modern systems, e.g.@: the @samp{_MIN}/@samp{_MAX} macros in @code{<limits.h>}.
++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.
++
++@item
++A function declared external in one block and then used after the end of
++the block.
++
++@item
++A @code{switch} statement has an operand of type @code{long}.
++
++@item
++A non-@code{static} function declaration follows a @code{static} one.
++This construct is not accepted by some traditional C compilers.
++
++@item
++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.
++
++@item
++Usage of ISO string concatenation is detected.
++
++@item
++Initialization of automatic aggregates.
++
++@item
++Identifier conflicts with labels. Traditional C lacks a separate
++namespace for labels.
++
++@item
++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.@: @code{__STDC__} to avoid missing
++initializer warnings and relies on default initialization to zero in the
++traditional C case.
++
++@item
++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 @option{-Wtraditional-conversion}.
++
++@item
++Use of ISO C style function definitions. This warning intentionally is
++@emph{not} issued for prototype declarations or variadic functions
++because these ISO C features will appear in your code when using
++libiberty's traditional C compatibility macros, @code{PARAMS} and
++@code{VPARAMS}. This warning is also bypassed for nested functions
++because that feature is already a GCC extension and thus not relevant to
++traditional C compatibility.
++@end itemize
++
++@item -Wtraditional-conversion @r{(C and Objective-C only)}
++@opindex Wtraditional-conversion
++@opindex Wno-traditional-conversion
++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.
++
++@item -Wdeclaration-after-statement @r{(C and Objective-C only)}
++@opindex Wdeclaration-after-statement
++@opindex Wno-declaration-after-statement
++Warn when a declaration is found after a statement in a block. This
++construct, known from C++, was introduced with ISO C99 and is by default
++allowed in GCC@. It is not supported by ISO C90 and was not supported by
++GCC versions before GCC 3.0. @xref{Mixed Declarations}.
++
++@item -Wundef
++@opindex Wundef
++@opindex Wno-undef
++Warn if an undefined identifier is evaluated in an @samp{#if} directive.
++
++@item -Wno-endif-labels
++@opindex Wno-endif-labels
++@opindex Wendif-labels
++Do not warn whenever an @samp{#else} or an @samp{#endif} are followed by text.
++
++@item -Wshadow
++@opindex Wshadow
++@opindex Wno-shadow
++Warn whenever a local variable shadows another local variable, parameter or
++global variable or whenever a built-in function is shadowed.
++
++@item -Wlarger-than=@var{len}
++@opindex Wlarger-than=@var{len}
++@opindex Wlarger-than-@var{len}
++Warn whenever an object of larger than @var{len} bytes is defined.
++
++@item -Wframe-larger-than=@var{len}
++@opindex Wframe-larger-than
++Warn if the size of a function frame is larger than @var{len} bytes.
++The computation done to determine the stack frame size is approximate
++and not conservative.
++The actual requirements may be somewhat greater than @var{len}
++even if you do not get a warning. In addition, any space allocated
++via @code{alloca}, variable-length arrays, or related constructs
++is not included by the compiler when determining
++whether or not to issue a warning.
++
++@item -Wunsafe-loop-optimizations
++@opindex Wunsafe-loop-optimizations
++@opindex Wno-unsafe-loop-optimizations
++Warn if the loop cannot be optimized because the compiler could not
++assume anything on the bounds of the loop indices. With
++@option{-funsafe-loop-optimizations} warn if the compiler made
++such assumptions.
++
++@item -Wno-pedantic-ms-format @r{(MinGW targets only)}
++@opindex Wno-pedantic-ms-format
++@opindex Wpedantic-ms-format
++Disables the warnings about non-ISO @code{printf} / @code{scanf} format
++width specifiers @code{I32}, @code{I64}, and @code{I} used on Windows targets
++depending on the MS runtime, when you are using the options @option{-Wformat}
++and @option{-pedantic} without gnu-extensions.
++
++@item -Wpointer-arith
++@opindex Wpointer-arith
++@opindex Wno-pointer-arith
++Warn about anything that depends on the ``size of'' a function type or
++of @code{void}. GNU C assigns these types a size of 1, for
++convenience in calculations with @code{void *} pointers and pointers
++to functions. In C++, warn also when an arithmetic operation involves
++@code{NULL}. This warning is also enabled by @option{-pedantic}.
++
++@item -Wtype-limits
++@opindex Wtype-limits
++@opindex Wno-type-limits
++Warn if a comparison is always true or always false due to the limited
++range of the data type, but do not warn for constant expressions. For
++example, warn if an unsigned variable is compared against zero with
++@samp{<} or @samp{>=}. This warning is also enabled by
++@option{-Wextra}.
++
++@item -Wbad-function-cast @r{(C and Objective-C only)}
++@opindex Wbad-function-cast
++@opindex Wno-bad-function-cast
++Warn whenever a function call is cast to a non-matching type.
++For example, warn if @code{int malloc()} is cast to @code{anything *}.
++
++@item -Wc++-compat @r{(C and Objective-C only)}
++Warn about ISO C constructs that are outside of the common subset of
++ISO C and ISO C++, e.g.@: request for implicit conversion from
++@code{void *} to a pointer to non-@code{void} type.
++
++@item -Wc++0x-compat @r{(C++ and Objective-C++ only)}
++Warn about C++ constructs whose meaning differs between ISO C++ 1998 and
++ISO C++ 200x, e.g., identifiers in ISO C++ 1998 that will become keywords
++in ISO C++ 200x. This warning is enabled by @option{-Wall}.
++
++@item -Wcast-qual
++@opindex Wcast-qual
++@opindex Wno-cast-qual
++Warn whenever a pointer is cast so as to remove a type qualifier from
++the target type. For example, warn if a @code{const char *} is cast
++to an ordinary @code{char *}.
++
++@item -Wcast-align
++@opindex Wcast-align
++@opindex Wno-cast-align
++Warn whenever a pointer is cast such that the required alignment of the
++target is increased. For example, warn if a @code{char *} is cast to
++an @code{int *} on machines where integers can only be accessed at
++two- or four-byte boundaries.
++
++@item -Wwrite-strings
++@opindex Wwrite-strings
++@opindex Wno-write-strings
++When compiling C, give string constants the type @code{const
++char[@var{length}]} so that copying the address of one into a
++non-@code{const} @code{char *} pointer will get a warning. 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 @code{const} in declarations and prototypes. Otherwise, it will
++just be a nuisance. This is why we did not make @option{-Wall} request
++these warnings.
++
++When compiling C++, warn about the deprecated conversion from string
++literals to @code{char *}. This warning is enabled by default for C++
++programs.
++
++@item -Wclobbered
++@opindex Wclobbered
++@opindex Wno-clobbered
++Warn for variables that might be changed by @samp{longjmp} or
++@samp{vfork}. This warning is also enabled by @option{-Wextra}.
++
++@item -Wconversion
++@opindex Wconversion
++@opindex Wno-conversion
++Warn for implicit conversions that may alter a value. This includes
++conversions between real and integer, like @code{abs (x)} when
++@code{x} is @code{double}; conversions between signed and unsigned,
++like @code{unsigned ui = -1}; and conversions to smaller types, like
++@code{sqrtf (M_PI)}. Do not warn for explicit casts like @code{abs
++((int) x)} and @code{ui = (unsigned) -1}, or if the value is not
++changed by the conversion like in @code{abs (2.0)}. Warnings about
++conversions between signed and unsigned integers can be disabled by
++using @option{-Wno-sign-conversion}.
++
++For C++, also warn for conversions between @code{NULL} and non-pointer
++types; confusing overload resolution for user-defined conversions; and
++conversions that will never use a type conversion operator:
++conversions to @code{void}, the same type, a base class or a reference
++to them. Warnings about conversions between signed and unsigned
++integers are disabled by default in C++ unless
++@option{-Wsign-conversion} is explicitly enabled.
++
++@item -Wempty-body
++@opindex Wempty-body
++@opindex Wno-empty-body
++Warn if an empty body occurs in an @samp{if}, @samp{else} or @samp{do
++while} statement. This warning is also enabled by @option{-Wextra}.
++
++@item -Wenum-compare @r{(C++ and Objective-C++ only)}
++@opindex Wenum-compare
++@opindex Wno-enum-compare
++Warn about a comparison between values of different enum types. This
++warning is enabled by default.
++
++@item -Wsign-compare
++@opindex Wsign-compare
++@opindex Wno-sign-compare
++@cindex warning for comparison of signed and unsigned values
++@cindex comparison of signed and unsigned values, warning
++@cindex signed and unsigned values, comparison warning
++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 @option{-Wextra}; to get the other warnings
++of @option{-Wextra} without this warning, use @samp{-Wextra -Wno-sign-compare}.
++
++@item -Wsign-conversion
++@opindex Wsign-conversion
++@opindex Wno-sign-conversion
++Warn for implicit conversions that may change the sign of an integer
++value, like assigning a signed integer expression to an unsigned
++integer variable. An explicit cast silences the warning. In C, this
++option is enabled also by @option{-Wconversion}.
++
++@item -Waddress
++@opindex Waddress
++@opindex Wno-address
++Warn about suspicious uses of memory addresses. These include using
++the address of a function in a conditional expression, such as
++@code{void func(void); if (func)}, and comparisons against the memory
++address of a string literal, such as @code{if (x == "abc")}. Such
++uses typically indicate a programmer error: the address of a function
++always evaluates to true, so their use in a conditional usually
++indicate that the programmer forgot the parentheses in a function
++call; and comparisons against string literals result in unspecified
++behavior and are not portable in C, so they usually indicate that the
++programmer intended to use @code{strcmp}. This warning is enabled by
++@option{-Wall}.
++
++@item -Wlogical-op
++@opindex Wlogical-op
++@opindex Wno-logical-op
++Warn about suspicious uses of logical operators in expressions.
++This includes using logical operators in contexts where a
++bit-wise operator is likely to be expected.
++
++@item -Waggregate-return
++@opindex Waggregate-return
++@opindex Wno-aggregate-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.)
++
++@item -Wno-attributes
++@opindex Wno-attributes
++@opindex Wattributes
++Do not warn if an unexpected @code{__attribute__} is used, such as
++unrecognized attributes, function attributes applied to variables,
++etc. This will not stop errors for incorrect use of supported
++attributes.
++
++@item -Wno-builtin-macro-redefined
++@opindex Wno-builtin-macro-redefined
++@opindex Wbuiltin-macro-redefined
++Do not warn if certain built-in macros are redefined. This suppresses
++warnings for redefinition of @code{__TIMESTAMP__}, @code{__TIME__},
++@code{__DATE__}, @code{__FILE__}, and @code{__BASE_FILE__}.
++
++@item -Wstrict-prototypes @r{(C and Objective-C only)}
++@opindex Wstrict-prototypes
++@opindex Wno-strict-prototypes
++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.)
++
++@item -Wold-style-declaration @r{(C and Objective-C only)}
++@opindex Wold-style-declaration
++@opindex Wno-old-style-declaration
++Warn for obsolescent usages, according to the C Standard, in a
++declaration. For example, warn if storage-class specifiers like
++@code{static} are not the first things in a declaration. This warning
++is also enabled by @option{-Wextra}.
++
++@item -Wold-style-definition @r{(C and Objective-C only)}
++@opindex Wold-style-definition
++@opindex Wno-old-style-definition
++Warn if an old-style function definition is used. A warning is given
++even if there is a previous prototype.
++
++@item -Wmissing-parameter-type @r{(C and Objective-C only)}
++@opindex Wmissing-parameter-type
++@opindex Wno-missing-parameter-type
++A function parameter is declared without a type specifier in K&R-style
++functions:
++
++@smallexample
++void foo(bar) @{ @}
++@end smallexample
++
++This warning is also enabled by @option{-Wextra}.
++
++@item -Wmissing-prototypes @r{(C and Objective-C only)}
++@opindex Wmissing-prototypes
++@opindex Wno-missing-prototypes
++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.
++
++@item -Wmissing-declarations
++@opindex Wmissing-declarations
++@opindex Wno-missing-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. In C++, no warnings are issued for function templates,
++or for inline functions, or for functions in anonymous namespaces.
++
++@item -Wmissing-field-initializers
++@opindex Wmissing-field-initializers
++@opindex Wno-missing-field-initializers
++@opindex W
++@opindex Wextra
++@opindex Wno-extra
++Warn if a structure's initializer has some fields missing. For
++example, the following code would cause such a warning, because
++@code{x.h} is implicitly zero:
++
++@smallexample
++struct s @{ int f, g, h; @};
++struct s x = @{ 3, 4 @};
++@end smallexample
++
++This option does not warn about designated initializers, so the following
++modification would not trigger a warning:
++
++@smallexample
++struct s @{ int f, g, h; @};
++struct s x = @{ .f = 3, .g = 4 @};
++@end smallexample
++
++This warning is included in @option{-Wextra}. To get other @option{-Wextra}
++warnings without this one, use @samp{-Wextra -Wno-missing-field-initializers}.
++
++@item -Wmissing-noreturn
++@opindex Wmissing-noreturn
++@opindex Wno-missing-noreturn
++Warn about functions which might be candidates for attribute @code{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 @code{noreturn} attribute, otherwise subtle code generation
++bugs could be introduced. You will not get a warning for @code{main} in
++hosted C environments.
++
++@item -Wmissing-format-attribute
++@opindex Wmissing-format-attribute
++@opindex Wno-missing-format-attribute
++@opindex Wformat
++@opindex Wno-format
++Warn about function pointers which might be candidates for @code{format}
++attributes. Note these are only possible candidates, not absolute ones.
++GCC will guess that function pointers with @code{format} attributes that
++are used in assignment, initialization, parameter passing or return
++statements should have a corresponding @code{format} attribute in the
++resulting type. I.e.@: the left-hand side of the assignment or
++initialization, the type of the parameter variable, or the return type
++of the containing function respectively should also have a @code{format}
++attribute to avoid the warning.
++
++GCC will also warn about function definitions which might be
++candidates for @code{format} attributes. Again, these are only
++possible candidates. GCC will guess that @code{format} attributes
++might be appropriate for any function that calls a function like
++@code{vprintf} or @code{vscanf}, but this might not always be the
++case, and some functions for which @code{format} attributes are
++appropriate may not be detected.
++
++@item -Wno-multichar
++@opindex Wno-multichar
++@opindex Wmultichar
++Do not warn if a multicharacter constant (@samp{'FOOF'}) is used.
++Usually they indicate a typo in the user's code, as they have
++implementation-defined values, and should not be used in portable code.
++
++@item -Wnormalized=<none|id|nfc|nfkc>
++@opindex Wnormalized=
++@cindex NFC
++@cindex NFKC
++@cindex character set, input normalization
++In ISO C and ISO C++, two identifiers are different if they are
++different sequences of characters. However, sometimes when characters
++outside the basic ASCII character set are used, you can have two
++different character sequences that look the same. To avoid confusion,
++the ISO 10646 standard sets out some @dfn{normalization rules} which
++when applied ensure that two sequences that look the same are turned into
++the same sequence. GCC can warn you if you are using identifiers which
++have not been normalized; this option controls that warning.
++
++There are four levels of warning that GCC supports. The default is
++@option{-Wnormalized=nfc}, which warns about any identifier which is
++not in the ISO 10646 ``C'' normalized form, @dfn{NFC}. NFC is the
++recommended form for most uses.
++
++Unfortunately, there are some characters which ISO C and ISO C++ allow
++in identifiers that when turned into NFC aren't allowable as
++identifiers. That is, there's no way to use these symbols in portable
++ISO C or C++ and have all your identifiers in NFC@.
++@option{-Wnormalized=id} suppresses the warning for these characters.
++It is hoped that future versions of the standards involved will correct
++this, which is why this option is not the default.
++
++You can switch the warning off for all characters by writing
++@option{-Wnormalized=none}. You would only want to do this if you
++were using some other normalization scheme (like ``D''), because
++otherwise you can easily create bugs that are literally impossible to see.
++
++Some characters in ISO 10646 have distinct meanings but look identical
++in some fonts or display methodologies, especially once formatting has
++been applied. For instance @code{\u207F}, ``SUPERSCRIPT LATIN SMALL
++LETTER N'', will display just like a regular @code{n} which has been
++placed in a superscript. ISO 10646 defines the @dfn{NFKC}
++normalization scheme to convert all these into a standard form as
++well, and GCC will warn if your code is not in NFKC if you use
++@option{-Wnormalized=nfkc}. This warning is comparable to warning
++about every identifier that contains the letter O because it might be
++confused with the digit 0, and so is not the default, but may be
++useful as a local coding convention if the programming environment is
++unable to be fixed to display these characters distinctly.
++
++@item -Wno-deprecated
++@opindex Wno-deprecated
++@opindex Wdeprecated
++Do not warn about usage of deprecated features. @xref{Deprecated Features}.
++
++@item -Wno-deprecated-declarations
++@opindex Wno-deprecated-declarations
++@opindex Wdeprecated-declarations
++Do not warn about uses of functions (@pxref{Function Attributes}),
++variables (@pxref{Variable Attributes}), and types (@pxref{Type
++Attributes}) marked as deprecated by using the @code{deprecated}
++attribute.
++
++@item -Wno-overflow
++@opindex Wno-overflow
++@opindex Woverflow
++Do not warn about compile-time overflow in constant expressions.
++
++@item -Woverride-init @r{(C and Objective-C only)}
++@opindex Woverride-init
++@opindex Wno-override-init
++@opindex W
++@opindex Wextra
++@opindex Wno-extra
++Warn if an initialized field without side effects is overridden when
++using designated initializers (@pxref{Designated Inits, , Designated
++Initializers}).
++
++This warning is included in @option{-Wextra}. To get other
++@option{-Wextra} warnings without this one, use @samp{-Wextra
++-Wno-override-init}.
++
++@item -Wpacked
++@opindex Wpacked
++@opindex Wno-packed
++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 @code{f.x} in @code{struct bar}
++will be misaligned even though @code{struct bar} does not itself
++have the packed attribute:
++
++@smallexample
++@group
++struct foo @{
++ int x;
++ char a, b, c, d;
++@} __attribute__((packed));
++struct bar @{
++ char z;
++ struct foo f;
++@};
++@end group
++@end smallexample
++
++@item -Wpacked-bitfield-compat
++@opindex Wpacked-bitfield-compat
++@opindex Wno-packed-bitfield-compat
++The 4.1, 4.2 and 4.3 series of GCC ignore the @code{packed} attribute
++on bit-fields of type @code{char}. This has been fixed in GCC 4.4 but
++the change can lead to differences in the structure layout. GCC
++informs you when the offset of such a field has changed in GCC 4.4.
++For example there is no longer a 4-bit padding between field @code{a}
++and @code{b} in this structure:
++
++@smallexample
++struct foo
++@{
++ char a:4;
++ char b:8;
++@} __attribute__ ((packed));
++@end smallexample
++
++This warning is enabled by default. Use
++@option{-Wno-packed-bitfield-compat} to disable this warning.
++
++@item -Wpadded
++@opindex Wpadded
++@opindex Wno-padded
++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.
++
++@item -Wredundant-decls
++@opindex Wredundant-decls
++@opindex Wno-redundant-decls
++Warn if anything is declared more than once in the same scope, even in
++cases where multiple declaration is valid and changes nothing.
++
++@item -Wnested-externs @r{(C and Objective-C only)}
++@opindex Wnested-externs
++@opindex Wno-nested-externs
++Warn if an @code{extern} declaration is encountered within a function.
++
++@item -Wunreachable-code
++@opindex Wunreachable-code
++@opindex Wno-unreachable-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 @option{-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.
++
++@item -Winline
++@opindex Winline
++@opindex Wno-inline
++Warn if a function can not be inlined and it was declared as inline.
++Even with this option, the compiler will not warn about failures to
++inline functions declared in system headers.
++
++The compiler uses a variety of heuristics to determine whether or not
++to inline a function. For example, the compiler takes into account
++the size of the function being inlined and the amount of inlining
++that has already been done in the current function. Therefore,
++seemingly insignificant changes in the source program can cause the
++warnings produced by @option{-Winline} to appear or disappear.
++
++@item -Wno-invalid-offsetof @r{(C++ and Objective-C++ only)}
++@opindex Wno-invalid-offsetof
++@opindex Winvalid-offsetof
++Suppress warnings from applying the @samp{offsetof} macro to a non-POD
++type. According to the 1998 ISO C++ standard, applying @samp{offsetof}
++to a non-POD type is undefined. In existing C++ implementations,
++however, @samp{offsetof} typically gives meaningful results even when
++applied to certain kinds of non-POD types. (Such as a simple
++@samp{struct} that fails to be a POD type only by virtue of having a
++constructor.) This flag is for users who are aware that they are
++writing nonportable code and who have deliberately chosen to ignore the
++warning about it.
++
++The restrictions on @samp{offsetof} may be relaxed in a future version
++of the C++ standard.
++
++@item -Wno-int-to-pointer-cast @r{(C and Objective-C only)}
++@opindex Wno-int-to-pointer-cast
++@opindex Wint-to-pointer-cast
++Suppress warnings from casts to pointer type of an integer of a
++different size.
++
++@item -Wno-pointer-to-int-cast @r{(C and Objective-C only)}
++@opindex Wno-pointer-to-int-cast
++@opindex Wpointer-to-int-cast
++Suppress warnings from casts from a pointer to an integer type of a
++different size.
++
++@item -Winvalid-pch
++@opindex Winvalid-pch
++@opindex Wno-invalid-pch
++Warn if a precompiled header (@pxref{Precompiled Headers}) is found in
++the search path but can't be used.
++
++@item -Wlong-long
++@opindex Wlong-long
++@opindex Wno-long-long
++Warn if @samp{long long} type is used. This is default. To inhibit
++the warning messages, use @option{-Wno-long-long}. Flags
++@option{-Wlong-long} and @option{-Wno-long-long} are taken into account
++only when @option{-pedantic} flag is used.
++
++@item -Wvariadic-macros
++@opindex Wvariadic-macros
++@opindex Wno-variadic-macros
++Warn if variadic macros are used in pedantic ISO C90 mode, or the GNU
++alternate syntax when in pedantic ISO C99 mode. This is default.
++To inhibit the warning messages, use @option{-Wno-variadic-macros}.
++
++@item -Wvla
++@opindex Wvla
++@opindex Wno-vla
++Warn if variable length array is used in the code.
++@option{-Wno-vla} will prevent the @option{-pedantic} warning of
++the variable length array.
++
++@item -Wvolatile-register-var
++@opindex Wvolatile-register-var
++@opindex Wno-volatile-register-var
++Warn if a register variable is declared volatile. The volatile
++modifier does not inhibit all optimizations that may eliminate reads
++and/or writes to register variables. This warning is enabled by
++@option{-Wall}.
++
++@item -Wdisabled-optimization
++@opindex Wdisabled-optimization
++@opindex Wno-disabled-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.
++
++@item -Wpointer-sign @r{(C and Objective-C only)}
++@opindex Wpointer-sign
++@opindex Wno-pointer-sign
++Warn for pointer argument passing or assignment with different signedness.
++This option is only supported for C and Objective-C@. It is implied by
++@option{-Wall} and by @option{-pedantic}, which can be disabled with
++@option{-Wno-pointer-sign}.
++
++@item -Wstack-protector
++@opindex Wstack-protector
++@opindex Wno-stack-protector
++This option is only active when @option{-fstack-protector} is active. It
++warns about functions that will not be protected against stack smashing.
++
++@item -Wno-mudflap
++@opindex Wno-mudflap
++Suppress warnings about constructs that cannot be instrumented by
++@option{-fmudflap}.
++
++@item -Woverlength-strings
++@opindex Woverlength-strings
++@opindex Wno-overlength-strings
++Warn about string constants which are longer than the ``minimum
++maximum'' length specified in the C standard. Modern compilers
++generally allow string constants which are much longer than the
++standard's minimum limit, but very portable programs should avoid
++using longer strings.
++
++The limit applies @emph{after} string constant concatenation, and does
++not count the trailing NUL@. In C89, the limit was 509 characters; in
++C99, it was raised to 4095. C++98 does not specify a normative
++minimum maximum, so we do not diagnose overlength strings in C++@.
++
++This option is implied by @option{-pedantic}, and can be disabled with
++@option{-Wno-overlength-strings}.
++@end table
++
++@node Debugging Options
++@section Options for Debugging Your Program or GCC
++@cindex options, debugging
++@cindex debugging information options
++
++GCC has various special options that are used for debugging
++either your program or GCC:
++
++@table @gcctabopt
++@item -g
++@opindex g
++Produce debugging information in the operating system's native format
++(stabs, COFF, XCOFF, or DWARF 2)@. GDB can work with this debugging
++information.
++
++On most systems that use stabs format, @option{-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 @option{-gstabs+}, @option{-gstabs},
++@option{-gxcoff+}, @option{-gxcoff}, or @option{-gvms} (see below).
++
++GCC allows you to use @option{-g} with
++@option{-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.
++
++@item -ggdb
++@opindex 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.
++
++@item -gstabs
++@opindex 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.
++
++@item -feliminate-unused-debug-symbols
++@opindex feliminate-unused-debug-symbols
++Produce debugging information in stabs format (if that is supported),
++for only symbols that are actually used.
++
++@item -femit-class-debug-always
++Instead of emitting debugging information for a C++ class in only one
++object file, emit it in all object files using the class. This option
++should be used only with debuggers that are unable to handle the way GCC
++normally emits debugging information for classes because using this
++option will increase the size of debugging information by as much as a
++factor of two.
++
++@item -gstabs+
++@opindex 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.
++
++@item -gcoff
++@opindex 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.
++
++@item -gxcoff
++@opindex 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.
++
++@item -gxcoff+
++@opindex 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.
++
++@item -gdwarf-2
++@opindex gdwarf-2
++Produce debugging information in DWARF version 2 format (if that is
++supported). This is the format used by DBX on IRIX 6. With this
++option, GCC uses features of DWARF version 3 when they are useful;
++version 3 is upward compatible with version 2, but may still cause
++problems for older debuggers.
++
++@item -gvms
++@opindex gvms
++Produce debugging information in VMS debug format (if that is
++supported). This is the format used by DEBUG on VMS systems.
++
++@item -g@var{level}
++@itemx -ggdb@var{level}
++@itemx -gstabs@var{level}
++@itemx -gcoff@var{level}
++@itemx -gxcoff@var{level}
++@itemx -gvms@var{level}
++Request debugging information and also use @var{level} to specify how
++much information. The default level is 2.
++
++Level 0 produces no debug information at all. Thus, @option{-g0} negates
++@option{-g}.
++
++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 @option{-g3}.
++
++@option{-gdwarf-2} does not accept a concatenated debug level, because
++GCC used to support an option @option{-gdwarf} that meant to generate
++debug information in version 1 of the DWARF format (which is very
++different from version 2), and it would have been too confusing. That
++debug format is long obsolete, but the option cannot be changed now.
++Instead use an additional @option{-g@var{level}} option to change the
++debug level for DWARF2.
++
++@item -feliminate-dwarf2-dups
++@opindex feliminate-dwarf2-dups
++Compress DWARF2 debugging information by eliminating duplicated
++information about each symbol. This option only makes sense when
++generating DWARF2 debugging information with @option{-gdwarf-2}.
++
++@item -femit-struct-debug-baseonly
++Emit debug information for struct-like types
++only when the base name of the compilation source file
++matches the base name of file in which the struct was defined.
++
++This option substantially reduces the size of debugging information,
++but at significant potential loss in type information to the debugger.
++See @option{-femit-struct-debug-reduced} for a less aggressive option.
++See @option{-femit-struct-debug-detailed} for more detailed control.
++
++This option works only with DWARF 2.
++
++@item -femit-struct-debug-reduced
++Emit debug information for struct-like types
++only when the base name of the compilation source file
++matches the base name of file in which the type was defined,
++unless the struct is a template or defined in a system header.
++
++This option significantly reduces the size of debugging information,
++with some potential loss in type information to the debugger.
++See @option{-femit-struct-debug-baseonly} for a more aggressive option.
++See @option{-femit-struct-debug-detailed} for more detailed control.
++
++This option works only with DWARF 2.
++
++@item -femit-struct-debug-detailed@r{[}=@var{spec-list}@r{]}
++Specify the struct-like types
++for which the compiler will generate debug information.
++The intent is to reduce duplicate struct debug information
++between different object files within the same program.
++
++This option is a detailed version of
++@option{-femit-struct-debug-reduced} and @option{-femit-struct-debug-baseonly},
++which will serve for most needs.
++
++A specification has the syntax
++[@samp{dir:}|@samp{ind:}][@samp{ord:}|@samp{gen:}](@samp{any}|@samp{sys}|@samp{base}|@samp{none})
++
++The optional first word limits the specification to
++structs that are used directly (@samp{dir:}) or used indirectly (@samp{ind:}).
++A struct type is used directly when it is the type of a variable, member.
++Indirect uses arise through pointers to structs.
++That is, when use of an incomplete struct would be legal, the use is indirect.
++An example is
++@samp{struct one direct; struct two * indirect;}.
++
++The optional second word limits the specification to
++ordinary structs (@samp{ord:}) or generic structs (@samp{gen:}).
++Generic structs are a bit complicated to explain.
++For C++, these are non-explicit specializations of template classes,
++or non-template classes within the above.
++Other programming languages have generics,
++but @samp{-femit-struct-debug-detailed} does not yet implement them.
++
++The third word specifies the source files for those
++structs for which the compiler will emit debug information.
++The values @samp{none} and @samp{any} have the normal meaning.
++The value @samp{base} means that
++the base of name of the file in which the type declaration appears
++must match the base of the name of the main compilation file.
++In practice, this means that
++types declared in @file{foo.c} and @file{foo.h} will have debug information,
++but types declared in other header will not.
++The value @samp{sys} means those types satisfying @samp{base}
++or declared in system or compiler headers.
++
++You may need to experiment to determine the best settings for your application.
++
++The default is @samp{-femit-struct-debug-detailed=all}.
++
++This option works only with DWARF 2.
++
++@item -fno-merge-debug-strings
++@opindex fmerge-debug-strings
++@opindex fno-merge-debug-strings
++Direct the linker to not merge together strings in the debugging
++information which are identical in different object files. Merging is
++not supported by all assemblers or linkers. Merging decreases the size
++of the debug information in the output file at the cost of increasing
++link processing time. Merging is enabled by default.
++
++@item -fdebug-prefix-map=@var{old}=@var{new}
++@opindex fdebug-prefix-map
++When compiling files in directory @file{@var{old}}, record debugging
++information describing them as in @file{@var{new}} instead.
++
++@item -fno-dwarf2-cfi-asm
++@opindex fdwarf2-cfi-asm
++@opindex fno-dwarf2-cfi-asm
++Emit DWARF 2 unwind info as compiler generated @code{.eh_frame} section
++instead of using GAS @code{.cfi_*} directives.
++
++@cindex @command{prof}
++@item -p
++@opindex p
++Generate extra code to write profile information suitable for the
++analysis program @command{prof}. You must use this option when compiling
++the source files you want data about, and you must also use it when
++linking.
++
++@cindex @command{gprof}
++@item -pg
++@opindex pg
++Generate extra code to write profile information suitable for the
++analysis program @command{gprof}. You must use this option when compiling
++the source files you want data about, and you must also use it when
++linking.
++
++@item -Q
++@opindex Q
++Makes the compiler print out each function name as it is compiled, and
++print some statistics about each pass when it finishes.
++
++@item -ftime-report
++@opindex ftime-report
++Makes the compiler print some statistics about the time consumed by each
++pass when it finishes.
++
++@item -fmem-report
++@opindex fmem-report
++Makes the compiler print some statistics about permanent memory
++allocation when it finishes.
++
++@item -fpre-ipa-mem-report
++@opindex fpre-ipa-mem-report
++@item -fpost-ipa-mem-report
++@opindex fpost-ipa-mem-report
++Makes the compiler print some statistics about permanent memory
++allocation before or after interprocedural optimization.
++
++@item -fprofile-arcs
++@opindex fprofile-arcs
++Add code so that program flow @dfn{arcs} are instrumented. During
++execution the program records how many times each branch and call is
++executed and how many times it is taken or returns. When the compiled
++program exits it saves this data to a file called
++@file{@var{auxname}.gcda} for each source file. The data may be used for
++profile-directed optimizations (@option{-fbranch-probabilities}), or for
++test coverage analysis (@option{-ftest-coverage}). Each object file's
++@var{auxname} is generated from the name of the output file, if
++explicitly specified and it is not the final executable, otherwise it is
++the basename of the source file. In both cases any suffix is removed
++(e.g.@: @file{foo.gcda} for input file @file{dir/foo.c}, or
++@file{dir/foo.gcda} for output file specified as @option{-o dir/foo.o}).
++@xref{Cross-profiling}.
++
++@cindex @command{gcov}
++@item --coverage
++@opindex coverage
++
++This option is used to compile and link code instrumented for coverage
++analysis. The option is a synonym for @option{-fprofile-arcs}
++@option{-ftest-coverage} (when compiling) and @option{-lgcov} (when
++linking). See the documentation for those options for more details.
++
++@itemize
++
++@item
++Compile the source files with @option{-fprofile-arcs} plus optimization
++and code generation options. For test coverage analysis, use the
++additional @option{-ftest-coverage} option. You do not need to profile
++every source file in a program.
++
++@item
++Link your object files with @option{-lgcov} or @option{-fprofile-arcs}
++(the latter implies the former).
++
++@item
++Run the program on a representative workload to generate the arc profile
++information. This may be repeated any number of times. You can run
++concurrent instances of your program, and provided that the file system
++supports locking, the data files will be correctly updated. Also
++@code{fork} calls are detected and correctly handled (double counting
++will not happen).
++
++@item
++For profile-directed optimizations, compile the source files again with
++the same optimization and code generation options plus
++@option{-fbranch-probabilities} (@pxref{Optimize Options,,Options that
++Control Optimization}).
++
++@item
++For test coverage analysis, use @command{gcov} to produce human readable
++information from the @file{.gcno} and @file{.gcda} files. Refer to the
++@command{gcov} documentation for further information.
++
++@end itemize
++
++With @option{-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.
++
++@need 2000
++@item -ftest-coverage
++@opindex ftest-coverage
++Produce a notes file that the @command{gcov} code-coverage utility
++(@pxref{Gcov,, @command{gcov}---a Test Coverage Program}) can use to
++show program coverage. Each source file's note file is called
++@file{@var{auxname}.gcno}. Refer to the @option{-fprofile-arcs} option
++above for a description of @var{auxname} and instructions on how to
++generate test coverage data. Coverage data will match the source files
++more closely, if you do not optimize.
++
++@item -fdbg-cnt-list
++@opindex fdbg-cnt-list
++Print the name and the counter upperbound for all debug counters.
++
++@item -fdbg-cnt=@var{counter-value-list}
++@opindex fdbg-cnt
++Set the internal debug counter upperbound. @var{counter-value-list}
++is a comma-separated list of @var{name}:@var{value} pairs
++which sets the upperbound of each debug counter @var{name} to @var{value}.
++All debug counters have the initial upperbound of @var{UINT_MAX},
++thus dbg_cnt() returns true always unless the upperbound is set by this option.
++e.g. With -fdbg-cnt=dce:10,tail_call:0
++dbg_cnt(dce) will return true only for first 10 invocations
++and dbg_cnt(tail_call) will return false always.
++
++@item -d@var{letters}
++@itemx -fdump-rtl-@var{pass}
++@opindex d
++Says to make debugging dumps during compilation at times specified by
++@var{letters}. This is used for debugging the RTL-based passes of the
++compiler. The file names for most of the dumps are made by appending a
++pass number and a word to the @var{dumpname}. @var{dumpname} is generated
++from the name of the output file, if explicitly specified and it is not
++an executable, otherwise it is the basename of the source file. These
++switches may have different effects when @option{-E} is used for
++preprocessing.
++
++Debug dumps can be enabled with a @option{-fdump-rtl} switch or some
++@option{-d} option @var{letters}. Here are the possible
++letters for use in @var{pass} and @var{letters}, and their meanings:
++
++@table @gcctabopt
++
++@item -fdump-rtl-alignments
++@opindex fdump-rtl-alignments
++Dump after branch alignments have been computed.
++
++@item -fdump-rtl-asmcons
++@opindex fdump-rtl-asmcons
++Dump after fixing rtl statements that have unsatisfied in/out constraints.
++
++@item -fdump-rtl-auto_inc_dec
++@opindex fdump-rtl-auto_inc_dec
++Dump after auto-inc-dec discovery. This pass is only run on
++architectures that have auto inc or auto dec instructions.
++
++@item -fdump-rtl-barriers
++@opindex fdump-rtl-barriers
++Dump after cleaning up the barrier instructions.
++
++@item -fdump-rtl-bbpart
++@opindex fdump-rtl-bbpart
++Dump after partitioning hot and cold basic blocks.
++
++@item -fdump-rtl-bbro
++@opindex fdump-rtl-bbro
++Dump after block reordering.
++
++@item -fdump-rtl-btl1
++@itemx -fdump-rtl-btl2
++@opindex fdump-rtl-btl2
++@opindex fdump-rtl-btl2
++@option{-fdump-rtl-btl1} and @option{-fdump-rtl-btl2} enable dumping
++after the two branch
++target load optimization passes.
++
++@item -fdump-rtl-bypass
++@opindex fdump-rtl-bypass
++Dump after jump bypassing and control flow optimizations.
++
++@item -fdump-rtl-combine
++@opindex fdump-rtl-combine
++Dump after the RTL instruction combination pass.
++
++@item -fdump-rtl-compgotos
++@opindex fdump-rtl-compgotos
++Dump after duplicating the computed gotos.
++
++@item -fdump-rtl-ce1
++@itemx -fdump-rtl-ce2
++@itemx -fdump-rtl-ce3
++@opindex fdump-rtl-ce1
++@opindex fdump-rtl-ce2
++@opindex fdump-rtl-ce3
++@option{-fdump-rtl-ce1}, @option{-fdump-rtl-ce2}, and
++@option{-fdump-rtl-ce3} enable dumping after the three
++if conversion passes.
++
++@itemx -fdump-rtl-cprop_hardreg
++@opindex fdump-rtl-cprop_hardreg
++Dump after hard register copy propagation.
++
++@itemx -fdump-rtl-csa
++@opindex fdump-rtl-csa
++Dump after combining stack adjustments.
++
++@item -fdump-rtl-cse1
++@itemx -fdump-rtl-cse2
++@opindex fdump-rtl-cse1
++@opindex fdump-rtl-cse2
++@option{-fdump-rtl-cse1} and @option{-fdump-rtl-cse2} enable dumping after
++the two common sub-expression elimination passes.
++
++@itemx -fdump-rtl-dce
++@opindex fdump-rtl-dce
++Dump after the standalone dead code elimination passes.
++
++@itemx -fdump-rtl-dbr
++@opindex fdump-rtl-dbr
++Dump after delayed branch scheduling.
++
++@item -fdump-rtl-dce1
++@itemx -fdump-rtl-dce2
++@opindex fdump-rtl-dce1
++@opindex fdump-rtl-dce2
++@option{-fdump-rtl-dce1} and @option{-fdump-rtl-dce2} enable dumping after
++the two dead store elimination passes.
++
++@item -fdump-rtl-eh
++@opindex fdump-rtl-eh
++Dump after finalization of EH handling code.
++
++@item -fdump-rtl-eh_ranges
++@opindex fdump-rtl-eh_ranges
++Dump after conversion of EH handling range regions.
++
++@item -fdump-rtl-expand
++@opindex fdump-rtl-expand
++Dump after RTL generation.
++
++@item -fdump-rtl-fwprop1
++@itemx -fdump-rtl-fwprop2
++@opindex fdump-rtl-fwprop1
++@opindex fdump-rtl-fwprop2
++@option{-fdump-rtl-fwprop1} and @option{-fdump-rtl-fwprop2} enable
++dumping after the two forward propagation passes.
++
++@item -fdump-rtl-gcse1
++@itemx -fdump-rtl-gcse2
++@opindex fdump-rtl-gcse1
++@opindex fdump-rtl-gcse2
++@option{-fdump-rtl-gcse1} and @option{-fdump-rtl-gcse2} enable dumping
++after global common subexpression elimination.
++
++@item -fdump-rtl-init-regs
++@opindex fdump-rtl-init-regs
++Dump after the initialization of the registers.
++
++@item -fdump-rtl-initvals
++@opindex fdump-rtl-initvals
++Dump after the computation of the initial value sets.
++
++@itemx -fdump-rtl-into_cfglayout
++@opindex fdump-rtl-into_cfglayout
++Dump after converting to cfglayout mode.
++
++@item -fdump-rtl-ira
++@opindex fdump-rtl-ira
++Dump after iterated register allocation.
++
++@item -fdump-rtl-jump
++@opindex fdump-rtl-jump
++Dump after the second jump optimization.
++
++@item -fdump-rtl-loop2
++@opindex fdump-rtl-loop2
++@option{-fdump-rtl-loop2} enables dumping after the rtl
++loop optimization passes.
++
++@item -fdump-rtl-mach
++@opindex fdump-rtl-mach
++Dump after performing the machine dependent reorganization pass, if that
++pass exists.
++
++@item -fdump-rtl-mode_sw
++@opindex fdump-rtl-mode_sw
++Dump after removing redundant mode switches.
++
++@item -fdump-rtl-rnreg
++@opindex fdump-rtl-rnreg
++Dump after register renumbering.
++
++@itemx -fdump-rtl-outof_cfglayout
++@opindex fdump-rtl-outof_cfglayout
++Dump after converting from cfglayout mode.
++
++@item -fdump-rtl-peephole2
++@opindex fdump-rtl-peephole2
++Dump after the peephole pass.
++
++@item -fdump-rtl-postreload
++@opindex fdump-rtl-postreload
++Dump after post-reload optimizations.
++
++@itemx -fdump-rtl-pro_and_epilogue
++@opindex fdump-rtl-pro_and_epilogue
++Dump after generating the function pro and epilogues.
++
++@item -fdump-rtl-regmove
++@opindex fdump-rtl-regmove
++Dump after the register move pass.
++
++@item -fdump-rtl-sched1
++@itemx -fdump-rtl-sched2
++@opindex fdump-rtl-sched1
++@opindex fdump-rtl-sched2
++@option{-fdump-rtl-sched1} and @option{-fdump-rtl-sched2} enable dumping
++after the basic block scheduling passes.
++
++@item -fdump-rtl-see
++@opindex fdump-rtl-see
++Dump after sign extension elimination.
++
++@item -fdump-rtl-seqabstr
++@opindex fdump-rtl-seqabstr
++Dump after common sequence discovery.
++
++@item -fdump-rtl-shorten
++@opindex fdump-rtl-shorten
++Dump after shortening branches.
++
++@item -fdump-rtl-sibling
++@opindex fdump-rtl-sibling
++Dump after sibling call optimizations.
++
++@item -fdump-rtl-split1
++@itemx -fdump-rtl-split2
++@itemx -fdump-rtl-split3
++@itemx -fdump-rtl-split4
++@itemx -fdump-rtl-split5
++@opindex fdump-rtl-split1
++@opindex fdump-rtl-split2
++@opindex fdump-rtl-split3
++@opindex fdump-rtl-split4
++@opindex fdump-rtl-split5
++@option{-fdump-rtl-split1}, @option{-fdump-rtl-split2},
++@option{-fdump-rtl-split3}, @option{-fdump-rtl-split4} and
++@option{-fdump-rtl-split5} enable dumping after five rounds of
++instruction splitting.
++
++@item -fdump-rtl-sms
++@opindex fdump-rtl-sms
++Dump after modulo scheduling. This pass is only run on some
++architectures.
++
++@item -fdump-rtl-stack
++@opindex fdump-rtl-stack
++Dump after conversion from GCC's "flat register file" registers to the
++x87's stack-like registers. This pass is only run on x86 variants.
++
++@item -fdump-rtl-subreg1
++@itemx -fdump-rtl-subreg2
++@opindex fdump-rtl-subreg1
++@opindex fdump-rtl-subreg2
++@option{-fdump-rtl-subreg1} and @option{-fdump-rtl-subreg2} enable dumping after
++the two subreg expansion passes.
++
++@item -fdump-rtl-unshare
++@opindex fdump-rtl-unshare
++Dump after all rtl has been unshared.
++
++@item -fdump-rtl-vartrack
++@opindex fdump-rtl-vartrack
++Dump after variable tracking.
++
++@item -fdump-rtl-vregs
++@opindex fdump-rtl-vregs
++Dump after converting virtual registers to hard registers.
++
++@item -fdump-rtl-web
++@opindex fdump-rtl-web
++Dump after live range splitting.
++
++@item -fdump-rtl-regclass
++@itemx -fdump-rtl-subregs_of_mode_init
++@itemx -fdump-rtl-subregs_of_mode_finish
++@itemx -fdump-rtl-dfinit
++@itemx -fdump-rtl-dfinish
++@opindex fdump-rtl-regclass
++@opindex fdump-rtl-subregs_of_mode_init
++@opindex fdump-rtl-subregs_of_mode_finish
++@opindex fdump-rtl-dfinit
++@opindex fdump-rtl-dfinish
++These dumps are defined but always produce empty files.
++
++@item -fdump-rtl-all
++@opindex fdump-rtl-all
++Produce all the dumps listed above.
++
++@item -dA
++@opindex dA
++Annotate the assembler output with miscellaneous debugging information.
++
++@item -dD
++@opindex dD
++Dump all macro definitions, at the end of preprocessing, in addition to
++normal output.
++
++@item -dH
++@opindex dH
++Produce a core dump whenever an error occurs.
++
++@item -dm
++@opindex dm
++Print statistics on memory usage, at the end of the run, to
++standard error.
++
++@item -dp
++@opindex dp
++Annotate the assembler output with a comment indicating which
++pattern and alternative was used. The length of each instruction is
++also printed.
++
++@item -dP
++@opindex dP
++Dump the RTL in the assembler output as a comment before each instruction.
++Also turns on @option{-dp} annotation.
++
++@item -dv
++@opindex dv
++For each of the other indicated dump files (@option{-fdump-rtl-@var{pass}}),
++dump a representation of the control flow graph suitable for viewing with VCG
++to @file{@var{file}.@var{pass}.vcg}.
++
++@item -dx
++@opindex dx
++Just generate RTL for a function instead of compiling it. Usually used
++with @option{-fdump-rtl-expand}.
++
++@item -dy
++@opindex dy
++Dump debugging information during parsing, to standard error.
++@end table
++
++@item -fdump-noaddr
++@opindex fdump-noaddr
++When doing debugging dumps, suppress address output. This makes it more
++feasible to use diff on debugging dumps for compiler invocations with
++different compiler binaries and/or different
++text / bss / data / heap / stack / dso start locations.
++
++@item -fdump-unnumbered
++@opindex fdump-unnumbered
++When doing debugging dumps, suppress instruction numbers and address output.
++This makes it more feasible to use diff on debugging dumps for compiler
++invocations with different options, in particular with and without
++@option{-g}.
++
++@item -fdump-translation-unit @r{(C++ only)}
++@itemx -fdump-translation-unit-@var{options} @r{(C++ only)}
++@opindex fdump-translation-unit
++Dump a representation of the tree structure for the entire translation
++unit to a file. The file name is made by appending @file{.tu} to the
++source file name. If the @samp{-@var{options}} form is used, @var{options}
++controls the details of the dump as described for the
++@option{-fdump-tree} options.
++
++@item -fdump-class-hierarchy @r{(C++ only)}
++@itemx -fdump-class-hierarchy-@var{options} @r{(C++ only)}
++@opindex fdump-class-hierarchy
++Dump a representation of each class's hierarchy and virtual function
++table layout to a file. The file name is made by appending @file{.class}
++to the source file name. If the @samp{-@var{options}} form is used,
++@var{options} controls the details of the dump as described for the
++@option{-fdump-tree} options.
++
++@item -fdump-ipa-@var{switch}
++@opindex fdump-ipa
++Control the dumping at various stages of inter-procedural analysis
++language tree to a file. The file name is generated by appending a switch
++specific suffix to the source file name. The following dumps are possible:
++
++@table @samp
++@item all
++Enables all inter-procedural analysis dumps.
++
++@item cgraph
++Dumps information about call-graph optimization, unused function removal,
++and inlining decisions.
++
++@item inline
++Dump after function inlining.
++
++@end table
++
++@item -fdump-statistics-@var{option}
++@opindex -fdump-statistics
++Enable and control dumping of pass statistics in a separate file. The
++file name is generated by appending a suffix ending in @samp{.statistics}
++to the source file name. If the @samp{-@var{option}} form is used,
++@samp{-stats} will cause counters to be summed over the whole compilation unit
++while @samp{-details} will dump every event as the passes generate them.
++The default with no option is to sum counters for each function compiled.
++
++@item -fdump-tree-@var{switch}
++@itemx -fdump-tree-@var{switch}-@var{options}
++@opindex fdump-tree
++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 @samp{-@var{options}}
++form is used, @var{options} is a list of @samp{-} 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
++
++@table @samp
++@item 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.
++@item 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. When dumping pretty-printed
++trees, this option inhibits dumping the bodies of control structures.
++@item raw
++Print a raw representation of the tree. By default, trees are
++pretty-printed into a C-like representation.
++@item details
++Enable more detailed dumps (not honored by every dump option).
++@item stats
++Enable dumping various statistics about the pass (not honored by every dump
++option).
++@item blocks
++Enable showing basic block boundaries (disabled in raw dumps).
++@item vops
++Enable showing virtual operands for every statement.
++@item lineno
++Enable showing line numbers for statements.
++@item uid
++Enable showing the unique ID (@code{DECL_UID}) for each variable.
++@item verbose
++Enable showing the tree dump for each statement.
++@item all
++Turn on all options, except @option{raw}, @option{slim}, @option{verbose}
++and @option{lineno}.
++@end table
++
++The following tree dumps are possible:
++@table @samp
++
++@item original
++Dump before any tree based optimization, to @file{@var{file}.original}.
++
++@item optimized
++Dump after all tree based optimization, to @file{@var{file}.optimized}.
++
++@item gimple
++@opindex fdump-tree-gimple
++Dump each function before and after the gimplification pass to a file. The
++file name is made by appending @file{.gimple} to the source file name.
++
++@item cfg
++@opindex fdump-tree-cfg
++Dump the control flow graph of each function to a file. The file name is
++made by appending @file{.cfg} to the source file name.
++
++@item vcg
++@opindex fdump-tree-vcg
++Dump the control flow graph of each function to a file in VCG format. The
++file name is made by appending @file{.vcg} to the source file name. Note
++that if the file contains more than one function, the generated file cannot
++be used directly by VCG@. You will need to cut and paste each function's
++graph into its own separate file first.
++
++@item ch
++@opindex fdump-tree-ch
++Dump each function after copying loop headers. The file name is made by
++appending @file{.ch} to the source file name.
++
++@item ssa
++@opindex fdump-tree-ssa
++Dump SSA related information to a file. The file name is made by appending
++@file{.ssa} to the source file name.
++
++@item alias
++@opindex fdump-tree-alias
++Dump aliasing information for each function. The file name is made by
++appending @file{.alias} to the source file name.
++
++@item ccp
++@opindex fdump-tree-ccp
++Dump each function after CCP@. The file name is made by appending
++@file{.ccp} to the source file name.
++
++@item storeccp
++@opindex fdump-tree-storeccp
++Dump each function after STORE-CCP@. The file name is made by appending
++@file{.storeccp} to the source file name.
++
++@item pre
++@opindex fdump-tree-pre
++Dump trees after partial redundancy elimination. The file name is made
++by appending @file{.pre} to the source file name.
++
++@item fre
++@opindex fdump-tree-fre
++Dump trees after full redundancy elimination. The file name is made
++by appending @file{.fre} to the source file name.
++
++@item copyprop
++@opindex fdump-tree-copyprop
++Dump trees after copy propagation. The file name is made
++by appending @file{.copyprop} to the source file name.
++
++@item store_copyprop
++@opindex fdump-tree-store_copyprop
++Dump trees after store copy-propagation. The file name is made
++by appending @file{.store_copyprop} to the source file name.
++
++@item dce
++@opindex fdump-tree-dce
++Dump each function after dead code elimination. The file name is made by
++appending @file{.dce} to the source file name.
++
++@item mudflap
++@opindex fdump-tree-mudflap
++Dump each function after adding mudflap instrumentation. The file name is
++made by appending @file{.mudflap} to the source file name.
++
++@item sra
++@opindex fdump-tree-sra
++Dump each function after performing scalar replacement of aggregates. The
++file name is made by appending @file{.sra} to the source file name.
++
++@item sink
++@opindex fdump-tree-sink
++Dump each function after performing code sinking. The file name is made
++by appending @file{.sink} to the source file name.
++
++@item dom
++@opindex fdump-tree-dom
++Dump each function after applying dominator tree optimizations. The file
++name is made by appending @file{.dom} to the source file name.
++
++@item dse
++@opindex fdump-tree-dse
++Dump each function after applying dead store elimination. The file
++name is made by appending @file{.dse} to the source file name.
++
++@item phiopt
++@opindex fdump-tree-phiopt
++Dump each function after optimizing PHI nodes into straightline code. The file
++name is made by appending @file{.phiopt} to the source file name.
++
++@item forwprop
++@opindex fdump-tree-forwprop
++Dump each function after forward propagating single use variables. The file
++name is made by appending @file{.forwprop} to the source file name.
++
++@item copyrename
++@opindex fdump-tree-copyrename
++Dump each function after applying the copy rename optimization. The file
++name is made by appending @file{.copyrename} to the source file name.
++
++@item nrv
++@opindex fdump-tree-nrv
++Dump each function after applying the named return value optimization on
++generic trees. The file name is made by appending @file{.nrv} to the source
++file name.
++
++@item vect
++@opindex fdump-tree-vect
++Dump each function after applying vectorization of loops. The file name is
++made by appending @file{.vect} to the source file name.
++
++@item vrp
++@opindex fdump-tree-vrp
++Dump each function after Value Range Propagation (VRP). The file name
++is made by appending @file{.vrp} to the source file name.
++
++@item all
++@opindex fdump-tree-all
++Enable all the available tree dumps with the flags provided in this option.
++@end table
++
++@item -ftree-vectorizer-verbose=@var{n}
++@opindex ftree-vectorizer-verbose
++This option controls the amount of debugging output the vectorizer prints.
++This information is written to standard error, unless
++@option{-fdump-tree-all} or @option{-fdump-tree-vect} is specified,
++in which case it is output to the usual dump listing file, @file{.vect}.
++For @var{n}=0 no diagnostic information is reported.
++If @var{n}=1 the vectorizer reports each loop that got vectorized,
++and the total number of loops that got vectorized.
++If @var{n}=2 the vectorizer also reports non-vectorized loops that passed
++the first analysis phase (vect_analyze_loop_form) - i.e.@: countable,
++inner-most, single-bb, single-entry/exit loops. This is the same verbosity
++level that @option{-fdump-tree-vect-stats} uses.
++Higher verbosity levels mean either more information dumped for each
++reported loop, or same amount of information reported for more loops:
++If @var{n}=3, alignment related information is added to the reports.
++If @var{n}=4, data-references related information (e.g.@: memory dependences,
++memory access-patterns) is added to the reports.
++If @var{n}=5, the vectorizer reports also non-vectorized inner-most loops
++that did not pass the first analysis phase (i.e., may not be countable, or
++may have complicated control-flow).
++If @var{n}=6, the vectorizer reports also non-vectorized nested loops.
++For @var{n}=7, all the information the vectorizer generates during its
++analysis and transformation is reported. This is the same verbosity level
++that @option{-fdump-tree-vect-details} uses.
++
++@item -frandom-seed=@var{string}
++@opindex frandom-string
++This option provides a seed that GCC uses when it would otherwise use
++random numbers. It is used to generate certain symbol names
++that have to be different in every compiled file. It is also used to
++place unique stamps in coverage data files and the object files that
++produce them. You can use the @option{-frandom-seed} option to produce
++reproducibly identical object files.
++
++The @var{string} should be different for every file you compile.
++
++@item -fsched-verbose=@var{n}
++@opindex fsched-verbose
++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 @option{-fdump-rtl-sched1} or
++@option{-fdump-rtl-sched2} is specified, in which case it is output
++to the usual dump listing file, @file{.sched} or @file{.sched2}
++respectively. However for @var{n} greater than nine, the output is
++always printed to standard error.
++
++For @var{n} greater than zero, @option{-fsched-verbose} outputs the
++same information as @option{-fdump-rtl-sched1} and @option{-fdump-rtl-sched2}.
++For @var{n} greater than one, it also output basic block probabilities,
++detailed ready list information and unit/insn info. For @var{n} greater
++than two, it includes RTL at abort point, control-flow and regions info.
++And for @var{n} over four, @option{-fsched-verbose} also includes
++dependence info.
++
++@item -save-temps
++@opindex 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 @file{foo.c} with @samp{-c -save-temps} would produce files
++@file{foo.i} and @file{foo.s}, as well as @file{foo.o}. This creates a
++preprocessed @file{foo.i} output file even though the compiler now
++normally uses an integrated preprocessor.
++
++When used in combination with the @option{-x} command line option,
++@option{-save-temps} is sensible enough to avoid over writing an
++input source file with the same extension as an intermediate file.
++The corresponding intermediate file may be obtained by renaming the
++source file before using @option{-save-temps}.
++
++@item -time
++@opindex 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:
++
++@smallexample
++# cc1 0.12 0.01
++# as 0.00 0.01
++@end smallexample
++
++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.
++
++@item -fvar-tracking
++@opindex fvar-tracking
++Run variable tracking pass. It computes where variables are stored at each
++position in code. Better debugging information is then generated
++(if the debugging information format supports this information).
++
++It is enabled by default when compiling with optimization (@option{-Os},
++@option{-O}, @option{-O2}, @dots{}), debugging information (@option{-g}) and
++the debug info format supports it.
++
++@item -print-file-name=@var{library}
++@opindex print-file-name
++Print the full absolute name of the library file @var{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.
++
++@item -print-multi-directory
++@opindex 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 @env{GCC_EXEC_PREFIX}.
++
++@item -print-multi-lib
++@opindex 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
++@samp{;}, and each switch starts with an @samp{@@} instead of the
++@samp{-}, without spaces between multiple switches. This is supposed to
++ease shell-processing.
++
++@item -print-prog-name=@var{program}
++@opindex print-prog-name
++Like @option{-print-file-name}, but searches for a program such as @samp{cpp}.
++
++@item -print-libgcc-file-name
++@opindex print-libgcc-file-name
++Same as @option{-print-file-name=libgcc.a}.
++
++This is useful when you use @option{-nostdlib} or @option{-nodefaultlibs}
++but you do want to link with @file{libgcc.a}. You can do
++
++@smallexample
++gcc -nostdlib @var{files}@dots{} `gcc -print-libgcc-file-name`
++@end smallexample
++
++@item -print-search-dirs
++@opindex print-search-dirs
++Print the name of the configured installation directory and a list of
++program and library directories @command{gcc} will search---and don't do anything else.
++
++This is useful when @command{gcc} prints the error message
++@samp{installation problem, cannot exec cpp0: No such file or directory}.
++To resolve this you either need to put @file{cpp0} and the other compiler
++components where @command{gcc} expects to find them, or you can set the environment
++variable @env{GCC_EXEC_PREFIX} to the directory where you installed them.
++Don't forget the trailing @samp{/}.
++@xref{Environment Variables}.
++
++@item -print-sysroot
++@opindex print-sysroot
++Print the target sysroot directory that will be used during
++compilation. This is the target sysroot specified either at configure
++time or using the @option{--sysroot} option, possibly with an extra
++suffix that depends on compilation options. If no target sysroot is
++specified, the option prints nothing.
++
++@item -print-sysroot-headers-suffix
++@opindex print-sysroot-headers-suffix
++Print the suffix added to the target sysroot when searching for
++headers, or give an error if the compiler is not configured with such
++a suffix---and don't do anything else.
++
++@item -dumpmachine
++@opindex dumpmachine
++Print the compiler's target machine (for example,
++@samp{i686-pc-linux-gnu})---and don't do anything else.
++
++@item -dumpversion
++@opindex dumpversion
++Print the compiler version (for example, @samp{3.0})---and don't do
++anything else.
++
++@item -dumpspecs
++@opindex dumpspecs
++Print the compiler's built-in specs---and don't do anything else. (This
++is used when GCC itself is being built.) @xref{Spec Files}.
++
++@item -feliminate-unused-debug-types
++@opindex feliminate-unused-debug-types
++Normally, when producing DWARF2 output, GCC will emit debugging
++information for all types declared in a compilation
++unit, regardless of whether or not they are actually used
++in that compilation unit. Sometimes this is useful, such as
++if, in the debugger, you want to cast a value to a type that is
++not actually used in your program (but is declared). More often,
++however, this results in a significant amount of wasted space.
++With this option, GCC will avoid producing debug symbol output
++for types that are nowhere used in the source file being compiled.
++@end table
++
++@node Optimize Options
++@section Options That Control Optimization
++@cindex optimize options
++@cindex options, optimization
++
++These options control various sorts of optimizations.
++
++Without any optimization option, 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.
++
++Turning on optimization flags makes the compiler attempt to improve
++the performance and/or code size at the expense of compilation time
++and possibly the ability to debug the program.
++
++The compiler performs optimization based on the knowledge it has of the
++program. Compiling multiple files at once to a single output file mode allows
++the compiler to use information gained from all of the files when compiling
++each of them.
++
++Not all optimizations are controlled directly by a flag. Only
++optimizations that have a flag are listed.
++
++@table @gcctabopt
++@item -O
++@itemx -O1
++@opindex O
++@opindex O1
++Optimize. Optimizing compilation takes somewhat more time, and a lot
++more memory for a large function.
++
++With @option{-O}, the compiler tries to reduce code size and execution
++time, without performing any optimizations that take a great deal of
++compilation time.
++
++@option{-O} turns on the following optimization flags:
++@gccoptlist{
++-fauto-inc-dec @gol
++-fcprop-registers @gol
++-fdce @gol
++-fdefer-pop @gol
++-fdelayed-branch @gol
++-fdse @gol
++-fguess-branch-probability @gol
++-fif-conversion2 @gol
++-fif-conversion @gol
++-finline-small-functions @gol
++-fipa-pure-const @gol
++-fipa-reference @gol
++-fmerge-constants
++-fsplit-wide-types @gol
++-ftree-builtin-call-dce @gol
++-ftree-ccp @gol
++-ftree-ch @gol
++-ftree-copyrename @gol
++-ftree-dce @gol
++-ftree-dominator-opts @gol
++-ftree-dse @gol
++-ftree-fre @gol
++-ftree-sra @gol
++-ftree-ter @gol
++-funit-at-a-time}
++
++@option{-O} also turns on @option{-fomit-frame-pointer} on machines
++where doing so does not interfere with debugging.
++
++@item -O2
++@opindex O2
++Optimize even more. GCC performs nearly all supported optimizations
++that do not involve a space-speed tradeoff.
++As compared to @option{-O}, this option increases both compilation time
++and the performance of the generated code.
++
++@option{-O2} turns on all optimization flags specified by @option{-O}. It
++also turns on the following optimization flags:
++@gccoptlist{-fthread-jumps @gol
++-falign-functions -falign-jumps @gol
++-falign-loops -falign-labels @gol
++-fcaller-saves @gol
++-fcrossjumping @gol
++-fcse-follow-jumps -fcse-skip-blocks @gol
++-fdelete-null-pointer-checks @gol
++-fexpensive-optimizations @gol
++-fgcse -fgcse-lm @gol
++-findirect-inlining @gol
++-foptimize-sibling-calls @gol
++-fpeephole2 @gol
++-fregmove @gol
++-freorder-blocks -freorder-functions @gol
++-frerun-cse-after-loop @gol
++-fsched-interblock -fsched-spec @gol
++-fschedule-insns -fschedule-insns2 @gol
++-fstrict-aliasing -fstrict-overflow @gol
++-ftree-switch-conversion @gol
++-ftree-pre @gol
++-ftree-vrp}
++
++Please note the warning under @option{-fgcse} about
++invoking @option{-O2} on programs that use computed gotos.
++
++@item -O3
++@opindex O3
++Optimize yet more. @option{-O3} turns on all optimizations specified
++by @option{-O2} and also turns on the @option{-finline-functions},
++@option{-funswitch-loops}, @option{-fpredictive-commoning},
++@option{-fgcse-after-reload} and @option{-ftree-vectorize} options.
++
++@item -O0
++@opindex O0
++Reduce compilation time and make debugging produce the expected
++results. This is the default.
++
++@item -Os
++@opindex Os
++Optimize for size. @option{-Os} enables all @option{-O2} optimizations that
++do not typically increase code size. It also performs further
++optimizations designed to reduce code size.
++
++@option{-Os} disables the following optimization flags:
++@gccoptlist{-falign-functions -falign-jumps -falign-loops @gol
++-falign-labels -freorder-blocks -freorder-blocks-and-partition @gol
++-fprefetch-loop-arrays -ftree-vect-loop-version}
++
++If you use multiple @option{-O} options, with or without level numbers,
++the last such option is the one that is effective.
++@end table
++
++Options of the form @option{-f@var{flag}} specify machine-independent
++flags. Most flags have both positive and negative forms; the negative
++form of @option{-ffoo} would be @option{-fno-foo}. In the table
++below, only one of the forms is listed---the one you typically will
++use. You can figure out the other form by either removing @samp{no-}
++or adding it.
++
++The following options control specific optimizations. They are either
++activated by @option{-O} options or are related to ones that are. You
++can use the following flags in the rare cases when ``fine-tuning'' of
++optimizations to be performed is desired.
++
++@table @gcctabopt
++@item -fno-default-inline
++@opindex 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
++@w{@option{-O}}, member functions defined inside class scope are compiled
++inline by default; i.e., you don't need to add @samp{inline} in front of
++the member function name.
++
++@item -fno-defer-pop
++@opindex 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.
++
++Disabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fforward-propagate
++@opindex fforward-propagate
++Perform a forward propagation pass on RTL@. The pass tries to combine two
++instructions and checks if the result can be simplified. If loop unrolling
++is active, two passes are performed and the second is scheduled after
++loop unrolling.
++
++This option is enabled by default at optimization levels @option{-O2},
++@option{-O3}, @option{-Os}.
++
++@item -fomit-frame-pointer
++@opindex 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. @strong{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 @code{FRAME_POINTER_REQUIRED} controls
++whether a target machine supports this flag. @xref{Registers,,Register
++Usage, gccint, GNU Compiler Collection (GCC) Internals}.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -foptimize-sibling-calls
++@opindex foptimize-sibling-calls
++Optimize sibling and tail recursive calls.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fno-inline
++@opindex fno-inline
++Don't pay attention to the @code{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.
++
++@item -finline-small-functions
++@opindex finline-small-functions
++Integrate functions into their callers when their body is smaller than expected
++function call code (so overall size of program gets smaller). The compiler
++heuristically decides which functions are simple enough to be worth integrating
++in this way.
++
++Enabled at level @option{-O2}.
++
++@item -findirect-inlining
++@opindex findirect-inlining
++Inline also indirect calls that are discovered to be known at compile
++time thanks to previous inlining. This option has any effect only
++when inlining itself is turned on by the @option{-finline-functions}
++or @option{-finline-small-functions} options.
++
++Enabled at level @option{-O2}.
++
++@item -finline-functions
++@opindex 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 @code{static}, then the function is normally not output as
++assembler code in its own right.
++
++Enabled at level @option{-O3}.
++
++@item -finline-functions-called-once
++@opindex finline-functions-called-once
++Consider all @code{static} functions called once for inlining into their
++caller even if they are not marked @code{inline}. If a call to a given
++function is integrated, then the function is not output as assembler code
++in its own right.
++
++Enabled at levels @option{-O1}, @option{-O2}, @option{-O3} and @option{-Os}.
++
++@item -fearly-inlining
++@opindex fearly-inlining
++Inline functions marked by @code{always_inline} and functions whose body seems
++smaller than the function call overhead early before doing
++@option{-fprofile-generate} instrumentation and real inlining pass. Doing so
++makes profiling significantly cheaper and usually inlining faster on programs
++having large chains of nested wrapper functions.
++
++Enabled by default.
++
++@item -finline-limit=@var{n}
++@opindex finline-limit
++By default, GCC limits the size of functions that can be inlined. This flag
++allows coarse control of this limit. @var{n} is the size of functions that
++can be inlined in number of pseudo instructions.
++
++Inlining is actually controlled by a number of parameters, which may be
++specified individually by using @option{--param @var{name}=@var{value}}.
++The @option{-finline-limit=@var{n}} option sets some of these parameters
++as follows:
++
++@table @gcctabopt
++@item max-inline-insns-single
++is set to @var{n}/2.
++@item max-inline-insns-auto
++is set to @var{n}/2.
++@end table
++
++See below for a documentation of the individual
++parameters controlling inlining and for the defaults of these parameters.
++
++@emph{Note:} there may be no value to @option{-finline-limit} that results
++in default behavior.
++
++@emph{Note:} pseudo instruction represents, in this particular context, an
++abstract measurement of function's size. In no way does it represent a count
++of assembly instructions and as such its exact meaning might change from one
++release to an another.
++
++@item -fkeep-inline-functions
++@opindex fkeep-inline-functions
++In C, emit @code{static} functions that are declared @code{inline}
++into the object file, even if the function has been inlined into all
++of its callers. This switch does not affect functions using the
++@code{extern inline} extension in GNU C89@. In C++, emit any and all
++inline functions into the object file.
++
++@item -fkeep-static-consts
++@opindex fkeep-static-consts
++Emit variables declared @code{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 @option{-fno-keep-static-consts} option.
++
++@item -fmerge-constants
++@opindex fmerge-constants
++Attempt to merge identical constants (string constants and floating point
++constants) across compilation units.
++
++This option is the default for optimized compilation if the assembler and
++linker support it. Use @option{-fno-merge-constants} to inhibit this
++behavior.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fmerge-all-constants
++@opindex fmerge-all-constants
++Attempt to merge identical constants and identical variables.
++
++This option implies @option{-fmerge-constants}. In addition to
++@option{-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 variable, including multiple
++instances of the same variable in recursive calls, to have distinct locations,
++so using this option will result in non-conforming
++behavior.
++
++@item -fmodulo-sched
++@opindex fmodulo-sched
++Perform swing modulo scheduling immediately before the first scheduling
++pass. This pass looks at innermost loops and reorders their
++instructions by overlapping different iterations.
++
++@item -fmodulo-sched-allow-regmoves
++@opindex fmodulo-sched-allow-regmoves
++Perform more aggressive SMS based modulo scheduling with register moves
++allowed. By setting this flag certain anti-dependences edges will be
++deleted which will trigger the generation of reg-moves based on the
++life-range analysis. This option is effective only with
++@option{-fmodulo-sched} enabled.
++
++@item -fno-branch-count-reg
++@opindex 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.
++
++The default is @option{-fbranch-count-reg}.
++
++@item -fno-function-cse
++@opindex 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.
++
++The default is @option{-ffunction-cse}
++
++@item -fno-zero-initialized-in-bss
++@opindex fno-zero-initialized-in-bss
++If the target supports a BSS section, GCC by default puts variables that
++are initialized to zero into BSS@. This can save space in the resulting
++code.
++
++This option turns off this behavior because some programs explicitly
++rely on variables going to the data section. E.g., so that the
++resulting executable can find the beginning of that section and/or make
++assumptions based on that.
++
++The default is @option{-fzero-initialized-in-bss}.
++
++@item -fmudflap -fmudflapth -fmudflapir
++@opindex fmudflap
++@opindex fmudflapth
++@opindex fmudflapir
++@cindex bounds checking
++@cindex mudflap
++For front-ends that support it (C and C++), instrument all risky
++pointer/array dereferencing operations, some standard library
++string/heap functions, and some other associated constructs with
++range/validity tests. Modules so instrumented should be immune to
++buffer overflows, invalid heap use, and some other classes of C/C++
++programming errors. The instrumentation relies on a separate runtime
++library (@file{libmudflap}), which will be linked into a program if
++@option{-fmudflap} is given at link time. Run-time behavior of the
++instrumented program is controlled by the @env{MUDFLAP_OPTIONS}
++environment variable. See @code{env MUDFLAP_OPTIONS=-help a.out}
++for its options.
++
++Use @option{-fmudflapth} instead of @option{-fmudflap} to compile and to
++link if your program is multi-threaded. Use @option{-fmudflapir}, in
++addition to @option{-fmudflap} or @option{-fmudflapth}, if
++instrumentation should ignore pointer reads. This produces less
++instrumentation (and therefore faster execution) and still provides
++some protection against outright memory corrupting writes, but allows
++erroneously read data to propagate within a program.
++
++@item -fthread-jumps
++@opindex 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.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fsplit-wide-types
++@opindex fsplit-wide-types
++When using a type that occupies multiple registers, such as @code{long
++long} on a 32-bit system, split the registers apart and allocate them
++independently. This normally generates better code for those types,
++but may make debugging more difficult.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3},
++@option{-Os}.
++
++@item -fcse-follow-jumps
++@opindex fcse-follow-jumps
++In common subexpression elimination (CSE), scan through jump instructions
++when the target of the jump is not reached by any other path. For
++example, when CSE encounters an @code{if} statement with an
++@code{else} clause, CSE will follow the jump when the condition
++tested is false.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fcse-skip-blocks
++@opindex fcse-skip-blocks
++This is similar to @option{-fcse-follow-jumps}, but causes CSE to
++follow jumps which conditionally skip over blocks. When CSE
++encounters a simple @code{if} statement with no else clause,
++@option{-fcse-skip-blocks} causes CSE to follow the jump around the
++body of the @code{if}.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -frerun-cse-after-loop
++@opindex frerun-cse-after-loop
++Re-run common subexpression elimination after loop optimizations has been
++performed.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fgcse
++@opindex fgcse
++Perform a global common subexpression elimination pass.
++This pass also performs global constant and copy propagation.
++
++@emph{Note:} When compiling a program using computed gotos, a GCC
++extension, you may get better runtime performance if you disable
++the global common subexpression elimination pass by adding
++@option{-fno-gcse} to the command line.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fgcse-lm
++@opindex fgcse-lm
++When @option{-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.
++
++Enabled by default when gcse is enabled.
++
++@item -fgcse-sm
++@opindex fgcse-sm
++When @option{-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 @option{-fgcse-lm},
++loops containing a load/store sequence can be changed to a load before
++the loop and a store after the loop.
++
++Not enabled at any optimization level.
++
++@item -fgcse-las
++@opindex fgcse-las
++When @option{-fgcse-las} is enabled, the global common subexpression
++elimination pass eliminates redundant loads that come after stores to the
++same memory location (both partial and full redundancies).
++
++Not enabled at any optimization level.
++
++@item -fgcse-after-reload
++@opindex fgcse-after-reload
++When @option{-fgcse-after-reload} is enabled, a redundant load elimination
++pass is performed after reload. The purpose of this pass is to cleanup
++redundant spilling.
++
++@item -funsafe-loop-optimizations
++@opindex funsafe-loop-optimizations
++If given, the loop optimizer will assume that loop indices do not
++overflow, and that the loops with nontrivial exit condition are not
++infinite. This enables a wider range of loop optimizations even if
++the loop optimizer itself cannot prove that these assumptions are valid.
++Using @option{-Wunsafe-loop-optimizations}, the compiler will warn you
++if it finds this kind of loop.
++
++@item -fcrossjumping
++@opindex fcrossjumping
++Perform cross-jumping transformation. This transformation unifies equivalent code and save code size. The
++resulting code may or may not perform better than without cross-jumping.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fauto-inc-dec
++@opindex fauto-inc-dec
++Combine increments or decrements of addresses with memory accesses.
++This pass is always skipped on architectures that do not have
++instructions to support this. Enabled by default at @option{-O} and
++higher on architectures that support this.
++
++@item -fdce
++@opindex fdce
++Perform dead code elimination (DCE) on RTL@.
++Enabled by default at @option{-O} and higher.
++
++@item -fdse
++@opindex fdse
++Perform dead store elimination (DSE) on RTL@.
++Enabled by default at @option{-O} and higher.
++
++@item -fif-conversion
++@opindex fif-conversion
++Attempt to transform conditional jumps into branch-less equivalents. This
++include use of conditional moves, min, max, set flags and abs instructions, and
++some tricks doable by standard arithmetics. The use of conditional execution
++on chips where it is available is controlled by @code{if-conversion2}.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fif-conversion2
++@opindex fif-conversion2
++Use conditional execution (where available) to transform conditional jumps into
++branch-less equivalents.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fdelete-null-pointer-checks
++@opindex 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
++@option{-fno-delete-null-pointer-checks} to disable this optimization
++for programs which depend on that behavior.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fexpensive-optimizations
++@opindex fexpensive-optimizations
++Perform a number of minor optimizations that are relatively expensive.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -foptimize-register-move
++@itemx -fregmove
++@opindex foptimize-register-move
++@opindex 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.
++
++Note @option{-fregmove} and @option{-foptimize-register-move} are the same
++optimization.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fira-algorithm=@var{algorithm}
++Use specified coloring algorithm for the integrated register
++allocator. The @var{algorithm} argument should be @code{priority} or
++@code{CB}. The first algorithm specifies Chow's priority coloring,
++the second one specifies Chaitin-Briggs coloring. The second
++algorithm can be unimplemented for some architectures. If it is
++implemented, it is the default because Chaitin-Briggs coloring as a
++rule generates a better code.
++
++@item -fira-region=@var{region}
++Use specified regions for the integrated register allocator. The
++@var{region} argument should be one of @code{all}, @code{mixed}, or
++@code{one}. The first value means using all loops as register
++allocation regions, the second value which is the default means using
++all loops except for loops with small register pressure as the
++regions, and third one means using all function as a single region.
++The first value can give best result for machines with small size and
++irregular register set, the third one results in faster and generates
++decent code and the smallest size code, and the default value usually
++give the best results in most cases and for most architectures.
++
++@item -fira-coalesce
++@opindex fira-coalesce
++Do optimistic register coalescing. This option might be profitable for
++architectures with big regular register files.
++
++@item -fno-ira-share-save-slots
++@opindex fno-ira-share-save-slots
++Switch off sharing stack slots used for saving call used hard
++registers living through a call. Each hard register will get a
++separate stack slot and as a result function stack frame will be
++bigger.
++
++@item -fno-ira-share-spill-slots
++@opindex fno-ira-share-spill-slots
++Switch off sharing stack slots allocated for pseudo-registers. Each
++pseudo-register which did not get a hard register will get a separate
++stack slot and as a result function stack frame will be bigger.
++
++@item -fira-verbose=@var{n}
++@opindex fira-verbose
++Set up how verbose dump file for the integrated register allocator
++will be. Default value is 5. If the value is greater or equal to 10,
++the dump file will be stderr as if the value were @var{n} minus 10.
++
++@item -fdelayed-branch
++@opindex fdelayed-branch
++If supported for the target machine, attempt to reorder instructions
++to exploit instruction slots available after delayed branch
++instructions.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fschedule-insns
++@opindex 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.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fschedule-insns2
++@opindex fschedule-insns2
++Similar to @option{-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.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fno-sched-interblock
++@opindex fno-sched-interblock
++Don't schedule instructions across basic blocks. This is normally
++enabled by default when scheduling before register allocation, i.e.@:
++with @option{-fschedule-insns} or at @option{-O2} or higher.
++
++@item -fno-sched-spec
++@opindex 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 @option{-fschedule-insns} or at @option{-O2} or higher.
++
++@item -fsched-spec-load
++@opindex fsched-spec-load
++Allow speculative motion of some load instructions. This only makes
++sense when scheduling before register allocation, i.e.@: with
++@option{-fschedule-insns} or at @option{-O2} or higher.
++
++@item -fsched-spec-load-dangerous
++@opindex fsched-spec-load-dangerous
++Allow speculative motion of more load instructions. This only makes
++sense when scheduling before register allocation, i.e.@: with
++@option{-fschedule-insns} or at @option{-O2} or higher.
++
++@item -fsched-stalled-insns
++@itemx -fsched-stalled-insns=@var{n}
++@opindex fsched-stalled-insns
++Define how many insns (if any) can be moved prematurely from the queue
++of stalled insns into the ready list, during the second scheduling pass.
++@option{-fno-sched-stalled-insns} means that no insns will be moved
++prematurely, @option{-fsched-stalled-insns=0} means there is no limit
++on how many queued insns can be moved prematurely.
++@option{-fsched-stalled-insns} without a value is equivalent to
++@option{-fsched-stalled-insns=1}.
++
++@item -fsched-stalled-insns-dep
++@itemx -fsched-stalled-insns-dep=@var{n}
++@opindex fsched-stalled-insns-dep
++Define how many insn groups (cycles) will be examined for a dependency
++on a stalled insn that is candidate for premature removal from the queue
++of stalled insns. This has an effect only during the second scheduling pass,
++and only if @option{-fsched-stalled-insns} is used.
++@option{-fno-sched-stalled-insns-dep} is equivalent to
++@option{-fsched-stalled-insns-dep=0}.
++@option{-fsched-stalled-insns-dep} without a value is equivalent to
++@option{-fsched-stalled-insns-dep=1}.
++
++@item -fsched2-use-superblocks
++@opindex fsched2-use-superblocks
++When scheduling after register allocation, do use superblock scheduling
++algorithm. Superblock scheduling allows motion across basic block boundaries
++resulting on faster schedules. This option is experimental, as not all machine
++descriptions used by GCC model the CPU closely enough to avoid unreliable
++results from the algorithm.
++
++This only makes sense when scheduling after register allocation, i.e.@: with
++@option{-fschedule-insns2} or at @option{-O2} or higher.
++
++@item -fsched2-use-traces
++@opindex fsched2-use-traces
++Use @option{-fsched2-use-superblocks} algorithm when scheduling after register
++allocation and additionally perform code duplication in order to increase the
++size of superblocks using tracer pass. See @option{-ftracer} for details on
++trace formation.
++
++This mode should produce faster but significantly longer programs. Also
++without @option{-fbranch-probabilities} the traces constructed may not
++match the reality and hurt the performance. This only makes
++sense when scheduling after register allocation, i.e.@: with
++@option{-fschedule-insns2} or at @option{-O2} or higher.
++
++@item -fsee
++@opindex fsee
++Eliminate redundant sign extension instructions and move the non-redundant
++ones to optimal placement using lazy code motion (LCM).
++
++@item -freschedule-modulo-scheduled-loops
++@opindex freschedule-modulo-scheduled-loops
++The modulo scheduling comes before the traditional scheduling, if a loop
++was modulo scheduled we may want to prevent the later scheduling passes
++from changing its schedule, we use this option to control that.
++
++@item -fselective-scheduling
++@opindex fselective-scheduling
++Schedule instructions using selective scheduling algorithm. Selective
++scheduling runs instead of the first scheduler pass.
++
++@item -fselective-scheduling2
++@opindex fselective-scheduling2
++Schedule instructions using selective scheduling algorithm. Selective
++scheduling runs instead of the second scheduler pass.
++
++@item -fsel-sched-pipelining
++@opindex fsel-sched-pipelining
++Enable software pipelining of innermost loops during selective scheduling.
++This option has no effect until one of @option{-fselective-scheduling} or
++@option{-fselective-scheduling2} is turned on.
++
++@item -fsel-sched-pipelining-outer-loops
++@opindex fsel-sched-pipelining-outer-loops
++When pipelining loops during selective scheduling, also pipeline outer loops.
++This option has no effect until @option{-fsel-sched-pipelining} is turned on.
++
++@item -fcaller-saves
++@opindex 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.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fconserve-stack
++@opindex fconserve-stack
++Attempt to minimize stack usage. The compiler will attempt to use less
++stack space, even if that makes the program slower. This option
++implies setting the @option{large-stack-frame} parameter to 100
++and the @option{large-stack-frame-growth} parameter to 400.
++
++@item -ftree-reassoc
++@opindex ftree-reassoc
++Perform reassociation on trees. This flag is enabled by default
++at @option{-O} and higher.
++
++@item -ftree-pre
++@opindex ftree-pre
++Perform partial redundancy elimination (PRE) on trees. This flag is
++enabled by default at @option{-O2} and @option{-O3}.
++
++@item -ftree-fre
++@opindex ftree-fre
++Perform full redundancy elimination (FRE) on trees. The difference
++between FRE and PRE is that FRE only considers expressions
++that are computed on all paths leading to the redundant computation.
++This analysis is faster than PRE, though it exposes fewer redundancies.
++This flag is enabled by default at @option{-O} and higher.
++
++@item -ftree-copy-prop
++@opindex ftree-copy-prop
++Perform copy propagation on trees. This pass eliminates unnecessary
++copy operations. This flag is enabled by default at @option{-O} and
++higher.
++
++@item -fipa-pure-const
++@opindex fipa-pure-const
++Discover which functions are pure or constant.
++Enabled by default at @option{-O} and higher.
++
++@item -fipa-reference
++@opindex fipa-reference
++Discover which static variables do not escape cannot escape the
++compilation unit.
++Enabled by default at @option{-O} and higher.
++
++@item -fipa-struct-reorg
++@opindex fipa-struct-reorg
++Perform structure reorganization optimization, that change C-like structures
++layout in order to better utilize spatial locality. This transformation is
++affective for programs containing arrays of structures. Available in two
++compilation modes: profile-based (enabled with @option{-fprofile-generate})
++or static (which uses built-in heuristics). Require @option{-fipa-type-escape}
++to provide the safety of this transformation. It works only in whole program
++mode, so it requires @option{-fwhole-program} and @option{-combine} to be
++enabled. Structures considered @samp{cold} by this transformation are not
++affected (see @option{--param struct-reorg-cold-struct-ratio=@var{value}}).
++
++With this flag, the program debug info reflects a new structure layout.
++
++@item -fipa-pta
++@opindex fipa-pta
++Perform interprocedural pointer analysis. This option is experimental
++and does not affect generated code.
++
++@item -fipa-cp
++@opindex fipa-cp
++Perform interprocedural constant propagation.
++This optimization analyzes the program to determine when values passed
++to functions are constants and then optimizes accordingly.
++This optimization can substantially increase performance
++if the application has constants passed to functions.
++This flag is enabled by default at @option{-O2}, @option{-Os} and @option{-O3}.
++
++@item -fipa-cp-clone
++@opindex fipa-cp-clone
++Perform function cloning to make interprocedural constant propagation stronger.
++When enabled, interprocedural constant propagation will perform function cloning
++when externally visible function can be called with constant arguments.
++Because this optimization can create multiple copies of functions,
++it may significantly increase code size
++(see @option{--param ipcp-unit-growth=@var{value}}).
++This flag is enabled by default at @option{-O3}.
++
++@item -fipa-matrix-reorg
++@opindex fipa-matrix-reorg
++Perform matrix flattening and transposing.
++Matrix flattening tries to replace a m-dimensional matrix
++with its equivalent n-dimensional matrix, where n < m.
++This reduces the level of indirection needed for accessing the elements
++of the matrix. The second optimization is matrix transposing that
++attempts to change the order of the matrix's dimensions in order to
++improve cache locality.
++Both optimizations need the @option{-fwhole-program} flag.
++Transposing is enabled only if profiling information is available.
++
++
++@item -ftree-sink
++@opindex ftree-sink
++Perform forward store motion on trees. This flag is
++enabled by default at @option{-O} and higher.
++
++@item -ftree-ccp
++@opindex ftree-ccp
++Perform sparse conditional constant propagation (CCP) on trees. This
++pass only operates on local scalar variables and is enabled by default
++at @option{-O} and higher.
++
++@item -ftree-switch-conversion
++Perform conversion of simple initializations in a switch to
++initializations from a scalar array. This flag is enabled by default
++at @option{-O2} and higher.
++
++@item -ftree-dce
++@opindex ftree-dce
++Perform dead code elimination (DCE) on trees. This flag is enabled by
++default at @option{-O} and higher.
++
++@item -ftree-builtin-call-dce
++@opindex ftree-builtin-call-dce
++Perform conditional dead code elimination (DCE) for calls to builtin functions
++that may set @code{errno} but are otherwise side-effect free. This flag is
++enabled by default at @option{-O2} and higher if @option{-Os} is not also
++specified.
++
++@item -ftree-dominator-opts
++@opindex ftree-dominator-opts
++Perform a variety of simple scalar cleanups (constant/copy
++propagation, redundancy elimination, range propagation and expression
++simplification) based on a dominator tree traversal. This also
++performs jump threading (to reduce jumps to jumps). This flag is
++enabled by default at @option{-O} and higher.
++
++@item -ftree-dse
++@opindex ftree-dse
++Perform dead store elimination (DSE) on trees. A dead store is a store into
++a memory location which will later be overwritten by another store without
++any intervening loads. In this case the earlier store can be deleted. This
++flag is enabled by default at @option{-O} and higher.
++
++@item -ftree-ch
++@opindex ftree-ch
++Perform loop header copying on trees. This is beneficial since it increases
++effectiveness of code motion optimizations. It also saves one jump. This flag
++is enabled by default at @option{-O} and higher. It is not enabled
++for @option{-Os}, since it usually increases code size.
++
++@item -ftree-loop-optimize
++@opindex ftree-loop-optimize
++Perform loop optimizations on trees. This flag is enabled by default
++at @option{-O} and higher.
++
++@item -ftree-loop-linear
++@opindex ftree-loop-linear
++Perform linear loop transformations on tree. This flag can improve cache
++performance and allow further loop optimizations to take place.
++
++@item -floop-interchange
++Perform loop interchange transformations on loops. Interchanging two
++nested loops switches the inner and outer loops. For example, given a
++loop like:
++@smallexample
++DO J = 1, M
++ DO I = 1, N
++ A(J, I) = A(J, I) * C
++ ENDDO
++ENDDO
++@end smallexample
++loop interchange will transform the loop as if the user had written:
++@smallexample
++DO I = 1, N
++ DO J = 1, M
++ A(J, I) = A(J, I) * C
++ ENDDO
++ENDDO
++@end smallexample
++which can be beneficial when @code{N} is larger than the caches,
++because in Fortran, the elements of an array are stored in memory
++contiguously by column, and the original loop iterates over rows,
++potentially creating at each access a cache miss. This optimization
++applies to all the languages supported by GCC and is not limited to
++Fortran. To use this code transformation, GCC has to be configured
++with @option{--with-ppl} and @option{--with-cloog} to enable the
++Graphite loop transformation infrastructure.
++
++@item -floop-strip-mine
++Perform loop strip mining transformations on loops. Strip mining
++splits a loop into two nested loops. The outer loop has strides
++equal to the strip size and the inner loop has strides of the
++original loop within a strip. For example, given a loop like:
++@smallexample
++DO I = 1, N
++ A(I) = A(I) + C
++ENDDO
++@end smallexample
++loop strip mining will transform the loop as if the user had written:
++@smallexample
++DO II = 1, N, 4
++ DO I = II, min (II + 3, N)
++ A(I) = A(I) + C
++ ENDDO
++ENDDO
++@end smallexample
++This optimization applies to all the languages supported by GCC and is
++not limited to Fortran. To use this code transformation, GCC has to
++be configured with @option{--with-ppl} and @option{--with-cloog} to
++enable the Graphite loop transformation infrastructure.
++
++@item -floop-block
++Perform loop blocking transformations on loops. Blocking strip mines
++each loop in the loop nest such that the memory accesses of the
++element loops fit inside caches. For example, given a loop like:
++@smallexample
++DO I = 1, N
++ DO J = 1, M
++ A(J, I) = B(I) + C(J)
++ ENDDO
++ENDDO
++@end smallexample
++loop blocking will transform the loop as if the user had written:
++@smallexample
++DO II = 1, N, 64
++ DO JJ = 1, M, 64
++ DO I = II, min (II + 63, N)
++ DO J = JJ, min (JJ + 63, M)
++ A(J, I) = B(I) + C(J)
++ ENDDO
++ ENDDO
++ ENDDO
++ENDDO
++@end smallexample
++which can be beneficial when @code{M} is larger than the caches,
++because the innermost loop will iterate over a smaller amount of data
++that can be kept in the caches. This optimization applies to all the
++languages supported by GCC and is not limited to Fortran. To use this
++code transformation, GCC has to be configured with @option{--with-ppl}
++and @option{--with-cloog} to enable the Graphite loop transformation
++infrastructure.
++
++@item -fcheck-data-deps
++@opindex fcheck-data-deps
++Compare the results of several data dependence analyzers. This option
++is used for debugging the data dependence analyzers.
++
++@item -ftree-loop-distribution
++Perform loop distribution. This flag can improve cache performance on
++big loop bodies and allow further loop optimizations, like
++parallelization or vectorization, to take place. For example, the loop
++@smallexample
++DO I = 1, N
++ A(I) = B(I) + C
++ D(I) = E(I) * F
++ENDDO
++@end smallexample
++is transformed to
++@smallexample
++DO I = 1, N
++ A(I) = B(I) + C
++ENDDO
++DO I = 1, N
++ D(I) = E(I) * F
++ENDDO
++@end smallexample
++
++@item -ftree-loop-im
++@opindex ftree-loop-im
++Perform loop invariant motion on trees. This pass moves only invariants that
++would be hard to handle at RTL level (function calls, operations that expand to
++nontrivial sequences of insns). With @option{-funswitch-loops} it also moves
++operands of conditions that are invariant out of the loop, so that we can use
++just trivial invariantness analysis in loop unswitching. The pass also includes
++store motion.
++
++@item -ftree-loop-ivcanon
++@opindex ftree-loop-ivcanon
++Create a canonical counter for number of iterations in the loop for that
++determining number of iterations requires complicated analysis. Later
++optimizations then may determine the number easily. Useful especially
++in connection with unrolling.
++
++@item -fivopts
++@opindex fivopts
++Perform induction variable optimizations (strength reduction, induction
++variable merging and induction variable elimination) on trees.
++
++@item -ftree-parallelize-loops=n
++@opindex ftree-parallelize-loops
++Parallelize loops, i.e., split their iteration space to run in n threads.
++This is only possible for loops whose iterations are independent
++and can be arbitrarily reordered. The optimization is only
++profitable on multiprocessor machines, for loops that are CPU-intensive,
++rather than constrained e.g.@: by memory bandwidth. This option
++implies @option{-pthread}, and thus is only supported on targets
++that have support for @option{-pthread}.
++
++@item -ftree-sra
++@opindex ftree-sra
++Perform scalar replacement of aggregates. This pass replaces structure
++references with scalars to prevent committing structures to memory too
++early. This flag is enabled by default at @option{-O} and higher.
++
++@item -ftree-copyrename
++@opindex ftree-copyrename
++Perform copy renaming on trees. This pass attempts to rename compiler
++temporaries to other variables at copy locations, usually resulting in
++variable names which more closely resemble the original variables. This flag
++is enabled by default at @option{-O} and higher.
++
++@item -ftree-ter
++@opindex ftree-ter
++Perform temporary expression replacement during the SSA->normal phase. Single
++use/single def temporaries are replaced at their use location with their
++defining expression. This results in non-GIMPLE code, but gives the expanders
++much more complex trees to work on resulting in better RTL generation. This is
++enabled by default at @option{-O} and higher.
++
++@item -ftree-vectorize
++@opindex ftree-vectorize
++Perform loop vectorization on trees. This flag is enabled by default at
++@option{-O3}.
++
++@item -ftree-vect-loop-version
++@opindex ftree-vect-loop-version
++Perform loop versioning when doing loop vectorization on trees. When a loop
++appears to be vectorizable except that data alignment or data dependence cannot
++be determined at compile time then vectorized and non-vectorized versions of
++the loop are generated along with runtime checks for alignment or dependence
++to control which version is executed. This option is enabled by default
++except at level @option{-Os} where it is disabled.
++
++@item -fvect-cost-model
++@opindex fvect-cost-model
++Enable cost model for vectorization.
++
++@item -ftree-vrp
++@opindex ftree-vrp
++Perform Value Range Propagation on trees. This is similar to the
++constant propagation pass, but instead of values, ranges of values are
++propagated. This allows the optimizers to remove unnecessary range
++checks like array bound checks and null pointer checks. This is
++enabled by default at @option{-O2} and higher. Null pointer check
++elimination is only done if @option{-fdelete-null-pointer-checks} is
++enabled.
++
++@item -ftracer
++@opindex ftracer
++Perform tail duplication to enlarge superblock size. This transformation
++simplifies the control flow of the function allowing other optimizations to do
++better job.
++
++@item -funroll-loops
++@opindex funroll-loops
++Unroll loops whose number of iterations can be determined at compile
++time or upon entry to the loop. @option{-funroll-loops} implies
++@option{-frerun-cse-after-loop}. This option makes code larger,
++and may or may not make it run faster.
++
++@item -funroll-all-loops
++@opindex 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.
++@option{-funroll-all-loops} implies the same options as
++@option{-funroll-loops},
++
++@item -fsplit-ivs-in-unroller
++@opindex fsplit-ivs-in-unroller
++Enables expressing of values of induction variables in later iterations
++of the unrolled loop using the value in the first iteration. This breaks
++long dependency chains, thus improving efficiency of the scheduling passes.
++
++Combination of @option{-fweb} and CSE is often sufficient to obtain the
++same effect. However in cases the loop body is more complicated than
++a single basic block, this is not reliable. It also does not work at all
++on some of the architectures due to restrictions in the CSE pass.
++
++This optimization is enabled by default.
++
++@item -fvariable-expansion-in-unroller
++@opindex fvariable-expansion-in-unroller
++With this option, the compiler will create multiple copies of some
++local variables when unrolling a loop which can result in superior code.
++
++@item -fpredictive-commoning
++@opindex fpredictive-commoning
++Perform predictive commoning optimization, i.e., reusing computations
++(especially memory loads and stores) performed in previous
++iterations of loops.
++
++This option is enabled at level @option{-O3}.
++
++@item -fprefetch-loop-arrays
++@opindex fprefetch-loop-arrays
++If supported by the target machine, generate instructions to prefetch
++memory to improve the performance of loops that access large arrays.
++
++This option may generate better or worse code; results are highly
++dependent on the structure of loops within the source code.
++
++Disabled at level @option{-Os}.
++
++@item -fno-peephole
++@itemx -fno-peephole2
++@opindex fno-peephole
++@opindex fno-peephole2
++Disable any machine-specific peephole optimizations. The difference
++between @option{-fno-peephole} and @option{-fno-peephole2} is in how they
++are implemented in the compiler; some targets use one, some use the
++other, a few use both.
++
++@option{-fpeephole} is enabled by default.
++@option{-fpeephole2} enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fno-guess-branch-probability
++@opindex fno-guess-branch-probability
++Do not guess branch probabilities using heuristics.
++
++GCC will use heuristics to guess branch probabilities if they are
++not provided by profiling feedback (@option{-fprofile-arcs}). These
++heuristics are based on the control flow graph. If some branch probabilities
++are specified by @samp{__builtin_expect}, then the heuristics will be
++used to guess branch probabilities for the rest of the control flow graph,
++taking the @samp{__builtin_expect} info into account. The interactions
++between the heuristics and @samp{__builtin_expect} can be complex, and in
++some cases, it may be useful to disable the heuristics so that the effects
++of @samp{__builtin_expect} are easier to understand.
++
++The default is @option{-fguess-branch-probability} at levels
++@option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -freorder-blocks
++@opindex freorder-blocks
++Reorder basic blocks in the compiled function in order to reduce number of
++taken branches and improve code locality.
++
++Enabled at levels @option{-O2}, @option{-O3}.
++
++@item -freorder-blocks-and-partition
++@opindex freorder-blocks-and-partition
++In addition to reordering basic blocks in the compiled function, in order
++to reduce number of taken branches, partitions hot and cold basic blocks
++into separate sections of the assembly and .o files, to improve
++paging and cache locality performance.
++
++This optimization is automatically turned off in the presence of
++exception handling, for linkonce sections, for functions with a user-defined
++section attribute and on any architecture that does not support named
++sections.
++
++@item -freorder-functions
++@opindex freorder-functions
++Reorder functions in the object file in order to
++improve code locality. This is implemented by using special
++subsections @code{.text.hot} for most frequently executed functions and
++@code{.text.unlikely} for unlikely executed functions. Reordering is done by
++the linker so object file format must support named sections and linker must
++place them in a reasonable way.
++
++Also profile feedback must be available in to make this option effective. See
++@option{-fprofile-arcs} for details.
++
++Enabled at levels @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fstrict-aliasing
++@opindex fstrict-aliasing
++Allow 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 @code{unsigned int} can alias an @code{int}, but not a
++@code{void*} or a @code{double}. A character type may alias any other
++type.
++
++@anchor{Type-punning}Pay special attention to code like this:
++@smallexample
++union a_union @{
++ int i;
++ double d;
++@};
++
++int f() @{
++ union a_union t;
++ t.d = 3.0;
++ return t.i;
++@}
++@end smallexample
++The practice of reading from a different union member than the one most
++recently written to (called ``type-punning'') is common. Even with
++@option{-fstrict-aliasing}, type-punning is allowed, provided the memory
++is accessed through the union type. So, the code above will work as
++expected. @xref{Structures unions enumerations and bit-fields
++implementation}. However, this code might not:
++@smallexample
++int f() @{
++ union a_union t;
++ int* ip;
++ t.d = 3.0;
++ ip = &t.i;
++ return *ip;
++@}
++@end smallexample
++
++Similarly, access by taking the address, casting the resulting pointer
++and dereferencing the result has undefined behavior, even if the cast
++uses a union type, e.g.:
++@smallexample
++int f() @{
++ double d = 3.0;
++ return ((union a_union *) &d)->i;
++@}
++@end smallexample
++
++The @option{-fstrict-aliasing} option is enabled at levels
++@option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fstrict-overflow
++@opindex fstrict-overflow
++Allow the compiler to assume strict signed overflow rules, depending
++on the language being compiled. For C (and C++) this means that
++overflow when doing arithmetic with signed numbers is undefined, which
++means that the compiler may assume that it will not happen. This
++permits various optimizations. For example, the compiler will assume
++that an expression like @code{i + 10 > i} will always be true for
++signed @code{i}. This assumption is only valid if signed overflow is
++undefined, as the expression is false if @code{i + 10} overflows when
++using twos complement arithmetic. When this option is in effect any
++attempt to determine whether an operation on signed numbers will
++overflow must be written carefully to not actually involve overflow.
++
++This option also allows the compiler to assume strict pointer
++semantics: given a pointer to an object, if adding an offset to that
++pointer does not produce a pointer to the same object, the addition is
++undefined. This permits the compiler to conclude that @code{p + u >
++p} is always true for a pointer @code{p} and unsigned integer
++@code{u}. This assumption is only valid because pointer wraparound is
++undefined, as the expression is false if @code{p + u} overflows using
++twos complement arithmetic.
++
++See also the @option{-fwrapv} option. Using @option{-fwrapv} means
++that integer signed overflow is fully defined: it wraps. When
++@option{-fwrapv} is used, there is no difference between
++@option{-fstrict-overflow} and @option{-fno-strict-overflow} for
++integers. With @option{-fwrapv} certain types of overflow are
++permitted. For example, if the compiler gets an overflow when doing
++arithmetic on constants, the overflowed value can still be used with
++@option{-fwrapv}, but not otherwise.
++
++The @option{-fstrict-overflow} option is enabled at levels
++@option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -falign-functions
++@itemx -falign-functions=@var{n}
++@opindex falign-functions
++Align the start of functions to the next power-of-two greater than
++@var{n}, skipping up to @var{n} bytes. For instance,
++@option{-falign-functions=32} aligns functions to the next 32-byte
++boundary, but @option{-falign-functions=24} would align to the next
++32-byte boundary only if this can be done by skipping 23 bytes or less.
++
++@option{-fno-align-functions} and @option{-falign-functions=1} are
++equivalent and mean that functions will not be aligned.
++
++Some assemblers only support this flag when @var{n} is a power of two;
++in that case, it is rounded up.
++
++If @var{n} is not specified or is zero, use a machine-dependent default.
++
++Enabled at levels @option{-O2}, @option{-O3}.
++
++@item -falign-labels
++@itemx -falign-labels=@var{n}
++@opindex falign-labels
++Align all branch targets to a power-of-two boundary, skipping up to
++@var{n} bytes like @option{-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.
++
++@option{-fno-align-labels} and @option{-falign-labels=1} are
++equivalent and mean that labels will not be aligned.
++
++If @option{-falign-loops} or @option{-falign-jumps} are applicable and
++are greater than this value, then their values are used instead.
++
++If @var{n} is not specified or is zero, use a machine-dependent default
++which is very likely to be @samp{1}, meaning no alignment.
++
++Enabled at levels @option{-O2}, @option{-O3}.
++
++@item -falign-loops
++@itemx -falign-loops=@var{n}
++@opindex falign-loops
++Align loops to a power-of-two boundary, skipping up to @var{n} bytes
++like @option{-falign-functions}. The hope is that the loop will be
++executed many times, which will make up for any execution of the dummy
++operations.
++
++@option{-fno-align-loops} and @option{-falign-loops=1} are
++equivalent and mean that loops will not be aligned.
++
++If @var{n} is not specified or is zero, use a machine-dependent default.
++
++Enabled at levels @option{-O2}, @option{-O3}.
++
++@item -falign-jumps
++@itemx -falign-jumps=@var{n}
++@opindex falign-jumps
++Align branch targets to a power-of-two boundary, for branch targets
++where the targets can only be reached by jumping, skipping up to @var{n}
++bytes like @option{-falign-functions}. In this case, no dummy operations
++need be executed.
++
++@option{-fno-align-jumps} and @option{-falign-jumps=1} are
++equivalent and mean that loops will not be aligned.
++
++If @var{n} is not specified or is zero, use a machine-dependent default.
++
++Enabled at levels @option{-O2}, @option{-O3}.
++
++@item -funit-at-a-time
++@opindex funit-at-a-time
++This option is left for compatibility reasons. @option{-funit-at-a-time}
++has no effect, while @option{-fno-unit-at-a-time} implies
++@option{-fno-toplevel-reorder} and @option{-fno-section-anchors}.
++
++Enabled by default.
++
++@item -fno-toplevel-reorder
++@opindex fno-toplevel-reorder
++Do not reorder top-level functions, variables, and @code{asm}
++statements. Output them in the same order that they appear in the
++input file. When this option is used, unreferenced static variables
++will not be removed. This option is intended to support existing code
++which relies on a particular ordering. For new code, it is better to
++use attributes.
++
++Enabled at level @option{-O0}. When disabled explicitly, it also imply
++@option{-fno-section-anchors} that is otherwise enabled at @option{-O0} on some
++targets.
++
++@item -fweb
++@opindex fweb
++Constructs webs as commonly used for register allocation purposes and assign
++each web individual pseudo register. This allows the register allocation pass
++to operate on pseudos directly, but also strengthens several other optimization
++passes, such as CSE, loop optimizer and trivial dead code remover. It can,
++however, make debugging impossible, since variables will no longer stay in a
++``home register''.
++
++Enabled by default with @option{-funroll-loops}.
++
++@item -fwhole-program
++@opindex fwhole-program
++Assume that the current compilation unit represents whole program being
++compiled. All public functions and variables with the exception of @code{main}
++and those merged by attribute @code{externally_visible} become static functions
++and in a affect gets more aggressively optimized by interprocedural optimizers.
++While this option is equivalent to proper use of @code{static} keyword for
++programs consisting of single file, in combination with option
++@option{--combine} this flag can be used to compile most of smaller scale C
++programs since the functions and variables become local for the whole combined
++compilation unit, not for the single source file itself.
++
++This option is not supported for Fortran programs.
++
++@item -fcprop-registers
++@opindex fcprop-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.
++
++Enabled at levels @option{-O}, @option{-O2}, @option{-O3}, @option{-Os}.
++
++@item -fprofile-correction
++@opindex fprofile-correction
++Profiles collected using an instrumented binary for multi-threaded programs may
++be inconsistent due to missed counter updates. When this option is specified,
++GCC will use heuristics to correct or smooth out such inconsistencies. By
++default, GCC will emit an error message when an inconsistent profile is detected.
++
++@item -fprofile-dir=@var{path}
++@opindex fprofile-dir
++
++Set the directory to search the profile data files in to @var{path}.
++This option affects only the profile data generated by
++@option{-fprofile-generate}, @option{-ftest-coverage}, @option{-fprofile-arcs}
++and used by @option{-fprofile-use} and @option{-fbranch-probabilities}
++and its related options.
++By default, GCC will use the current directory as @var{path}
++thus the profile data file will appear in the same directory as the object file.
++
++@item -fprofile-generate
++@itemx -fprofile-generate=@var{path}
++@opindex fprofile-generate
++
++Enable options usually used for instrumenting application to produce
++profile useful for later recompilation with profile feedback based
++optimization. You must use @option{-fprofile-generate} both when
++compiling and when linking your program.
++
++The following options are enabled: @code{-fprofile-arcs}, @code{-fprofile-values}, @code{-fvpt}.
++
++If @var{path} is specified, GCC will look at the @var{path} to find
++the profile feedback data files. See @option{-fprofile-dir}.
++
++@item -fprofile-use
++@itemx -fprofile-use=@var{path}
++@opindex fprofile-use
++Enable profile feedback directed optimizations, and optimizations
++generally profitable only with profile feedback available.
++
++The following options are enabled: @code{-fbranch-probabilities}, @code{-fvpt},
++@code{-funroll-loops}, @code{-fpeel-loops}, @code{-ftracer}
++
++By default, GCC emits an error message if the feedback profiles do not
++match the source code. This error can be turned into a warning by using
++@option{-Wcoverage-mismatch}. Note this may result in poorly optimized
++code.
++
++If @var{path} is specified, GCC will look at the @var{path} to find
++the profile feedback data files. See @option{-fprofile-dir}.
++@end table
++
++The following options control compiler behavior regarding floating
++point arithmetic. These options trade off between speed and
++correctness. All must be specifically enabled.
++
++@table @gcctabopt
++@item -ffloat-store
++@opindex 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.
++
++@cindex floating point precision
++This option prevents undesirable excess precision on machines such as
++the 68000 where the floating registers (of the 68881) keep more
++precision than a @code{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 @option{-ffloat-store} for such programs, after modifying
++them to store all pertinent intermediate computations into variables.
++
++@item -ffast-math
++@opindex ffast-math
++Sets @option{-fno-math-errno}, @option{-funsafe-math-optimizations},
++@option{-ffinite-math-only}, @option{-fno-rounding-math},
++@option{-fno-signaling-nans} and @option{-fcx-limited-range}.
++
++This option causes the preprocessor macro @code{__FAST_MATH__} to be defined.
++
++This option is not turned on by any @option{-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. It may, however, yield faster code for programs
++that do not require the guarantees of these specifications.
++
++@item -fno-math-errno
++@opindex 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 is not turned on by any @option{-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. It may, however, yield faster code for programs
++that do not require the guarantees of these specifications.
++
++The default is @option{-fmath-errno}.
++
++On Darwin systems, the math library never sets @code{errno}. There is
++therefore no reason for the compiler to consider the possibility that
++it might, and @option{-fno-math-errno} is the default.
++
++@item -funsafe-math-optimizations
++@opindex 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 is not turned on by any @option{-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. It may, however, yield faster code for programs
++that do not require the guarantees of these specifications.
++Enables @option{-fno-signed-zeros}, @option{-fno-trapping-math},
++@option{-fassociative-math} and @option{-freciprocal-math}.
++
++The default is @option{-fno-unsafe-math-optimizations}.
++
++@item -fassociative-math
++@opindex fassociative-math
++
++Allow re-association of operands in series of floating-point operations.
++This violates the ISO C and C++ language standard by possibly changing
++computation result. NOTE: re-ordering may change the sign of zero as
++well as ignore NaNs and inhibit or create underflow or overflow (and
++thus cannot be used on a code which relies on rounding behavior like
++@code{(x + 2**52) - 2**52)}. May also reorder floating-point comparisons
++and thus may not be used when ordered comparisons are required.
++This option requires that both @option{-fno-signed-zeros} and
++@option{-fno-trapping-math} be in effect. Moreover, it doesn't make
++much sense with @option{-frounding-math}.
++
++The default is @option{-fno-associative-math}.
++
++@item -freciprocal-math
++@opindex freciprocal-math
++
++Allow the reciprocal of a value to be used instead of dividing by
++the value if this enables optimizations. For example @code{x / y}
++can be replaced with @code{x * (1/y)} which is useful if @code{(1/y)}
++is subject to common subexpression elimination. Note that this loses
++precision and increases the number of flops operating on the value.
++
++The default is @option{-fno-reciprocal-math}.
++
++@item -ffinite-math-only
++@opindex ffinite-math-only
++Allow optimizations for floating-point arithmetic that assume
++that arguments and results are not NaNs or +-Infs.
++
++This option is not turned on by any @option{-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. It may, however, yield faster code for programs
++that do not require the guarantees of these specifications.
++
++The default is @option{-fno-finite-math-only}.
++
++@item -fno-signed-zeros
++@opindex fno-signed-zeros
++Allow optimizations for floating point arithmetic that ignore the
++signedness of zero. IEEE arithmetic specifies the behavior of
++distinct +0.0 and @minus{}0.0 values, which then prohibits simplification
++of expressions such as x+0.0 or 0.0*x (even with @option{-ffinite-math-only}).
++This option implies that the sign of a zero result isn't significant.
++
++The default is @option{-fsigned-zeros}.
++
++@item -fno-trapping-math
++@opindex fno-trapping-math
++Compile code assuming that floating-point operations cannot generate
++user-visible traps. These traps include division by zero, overflow,
++underflow, inexact result and invalid operation. This option requires
++that @option{-fno-signaling-nans} be in effect. 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 @option{-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 @option{-ftrapping-math}.
++
++@item -frounding-math
++@opindex frounding-math
++Disable transformations and optimizations that assume default floating
++point rounding behavior. This is round-to-zero for all floating point
++to integer conversions, and round-to-nearest for all other arithmetic
++truncations. This option should be specified for programs that change
++the FP rounding mode dynamically, or that may be executed with a
++non-default rounding mode. This option disables constant folding of
++floating point expressions at compile-time (which may be affected by
++rounding mode) and arithmetic transformations that are unsafe in the
++presence of sign-dependent rounding modes.
++
++The default is @option{-fno-rounding-math}.
++
++This option is experimental and does not currently guarantee to
++disable all GCC optimizations that are affected by rounding mode.
++Future versions of GCC may provide finer control of this setting
++using C99's @code{FENV_ACCESS} pragma. This command line option
++will be used to specify the default state for @code{FENV_ACCESS}.
++
++@item -frtl-abstract-sequences
++@opindex frtl-abstract-sequences
++It is a size optimization method. This option is to find identical
++sequences of code, which can be turned into pseudo-procedures and
++then replace all occurrences with calls to the newly created
++subroutine. It is kind of an opposite of @option{-finline-functions}.
++This optimization runs at RTL level.
++
++@item -fsignaling-nans
++@opindex fsignaling-nans
++Compile code assuming that IEEE signaling NaNs may generate user-visible
++traps during floating-point operations. Setting this option disables
++optimizations that may change the number of exceptions visible with
++signaling NaNs. This option implies @option{-ftrapping-math}.
++
++This option causes the preprocessor macro @code{__SUPPORT_SNAN__} to
++be defined.
++
++The default is @option{-fno-signaling-nans}.
++
++This option is experimental and does not currently guarantee to
++disable all GCC optimizations that affect signaling NaN behavior.
++
++@item -fsingle-precision-constant
++@opindex fsingle-precision-constant
++Treat floating point constant as single precision constant instead of
++implicitly converting it to double precision constant.
++
++@item -fcx-limited-range
++@opindex fcx-limited-range
++When enabled, this option states that a range reduction step is not
++needed when performing complex division. Also, there is no checking
++whether the result of a complex multiplication or division is @code{NaN
+++ I*NaN}, with an attempt to rescue the situation in that case. The
++default is @option{-fno-cx-limited-range}, but is enabled by
++@option{-ffast-math}.
++
++This option controls the default setting of the ISO C99
++@code{CX_LIMITED_RANGE} pragma. Nevertheless, the option applies to
++all languages.
++
++@item -fcx-fortran-rules
++@opindex fcx-fortran-rules
++Complex multiplication and division follow Fortran rules. Range
++reduction is done as part of complex division, but there is no checking
++whether the result of a complex multiplication or division is @code{NaN
+++ I*NaN}, with an attempt to rescue the situation in that case.
++
++The default is @option{-fno-cx-fortran-rules}.
++
++@end table
++
++The following options control optimizations that may improve
++performance, but are not enabled by any @option{-O} options. This
++section includes experimental options that may produce broken code.
++
++@table @gcctabopt
++@item -fbranch-probabilities
++@opindex fbranch-probabilities
++After running a program compiled with @option{-fprofile-arcs}
++(@pxref{Debugging Options,, Options for Debugging Your Program or
++@command{gcc}}), you can compile it a second time using
++@option{-fbranch-probabilities}, to improve optimizations based on
++the number of times each branch was taken. When the program
++compiled with @option{-fprofile-arcs} exits it saves arc execution
++counts to a file called @file{@var{sourcename}.gcda} 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 @option{-fbranch-probabilities}, GCC puts a
++@samp{REG_BR_PROB} note on each @samp{JUMP_INSN} and @samp{CALL_INSN}.
++These can be used to improve optimization. Currently, they are only
++used in one place: in @file{reorg.c}, instead of guessing which path a
++branch is mostly to take, the @samp{REG_BR_PROB} values are used to
++exactly determine which path is taken more often.
++
++@item -fprofile-values
++@opindex fprofile-values
++If combined with @option{-fprofile-arcs}, it adds code so that some
++data about values of expressions in the program is gathered.
++
++With @option{-fbranch-probabilities}, it reads back the data gathered
++from profiling values of expressions and adds @samp{REG_VALUE_PROFILE}
++notes to instructions for their later usage in optimizations.
++
++Enabled with @option{-fprofile-generate} and @option{-fprofile-use}.
++
++@item -fvpt
++@opindex fvpt
++If combined with @option{-fprofile-arcs}, it instructs the compiler to add
++a code to gather information about values of expressions.
++
++With @option{-fbranch-probabilities}, it reads back the data gathered
++and actually performs the optimizations based on them.
++Currently the optimizations include specialization of division operation
++using the knowledge about the value of the denominator.
++
++@item -frename-registers
++@opindex 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. Depending on the
++debug information format adopted by the target, however, it can
++make debugging impossible, since variables will no longer stay in
++a ``home register''.
++
++Enabled by default with @option{-funroll-loops}.
++
++@item -ftracer
++@opindex ftracer
++Perform tail duplication to enlarge superblock size. This transformation
++simplifies the control flow of the function allowing other optimizations to do
++better job.
++
++Enabled with @option{-fprofile-use}.
++
++@item -funroll-loops
++@opindex funroll-loops
++Unroll loops whose number of iterations can be determined at compile time or
++upon entry to the loop. @option{-funroll-loops} implies
++@option{-frerun-cse-after-loop}, @option{-fweb} and @option{-frename-registers}.
++It also turns on complete loop peeling (i.e.@: complete removal of loops with
++small constant number of iterations). This option makes code larger, and may
++or may not make it run faster.
++
++Enabled with @option{-fprofile-use}.
++
++@item -funroll-all-loops
++@opindex 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.
++@option{-funroll-all-loops} implies the same options as
++@option{-funroll-loops}.
++
++@item -fpeel-loops
++@opindex fpeel-loops
++Peels the loops for that there is enough information that they do not
++roll much (from profile feedback). It also turns on complete loop peeling
++(i.e.@: complete removal of loops with small constant number of iterations).
++
++Enabled with @option{-fprofile-use}.
++
++@item -fmove-loop-invariants
++@opindex fmove-loop-invariants
++Enables the loop invariant motion pass in the RTL loop optimizer. Enabled
++at level @option{-O1}
++
++@item -funswitch-loops
++@opindex funswitch-loops
++Move branches with loop invariant conditions out of the loop, with duplicates
++of the loop on both branches (modified according to result of the condition).
++
++@item -ffunction-sections
++@itemx -fdata-sections
++@opindex ffunction-sections
++@opindex 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. Most systems
++using the ELF object format and SPARC processors running Solaris 2 have
++linkers with such optimizations. 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 @code{gprof} on all systems if you
++specify this option and you may have problems with debugging if
++you specify both this option and @option{-g}.
++
++@item -fbranch-target-load-optimize
++@opindex fbranch-target-load-optimize
++Perform branch target register load optimization before prologue / epilogue
++threading.
++The use of target registers can typically be exposed only during reload,
++thus hoisting loads out of loops and doing inter-block scheduling needs
++a separate optimization pass.
++
++@item -fbranch-target-load-optimize2
++@opindex fbranch-target-load-optimize2
++Perform branch target register load optimization after prologue / epilogue
++threading.
++
++@item -fbtr-bb-exclusive
++@opindex fbtr-bb-exclusive
++When performing branch target register load optimization, don't reuse
++branch target registers in within any basic block.
++
++@item -fstack-protector
++@opindex fstack-protector
++Emit extra code to check for buffer overflows, such as stack smashing
++attacks. This is done by adding a guard variable to functions with
++vulnerable objects. This includes functions that call alloca, and
++functions with buffers larger than 8 bytes. The guards are initialized
++when a function is entered and then checked when the function exits.
++If a guard check fails, an error message is printed and the program exits.
++
++@item -fstack-protector-all
++@opindex fstack-protector-all
++Like @option{-fstack-protector} except that all functions are protected.
++
++@item -fsection-anchors
++@opindex fsection-anchors
++Try to reduce the number of symbolic address calculations by using
++shared ``anchor'' symbols to address nearby objects. This transformation
++can help to reduce the number of GOT entries and GOT accesses on some
++targets.
++
++For example, the implementation of the following function @code{foo}:
++
++@smallexample
++static int a, b, c;
++int foo (void) @{ return a + b + c; @}
++@end smallexample
++
++would usually calculate the addresses of all three variables, but if you
++compile it with @option{-fsection-anchors}, it will access the variables
++from a common anchor point instead. The effect is similar to the
++following pseudocode (which isn't valid C):
++
++@smallexample
++int foo (void)
++@{
++ register int *xr = &x;
++ return xr[&a - &x] + xr[&b - &x] + xr[&c - &x];
++@}
++@end smallexample
++
++Not all targets support this option.
++
++@item --param @var{name}=@var{value}
++@opindex param
++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
++@option{--param} option.
++
++The names of specific parameters, and the meaning of the values, are
++tied to the internals of the compiler, and are subject to change
++without notice in future releases.
++
++In each case, the @var{value} is an integer. The allowable choices for
++@var{name} are given in the following table:
++
++@table @gcctabopt
++@item sra-max-structure-size
++The maximum structure size, in bytes, at which the scalar replacement
++of aggregates (SRA) optimization will perform block copies. The
++default value, 0, implies that GCC will select the most appropriate
++size itself.
++
++@item sra-field-structure-ratio
++The threshold ratio (as a percentage) between instantiated fields and
++the complete structure size. We say that if the ratio of the number
++of bytes in instantiated fields to the number of bytes in the complete
++structure exceeds this parameter, then block copies are not used. The
++default is 75.
++
++@item struct-reorg-cold-struct-ratio
++The threshold ratio (as a percentage) between a structure frequency
++and the frequency of the hottest structure in the program. This parameter
++is used by struct-reorg optimization enabled by @option{-fipa-struct-reorg}.
++We say that if the ratio of a structure frequency, calculated by profiling,
++to the hottest structure frequency in the program is less than this
++parameter, then structure reorganization is not applied to this structure.
++The default is 10.
++
++@item predictable-branch-cost-outcome
++When branch is predicted to be taken with probability lower than this threshold
++(in percent), then it is considered well predictable. The default is 10.
++
++@item max-crossjump-edges
++The maximum number of incoming edges to consider for crossjumping.
++The algorithm used by @option{-fcrossjumping} is @math{O(N^2)} in
++the number of edges incoming to each block. Increasing values mean
++more aggressive optimization, making the compile time increase with
++probably small improvement in executable size.
++
++@item min-crossjump-insns
++The minimum number of instructions which must be matched at the end
++of two blocks before crossjumping will be performed on them. This
++value is ignored in the case where all instructions in the block being
++crossjumped from are matched. The default value is 5.
++
++@item max-grow-copy-bb-insns
++The maximum code size expansion factor when copying basic blocks
++instead of jumping. The expansion is relative to a jump instruction.
++The default value is 8.
++
++@item max-goto-duplication-insns
++The maximum number of instructions to duplicate to a block that jumps
++to a computed goto. To avoid @math{O(N^2)} behavior in a number of
++passes, GCC factors computed gotos early in the compilation process,
++and unfactors them as late as possible. Only computed jumps at the
++end of a basic blocks with no more than max-goto-duplication-insns are
++unfactored. The default value is 8.
++
++@item 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.
++
++@item 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.
++
++@item 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.
++
++@item max-gcse-passes
++The maximum number of passes of GCSE to run. The default is 1.
++
++@item 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.
++
++@item max-inline-insns-single
++Several parameters control the tree inliner used in gcc.
++This number sets the maximum number of instructions (counted in GCC's
++internal representation) in a single function that the tree inliner
++will consider for inlining. This only affects functions declared
++inline and methods implemented in a class declaration (C++).
++The default value is 450.
++
++@item max-inline-insns-auto
++When you use @option{-finline-functions} (included in @option{-O3}),
++a lot of functions that would otherwise not be considered for inlining
++by the compiler will be investigated. To those functions, a different
++(more restrictive) limit compared to functions declared inline can
++be applied.
++The default value is 90.
++
++@item large-function-insns
++The limit specifying really large functions. For functions larger than this
++limit after inlining, inlining is constrained by
++@option{--param large-function-growth}. This parameter is useful primarily
++to avoid extreme compilation time caused by non-linear algorithms used by the
++backend.
++The default value is 2700.
++
++@item large-function-growth
++Specifies maximal growth of large function caused by inlining in percents.
++The default value is 100 which limits large function growth to 2.0 times
++the original size.
++
++@item large-unit-insns
++The limit specifying large translation unit. Growth caused by inlining of
++units larger than this limit is limited by @option{--param inline-unit-growth}.
++For small units this might be too tight (consider unit consisting of function A
++that is inline and B that just calls A three time. If B is small relative to
++A, the growth of unit is 300\% and yet such inlining is very sane. For very
++large units consisting of small inlineable functions however the overall unit
++growth limit is needed to avoid exponential explosion of code size. Thus for
++smaller units, the size is increased to @option{--param large-unit-insns}
++before applying @option{--param inline-unit-growth}. The default is 10000
++
++@item inline-unit-growth
++Specifies maximal overall growth of the compilation unit caused by inlining.
++The default value is 30 which limits unit growth to 1.3 times the original
++size.
++
++@item ipcp-unit-growth
++Specifies maximal overall growth of the compilation unit caused by
++interprocedural constant propagation. The default value is 10 which limits
++unit growth to 1.1 times the original size.
++
++@item large-stack-frame
++The limit specifying large stack frames. While inlining the algorithm is trying
++to not grow past this limit too much. Default value is 256 bytes.
++
++@item large-stack-frame-growth
++Specifies maximal growth of large stack frames caused by inlining in percents.
++The default value is 1000 which limits large stack frame growth to 11 times
++the original size.
++
++@item max-inline-insns-recursive
++@itemx max-inline-insns-recursive-auto
++Specifies maximum number of instructions out-of-line copy of self recursive inline
++function can grow into by performing recursive inlining.
++
++For functions declared inline @option{--param max-inline-insns-recursive} is
++taken into account. For function not declared inline, recursive inlining
++happens only when @option{-finline-functions} (included in @option{-O3}) is
++enabled and @option{--param max-inline-insns-recursive-auto} is used. The
++default value is 450.
++
++@item max-inline-recursive-depth
++@itemx max-inline-recursive-depth-auto
++Specifies maximum recursion depth used by the recursive inlining.
++
++For functions declared inline @option{--param max-inline-recursive-depth} is
++taken into account. For function not declared inline, recursive inlining
++happens only when @option{-finline-functions} (included in @option{-O3}) is
++enabled and @option{--param max-inline-recursive-depth-auto} is used. The
++default value is 8.
++
++@item min-inline-recursive-probability
++Recursive inlining is profitable only for function having deep recursion
++in average and can hurt for function having little recursion depth by
++increasing the prologue size or complexity of function body to other
++optimizers.
++
++When profile feedback is available (see @option{-fprofile-generate}) the actual
++recursion depth can be guessed from probability that function will recurse via
++given call expression. This parameter limits inlining only to call expression
++whose probability exceeds given threshold (in percents). The default value is
++10.
++
++@item inline-call-cost
++Specify cost of call instruction relative to simple arithmetics operations
++(having cost of 1). Increasing this cost disqualifies inlining of non-leaf
++functions and at the same time increases size of leaf function that is believed to
++reduce function size by being inlined. In effect it increases amount of
++inlining for code having large abstraction penalty (many functions that just
++pass the arguments to other functions) and decrease inlining for code with low
++abstraction penalty. The default value is 12.
++
++@item min-vect-loop-bound
++The minimum number of iterations under which a loop will not get vectorized
++when @option{-ftree-vectorize} is used. The number of iterations after
++vectorization needs to be greater than the value specified by this option
++to allow vectorization. The default value is 0.
++
++@item max-unrolled-insns
++The maximum number of instructions that a loop should have if that loop
++is unrolled, and if the loop is unrolled, it determines how many times
++the loop code is unrolled.
++
++@item max-average-unrolled-insns
++The maximum number of instructions biased by probabilities of their execution
++that a loop should have if that loop is unrolled, and if the loop is unrolled,
++it determines how many times the loop code is unrolled.
++
++@item max-unroll-times
++The maximum number of unrollings of a single loop.
++
++@item max-peeled-insns
++The maximum number of instructions that a loop should have if that loop
++is peeled, and if the loop is peeled, it determines how many times
++the loop code is peeled.
++
++@item max-peel-times
++The maximum number of peelings of a single loop.
++
++@item max-completely-peeled-insns
++The maximum number of insns of a completely peeled loop.
++
++@item max-completely-peel-times
++The maximum number of iterations of a loop to be suitable for complete peeling.
++
++@item max-unswitch-insns
++The maximum number of insns of an unswitched loop.
++
++@item max-unswitch-level
++The maximum number of branches unswitched in a single loop.
++
++@item lim-expensive
++The minimum cost of an expensive expression in the loop invariant motion.
++
++@item iv-consider-all-candidates-bound
++Bound on number of candidates for induction variables below that
++all candidates are considered for each use in induction variable
++optimizations. Only the most relevant candidates are considered
++if there are more candidates, to avoid quadratic time complexity.
++
++@item iv-max-considered-uses
++The induction variable optimizations give up on loops that contain more
++induction variable uses.
++
++@item iv-always-prune-cand-set-bound
++If number of candidates in the set is smaller than this value,
++we always try to remove unnecessary ivs from the set during its
++optimization when a new iv is added to the set.
++
++@item scev-max-expr-size
++Bound on size of expressions used in the scalar evolutions analyzer.
++Large expressions slow the analyzer.
++
++@item omega-max-vars
++The maximum number of variables in an Omega constraint system.
++The default value is 128.
++
++@item omega-max-geqs
++The maximum number of inequalities in an Omega constraint system.
++The default value is 256.
++
++@item omega-max-eqs
++The maximum number of equalities in an Omega constraint system.
++The default value is 128.
++
++@item omega-max-wild-cards
++The maximum number of wildcard variables that the Omega solver will
++be able to insert. The default value is 18.
++
++@item omega-hash-table-size
++The size of the hash table in the Omega solver. The default value is
++550.
++
++@item omega-max-keys
++The maximal number of keys used by the Omega solver. The default
++value is 500.
++
++@item omega-eliminate-redundant-constraints
++When set to 1, use expensive methods to eliminate all redundant
++constraints. The default value is 0.
++
++@item vect-max-version-for-alignment-checks
++The maximum number of runtime checks that can be performed when
++doing loop versioning for alignment in the vectorizer. See option
++ftree-vect-loop-version for more information.
++
++@item vect-max-version-for-alias-checks
++The maximum number of runtime checks that can be performed when
++doing loop versioning for alias in the vectorizer. See option
++ftree-vect-loop-version for more information.
++
++@item max-iterations-to-track
++
++The maximum number of iterations of a loop the brute force algorithm
++for analysis of # of iterations of the loop tries to evaluate.
++
++@item hot-bb-count-fraction
++Select fraction of the maximal count of repetitions of basic block in program
++given basic block needs to have to be considered hot.
++
++@item hot-bb-frequency-fraction
++Select fraction of the maximal frequency of executions of basic block in
++function given basic block needs to have to be considered hot
++
++@item max-predicted-iterations
++The maximum number of loop iterations we predict statically. This is useful
++in cases where function contain single loop with known bound and other loop
++with unknown. We predict the known number of iterations correctly, while
++the unknown number of iterations average to roughly 10. This means that the
++loop without bounds would appear artificially cold relative to the other one.
++
++@item align-threshold
++
++Select fraction of the maximal frequency of executions of basic block in
++function given basic block will get aligned.
++
++@item align-loop-iterations
++
++A loop expected to iterate at lest the selected number of iterations will get
++aligned.
++
++@item tracer-dynamic-coverage
++@itemx tracer-dynamic-coverage-feedback
++
++This value is used to limit superblock formation once the given percentage of
++executed instructions is covered. This limits unnecessary code size
++expansion.
++
++The @option{tracer-dynamic-coverage-feedback} is used only when profile
++feedback is available. The real profiles (as opposed to statically estimated
++ones) are much less balanced allowing the threshold to be larger value.
++
++@item tracer-max-code-growth
++Stop tail duplication once code growth has reached given percentage. This is
++rather hokey argument, as most of the duplicates will be eliminated later in
++cross jumping, so it may be set to much higher values than is the desired code
++growth.
++
++@item tracer-min-branch-ratio
++
++Stop reverse growth when the reverse probability of best edge is less than this
++threshold (in percent).
++
++@item tracer-min-branch-ratio
++@itemx tracer-min-branch-ratio-feedback
++
++Stop forward growth if the best edge do have probability lower than this
++threshold.
++
++Similarly to @option{tracer-dynamic-coverage} two values are present, one for
++compilation for profile feedback and one for compilation without. The value
++for compilation with profile feedback needs to be more conservative (higher) in
++order to make tracer effective.
++
++@item max-cse-path-length
++
++Maximum number of basic blocks on path that cse considers. The default is 10.
++
++@item max-cse-insns
++The maximum instructions CSE process before flushing. The default is 1000.
++
++@item max-aliased-vops
++
++Maximum number of virtual operands per function allowed to represent
++aliases before triggering the alias partitioning heuristic. Alias
++partitioning reduces compile times and memory consumption needed for
++aliasing at the expense of precision loss in alias information. The
++default value for this parameter is 100 for -O1, 500 for -O2 and 1000
++for -O3.
++
++Notice that if a function contains more memory statements than the
++value of this parameter, it is not really possible to achieve this
++reduction. In this case, the compiler will use the number of memory
++statements as the value for @option{max-aliased-vops}.
++
++@item avg-aliased-vops
++
++Average number of virtual operands per statement allowed to represent
++aliases before triggering the alias partitioning heuristic. This
++works in conjunction with @option{max-aliased-vops}. If a function
++contains more than @option{max-aliased-vops} virtual operators, then
++memory symbols will be grouped into memory partitions until either the
++total number of virtual operators is below @option{max-aliased-vops}
++or the average number of virtual operators per memory statement is
++below @option{avg-aliased-vops}. The default value for this parameter
++is 1 for -O1 and -O2, and 3 for -O3.
++
++@item ggc-min-expand
++
++GCC uses a garbage collector to manage its own memory allocation. This
++parameter specifies the minimum percentage by which the garbage
++collector's heap should be allowed to expand between collections.
++Tuning this may improve compilation speed; it has no effect on code
++generation.
++
++The default is 30% + 70% * (RAM/1GB) with an upper bound of 100% when
++RAM >= 1GB@. If @code{getrlimit} is available, the notion of "RAM" is
++the smallest of actual RAM and @code{RLIMIT_DATA} or @code{RLIMIT_AS}. If
++GCC is not able to calculate RAM on a particular platform, the lower
++bound of 30% is used. Setting this parameter and
++@option{ggc-min-heapsize} to zero causes a full collection to occur at
++every opportunity. This is extremely slow, but can be useful for
++debugging.
++
++@item ggc-min-heapsize
++
++Minimum size of the garbage collector's heap before it begins bothering
++to collect garbage. The first collection occurs after the heap expands
++by @option{ggc-min-expand}% beyond @option{ggc-min-heapsize}. Again,
++tuning this may improve compilation speed, and has no effect on code
++generation.
++
++The default is the smaller of RAM/8, RLIMIT_RSS, or a limit which
++tries to ensure that RLIMIT_DATA or RLIMIT_AS are not exceeded, but
++with a lower bound of 4096 (four megabytes) and an upper bound of
++131072 (128 megabytes). If GCC is not able to calculate RAM on a
++particular platform, the lower bound is used. Setting this parameter
++very large effectively disables garbage collection. Setting this
++parameter and @option{ggc-min-expand} to zero causes a full collection
++to occur at every opportunity.
++
++@item max-reload-search-insns
++The maximum number of instruction reload should look backward for equivalent
++register. Increasing values mean more aggressive optimization, making the
++compile time increase with probably slightly better performance. The default
++value is 100.
++
++@item max-cselib-memory-locations
++The maximum number of memory locations cselib should take into account.
++Increasing values mean more aggressive optimization, making the compile time
++increase with probably slightly better performance. The default value is 500.
++
++@item reorder-blocks-duplicate
++@itemx reorder-blocks-duplicate-feedback
++
++Used by basic block reordering pass to decide whether to use unconditional
++branch or duplicate the code on its destination. Code is duplicated when its
++estimated size is smaller than this value multiplied by the estimated size of
++unconditional jump in the hot spots of the program.
++
++The @option{reorder-block-duplicate-feedback} is used only when profile
++feedback is available and may be set to higher values than
++@option{reorder-block-duplicate} since information about the hot spots is more
++accurate.
++
++@item max-sched-ready-insns
++The maximum number of instructions ready to be issued the scheduler should
++consider at any given time during the first scheduling pass. Increasing
++values mean more thorough searches, making the compilation time increase
++with probably little benefit. The default value is 100.
++
++@item max-sched-region-blocks
++The maximum number of blocks in a region to be considered for
++interblock scheduling. The default value is 10.
++
++@item max-pipeline-region-blocks
++The maximum number of blocks in a region to be considered for
++pipelining in the selective scheduler. The default value is 15.
++
++@item max-sched-region-insns
++The maximum number of insns in a region to be considered for
++interblock scheduling. The default value is 100.
++
++@item max-pipeline-region-insns
++The maximum number of insns in a region to be considered for
++pipelining in the selective scheduler. The default value is 200.
++
++@item min-spec-prob
++The minimum probability (in percents) of reaching a source block
++for interblock speculative scheduling. The default value is 40.
++
++@item max-sched-extend-regions-iters
++The maximum number of iterations through CFG to extend regions.
++0 - disable region extension,
++N - do at most N iterations.
++The default value is 0.
++
++@item max-sched-insn-conflict-delay
++The maximum conflict delay for an insn to be considered for speculative motion.
++The default value is 3.
++
++@item sched-spec-prob-cutoff
++The minimal probability of speculation success (in percents), so that
++speculative insn will be scheduled.
++The default value is 40.
++
++@item sched-mem-true-dep-cost
++Minimal distance (in CPU cycles) between store and load targeting same
++memory locations. The default value is 1.
++
++@item selsched-max-lookahead
++The maximum size of the lookahead window of selective scheduling. It is a
++depth of search for available instructions.
++The default value is 50.
++
++@item selsched-max-sched-times
++The maximum number of times that an instruction will be scheduled during
++selective scheduling. This is the limit on the number of iterations
++through which the instruction may be pipelined. The default value is 2.
++
++@item selsched-max-insns-to-rename
++The maximum number of best instructions in the ready list that are considered
++for renaming in the selective scheduler. The default value is 2.
++
++@item max-last-value-rtl
++The maximum size measured as number of RTLs that can be recorded in an expression
++in combiner for a pseudo register as last known value of that register. The default
++is 10000.
++
++@item integer-share-limit
++Small integer constants can use a shared data structure, reducing the
++compiler's memory usage and increasing its speed. This sets the maximum
++value of a shared integer constant. The default value is 256.
++
++@item min-virtual-mappings
++Specifies the minimum number of virtual mappings in the incremental
++SSA updater that should be registered to trigger the virtual mappings
++heuristic defined by virtual-mappings-ratio. The default value is
++100.
++
++@item virtual-mappings-ratio
++If the number of virtual mappings is virtual-mappings-ratio bigger
++than the number of virtual symbols to be updated, then the incremental
++SSA updater switches to a full update for those symbols. The default
++ratio is 3.
++
++@item ssp-buffer-size
++The minimum size of buffers (i.e.@: arrays) that will receive stack smashing
++protection when @option{-fstack-protection} is used.
++
++@item max-jump-thread-duplication-stmts
++Maximum number of statements allowed in a block that needs to be
++duplicated when threading jumps.
++
++@item max-fields-for-field-sensitive
++Maximum number of fields in a structure we will treat in
++a field sensitive manner during pointer analysis. The default is zero
++for -O0, and -O1 and 100 for -Os, -O2, and -O3.
++
++@item prefetch-latency
++Estimate on average number of instructions that are executed before
++prefetch finishes. The distance we prefetch ahead is proportional
++to this constant. Increasing this number may also lead to less
++streams being prefetched (see @option{simultaneous-prefetches}).
++
++@item simultaneous-prefetches
++Maximum number of prefetches that can run at the same time.
++
++@item l1-cache-line-size
++The size of cache line in L1 cache, in bytes.
++
++@item l1-cache-size
++The size of L1 cache, in kilobytes.
++
++@item l2-cache-size
++The size of L2 cache, in kilobytes.
++
++@item use-canonical-types
++Whether the compiler should use the ``canonical'' type system. By
++default, this should always be 1, which uses a more efficient internal
++mechanism for comparing types in C++ and Objective-C++. However, if
++bugs in the canonical type system are causing compilation failures,
++set this value to 0 to disable canonical types.
++
++@item switch-conversion-max-branch-ratio
++Switch initialization conversion will refuse to create arrays that are
++bigger than @option{switch-conversion-max-branch-ratio} times the number of
++branches in the switch.
++
++@item max-partial-antic-length
++Maximum length of the partial antic set computed during the tree
++partial redundancy elimination optimization (@option{-ftree-pre}) when
++optimizing at @option{-O3} and above. For some sorts of source code
++the enhanced partial redundancy elimination optimization can run away,
++consuming all of the memory available on the host machine. This
++parameter sets a limit on the length of the sets that are computed,
++which prevents the runaway behavior. Setting a value of 0 for
++this parameter will allow an unlimited set length.
++
++@item sccvn-max-scc-size
++Maximum size of a strongly connected component (SCC) during SCCVN
++processing. If this limit is hit, SCCVN processing for the whole
++function will not be done and optimizations depending on it will
++be disabled. The default maximum SCC size is 10000.
++
++@item ira-max-loops-num
++IRA uses a regional register allocation by default. If a function
++contains loops more than number given by the parameter, only at most
++given number of the most frequently executed loops will form regions
++for the regional register allocation. The default value of the
++parameter is 100.
++
++@item ira-max-conflict-table-size
++Although IRA uses a sophisticated algorithm of compression conflict
++table, the table can be still big for huge functions. If the conflict
++table for a function could be more than size in MB given by the
++parameter, the conflict table is not built and faster, simpler, and
++lower quality register allocation algorithm will be used. The
++algorithm do not use pseudo-register conflicts. The default value of
++the parameter is 2000.
++
++@item loop-invariant-max-bbs-in-loop
++Loop invariant motion can be very expensive, both in compile time and
++in amount of needed compile time memory, with very large loops. Loops
++with more basic blocks than this parameter won't have loop invariant
++motion optimization performed on them. The default value of the
++parameter is 1000 for -O1 and 10000 for -O2 and above.
++
++@end table
++@end table
++
++@node Preprocessor Options
++@section Options Controlling the Preprocessor
++@cindex preprocessor options
++@cindex options, preprocessor
++
++These options control the C preprocessor, which is run on each C source
++file before actual compilation.
++
++If you use the @option{-E} option, nothing is done except preprocessing.
++Some of these options make sense only together with @option{-E} because
++they cause the preprocessor output to be unsuitable for actual
++compilation.
++
++@table @gcctabopt
++@opindex Wp
++You can use @option{-Wp,@var{option}} to bypass the compiler driver
++and pass @var{option} directly through to the preprocessor. If
++@var{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
++@option{-Wp} forcibly bypasses this phase. The preprocessor's direct
++interface is undocumented and subject to change, so whenever possible
++you should avoid using @option{-Wp} and let the driver handle the
++options instead.
++
++@item -Xpreprocessor @var{option}
++@opindex preprocessor
++Pass @var{option} as an option to the preprocessor. You can use this to
++supply system-specific preprocessor options which GCC does not know how to
++recognize.
++
++If you want to pass an option that takes an argument, you must use
++@option{-Xpreprocessor} twice, once for the option and once for the argument.
++@end table
++
++@include cppopts.texi
++
++@node Assembler Options
++@section Passing Options to the Assembler
++
++@c prevent bad page break with this line
++You can pass options to the assembler.
++
++@table @gcctabopt
++@item -Wa,@var{option}
++@opindex Wa
++Pass @var{option} as an option to the assembler. If @var{option}
++contains commas, it is split into multiple options at the commas.
++
++@item -Xassembler @var{option}
++@opindex Xassembler
++Pass @var{option} as an option to the assembler. You can use this to
++supply system-specific assembler options which GCC does not know how to
++recognize.
++
++If you want to pass an option that takes an argument, you must use
++@option{-Xassembler} twice, once for the option and once for the argument.
++
++@end table
++
++@node Link Options
++@section Options for Linking
++@cindex link options
++@cindex options, linking
++
++These options come into play when the compiler links object files into
++an executable output file. They are meaningless if the compiler is
++not doing a link step.
++
++@table @gcctabopt
++@cindex file names
++@item @var{object-file-name}
++A file name that does not end in a special recognized suffix is
++considered to name an object file or library. (Object files are
++distinguished from libraries by the linker according to the file
++contents.) If linking is done, these object files are used as input
++to the linker.
++
++@item -c
++@itemx -S
++@itemx -E
++@opindex c
++@opindex S
++@opindex E
++If any of these options is used, then the linker is not run, and
++object file names should not be used as arguments. @xref{Overall
++Options}.
++
++@cindex Libraries
++@item -l@var{library}
++@itemx -l @var{library}
++@opindex l
++Search the library named @var{library} when linking. (The second
++alternative with the library as a separate argument is only for
++POSIX compliance and is not recommended.)
++
++It makes a difference where in the command you write this option; the
++linker searches and processes libraries and object files in the order they
++are specified. Thus, @samp{foo.o -lz bar.o} searches library @samp{z}
++after file @file{foo.o} but before @file{bar.o}. If @file{bar.o} refers
++to functions in @samp{z}, those functions may not be loaded.
++
++The linker searches a standard list of directories for the library,
++which is actually a file named @file{lib@var{library}.a}. The linker
++then uses this file as if it had been specified precisely by name.
++
++The directories searched include several standard system directories
++plus any that you specify with @option{-L}.
++
++Normally the files found this way are library files---archive files
++whose members are object files. The linker handles an archive file by
++scanning through it for members which define symbols that have so far
++been referenced but not defined. But if the file that is found is an
++ordinary object file, it is linked in the usual fashion. The only
++difference between using an @option{-l} option and specifying a file name
++is that @option{-l} surrounds @var{library} with @samp{lib} and @samp{.a}
++and searches several directories.
++
++@item -lobjc
++@opindex lobjc
++You need this special case of the @option{-l} option in order to
++link an Objective-C or Objective-C++ program.
++
++@item -nostartfiles
++@opindex nostartfiles
++Do not use the standard system startup files when linking.
++The standard system libraries are used normally, unless @option{-nostdlib}
++or @option{-nodefaultlibs} is used.
++
++@item -nodefaultlibs
++@opindex nodefaultlibs
++Do not use the standard system libraries when linking.
++Only the libraries you specify will be passed to the linker.
++The standard startup files are used normally, unless @option{-nostartfiles}
++is used. The compiler may generate calls to @code{memcmp},
++@code{memset}, @code{memcpy} and @code{memmove}.
++These entries are usually resolved by entries in
++libc. These entry points should be supplied through some other
++mechanism when this option is specified.
++
++@item -nostdlib
++@opindex nostdlib
++Do not use the standard system startup files or libraries when linking.
++No startup files and only the libraries you specify will be passed to
++the linker. The compiler may generate calls to @code{memcmp}, @code{memset},
++@code{memcpy} and @code{memmove}.
++These entries are usually resolved by entries in
++libc. These entry points should be supplied through some other
++mechanism when this option is specified.
++
++@cindex @option{-lgcc}, use with @option{-nostdlib}
++@cindex @option{-nostdlib} and unresolved references
++@cindex unresolved references and @option{-nostdlib}
++@cindex @option{-lgcc}, use with @option{-nodefaultlibs}
++@cindex @option{-nodefaultlibs} and unresolved references
++@cindex unresolved references and @option{-nodefaultlibs}
++One of the standard libraries bypassed by @option{-nostdlib} and
++@option{-nodefaultlibs} is @file{libgcc.a}, a library of internal subroutines
++that GCC uses to overcome shortcomings of particular machines, or special
++needs for some languages.
++(@xref{Interface,,Interfacing to GCC Output,gccint,GNU Compiler
++Collection (GCC) Internals},
++for more discussion of @file{libgcc.a}.)
++In most cases, you need @file{libgcc.a} even when you want to avoid
++other standard libraries. In other words, when you specify @option{-nostdlib}
++or @option{-nodefaultlibs} you should usually specify @option{-lgcc} as well.
++This ensures that you have no unresolved references to internal GCC
++library subroutines. (For example, @samp{__main}, used to ensure C++
++constructors will be called; @pxref{Collect2,,@code{collect2}, gccint,
++GNU Compiler Collection (GCC) Internals}.)
++
++@item -pie
++@opindex pie
++Produce a position independent executable on targets which support it.
++For predictable results, you must also specify the same set of options
++that were used to generate code (@option{-fpie}, @option{-fPIE},
++or model suboptions) when you specify this option.
++
++@item -rdynamic
++@opindex rdynamic
++Pass the flag @option{-export-dynamic} to the ELF linker, on targets
++that support it. This instructs the linker to add all symbols, not
++only used ones, to the dynamic symbol table. This option is needed
++for some uses of @code{dlopen} or to allow obtaining backtraces
++from within a program.
++
++@item -s
++@opindex s
++Remove all symbol table and relocation information from the executable.
++
++@item -static
++@opindex static
++On systems that support dynamic linking, this prevents linking with the shared
++libraries. On other systems, this option has no effect.
++
++@item -shared
++@opindex shared
++Produce a shared object which can then be linked with other objects to
++form an executable. Not all systems support this option. For predictable
++results, you must also specify the same set of options that were used to
++generate code (@option{-fpic}, @option{-fPIC}, or model suboptions)
++when you specify this option.@footnote{On some systems, @samp{gcc -shared}
++needs to build supplementary stub code for constructors to work. On
++multi-libbed systems, @samp{gcc -shared} must select the correct support
++libraries to link against. Failing to supply the correct flags may lead
++to subtle defects. Supplying them in cases where they are not necessary
++is innocuous.}
++
++@item -shared-libgcc
++@itemx -static-libgcc
++@opindex shared-libgcc
++@opindex static-libgcc
++On systems that provide @file{libgcc} as a shared library, these options
++force the use of either the shared or static version respectively.
++If no shared version of @file{libgcc} was built when the compiler was
++configured, these options have no effect.
++
++There are several situations in which an application should use the
++shared @file{libgcc} instead of the static version. The most common
++of these is when the application wishes to throw and catch exceptions
++across different shared libraries. In that case, each of the libraries
++as well as the application itself should use the shared @file{libgcc}.
++
++Therefore, the G++ and GCJ drivers automatically add
++@option{-shared-libgcc} whenever you build a shared library or a main
++executable, because C++ and Java programs typically use exceptions, so
++this is the right thing to do.
++
++If, instead, you use the GCC driver to create shared libraries, you may
++find that they will not always be linked with the shared @file{libgcc}.
++If GCC finds, at its configuration time, that you have a non-GNU linker
++or a GNU linker that does not support option @option{--eh-frame-hdr},
++it will link the shared version of @file{libgcc} into shared libraries
++by default. Otherwise, it will take advantage of the linker and optimize
++away the linking with the shared version of @file{libgcc}, linking with
++the static version of libgcc by default. This allows exceptions to
++propagate through such shared libraries, without incurring relocation
++costs at library load time.
++
++However, if a library or main executable is supposed to throw or catch
++exceptions, you must link it using the G++ or GCJ driver, as appropriate
++for the languages used in the program, or using the option
++@option{-shared-libgcc}, such that it is linked with the shared
++@file{libgcc}.
++
++@item -symbolic
++@opindex symbolic
++Bind references to global symbols when building a shared object. Warn
++about any unresolved references (unless overridden by the link editor
++option @samp{-Xlinker -z -Xlinker defs}). Only a few systems support
++this option.
++
++@item -T @var{script}
++@opindex T
++@cindex linker script
++Use @var{script} as the linker script. This option is supported by most
++systems using the GNU linker. On some targets, such as bare-board
++targets without an operating system, the @option{-T} option may be required
++when linking to avoid references to undefined symbols.
++
++@item -Xlinker @var{option}
++@opindex Xlinker
++Pass @var{option} as an option to the linker. You can use this to
++supply system-specific linker options which GCC does not know how to
++recognize.
++
++If you want to pass an option that takes a separate argument, you must use
++@option{-Xlinker} twice, once for the option and once for the argument.
++For example, to pass @option{-assert definitions}, you must write
++@samp{-Xlinker -assert -Xlinker definitions}. It does not work to write
++@option{-Xlinker "-assert definitions"}, because this passes the entire
++string as a single argument, which is not what the linker expects.
++
++When using the GNU linker, it is usually more convenient to pass
++arguments to linker options using the @option{@var{option}=@var{value}}
++syntax than as separate arguments. For example, you can specify
++@samp{-Xlinker -Map=output.map} rather than
++@samp{-Xlinker -Map -Xlinker output.map}. Other linkers may not support
++this syntax for command-line options.
++
++@item -Wl,@var{option}
++@opindex Wl
++Pass @var{option} as an option to the linker. If @var{option} contains
++commas, it is split into multiple options at the commas. You can use this
++syntax to pass an argument to the option.
++For example, @samp{-Wl,-Map,output.map} passes @samp{-Map output.map} to the
++linker. When using the GNU linker, you can also get the same effect with
++@samp{-Wl,-Map=output.map}.
++
++@item -u @var{symbol}
++@opindex u
++Pretend the symbol @var{symbol} is undefined, to force linking of
++library modules to define it. You can use @option{-u} multiple times with
++different symbols to force loading of additional library modules.
++@end table
++
++@node Directory Options
++@section Options for Directory Search
++@cindex directory options
++@cindex options, directory search
++@cindex search path
++
++These options specify directories to search for header files, for
++libraries and for parts of the compiler:
++
++@table @gcctabopt
++@item -I@var{dir}
++@opindex I
++Add the directory @var{dir} to the head of the list of directories to be
++searched for header files. This can be used to override a system header
++file, substituting your own version, since these directories are
++searched before the system header file directories. However, you should
++not use this option to add directories that contain vendor-supplied
++system header files (use @option{-isystem} for that). If you use more than
++one @option{-I} option, the directories are scanned in left-to-right
++order; the standard system directories come after.
++
++If a standard system include directory, or a directory specified with
++@option{-isystem}, is also specified with @option{-I}, the @option{-I}
++option will be ignored. The directory will still be searched but as a
++system directory at its normal position in the system include chain.
++This is to ensure that GCC's procedure to fix buggy system headers and
++the ordering for the include_next directive are not inadvertently changed.
++If you really need to change the search order for system directories,
++use the @option{-nostdinc} and/or @option{-isystem} options.
++
++@item -iquote@var{dir}
++@opindex iquote
++Add the directory @var{dir} to the head of the list of directories to
++be searched for header files only for the case of @samp{#include
++"@var{file}"}; they are not searched for @samp{#include <@var{file}>},
++otherwise just like @option{-I}.
++
++@item -L@var{dir}
++@opindex L
++Add directory @var{dir} to the list of directories to be searched
++for @option{-l}.
++
++@item -B@var{prefix}
++@opindex B
++This option specifies where to find the executables, libraries,
++include files, and data files of the compiler itself.
++
++The compiler driver program runs one or more of the subprograms
++@file{cpp}, @file{cc1}, @file{as} and @file{ld}. It tries
++@var{prefix} as a prefix for each program it tries to run, both with and
++without @samp{@var{machine}/@var{version}/} (@pxref{Target Options}).
++
++For each subprogram to be run, the compiler driver first tries the
++@option{-B} prefix, if any. If that name is not found, or if @option{-B}
++was not specified, the driver tries two standard prefixes, which are
++@file{/usr/lib/gcc/} and @file{/usr/local/lib/gcc/}. If neither of
++those results in a file name that is found, the unmodified program
++name is searched for using the directories specified in your
++@env{PATH} environment variable.
++
++The compiler will check to see if the path provided by the @option{-B}
++refers to a directory, and if necessary it will add a directory
++separator character at the end of the path.
++
++@option{-B} prefixes that effectively specify directory names also apply
++to libraries in the linker, because the compiler translates these
++options into @option{-L} options for the linker. They also apply to
++includes files in the preprocessor, because the compiler translates these
++options into @option{-isystem} options for the preprocessor. In this case,
++the compiler appends @samp{include} to the prefix.
++
++The run-time support file @file{libgcc.a} can also be searched for using
++the @option{-B} prefix, if needed. If it is not found there, the two
++standard prefixes above are tried, and that is all. The file is left
++out of the link if it is not found by those means.
++
++Another way to specify a prefix much like the @option{-B} prefix is to use
++the environment variable @env{GCC_EXEC_PREFIX}. @xref{Environment
++Variables}.
++
++As a special kludge, if the path provided by @option{-B} is
++@file{[dir/]stage@var{N}/}, where @var{N} is a number in the range 0 to
++9, then it will be replaced by @file{[dir/]include}. This is to help
++with boot-strapping the compiler.
++
++@item -specs=@var{file}
++@opindex specs
++Process @var{file} after the compiler reads in the standard @file{specs}
++file, in order to override the defaults that the @file{gcc} driver
++program uses when determining what switches to pass to @file{cc1},
++@file{cc1plus}, @file{as}, @file{ld}, etc. More than one
++@option{-specs=@var{file}} can be specified on the command line, and they
++are processed in order, from left to right.
++
++@item --sysroot=@var{dir}
++@opindex sysroot
++Use @var{dir} as the logical root directory for headers and libraries.
++For example, if the compiler would normally search for headers in
++@file{/usr/include} and libraries in @file{/usr/lib}, it will instead
++search @file{@var{dir}/usr/include} and @file{@var{dir}/usr/lib}.
++
++If you use both this option and the @option{-isysroot} option, then
++the @option{--sysroot} option will apply to libraries, but the
++@option{-isysroot} option will apply to header files.
++
++The GNU linker (beginning with version 2.16) has the necessary support
++for this option. If your linker does not support this option, the
++header file aspect of @option{--sysroot} will still work, but the
++library aspect will not.
++
++@item -I-
++@opindex I-
++This option has been deprecated. Please use @option{-iquote} instead for
++@option{-I} directories before the @option{-I-} and remove the @option{-I-}.
++Any directories you specify with @option{-I} options before the @option{-I-}
++option are searched only for the case of @samp{#include "@var{file}"};
++they are not searched for @samp{#include <@var{file}>}.
++
++If additional directories are specified with @option{-I} options after
++the @option{-I-}, these directories are searched for all @samp{#include}
++directives. (Ordinarily @emph{all} @option{-I} directories are used
++this way.)
++
++In addition, the @option{-I-} option inhibits the use of the current
++directory (where the current input file came from) as the first search
++directory for @samp{#include "@var{file}"}. There is no way to
++override this effect of @option{-I-}. With @option{-I.} you can specify
++searching the directory which was current when the compiler was
++invoked. That is not exactly the same as what the preprocessor does
++by default, but it is often satisfactory.
++
++@option{-I-} does not inhibit the use of the standard system directories
++for header files. Thus, @option{-I-} and @option{-nostdinc} are
++independent.
++@end table
++
++@c man end
++
++@node Spec Files
++@section Specifying subprocesses and the switches to pass to them
++@cindex Spec Files
++
++@command{gcc} is a driver program. It performs its job by invoking a
++sequence of other programs to do the work of compiling, assembling and
++linking. GCC interprets its command-line parameters and uses these to
++deduce which programs it should invoke, and which command-line options
++it ought to place on their command lines. This behavior is controlled
++by @dfn{spec strings}. In most cases there is one spec string for each
++program that GCC can invoke, but a few programs have multiple spec
++strings to control their behavior. The spec strings built into GCC can
++be overridden by using the @option{-specs=} command-line switch to specify
++a spec file.
++
++@dfn{Spec files} are plaintext files that are used to construct spec
++strings. They consist of a sequence of directives separated by blank
++lines. The type of directive is determined by the first non-whitespace
++character on the line and it can be one of the following:
++
++@table @code
++@item %@var{command}
++Issues a @var{command} to the spec file processor. The commands that can
++appear here are:
++
++@table @code
++@item %include <@var{file}>
++@cindex %include
++Search for @var{file} and insert its text at the current point in the
++specs file.
++
++@item %include_noerr <@var{file}>
++@cindex %include_noerr
++Just like @samp{%include}, but do not generate an error message if the include
++file cannot be found.
++
++@item %rename @var{old_name} @var{new_name}
++@cindex %rename
++Rename the spec string @var{old_name} to @var{new_name}.
++
++@end table
++
++@item *[@var{spec_name}]:
++This tells the compiler to create, override or delete the named spec
++string. All lines after this directive up to the next directive or
++blank line are considered to be the text for the spec string. If this
++results in an empty string then the spec will be deleted. (Or, if the
++spec did not exist, then nothing will happened.) Otherwise, if the spec
++does not currently exist a new spec will be created. If the spec does
++exist then its contents will be overridden by the text of this
++directive, unless the first character of that text is the @samp{+}
++character, in which case the text will be appended to the spec.
++
++@item [@var{suffix}]:
++Creates a new @samp{[@var{suffix}] spec} pair. All lines after this directive
++and up to the next directive or blank line are considered to make up the
++spec string for the indicated suffix. When the compiler encounters an
++input file with the named suffix, it will processes the spec string in
++order to work out how to compile that file. For example:
++
++@smallexample
++.ZZ:
++z-compile -input %i
++@end smallexample
++
++This says that any input file whose name ends in @samp{.ZZ} should be
++passed to the program @samp{z-compile}, which should be invoked with the
++command-line switch @option{-input} and with the result of performing the
++@samp{%i} substitution. (See below.)
++
++As an alternative to providing a spec string, the text that follows a
++suffix directive can be one of the following:
++
++@table @code
++@item @@@var{language}
++This says that the suffix is an alias for a known @var{language}. This is
++similar to using the @option{-x} command-line switch to GCC to specify a
++language explicitly. For example:
++
++@smallexample
++.ZZ:
++@@c++
++@end smallexample
++
++Says that .ZZ files are, in fact, C++ source files.
++
++@item #@var{name}
++This causes an error messages saying:
++
++@smallexample
++@var{name} compiler not installed on this system.
++@end smallexample
++@end table
++
++GCC already has an extensive list of suffixes built into it.
++This directive will add an entry to the end of the list of suffixes, but
++since the list is searched from the end backwards, it is effectively
++possible to override earlier entries using this technique.
++
++@end table
++
++GCC has the following spec strings built into it. Spec files can
++override these strings or create their own. Note that individual
++targets can also add their own spec strings to this list.
++
++@smallexample
++asm Options to pass to the assembler
++asm_final Options to pass to the assembler post-processor
++cpp Options to pass to the C preprocessor
++cc1 Options to pass to the C compiler
++cc1plus Options to pass to the C++ compiler
++endfile Object files to include at the end of the link
++link Options to pass to the linker
++lib Libraries to include on the command line to the linker
++libgcc Decides which GCC support library to pass to the linker
++linker Sets the name of the linker
++predefines Defines to be passed to the C preprocessor
++signed_char Defines to pass to CPP to say whether @code{char} is signed
++ by default
++startfile Object files to include at the start of the link
++@end smallexample
++
++Here is a small example of a spec file:
++
++@smallexample
++%rename lib old_lib
++
++*lib:
++--start-group -lgcc -lc -leval1 --end-group %(old_lib)
++@end smallexample
++
++This example renames the spec called @samp{lib} to @samp{old_lib} and
++then overrides the previous definition of @samp{lib} with a new one.
++The new definition adds in some extra command-line options before
++including the text of the old definition.
++
++@dfn{Spec strings} are a list of command-line options to be passed to their
++corresponding program. In addition, the spec strings can contain
++@samp{%}-prefixed sequences to substitute variable text or to
++conditionally insert text into the command line. Using these constructs
++it is possible to generate quite complex command lines.
++
++Here is a table of all defined @samp{%}-sequences for spec
++strings. Note that spaces are not generated automatically around the
++results of expanding these sequences. Therefore you can concatenate them
++together or combine them with constant text in a single argument.
++
++@table @code
++@item %%
++Substitute one @samp{%} into the program name or argument.
++
++@item %i
++Substitute the name of the input file being processed.
++
++@item %b
++Substitute the basename of the input file being processed.
++This is the substring up to (and not including) the last period
++and not including the directory.
++
++@item %B
++This is the same as @samp{%b}, but include the file suffix (text after
++the last period).
++
++@item %d
++Marks the argument containing or following the @samp{%d} as a
++temporary file name, so that that file will be deleted if GCC exits
++successfully. Unlike @samp{%g}, this contributes no text to the
++argument.
++
++@item %g@var{suffix}
++Substitute a file name that has suffix @var{suffix} and is chosen
++once per compilation, and mark the argument in the same way as
++@samp{%d}. To reduce exposure to denial-of-service attacks, the file
++name is now chosen in a way that is hard to predict even when previously
++chosen file names are known. For example, @samp{%g.s @dots{} %g.o @dots{} %g.s}
++might turn into @samp{ccUVUUAU.s ccXYAXZ12.o ccUVUUAU.s}. @var{suffix} matches
++the regexp @samp{[.A-Za-z]*} or the special string @samp{%O}, which is
++treated exactly as if @samp{%O} had been preprocessed. Previously, @samp{%g}
++was simply substituted with a file name chosen once per compilation,
++without regard to any appended suffix (which was therefore treated
++just like ordinary text), making such attacks more likely to succeed.
++
++@item %u@var{suffix}
++Like @samp{%g}, but generates a new temporary file name even if
++@samp{%u@var{suffix}} was already seen.
++
++@item %U@var{suffix}
++Substitutes the last file name generated with @samp{%u@var{suffix}}, generating a
++new one if there is no such last file name. In the absence of any
++@samp{%u@var{suffix}}, this is just like @samp{%g@var{suffix}}, except they don't share
++the same suffix @emph{space}, so @samp{%g.s @dots{} %U.s @dots{} %g.s @dots{} %U.s}
++would involve the generation of two distinct file names, one
++for each @samp{%g.s} and another for each @samp{%U.s}. Previously, @samp{%U} was
++simply substituted with a file name chosen for the previous @samp{%u},
++without regard to any appended suffix.
++
++@item %j@var{suffix}
++Substitutes the name of the @code{HOST_BIT_BUCKET}, if any, and if it is
++writable, and if save-temps is off; otherwise, substitute the name
++of a temporary file, just like @samp{%u}. This temporary file is not
++meant for communication between processes, but rather as a junk
++disposal mechanism.
++
++@item %|@var{suffix}
++@itemx %m@var{suffix}
++Like @samp{%g}, except if @option{-pipe} is in effect. In that case
++@samp{%|} substitutes a single dash and @samp{%m} substitutes nothing at
++all. These are the two most common ways to instruct a program that it
++should read from standard input or write to standard output. If you
++need something more elaborate you can use an @samp{%@{pipe:@code{X}@}}
++construct: see for example @file{f/lang-specs.h}.
++
++@item %.@var{SUFFIX}
++Substitutes @var{.SUFFIX} for the suffixes of a matched switch's args
++when it is subsequently output with @samp{%*}. @var{SUFFIX} is
++terminated by the next space or %.
++
++@item %w
++Marks the argument containing or following the @samp{%w} as the
++designated output file of this compilation. This puts the argument
++into the sequence of arguments that @samp{%o} will substitute later.
++
++@item %o
++Substitutes the names of all the output files, with spaces
++automatically placed around them. You should write spaces
++around the @samp{%o} as well or the results are undefined.
++@samp{%o} is for use in the specs for running the linker.
++Input files whose names have no recognized suffix are not compiled
++at all, but they are included among the output files, so they will
++be linked.
++
++@item %O
++Substitutes the suffix for object files. Note that this is
++handled specially when it immediately follows @samp{%g, %u, or %U},
++because of the need for those to form complete file names. The
++handling is such that @samp{%O} is treated exactly as if it had already
++been substituted, except that @samp{%g, %u, and %U} do not currently
++support additional @var{suffix} characters following @samp{%O} as they would
++following, for example, @samp{.o}.
++
++@item %p
++Substitutes the standard macro predefinitions for the
++current target machine. Use this when running @code{cpp}.
++
++@item %P
++Like @samp{%p}, but puts @samp{__} before and after the name of each
++predefined macro, except for macros that start with @samp{__} or with
++@samp{_@var{L}}, where @var{L} is an uppercase letter. This is for ISO
++C@.
++
++@item %I
++Substitute any of @option{-iprefix} (made from @env{GCC_EXEC_PREFIX}),
++@option{-isysroot} (made from @env{TARGET_SYSTEM_ROOT}),
++@option{-isystem} (made from @env{COMPILER_PATH} and @option{-B} options)
++and @option{-imultilib} as necessary.
++
++@item %s
++Current argument is the name of a library or startup file of some sort.
++Search for that file in a standard list of directories and substitute
++the full name found.
++
++@item %e@var{str}
++Print @var{str} as an error message. @var{str} is terminated by a newline.
++Use this when inconsistent options are detected.
++
++@item %(@var{name})
++Substitute the contents of spec string @var{name} at this point.
++
++@item %[@var{name}]
++Like @samp{%(@dots{})} but put @samp{__} around @option{-D} arguments.
++
++@item %x@{@var{option}@}
++Accumulate an option for @samp{%X}.
++
++@item %X
++Output the accumulated linker options specified by @option{-Wl} or a @samp{%x}
++spec string.
++
++@item %Y
++Output the accumulated assembler options specified by @option{-Wa}.
++
++@item %Z
++Output the accumulated preprocessor options specified by @option{-Wp}.
++
++@item %a
++Process the @code{asm} spec. This is used to compute the
++switches to be passed to the assembler.
++
++@item %A
++Process the @code{asm_final} spec. This is a spec string for
++passing switches to an assembler post-processor, if such a program is
++needed.
++
++@item %l
++Process the @code{link} spec. This is the spec for computing the
++command line passed to the linker. Typically it will make use of the
++@samp{%L %G %S %D and %E} sequences.
++
++@item %D
++Dump out a @option{-L} option for each directory that GCC believes might
++contain startup files. If the target supports multilibs then the
++current multilib directory will be prepended to each of these paths.
++
++@item %L
++Process the @code{lib} spec. This is a spec string for deciding which
++libraries should be included on the command line to the linker.
++
++@item %G
++Process the @code{libgcc} spec. This is a spec string for deciding
++which GCC support library should be included on the command line to the linker.
++
++@item %S
++Process the @code{startfile} spec. This is a spec for deciding which
++object files should be the first ones passed to the linker. Typically
++this might be a file named @file{crt0.o}.
++
++@item %E
++Process the @code{endfile} spec. This is a spec string that specifies
++the last object files that will be passed to the linker.
++
++@item %C
++Process the @code{cpp} spec. This is used to construct the arguments
++to be passed to the C preprocessor.
++
++@item %1
++Process the @code{cc1} spec. This is used to construct the options to be
++passed to the actual C compiler (@samp{cc1}).
++
++@item %2
++Process the @code{cc1plus} spec. This is used to construct the options to be
++passed to the actual C++ compiler (@samp{cc1plus}).
++
++@item %*
++Substitute the variable part of a matched option. See below.
++Note that each comma in the substituted string is replaced by
++a single space.
++
++@item %<@code{S}
++Remove all occurrences of @code{-S} from the command line. Note---this
++command is position dependent. @samp{%} commands in the spec string
++before this one will see @code{-S}, @samp{%} commands in the spec string
++after this one will not.
++
++@item %:@var{function}(@var{args})
++Call the named function @var{function}, passing it @var{args}.
++@var{args} is first processed as a nested spec string, then split
++into an argument vector in the usual fashion. The function returns
++a string which is processed as if it had appeared literally as part
++of the current spec.
++
++The following built-in spec functions are provided:
++
++@table @code
++@item @code{getenv}
++The @code{getenv} spec function takes two arguments: an environment
++variable name and a string. If the environment variable is not
++defined, a fatal error is issued. Otherwise, the return value is the
++value of the environment variable concatenated with the string. For
++example, if @env{TOPDIR} is defined as @file{/path/to/top}, then:
++
++@smallexample
++%:getenv(TOPDIR /include)
++@end smallexample
++
++expands to @file{/path/to/top/include}.
++
++@item @code{if-exists}
++The @code{if-exists} spec function takes one argument, an absolute
++pathname to a file. If the file exists, @code{if-exists} returns the
++pathname. Here is a small example of its usage:
++
++@smallexample
++*startfile:
++crt0%O%s %:if-exists(crti%O%s) crtbegin%O%s
++@end smallexample
++
++@item @code{if-exists-else}
++The @code{if-exists-else} spec function is similar to the @code{if-exists}
++spec function, except that it takes two arguments. The first argument is
++an absolute pathname to a file. If the file exists, @code{if-exists-else}
++returns the pathname. If it does not exist, it returns the second argument.
++This way, @code{if-exists-else} can be used to select one file or another,
++based on the existence of the first. Here is a small example of its usage:
++
++@smallexample
++*startfile:
++crt0%O%s %:if-exists(crti%O%s) \
++%:if-exists-else(crtbeginT%O%s crtbegin%O%s)
++@end smallexample
++
++@item @code{replace-outfile}
++The @code{replace-outfile} spec function takes two arguments. It looks for the
++first argument in the outfiles array and replaces it with the second argument. Here
++is a small example of its usage:
++
++@smallexample
++%@{fgnu-runtime:%:replace-outfile(-lobjc -lobjc-gnu)@}
++@end smallexample
++
++@item @code{print-asm-header}
++The @code{print-asm-header} function takes no arguments and simply
++prints a banner like:
++
++@smallexample
++Assembler options
++=================
++
++Use "-Wa,OPTION" to pass "OPTION" to the assembler.
++@end smallexample
++
++It is used to separate compiler options from assembler options
++in the @option{--target-help} output.
++@end table
++
++@item %@{@code{S}@}
++Substitutes the @code{-S} switch, if that switch was given to GCC@.
++If that switch was not specified, this substitutes nothing. Note that
++the leading dash is omitted when specifying this option, and it is
++automatically inserted if the substitution is performed. Thus the spec
++string @samp{%@{foo@}} would match the command-line option @option{-foo}
++and would output the command line option @option{-foo}.
++
++@item %W@{@code{S}@}
++Like %@{@code{S}@} but mark last argument supplied within as a file to be
++deleted on failure.
++
++@item %@{@code{S}*@}
++Substitutes all the switches specified to GCC whose names start
++with @code{-S}, but which also take an argument. This is used for
++switches like @option{-o}, @option{-D}, @option{-I}, etc.
++GCC considers @option{-o foo} as being
++one switch whose names starts with @samp{o}. %@{o*@} would substitute this
++text, including the space. Thus two arguments would be generated.
++
++@item %@{@code{S}*&@code{T}*@}
++Like %@{@code{S}*@}, but preserve order of @code{S} and @code{T} options
++(the order of @code{S} and @code{T} in the spec is not significant).
++There can be any number of ampersand-separated variables; for each the
++wild card is optional. Useful for CPP as @samp{%@{D*&U*&A*@}}.
++
++@item %@{@code{S}:@code{X}@}
++Substitutes @code{X}, if the @samp{-S} switch was given to GCC@.
++
++@item %@{!@code{S}:@code{X}@}
++Substitutes @code{X}, if the @samp{-S} switch was @emph{not} given to GCC@.
++
++@item %@{@code{S}*:@code{X}@}
++Substitutes @code{X} if one or more switches whose names start with
++@code{-S} are specified to GCC@. Normally @code{X} is substituted only
++once, no matter how many such switches appeared. However, if @code{%*}
++appears somewhere in @code{X}, then @code{X} will be substituted once
++for each matching switch, with the @code{%*} replaced by the part of
++that switch that matched the @code{*}.
++
++@item %@{.@code{S}:@code{X}@}
++Substitutes @code{X}, if processing a file with suffix @code{S}.
++
++@item %@{!.@code{S}:@code{X}@}
++Substitutes @code{X}, if @emph{not} processing a file with suffix @code{S}.
++
++@item %@{,@code{S}:@code{X}@}
++Substitutes @code{X}, if processing a file for language @code{S}.
++
++@item %@{!,@code{S}:@code{X}@}
++Substitutes @code{X}, if not processing a file for language @code{S}.
++
++@item %@{@code{S}|@code{P}:@code{X}@}
++Substitutes @code{X} if either @code{-S} or @code{-P} was given to
++GCC@. This may be combined with @samp{!}, @samp{.}, @samp{,}, and
++@code{*} sequences as well, although they have a stronger binding than
++the @samp{|}. If @code{%*} appears in @code{X}, all of the
++alternatives must be starred, and only the first matching alternative
++is substituted.
++
++For example, a spec string like this:
++
++@smallexample
++%@{.c:-foo@} %@{!.c:-bar@} %@{.c|d:-baz@} %@{!.c|d:-boggle@}
++@end smallexample
++
++will output the following command-line options from the following input
++command-line options:
++
++@smallexample
++fred.c -foo -baz
++jim.d -bar -boggle
++-d fred.c -foo -baz -boggle
++-d jim.d -bar -baz -boggle
++@end smallexample
++
++@item %@{S:X; T:Y; :D@}
++
++If @code{S} was given to GCC, substitutes @code{X}; else if @code{T} was
++given to GCC, substitutes @code{Y}; else substitutes @code{D}. There can
++be as many clauses as you need. This may be combined with @code{.},
++@code{,}, @code{!}, @code{|}, and @code{*} as needed.
++
++
++@end table
++
++The conditional text @code{X} in a %@{@code{S}:@code{X}@} or similar
++construct may contain other nested @samp{%} constructs or spaces, or
++even newlines. They are processed as usual, as described above.
++Trailing white space in @code{X} is ignored. White space may also
++appear anywhere on the left side of the colon in these constructs,
++except between @code{.} or @code{*} and the corresponding word.
++
++The @option{-O}, @option{-f}, @option{-m}, and @option{-W} switches are
++handled specifically in these constructs. If another value of
++@option{-O} or the negated form of a @option{-f}, @option{-m}, or
++@option{-W} switch is found later in the command line, the earlier
++switch value is ignored, except with @{@code{S}*@} where @code{S} is
++just one letter, which passes all matching options.
++
++The character @samp{|} at the beginning of the predicate text is used to
++indicate that a command should be piped to the following command, but
++only if @option{-pipe} is specified.
++
++It is built into GCC which switches take arguments and which do not.
++(You might think it would be useful to generalize this to allow each
++compiler's spec to say which switches take arguments. But this cannot
++be done in a consistent fashion. GCC cannot even decide which input
++files have been specified without knowing which switches take arguments,
++and it must know which input files to compile in order to tell which
++compilers to run).
++
++GCC also knows implicitly that arguments starting in @option{-l} are to be
++treated as compiler output files, and passed to the linker in their
++proper position among the other output files.
++
++@c man begin OPTIONS
++
++@node Target Options
++@section Specifying Target Machine and Compiler Version
++@cindex target options
++@cindex cross compiling
++@cindex specifying machine version
++@cindex specifying compiler version and target machine
++@cindex compiler version, specifying
++@cindex target machine, specifying
++
++The usual way to run GCC is to run the executable called @file{gcc}, or
++@file{<machine>-gcc} when cross-compiling, or
++@file{<machine>-gcc-<version>} to run a version other than the one that
++was installed last. Sometimes this is inconvenient, so GCC provides
++options that will switch to another cross-compiler or version.
++
++@table @gcctabopt
++@item -b @var{machine}
++@opindex b
++The argument @var{machine} specifies the target machine for compilation.
++
++The value to use for @var{machine} is the same as was specified as the
++machine type when configuring GCC as a cross-compiler. For
++example, if a cross-compiler was configured with @samp{configure
++arm-elf}, meaning to compile for an arm processor with elf binaries,
++then you would specify @option{-b arm-elf} to run that cross compiler.
++Because there are other options beginning with @option{-b}, the
++configuration must contain a hyphen, or @option{-b} alone should be one
++argument followed by the configuration in the next argument.
++
++@item -V @var{version}
++@opindex V
++The argument @var{version} specifies which version of GCC to run.
++This is useful when multiple versions are installed. For example,
++@var{version} might be @samp{4.0}, meaning to run GCC version 4.0.
++@end table
++
++The @option{-V} and @option{-b} options work by running the
++@file{<machine>-gcc-<version>} executable, so there's no real reason to
++use them if you can just run that directly.
++
++@node Submodel Options
++@section Hardware Models and Configurations
++@cindex submodel options
++@cindex specifying hardware config
++@cindex hardware models and configurations, specifying
++@cindex machine dependent options
++
++Earlier we discussed the standard option @option{-b} which chooses among
++different installed compilers for completely different target
++machines, such as VAX vs.@: 68000 vs.@: 80386.
++
++In addition, each of these target machine types can have its own
++special options, starting with @samp{-m}, to choose among various
++hardware models or configurations---for example, 68010 vs 68020,
++floating coprocessor or none. A single installed version of the
++compiler can compile for any model or configuration, according to the
++options specified.
++
++Some configurations of the compiler also support additional special
++options, usually for compatibility with other compilers on the same
++platform.
++
++@c This list is ordered alphanumerically by subsection name.
++@c It should be the same order and spelling as these options are listed
++@c in Machine Dependent Options
++
++@menu
++* ARC Options::
++* ARM Options::
++* AVR Options::
++* Blackfin Options::
++* CRIS Options::
++* CRX Options::
++* Darwin Options::
++* DEC Alpha Options::
++* DEC Alpha/VMS Options::
++* FR30 Options::
++* FRV Options::
++* GNU/Linux Options::
++* H8/300 Options::
++* HPPA Options::
++* i386 and x86-64 Options::
++* i386 and x86-64 Windows Options::
++* IA-64 Options::
++* M32C Options::
++* M32R/D Options::
++* M680x0 Options::
++* M68hc1x Options::
++* MCore Options::
++* MIPS Options::
++* MMIX Options::
++* MN10300 Options::
++* PDP-11 Options::
++* picoChip Options::
++* PowerPC Options::
++* RS/6000 and PowerPC Options::
++* S/390 and zSeries Options::
++* Score Options::
++* SH Options::
++* SPARC Options::
++* SPU Options::
++* System V Options::
++* V850 Options::
++* VAX Options::
++* VxWorks Options::
++* x86-64 Options::
++* Xstormy16 Options::
++* Xtensa Options::
++* zSeries Options::
++@end menu
++
++@node ARC Options
++@subsection ARC Options
++@cindex ARC Options
++
++These options are defined for ARC implementations:
++
++@table @gcctabopt
++@item -EL
++@opindex EL
++Compile code for little endian mode. This is the default.
++
++@item -EB
++@opindex EB
++Compile code for big endian mode.
++
++@item -mmangle-cpu
++@opindex mmangle-cpu
++Prepend the name of the cpu to all public symbol names.
++In multiple-processor systems, there are many ARC variants with different
++instruction and register set characteristics. This flag prevents code
++compiled for one cpu to be linked with code compiled for another.
++No facility exists for handling variants that are ``almost identical''.
++This is an all or nothing option.
++
++@item -mcpu=@var{cpu}
++@opindex mcpu
++Compile code for ARC variant @var{cpu}.
++Which variants are supported depend on the configuration.
++All variants support @option{-mcpu=base}, this is the default.
++
++@item -mtext=@var{text-section}
++@itemx -mdata=@var{data-section}
++@itemx -mrodata=@var{readonly-data-section}
++@opindex mtext
++@opindex mdata
++@opindex mrodata
++Put functions, data, and readonly data in @var{text-section},
++@var{data-section}, and @var{readonly-data-section} respectively
++by default. This can be overridden with the @code{section} attribute.
++@xref{Variable Attributes}.
++
++@item -mfix-cortex-m3-ldrd
++@opindex mfix-cortex-m3-ldrd
++Some Cortex-M3 cores can cause data corruption when @code{ldrd} instructions
++with overlapping destination and base registers are used. This option avoids
++generating these instructions. This option is enabled by default when
++@option{-mcpu=cortex-m3} is specified.
++
++@end table
++
++@node ARM Options
++@subsection ARM Options
++@cindex ARM options
++
++These @samp{-m} options are defined for Advanced RISC Machines (ARM)
++architectures:
++
++@table @gcctabopt
++@item -mabi=@var{name}
++@opindex mabi
++Generate code for the specified ABI@. Permissible values are: @samp{apcs-gnu},
++@samp{atpcs}, @samp{aapcs}, @samp{aapcs-linux} and @samp{iwmmxt}.
++
++@item -mapcs-frame
++@opindex mapcs-frame
++Generate a stack frame that is compliant with the ARM Procedure Call
++Standard for all functions, even if this is not strictly necessary for
++correct execution of the code. Specifying @option{-fomit-frame-pointer}
++with this option will cause the stack frames not to be generated for
++leaf functions. The default is @option{-mno-apcs-frame}.
++
++@item -mapcs
++@opindex mapcs
++This is a synonym for @option{-mapcs-frame}.
++
++@ignore
++@c not currently implemented
++@item -mapcs-stack-check
++@opindex mapcs-stack-check
++Generate code to check the amount of stack space available upon entry to
++every function (that actually uses some stack space). If there is
++insufficient space available then either the function
++@samp{__rt_stkovf_split_small} or @samp{__rt_stkovf_split_big} will be
++called, depending upon the amount of stack space required. The run time
++system is required to provide these functions. The default is
++@option{-mno-apcs-stack-check}, since this produces smaller code.
++
++@c not currently implemented
++@item -mapcs-float
++@opindex mapcs-float
++Pass floating point arguments using the float point registers. This is
++one of the variants of the APCS@. This option is recommended if the
++target hardware has a floating point unit or if a lot of floating point
++arithmetic is going to be performed by the code. The default is
++@option{-mno-apcs-float}, since integer only code is slightly increased in
++size if @option{-mapcs-float} is used.
++
++@c not currently implemented
++@item -mapcs-reentrant
++@opindex mapcs-reentrant
++Generate reentrant, position independent code. The default is
++@option{-mno-apcs-reentrant}.
++@end ignore
++
++@item -mthumb-interwork
++@opindex mthumb-interwork
++Generate code which supports calling between the ARM and Thumb
++instruction sets. Without this option the two instruction sets cannot
++be reliably used inside one program. The default is
++@option{-mno-thumb-interwork}, since slightly larger code is generated
++when @option{-mthumb-interwork} is specified.
++
++@item -mno-sched-prolog
++@opindex mno-sched-prolog
++Prevent the reordering of instructions in the function prolog, or the
++merging of those instruction with the instructions in the function's
++body. This means that all functions will start with a recognizable set
++of instructions (or in fact one of a choice from a small set of
++different function prologues), and this information can be used to
++locate the start if functions inside an executable piece of code. The
++default is @option{-msched-prolog}.
++
++@item -mfloat-abi=@var{name}
++@opindex mfloat-abi
++Specifies which floating-point ABI to use. Permissible values
++are: @samp{soft}, @samp{softfp} and @samp{hard}.
++
++Specifying @samp{soft} causes GCC to generate output containing
++library calls for floating-point operations.
++@samp{softfp} allows the generation of code using hardware floating-point
++instructions, but still uses the soft-float calling conventions.
++@samp{hard} allows generation of floating-point instructions
++and uses FPU-specific calling conventions.
++
++Using @option{-mfloat-abi=hard} with VFP coprocessors is not supported.
++Use @option{-mfloat-abi=softfp} with the appropriate @option{-mfpu} option
++to allow the compiler to generate code that makes use of the hardware
++floating-point capabilities for these CPUs.
++
++The default depends on the specific target configuration. Note that
++the hard-float and soft-float ABIs are not link-compatible; you must
++compile your entire program with the same ABI, and link with a
++compatible set of libraries.
++
++@item -mhard-float
++@opindex mhard-float
++Equivalent to @option{-mfloat-abi=hard}.
++
++@item -msoft-float
++@opindex msoft-float
++Equivalent to @option{-mfloat-abi=soft}.
++
++@item -mlittle-endian
++@opindex mlittle-endian
++Generate code for a processor running in little-endian mode. This is
++the default for all standard configurations.
++
++@item -mbig-endian
++@opindex mbig-endian
++Generate code for a processor running in big-endian mode; the default is
++to compile code for a little-endian processor.
++
++@item -mwords-little-endian
++@opindex mwords-little-endian
++This option only applies when generating code for big-endian processors.
++Generate code for a little-endian word order but a big-endian byte
++order. That is, a byte order of the form @samp{32107654}. Note: this
++option should only be used if you require compatibility with code for
++big-endian ARM processors generated by versions of the compiler prior to
++2.8.
++
++@item -mcpu=@var{name}
++@opindex mcpu
++This specifies the name of the target ARM processor. GCC uses this name
++to determine what kind of instructions it can emit when generating
++assembly code. Permissible names are: @samp{arm2}, @samp{arm250},
++@samp{arm3}, @samp{arm6}, @samp{arm60}, @samp{arm600}, @samp{arm610},
++@samp{arm620}, @samp{arm7}, @samp{arm7m}, @samp{arm7d}, @samp{arm7dm},
++@samp{arm7di}, @samp{arm7dmi}, @samp{arm70}, @samp{arm700},
++@samp{arm700i}, @samp{arm710}, @samp{arm710c}, @samp{arm7100},
++@samp{arm720},
++@samp{arm7500}, @samp{arm7500fe}, @samp{arm7tdmi}, @samp{arm7tdmi-s},
++@samp{arm710t}, @samp{arm720t}, @samp{arm740t},
++@samp{strongarm}, @samp{strongarm110}, @samp{strongarm1100},
++@samp{strongarm1110},
++@samp{arm8}, @samp{arm810}, @samp{arm9}, @samp{arm9e}, @samp{arm920},
++@samp{arm920t}, @samp{arm922t}, @samp{arm946e-s}, @samp{arm966e-s},
++@samp{arm968e-s}, @samp{arm926ej-s}, @samp{arm940t}, @samp{arm9tdmi},
++@samp{arm10tdmi}, @samp{arm1020t}, @samp{arm1026ej-s},
++@samp{arm10e}, @samp{arm1020e}, @samp{arm1022e},
++@samp{arm1136j-s}, @samp{arm1136jf-s}, @samp{mpcore}, @samp{mpcorenovfp},
++@samp{arm1156t2-s}, @samp{arm1176jz-s}, @samp{arm1176jzf-s},
++@samp{cortex-a8}, @samp{cortex-a9},
++@samp{cortex-r4}, @samp{cortex-r4f}, @samp{cortex-m3},
++@samp{cortex-m1},
++@samp{xscale}, @samp{iwmmxt}, @samp{iwmmxt2}, @samp{ep9312}.
++
++@item -mtune=@var{name}
++@opindex mtune
++This option is very similar to the @option{-mcpu=} option, except that
++instead of specifying the actual target processor type, and hence
++restricting which instructions can be used, it specifies that GCC should
++tune the performance of the code as if the target were of the type
++specified in this option, but still choosing the instructions that it
++will generate based on the cpu specified by a @option{-mcpu=} option.
++For some ARM implementations better performance can be obtained by using
++this option.
++
++@item -march=@var{name}
++@opindex march
++This specifies the name of the target ARM architecture. GCC uses this
++name to determine what kind of instructions it can emit when generating
++assembly code. This option can be used in conjunction with or instead
++of the @option{-mcpu=} option. Permissible names are: @samp{armv2},
++@samp{armv2a}, @samp{armv3}, @samp{armv3m}, @samp{armv4}, @samp{armv4t},
++@samp{armv5}, @samp{armv5t}, @samp{armv5e}, @samp{armv5te},
++@samp{armv6}, @samp{armv6j},
++@samp{armv6t2}, @samp{armv6z}, @samp{armv6zk}, @samp{armv6-m},
++@samp{armv7}, @samp{armv7-a}, @samp{armv7-r}, @samp{armv7-m},
++@samp{iwmmxt}, @samp{iwmmxt2}, @samp{ep9312}.
++
++@item -mfpu=@var{name}
++@itemx -mfpe=@var{number}
++@itemx -mfp=@var{number}
++@opindex mfpu
++@opindex mfpe
++@opindex mfp
++This specifies what floating point hardware (or hardware emulation) is
++available on the target. Permissible names are: @samp{fpa}, @samp{fpe2},
++@samp{fpe3}, @samp{maverick}, @samp{vfp}, @samp{vfpv3}, @samp{vfpv3-d16} and
++@samp{neon}. @option{-mfp} and @option{-mfpe}
++are synonyms for @option{-mfpu}=@samp{fpe}@var{number}, for compatibility
++with older versions of GCC@.
++
++If @option{-msoft-float} is specified this specifies the format of
++floating point values.
++
++@item -mstructure-size-boundary=@var{n}
++@opindex mstructure-size-boundary
++The size of all structures and unions will be rounded up to a multiple
++of the number of bits set by this option. Permissible values are 8, 32
++and 64. The default value varies for different toolchains. For the COFF
++targeted toolchain the default value is 8. A value of 64 is only allowed
++if the underlying ABI supports it.
++
++Specifying the larger number can produce faster, more efficient code, but
++can also increase the size of the program. Different values are potentially
++incompatible. Code compiled with one value cannot necessarily expect to
++work with code or libraries compiled with another value, if they exchange
++information using structures or unions.
++
++@item -mabort-on-noreturn
++@opindex mabort-on-noreturn
++Generate a call to the function @code{abort} at the end of a
++@code{noreturn} function. It will be executed if the function tries to
++return.
++
++@item -mlong-calls
++@itemx -mno-long-calls
++@opindex mlong-calls
++@opindex mno-long-calls
++Tells the compiler to perform function calls by first loading the
++address of the function into a register and then performing a subroutine
++call on this register. This switch is needed if the target function
++will lie outside of the 64 megabyte addressing range of the offset based
++version of subroutine call instruction.
++
++Even if this switch is enabled, not all function calls will be turned
++into long calls. The heuristic is that static functions, functions
++which have the @samp{short-call} attribute, functions that are inside
++the scope of a @samp{#pragma no_long_calls} directive and functions whose
++definitions have already been compiled within the current compilation
++unit, will not be turned into long calls. The exception to this rule is
++that weak function definitions, functions with the @samp{long-call}
++attribute or the @samp{section} attribute, and functions that are within
++the scope of a @samp{#pragma long_calls} directive, will always be
++turned into long calls.
++
++This feature is not enabled by default. Specifying
++@option{-mno-long-calls} will restore the default behavior, as will
++placing the function calls within the scope of a @samp{#pragma
++long_calls_off} directive. Note these switches have no effect on how
++the compiler generates code to handle function calls via function
++pointers.
++
++@item -msingle-pic-base
++@opindex msingle-pic-base
++Treat the register used for PIC addressing as read-only, rather than
++loading it in the prologue for each function. The run-time system is
++responsible for initializing this register with an appropriate value
++before execution begins.
++
++@item -mpic-register=@var{reg}
++@opindex mpic-register
++Specify the register to be used for PIC addressing. The default is R10
++unless stack-checking is enabled, when R9 is used.
++
++@item -mcirrus-fix-invalid-insns
++@opindex mcirrus-fix-invalid-insns
++@opindex mno-cirrus-fix-invalid-insns
++Insert NOPs into the instruction stream to in order to work around
++problems with invalid Maverick instruction combinations. This option
++is only valid if the @option{-mcpu=ep9312} option has been used to
++enable generation of instructions for the Cirrus Maverick floating
++point co-processor. This option is not enabled by default, since the
++problem is only present in older Maverick implementations. The default
++can be re-enabled by use of the @option{-mno-cirrus-fix-invalid-insns}
++switch.
++
++@item -mpoke-function-name
++@opindex mpoke-function-name
++Write the name of each function into the text section, directly
++preceding the function prologue. The generated code is similar to this:
++
++@smallexample
++ t0
++ .ascii "arm_poke_function_name", 0
++ .align
++ t1
++ .word 0xff000000 + (t1 - t0)
++ arm_poke_function_name
++ mov ip, sp
++ stmfd sp!, @{fp, ip, lr, pc@}
++ sub fp, ip, #4
++@end smallexample
++
++When performing a stack backtrace, code can inspect the value of
++@code{pc} stored at @code{fp + 0}. If the trace function then looks at
++location @code{pc - 12} and the top 8 bits are set, then we know that
++there is a function name embedded immediately preceding this location
++and has length @code{((pc[-3]) & 0xff000000)}.
++
++@item -mthumb
++@opindex mthumb
++Generate code for the Thumb instruction set. The default is to
++use the 32-bit ARM instruction set.
++This option automatically enables either 16-bit Thumb-1 or
++mixed 16/32-bit Thumb-2 instructions based on the @option{-mcpu=@var{name}}
++and @option{-march=@var{name}} options.
++
++@item -mtpcs-frame
++@opindex mtpcs-frame
++Generate a stack frame that is compliant with the Thumb Procedure Call
++Standard for all non-leaf functions. (A leaf function is one that does
++not call any other functions.) The default is @option{-mno-tpcs-frame}.
++
++@item -mtpcs-leaf-frame
++@opindex mtpcs-leaf-frame
++Generate a stack frame that is compliant with the Thumb Procedure Call
++Standard for all leaf functions. (A leaf function is one that does
++not call any other functions.) The default is @option{-mno-apcs-leaf-frame}.
++
++@item -mcallee-super-interworking
++@opindex mcallee-super-interworking
++Gives all externally visible functions in the file being compiled an ARM
++instruction set header which switches to Thumb mode before executing the
++rest of the function. This allows these functions to be called from
++non-interworking code.
++
++@item -mcaller-super-interworking
++@opindex mcaller-super-interworking
++Allows calls via function pointers (including virtual functions) to
++execute correctly regardless of whether the target code has been
++compiled for interworking or not. There is a small overhead in the cost
++of executing a function pointer if this option is enabled.
++
++@item -mtp=@var{name}
++@opindex mtp
++Specify the access model for the thread local storage pointer. The valid
++models are @option{soft}, which generates calls to @code{__aeabi_read_tp},
++@option{cp15}, which fetches the thread pointer from @code{cp15} directly
++(supported in the arm6k architecture), and @option{auto}, which uses the
++best available method for the selected processor. The default setting is
++@option{auto}.
++
++@item -mword-relocations
++@opindex mword-relocations
++Only generate absolute relocations on word sized values (i.e. R_ARM_ABS32).
++This is enabled by default on targets (uClinux, SymbianOS) where the runtime
++loader imposes this restriction, and when @option{-fpic} or @option{-fPIC}
++is specified.
++
++@end table
++
++@node AVR Options
++@subsection AVR Options
++@cindex AVR Options
++
++These options are defined for AVR implementations:
++
++@table @gcctabopt
++@item -mmcu=@var{mcu}
++@opindex mmcu
++Specify ATMEL AVR instruction set or MCU type.
++
++Instruction set avr1 is for the minimal AVR core, not supported by the C
++compiler, only for assembler programs (MCU types: at90s1200, attiny10,
++attiny11, attiny12, attiny15, attiny28).
++
++Instruction set avr2 (default) is for the classic AVR core with up to
++8K program memory space (MCU types: at90s2313, at90s2323, attiny22,
++at90s2333, at90s2343, at90s4414, at90s4433, at90s4434, at90s8515,
++at90c8534, at90s8535).
++
++Instruction set avr3 is for the classic AVR core with up to 128K program
++memory space (MCU types: atmega103, atmega603, at43usb320, at76c711).
++
++Instruction set avr4 is for the enhanced AVR core with up to 8K program
++memory space (MCU types: atmega8, atmega83, atmega85).
++
++Instruction set avr5 is for the enhanced AVR core with up to 128K program
++memory space (MCU types: atmega16, atmega161, atmega163, atmega32, atmega323,
++atmega64, atmega128, at43usb355, at94k).
++
++@item -msize
++@opindex msize
++Output instruction sizes to the asm file.
++
++@item -mno-interrupts
++@opindex mno-interrupts
++Generated code is not compatible with hardware interrupts.
++Code size will be smaller.
++
++@item -mcall-prologues
++@opindex mcall-prologues
++Functions prologues/epilogues expanded as call to appropriate
++subroutines. Code size will be smaller.
++
++@item -mno-tablejump
++@opindex mno-tablejump
++Do not generate tablejump insns which sometimes increase code size.
++The option is now deprecated in favor of the equivalent
++@option{-fno-jump-tables}
++
++@item -mtiny-stack
++@opindex mtiny-stack
++Change only the low 8 bits of the stack pointer.
++
++@item -mint8
++@opindex mint8
++Assume int to be 8 bit integer. This affects the sizes of all types: A
++char will be 1 byte, an int will be 1 byte, an long will be 2 bytes
++and long long will be 4 bytes. Please note that this option does not
++comply to the C standards, but it will provide you with smaller code
++size.
++@end table
++
++@node Blackfin Options
++@subsection Blackfin Options
++@cindex Blackfin Options
++
++@table @gcctabopt
++@item -mcpu=@var{cpu}@r{[}-@var{sirevision}@r{]}
++@opindex mcpu=
++Specifies the name of the target Blackfin processor. Currently, @var{cpu}
++can be one of @samp{bf512}, @samp{bf514}, @samp{bf516}, @samp{bf518},
++@samp{bf522}, @samp{bf523}, @samp{bf524}, @samp{bf525}, @samp{bf526},
++@samp{bf527}, @samp{bf531}, @samp{bf532}, @samp{bf533},
++@samp{bf534}, @samp{bf536}, @samp{bf537}, @samp{bf538}, @samp{bf539},
++@samp{bf542}, @samp{bf544}, @samp{bf547}, @samp{bf548}, @samp{bf549},
++@samp{bf561}.
++The optional @var{sirevision} specifies the silicon revision of the target
++Blackfin processor. Any workarounds available for the targeted silicon revision
++will be enabled. If @var{sirevision} is @samp{none}, no workarounds are enabled.
++If @var{sirevision} is @samp{any}, all workarounds for the targeted processor
++will be enabled. The @code{__SILICON_REVISION__} macro is defined to two
++hexadecimal digits representing the major and minor numbers in the silicon
++revision. If @var{sirevision} is @samp{none}, the @code{__SILICON_REVISION__}
++is not defined. If @var{sirevision} is @samp{any}, the
++@code{__SILICON_REVISION__} is defined to be @code{0xffff}.
++If this optional @var{sirevision} is not used, GCC assumes the latest known
++silicon revision of the targeted Blackfin processor.
++
++Support for @samp{bf561} is incomplete. For @samp{bf561},
++Only the processor macro is defined.
++Without this option, @samp{bf532} is used as the processor by default.
++The corresponding predefined processor macros for @var{cpu} is to
++be defined. And for @samp{bfin-elf} toolchain, this causes the hardware BSP
++provided by libgloss to be linked in if @option{-msim} is not given.
++
++@item -msim
++@opindex msim
++Specifies that the program will be run on the simulator. This causes
++the simulator BSP provided by libgloss to be linked in. This option
++has effect only for @samp{bfin-elf} toolchain.
++Certain other options, such as @option{-mid-shared-library} and
++@option{-mfdpic}, imply @option{-msim}.
++
++@item -momit-leaf-frame-pointer
++@opindex momit-leaf-frame-pointer
++Don't keep the frame pointer in a register for leaf functions. This
++avoids the instructions to save, set up and restore frame pointers and
++makes an extra register available in leaf functions. The option
++@option{-fomit-frame-pointer} removes the frame pointer for all functions
++which might make debugging harder.
++
++@item -mspecld-anomaly
++@opindex mspecld-anomaly
++When enabled, the compiler will ensure that the generated code does not
++contain speculative loads after jump instructions. If this option is used,
++@code{__WORKAROUND_SPECULATIVE_LOADS} is defined.
++
++@item -mno-specld-anomaly
++@opindex mno-specld-anomaly
++Don't generate extra code to prevent speculative loads from occurring.
++
++@item -mcsync-anomaly
++@opindex mcsync-anomaly
++When enabled, the compiler will ensure that the generated code does not
++contain CSYNC or SSYNC instructions too soon after conditional branches.
++If this option is used, @code{__WORKAROUND_SPECULATIVE_SYNCS} is defined.
++
++@item -mno-csync-anomaly
++@opindex mno-csync-anomaly
++Don't generate extra code to prevent CSYNC or SSYNC instructions from
++occurring too soon after a conditional branch.
++
++@item -mlow-64k
++@opindex mlow-64k
++When enabled, the compiler is free to take advantage of the knowledge that
++the entire program fits into the low 64k of memory.
++
++@item -mno-low-64k
++@opindex mno-low-64k
++Assume that the program is arbitrarily large. This is the default.
++
++@item -mstack-check-l1
++@opindex mstack-check-l1
++Do stack checking using information placed into L1 scratchpad memory by the
++uClinux kernel.
++
++@item -mid-shared-library
++@opindex mid-shared-library
++Generate code that supports shared libraries via the library ID method.
++This allows for execute in place and shared libraries in an environment
++without virtual memory management. This option implies @option{-fPIC}.
++With a @samp{bfin-elf} target, this option implies @option{-msim}.
++
++@item -mno-id-shared-library
++@opindex mno-id-shared-library
++Generate code that doesn't assume ID based shared libraries are being used.
++This is the default.
++
++@item -mleaf-id-shared-library
++@opindex mleaf-id-shared-library
++Generate code that supports shared libraries via the library ID method,
++but assumes that this library or executable won't link against any other
++ID shared libraries. That allows the compiler to use faster code for jumps
++and calls.
++
++@item -mno-leaf-id-shared-library
++@opindex mno-leaf-id-shared-library
++Do not assume that the code being compiled won't link against any ID shared
++libraries. Slower code will be generated for jump and call insns.
++
++@item -mshared-library-id=n
++@opindex mshared-library-id
++Specified the identification number of the ID based shared library being
++compiled. Specifying a value of 0 will generate more compact code, specifying
++other values will force the allocation of that number to the current
++library but is no more space or time efficient than omitting this option.
++
++@item -msep-data
++@opindex msep-data
++Generate code that allows the data segment to be located in a different
++area of memory from the text segment. This allows for execute in place in
++an environment without virtual memory management by eliminating relocations
++against the text section.
++
++@item -mno-sep-data
++@opindex mno-sep-data
++Generate code that assumes that the data segment follows the text segment.
++This is the default.
++
++@item -mlong-calls
++@itemx -mno-long-calls
++@opindex mlong-calls
++@opindex mno-long-calls
++Tells the compiler to perform function calls by first loading the
++address of the function into a register and then performing a subroutine
++call on this register. This switch is needed if the target function
++will lie outside of the 24 bit addressing range of the offset based
++version of subroutine call instruction.
++
++This feature is not enabled by default. Specifying
++@option{-mno-long-calls} will restore the default behavior. Note these
++switches have no effect on how the compiler generates code to handle
++function calls via function pointers.
++
++@item -mfast-fp
++@opindex mfast-fp
++Link with the fast floating-point library. This library relaxes some of
++the IEEE floating-point standard's rules for checking inputs against
++Not-a-Number (NAN), in the interest of performance.
++
++@item -minline-plt
++@opindex minline-plt
++Enable inlining of PLT entries in function calls to functions that are
++not known to bind locally. It has no effect without @option{-mfdpic}.
++
++@item -mmulticore
++@opindex mmulticore
++Build standalone application for multicore Blackfin processor. Proper
++start files and link scripts will be used to support multicore.
++This option defines @code{__BFIN_MULTICORE}. It can only be used with
++@option{-mcpu=bf561@r{[}-@var{sirevision}@r{]}}. It can be used with
++@option{-mcorea} or @option{-mcoreb}. If it's used without
++@option{-mcorea} or @option{-mcoreb}, single application/dual core
++programming model is used. In this model, the main function of Core B
++should be named as coreb_main. If it's used with @option{-mcorea} or
++@option{-mcoreb}, one application per core programming model is used.
++If this option is not used, single core application programming
++model is used.
++
++@item -mcorea
++@opindex mcorea
++Build standalone application for Core A of BF561 when using
++one application per core programming model. Proper start files
++and link scripts will be used to support Core A. This option
++defines @code{__BFIN_COREA}. It must be used with @option{-mmulticore}.
++
++@item -mcoreb
++@opindex mcoreb
++Build standalone application for Core B of BF561 when using
++one application per core programming model. Proper start files
++and link scripts will be used to support Core B. This option
++defines @code{__BFIN_COREB}. When this option is used, coreb_main
++should be used instead of main. It must be used with
++@option{-mmulticore}.
++
++@item -msdram
++@opindex msdram
++Build standalone application for SDRAM. Proper start files and
++link scripts will be used to put the application into SDRAM.
++Loader should initialize SDRAM before loading the application
++into SDRAM. This option defines @code{__BFIN_SDRAM}.
++
++@item -micplb
++@opindex micplb
++Assume that ICPLBs are enabled at runtime. This has an effect on certain
++anomaly workarounds. For Linux targets, the default is to assume ICPLBs
++are enabled; for standalone applications the default is off.
++@end table
++
++@node CRIS Options
++@subsection CRIS Options
++@cindex CRIS Options
++
++These options are defined specifically for the CRIS ports.
++
++@table @gcctabopt
++@item -march=@var{architecture-type}
++@itemx -mcpu=@var{architecture-type}
++@opindex march
++@opindex mcpu
++Generate code for the specified architecture. The choices for
++@var{architecture-type} are @samp{v3}, @samp{v8} and @samp{v10} for
++respectively ETRAX@w{ }4, ETRAX@w{ }100, and ETRAX@w{ }100@w{ }LX@.
++Default is @samp{v0} except for cris-axis-linux-gnu, where the default is
++@samp{v10}.
++
++@item -mtune=@var{architecture-type}
++@opindex mtune
++Tune to @var{architecture-type} everything applicable about the generated
++code, except for the ABI and the set of available instructions. The
++choices for @var{architecture-type} are the same as for
++@option{-march=@var{architecture-type}}.
++
++@item -mmax-stack-frame=@var{n}
++@opindex mmax-stack-frame
++Warn when the stack frame of a function exceeds @var{n} bytes.
++
++@item -metrax4
++@itemx -metrax100
++@opindex metrax4
++@opindex metrax100
++The options @option{-metrax4} and @option{-metrax100} are synonyms for
++@option{-march=v3} and @option{-march=v8} respectively.
++
++@item -mmul-bug-workaround
++@itemx -mno-mul-bug-workaround
++@opindex mmul-bug-workaround
++@opindex mno-mul-bug-workaround
++Work around a bug in the @code{muls} and @code{mulu} instructions for CPU
++models where it applies. This option is active by default.
++
++@item -mpdebug
++@opindex mpdebug
++Enable CRIS-specific verbose debug-related information in the assembly
++code. This option also has the effect to turn off the @samp{#NO_APP}
++formatted-code indicator to the assembler at the beginning of the
++assembly file.
++
++@item -mcc-init
++@opindex mcc-init
++Do not use condition-code results from previous instruction; always emit
++compare and test instructions before use of condition codes.
++
++@item -mno-side-effects
++@opindex mno-side-effects
++Do not emit instructions with side-effects in addressing modes other than
++post-increment.
++
++@item -mstack-align
++@itemx -mno-stack-align
++@itemx -mdata-align
++@itemx -mno-data-align
++@itemx -mconst-align
++@itemx -mno-const-align
++@opindex mstack-align
++@opindex mno-stack-align
++@opindex mdata-align
++@opindex mno-data-align
++@opindex mconst-align
++@opindex mno-const-align
++These options (no-options) arranges (eliminate arrangements) for the
++stack-frame, individual data and constants to be aligned for the maximum
++single data access size for the chosen CPU model. The default is to
++arrange for 32-bit alignment. ABI details such as structure layout are
++not affected by these options.
++
++@item -m32-bit
++@itemx -m16-bit
++@itemx -m8-bit
++@opindex m32-bit
++@opindex m16-bit
++@opindex m8-bit
++Similar to the stack- data- and const-align options above, these options
++arrange for stack-frame, writable data and constants to all be 32-bit,
++16-bit or 8-bit aligned. The default is 32-bit alignment.
++
++@item -mno-prologue-epilogue
++@itemx -mprologue-epilogue
++@opindex mno-prologue-epilogue
++@opindex mprologue-epilogue
++With @option{-mno-prologue-epilogue}, the normal function prologue and
++epilogue that sets up the stack-frame are omitted and no return
++instructions or return sequences are generated in the code. Use this
++option only together with visual inspection of the compiled code: no
++warnings or errors are generated when call-saved registers must be saved,
++or storage for local variable needs to be allocated.
++
++@item -mno-gotplt
++@itemx -mgotplt
++@opindex mno-gotplt
++@opindex mgotplt
++With @option{-fpic} and @option{-fPIC}, don't generate (do generate)
++instruction sequences that load addresses for functions from the PLT part
++of the GOT rather than (traditional on other architectures) calls to the
++PLT@. The default is @option{-mgotplt}.
++
++@item -melf
++@opindex melf
++Legacy no-op option only recognized with the cris-axis-elf and
++cris-axis-linux-gnu targets.
++
++@item -mlinux
++@opindex mlinux
++Legacy no-op option only recognized with the cris-axis-linux-gnu target.
++
++@item -sim
++@opindex sim
++This option, recognized for the cris-axis-elf arranges
++to link with input-output functions from a simulator library. Code,
++initialized data and zero-initialized data are allocated consecutively.
++
++@item -sim2
++@opindex sim2
++Like @option{-sim}, but pass linker options to locate initialized data at
++0x40000000 and zero-initialized data at 0x80000000.
++@end table
++
++@node CRX Options
++@subsection CRX Options
++@cindex CRX Options
++
++These options are defined specifically for the CRX ports.
++
++@table @gcctabopt
++
++@item -mmac
++@opindex mmac
++Enable the use of multiply-accumulate instructions. Disabled by default.
++
++@item -mpush-args
++@opindex mpush-args
++Push instructions will be used to pass outgoing arguments when functions
++are called. Enabled by default.
++@end table
++
++@node Darwin Options
++@subsection Darwin Options
++@cindex Darwin options
++
++These options are defined for all architectures running the Darwin operating
++system.
++
++FSF GCC on Darwin does not create ``fat'' object files; it will create
++an object file for the single architecture that it was built to
++target. Apple's GCC on Darwin does create ``fat'' files if multiple
++@option{-arch} options are used; it does so by running the compiler or
++linker multiple times and joining the results together with
++@file{lipo}.
++
++The subtype of the file created (like @samp{ppc7400} or @samp{ppc970} or
++@samp{i686}) is determined by the flags that specify the ISA
++that GCC is targetting, like @option{-mcpu} or @option{-march}. The
++@option{-force_cpusubtype_ALL} option can be used to override this.
++
++The Darwin tools vary in their behavior when presented with an ISA
++mismatch. The assembler, @file{as}, will only permit instructions to
++be used that are valid for the subtype of the file it is generating,
++so you cannot put 64-bit instructions in an @samp{ppc750} object file.
++The linker for shared libraries, @file{/usr/bin/libtool}, will fail
++and print an error if asked to create a shared library with a less
++restrictive subtype than its input files (for instance, trying to put
++a @samp{ppc970} object file in a @samp{ppc7400} library). The linker
++for executables, @file{ld}, will quietly give the executable the most
++restrictive subtype of any of its input files.
++
++@table @gcctabopt
++@item -F@var{dir}
++@opindex F
++Add the framework directory @var{dir} to the head of the list of
++directories to be searched for header files. These directories are
++interleaved with those specified by @option{-I} options and are
++scanned in a left-to-right order.
++
++A framework directory is a directory with frameworks in it. A
++framework is a directory with a @samp{"Headers"} and/or
++@samp{"PrivateHeaders"} directory contained directly in it that ends
++in @samp{".framework"}. The name of a framework is the name of this
++directory excluding the @samp{".framework"}. Headers associated with
++the framework are found in one of those two directories, with
++@samp{"Headers"} being searched first. A subframework is a framework
++directory that is in a framework's @samp{"Frameworks"} directory.
++Includes of subframework headers can only appear in a header of a
++framework that contains the subframework, or in a sibling subframework
++header. Two subframeworks are siblings if they occur in the same
++framework. A subframework should not have the same name as a
++framework, a warning will be issued if this is violated. Currently a
++subframework cannot have subframeworks, in the future, the mechanism
++may be extended to support this. The standard frameworks can be found
++in @samp{"/System/Library/Frameworks"} and
++@samp{"/Library/Frameworks"}. An example include looks like
++@code{#include <Framework/header.h>}, where @samp{Framework} denotes
++the name of the framework and header.h is found in the
++@samp{"PrivateHeaders"} or @samp{"Headers"} directory.
++
++@item -iframework@var{dir}
++@opindex iframework
++Like @option{-F} except the directory is a treated as a system
++directory. The main difference between this @option{-iframework} and
++@option{-F} is that with @option{-iframework} the compiler does not
++warn about constructs contained within header files found via
++@var{dir}. This option is valid only for the C family of languages.
++
++@item -gused
++@opindex gused
++Emit debugging information for symbols that are used. For STABS
++debugging format, this enables @option{-feliminate-unused-debug-symbols}.
++This is by default ON@.
++
++@item -gfull
++@opindex gfull
++Emit debugging information for all symbols and types.
++
++@item -mmacosx-version-min=@var{version}
++The earliest version of MacOS X that this executable will run on
++is @var{version}. Typical values of @var{version} include @code{10.1},
++@code{10.2}, and @code{10.3.9}.
++
++If the compiler was built to use the system's headers by default,
++then the default for this option is the system version on which the
++compiler is running, otherwise the default is to make choices which
++are compatible with as many systems and code bases as possible.
++
++@item -mkernel
++@opindex mkernel
++Enable kernel development mode. The @option{-mkernel} option sets
++@option{-static}, @option{-fno-common}, @option{-fno-cxa-atexit},
++@option{-fno-exceptions}, @option{-fno-non-call-exceptions},
++@option{-fapple-kext}, @option{-fno-weak} and @option{-fno-rtti} where
++applicable. This mode also sets @option{-mno-altivec},
++@option{-msoft-float}, @option{-fno-builtin} and
++@option{-mlong-branch} for PowerPC targets.
++
++@item -mone-byte-bool
++@opindex mone-byte-bool
++Override the defaults for @samp{bool} so that @samp{sizeof(bool)==1}.
++By default @samp{sizeof(bool)} is @samp{4} when compiling for
++Darwin/PowerPC and @samp{1} when compiling for Darwin/x86, so this
++option has no effect on x86.
++
++@strong{Warning:} The @option{-mone-byte-bool} switch causes GCC
++to generate code that is not binary compatible with code generated
++without that switch. Using this switch may require recompiling all
++other modules in a program, including system libraries. Use this
++switch to conform to a non-default data model.
++
++@item -mfix-and-continue
++@itemx -ffix-and-continue
++@itemx -findirect-data
++@opindex mfix-and-continue
++@opindex ffix-and-continue
++@opindex findirect-data
++Generate code suitable for fast turn around development. Needed to
++enable gdb to dynamically load @code{.o} files into already running
++programs. @option{-findirect-data} and @option{-ffix-and-continue}
++are provided for backwards compatibility.
++
++@item -all_load
++@opindex all_load
++Loads all members of static archive libraries.
++See man ld(1) for more information.
++
++@item -arch_errors_fatal
++@opindex arch_errors_fatal
++Cause the errors having to do with files that have the wrong architecture
++to be fatal.
++
++@item -bind_at_load
++@opindex bind_at_load
++Causes the output file to be marked such that the dynamic linker will
++bind all undefined references when the file is loaded or launched.
++
++@item -bundle
++@opindex bundle
++Produce a Mach-o bundle format file.
++See man ld(1) for more information.
++
++@item -bundle_loader @var{executable}
++@opindex bundle_loader
++This option specifies the @var{executable} that will be loading the build
++output file being linked. See man ld(1) for more information.
++
++@item -dynamiclib
++@opindex dynamiclib
++When passed this option, GCC will produce a dynamic library instead of
++an executable when linking, using the Darwin @file{libtool} command.
++
++@item -force_cpusubtype_ALL
++@opindex force_cpusubtype_ALL
++This causes GCC's output file to have the @var{ALL} subtype, instead of
++one controlled by the @option{-mcpu} or @option{-march} option.
++
++@item -allowable_client @var{client_name}
++@itemx -client_name
++@itemx -compatibility_version
++@itemx -current_version
++@itemx -dead_strip
++@itemx -dependency-file
++@itemx -dylib_file
++@itemx -dylinker_install_name
++@itemx -dynamic
++@itemx -exported_symbols_list
++@itemx -filelist
++@itemx -flat_namespace
++@itemx -force_flat_namespace
++@itemx -headerpad_max_install_names
++@itemx -image_base
++@itemx -init
++@itemx -install_name
++@itemx -keep_private_externs
++@itemx -multi_module
++@itemx -multiply_defined
++@itemx -multiply_defined_unused
++@itemx -noall_load
++@itemx -no_dead_strip_inits_and_terms
++@itemx -nofixprebinding
++@itemx -nomultidefs
++@itemx -noprebind
++@itemx -noseglinkedit
++@itemx -pagezero_size
++@itemx -prebind
++@itemx -prebind_all_twolevel_modules
++@itemx -private_bundle
++@itemx -read_only_relocs
++@itemx -sectalign
++@itemx -sectobjectsymbols
++@itemx -whyload
++@itemx -seg1addr
++@itemx -sectcreate
++@itemx -sectobjectsymbols
++@itemx -sectorder
++@itemx -segaddr
++@itemx -segs_read_only_addr
++@itemx -segs_read_write_addr
++@itemx -seg_addr_table
++@itemx -seg_addr_table_filename
++@itemx -seglinkedit
++@itemx -segprot
++@itemx -segs_read_only_addr
++@itemx -segs_read_write_addr
++@itemx -single_module
++@itemx -static
++@itemx -sub_library
++@itemx -sub_umbrella
++@itemx -twolevel_namespace
++@itemx -umbrella
++@itemx -undefined
++@itemx -unexported_symbols_list
++@itemx -weak_reference_mismatches
++@itemx -whatsloaded
++@opindex allowable_client
++@opindex client_name
++@opindex compatibility_version
++@opindex current_version
++@opindex dead_strip
++@opindex dependency-file
++@opindex dylib_file
++@opindex dylinker_install_name
++@opindex dynamic
++@opindex exported_symbols_list
++@opindex filelist
++@opindex flat_namespace
++@opindex force_flat_namespace
++@opindex headerpad_max_install_names
++@opindex image_base
++@opindex init
++@opindex install_name
++@opindex keep_private_externs
++@opindex multi_module
++@opindex multiply_defined
++@opindex multiply_defined_unused
++@opindex noall_load
++@opindex no_dead_strip_inits_and_terms
++@opindex nofixprebinding
++@opindex nomultidefs
++@opindex noprebind
++@opindex noseglinkedit
++@opindex pagezero_size
++@opindex prebind
++@opindex prebind_all_twolevel_modules
++@opindex private_bundle
++@opindex read_only_relocs
++@opindex sectalign
++@opindex sectobjectsymbols
++@opindex whyload
++@opindex seg1addr
++@opindex sectcreate
++@opindex sectobjectsymbols
++@opindex sectorder
++@opindex segaddr
++@opindex segs_read_only_addr
++@opindex segs_read_write_addr
++@opindex seg_addr_table
++@opindex seg_addr_table_filename
++@opindex seglinkedit
++@opindex segprot
++@opindex segs_read_only_addr
++@opindex segs_read_write_addr
++@opindex single_module
++@opindex static
++@opindex sub_library
++@opindex sub_umbrella
++@opindex twolevel_namespace
++@opindex umbrella
++@opindex undefined
++@opindex unexported_symbols_list
++@opindex weak_reference_mismatches
++@opindex whatsloaded
++These options are passed to the Darwin linker. The Darwin linker man page
++describes them in detail.
++@end table
++
++@node DEC Alpha Options
++@subsection DEC Alpha Options
++
++These @samp{-m} options are defined for the DEC Alpha implementations:
++
++@table @gcctabopt
++@item -mno-soft-float
++@itemx -msoft-float
++@opindex mno-soft-float
++@opindex msoft-float
++Use (do not use) the hardware floating-point instructions for
++floating-point operations. When @option{-msoft-float} is specified,
++functions in @file{libgcc.a} will be used to perform floating-point
++operations. Unless they are replaced by routines that emulate the
++floating-point operations, or compiled in such a way as to call such
++emulations routines, these routines will issue floating-point
++operations. If you are compiling for an Alpha without floating-point
++operations, you must ensure that the library is built so as not to call
++them.
++
++Note that Alpha implementations without floating-point operations are
++required to have floating-point registers.
++
++@item -mfp-reg
++@itemx -mno-fp-regs
++@opindex mfp-reg
++@opindex mno-fp-regs
++Generate code that uses (does not use) the floating-point register set.
++@option{-mno-fp-regs} implies @option{-msoft-float}. If the floating-point
++register set is not used, floating point operands are passed in integer
++registers as if they were integers and floating-point results are passed
++in @code{$0} instead of @code{$f0}. This is a non-standard calling sequence,
++so any function with a floating-point argument or return value called by code
++compiled with @option{-mno-fp-regs} must also be compiled with that
++option.
++
++A typical use of this option is building a kernel that does not use,
++and hence need not save and restore, any floating-point registers.
++
++@item -mieee
++@opindex mieee
++The Alpha architecture implements floating-point hardware optimized for
++maximum performance. It is mostly compliant with the IEEE floating
++point standard. However, for full compliance, software assistance is
++required. This option generates code fully IEEE compliant code
++@emph{except} that the @var{inexact-flag} is not maintained (see below).
++If this option is turned on, the preprocessor macro @code{_IEEE_FP} is
++defined during compilation. The resulting code is less efficient but is
++able to correctly support denormalized numbers and exceptional IEEE
++values such as not-a-number and plus/minus infinity. Other Alpha
++compilers call this option @option{-ieee_with_no_inexact}.
++
++@item -mieee-with-inexact
++@opindex mieee-with-inexact
++This is like @option{-mieee} except the generated code also maintains
++the IEEE @var{inexact-flag}. Turning on this option causes the
++generated code to implement fully-compliant IEEE math. In addition to
++@code{_IEEE_FP}, @code{_IEEE_FP_EXACT} is defined as a preprocessor
++macro. On some Alpha implementations the resulting code may execute
++significantly slower than the code generated by default. Since there is
++very little code that depends on the @var{inexact-flag}, you should
++normally not specify this option. Other Alpha compilers call this
++option @option{-ieee_with_inexact}.
++
++@item -mfp-trap-mode=@var{trap-mode}
++@opindex mfp-trap-mode
++This option controls what floating-point related traps are enabled.
++Other Alpha compilers call this option @option{-fptm @var{trap-mode}}.
++The trap mode can be set to one of four values:
++
++@table @samp
++@item n
++This is the default (normal) setting. The only traps that are enabled
++are the ones that cannot be disabled in software (e.g., division by zero
++trap).
++
++@item u
++In addition to the traps enabled by @samp{n}, underflow traps are enabled
++as well.
++
++@item su
++Like @samp{u}, but the instructions are marked to be safe for software
++completion (see Alpha architecture manual for details).
++
++@item sui
++Like @samp{su}, but inexact traps are enabled as well.
++@end table
++
++@item -mfp-rounding-mode=@var{rounding-mode}
++@opindex mfp-rounding-mode
++Selects the IEEE rounding mode. Other Alpha compilers call this option
++@option{-fprm @var{rounding-mode}}. The @var{rounding-mode} can be one
++of:
++
++@table @samp
++@item n
++Normal IEEE rounding mode. Floating point numbers are rounded towards
++the nearest machine number or towards the even machine number in case
++of a tie.
++
++@item m
++Round towards minus infinity.
++
++@item c
++Chopped rounding mode. Floating point numbers are rounded towards zero.
++
++@item d
++Dynamic rounding mode. A field in the floating point control register
++(@var{fpcr}, see Alpha architecture reference manual) controls the
++rounding mode in effect. The C library initializes this register for
++rounding towards plus infinity. Thus, unless your program modifies the
++@var{fpcr}, @samp{d} corresponds to round towards plus infinity.
++@end table
++
++@item -mtrap-precision=@var{trap-precision}
++@opindex mtrap-precision
++In the Alpha architecture, floating point traps are imprecise. This
++means without software assistance it is impossible to recover from a
++floating trap and program execution normally needs to be terminated.
++GCC can generate code that can assist operating system trap handlers
++in determining the exact location that caused a floating point trap.
++Depending on the requirements of an application, different levels of
++precisions can be selected:
++
++@table @samp
++@item p
++Program precision. This option is the default and means a trap handler
++can only identify which program caused a floating point exception.
++
++@item f
++Function precision. The trap handler can determine the function that
++caused a floating point exception.
++
++@item i
++Instruction precision. The trap handler can determine the exact
++instruction that caused a floating point exception.
++@end table
++
++Other Alpha compilers provide the equivalent options called
++@option{-scope_safe} and @option{-resumption_safe}.
++
++@item -mieee-conformant
++@opindex mieee-conformant
++This option marks the generated code as IEEE conformant. You must not
++use this option unless you also specify @option{-mtrap-precision=i} and either
++@option{-mfp-trap-mode=su} or @option{-mfp-trap-mode=sui}. Its only effect
++is to emit the line @samp{.eflag 48} in the function prologue of the
++generated assembly file. Under DEC Unix, this has the effect that
++IEEE-conformant math library routines will be linked in.
++
++@item -mbuild-constants
++@opindex mbuild-constants
++Normally GCC examines a 32- or 64-bit integer constant to
++see if it can construct it from smaller constants in two or three
++instructions. If it cannot, it will output the constant as a literal and
++generate code to load it from the data segment at runtime.
++
++Use this option to require GCC to construct @emph{all} integer constants
++using code, even if it takes more instructions (the maximum is six).
++
++You would typically use this option to build a shared library dynamic
++loader. Itself a shared library, it must relocate itself in memory
++before it can find the variables and constants in its own data segment.
++
++@item -malpha-as
++@itemx -mgas
++@opindex malpha-as
++@opindex mgas
++Select whether to generate code to be assembled by the vendor-supplied
++assembler (@option{-malpha-as}) or by the GNU assembler @option{-mgas}.
++
++@item -mbwx
++@itemx -mno-bwx
++@itemx -mcix
++@itemx -mno-cix
++@itemx -mfix
++@itemx -mno-fix
++@itemx -mmax
++@itemx -mno-max
++@opindex mbwx
++@opindex mno-bwx
++@opindex mcix
++@opindex mno-cix
++@opindex mfix
++@opindex mno-fix
++@opindex mmax
++@opindex mno-max
++Indicate whether GCC should generate code to use the optional BWX,
++CIX, FIX and MAX instruction sets. The default is to use the instruction
++sets supported by the CPU type specified via @option{-mcpu=} option or that
++of the CPU on which GCC was built if none was specified.
++
++@item -mfloat-vax
++@itemx -mfloat-ieee
++@opindex mfloat-vax
++@opindex mfloat-ieee
++Generate code that uses (does not use) VAX F and G floating point
++arithmetic instead of IEEE single and double precision.
++
++@item -mexplicit-relocs
++@itemx -mno-explicit-relocs
++@opindex mexplicit-relocs
++@opindex mno-explicit-relocs
++Older Alpha assemblers provided no way to generate symbol relocations
++except via assembler macros. Use of these macros does not allow
++optimal instruction scheduling. GNU binutils as of version 2.12
++supports a new syntax that allows the compiler to explicitly mark
++which relocations should apply to which instructions. This option
++is mostly useful for debugging, as GCC detects the capabilities of
++the assembler when it is built and sets the default accordingly.
++
++@item -msmall-data
++@itemx -mlarge-data
++@opindex msmall-data
++@opindex mlarge-data
++When @option{-mexplicit-relocs} is in effect, static data is
++accessed via @dfn{gp-relative} relocations. When @option{-msmall-data}
++is used, objects 8 bytes long or smaller are placed in a @dfn{small data area}
++(the @code{.sdata} and @code{.sbss} sections) and are accessed via
++16-bit relocations off of the @code{$gp} register. This limits the
++size of the small data area to 64KB, but allows the variables to be
++directly accessed via a single instruction.
++
++The default is @option{-mlarge-data}. With this option the data area
++is limited to just below 2GB@. Programs that require more than 2GB of
++data must use @code{malloc} or @code{mmap} to allocate the data in the
++heap instead of in the program's data segment.
++
++When generating code for shared libraries, @option{-fpic} implies
++@option{-msmall-data} and @option{-fPIC} implies @option{-mlarge-data}.
++
++@item -msmall-text
++@itemx -mlarge-text
++@opindex msmall-text
++@opindex mlarge-text
++When @option{-msmall-text} is used, the compiler assumes that the
++code of the entire program (or shared library) fits in 4MB, and is
++thus reachable with a branch instruction. When @option{-msmall-data}
++is used, the compiler can assume that all local symbols share the
++same @code{$gp} value, and thus reduce the number of instructions
++required for a function call from 4 to 1.
++
++The default is @option{-mlarge-text}.
++
++@item -mcpu=@var{cpu_type}
++@opindex mcpu
++Set the instruction set and instruction scheduling parameters for
++machine type @var{cpu_type}. You can specify either the @samp{EV}
++style name or the corresponding chip number. GCC supports scheduling
++parameters for the EV4, EV5 and EV6 family of processors and will
++choose the default values for the instruction set from the processor
++you specify. If you do not specify a processor type, GCC will default
++to the processor on which the compiler was built.
++
++Supported values for @var{cpu_type} are
++
++@table @samp
++@item ev4
++@itemx ev45
++@itemx 21064
++Schedules as an EV4 and has no instruction set extensions.
++
++@item ev5
++@itemx 21164
++Schedules as an EV5 and has no instruction set extensions.
++
++@item ev56
++@itemx 21164a
++Schedules as an EV5 and supports the BWX extension.
++
++@item pca56
++@itemx 21164pc
++@itemx 21164PC
++Schedules as an EV5 and supports the BWX and MAX extensions.
++
++@item ev6
++@itemx 21264
++Schedules as an EV6 and supports the BWX, FIX, and MAX extensions.
++
++@item ev67
++@itemx 21264a
++Schedules as an EV6 and supports the BWX, CIX, FIX, and MAX extensions.
++@end table
++
++Native Linux/GNU toolchains also support the value @samp{native},
++which selects the best architecture option for the host processor.
++@option{-mcpu=native} has no effect if GCC does not recognize
++the processor.
++
++@item -mtune=@var{cpu_type}
++@opindex mtune
++Set only the instruction scheduling parameters for machine type
++@var{cpu_type}. The instruction set is not changed.
++
++Native Linux/GNU toolchains also support the value @samp{native},
++which selects the best architecture option for the host processor.
++@option{-mtune=native} has no effect if GCC does not recognize
++the processor.
++
++@item -mmemory-latency=@var{time}
++@opindex mmemory-latency
++Sets the latency the scheduler should assume for typical memory
++references as seen by the application. This number is highly
++dependent on the memory access patterns used by the application
++and the size of the external cache on the machine.
++
++Valid options for @var{time} are
++
++@table @samp
++@item @var{number}
++A decimal number representing clock cycles.
++
++@item L1
++@itemx L2
++@itemx L3
++@itemx main
++The compiler contains estimates of the number of clock cycles for
++``typical'' EV4 & EV5 hardware for the Level 1, 2 & 3 caches
++(also called Dcache, Scache, and Bcache), as well as to main memory.
++Note that L3 is only valid for EV5.
++
++@end table
++@end table
++
++@node DEC Alpha/VMS Options
++@subsection DEC Alpha/VMS Options
++
++These @samp{-m} options are defined for the DEC Alpha/VMS implementations:
++
++@table @gcctabopt
++@item -mvms-return-codes
++@opindex mvms-return-codes
++Return VMS condition codes from main. The default is to return POSIX
++style condition (e.g.@: error) codes.
++@end table
++
++@node FR30 Options
++@subsection FR30 Options
++@cindex FR30 Options
++
++These options are defined specifically for the FR30 port.
++
++@table @gcctabopt
++
++@item -msmall-model
++@opindex msmall-model
++Use the small address space model. This can produce smaller code, but
++it does assume that all symbolic values and addresses will fit into a
++20-bit range.
++
++@item -mno-lsim
++@opindex mno-lsim
++Assume that run-time support has been provided and so there is no need
++to include the simulator library (@file{libsim.a}) on the linker
++command line.
++
++@end table
++
++@node FRV Options
++@subsection FRV Options
++@cindex FRV Options
++
++@table @gcctabopt
++@item -mgpr-32
++@opindex mgpr-32
++
++Only use the first 32 general purpose registers.
++
++@item -mgpr-64
++@opindex mgpr-64
++
++Use all 64 general purpose registers.
++
++@item -mfpr-32
++@opindex mfpr-32
++
++Use only the first 32 floating point registers.
++
++@item -mfpr-64
++@opindex mfpr-64
++
++Use all 64 floating point registers
++
++@item -mhard-float
++@opindex mhard-float
++
++Use hardware instructions for floating point operations.
++
++@item -msoft-float
++@opindex msoft-float
++
++Use library routines for floating point operations.
++
++@item -malloc-cc
++@opindex malloc-cc
++
++Dynamically allocate condition code registers.
++
++@item -mfixed-cc
++@opindex mfixed-cc
++
++Do not try to dynamically allocate condition code registers, only
++use @code{icc0} and @code{fcc0}.
++
++@item -mdword
++@opindex mdword
++
++Change ABI to use double word insns.
++
++@item -mno-dword
++@opindex mno-dword
++
++Do not use double word instructions.
++
++@item -mdouble
++@opindex mdouble
++
++Use floating point double instructions.
++
++@item -mno-double
++@opindex mno-double
++
++Do not use floating point double instructions.
++
++@item -mmedia
++@opindex mmedia
++
++Use media instructions.
++
++@item -mno-media
++@opindex mno-media
++
++Do not use media instructions.
++
++@item -mmuladd
++@opindex mmuladd
++
++Use multiply and add/subtract instructions.
++
++@item -mno-muladd
++@opindex mno-muladd
++
++Do not use multiply and add/subtract instructions.
++
++@item -mfdpic
++@opindex mfdpic
++
++Select the FDPIC ABI, that uses function descriptors to represent
++pointers to functions. Without any PIC/PIE-related options, it
++implies @option{-fPIE}. With @option{-fpic} or @option{-fpie}, it
++assumes GOT entries and small data are within a 12-bit range from the
++GOT base address; with @option{-fPIC} or @option{-fPIE}, GOT offsets
++are computed with 32 bits.
++With a @samp{bfin-elf} target, this option implies @option{-msim}.
++
++@item -minline-plt
++@opindex minline-plt
++
++Enable inlining of PLT entries in function calls to functions that are
++not known to bind locally. It has no effect without @option{-mfdpic}.
++It's enabled by default if optimizing for speed and compiling for
++shared libraries (i.e., @option{-fPIC} or @option{-fpic}), or when an
++optimization option such as @option{-O3} or above is present in the
++command line.
++
++@item -mTLS
++@opindex TLS
++
++Assume a large TLS segment when generating thread-local code.
++
++@item -mtls
++@opindex tls
++
++Do not assume a large TLS segment when generating thread-local code.
++
++@item -mgprel-ro
++@opindex mgprel-ro
++
++Enable the use of @code{GPREL} relocations in the FDPIC ABI for data
++that is known to be in read-only sections. It's enabled by default,
++except for @option{-fpic} or @option{-fpie}: even though it may help
++make the global offset table smaller, it trades 1 instruction for 4.
++With @option{-fPIC} or @option{-fPIE}, it trades 3 instructions for 4,
++one of which may be shared by multiple symbols, and it avoids the need
++for a GOT entry for the referenced symbol, so it's more likely to be a
++win. If it is not, @option{-mno-gprel-ro} can be used to disable it.
++
++@item -multilib-library-pic
++@opindex multilib-library-pic
++
++Link with the (library, not FD) pic libraries. It's implied by
++@option{-mlibrary-pic}, as well as by @option{-fPIC} and
++@option{-fpic} without @option{-mfdpic}. You should never have to use
++it explicitly.
++
++@item -mlinked-fp
++@opindex mlinked-fp
++
++Follow the EABI requirement of always creating a frame pointer whenever
++a stack frame is allocated. This option is enabled by default and can
++be disabled with @option{-mno-linked-fp}.
++
++@item -mlong-calls
++@opindex mlong-calls
++
++Use indirect addressing to call functions outside the current
++compilation unit. This allows the functions to be placed anywhere
++within the 32-bit address space.
++
++@item -malign-labels
++@opindex malign-labels
++
++Try to align labels to an 8-byte boundary by inserting nops into the
++previous packet. This option only has an effect when VLIW packing
++is enabled. It doesn't create new packets; it merely adds nops to
++existing ones.
++
++@item -mlibrary-pic
++@opindex mlibrary-pic
++
++Generate position-independent EABI code.
++
++@item -macc-4
++@opindex macc-4
++
++Use only the first four media accumulator registers.
++
++@item -macc-8
++@opindex macc-8
++
++Use all eight media accumulator registers.
++
++@item -mpack
++@opindex mpack
++
++Pack VLIW instructions.
++
++@item -mno-pack
++@opindex mno-pack
++
++Do not pack VLIW instructions.
++
++@item -mno-eflags
++@opindex mno-eflags
++
++Do not mark ABI switches in e_flags.
++
++@item -mcond-move
++@opindex mcond-move
++
++Enable the use of conditional-move instructions (default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-cond-move
++@opindex mno-cond-move
++
++Disable the use of conditional-move instructions.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mscc
++@opindex mscc
++
++Enable the use of conditional set instructions (default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-scc
++@opindex mno-scc
++
++Disable the use of conditional set instructions.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mcond-exec
++@opindex mcond-exec
++
++Enable the use of conditional execution (default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-cond-exec
++@opindex mno-cond-exec
++
++Disable the use of conditional execution.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mvliw-branch
++@opindex mvliw-branch
++
++Run a pass to pack branches into VLIW instructions (default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-vliw-branch
++@opindex mno-vliw-branch
++
++Do not run a pass to pack branches into VLIW instructions.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mmulti-cond-exec
++@opindex mmulti-cond-exec
++
++Enable optimization of @code{&&} and @code{||} in conditional execution
++(default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-multi-cond-exec
++@opindex mno-multi-cond-exec
++
++Disable optimization of @code{&&} and @code{||} in conditional execution.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mnested-cond-exec
++@opindex mnested-cond-exec
++
++Enable nested conditional execution optimizations (default).
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -mno-nested-cond-exec
++@opindex mno-nested-cond-exec
++
++Disable nested conditional execution optimizations.
++
++This switch is mainly for debugging the compiler and will likely be removed
++in a future version.
++
++@item -moptimize-membar
++@opindex moptimize-membar
++
++This switch removes redundant @code{membar} instructions from the
++compiler generated code. It is enabled by default.
++
++@item -mno-optimize-membar
++@opindex mno-optimize-membar
++
++This switch disables the automatic removal of redundant @code{membar}
++instructions from the generated code.
++
++@item -mtomcat-stats
++@opindex mtomcat-stats
++
++Cause gas to print out tomcat statistics.
++
++@item -mcpu=@var{cpu}
++@opindex mcpu
++
++Select the processor type for which to generate code. Possible values are
++@samp{frv}, @samp{fr550}, @samp{tomcat}, @samp{fr500}, @samp{fr450},
++@samp{fr405}, @samp{fr400}, @samp{fr300} and @samp{simple}.
++
++@end table
++
++@node GNU/Linux Options
++@subsection GNU/Linux Options
++
++These @samp{-m} options are defined for GNU/Linux targets:
++
++@table @gcctabopt
++@item -mglibc
++@opindex mglibc
++Use the GNU C library instead of uClibc. This is the default except
++on @samp{*-*-linux-*uclibc*} targets.
++
++@item -muclibc
++@opindex muclibc
++Use uClibc instead of the GNU C library. This is the default on
++@samp{*-*-linux-*uclibc*} targets.
++@end table
++
++@node H8/300 Options
++@subsection H8/300 Options
++
++These @samp{-m} options are defined for the H8/300 implementations:
++
++@table @gcctabopt
++@item -mrelax
++@opindex mrelax
++Shorten some address references at link time, when possible; uses the
++linker option @option{-relax}. @xref{H8/300,, @code{ld} and the H8/300,
++ld, Using ld}, for a fuller description.
++
++@item -mh
++@opindex mh
++Generate code for the H8/300H@.
++
++@item -ms
++@opindex ms
++Generate code for the H8S@.
++
++@item -mn
++@opindex mn
++Generate code for the H8S and H8/300H in the normal mode. This switch
++must be used either with @option{-mh} or @option{-ms}.
++
++@item -ms2600
++@opindex ms2600
++Generate code for the H8S/2600. This switch must be used with @option{-ms}.
++
++@item -mint32
++@opindex mint32
++Make @code{int} data 32 bits by default.
++
++@item -malign-300
++@opindex malign-300
++On the H8/300H and H8S, use the same alignment rules as for the H8/300.
++The default for the H8/300H and H8S is to align longs and floats on 4
++byte boundaries.
++@option{-malign-300} causes them to be aligned on 2 byte boundaries.
++This option has no effect on the H8/300.
++@end table
++
++@node HPPA Options
++@subsection HPPA Options
++@cindex HPPA Options
++
++These @samp{-m} options are defined for the HPPA family of computers:
++
++@table @gcctabopt
++@item -march=@var{architecture-type}
++@opindex march
++Generate code for the specified architecture. The choices for
++@var{architecture-type} are @samp{1.0} for PA 1.0, @samp{1.1} for PA
++1.1, and @samp{2.0} for PA 2.0 processors. Refer to
++@file{/usr/lib/sched.models} on an HP-UX system to determine the proper
++architecture option for your machine. Code compiled for lower numbered
++architectures will run on higher numbered architectures, but not the
++other way around.
++
++@item -mpa-risc-1-0
++@itemx -mpa-risc-1-1
++@itemx -mpa-risc-2-0
++@opindex mpa-risc-1-0
++@opindex mpa-risc-1-1
++@opindex mpa-risc-2-0
++Synonyms for @option{-march=1.0}, @option{-march=1.1}, and @option{-march=2.0} respectively.
++
++@item -mbig-switch
++@opindex mbig-switch
++Generate code suitable for big switch tables. Use this option only if
++the assembler/linker complain about out of range branches within a switch
++table.
++
++@item -mjump-in-delay
++@opindex mjump-in-delay
++Fill delay slots of function calls with unconditional jump instructions
++by modifying the return pointer for the function call to be the target
++of the conditional jump.
++
++@item -mdisable-fpregs
++@opindex mdisable-fpregs
++Prevent floating point registers from being used in any manner. This is
++necessary for compiling kernels which perform lazy context switching of
++floating point registers. If you use this option and attempt to perform
++floating point operations, the compiler will abort.
++
++@item -mdisable-indexing
++@opindex mdisable-indexing
++Prevent the compiler from using indexing address modes. This avoids some
++rather obscure problems when compiling MIG generated code under MACH@.
++
++@item -mno-space-regs
++@opindex mno-space-regs
++Generate code that assumes the target has no space registers. This allows
++GCC to generate faster indirect calls and use unscaled index address modes.
++
++Such code is suitable for level 0 PA systems and kernels.
++
++@item -mfast-indirect-calls
++@opindex mfast-indirect-calls
++Generate code that assumes calls never cross space boundaries. This
++allows GCC to emit code which performs faster indirect calls.
++
++This option will not work in the presence of shared libraries or nested
++functions.
++
++@item -mfixed-range=@var{register-range}
++@opindex mfixed-range
++Generate code treating the given register range as fixed registers.
++A fixed register is one that the register allocator can not use. This is
++useful when compiling kernel code. A register range is specified as
++two registers separated by a dash. Multiple register ranges can be
++specified separated by a comma.
++
++@item -mlong-load-store
++@opindex mlong-load-store
++Generate 3-instruction load and store sequences as sometimes required by
++the HP-UX 10 linker. This is equivalent to the @samp{+k} option to
++the HP compilers.
++
++@item -mportable-runtime
++@opindex mportable-runtime
++Use the portable calling conventions proposed by HP for ELF systems.
++
++@item -mgas
++@opindex mgas
++Enable the use of assembler directives only GAS understands.
++
++@item -mschedule=@var{cpu-type}
++@opindex mschedule
++Schedule code according to the constraints for the machine type
++@var{cpu-type}. The choices for @var{cpu-type} are @samp{700}
++@samp{7100}, @samp{7100LC}, @samp{7200}, @samp{7300} and @samp{8000}. Refer
++to @file{/usr/lib/sched.models} on an HP-UX system to determine the
++proper scheduling option for your machine. The default scheduling is
++@samp{8000}.
++
++@item -mlinker-opt
++@opindex mlinker-opt
++Enable the optimization pass in the HP-UX linker. Note this makes symbolic
++debugging impossible. It also triggers a bug in the HP-UX 8 and HP-UX 9
++linkers in which they give bogus error messages when linking some programs.
++
++@item -msoft-float
++@opindex msoft-float
++Generate output containing library calls for floating point.
++@strong{Warning:} the requisite libraries are not available for all HPPA
++targets. Normally the facilities of the machine's usual C compiler are
++used, but this cannot be done directly in cross-compilation. You must make
++your own arrangements to provide suitable library functions for
++cross-compilation.
++
++@option{-msoft-float} changes the calling convention in the output file;
++therefore, it is only useful if you compile @emph{all} of a program with
++this option. In particular, you need to compile @file{libgcc.a}, the
++library that comes with GCC, with @option{-msoft-float} in order for
++this to work.
++
++@item -msio
++@opindex msio
++Generate the predefine, @code{_SIO}, for server IO@. The default is
++@option{-mwsio}. This generates the predefines, @code{__hp9000s700},
++@code{__hp9000s700__} and @code{_WSIO}, for workstation IO@. These
++options are available under HP-UX and HI-UX@.
++
++@item -mgnu-ld
++@opindex gnu-ld
++Use GNU ld specific options. This passes @option{-shared} to ld when
++building a shared library. It is the default when GCC is configured,
++explicitly or implicitly, with the GNU linker. This option does not
++have any affect on which ld is called, it only changes what parameters
++are passed to that ld. The ld that is called is determined by the
++@option{--with-ld} configure option, GCC's program search path, and
++finally by the user's @env{PATH}. The linker used by GCC can be printed
++using @samp{which `gcc -print-prog-name=ld`}. This option is only available
++on the 64 bit HP-UX GCC, i.e.@: configured with @samp{hppa*64*-*-hpux*}.
++
++@item -mhp-ld
++@opindex hp-ld
++Use HP ld specific options. This passes @option{-b} to ld when building
++a shared library and passes @option{+Accept TypeMismatch} to ld on all
++links. It is the default when GCC is configured, explicitly or
++implicitly, with the HP linker. This option does not have any affect on
++which ld is called, it only changes what parameters are passed to that
++ld. The ld that is called is determined by the @option{--with-ld}
++configure option, GCC's program search path, and finally by the user's
++@env{PATH}. The linker used by GCC can be printed using @samp{which
++`gcc -print-prog-name=ld`}. This option is only available on the 64 bit
++HP-UX GCC, i.e.@: configured with @samp{hppa*64*-*-hpux*}.
++
++@item -mlong-calls
++@opindex mno-long-calls
++Generate code that uses long call sequences. This ensures that a call
++is always able to reach linker generated stubs. The default is to generate
++long calls only when the distance from the call site to the beginning
++of the function or translation unit, as the case may be, exceeds a
++predefined limit set by the branch type being used. The limits for
++normal calls are 7,600,000 and 240,000 bytes, respectively for the
++PA 2.0 and PA 1.X architectures. Sibcalls are always limited at
++240,000 bytes.
++
++Distances are measured from the beginning of functions when using the
++@option{-ffunction-sections} option, or when using the @option{-mgas}
++and @option{-mno-portable-runtime} options together under HP-UX with
++the SOM linker.
++
++It is normally not desirable to use this option as it will degrade
++performance. However, it may be useful in large applications,
++particularly when partial linking is used to build the application.
++
++The types of long calls used depends on the capabilities of the
++assembler and linker, and the type of code being generated. The
++impact on systems that support long absolute calls, and long pic
++symbol-difference or pc-relative calls should be relatively small.
++However, an indirect call is used on 32-bit ELF systems in pic code
++and it is quite long.
++
++@item -munix=@var{unix-std}
++@opindex march
++Generate compiler predefines and select a startfile for the specified
++UNIX standard. The choices for @var{unix-std} are @samp{93}, @samp{95}
++and @samp{98}. @samp{93} is supported on all HP-UX versions. @samp{95}
++is available on HP-UX 10.10 and later. @samp{98} is available on HP-UX
++11.11 and later. The default values are @samp{93} for HP-UX 10.00,
++@samp{95} for HP-UX 10.10 though to 11.00, and @samp{98} for HP-UX 11.11
++and later.
++
++@option{-munix=93} provides the same predefines as GCC 3.3 and 3.4.
++@option{-munix=95} provides additional predefines for @code{XOPEN_UNIX}
++and @code{_XOPEN_SOURCE_EXTENDED}, and the startfile @file{unix95.o}.
++@option{-munix=98} provides additional predefines for @code{_XOPEN_UNIX},
++@code{_XOPEN_SOURCE_EXTENDED}, @code{_INCLUDE__STDC_A1_SOURCE} and
++@code{_INCLUDE_XOPEN_SOURCE_500}, and the startfile @file{unix98.o}.
++
++It is @emph{important} to note that this option changes the interfaces
++for various library routines. It also affects the operational behavior
++of the C library. Thus, @emph{extreme} care is needed in using this
++option.
++
++Library code that is intended to operate with more than one UNIX
++standard must test, set and restore the variable @var{__xpg4_extended_mask}
++as appropriate. Most GNU software doesn't provide this capability.
++
++@item -nolibdld
++@opindex nolibdld
++Suppress the generation of link options to search libdld.sl when the
++@option{-static} option is specified on HP-UX 10 and later.
++
++@item -static
++@opindex static
++The HP-UX implementation of setlocale in libc has a dependency on
++libdld.sl. There isn't an archive version of libdld.sl. Thus,
++when the @option{-static} option is specified, special link options
++are needed to resolve this dependency.
++
++On HP-UX 10 and later, the GCC driver adds the necessary options to
++link with libdld.sl when the @option{-static} option is specified.
++This causes the resulting binary to be dynamic. On the 64-bit port,
++the linkers generate dynamic binaries by default in any case. The
++@option{-nolibdld} option can be used to prevent the GCC driver from
++adding these link options.
++
++@item -threads
++@opindex threads
++Add support for multithreading with the @dfn{dce thread} library
++under HP-UX@. This option sets flags for both the preprocessor and
++linker.
++@end table
++
++@node i386 and x86-64 Options
++@subsection Intel 386 and AMD x86-64 Options
++@cindex i386 Options
++@cindex x86-64 Options
++@cindex Intel 386 Options
++@cindex AMD x86-64 Options
++
++These @samp{-m} options are defined for the i386 and x86-64 family of
++computers:
++
++@table @gcctabopt
++@item -mtune=@var{cpu-type}
++@opindex mtune
++Tune to @var{cpu-type} everything applicable about the generated code, except
++for the ABI and the set of available instructions. The choices for
++@var{cpu-type} are:
++@table @emph
++@item generic
++Produce code optimized for the most common IA32/AMD64/EM64T processors.
++If you know the CPU on which your code will run, then you should use
++the corresponding @option{-mtune} option instead of
++@option{-mtune=generic}. But, if you do not know exactly what CPU users
++of your application will have, then you should use this option.
++
++As new processors are deployed in the marketplace, the behavior of this
++option will change. Therefore, if you upgrade to a newer version of
++GCC, the code generated option will change to reflect the processors
++that were most common when that version of GCC was released.
++
++There is no @option{-march=generic} option because @option{-march}
++indicates the instruction set the compiler can use, and there is no
++generic instruction set applicable to all processors. In contrast,
++@option{-mtune} indicates the processor (or, in this case, collection of
++processors) for which the code is optimized.
++@item native
++This selects the CPU to tune for at compilation time by determining
++the processor type of the compiling machine. Using @option{-mtune=native}
++will produce code optimized for the local machine under the constraints
++of the selected instruction set. Using @option{-march=native} will
++enable all instruction subsets supported by the local machine (hence
++the result might not run on different machines).
++@item i386
++Original Intel's i386 CPU@.
++@item i486
++Intel's i486 CPU@. (No scheduling is implemented for this chip.)
++@item i586, pentium
++Intel Pentium CPU with no MMX support.
++@item pentium-mmx
++Intel PentiumMMX CPU based on Pentium core with MMX instruction set support.
++@item pentiumpro
++Intel PentiumPro CPU@.
++@item i686
++Same as @code{generic}, but when used as @code{march} option, PentiumPro
++instruction set will be used, so the code will run on all i686 family chips.
++@item pentium2
++Intel Pentium2 CPU based on PentiumPro core with MMX instruction set support.
++@item pentium3, pentium3m
++Intel Pentium3 CPU based on PentiumPro core with MMX and SSE instruction set
++support.
++@item pentium-m
++Low power version of Intel Pentium3 CPU with MMX, SSE and SSE2 instruction set
++support. Used by Centrino notebooks.
++@item pentium4, pentium4m
++Intel Pentium4 CPU with MMX, SSE and SSE2 instruction set support.
++@item prescott
++Improved version of Intel Pentium4 CPU with MMX, SSE, SSE2 and SSE3 instruction
++set support.
++@item nocona
++Improved version of Intel Pentium4 CPU with 64-bit extensions, MMX, SSE,
++SSE2 and SSE3 instruction set support.
++@item core2
++Intel Core2 CPU with 64-bit extensions, MMX, SSE, SSE2, SSE3 and SSSE3
++instruction set support.
++@item k6
++AMD K6 CPU with MMX instruction set support.
++@item k6-2, k6-3
++Improved versions of AMD K6 CPU with MMX and 3dNOW!@: instruction set support.
++@item athlon, athlon-tbird
++AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW!@: and SSE prefetch instructions
++support.
++@item athlon-4, athlon-xp, athlon-mp
++Improved AMD Athlon CPU with MMX, 3dNOW!, enhanced 3dNOW!@: and full SSE
++instruction set support.
++@item k8, opteron, athlon64, athlon-fx
++AMD K8 core based CPUs with x86-64 instruction set support. (This supersets
++MMX, SSE, SSE2, 3dNOW!, enhanced 3dNOW!@: and 64-bit instruction set extensions.)
++@item k8-sse3, opteron-sse3, athlon64-sse3
++Improved versions of k8, opteron and athlon64 with SSE3 instruction set support.
++@item amdfam10, barcelona
++AMD Family 10h core based CPUs with x86-64 instruction set support. (This
++supersets MMX, SSE, SSE2, SSE3, SSE4A, 3dNOW!, enhanced 3dNOW!, ABM and 64-bit
++instruction set extensions.)
++@item winchip-c6
++IDT Winchip C6 CPU, dealt in same way as i486 with additional MMX instruction
++set support.
++@item winchip2
++IDT Winchip2 CPU, dealt in same way as i486 with additional MMX and 3dNOW!@:
++instruction set support.
++@item c3
++Via C3 CPU with MMX and 3dNOW!@: instruction set support. (No scheduling is
++implemented for this chip.)
++@item c3-2
++Via C3-2 CPU with MMX and SSE instruction set support. (No scheduling is
++implemented for this chip.)
++@item geode
++Embedded AMD CPU with MMX and 3dNOW! instruction set support.
++@end table
++
++While picking a specific @var{cpu-type} will schedule things appropriately
++for that particular chip, the compiler will not generate any code that
++does not run on the i386 without the @option{-march=@var{cpu-type}} option
++being used.
++
++@item -march=@var{cpu-type}
++@opindex march
++Generate instructions for the machine type @var{cpu-type}. The choices
++for @var{cpu-type} are the same as for @option{-mtune}. Moreover,
++specifying @option{-march=@var{cpu-type}} implies @option{-mtune=@var{cpu-type}}.
++
++@item -mcpu=@var{cpu-type}
++@opindex mcpu
++A deprecated synonym for @option{-mtune}.
++
++@item -mfpmath=@var{unit}
++@opindex march
++Generate floating point arithmetics for selected unit @var{unit}. The choices
++for @var{unit} are:
++
++@table @samp
++@item 387
++Use the standard 387 floating point coprocessor present majority of chips and
++emulated otherwise. Code compiled with this option will run almost everywhere.
++The temporary results are computed in 80bit precision instead of precision
++specified by the type resulting in slightly different results compared to most
++of other chips. See @option{-ffloat-store} for more detailed description.
++
++This is the default choice for i386 compiler.
++
++@item sse
++Use scalar floating point instructions present in the SSE instruction set.
++This instruction set is supported by Pentium3 and newer chips, in the AMD line
++by Athlon-4, Athlon-xp and Athlon-mp chips. The earlier version of SSE
++instruction set supports only single precision arithmetics, thus the double and
++extended precision arithmetics is still done using 387. Later version, present
++only in Pentium4 and the future AMD x86-64 chips supports double precision
++arithmetics too.
++
++For the i386 compiler, you need to use @option{-march=@var{cpu-type}}, @option{-msse}
++or @option{-msse2} switches to enable SSE extensions and make this option
++effective. For the x86-64 compiler, these extensions are enabled by default.
++
++The resulting code should be considerably faster in the majority of cases and avoid
++the numerical instability problems of 387 code, but may break some existing
++code that expects temporaries to be 80bit.
++
++This is the default choice for the x86-64 compiler.
++
++@item sse,387
++@itemx sse+387
++@itemx both
++Attempt to utilize both instruction sets at once. This effectively double the
++amount of available registers and on chips with separate execution units for
++387 and SSE the execution resources too. Use this option with care, as it is
++still experimental, because the GCC register allocator does not model separate
++functional units well resulting in instable performance.
++@end table
++
++@item -masm=@var{dialect}
++@opindex masm=@var{dialect}
++Output asm instructions using selected @var{dialect}. Supported
++choices are @samp{intel} or @samp{att} (the default one). Darwin does
++not support @samp{intel}.
++
++@item -mieee-fp
++@itemx -mno-ieee-fp
++@opindex mieee-fp
++@opindex mno-ieee-fp
++Control whether or not the compiler uses IEEE floating point
++comparisons. These handle correctly the case where the result of a
++comparison is unordered.
++
++@item -msoft-float
++@opindex msoft-float
++Generate output containing library calls for floating point.
++@strong{Warning:} the requisite libraries are not part of GCC@.
++Normally the facilities of the machine's usual C compiler are used, but
++this can't be done directly in cross-compilation. You must make your
++own arrangements to provide suitable library functions for
++cross-compilation.
++
++On machines where a function returns floating point results in the 80387
++register stack, some floating point opcodes may be emitted even if
++@option{-msoft-float} is used.
++
++@item -mno-fp-ret-in-387
++@opindex mno-fp-ret-in-387
++Do not use the FPU registers for return values of functions.
++
++The usual calling convention has functions return values of types
++@code{float} and @code{double} in an FPU register, even if there
++is no FPU@. The idea is that the operating system should emulate
++an FPU@.
++
++The option @option{-mno-fp-ret-in-387} causes such values to be returned
++in ordinary CPU registers instead.
++
++@item -mno-fancy-math-387
++@opindex mno-fancy-math-387
++Some 387 emulators do not support the @code{sin}, @code{cos} and
++@code{sqrt} instructions for the 387. Specify this option to avoid
++generating those instructions. This option is the default on FreeBSD,
++OpenBSD and NetBSD@. This option is overridden when @option{-march}
++indicates that the target cpu will always have an FPU and so the
++instruction will not need emulation. As of revision 2.6.1, these
++instructions are not generated unless you also use the
++@option{-funsafe-math-optimizations} switch.
++
++@item -malign-double
++@itemx -mno-align-double
++@opindex malign-double
++@opindex mno-align-double
++Control whether GCC aligns @code{double}, @code{long double}, and
++@code{long long} variables on a two word boundary or a one word
++boundary. Aligning @code{double} variables on a two word boundary will
++produce code that runs somewhat faster on a @samp{Pentium} at the
++expense of more memory.
++
++On x86-64, @option{-malign-double} is enabled by default.
++
++@strong{Warning:} if you use the @option{-malign-double} switch,
++structures containing the above types will be aligned differently than
++the published application binary interface specifications for the 386
++and will not be binary compatible with structures in code compiled
++without that switch.
++
++@item -m96bit-long-double
++@itemx -m128bit-long-double
++@opindex m96bit-long-double
++@opindex m128bit-long-double
++These switches control the size of @code{long double} type. The i386
++application binary interface specifies the size to be 96 bits,
++so @option{-m96bit-long-double} is the default in 32 bit mode.
++
++Modern architectures (Pentium and newer) would prefer @code{long double}
++to be aligned to an 8 or 16 byte boundary. In arrays or structures
++conforming to the ABI, this would not be possible. So specifying a
++@option{-m128bit-long-double} will align @code{long double}
++to a 16 byte boundary by padding the @code{long double} with an additional
++32 bit zero.
++
++In the x86-64 compiler, @option{-m128bit-long-double} is the default choice as
++its ABI specifies that @code{long double} is to be aligned on 16 byte boundary.
++
++Notice that neither of these options enable any extra precision over the x87
++standard of 80 bits for a @code{long double}.
++
++@strong{Warning:} if you override the default value for your target ABI, the
++structures and arrays containing @code{long double} variables will change
++their size as well as function calling convention for function taking
++@code{long double} will be modified. Hence they will not be binary
++compatible with arrays or structures in code compiled without that switch.
++
++@item -mlarge-data-threshold=@var{number}
++@opindex mlarge-data-threshold=@var{number}
++When @option{-mcmodel=medium} is specified, the data greater than
++@var{threshold} are placed in large data section. This value must be the
++same across all object linked into the binary and defaults to 65535.
++
++@item -mrtd
++@opindex mrtd
++Use a different function-calling convention, in which functions that
++take a fixed number of arguments return with the @code{ret} @var{num}
++instruction, which pops their arguments while returning. This saves one
++instruction in the caller since there is no need to pop the arguments
++there.
++
++You can specify that an individual function is called with this calling
++sequence with the function attribute @samp{stdcall}. You can also
++override the @option{-mrtd} option by using the function attribute
++@samp{cdecl}. @xref{Function Attributes}.
++
++@strong{Warning:} this calling convention is incompatible with the one
++normally used on Unix, so you cannot use it if you need to call
++libraries compiled with the Unix compiler.
++
++Also, you must provide function prototypes for all functions that
++take variable numbers of arguments (including @code{printf});
++otherwise incorrect code will be generated for calls to those
++functions.
++
++In addition, seriously incorrect code will result if you call a
++function with too many arguments. (Normally, extra arguments are
++harmlessly ignored.)
++
++@item -mregparm=@var{num}
++@opindex mregparm
++Control how many registers are used to pass integer arguments. By
++default, no registers are used to pass arguments, and at most 3
++registers can be used. You can control this behavior for a specific
++function by using the function attribute @samp{regparm}.
++@xref{Function Attributes}.
++
++@strong{Warning:} if you use this switch, and
++@var{num} is nonzero, then you must build all modules with the same
++value, including any libraries. This includes the system libraries and
++startup modules.
++
++@item -msseregparm
++@opindex msseregparm
++Use SSE register passing conventions for float and double arguments
++and return values. You can control this behavior for a specific
++function by using the function attribute @samp{sseregparm}.
++@xref{Function Attributes}.
++
++@strong{Warning:} if you use this switch then you must build all
++modules with the same value, including any libraries. This includes
++the system libraries and startup modules.
++
++@item -mpc32
++@itemx -mpc64
++@itemx -mpc80
++@opindex mpc32
++@opindex mpc64
++@opindex mpc80
++
++Set 80387 floating-point precision to 32, 64 or 80 bits. When @option{-mpc32}
++is specified, the significands of results of floating-point operations are
++rounded to 24 bits (single precision); @option{-mpc64} rounds the
++significands of results of floating-point operations to 53 bits (double
++precision) and @option{-mpc80} rounds the significands of results of
++floating-point operations to 64 bits (extended double precision), which is
++the default. When this option is used, floating-point operations in higher
++precisions are not available to the programmer without setting the FPU
++control word explicitly.
++
++Setting the rounding of floating-point operations to less than the default
++80 bits can speed some programs by 2% or more. Note that some mathematical
++libraries assume that extended precision (80 bit) floating-point operations
++are enabled by default; routines in such libraries could suffer significant
++loss of accuracy, typically through so-called "catastrophic cancellation",
++when this option is used to set the precision to less than extended precision.
++
++@item -mstackrealign
++@opindex mstackrealign
++Realign the stack at entry. On the Intel x86, the @option{-mstackrealign}
++option will generate an alternate prologue and epilogue that realigns the
++runtime stack if necessary. This supports mixing legacy codes that keep
++a 4-byte aligned stack with modern codes that keep a 16-byte stack for
++SSE compatibility. See also the attribute @code{force_align_arg_pointer},
++applicable to individual functions.
++
++@item -mpreferred-stack-boundary=@var{num}
++@opindex mpreferred-stack-boundary
++Attempt to keep the stack boundary aligned to a 2 raised to @var{num}
++byte boundary. If @option{-mpreferred-stack-boundary} is not specified,
++the default is 4 (16 bytes or 128 bits).
++
++@item -mincoming-stack-boundary=@var{num}
++@opindex mincoming-stack-boundary
++Assume the incoming stack is aligned to a 2 raised to @var{num} byte
++boundary. If @option{-mincoming-stack-boundary} is not specified,
++the one specified by @option{-mpreferred-stack-boundary} will be used.
++
++On Pentium and PentiumPro, @code{double} and @code{long double} values
++should be aligned to an 8 byte boundary (see @option{-malign-double}) or
++suffer significant run time performance penalties. On Pentium III, the
++Streaming SIMD Extension (SSE) data type @code{__m128} may not work
++properly if it is not 16 byte aligned.
++
++To ensure proper alignment of this values on the stack, the stack boundary
++must be as aligned as that required by any value stored on the stack.
++Further, every function must be generated such that it keeps the stack
++aligned. Thus calling a function compiled with a higher preferred
++stack boundary from a function compiled with a lower preferred stack
++boundary will most likely misalign the stack. It is recommended that
++libraries that use callbacks always use the default setting.
++
++This extra alignment does consume extra stack space, and generally
++increases code size. Code that is sensitive to stack space usage, such
++as embedded systems and operating system kernels, may want to reduce the
++preferred alignment to @option{-mpreferred-stack-boundary=2}.
++
++@item -mmmx
++@itemx -mno-mmx
++@itemx -msse
++@itemx -mno-sse
++@itemx -msse2
++@itemx -mno-sse2
++@itemx -msse3
++@itemx -mno-sse3
++@itemx -mssse3
++@itemx -mno-ssse3
++@itemx -msse4.1
++@itemx -mno-sse4.1
++@itemx -msse4.2
++@itemx -mno-sse4.2
++@itemx -msse4
++@itemx -mno-sse4
++@itemx -mavx
++@itemx -mno-avx
++@itemx -maes
++@itemx -mno-aes
++@itemx -mpclmul
++@itemx -mno-pclmul
++@itemx -msse4a
++@itemx -mno-sse4a
++@itemx -msse5
++@itemx -mno-sse5
++@itemx -m3dnow
++@itemx -mno-3dnow
++@itemx -mpopcnt
++@itemx -mno-popcnt
++@itemx -mabm
++@itemx -mno-abm
++@opindex mmmx
++@opindex mno-mmx
++@opindex msse
++@opindex mno-sse
++@opindex m3dnow
++@opindex mno-3dnow
++These switches enable or disable the use of instructions in the MMX,
++SSE, SSE2, SSE3, SSSE3, SSE4.1, AVX, AES, PCLMUL, SSE4A, SSE5, ABM or
++3DNow!@: extended instruction sets.
++These extensions are also available as built-in functions: see
++@ref{X86 Built-in Functions}, for details of the functions enabled and
++disabled by these switches.
++
++To have SSE/SSE2 instructions generated automatically from floating-point
++code (as opposed to 387 instructions), see @option{-mfpmath=sse}.
++
++GCC depresses SSEx instructions when @option{-mavx} is used. Instead, it
++generates new AVX instructions or AVX equivalence for all SSEx instructions
++when needed.
++
++These options will enable GCC to use these extended instructions in
++generated code, even without @option{-mfpmath=sse}. Applications which
++perform runtime CPU detection must compile separate files for each
++supported architecture, using the appropriate flags. In particular,
++the file containing the CPU detection code should be compiled without
++these options.
++
++@item -mcld
++@opindex mcld
++This option instructs GCC to emit a @code{cld} instruction in the prologue
++of functions that use string instructions. String instructions depend on
++the DF flag to select between autoincrement or autodecrement mode. While the
++ABI specifies the DF flag to be cleared on function entry, some operating
++systems violate this specification by not clearing the DF flag in their
++exception dispatchers. The exception handler can be invoked with the DF flag
++set which leads to wrong direction mode, when string instructions are used.
++This option can be enabled by default on 32-bit x86 targets by configuring
++GCC with the @option{--enable-cld} configure option. Generation of @code{cld}
++instructions can be suppressed with the @option{-mno-cld} compiler option
++in this case.
++
++@item -mcx16
++@opindex mcx16
++This option will enable GCC to use CMPXCHG16B instruction in generated code.
++CMPXCHG16B allows for atomic operations on 128-bit double quadword (or oword)
++data types. This is useful for high resolution counters that could be updated
++by multiple processors (or cores). This instruction is generated as part of
++atomic built-in functions: see @ref{Atomic Builtins} for details.
++
++@item -msahf
++@opindex msahf
++This option will enable GCC to use SAHF instruction in generated 64-bit code.
++Early Intel CPUs with Intel 64 lacked LAHF and SAHF instructions supported
++by AMD64 until introduction of Pentium 4 G1 step in December 2005. LAHF and
++SAHF are load and store instructions, respectively, for certain status flags.
++In 64-bit mode, SAHF instruction is used to optimize @code{fmod}, @code{drem}
++or @code{remainder} built-in functions: see @ref{Other Builtins} for details.
++
++@item -mrecip
++@opindex mrecip
++This option will enable GCC to use RCPSS and RSQRTSS instructions (and their
++vectorized variants RCPPS and RSQRTPS) with an additional Newton-Raphson step
++to increase precision instead of DIVSS and SQRTSS (and their vectorized
++variants) for single precision floating point arguments. These instructions
++are generated only when @option{-funsafe-math-optimizations} is enabled
++together with @option{-finite-math-only} and @option{-fno-trapping-math}.
++Note that while the throughput of the sequence is higher than the throughput
++of the non-reciprocal instruction, the precision of the sequence can be
++decreased by up to 2 ulp (i.e. the inverse of 1.0 equals 0.99999994).
++
++@item -mveclibabi=@var{type}
++@opindex mveclibabi
++Specifies the ABI type to use for vectorizing intrinsics using an
++external library. Supported types are @code{svml} for the Intel short
++vector math library and @code{acml} for the AMD math core library style
++of interfacing. GCC will currently emit calls to @code{vmldExp2},
++@code{vmldLn2}, @code{vmldLog102}, @code{vmldLog102}, @code{vmldPow2},
++@code{vmldTanh2}, @code{vmldTan2}, @code{vmldAtan2}, @code{vmldAtanh2},
++@code{vmldCbrt2}, @code{vmldSinh2}, @code{vmldSin2}, @code{vmldAsinh2},
++@code{vmldAsin2}, @code{vmldCosh2}, @code{vmldCos2}, @code{vmldAcosh2},
++@code{vmldAcos2}, @code{vmlsExp4}, @code{vmlsLn4}, @code{vmlsLog104},
++@code{vmlsLog104}, @code{vmlsPow4}, @code{vmlsTanh4}, @code{vmlsTan4},
++@code{vmlsAtan4}, @code{vmlsAtanh4}, @code{vmlsCbrt4}, @code{vmlsSinh4},
++@code{vmlsSin4}, @code{vmlsAsinh4}, @code{vmlsAsin4}, @code{vmlsCosh4},
++@code{vmlsCos4}, @code{vmlsAcosh4} and @code{vmlsAcos4} for corresponding
++function type when @option{-mveclibabi=svml} is used and @code{__vrd2_sin},
++@code{__vrd2_cos}, @code{__vrd2_exp}, @code{__vrd2_log}, @code{__vrd2_log2},
++@code{__vrd2_log10}, @code{__vrs4_sinf}, @code{__vrs4_cosf},
++@code{__vrs4_expf}, @code{__vrs4_logf}, @code{__vrs4_log2f},
++@code{__vrs4_log10f} and @code{__vrs4_powf} for corresponding function type
++when @option{-mveclibabi=acml} is used. Both @option{-ftree-vectorize} and
++@option{-funsafe-math-optimizations} have to be enabled. A SVML or ACML ABI
++compatible library will have to be specified at link time.
++
++@item -mpush-args
++@itemx -mno-push-args
++@opindex mpush-args
++@opindex mno-push-args
++Use PUSH operations to store outgoing parameters. This method is shorter
++and usually equally fast as method using SUB/MOV operations and is enabled
++by default. In some cases disabling it may improve performance because of
++improved scheduling and reduced dependencies.
++
++@item -maccumulate-outgoing-args
++@opindex maccumulate-outgoing-args
++If enabled, the maximum amount of space required for outgoing arguments will be
++computed in the function prologue. This is faster on most modern CPUs
++because of reduced dependencies, improved scheduling and reduced stack usage
++when preferred stack boundary is not equal to 2. The drawback is a notable
++increase in code size. This switch implies @option{-mno-push-args}.
++
++@item -mthreads
++@opindex mthreads
++Support thread-safe exception handling on @samp{Mingw32}. Code that relies
++on thread-safe exception handling must compile and link all code with the
++@option{-mthreads} option. When compiling, @option{-mthreads} defines
++@option{-D_MT}; when linking, it links in a special thread helper library
++@option{-lmingwthrd} which cleans up per thread exception handling data.
++
++@item -mno-align-stringops
++@opindex mno-align-stringops
++Do not align destination of inlined string operations. This switch reduces
++code size and improves performance in case the destination is already aligned,
++but GCC doesn't know about it.
++
++@item -minline-all-stringops
++@opindex minline-all-stringops
++By default GCC inlines string operations only when destination is known to be
++aligned at least to 4 byte boundary. This enables more inlining, increase code
++size, but may improve performance of code that depends on fast memcpy, strlen
++and memset for short lengths.
++
++@item -minline-stringops-dynamically
++@opindex minline-stringops-dynamically
++For string operation of unknown size, inline runtime checks so for small
++blocks inline code is used, while for large blocks library call is used.
++
++@item -mstringop-strategy=@var{alg}
++@opindex mstringop-strategy=@var{alg}
++Overwrite internal decision heuristic about particular algorithm to inline
++string operation with. The allowed values are @code{rep_byte},
++@code{rep_4byte}, @code{rep_8byte} for expanding using i386 @code{rep} prefix
++of specified size, @code{byte_loop}, @code{loop}, @code{unrolled_loop} for
++expanding inline loop, @code{libcall} for always expanding library call.
++
++@item -momit-leaf-frame-pointer
++@opindex momit-leaf-frame-pointer
++Don't keep the frame pointer in a register for leaf functions. This
++avoids the instructions to save, set up and restore frame pointers and
++makes an extra register available in leaf functions. The option
++@option{-fomit-frame-pointer} removes the frame pointer for all functions
++which might make debugging harder.
++
++@item -mtls-direct-seg-refs
++@itemx -mno-tls-direct-seg-refs
++@opindex mtls-direct-seg-refs
++Controls whether TLS variables may be accessed with offsets from the
++TLS segment register (@code{%gs} for 32-bit, @code{%fs} for 64-bit),
++or whether the thread base pointer must be added. Whether or not this
++is legal depends on the operating system, and whether it maps the
++segment to cover the entire TLS area.
++
++For systems that use GNU libc, the default is on.
++
++@item -mfused-madd
++@itemx -mno-fused-madd
++@opindex mfused-madd
++Enable automatic generation of fused floating point multiply-add instructions
++if the ISA supports such instructions. The -mfused-madd option is on by
++default. The fused multiply-add instructions have a different
++rounding behavior compared to executing a multiply followed by an add.
++
++@item -msse2avx
++@itemx -mno-sse2avx
++@opindex msse2avx
++Specify that the assembler should encode SSE instructions with VEX
++prefix. The option @option{-mavx} turns this on by default.
++@end table
++
++These @samp{-m} switches are supported in addition to the above
++on AMD x86-64 processors in 64-bit environments.
++
++@table @gcctabopt
++@item -m32
++@itemx -m64
++@opindex m32
++@opindex m64
++Generate code for a 32-bit or 64-bit environment.
++The 32-bit environment sets int, long and pointer to 32 bits and
++generates code that runs on any i386 system.
++The 64-bit environment sets int to 32 bits and long and pointer
++to 64 bits and generates code for AMD's x86-64 architecture. For
++darwin only the -m64 option turns off the @option{-fno-pic} and
++@option{-mdynamic-no-pic} options.
++
++@item -mno-red-zone
++@opindex no-red-zone
++Do not use a so called red zone for x86-64 code. The red zone is mandated
++by the x86-64 ABI, it is a 128-byte area beyond the location of the
++stack pointer that will not be modified by signal or interrupt handlers
++and therefore can be used for temporary data without adjusting the stack
++pointer. The flag @option{-mno-red-zone} disables this red zone.
++
++@item -mcmodel=small
++@opindex mcmodel=small
++Generate code for the small code model: the program and its symbols must
++be linked in the lower 2 GB of the address space. Pointers are 64 bits.
++Programs can be statically or dynamically linked. This is the default
++code model.
++
++@item -mcmodel=kernel
++@opindex mcmodel=kernel
++Generate code for the kernel code model. The kernel runs in the
++negative 2 GB of the address space.
++This model has to be used for Linux kernel code.
++
++@item -mcmodel=medium
++@opindex mcmodel=medium
++Generate code for the medium model: The program is linked in the lower 2
++GB of the address space. Small symbols are also placed there. Symbols
++with sizes larger than @option{-mlarge-data-threshold} are put into
++large data or bss sections and can be located above 2GB. Programs can
++be statically or dynamically linked.
++
++@item -mcmodel=large
++@opindex mcmodel=large
++Generate code for the large model: This model makes no assumptions
++about addresses and sizes of sections.
++@end table
++
++@node IA-64 Options
++@subsection IA-64 Options
++@cindex IA-64 Options
++
++These are the @samp{-m} options defined for the Intel IA-64 architecture.
++
++@table @gcctabopt
++@item -mbig-endian
++@opindex mbig-endian
++Generate code for a big endian target. This is the default for HP-UX@.
++
++@item -mlittle-endian
++@opindex mlittle-endian
++Generate code for a little endian target. This is the default for AIX5
++and GNU/Linux.
++
++@item -mgnu-as
++@itemx -mno-gnu-as
++@opindex mgnu-as
++@opindex mno-gnu-as
++Generate (or don't) code for the GNU assembler. This is the default.
++@c Also, this is the default if the configure option @option{--with-gnu-as}
++@c is used.
++
++@item -mgnu-ld
++@itemx -mno-gnu-ld
++@opindex mgnu-ld
++@opindex mno-gnu-ld
++Generate (or don't) code for the GNU linker. This is the default.
++@c Also, this is the default if the configure option @option{--with-gnu-ld}
++@c is used.
++
++@item -mno-pic
++@opindex mno-pic
++Generate code that does not use a global pointer register. The result
++is not position independent code, and violates the IA-64 ABI@.
++
++@item -mvolatile-asm-stop
++@itemx -mno-volatile-asm-stop
++@opindex mvolatile-asm-stop
++@opindex mno-volatile-asm-stop
++Generate (or don't) a stop bit immediately before and after volatile asm
++statements.
++
++@item -mregister-names
++@itemx -mno-register-names
++@opindex mregister-names
++@opindex mno-register-names
++Generate (or don't) @samp{in}, @samp{loc}, and @samp{out} register names for
++the stacked registers. This may make assembler output more readable.
++
++@item -mno-sdata
++@itemx -msdata
++@opindex mno-sdata
++@opindex msdata
++Disable (or enable) optimizations that use the small data section. This may
++be useful for working around optimizer bugs.
++
++@item -mconstant-gp
++@opindex mconstant-gp
++Generate code that uses a single constant global pointer value. This is
++useful when compiling kernel code.
++
++@item -mauto-pic
++@opindex mauto-pic
++Generate code that is self-relocatable. This implies @option{-mconstant-gp}.
++This is useful when compiling firmware code.
++
++@item -minline-float-divide-min-latency
++@opindex minline-float-divide-min-latency
++Generate code for inline divides of floating point values
++using the minimum latency algorithm.
++
++@item -minline-float-divide-max-throughput
++@opindex minline-float-divide-max-throughput
++Generate code for inline divides of floating point values
++using the maximum throughput algorithm.
++
++@item -minline-int-divide-min-latency
++@opindex minline-int-divide-min-latency
++Generate code for inline divides of integer values
++using the minimum latency algorithm.
++
++@item -minline-int-divide-max-throughput
++@opindex minline-int-divide-max-throughput
++Generate code for inline divides of integer values
++using the maximum throughput algorithm.
++
++@item -minline-sqrt-min-latency
++@opindex minline-sqrt-min-latency
++Generate code for inline square roots
++using the minimum latency algorithm.
++
++@item -minline-sqrt-max-throughput
++@opindex minline-sqrt-max-throughput
++Generate code for inline square roots
++using the maximum throughput algorithm.
++
++@item -mno-dwarf2-asm
++@itemx -mdwarf2-asm
++@opindex mno-dwarf2-asm
++@opindex mdwarf2-asm
++Don't (or do) generate assembler code for the DWARF2 line number debugging
++info. This may be useful when not using the GNU assembler.
++
++@item -mearly-stop-bits
++@itemx -mno-early-stop-bits
++@opindex mearly-stop-bits
++@opindex mno-early-stop-bits
++Allow stop bits to be placed earlier than immediately preceding the
++instruction that triggered the stop bit. This can improve instruction
++scheduling, but does not always do so.
++
++@item -mfixed-range=@var{register-range}
++@opindex mfixed-range
++Generate code treating the given register range as fixed registers.
++A fixed register is one that the register allocator can not use. This is
++useful when compiling kernel code. A register range is specified as
++two registers separated by a dash. Multiple register ranges can be
++specified separated by a comma.
++
++@item -mtls-size=@var{tls-size}
++@opindex mtls-size
++Specify bit size of immediate TLS offsets. Valid values are 14, 22, and
++64.
++
++@item -mtune=@var{cpu-type}
++@opindex mtune
++Tune the instruction scheduling for a particular CPU, Valid values are
++itanium, itanium1, merced, itanium2, and mckinley.
++
++@item -mt
++@itemx -pthread
++@opindex mt
++@opindex pthread
++Add support for multithreading using the POSIX threads library. This
++option sets flags for both the preprocessor and linker. It does
++not affect the thread safety of object code produced by the compiler or
++that of libraries supplied with it. These are HP-UX specific flags.
++
++@item -milp32
++@itemx -mlp64
++@opindex milp32
++@opindex mlp64
++Generate code for a 32-bit or 64-bit environment.
++The 32-bit environment sets int, long and pointer to 32 bits.
++The 64-bit environment sets int to 32 bits and long and pointer
++to 64 bits. These are HP-UX specific flags.
++
++@item -mno-sched-br-data-spec
++@itemx -msched-br-data-spec
++@opindex mno-sched-br-data-spec
++@opindex msched-br-data-spec
++(Dis/En)able data speculative scheduling before reload.
++This will result in generation of the ld.a instructions and
++the corresponding check instructions (ld.c / chk.a).
++The default is 'disable'.
++
++@item -msched-ar-data-spec
++@itemx -mno-sched-ar-data-spec
++@opindex msched-ar-data-spec
++@opindex mno-sched-ar-data-spec
++(En/Dis)able data speculative scheduling after reload.
++This will result in generation of the ld.a instructions and
++the corresponding check instructions (ld.c / chk.a).
++The default is 'enable'.
++
++@item -mno-sched-control-spec
++@itemx -msched-control-spec
++@opindex mno-sched-control-spec
++@opindex msched-control-spec
++(Dis/En)able control speculative scheduling. This feature is
++available only during region scheduling (i.e.@: before reload).
++This will result in generation of the ld.s instructions and
++the corresponding check instructions chk.s .
++The default is 'disable'.
++
++@item -msched-br-in-data-spec
++@itemx -mno-sched-br-in-data-spec
++@opindex msched-br-in-data-spec
++@opindex mno-sched-br-in-data-spec
++(En/Dis)able speculative scheduling of the instructions that
++are dependent on the data speculative loads before reload.
++This is effective only with @option{-msched-br-data-spec} enabled.
++The default is 'enable'.
++
++@item -msched-ar-in-data-spec
++@itemx -mno-sched-ar-in-data-spec
++@opindex msched-ar-in-data-spec
++@opindex mno-sched-ar-in-data-spec
++(En/Dis)able speculative scheduling of the instructions that
++are dependent on the data speculative loads after reload.
++This is effective only with @option{-msched-ar-data-spec} enabled.
++The default is 'enable'.
++
++@item -msched-in-control-spec
++@itemx -mno-sched-in-control-spec
++@opindex msched-in-control-spec
++@opindex mno-sched-in-control-spec
++(En/Dis)able speculative scheduling of the instructions that
++are dependent on the control speculative loads.
++This is effective only with @option{-msched-control-spec} enabled.
++The default is 'enable'.
++
++@item -msched-ldc
++@itemx -mno-sched-ldc
++@opindex msched-ldc
++@opindex mno-sched-ldc
++(En/Dis)able use of simple data speculation checks ld.c .
++If disabled, only chk.a instructions will be emitted to check
++data speculative loads.
++The default is 'enable'.
++
++@item -mno-sched-control-ldc
++@itemx -msched-control-ldc
++@opindex mno-sched-control-ldc
++@opindex msched-control-ldc
++(Dis/En)able use of ld.c instructions to check control speculative loads.
++If enabled, in case of control speculative load with no speculatively
++scheduled dependent instructions this load will be emitted as ld.sa and
++ld.c will be used to check it.
++The default is 'disable'.
++
++@item -mno-sched-spec-verbose
++@itemx -msched-spec-verbose
++@opindex mno-sched-spec-verbose
++@opindex msched-spec-verbose
++(Dis/En)able printing of the information about speculative motions.
++
++@item -mno-sched-prefer-non-data-spec-insns
++@itemx -msched-prefer-non-data-spec-insns
++@opindex mno-sched-prefer-non-data-spec-insns
++@opindex msched-prefer-non-data-spec-insns
++If enabled, data speculative instructions will be chosen for schedule
++only if there are no other choices at the moment. This will make
++the use of the data speculation much more conservative.
++The default is 'disable'.
++
++@item -mno-sched-prefer-non-control-spec-insns
++@itemx -msched-prefer-non-control-spec-insns
++@opindex mno-sched-prefer-non-control-spec-insns
++@opindex msched-prefer-non-control-spec-insns
++If enabled, control speculative instructions will be chosen for schedule
++only if there are no other choices at the moment. This will make
++the use of the control speculation much more conservative.
++The default is 'disable'.
++
++@item -mno-sched-count-spec-in-critical-path
++@itemx -msched-count-spec-in-critical-path
++@opindex mno-sched-count-spec-in-critical-path
++@opindex msched-count-spec-in-critical-path
++If enabled, speculative dependencies will be considered during
++computation of the instructions priorities. This will make the use of the
++speculation a bit more conservative.
++The default is 'disable'.
++
++@end table
++
++@node M32C Options
++@subsection M32C Options
++@cindex M32C options
++
++@table @gcctabopt
++@item -mcpu=@var{name}
++@opindex mcpu=
++Select the CPU for which code is generated. @var{name} may be one of
++@samp{r8c} for the R8C/Tiny series, @samp{m16c} for the M16C (up to
++/60) series, @samp{m32cm} for the M16C/80 series, or @samp{m32c} for
++the M32C/80 series.
++
++@item -msim
++@opindex msim
++Specifies that the program will be run on the simulator. This causes
++an alternate runtime library to be linked in which supports, for
++example, file I/O@. You must not use this option when generating
++programs that will run on real hardware; you must provide your own
++runtime library for whatever I/O functions are needed.
++
++@item -memregs=@var{number}
++@opindex memregs=
++Specifies the number of memory-based pseudo-registers GCC will use
++during code generation. These pseudo-registers will be used like real
++registers, so there is a tradeoff between GCC's ability to fit the
++code into available registers, and the performance penalty of using
++memory instead of registers. Note that all modules in a program must
++be compiled with the same value for this option. Because of that, you
++must not use this option with the default runtime libraries gcc
++builds.
++
++@end table
++
++@node M32R/D Options
++@subsection M32R/D Options
++@cindex M32R/D options
++
++These @option{-m} options are defined for Renesas M32R/D architectures:
++
++@table @gcctabopt
++@item -m32r2
++@opindex m32r2
++Generate code for the M32R/2@.
++
++@item -m32rx
++@opindex m32rx
++Generate code for the M32R/X@.
++
++@item -m32r
++@opindex m32r
++Generate code for the M32R@. This is the default.
++
++@item -mmodel=small
++@opindex mmodel=small
++Assume all objects live in the lower 16MB of memory (so that their addresses
++can be loaded with the @code{ld24} instruction), and assume all subroutines
++are reachable with the @code{bl} instruction.
++This is the default.
++
++The addressability of a particular object can be set with the
++@code{model} attribute.
++
++@item -mmodel=medium
++@opindex mmodel=medium
++Assume objects may be anywhere in the 32-bit address space (the compiler
++will generate @code{seth/add3} instructions to load their addresses), and
++assume all subroutines are reachable with the @code{bl} instruction.
++
++@item -mmodel=large
++@opindex mmodel=large
++Assume objects may be anywhere in the 32-bit address space (the compiler
++will generate @code{seth/add3} instructions to load their addresses), and
++assume subroutines may not be reachable with the @code{bl} instruction
++(the compiler will generate the much slower @code{seth/add3/jl}
++instruction sequence).
++
++@item -msdata=none
++@opindex msdata=none
++Disable use of the small data area. Variables will be put into
++one of @samp{.data}, @samp{bss}, or @samp{.rodata} (unless the
++@code{section} attribute has been specified).
++This is the default.
++
++The small data area consists of sections @samp{.sdata} and @samp{.sbss}.
++Objects may be explicitly put in the small data area with the
++@code{section} attribute using one of these sections.
++
++@item -msdata=sdata
++@opindex msdata=sdata
++Put small global and static data in the small data area, but do not
++generate special code to reference them.
++
++@item -msdata=use
++@opindex msdata=use
++Put small global and static data in the small data area, and generate
++special instructions to reference them.
++
++@item -G @var{num}
++@opindex G
++@cindex smaller data references
++Put global and static objects less than or equal to @var{num} bytes
++into the small data or bss sections instead of the normal data or bss
++sections. The default value of @var{num} is 8.
++The @option{-msdata} option must be set to one of @samp{sdata} or @samp{use}
++for this option to have any effect.
++
++All modules should be compiled with the same @option{-G @var{num}} value.
++Compiling with different values of @var{num} may or may not work; if it
++doesn't the linker will give an error message---incorrect code will not be
++generated.
++
++@item -mdebug
++@opindex mdebug
++Makes the M32R specific code in the compiler display some statistics
++that might help in debugging programs.
++
++@item -malign-loops
++@opindex malign-loops
++Align all loops to a 32-byte boundary.
++
++@item -mno-align-loops
++@opindex mno-align-loops
++Do not enforce a 32-byte alignment for loops. This is the default.
++
++@item -missue-rate=@var{number}
++@opindex missue-rate=@var{number}
++Issue @var{number} instructions per cycle. @var{number} can only be 1
++or 2.
++
++@item -mbranch-cost=@var{number}
++@opindex mbranch-cost=@var{number}
++@var{number} can only be 1 or 2. If it is 1 then branches will be
++preferred over conditional code, if it is 2, then the opposite will
++apply.
++
++@item -mflush-trap=@var{number}
++@opindex mflush-trap=@var{number}
++Specifies the trap number to use to flush the cache. The default is
++12. Valid numbers are between 0 and 15 inclusive.
++
++@item -mno-flush-trap
++@opindex mno-flush-trap
++Specifies that the cache cannot be flushed by using a trap.
++
++@item -mflush-func=@var{name}
++@opindex mflush-func=@var{name}
++Specifies the name of the operating system function to call to flush
++the cache. The default is @emph{_flush_cache}, but a function call
++will only be used if a trap is not available.
++
++@item -mno-flush-func
++@opindex mno-flush-func
++Indicates that there is no OS function for flushing the cache.
++
++@end table
++
++@node M680x0 Options
++@subsection M680x0 Options
++@cindex M680x0 options
++
++These are the @samp{-m} options defined for M680x0 and ColdFire processors.
++The default settings depend on which architecture was selected when
++the compiler was configured; the defaults for the most common choices
++are given below.
++
++@table @gcctabopt
++@item -march=@var{arch}
++@opindex march
++Generate code for a specific M680x0 or ColdFire instruction set
++architecture. Permissible values of @var{arch} for M680x0
++architectures are: @samp{68000}, @samp{68010}, @samp{68020},
++@samp{68030}, @samp{68040}, @samp{68060} and @samp{cpu32}. ColdFire
++architectures are selected according to Freescale's ISA classification
++and the permissible values are: @samp{isaa}, @samp{isaaplus},
++@samp{isab} and @samp{isac}.
++
++gcc defines a macro @samp{__mcf@var{arch}__} whenever it is generating
++code for a ColdFire target. The @var{arch} in this macro is one of the
++@option{-march} arguments given above.
++
++When used together, @option{-march} and @option{-mtune} select code
++that runs on a family of similar processors but that is optimized
++for a particular microarchitecture.
++
++@item -mcpu=@var{cpu}
++@opindex mcpu
++Generate code for a specific M680x0 or ColdFire processor.
++The M680x0 @var{cpu}s are: @samp{68000}, @samp{68010}, @samp{68020},
++@samp{68030}, @samp{68040}, @samp{68060}, @samp{68302}, @samp{68332}
++and @samp{cpu32}. The ColdFire @var{cpu}s are given by the table
++below, which also classifies the CPUs into families:
++
++@multitable @columnfractions 0.20 0.80
++@item @strong{Family} @tab @strong{@samp{-mcpu} arguments}
++@item @samp{51qe} @tab @samp{51qe}
++@item @samp{5206} @tab @samp{5202} @samp{5204} @samp{5206}
++@item @samp{5206e} @tab @samp{5206e}
++@item @samp{5208} @tab @samp{5207} @samp{5208}
++@item @samp{5211a} @tab @samp{5210a} @samp{5211a}
++@item @samp{5213} @tab @samp{5211} @samp{5212} @samp{5213}
++@item @samp{5216} @tab @samp{5214} @samp{5216}
++@item @samp{52235} @tab @samp{52230} @samp{52231} @samp{52232} @samp{52233} @samp{52234} @samp{52235}
++@item @samp{5225} @tab @samp{5224} @samp{5225}
++@item @samp{5235} @tab @samp{5232} @samp{5233} @samp{5234} @samp{5235} @samp{523x}
++@item @samp{5249} @tab @samp{5249}
++@item @samp{5250} @tab @samp{5250}
++@item @samp{5271} @tab @samp{5270} @samp{5271}
++@item @samp{5272} @tab @samp{5272}
++@item @samp{5275} @tab @samp{5274} @samp{5275}
++@item @samp{5282} @tab @samp{5280} @samp{5281} @samp{5282} @samp{528x}
++@item @samp{5307} @tab @samp{5307}
++@item @samp{5329} @tab @samp{5327} @samp{5328} @samp{5329} @samp{532x}
++@item @samp{5373} @tab @samp{5372} @samp{5373} @samp{537x}
++@item @samp{5407} @tab @samp{5407}
++@item @samp{5475} @tab @samp{5470} @samp{5471} @samp{5472} @samp{5473} @samp{5474} @samp{5475} @samp{547x} @samp{5480} @samp{5481} @samp{5482} @samp{5483} @samp{5484} @samp{5485}
++@end multitable
++
++@option{-mcpu=@var{cpu}} overrides @option{-march=@var{arch}} if
++@var{arch} is compatible with @var{cpu}. Other combinations of
++@option{-mcpu} and @option{-march} are rejected.
++
++gcc defines the macro @samp{__mcf_cpu_@var{cpu}} when ColdFire target
++@var{cpu} is selected. It also defines @samp{__mcf_family_@var{family}},
++where the value of @var{family} is given by the table above.
++
++@item -mtune=@var{tune}
++@opindex mtune
++Tune the code for a particular microarchitecture, within the
++constraints set by @option{-march} and @option{-mcpu}.
++The M680x0 microarchitectures are: @samp{68000}, @samp{68010},
++@samp{68020}, @samp{68030}, @samp{68040}, @samp{68060}
++and @samp{cpu32}. The ColdFire microarchitectures
++are: @samp{cfv1}, @samp{cfv2}, @samp{cfv3}, @samp{cfv4} and @samp{cfv4e}.
++
++You can also use @option{-mtune=68020-40} for code that needs
++to run relatively well on 68020, 68030 and 68040 targets.
++@option{-mtune=68020-60} is similar but includes 68060 targets
++as well. These two options select the same tuning decisions as
++@option{-m68020-40} and @option{-m68020-60} respectively.
++
++gcc defines the macros @samp{__mc@var{arch}} and @samp{__mc@var{arch}__}
++when tuning for 680x0 architecture @var{arch}. It also defines
++@samp{mc@var{arch}} unless either @option{-ansi} or a non-GNU @option{-std}
++option is used. If gcc is tuning for a range of architectures,
++as selected by @option{-mtune=68020-40} or @option{-mtune=68020-60},
++it defines the macros for every architecture in the range.
++
++gcc also defines the macro @samp{__m@var{uarch}__} when tuning for
++ColdFire microarchitecture @var{uarch}, where @var{uarch} is one
++of the arguments given above.
++
++@item -m68000
++@itemx -mc68000
++@opindex m68000
++@opindex mc68000
++Generate output for a 68000. This is the default
++when the compiler is configured for 68000-based systems.
++It is equivalent to @option{-march=68000}.
++
++Use this option for microcontrollers with a 68000 or EC000 core,
++including the 68008, 68302, 68306, 68307, 68322, 68328 and 68356.
++
++@item -m68010
++@opindex m68010
++Generate output for a 68010. This is the default
++when the compiler is configured for 68010-based systems.
++It is equivalent to @option{-march=68010}.
++
++@item -m68020
++@itemx -mc68020
++@opindex m68020
++@opindex mc68020
++Generate output for a 68020. This is the default
++when the compiler is configured for 68020-based systems.
++It is equivalent to @option{-march=68020}.
++
++@item -m68030
++@opindex m68030
++Generate output for a 68030. This is the default when the compiler is
++configured for 68030-based systems. It is equivalent to
++@option{-march=68030}.
++
++@item -m68040
++@opindex m68040
++Generate output for a 68040. This is the default when the compiler is
++configured for 68040-based systems. It is equivalent to
++@option{-march=68040}.
++
++This option inhibits the use of 68881/68882 instructions that have to be
++emulated by software on the 68040. Use this option if your 68040 does not
++have code to emulate those instructions.
++
++@item -m68060
++@opindex m68060
++Generate output for a 68060. This is the default when the compiler is
++configured for 68060-based systems. It is equivalent to
++@option{-march=68060}.
++
++This option inhibits the use of 68020 and 68881/68882 instructions that
++have to be emulated by software on the 68060. Use this option if your 68060
++does not have code to emulate those instructions.
++
++@item -mcpu32
++@opindex mcpu32
++Generate output for a CPU32. This is the default
++when the compiler is configured for CPU32-based systems.
++It is equivalent to @option{-march=cpu32}.
++
++Use this option for microcontrollers with a
++CPU32 or CPU32+ core, including the 68330, 68331, 68332, 68333, 68334,
++68336, 68340, 68341, 68349 and 68360.
++
++@item -m5200
++@opindex m5200
++Generate output for a 520X ColdFire CPU@. This is the default
++when the compiler is configured for 520X-based systems.
++It is equivalent to @option{-mcpu=5206}, and is now deprecated
++in favor of that option.
++
++Use this option for microcontroller with a 5200 core, including
++the MCF5202, MCF5203, MCF5204 and MCF5206.
++
++@item -m5206e
++@opindex m5206e
++Generate output for a 5206e ColdFire CPU@. The option is now
++deprecated in favor of the equivalent @option{-mcpu=5206e}.
++
++@item -m528x
++@opindex m528x
++Generate output for a member of the ColdFire 528X family.
++The option is now deprecated in favor of the equivalent
++@option{-mcpu=528x}.
++
++@item -m5307
++@opindex m5307
++Generate output for a ColdFire 5307 CPU@. The option is now deprecated
++in favor of the equivalent @option{-mcpu=5307}.
++
++@item -m5407
++@opindex m5407
++Generate output for a ColdFire 5407 CPU@. The option is now deprecated
++in favor of the equivalent @option{-mcpu=5407}.
++
++@item -mcfv4e
++@opindex mcfv4e
++Generate output for a ColdFire V4e family CPU (e.g.@: 547x/548x).
++This includes use of hardware floating point instructions.
++The option is equivalent to @option{-mcpu=547x}, and is now
++deprecated in favor of that option.
++
++@item -m68020-40
++@opindex m68020-40
++Generate output for a 68040, without using any of the new instructions.
++This results in code which can run relatively efficiently on either a
++68020/68881 or a 68030 or a 68040. The generated code does use the
++68881 instructions that are emulated on the 68040.
++
++The option is equivalent to @option{-march=68020} @option{-mtune=68020-40}.
++
++@item -m68020-60
++@opindex m68020-60
++Generate output for a 68060, without using any of the new instructions.
++This results in code which can run relatively efficiently on either a
++68020/68881 or a 68030 or a 68040. The generated code does use the
++68881 instructions that are emulated on the 68060.
++
++The option is equivalent to @option{-march=68020} @option{-mtune=68020-60}.
++
++@item -mhard-float
++@itemx -m68881
++@opindex mhard-float
++@opindex m68881
++Generate floating-point instructions. This is the default for 68020
++and above, and for ColdFire devices that have an FPU@. It defines the
++macro @samp{__HAVE_68881__} on M680x0 targets and @samp{__mcffpu__}
++on ColdFire targets.
++
++@item -msoft-float
++@opindex msoft-float
++Do not generate floating-point instructions; use library calls instead.
++This is the default for 68000, 68010, and 68832 targets. It is also
++the default for ColdFire devices that have no FPU.
++
++@item -mdiv
++@itemx -mno-div
++@opindex mdiv
++@opindex mno-div
++Generate (do not generate) ColdFire hardware divide and remainder
++instructions. If @option{-march} is used without @option{-mcpu},
++the default is ``on'' for ColdFire architectures and ``off'' for M680x0
++architectures. Otherwise, the default is taken from the target CPU
++(either the default CPU, or the one specified by @option{-mcpu}). For
++example, the default is ``off'' for @option{-mcpu=5206} and ``on'' for
++@option{-mcpu=5206e}.
++
++gcc defines the macro @samp{__mcfhwdiv__} when this option is enabled.
++
++@item -mshort
++@opindex mshort
++Consider type @code{int} to be 16 bits wide, like @code{short int}.
++Additionally, parameters passed on the stack are also aligned to a
++16-bit boundary even on targets whose API mandates promotion to 32-bit.
++
++@item -mno-short
++@opindex mno-short
++Do not consider type @code{int} to be 16 bits wide. This is the default.
++
++@item -mnobitfield
++@itemx -mno-bitfield
++@opindex mnobitfield
++@opindex mno-bitfield
++Do not use the bit-field instructions. The @option{-m68000}, @option{-mcpu32}
++and @option{-m5200} options imply @w{@option{-mnobitfield}}.
++
++@item -mbitfield
++@opindex mbitfield
++Do use the bit-field instructions. The @option{-m68020} option implies
++@option{-mbitfield}. This is the default if you use a configuration
++designed for a 68020.
++
++@item -mrtd
++@opindex mrtd
++Use a different function-calling convention, in which functions
++that take a fixed number of arguments return with the @code{rtd}
++instruction, which pops their arguments while returning. This
++saves one instruction in the caller since there is no need to pop
++the arguments there.
++
++This calling convention is incompatible with the one normally
++used on Unix, so you cannot use it if you need to call libraries
++compiled with the Unix compiler.
++
++Also, you must provide function prototypes for all functions that
++take variable numbers of arguments (including @code{printf});
++otherwise incorrect code will be generated for calls to those
++functions.
++
++In addition, seriously incorrect code will result if you call a
++function with too many arguments. (Normally, extra arguments are
++harmlessly ignored.)
++
++The @code{rtd} instruction is supported by the 68010, 68020, 68030,
++68040, 68060 and CPU32 processors, but not by the 68000 or 5200.
++
++@item -mno-rtd
++@opindex mno-rtd
++Do not use the calling conventions selected by @option{-mrtd}.
++This is the default.
++
++@item -malign-int
++@itemx -mno-align-int
++@opindex malign-int
++@opindex mno-align-int
++Control whether GCC aligns @code{int}, @code{long}, @code{long long},
++@code{float}, @code{double}, and @code{long double} variables on a 32-bit
++boundary (@option{-malign-int}) or a 16-bit boundary (@option{-mno-align-int}).
++Aligning variables on 32-bit boundaries produces code that runs somewhat
++faster on processors with 32-bit busses at the expense of more memory.
++
++@strong{Warning:} if you use the @option{-malign-int} switch, GCC will
++align structures containing the above types differently than
++most published application binary interface specifications for the m68k.
++
++@item -mpcrel
++@opindex mpcrel
++Use the pc-relative addressing mode of the 68000 directly, instead of
++using a global offset table. At present, this option implies @option{-fpic},
++allowing at most a 16-bit offset for pc-relative addressing. @option{-fPIC} is
++not presently supported with @option{-mpcrel}, though this could be supported for
++68020 and higher processors.
++
++@item -mno-strict-align
++@itemx -mstrict-align
++@opindex mno-strict-align
++@opindex mstrict-align
++Do not (do) assume that unaligned memory references will be handled by
++the system.
++
++@item -msep-data
++Generate code that allows the data segment to be located in a different
++area of memory from the text segment. This allows for execute in place in
++an environment without virtual memory management. This option implies
++@option{-fPIC}.
++
++@item -mno-sep-data
++Generate code that assumes that the data segment follows the text segment.
++This is the default.
++
++@item -mid-shared-library
++Generate code that supports shared libraries via the library ID method.
++This allows for execute in place and shared libraries in an environment
++without virtual memory management. This option implies @option{-fPIC}.
++
++@item -mno-id-shared-library
++Generate code that doesn't assume ID based shared libraries are being used.
++This is the default.
++
++@item -mshared-library-id=n
++Specified the identification number of the ID based shared library being
++compiled. Specifying a value of 0 will generate more compact code, specifying
++other values will force the allocation of that number to the current
++library but is no more space or time efficient than omitting this option.
++
++@item -mxgot
++@itemx -mno-xgot
++@opindex mxgot
++@opindex mno-xgot
++When generating position-independent code for ColdFire, generate code
++that works if the GOT has more than 8192 entries. This code is
++larger and slower than code generated without this option. On M680x0
++processors, this option is not needed; @option{-fPIC} suffices.
++
++GCC normally uses a single instruction to load values from the GOT@.
++While this is relatively efficient, it only works if the GOT
++is smaller than about 64k. Anything larger causes the linker
++to report an error such as:
++
++@cindex relocation truncated to fit (ColdFire)
++@smallexample
++relocation truncated to fit: R_68K_GOT16O foobar
++@end smallexample
++
++If this happens, you should recompile your code with @option{-mxgot}.
++It should then work with very large GOTs. However, code generated with
++@option{-mxgot} is less efficient, since it takes 4 instructions to fetch
++the value of a global symbol.
++
++Note that some linkers, including newer versions of the GNU linker,
++can create multiple GOTs and sort GOT entries. If you have such a linker,
++you should only need to use @option{-mxgot} when compiling a single
++object file that accesses more than 8192 GOT entries. Very few do.
++
++These options have no effect unless GCC is generating
++position-independent code.
++
++@end table
++
++@node M68hc1x Options
++@subsection M68hc1x Options
++@cindex M68hc1x options
++
++These are the @samp{-m} options defined for the 68hc11 and 68hc12
++microcontrollers. The default values for these options depends on
++which style of microcontroller was selected when the compiler was configured;
++the defaults for the most common choices are given below.
++
++@table @gcctabopt
++@item -m6811
++@itemx -m68hc11
++@opindex m6811
++@opindex m68hc11
++Generate output for a 68HC11. This is the default
++when the compiler is configured for 68HC11-based systems.
++
++@item -m6812
++@itemx -m68hc12
++@opindex m6812
++@opindex m68hc12
++Generate output for a 68HC12. This is the default
++when the compiler is configured for 68HC12-based systems.
++
++@item -m68S12
++@itemx -m68hcs12
++@opindex m68S12
++@opindex m68hcs12
++Generate output for a 68HCS12.
++
++@item -mauto-incdec
++@opindex mauto-incdec
++Enable the use of 68HC12 pre and post auto-increment and auto-decrement
++addressing modes.
++
++@item -minmax
++@itemx -nominmax
++@opindex minmax
++@opindex mnominmax
++Enable the use of 68HC12 min and max instructions.
++
++@item -mlong-calls
++@itemx -mno-long-calls
++@opindex mlong-calls
++@opindex mno-long-calls
++Treat all calls as being far away (near). If calls are assumed to be
++far away, the compiler will use the @code{call} instruction to
++call a function and the @code{rtc} instruction for returning.
++
++@item -mshort
++@opindex mshort
++Consider type @code{int} to be 16 bits wide, like @code{short int}.
++
++@item -msoft-reg-count=@var{count}
++@opindex msoft-reg-count
++Specify the number of pseudo-soft registers which are used for the
++code generation. The maximum number is 32. Using more pseudo-soft
++register may or may not result in better code depending on the program.
++The default is 4 for 68HC11 and 2 for 68HC12.
++
++@end table
++
++@node MCore Options
++@subsection MCore Options
++@cindex MCore options
++
++These are the @samp{-m} options defined for the Motorola M*Core
++processors.
++
++@table @gcctabopt
++
++@item -mhardlit
++@itemx -mno-hardlit
++@opindex mhardlit
++@opindex mno-hardlit
++Inline constants into the code stream if it can be done in two
++instructions or less.
++
++@item -mdiv
++@itemx -mno-div
++@opindex mdiv
++@opindex mno-div
++Use the divide instruction. (Enabled by default).
++
++@item -mrelax-immediate
++@itemx -mno-relax-immediate
++@opindex mrelax-immediate
++@opindex mno-relax-immediate
++Allow arbitrary sized immediates in bit operations.
++
++@item -mwide-bitfields
++@itemx -mno-wide-bitfields
++@opindex mwide-bitfields
++@opindex mno-wide-bitfields
++Always treat bit-fields as int-sized.
++
++@item -m4byte-functions
++@itemx -mno-4byte-functions
++@opindex m4byte-functions
++@opindex mno-4byte-functions
++Force all functions to be aligned to a four byte boundary.
++
++@item -mcallgraph-data
++@itemx -mno-callgraph-data
++@opindex mcallgraph-data
++@opindex mno-callgraph-data
++Emit callgraph information.
++
++@item -mslow-bytes
++@itemx -mno-slow-bytes
++@opindex mslow-bytes
++@opindex mno-slow-bytes
++Prefer word access when reading byte quantities.
++
++@item -mlittle-endian
++@itemx -mbig-endian
++@opindex mlittle-endian
++@opindex mbig-endian
++Generate code for a little endian target.
++
++@item -m210
++@itemx -m340
++@opindex m210
++@opindex m340
++Generate code for the 210 processor.
++
++@item -mno-lsim
++@opindex no-lsim
++Assume that run-time support has been provided and so omit the
++simulator library (@file{libsim.a)} from the linker command line.
++
++@item -mstack-increment=@var{size}
++@opindex mstack-increment
++Set the maximum amount for a single stack increment operation. Large
++values can increase the speed of programs which contain functions
++that need a large amount of stack space, but they can also trigger a
++segmentation fault if the stack is extended too much. The default
++value is 0x1000.
++
++@end table
++
++@node MIPS Options
++@subsection MIPS Options
++@cindex MIPS options
++
++@table @gcctabopt
++
++@item -EB
++@opindex EB
++Generate big-endian code.
++
++@item -EL
++@opindex EL
++Generate little-endian code. This is the default for @samp{mips*el-*-*}
++configurations.
++
++@item -march=@var{arch}
++@opindex march
++Generate code that will run on @var{arch}, which can be the name of a
++generic MIPS ISA, or the name of a particular processor.
++The ISA names are:
++@samp{mips1}, @samp{mips2}, @samp{mips3}, @samp{mips4},
++@samp{mips32}, @samp{mips32r2}, @samp{mips64} and @samp{mips64r2}.
++The processor names are:
++@samp{4kc}, @samp{4km}, @samp{4kp}, @samp{4ksc},
++@samp{4kec}, @samp{4kem}, @samp{4kep}, @samp{4ksd},
++@samp{5kc}, @samp{5kf},
++@samp{20kc},
++@samp{24kc}, @samp{24kf2_1}, @samp{24kf1_1},
++@samp{24kec}, @samp{24kef2_1}, @samp{24kef1_1},
++@samp{34kc}, @samp{34kf2_1}, @samp{34kf1_1},
++@samp{74kc}, @samp{74kf2_1}, @samp{74kf1_1}, @samp{74kf3_2},
++@samp{loongson2e}, @samp{loongson2f},
++@samp{m4k},
++@samp{octeon},
++@samp{orion},
++@samp{r2000}, @samp{r3000}, @samp{r3900}, @samp{r4000}, @samp{r4400},
++@samp{r4600}, @samp{r4650}, @samp{r6000}, @samp{r8000},
++@samp{rm7000}, @samp{rm9000},
++@samp{r10000}, @samp{r12000}, @samp{r14000}, @samp{r16000},
++@samp{sb1},
++@samp{sr71000},
++@samp{vr4100}, @samp{vr4111}, @samp{vr4120}, @samp{vr4130}, @samp{vr4300},
++@samp{vr5000}, @samp{vr5400}, @samp{vr5500}
++and @samp{xlr}.
++The special value @samp{from-abi} selects the
++most compatible architecture for the selected ABI (that is,
++@samp{mips1} for 32-bit ABIs and @samp{mips3} for 64-bit ABIs)@.
++
++Native Linux/GNU toolchains also support the value @samp{native},
++which selects the best architecture option for the host processor.
++@option{-march=native} has no effect if GCC does not recognize
++the processor.
++
++In processor names, a final @samp{000} can be abbreviated as @samp{k}
++(for example, @samp{-march=r2k}). Prefixes are optional, and
++@samp{vr} may be written @samp{r}.
++
++Names of the form @samp{@var{n}f2_1} refer to processors with
++FPUs clocked at half the rate of the core, names of the form
++@samp{@var{n}f1_1} refer to processors with FPUs clocked at the same
++rate as the core, and names of the form @samp{@var{n}f3_2} refer to
++processors with FPUs clocked a ratio of 3:2 with respect to the core.
++For compatibility reasons, @samp{@var{n}f} is accepted as a synonym
++for @samp{@var{n}f2_1} while @samp{@var{n}x} and @samp{@var{b}fx} are
++accepted as synonyms for @samp{@var{n}f1_1}.
++
++GCC defines two macros based on the value of this option. The first
++is @samp{_MIPS_ARCH}, which gives the name of target architecture, as
++a string. The second has the form @samp{_MIPS_ARCH_@var{foo}},
++where @var{foo} is the capitalized value of @samp{_MIPS_ARCH}@.
++For example, @samp{-march=r2000} will set @samp{_MIPS_ARCH}
++to @samp{"r2000"} and define the macro @samp{_MIPS_ARCH_R2000}.
++
++Note that the @samp{_MIPS_ARCH} macro uses the processor names given
++above. In other words, it will have the full prefix and will not
++abbreviate @samp{000} as @samp{k}. In the case of @samp{from-abi},
++the macro names the resolved architecture (either @samp{"mips1"} or
++@samp{"mips3"}). It names the default architecture when no
++@option{-march} option is given.
++
++@item -mtune=@var{arch}
++@opindex mtune
++Optimize for @var{arch}. Among other things, this option controls
++the way instructions are scheduled, and the perceived cost of arithmetic
++operations. The list of @var{arch} values is the same as for
++@option{-march}.
++
++When this option is not used, GCC will optimize for the processor
++specified by @option{-march}. By using @option{-march} and
++@option{-mtune} together, it is possible to generate code that will
++run on a family of processors, but optimize the code for one
++particular member of that family.
++
++@samp{-mtune} defines the macros @samp{_MIPS_TUNE} and
++@samp{_MIPS_TUNE_@var{foo}}, which work in the same way as the
++@samp{-march} ones described above.
++
++@item -mips1
++@opindex mips1
++Equivalent to @samp{-march=mips1}.
++
++@item -mips2
++@opindex mips2
++Equivalent to @samp{-march=mips2}.
++
++@item -mips3
++@opindex mips3
++Equivalent to @samp{-march=mips3}.
++
++@item -mips4
++@opindex mips4
++Equivalent to @samp{-march=mips4}.
++
++@item -mips32
++@opindex mips32
++Equivalent to @samp{-march=mips32}.
++
++@item -mips32r2
++@opindex mips32r2
++Equivalent to @samp{-march=mips32r2}.
++
++@item -mips64
++@opindex mips64
++Equivalent to @samp{-march=mips64}.
++
++@item -mips64r2
++@opindex mips64r2
++Equivalent to @samp{-march=mips64r2}.
++
++@item -mips16
++@itemx -mno-mips16
++@opindex mips16
++@opindex mno-mips16
++Generate (do not generate) MIPS16 code. If GCC is targetting a
++MIPS32 or MIPS64 architecture, it will make use of the MIPS16e ASE@.
++
++MIPS16 code generation can also be controlled on a per-function basis
++by means of @code{mips16} and @code{nomips16} attributes.
++@xref{Function Attributes}, for more information.
++
++@item -mflip-mips16
++@opindex mflip-mips16
++Generate MIPS16 code on alternating functions. This option is provided
++for regression testing of mixed MIPS16/non-MIPS16 code generation, and is
++not intended for ordinary use in compiling user code.
++
++@item -minterlink-mips16
++@itemx -mno-interlink-mips16
++@opindex minterlink-mips16
++@opindex mno-interlink-mips16
++Require (do not require) that non-MIPS16 code be link-compatible with
++MIPS16 code.
++
++For example, non-MIPS16 code cannot jump directly to MIPS16 code;
++it must either use a call or an indirect jump. @option{-minterlink-mips16}
++therefore disables direct jumps unless GCC knows that the target of the
++jump is not MIPS16.
++
++@item -mabi=32
++@itemx -mabi=o64
++@itemx -mabi=n32
++@itemx -mabi=64
++@itemx -mabi=eabi
++@opindex mabi=32
++@opindex mabi=o64
++@opindex mabi=n32
++@opindex mabi=64
++@opindex mabi=eabi
++Generate code for the given ABI@.
++
++Note that the EABI has a 32-bit and a 64-bit variant. GCC normally
++generates 64-bit code when you select a 64-bit architecture, but you
++can use @option{-mgp32} to get 32-bit code instead.
++
++For information about the O64 ABI, see
++@w{@uref{http://gcc.gnu.org/projects/mipso64-abi.html}}.
++
++GCC supports a variant of the o32 ABI in which floating-point registers
++are 64 rather than 32 bits wide. You can select this combination with
++@option{-mabi=32} @option{-mfp64}. This ABI relies on the @samp{mthc1}
++and @samp{mfhc1} instructions and is therefore only supported for
++MIPS32R2 processors.
++
++The register assignments for arguments and return values remain the
++same, but each scalar value is passed in a single 64-bit register
++rather than a pair of 32-bit registers. For example, scalar
++floating-point values are returned in @samp{$f0} only, not a
++@samp{$f0}/@samp{$f1} pair. The set of call-saved registers also
++remains the same, but all 64 bits are saved.
++
++@item -mabicalls
++@itemx -mno-abicalls
++@opindex mabicalls
++@opindex mno-abicalls
++Generate (do not generate) code that is suitable for SVR4-style
++dynamic objects. @option{-mabicalls} is the default for SVR4-based
++systems.
++
++@item -mshared
++@itemx -mno-shared
++Generate (do not generate) code that is fully position-independent,
++and that can therefore be linked into shared libraries. This option
++only affects @option{-mabicalls}.
++
++All @option{-mabicalls} code has traditionally been position-independent,
++regardless of options like @option{-fPIC} and @option{-fpic}. However,
++as an extension, the GNU toolchain allows executables to use absolute
++accesses for locally-binding symbols. It can also use shorter GP
++initialization sequences and generate direct calls to locally-defined
++functions. This mode is selected by @option{-mno-shared}.
++
++@option{-mno-shared} depends on binutils 2.16 or higher and generates
++objects that can only be linked by the GNU linker. However, the option
++does not affect the ABI of the final executable; it only affects the ABI
++of relocatable objects. Using @option{-mno-shared} will generally make
++executables both smaller and quicker.
++
++@option{-mshared} is the default.
++
++@item -mplt
++@itemx -mno-plt
++@opindex mplt
++@opindex mno-plt
++Assume (do not assume) that the static and dynamic linkers
++support PLTs and copy relocations. This option only affects
++@samp{-mno-shared -mabicalls}. For the n64 ABI, this option
++has no effect without @samp{-msym32}.
++
++You can make @option{-mplt} the default by configuring
++GCC with @option{--with-mips-plt}. The default is
++@option{-mno-plt} otherwise.
++
++@item -mxgot
++@itemx -mno-xgot
++@opindex mxgot
++@opindex mno-xgot
++Lift (do not lift) the usual restrictions on the size of the global
++offset table.
++
++GCC normally uses a single instruction to load values from the GOT@.
++While this is relatively efficient, it will only work if the GOT
++is smaller than about 64k. Anything larger will cause the linker
++to report an error such as:
++
++@cindex relocation truncated to fit (MIPS)
++@smallexample
++relocation truncated to fit: R_MIPS_GOT16 foobar
++@end smallexample
++
++If this happens, you should recompile your code with @option{-mxgot}.
++It should then work with very large GOTs, although it will also be
++less efficient, since it will take three instructions to fetch the
++value of a global symbol.
++
++Note that some linkers can create multiple GOTs. If you have such a
++linker, you should only need to use @option{-mxgot} when a single object
++file accesses more than 64k's worth of GOT entries. Very few do.
++
++These options have no effect unless GCC is generating position
++independent code.
++
++@item -mgp32
++@opindex mgp32
++Assume that general-purpose registers are 32 bits wide.
++
++@item -mgp64
++@opindex mgp64
++Assume that general-purpose registers are 64 bits wide.
++
++@item -mfp32
++@opindex mfp32
++Assume that floating-point registers are 32 bits wide.
++
++@item -mfp64
++@opindex mfp64
++Assume that floating-point registers are 64 bits wide.
++
++@item -mhard-float
++@opindex mhard-float
++Use floating-point coprocessor instructions.
++
++@item -msoft-float
++@opindex msoft-float
++Do not use floating-point coprocessor instructions. Implement
++floating-point calculations using library calls instead.
++
++@item -msingle-float
++@opindex msingle-float
++Assume that the floating-point coprocessor only supports single-precision
++operations.
++
++@item -mdouble-float
++@opindex mdouble-float
++Assume that the floating-point coprocessor supports double-precision
++operations. This is the default.
++
++@item -mllsc
++@itemx -mno-llsc
++@opindex mllsc
++@opindex mno-llsc
++Use (do not use) @samp{ll}, @samp{sc}, and @samp{sync} instructions to
++implement atomic memory built-in functions. When neither option is
++specified, GCC will use the instructions if the target architecture
++supports them.
++
++@option{-mllsc} is useful if the runtime environment can emulate the
++instructions and @option{-mno-llsc} can be useful when compiling for
++nonstandard ISAs. You can make either option the default by
++configuring GCC with @option{--with-llsc} and @option{--without-llsc}
++respectively. @option{--with-llsc} is the default for some
++configurations; see the installation documentation for details.
++
++@item -mdsp
++@itemx -mno-dsp
++@opindex mdsp
++@opindex mno-dsp
++Use (do not use) revision 1 of the MIPS DSP ASE@.
++@xref{MIPS DSP Built-in Functions}. This option defines the
++preprocessor macro @samp{__mips_dsp}. It also defines
++@samp{__mips_dsp_rev} to 1.
++
++@item -mdspr2
++@itemx -mno-dspr2
++@opindex mdspr2
++@opindex mno-dspr2
++Use (do not use) revision 2 of the MIPS DSP ASE@.
++@xref{MIPS DSP Built-in Functions}. This option defines the
++preprocessor macros @samp{__mips_dsp} and @samp{__mips_dspr2}.
++It also defines @samp{__mips_dsp_rev} to 2.
++
++@item -msmartmips
++@itemx -mno-smartmips
++@opindex msmartmips
++@opindex mno-smartmips
++Use (do not use) the MIPS SmartMIPS ASE.
++
++@item -mpaired-single
++@itemx -mno-paired-single
++@opindex mpaired-single
++@opindex mno-paired-single
++Use (do not use) paired-single floating-point instructions.
++@xref{MIPS Paired-Single Support}. This option requires
++hardware floating-point support to be enabled.
++
++@item -mdmx
++@itemx -mno-mdmx
++@opindex mdmx
++@opindex mno-mdmx
++Use (do not use) MIPS Digital Media Extension instructions.
++This option can only be used when generating 64-bit code and requires
++hardware floating-point support to be enabled.
++
++@item -mips3d
++@itemx -mno-mips3d
++@opindex mips3d
++@opindex mno-mips3d
++Use (do not use) the MIPS-3D ASE@. @xref{MIPS-3D Built-in Functions}.
++The option @option{-mips3d} implies @option{-mpaired-single}.
++
++@item -mmt
++@itemx -mno-mt
++@opindex mmt
++@opindex mno-mt
++Use (do not use) MT Multithreading instructions.
++
++@item -mlong64
++@opindex mlong64
++Force @code{long} types to be 64 bits wide. See @option{-mlong32} for
++an explanation of the default and the way that the pointer size is
++determined.
++
++@item -mlong32
++@opindex mlong32
++Force @code{long}, @code{int}, and pointer types to be 32 bits wide.
++
++The default size of @code{int}s, @code{long}s and pointers depends on
++the ABI@. All the supported ABIs use 32-bit @code{int}s. The n64 ABI
++uses 64-bit @code{long}s, as does the 64-bit EABI; the others use
++32-bit @code{long}s. Pointers are the same size as @code{long}s,
++or the same size as integer registers, whichever is smaller.
++
++@item -msym32
++@itemx -mno-sym32
++@opindex msym32
++@opindex mno-sym32
++Assume (do not assume) that all symbols have 32-bit values, regardless
++of the selected ABI@. This option is useful in combination with
++@option{-mabi=64} and @option{-mno-abicalls} because it allows GCC
++to generate shorter and faster references to symbolic addresses.
++
++@item -G @var{num}
++@opindex G
++Put definitions of externally-visible data in a small data section
++if that data is no bigger than @var{num} bytes. GCC can then access
++the data more efficiently; see @option{-mgpopt} for details.
++
++The default @option{-G} option depends on the configuration.
++
++@item -mlocal-sdata
++@itemx -mno-local-sdata
++@opindex mlocal-sdata
++@opindex mno-local-sdata
++Extend (do not extend) the @option{-G} behavior to local data too,
++such as to static variables in C@. @option{-mlocal-sdata} is the
++default for all configurations.
++
++If the linker complains that an application is using too much small data,
++you might want to try rebuilding the less performance-critical parts with
++@option{-mno-local-sdata}. You might also want to build large
++libraries with @option{-mno-local-sdata}, so that the libraries leave
++more room for the main program.
++
++@item -mextern-sdata
++@itemx -mno-extern-sdata
++@opindex mextern-sdata
++@opindex mno-extern-sdata
++Assume (do not assume) that externally-defined data will be in
++a small data section if that data is within the @option{-G} limit.
++@option{-mextern-sdata} is the default for all configurations.
++
++If you compile a module @var{Mod} with @option{-mextern-sdata} @option{-G
++@var{num}} @option{-mgpopt}, and @var{Mod} references a variable @var{Var}
++that is no bigger than @var{num} bytes, you must make sure that @var{Var}
++is placed in a small data section. If @var{Var} is defined by another
++module, you must either compile that module with a high-enough
++@option{-G} setting or attach a @code{section} attribute to @var{Var}'s
++definition. If @var{Var} is common, you must link the application
++with a high-enough @option{-G} setting.
++
++The easiest way of satisfying these restrictions is to compile
++and link every module with the same @option{-G} option. However,
++you may wish to build a library that supports several different
++small data limits. You can do this by compiling the library with
++the highest supported @option{-G} setting and additionally using
++@option{-mno-extern-sdata} to stop the library from making assumptions
++about externally-defined data.
++
++@item -mgpopt
++@itemx -mno-gpopt
++@opindex mgpopt
++@opindex mno-gpopt
++Use (do not use) GP-relative accesses for symbols that are known to be
++in a small data section; see @option{-G}, @option{-mlocal-sdata} and
++@option{-mextern-sdata}. @option{-mgpopt} is the default for all
++configurations.
++
++@option{-mno-gpopt} is useful for cases where the @code{$gp} register
++might not hold the value of @code{_gp}. For example, if the code is
++part of a library that might be used in a boot monitor, programs that
++call boot monitor routines will pass an unknown value in @code{$gp}.
++(In such situations, the boot monitor itself would usually be compiled
++with @option{-G0}.)
++
++@option{-mno-gpopt} implies @option{-mno-local-sdata} and
++@option{-mno-extern-sdata}.
++
++@item -membedded-data
++@itemx -mno-embedded-data
++@opindex membedded-data
++@opindex mno-embedded-data
++Allocate variables to the read-only data section first if possible, then
++next in the small data section if possible, otherwise in data. This gives
++slightly slower code than the default, but reduces the amount of RAM required
++when executing, and thus may be preferred for some embedded systems.
++
++@item -muninit-const-in-rodata
++@itemx -mno-uninit-const-in-rodata
++@opindex muninit-const-in-rodata
++@opindex mno-uninit-const-in-rodata
++Put uninitialized @code{const} variables in the read-only data section.
++This option is only meaningful in conjunction with @option{-membedded-data}.
++
++@item -mcode-readable=@var{setting}
++@opindex mcode-readable
++Specify whether GCC may generate code that reads from executable sections.
++There are three possible settings:
++
++@table @gcctabopt
++@item -mcode-readable=yes
++Instructions may freely access executable sections. This is the
++default setting.
++
++@item -mcode-readable=pcrel
++MIPS16 PC-relative load instructions can access executable sections,
++but other instructions must not do so. This option is useful on 4KSc
++and 4KSd processors when the code TLBs have the Read Inhibit bit set.
++It is also useful on processors that can be configured to have a dual
++instruction/data SRAM interface and that, like the M4K, automatically
++redirect PC-relative loads to the instruction RAM.
++
++@item -mcode-readable=no
++Instructions must not access executable sections. This option can be
++useful on targets that are configured to have a dual instruction/data
++SRAM interface but that (unlike the M4K) do not automatically redirect
++PC-relative loads to the instruction RAM.
++@end table
++
++@item -msplit-addresses
++@itemx -mno-split-addresses
++@opindex msplit-addresses
++@opindex mno-split-addresses
++Enable (disable) use of the @code{%hi()} and @code{%lo()} assembler
++relocation operators. This option has been superseded by
++@option{-mexplicit-relocs} but is retained for backwards compatibility.
++
++@item -mexplicit-relocs
++@itemx -mno-explicit-relocs
++@opindex mexplicit-relocs
++@opindex mno-explicit-relocs
++Use (do not use) assembler relocation operators when dealing with symbolic
++addresses. The alternative, selected by @option{-mno-explicit-relocs},
++is to use assembler macros instead.
++
++@option{-mexplicit-relocs} is the default if GCC was configured
++to use an assembler that supports relocation operators.
++
++@item -mcheck-zero-division
++@itemx -mno-check-zero-division
++@opindex mcheck-zero-division
++@opindex mno-check-zero-division
++Trap (do not trap) on integer division by zero.
++
++The default is @option{-mcheck-zero-division}.
++
++@item -mdivide-traps
++@itemx -mdivide-breaks
++@opindex mdivide-traps
++@opindex mdivide-breaks
++MIPS systems check for division by zero by generating either a
++conditional trap or a break instruction. Using traps results in
++smaller code, but is only supported on MIPS II and later. Also, some
++versions of the Linux kernel have a bug that prevents trap from
++generating the proper signal (@code{SIGFPE}). Use @option{-mdivide-traps} to
++allow conditional traps on architectures that support them and
++@option{-mdivide-breaks} to force the use of breaks.
++
++The default is usually @option{-mdivide-traps}, but this can be
++overridden at configure time using @option{--with-divide=breaks}.
++Divide-by-zero checks can be completely disabled using
++@option{-mno-check-zero-division}.
++
++@item -mmemcpy
++@itemx -mno-memcpy
++@opindex mmemcpy
++@opindex mno-memcpy
++Force (do not force) the use of @code{memcpy()} for non-trivial block
++moves. The default is @option{-mno-memcpy}, which allows GCC to inline
++most constant-sized copies.
++
++@item -mlong-calls
++@itemx -mno-long-calls
++@opindex mlong-calls
++@opindex mno-long-calls
++Disable (do not disable) use of the @code{jal} instruction. Calling
++functions using @code{jal} is more efficient but requires the caller
++and callee to be in the same 256 megabyte segment.
++
++This option has no effect on abicalls code. The default is
++@option{-mno-long-calls}.
++
++@item -mmad
++@itemx -mno-mad
++@opindex mmad
++@opindex mno-mad
++Enable (disable) use of the @code{mad}, @code{madu} and @code{mul}
++instructions, as provided by the R4650 ISA@.
++
++@item -mfused-madd
++@itemx -mno-fused-madd
++@opindex mfused-madd
++@opindex mno-fused-madd
++Enable (disable) use of the floating point multiply-accumulate
++instructions, when they are available. The default is
++@option{-mfused-madd}.
++
++When multiply-accumulate instructions are used, the intermediate
++product is calculated to infinite precision and is not subject to
++the FCSR Flush to Zero bit. This may be undesirable in some
++circumstances.
++
++@item -nocpp
++@opindex nocpp
++Tell the MIPS assembler to not run its preprocessor over user
++assembler files (with a @samp{.s} suffix) when assembling them.
++
++@item -mfix-r4000
++@itemx -mno-fix-r4000
++@opindex mfix-r4000
++@opindex mno-fix-r4000
++Work around certain R4000 CPU errata:
++@itemize @minus
++@item
++A double-word or a variable shift may give an incorrect result if executed
++immediately after starting an integer division.
++@item
++A double-word or a variable shift may give an incorrect result if executed
++while an integer multiplication is in progress.
++@item
++An integer division may give an incorrect result if started in a delay slot
++of a taken branch or a jump.
++@end itemize
++
++@item -mfix-r4400
++@itemx -mno-fix-r4400
++@opindex mfix-r4400
++@opindex mno-fix-r4400
++Work around certain R4400 CPU errata:
++@itemize @minus
++@item
++A double-word or a variable shift may give an incorrect result if executed
++immediately after starting an integer division.
++@end itemize
++
++@item -mfix-r10000
++@itemx -mno-fix-r10000
++@opindex mfix-r10000
++@opindex mno-fix-r10000
++Work around certain R10000 errata:
++@itemize @minus
++@item
++@code{ll}/@code{sc} sequences may not behave atomically on revisions
++prior to 3.0. They may deadlock on revisions 2.6 and earlier.
++@end itemize
++
++This option can only be used if the target architecture supports
++branch-likely instructions. @option{-mfix-r10000} is the default when
++@option{-march=r10000} is used; @option{-mno-fix-r10000} is the default
++otherwise.
++
++@item -mfix-vr4120
++@itemx -mno-fix-vr4120
++@opindex mfix-vr4120
++Work around certain VR4120 errata:
++@itemize @minus
++@item
++@code{dmultu} does not always produce the correct result.
++@item
++@code{div} and @code{ddiv} do not always produce the correct result if one
++of the operands is negative.
++@end itemize
++The workarounds for the division errata rely on special functions in
++@file{libgcc.a}. At present, these functions are only provided by
++the @code{mips64vr*-elf} configurations.
++
++Other VR4120 errata require a nop to be inserted between certain pairs of
++instructions. These errata are handled by the assembler, not by GCC itself.
++
++@item -mfix-vr4130
++@opindex mfix-vr4130
++Work around the VR4130 @code{mflo}/@code{mfhi} errata. The
++workarounds are implemented by the assembler rather than by GCC,
++although GCC will avoid using @code{mflo} and @code{mfhi} if the
++VR4130 @code{macc}, @code{macchi}, @code{dmacc} and @code{dmacchi}
++instructions are available instead.
++
++@item -mfix-sb1
++@itemx -mno-fix-sb1
++@opindex mfix-sb1
++Work around certain SB-1 CPU core errata.
++(This flag currently works around the SB-1 revision 2
++``F1'' and ``F2'' floating point errata.)
++
++@item -mr10k-cache-barrier=@var{setting}
++@opindex mr10k-cache-barrier
++Specify whether GCC should insert cache barriers to avoid the
++side-effects of speculation on R10K processors.
++
++In common with many processors, the R10K tries to predict the outcome
++of a conditional branch and speculatively executes instructions from
++the ``taken'' branch. It later aborts these instructions if the
++predicted outcome was wrong. However, on the R10K, even aborted
++instructions can have side effects.
++
++This problem only affects kernel stores and, depending on the system,
++kernel loads. As an example, a speculatively-executed store may load
++the target memory into cache and mark the cache line as dirty, even if
++the store itself is later aborted. If a DMA operation writes to the
++same area of memory before the ``dirty'' line is flushed, the cached
++data will overwrite the DMA-ed data. See the R10K processor manual
++for a full description, including other potential problems.
++
++One workaround is to insert cache barrier instructions before every memory
++access that might be speculatively executed and that might have side
++effects even if aborted. @option{-mr10k-cache-barrier=@var{setting}}
++controls GCC's implementation of this workaround. It assumes that
++aborted accesses to any byte in the following regions will not have
++side effects:
++
++@enumerate
++@item
++the memory occupied by the current function's stack frame;
++
++@item
++the memory occupied by an incoming stack argument;
++
++@item
++the memory occupied by an object with a link-time-constant address.
++@end enumerate
++
++It is the kernel's responsibility to ensure that speculative
++accesses to these regions are indeed safe.
++
++If the input program contains a function declaration such as:
++
++@smallexample
++void foo (void);
++@end smallexample
++
++then the implementation of @code{foo} must allow @code{j foo} and
++@code{jal foo} to be executed speculatively. GCC honors this
++restriction for functions it compiles itself. It expects non-GCC
++functions (such as hand-written assembly code) to do the same.
++
++The option has three forms:
++
++@table @gcctabopt
++@item -mr10k-cache-barrier=load-store
++Insert a cache barrier before a load or store that might be
++speculatively executed and that might have side effects even
++if aborted.
++
++@item -mr10k-cache-barrier=store
++Insert a cache barrier before a store that might be speculatively
++executed and that might have side effects even if aborted.
++
++@item -mr10k-cache-barrier=none
++Disable the insertion of cache barriers. This is the default setting.
++@end table
++
++@item -mflush-func=@var{func}
++@itemx -mno-flush-func
++@opindex mflush-func
++Specifies the function to call to flush the I and D caches, or to not
++call any such function. If called, the function must take the same
++arguments as the common @code{_flush_func()}, that is, the address of the
++memory range for which the cache is being flushed, the size of the
++memory range, and the number 3 (to flush both caches). The default
++depends on the target GCC was configured for, but commonly is either
++@samp{_flush_func} or @samp{__cpu_flush}.
++
++@item mbranch-cost=@var{num}
++@opindex mbranch-cost
++Set the cost of branches to roughly @var{num} ``simple'' instructions.
++This cost is only a heuristic and is not guaranteed to produce
++consistent results across releases. A zero cost redundantly selects
++the default, which is based on the @option{-mtune} setting.
++
++@item -mbranch-likely
++@itemx -mno-branch-likely
++@opindex mbranch-likely
++@opindex mno-branch-likely
++Enable or disable use of Branch Likely instructions, regardless of the
++default for the selected architecture. By default, Branch Likely
++instructions may be generated if they are supported by the selected
++architecture. An exception is for the MIPS32 and MIPS64 architectures
++and processors which implement those architectures; for those, Branch
++Likely instructions will not be generated by default because the MIPS32
++and MIPS64 architectures specifically deprecate their use.
++
++@item -mfp-exceptions
++@itemx -mno-fp-exceptions
++@opindex mfp-exceptions
++Specifies whether FP exceptions are enabled. This affects how we schedule
++FP instructions for some processors. The default is that FP exceptions are
++enabled.
++
++For instance, on the SB-1, if FP exceptions are disabled, and we are emitting
++64-bit code, then we can use both FP pipes. Otherwise, we can only use one
++FP pipe.
++
++@item -mvr4130-align
++@itemx -mno-vr4130-align
++@opindex mvr4130-align
++The VR4130 pipeline is two-way superscalar, but can only issue two
++instructions together if the first one is 8-byte aligned. When this
++option is enabled, GCC will align pairs of instructions that it
++thinks should execute in parallel.
++
++This option only has an effect when optimizing for the VR4130.
++It normally makes code faster, but at the expense of making it bigger.
++It is enabled by default at optimization level @option{-O3}.
++@end table
++
++@node MMIX Options
++@subsection MMIX Options
++@cindex MMIX Options
++
++These options are defined for the MMIX:
++
++@table @gcctabopt
++@item -mlibfuncs
++@itemx -mno-libfuncs
++@opindex mlibfuncs
++@opindex mno-libfuncs
++Specify that intrinsic library functions are being compiled, passing all
++values in registers, no matter the size.
++
++@item -mepsilon
++@itemx -mno-epsilon
++@opindex mepsilon
++@opindex mno-epsilon
++Generate floating-point comparison instructions that compare with respect
++to the @code{rE} epsilon register.
++
++@item -mabi=mmixware
++@itemx -mabi=gnu
++@opindex mabi-mmixware
++@opindex mabi=gnu
++Generate code that passes function parameters and return values that (in
++the called function) are seen as registers @code{$0} and up, as opposed to
++the GNU ABI which uses global registers @code{$231} and up.
++
++@item -mzero-extend
++@itemx -mno-zero-extend
++@opindex mzero-extend
++@opindex mno-zero-extend
++When reading data from memory in sizes shorter than 64 bits, use (do not
++use) zero-extending load instructions by default, rather than
++sign-extending ones.
++
++@item -mknuthdiv
++@itemx -mno-knuthdiv
++@opindex mknuthdiv
++@opindex mno-knuthdiv
++Make the result of a division yielding a remainder have the same sign as
++the divisor. With the default, @option{-mno-knuthdiv}, the sign of the
++remainder follows the sign of the dividend. Both methods are
++arithmetically valid, the latter being almost exclusively used.
++
++@item -mtoplevel-symbols
++@itemx -mno-toplevel-symbols
++@opindex mtoplevel-symbols
++@opindex mno-toplevel-symbols
++Prepend (do not prepend) a @samp{:} to all global symbols, so the assembly
++code can be used with the @code{PREFIX} assembly directive.
++
++@item -melf
++@opindex melf
++Generate an executable in the ELF format, rather than the default
++@samp{mmo} format used by the @command{mmix} simulator.
++
++@item -mbranch-predict
++@itemx -mno-branch-predict
++@opindex mbranch-predict
++@opindex mno-branch-predict
++Use (do not use) the probable-branch instructions, when static branch
++prediction indicates a probable branch.
++
++@item -mbase-addresses
++@itemx -mno-base-addresses
++@opindex mbase-addresses
++@opindex mno-base-addresses
++Generate (do not generate) code that uses @emph{base addresses}. Using a
++base address automatically generates a request (handled by the assembler
++and the linker) for a constant to be set up in a global register. The
++register is used for one or more base address requests within the range 0
++to 255 from the value held in the register. The generally leads to short
++and fast code, but the number of different data items that can be
++addressed is limited. This means that a program that uses lots of static
++data may require @option{-mno-base-addresses}.
++
++@item -msingle-exit
++@itemx -mno-single-exit
++@opindex msingle-exit
++@opindex mno-single-exit
++Force (do not force) generated code to have a single exit point in each
++function.
++@end table
++
++@node MN10300 Options
++@subsection MN10300 Options
++@cindex MN10300 options
++
++These @option{-m} options are defined for Matsushita MN10300 architectures:
++
++@table @gcctabopt
++@item -mmult-bug
++@opindex mmult-bug
++Generate code to avoid bugs in the multiply instructions for the MN10300
++processors. This is the default.
++
++@item -mno-mult-bug
++@opindex mno-mult-bug
++Do not generate code to avoid bugs in the multiply instructions for the
++MN10300 processors.
++
++@item -mam33
++@opindex mam33
++Generate code which uses features specific to the AM33 processor.
++
++@item -mno-am33
++@opindex mno-am33
++Do not generate code which uses features specific to the AM33 processor. This
++is the default.
++
++@item -mreturn-pointer-on-d0
++@opindex mreturn-pointer-on-d0
++When generating a function which returns a pointer, return the pointer
++in both @code{a0} and @code{d0}. Otherwise, the pointer is returned
++only in a0, and attempts to call such functions without a prototype
++would result in errors. Note that this option is on by default; use
++@option{-mno-return-pointer-on-d0} to disable it.
++
++@item -mno-crt0
++@opindex mno-crt0
++Do not link in the C run-time initialization object file.
++
++@item -mrelax
++@opindex mrelax
++Indicate to the linker that it should perform a relaxation optimization pass
++to shorten branches, calls and absolute memory addresses. This option only
++has an effect when used on the command line for the final link step.
++
++This option makes symbolic debugging impossible.
++@end table
++
++@node PDP-11 Options
++@subsection PDP-11 Options
++@cindex PDP-11 Options
++
++These options are defined for the PDP-11:
++
++@table @gcctabopt
++@item -mfpu
++@opindex mfpu
++Use hardware FPP floating point. This is the default. (FIS floating
++point on the PDP-11/40 is not supported.)
++
++@item -msoft-float
++@opindex msoft-float
++Do not use hardware floating point.
++
++@item -mac0
++@opindex mac0
++Return floating-point results in ac0 (fr0 in Unix assembler syntax).
++
++@item -mno-ac0
++@opindex mno-ac0
++Return floating-point results in memory. This is the default.
++
++@item -m40
++@opindex m40
++Generate code for a PDP-11/40.
++
++@item -m45
++@opindex m45
++Generate code for a PDP-11/45. This is the default.
++
++@item -m10
++@opindex m10
++Generate code for a PDP-11/10.
++
++@item -mbcopy-builtin
++@opindex bcopy-builtin
++Use inline @code{movmemhi} patterns for copying memory. This is the
++default.
++
++@item -mbcopy
++@opindex mbcopy
++Do not use inline @code{movmemhi} patterns for copying memory.
++
++@item -mint16
++@itemx -mno-int32
++@opindex mint16
++@opindex mno-int32
++Use 16-bit @code{int}. This is the default.
++
++@item -mint32
++@itemx -mno-int16
++@opindex mint32
++@opindex mno-int16
++Use 32-bit @code{int}.
++
++@item -mfloat64
++@itemx -mno-float32
++@opindex mfloat64
++@opindex mno-float32
++Use 64-bit @code{float}. This is the default.
++
++@item -mfloat32
++@itemx -mno-float64
++@opindex mfloat32
++@opindex mno-float64
++Use 32-bit @code{float}.
++
++@item -mabshi
++@opindex mabshi
++Use @code{abshi2} pattern. This is the default.
++
++@item -mno-abshi
++@opindex mno-abshi
++Do not use @code{abshi2} pattern.
++
++@item -mbranch-expensive
++@opindex mbranch-expensive
++Pretend that branches are expensive. This is for experimenting with
++code generation only.
++
++@item -mbranch-cheap
++@opindex mbranch-cheap
++Do not pretend that branches are expensive. This is the default.
++
++@item -msplit
++@opindex msplit
++Generate code for a system with split I&D@.
++
++@item -mno-split
++@opindex mno-split
++Generate code for a system without split I&D@. This is the default.
++
++@item -munix-asm
++@opindex munix-asm
++Use Unix assembler syntax. This is the default when configured for
++@samp{pdp11-*-bsd}.
++
++@item -mdec-asm
++@opindex mdec-asm
++Use DEC assembler syntax. This is the default when configured for any
++PDP-11 target other than @samp{pdp11-*-bsd}.
++@end table
++
++@node picoChip Options
++@subsection picoChip Options
++@cindex picoChip options
++
++These @samp{-m} options are defined for picoChip implementations:
++
++@table @gcctabopt
++
++@item -mae=@var{ae_type}
++@opindex mcpu
++Set the instruction set, register set, and instruction scheduling
++parameters for array element type @var{ae_type}. Supported values
++for @var{ae_type} are @samp{ANY}, @samp{MUL}, and @samp{MAC}.
++
++@option{-mae=ANY} selects a completely generic AE type. Code
++generated with this option will run on any of the other AE types. The
++code will not be as efficient as it would be if compiled for a specific
++AE type, and some types of operation (e.g., multiplication) will not
++work properly on all types of AE.
++
++@option{-mae=MUL} selects a MUL AE type. This is the most useful AE type
++for compiled code, and is the default.
++
++@option{-mae=MAC} selects a DSP-style MAC AE. Code compiled with this
++option may suffer from poor performance of byte (char) manipulation,
++since the DSP AE does not provide hardware support for byte load/stores.
++
++@item -msymbol-as-address
++Enable the compiler to directly use a symbol name as an address in a
++load/store instruction, without first loading it into a
++register. Typically, the use of this option will generate larger
++programs, which run faster than when the option isn't used. However, the
++results vary from program to program, so it is left as a user option,
++rather than being permanently enabled.
++
++@item -mno-inefficient-warnings
++Disables warnings about the generation of inefficient code. These
++warnings can be generated, for example, when compiling code which
++performs byte-level memory operations on the MAC AE type. The MAC AE has
++no hardware support for byte-level memory operations, so all byte
++load/stores must be synthesized from word load/store operations. This is
++inefficient and a warning will be generated indicating to the programmer
++that they should rewrite the code to avoid byte operations, or to target
++an AE type which has the necessary hardware support. This option enables
++the warning to be turned off.
++
++@end table
++
++@node PowerPC Options
++@subsection PowerPC Options
++@cindex PowerPC options
++
++These are listed under @xref{RS/6000 and PowerPC Options}.
++
++@node RS/6000 and PowerPC Options
++@subsection IBM RS/6000 and PowerPC Options
++@cindex RS/6000 and PowerPC Options
++@cindex IBM RS/6000 and PowerPC Options
++
++These @samp{-m} options are defined for the IBM RS/6000 and PowerPC:
++@table @gcctabopt
++@item -mpower
++@itemx -mno-power
++@itemx -mpower2
++@itemx -mno-power2
++@itemx -mpowerpc
++@itemx -mno-powerpc
++@itemx -mpowerpc-gpopt
++@itemx -mno-powerpc-gpopt
++@itemx -mpowerpc-gfxopt
++@itemx -mno-powerpc-gfxopt
++@itemx -mpowerpc64
++@itemx -mno-powerpc64
++@itemx -mmfcrf
++@itemx -mno-mfcrf
++@itemx -mpopcntb
++@itemx -mno-popcntb
++@itemx -mfprnd
++@itemx -mno-fprnd
++@itemx -mcmpb
++@itemx -mno-cmpb
++@itemx -mmfpgpr
++@itemx -mno-mfpgpr
++@itemx -mhard-dfp
++@itemx -mno-hard-dfp
++@opindex mpower
++@opindex mno-power
++@opindex mpower2
++@opindex mno-power2
++@opindex mpowerpc
++@opindex mno-powerpc
++@opindex mpowerpc-gpopt
++@opindex mno-powerpc-gpopt
++@opindex mpowerpc-gfxopt
++@opindex mno-powerpc-gfxopt
++@opindex mpowerpc64
++@opindex mno-powerpc64
++@opindex mmfcrf
++@opindex mno-mfcrf
++@opindex mpopcntb
++@opindex mno-popcntb
++@opindex mfprnd
++@opindex mno-fprnd
++@opindex mcmpb
++@opindex mno-cmpb
++@opindex mmfpgpr
++@opindex mno-mfpgpr
++@opindex mhard-dfp
++@opindex mno-hard-dfp
++GCC supports two related instruction set architectures for the
++RS/6000 and PowerPC@. The @dfn{POWER} instruction set are those
++instructions supported by the @samp{rios} chip set used in the original
++RS/6000 systems and the @dfn{PowerPC} instruction set is the
++architecture of the Freescale MPC5xx, MPC6xx, MPC8xx microprocessors, and
++the IBM 4xx, 6xx, and follow-on microprocessors.
++
++Neither architecture is a subset of the other. However there is a
++large common subset of instructions supported by both. An MQ
++register is included in processors supporting the POWER architecture.
++
++You use these options to specify which instructions are available on the
++processor you are using. The default value of these options is
++determined when configuring GCC@. Specifying the
++@option{-mcpu=@var{cpu_type}} overrides the specification of these
++options. We recommend you use the @option{-mcpu=@var{cpu_type}} option
++rather than the options listed above.
++
++The @option{-mpower} option allows GCC to generate instructions that
++are found only in the POWER architecture and to use the MQ register.
++Specifying @option{-mpower2} implies @option{-power} and also allows GCC
++to generate instructions that are present in the POWER2 architecture but
++not the original POWER architecture.
++
++The @option{-mpowerpc} option allows GCC to generate instructions that
++are found only in the 32-bit subset of the PowerPC architecture.
++Specifying @option{-mpowerpc-gpopt} implies @option{-mpowerpc} and also allows
++GCC to use the optional PowerPC architecture instructions in the
++General Purpose group, including floating-point square root. Specifying
++@option{-mpowerpc-gfxopt} implies @option{-mpowerpc} and also allows GCC to
++use the optional PowerPC architecture instructions in the Graphics
++group, including floating-point select.
++
++The @option{-mmfcrf} option allows GCC to generate the move from
++condition register field instruction implemented on the POWER4
++processor and other processors that support the PowerPC V2.01
++architecture.
++The @option{-mpopcntb} option allows GCC to generate the popcount and
++double precision FP reciprocal estimate instruction implemented on the
++POWER5 processor and other processors that support the PowerPC V2.02
++architecture.
++The @option{-mfprnd} option allows GCC to generate the FP round to
++integer instructions implemented on the POWER5+ processor and other
++processors that support the PowerPC V2.03 architecture.
++The @option{-mcmpb} option allows GCC to generate the compare bytes
++instruction implemented on the POWER6 processor and other processors
++that support the PowerPC V2.05 architecture.
++The @option{-mmfpgpr} option allows GCC to generate the FP move to/from
++general purpose register instructions implemented on the POWER6X
++processor and other processors that support the extended PowerPC V2.05
++architecture.
++The @option{-mhard-dfp} option allows GCC to generate the decimal floating
++point instructions implemented on some POWER processors.
++
++The @option{-mpowerpc64} option allows GCC to generate the additional
++64-bit instructions that are found in the full PowerPC64 architecture
++and to treat GPRs as 64-bit, doubleword quantities. GCC defaults to
++@option{-mno-powerpc64}.
++
++If you specify both @option{-mno-power} and @option{-mno-powerpc}, GCC
++will use only the instructions in the common subset of both
++architectures plus some special AIX common-mode calls, and will not use
++the MQ register. Specifying both @option{-mpower} and @option{-mpowerpc}
++permits GCC to use any instruction from either architecture and to
++allow use of the MQ register; specify this for the Motorola MPC601.
++
++@item -mnew-mnemonics
++@itemx -mold-mnemonics
++@opindex mnew-mnemonics
++@opindex mold-mnemonics
++Select which mnemonics to use in the generated assembler code. With
++@option{-mnew-mnemonics}, GCC uses the assembler mnemonics defined for
++the PowerPC architecture. With @option{-mold-mnemonics} it uses the
++assembler mnemonics defined for the POWER architecture. Instructions
++defined in only one architecture have only one mnemonic; GCC uses that
++mnemonic irrespective of which of these options is specified.
++
++GCC defaults to the mnemonics appropriate for the architecture in
++use. Specifying @option{-mcpu=@var{cpu_type}} sometimes overrides the
++value of these option. Unless you are building a cross-compiler, you
++should normally not specify either @option{-mnew-mnemonics} or
++@option{-mold-mnemonics}, but should instead accept the default.
++
++@item -mcpu=@var{cpu_type}
++@opindex mcpu
++Set architecture type, register usage, choice of mnemonics, and
++instruction scheduling parameters for machine type @var{cpu_type}.
++Supported values for @var{cpu_type} are @samp{401}, @samp{403},
++@samp{405}, @samp{405fp}, @samp{440}, @samp{440fp}, @samp{464}, @samp{464fp},
++@samp{505}, @samp{601}, @samp{602}, @samp{603}, @samp{603e}, @samp{604},
++@samp{604e}, @samp{620}, @samp{630}, @samp{740}, @samp{7400},
++@samp{7450}, @samp{750}, @samp{801}, @samp{821}, @samp{823},
++@samp{860}, @samp{970}, @samp{8540}, @samp{e300c2}, @samp{e300c3},
++@samp{e500mc}, @samp{ec603e}, @samp{G3}, @samp{G4}, @samp{G5},
++@samp{power}, @samp{power2}, @samp{power3}, @samp{power4},
++@samp{power5}, @samp{power5+}, @samp{power6}, @samp{power6x}, @samp{power7}
++@samp{common}, @samp{powerpc}, @samp{powerpc64}, @samp{rios},
++@samp{rios1}, @samp{rios2}, @samp{rsc}, and @samp{rs64}.
++
++@option{-mcpu=common} selects a completely generic processor. Code
++generated under this option will run on any POWER or PowerPC processor.
++GCC will use only the instructions in the common subset of both
++architectures, and will not use the MQ register. GCC assumes a generic
++processor model for scheduling purposes.
++
++@option{-mcpu=power}, @option{-mcpu=power2}, @option{-mcpu=powerpc}, and
++@option{-mcpu=powerpc64} specify generic POWER, POWER2, pure 32-bit
++PowerPC (i.e., not MPC601), and 64-bit PowerPC architecture machine
++types, with an appropriate, generic processor model assumed for
++scheduling purposes.
++
++The other options specify a specific processor. Code generated under
++those options will run best on that processor, and may not run at all on
++others.
++
++The @option{-mcpu} options automatically enable or disable the
++following options:
++
++@gccoptlist{-maltivec -mfprnd -mhard-float -mmfcrf -mmultiple @gol
++-mnew-mnemonics -mpopcntb -mpower -mpower2 -mpowerpc64 @gol
++-mpowerpc-gpopt -mpowerpc-gfxopt -msingle-float -mdouble-float @gol
++-msimple-fpu -mstring -mmulhw -mdlmzb -mmfpgpr}
++
++The particular options set for any particular CPU will vary between
++compiler versions, depending on what setting seems to produce optimal
++code for that CPU; it doesn't necessarily reflect the actual hardware's
++capabilities. If you wish to set an individual option to a particular
++value, you may specify it after the @option{-mcpu} option, like
++@samp{-mcpu=970 -mno-altivec}.
++
++On AIX, the @option{-maltivec} and @option{-mpowerpc64} options are
++not enabled or disabled by the @option{-mcpu} option at present because
++AIX does not have full support for these options. You may still
++enable or disable them individually if you're sure it'll work in your
++environment.
++
++@item -mtune=@var{cpu_type}
++@opindex mtune
++Set the instruction scheduling parameters for machine type
++@var{cpu_type}, but do not set the architecture type, register usage, or
++choice of mnemonics, as @option{-mcpu=@var{cpu_type}} would. The same
++values for @var{cpu_type} are used for @option{-mtune} as for
++@option{-mcpu}. If both are specified, the code generated will use the
++architecture, registers, and mnemonics set by @option{-mcpu}, but the
++scheduling parameters set by @option{-mtune}.
++
++@item -mswdiv
++@itemx -mno-swdiv
++@opindex mswdiv
++@opindex mno-swdiv
++Generate code to compute division as reciprocal estimate and iterative
++refinement, creating opportunities for increased throughput. This
++feature requires: optional PowerPC Graphics instruction set for single
++precision and FRE instruction for double precision, assuming divides
++cannot generate user-visible traps, and the domain values not include
++Infinities, denormals or zero denominator.
++
++@item -maltivec
++@itemx -mno-altivec
++@opindex maltivec
++@opindex mno-altivec
++Generate code that uses (does not use) AltiVec instructions, and also
++enable the use of built-in functions that allow more direct access to
++the AltiVec instruction set. You may also need to set
++@option{-mabi=altivec} to adjust the current ABI with AltiVec ABI
++enhancements.
++
++@item -mvrsave
++@itemx -mno-vrsave
++@opindex mvrsave
++@opindex mno-vrsave
++Generate VRSAVE instructions when generating AltiVec code.
++
++@item -mgen-cell-microcode
++@opindex mgen-cell-microcode
++Generate Cell microcode instructions
++
++@item -mwarn-cell-microcode
++@opindex mwarn-cell-microcode
++Warning when a Cell microcode instruction is going to emitted. An example
++of a Cell microcode instruction is a variable shift.
++
++@item -msecure-plt
++@opindex msecure-plt
++Generate code that allows ld and ld.so to build executables and shared
++libraries with non-exec .plt and .got sections. This is a PowerPC
++32-bit SYSV ABI option.
++
++@item -mbss-plt
++@opindex mbss-plt
++Generate code that uses a BSS .plt section that ld.so fills in, and
++requires .plt and .got sections that are both writable and executable.
++This is a PowerPC 32-bit SYSV ABI option.
++
++@item -misel
++@itemx -mno-isel
++@opindex misel
++@opindex mno-isel
++This switch enables or disables the generation of ISEL instructions.
++
++@item -misel=@var{yes/no}
++This switch has been deprecated. Use @option{-misel} and
++@option{-mno-isel} instead.
++
++@item -mspe
++@itemx -mno-spe
++@opindex mspe
++@opindex mno-spe
++This switch enables or disables the generation of SPE simd
++instructions.
++
++@item -mpaired
++@itemx -mno-paired
++@opindex mpaired
++@opindex mno-paired
++This switch enables or disables the generation of PAIRED simd
++instructions.
++
++@item -mspe=@var{yes/no}
++This option has been deprecated. Use @option{-mspe} and
++@option{-mno-spe} instead.
++
++@item -mfloat-gprs=@var{yes/single/double/no}
++@itemx -mfloat-gprs
++@opindex mfloat-gprs
++This switch enables or disables the generation of floating point
++operations on the general purpose registers for architectures that
++support it.
++
++The argument @var{yes} or @var{single} enables the use of
++single-precision floating point operations.
++
++The argument @var{double} enables the use of single and
++double-precision floating point operations.
++
++The argument @var{no} disables floating point operations on the
++general purpose registers.
++
++This option is currently only available on the MPC854x.
++
++@item -m32
++@itemx -m64
++@opindex m32
++@opindex m64
++Generate code for 32-bit or 64-bit environments of Darwin and SVR4
++targets (including GNU/Linux). The 32-bit environment sets int, long
++and pointer to 32 bits and generates code that runs on any PowerPC
++variant. The 64-bit environment sets int to 32 bits and long and
++pointer to 64 bits, and generates code for PowerPC64, as for
++@option{-mpowerpc64}.
++
++@item -mfull-toc
++@itemx -mno-fp-in-toc
++@itemx -mno-sum-in-toc
++@itemx -mminimal-toc
++@opindex mfull-toc
++@opindex mno-fp-in-toc
++@opindex mno-sum-in-toc
++@opindex mminimal-toc
++Modify generation of the TOC (Table Of Contents), which is created for
++every executable file. The @option{-mfull-toc} option is selected by
++default. In that case, GCC will allocate at least one TOC entry for
++each unique non-automatic variable reference in your program. GCC
++will also place floating-point constants in the TOC@. However, only
++16,384 entries are available in the TOC@.
++
++If you receive a linker error message that saying you have overflowed
++the available TOC space, you can reduce the amount of TOC space used
++with the @option{-mno-fp-in-toc} and @option{-mno-sum-in-toc} options.
++@option{-mno-fp-in-toc} prevents GCC from putting floating-point
++constants in the TOC and @option{-mno-sum-in-toc} forces GCC to
++generate code to calculate the sum of an address and a constant at
++run-time instead of putting that sum into the TOC@. You may specify one
++or both of these options. Each causes GCC to produce very slightly
++slower and larger code at the expense of conserving TOC space.
++
++If you still run out of space in the TOC even when you specify both of
++these options, specify @option{-mminimal-toc} instead. This option causes
++GCC to make only one TOC entry for every file. When you specify this
++option, GCC will produce code that is slower and larger but which
++uses extremely little TOC space. You may wish to use this option
++only on files that contain less frequently executed code.
++
++@item -maix64
++@itemx -maix32
++@opindex maix64
++@opindex maix32
++Enable 64-bit AIX ABI and calling convention: 64-bit pointers, 64-bit
++@code{long} type, and the infrastructure needed to support them.
++Specifying @option{-maix64} implies @option{-mpowerpc64} and
++@option{-mpowerpc}, while @option{-maix32} disables the 64-bit ABI and
++implies @option{-mno-powerpc64}. GCC defaults to @option{-maix32}.
++
++@item -mxl-compat
++@itemx -mno-xl-compat
++@opindex mxl-compat
++@opindex mno-xl-compat
++Produce code that conforms more closely to IBM XL compiler semantics
++when using AIX-compatible ABI@. Pass floating-point arguments to
++prototyped functions beyond the register save area (RSA) on the stack
++in addition to argument FPRs. Do not assume that most significant
++double in 128-bit long double value is properly rounded when comparing
++values and converting to double. Use XL symbol names for long double
++support routines.
++
++The AIX calling convention was extended but not initially documented to
++handle an obscure K&R C case of calling a function that takes the
++address of its arguments with fewer arguments than declared. IBM XL
++compilers access floating point arguments which do not fit in the
++RSA from the stack when a subroutine is compiled without
++optimization. Because always storing floating-point arguments on the
++stack is inefficient and rarely needed, this option is not enabled by
++default and only is necessary when calling subroutines compiled by IBM
++XL compilers without optimization.
++
++@item -mpe
++@opindex mpe
++Support @dfn{IBM RS/6000 SP} @dfn{Parallel Environment} (PE)@. Link an
++application written to use message passing with special startup code to
++enable the application to run. The system must have PE installed in the
++standard location (@file{/usr/lpp/ppe.poe/}), or the @file{specs} file
++must be overridden with the @option{-specs=} option to specify the
++appropriate directory location. The Parallel Environment does not
++support threads, so the @option{-mpe} option and the @option{-pthread}
++option are incompatible.
++
++@item -malign-natural
++@itemx -malign-power
++@opindex malign-natural
++@opindex malign-power
++On AIX, 32-bit Darwin, and 64-bit PowerPC GNU/Linux, the option
++@option{-malign-natural} overrides the ABI-defined alignment of larger
++types, such as floating-point doubles, on their natural size-based boundary.
++The option @option{-malign-power} instructs GCC to follow the ABI-specified
++alignment rules. GCC defaults to the standard alignment defined in the ABI@.
++
++On 64-bit Darwin, natural alignment is the default, and @option{-malign-power}
++is not supported.
++
++@item -msoft-float
++@itemx -mhard-float
++@opindex msoft-float
++@opindex mhard-float
++Generate code that does not use (uses) the floating-point register set.
++Software floating point emulation is provided if you use the
++@option{-msoft-float} option, and pass the option to GCC when linking.
++
++@item -msingle-float
++@itemx -mdouble-float
++@opindex msingle-float
++@opindex mdouble-float
++Generate code for single or double-precision floating point operations.
++@option{-mdouble-float} implies @option{-msingle-float}.
++
++@item -msimple-fpu
++@opindex msimple-fpu
++Do not generate sqrt and div instructions for hardware floating point unit.
++
++@item -mfpu
++@opindex mfpu
++Specify type of floating point unit. Valid values are @var{sp_lite}
++(equivalent to -msingle-float -msimple-fpu), @var{dp_lite} (equivalent
++to -mdouble-float -msimple-fpu), @var{sp_full} (equivalent to -msingle-float),
++and @var{dp_full} (equivalent to -mdouble-float).
++
++@item -mxilinx-fpu
++@opindex mxilinx-fpu
++Perform optimizations for floating point unit on Xilinx PPC 405/440.
++
++@item -mmultiple
++@itemx -mno-multiple
++@opindex mmultiple
++@opindex mno-multiple
++Generate code that uses (does not use) the load multiple word
++instructions and the store multiple word instructions. These
++instructions are generated by default on POWER systems, and not
++generated on PowerPC systems. Do not use @option{-mmultiple} on little
++endian PowerPC systems, since those instructions do not work when the
++processor is in little endian mode. The exceptions are PPC740 and
++PPC750 which permit the instructions usage in little endian mode.
++
++@item -mstring
++@itemx -mno-string
++@opindex mstring
++@opindex mno-string
++Generate code that uses (does not use) the load string instructions
++and the store string word instructions to save multiple registers and
++do small block moves. These instructions are generated by default on
++POWER systems, and not generated on PowerPC systems. Do not use
++@option{-mstring} on little endian PowerPC systems, since those
++instructions do not work when the processor is in little endian mode.
++The exceptions are PPC740 and PPC750 which permit the instructions
++usage in little endian mode.
++
++@item -mupdate
++@itemx -mno-update
++@opindex mupdate
++@opindex mno-update
++Generate code that uses (does not use) the load or store instructions
++that update the base register to the address of the calculated memory
++location. These instructions are generated by default. If you use
++@option{-mno-update}, there is a small window between the time that the
++stack pointer is updated and the address of the previous frame is
++stored, which means code that walks the stack frame across interrupts or
++signals may get corrupted data.
++
++@item -mavoid-indexed-addresses
++@item -mno-avoid-indexed-addresses
++@opindex mavoid-indexed-addresses
++@opindex mno-avoid-indexed-addresses
++Generate code that tries to avoid (not avoid) the use of indexed load
++or store instructions. These instructions can incur a performance
++penalty on Power6 processors in certain situations, such as when
++stepping through large arrays that cross a 16M boundary. This option
++is enabled by default when targetting Power6 and disabled otherwise.
++
++@item -mfused-madd
++@itemx -mno-fused-madd
++@opindex mfused-madd
++@opindex mno-fused-madd
++Generate code that uses (does not use) the floating point multiply and
++accumulate instructions. These instructions are generated by default if
++hardware floating is used.
++
++@item -mmulhw
++@itemx -mno-mulhw
++@opindex mmulhw
++@opindex mno-mulhw
++Generate code that uses (does not use) the half-word multiply and
++multiply-accumulate instructions on the IBM 405, 440 and 464 processors.
++These instructions are generated by default when targetting those
++processors.
++
++@item -mdlmzb
++@itemx -mno-dlmzb
++@opindex mdlmzb
++@opindex mno-dlmzb
++Generate code that uses (does not use) the string-search @samp{dlmzb}
++instruction on the IBM 405, 440 and 464 processors. This instruction is
++generated by default when targetting those processors.
++
++@item -mno-bit-align
++@itemx -mbit-align
++@opindex mno-bit-align
++@opindex mbit-align
++On System V.4 and embedded PowerPC systems do not (do) force structures
++and unions that contain bit-fields to be aligned to the base type of the
++bit-field.
++
++For example, by default a structure containing nothing but 8
++@code{unsigned} bit-fields of length 1 would be aligned to a 4 byte
++boundary and have a size of 4 bytes. By using @option{-mno-bit-align},
++the structure would be aligned to a 1 byte boundary and be one byte in
++size.
++
++@item -mno-strict-align
++@itemx -mstrict-align
++@opindex mno-strict-align
++@opindex mstrict-align
++On System V.4 and embedded PowerPC systems do not (do) assume that
++unaligned memory references will be handled by the system.
++
++@item -mrelocatable
++@itemx -mno-relocatable
++@opindex mrelocatable
++@opindex mno-relocatable
++On embedded PowerPC systems generate code that allows (does not allow)
++the program to be relocated to a different address at runtime. If you
++use @option{-mrelocatable} on any module, all objects linked together must
++be compiled with @option{-mrelocatable} or @option{-mrelocatable-lib}.
++
++@item -mrelocatable-lib
++@itemx -mno-relocatable-lib
++@opindex mrelocatable-lib
++@opindex mno-relocatable-lib
++On embedded PowerPC systems generate code that allows (does not allow)
++the program to be relocated to a different address at runtime. Modules
++compiled with @option{-mrelocatable-lib} can be linked with either modules
++compiled without @option{-mrelocatable} and @option{-mrelocatable-lib} or
++with modules compiled with the @option{-mrelocatable} options.
++
++@item -mno-toc
++@itemx -mtoc
++@opindex mno-toc
++@opindex mtoc
++On System V.4 and embedded PowerPC systems do not (do) assume that
++register 2 contains a pointer to a global area pointing to the addresses
++used in the program.
++
++@item -mlittle
++@itemx -mlittle-endian
++@opindex mlittle
++@opindex mlittle-endian
++On System V.4 and embedded PowerPC systems compile code for the
++processor in little endian mode. The @option{-mlittle-endian} option is
++the same as @option{-mlittle}.
++
++@item -mbig
++@itemx -mbig-endian
++@opindex mbig
++@opindex mbig-endian
++On System V.4 and embedded PowerPC systems compile code for the
++processor in big endian mode. The @option{-mbig-endian} option is
++the same as @option{-mbig}.
++
++@item -mdynamic-no-pic
++@opindex mdynamic-no-pic
++On Darwin and Mac OS X systems, compile code so that it is not
++relocatable, but that its external references are relocatable. The
++resulting code is suitable for applications, but not shared
++libraries.
++
++@item -mprioritize-restricted-insns=@var{priority}
++@opindex mprioritize-restricted-insns
++This option controls the priority that is assigned to
++dispatch-slot restricted instructions during the second scheduling
++pass. The argument @var{priority} takes the value @var{0/1/2} to assign
++@var{no/highest/second-highest} priority to dispatch slot restricted
++instructions.
++
++@item -msched-costly-dep=@var{dependence_type}
++@opindex msched-costly-dep
++This option controls which dependences are considered costly
++by the target during instruction scheduling. The argument
++@var{dependence_type} takes one of the following values:
++@var{no}: no dependence is costly,
++@var{all}: all dependences are costly,
++@var{true_store_to_load}: a true dependence from store to load is costly,
++@var{store_to_load}: any dependence from store to load is costly,
++@var{number}: any dependence which latency >= @var{number} is costly.
++
++@item -minsert-sched-nops=@var{scheme}
++@opindex minsert-sched-nops
++This option controls which nop insertion scheme will be used during
++the second scheduling pass. The argument @var{scheme} takes one of the
++following values:
++@var{no}: Don't insert nops.
++@var{pad}: Pad with nops any dispatch group which has vacant issue slots,
++according to the scheduler's grouping.
++@var{regroup_exact}: Insert nops to force costly dependent insns into
++separate groups. Insert exactly as many nops as needed to force an insn
++to a new group, according to the estimated processor grouping.
++@var{number}: Insert nops to force costly dependent insns into
++separate groups. Insert @var{number} nops to force an insn to a new group.
++
++@item -mcall-sysv
++@opindex mcall-sysv
++On System V.4 and embedded PowerPC systems compile code using calling
++conventions that adheres to the March 1995 draft of the System V
++Application Binary Interface, PowerPC processor supplement. This is the
++default unless you configured GCC using @samp{powerpc-*-eabiaix}.
++
++@item -mcall-sysv-eabi
++@opindex mcall-sysv-eabi
++Specify both @option{-mcall-sysv} and @option{-meabi} options.
++
++@item -mcall-sysv-noeabi
++@opindex mcall-sysv-noeabi
++Specify both @option{-mcall-sysv} and @option{-mno-eabi} options.
++
++@item -mcall-solaris
++@opindex mcall-solaris
++On System V.4 and embedded PowerPC systems compile code for the Solaris
++operating system.
++
++@item -mcall-linux
++@opindex mcall-linux
++On System V.4 and embedded PowerPC systems compile code for the
++Linux-based GNU system.
++
++@item -mcall-gnu
++@opindex mcall-gnu
++On System V.4 and embedded PowerPC systems compile code for the
++Hurd-based GNU system.
++
++@item -mcall-netbsd
++@opindex mcall-netbsd
++On System V.4 and embedded PowerPC systems compile code for the
++NetBSD operating system.
++
++@item -maix-struct-return
++@opindex maix-struct-return
++Return all structures in memory (as specified by the AIX ABI)@.
++
++@item -msvr4-struct-return
++@opindex msvr4-struct-return
++Return structures smaller than 8 bytes in registers (as specified by the
++SVR4 ABI)@.
++
++@item -mabi=@var{abi-type}
++@opindex mabi
++Extend the current ABI with a particular extension, or remove such extension.
++Valid values are @var{altivec}, @var{no-altivec}, @var{spe},
++@var{no-spe}, @var{ibmlongdouble}, @var{ieeelongdouble}@.
++
++@item -mabi=spe
++@opindex mabi=spe
++Extend the current ABI with SPE ABI extensions. This does not change
++the default ABI, instead it adds the SPE ABI extensions to the current
++ABI@.
++
++@item -mabi=no-spe
++@opindex mabi=no-spe
++Disable Booke SPE ABI extensions for the current ABI@.
++
++@item -mabi=ibmlongdouble
++@opindex mabi=ibmlongdouble
++Change the current ABI to use IBM extended precision long double.
++This is a PowerPC 32-bit SYSV ABI option.
++
++@item -mabi=ieeelongdouble
++@opindex mabi=ieeelongdouble
++Change the current ABI to use IEEE extended precision long double.
++This is a PowerPC 32-bit Linux ABI option.
++
++@item -mprototype
++@itemx -mno-prototype
++@opindex mprototype
++@opindex mno-prototype
++On System V.4 and embedded PowerPC systems assume that all calls to
++variable argument functions are properly prototyped. Otherwise, the
++compiler must insert an instruction before every non prototyped call to
++set or clear bit 6 of the condition code register (@var{CR}) to
++indicate whether floating point values were passed in the floating point
++registers in case the function takes a variable arguments. With
++@option{-mprototype}, only calls to prototyped variable argument functions
++will set or clear the bit.
++
++@item -msim
++@opindex msim
++On embedded PowerPC systems, assume that the startup module is called
++@file{sim-crt0.o} and that the standard C libraries are @file{libsim.a} and
++@file{libc.a}. This is the default for @samp{powerpc-*-eabisim}
++configurations.
++
++@item -mmvme
++@opindex mmvme
++On embedded PowerPC systems, assume that the startup module is called
++@file{crt0.o} and the standard C libraries are @file{libmvme.a} and
++@file{libc.a}.
++
++@item -mads
++@opindex mads
++On embedded PowerPC systems, assume that the startup module is called
++@file{crt0.o} and the standard C libraries are @file{libads.a} and
++@file{libc.a}.
++
++@item -myellowknife
++@opindex myellowknife
++On embedded PowerPC systems, assume that the startup module is called
++@file{crt0.o} and the standard C libraries are @file{libyk.a} and
++@file{libc.a}.
++
++@item -mvxworks
++@opindex mvxworks
++On System V.4 and embedded PowerPC systems, specify that you are
++compiling for a VxWorks system.
++
++@item -memb
++@opindex memb
++On embedded PowerPC systems, set the @var{PPC_EMB} bit in the ELF flags
++header to indicate that @samp{eabi} extended relocations are used.
++
++@item -meabi
++@itemx -mno-eabi
++@opindex meabi
++@opindex mno-eabi
++On System V.4 and embedded PowerPC systems do (do not) adhere to the
++Embedded Applications Binary Interface (eabi) which is a set of
++modifications to the System V.4 specifications. Selecting @option{-meabi}
++means that the stack is aligned to an 8 byte boundary, a function
++@code{__eabi} is called to from @code{main} to set up the eabi
++environment, and the @option{-msdata} option can use both @code{r2} and
++@code{r13} to point to two separate small data areas. Selecting
++@option{-mno-eabi} means that the stack is aligned to a 16 byte boundary,
++do not call an initialization function from @code{main}, and the
++@option{-msdata} option will only use @code{r13} to point to a single
++small data area. The @option{-meabi} option is on by default if you
++configured GCC using one of the @samp{powerpc*-*-eabi*} options.
++
++@item -msdata=eabi
++@opindex msdata=eabi
++On System V.4 and embedded PowerPC systems, put small initialized
++@code{const} global and static data in the @samp{.sdata2} section, which
++is pointed to by register @code{r2}. Put small initialized
++non-@code{const} global and static data in the @samp{.sdata} section,
++which is pointed to by register @code{r13}. Put small uninitialized
++global and static data in the @samp{.sbss} section, which is adjacent to
++the @samp{.sdata} section. The @option{-msdata=eabi} option is
++incompatible with the @option{-mrelocatable} option. The
++@option{-msdata=eabi} option also sets the @option{-memb} option.
++
++@item -msdata=sysv
++@opindex msdata=sysv
++On System V.4 and embedded PowerPC systems, put small global and static
++data in the @samp{.sdata} section, which is pointed to by register
++@code{r13}. Put small uninitialized global and static data in the
++@samp{.sbss} section, which is adjacent to the @samp{.sdata} section.
++The @option{-msdata=sysv} option is incompatible with the
++@option{-mrelocatable} option.
++
++@item -msdata=default
++@itemx -msdata
++@opindex msdata=default
++@opindex msdata
++On System V.4 and embedded PowerPC systems, if @option{-meabi} is used,
++compile code the same as @option{-msdata=eabi}, otherwise compile code the
++same as @option{-msdata=sysv}.
++
++@item -msdata=data
++@opindex msdata=data
++On System V.4 and embedded PowerPC systems, put small global
++data in the @samp{.sdata} section. Put small uninitialized global
++data in the @samp{.sbss} section. Do not use register @code{r13}
++to address small data however. This is the default behavior unless
++other @option{-msdata} options are used.
++
++@item -msdata=none
++@itemx -mno-sdata
++@opindex msdata=none
++@opindex mno-sdata
++On embedded PowerPC systems, put all initialized global and static data
++in the @samp{.data} section, and all uninitialized data in the
++@samp{.bss} section.
++
++@item -G @var{num}
++@opindex G
++@cindex smaller data references (PowerPC)
++@cindex .sdata/.sdata2 references (PowerPC)
++On embedded PowerPC systems, put global and static items less than or
++equal to @var{num} bytes into the small data or bss sections instead of
++the normal data or bss section. By default, @var{num} is 8. The
++@option{-G @var{num}} switch is also passed to the linker.
++All modules should be compiled with the same @option{-G @var{num}} value.
++
++@item -mregnames
++@itemx -mno-regnames
++@opindex mregnames
++@opindex mno-regnames
++On System V.4 and embedded PowerPC systems do (do not) emit register
++names in the assembly language output using symbolic forms.
++
++@item -mlongcall
++@itemx -mno-longcall
++@opindex mlongcall
++@opindex mno-longcall
++By default assume that all calls are far away so that a longer more
++expensive calling sequence is required. This is required for calls
++further than 32 megabytes (33,554,432 bytes) from the current location.
++A short call will be generated if the compiler knows
++the call cannot be that far away. This setting can be overridden by
++the @code{shortcall} function attribute, or by @code{#pragma
++longcall(0)}.
++
++Some linkers are capable of detecting out-of-range calls and generating
++glue code on the fly. On these systems, long calls are unnecessary and
++generate slower code. As of this writing, the AIX linker can do this,
++as can the GNU linker for PowerPC/64. It is planned to add this feature
++to the GNU linker for 32-bit PowerPC systems as well.
++
++On Darwin/PPC systems, @code{#pragma longcall} will generate ``jbsr
++callee, L42'', plus a ``branch island'' (glue code). The two target
++addresses represent the callee and the ``branch island''. The
++Darwin/PPC linker will prefer the first address and generate a ``bl
++callee'' if the PPC ``bl'' instruction will reach the callee directly;
++otherwise, the linker will generate ``bl L42'' to call the ``branch
++island''. The ``branch island'' is appended to the body of the
++calling function; it computes the full 32-bit address of the callee
++and jumps to it.
++
++On Mach-O (Darwin) systems, this option directs the compiler emit to
++the glue for every direct call, and the Darwin linker decides whether
++to use or discard it.
++
++In the future, we may cause GCC to ignore all longcall specifications
++when the linker is known to generate glue.
++
++@item -pthread
++@opindex pthread
++Adds support for multithreading with the @dfn{pthreads} library.
++This option sets flags for both the preprocessor and linker.
++
++@end table
++
++@node S/390 and zSeries Options
++@subsection S/390 and zSeries Options
++@cindex S/390 and zSeries Options
++
++These are the @samp{-m} options defined for the S/390 and zSeries architecture.
++
++@table @gcctabopt
++@item -mhard-float
++@itemx -msoft-float
++@opindex mhard-float
++@opindex msoft-float
++Use (do not use) the hardware floating-point instructions and registers
++for floating-point operations. When @option{-msoft-float} is specified,
++functions in @file{libgcc.a} will be used to perform floating-point
++operations. When @option{-mhard-float} is specified, the compiler
++generates IEEE floating-point instructions. This is the default.
++
++@item -mhard-dfp
++@itemx -mno-hard-dfp
++@opindex mhard-dfp
++@opindex mno-hard-dfp
++Use (do not use) the hardware decimal-floating-point instructions for
++decimal-floating-point operations. When @option{-mno-hard-dfp} is
++specified, functions in @file{libgcc.a} will be used to perform
++decimal-floating-point operations. When @option{-mhard-dfp} is
++specified, the compiler generates decimal-floating-point hardware
++instructions. This is the default for @option{-march=z9-ec} or higher.
++
++@item -mlong-double-64
++@itemx -mlong-double-128
++@opindex mlong-double-64
++@opindex mlong-double-128
++These switches control the size of @code{long double} type. A size
++of 64bit makes the @code{long double} type equivalent to the @code{double}
++type. This is the default.
++
++@item -mbackchain
++@itemx -mno-backchain
++@opindex mbackchain
++@opindex mno-backchain
++Store (do not store) the address of the caller's frame as backchain pointer
++into the callee's stack frame.
++A backchain may be needed to allow debugging using tools that do not understand
++DWARF-2 call frame information.
++When @option{-mno-packed-stack} is in effect, the backchain pointer is stored
++at the bottom of the stack frame; when @option{-mpacked-stack} is in effect,
++the backchain is placed into the topmost word of the 96/160 byte register
++save area.
++
++In general, code compiled with @option{-mbackchain} is call-compatible with
++code compiled with @option{-mmo-backchain}; however, use of the backchain
++for debugging purposes usually requires that the whole binary is built with
++@option{-mbackchain}. Note that the combination of @option{-mbackchain},
++@option{-mpacked-stack} and @option{-mhard-float} is not supported. In order
++to build a linux kernel use @option{-msoft-float}.
++
++The default is to not maintain the backchain.
++
++@item -mpacked-stack
++@itemx -mno-packed-stack
++@opindex mpacked-stack
++@opindex mno-packed-stack
++Use (do not use) the packed stack layout. When @option{-mno-packed-stack} is
++specified, the compiler uses the all fields of the 96/160 byte register save
++area only for their default purpose; unused fields still take up stack space.
++When @option{-mpacked-stack} is specified, register save slots are densely
++packed at the top of the register save area; unused space is reused for other
++purposes, allowing for more efficient use of the available stack space.
++However, when @option{-mbackchain} is also in effect, the topmost word of
++the save area is always used to store the backchain, and the return address
++register is always saved two words below the backchain.
++
++As long as the stack frame backchain is not used, code generated with
++@option{-mpacked-stack} is call-compatible with code generated with
++@option{-mno-packed-stack}. Note that some non-FSF releases of GCC 2.95 for
++S/390 or zSeries generated code that uses the stack frame backchain at run
++time, not just for debugging purposes. Such code is not call-compatible
++with code compiled with @option{-mpacked-stack}. Also, note that the
++combination of @option{-mbackchain},
++@option{-mpacked-stack} and @option{-mhard-float} is not supported. In order
++to build a linux kernel use @option{-msoft-float}.
++
++The default is to not use the packed stack layout.
++
++@item -msmall-exec
++@itemx -mno-small-exec
++@opindex msmall-exec
++@opindex mno-small-exec
++Generate (or do not generate) code using the @code{bras} instruction
++to do subroutine calls.
++This only works reliably if the total executable size does not
++exceed 64k. The default is to use the @code{basr} instruction instead,
++which does not have this limitation.
++
++@item -m64
++@itemx -m31
++@opindex m64
++@opindex m31
++When @option{-m31} is specified, generate code compliant to the
++GNU/Linux for S/390 ABI@. When @option{-m64} is specified, generate
++code compliant to the GNU/Linux for zSeries ABI@. This allows GCC in
++particular to generate 64-bit instructions. For the @samp{s390}
++targets, the default is @option{-m31}, while the @samp{s390x}
++targets default to @option{-m64}.
++
++@item -mzarch
++@itemx -mesa
++@opindex mzarch
++@opindex mesa
++When @option{-mzarch} is specified, generate code using the
++instructions available on z/Architecture.
++When @option{-mesa} is specified, generate code using the
++instructions available on ESA/390. Note that @option{-mesa} is
++not possible with @option{-m64}.
++When generating code compliant to the GNU/Linux for S/390 ABI,
++the default is @option{-mesa}. When generating code compliant
++to the GNU/Linux for zSeries ABI, the default is @option{-mzarch}.
++
++@item -mmvcle
++@itemx -mno-mvcle
++@opindex mmvcle
++@opindex mno-mvcle
++Generate (or do not generate) code using the @code{mvcle} instruction
++to perform block moves. When @option{-mno-mvcle} is specified,
++use a @code{mvc} loop instead. This is the default unless optimizing for
++size.
++
++@item -mdebug
++@itemx -mno-debug
++@opindex mdebug
++@opindex mno-debug
++Print (or do not print) additional debug information when compiling.
++The default is to not print debug information.
++
++@item -march=@var{cpu-type}
++@opindex march
++Generate code that will run on @var{cpu-type}, which is the name of a system
++representing a certain processor type. Possible values for
++@var{cpu-type} are @samp{g5}, @samp{g6}, @samp{z900}, @samp{z990},
++@samp{z9-109}, @samp{z9-ec} and @samp{z10}.
++When generating code using the instructions available on z/Architecture,
++the default is @option{-march=z900}. Otherwise, the default is
++@option{-march=g5}.
++
++@item -mtune=@var{cpu-type}
++@opindex mtune
++Tune to @var{cpu-type} everything applicable about the generated code,
++except for the ABI and the set of available instructions.
++The list of @var{cpu-type} values is the same as for @option{-march}.
++The default is the value used for @option{-march}.
++
++@item -mtpf-trace
++@itemx -mno-tpf-trace
++@opindex mtpf-trace
++@opindex mno-tpf-trace
++Generate code that adds (does not add) in TPF OS specific branches to trace
++routines in the operating system. This option is off by default, even
++when compiling for the TPF OS@.
++
++@item -mfused-madd
++@itemx -mno-fused-madd
++@opindex mfused-madd
++@opindex mno-fused-madd
++Generate code that uses (does not use) the floating point multiply and
++accumulate instructions. These instructions are generated by default if
++hardware floating point is used.
++
++@item -mwarn-framesize=@var{framesize}
++@opindex mwarn-framesize
++Emit a warning if the current function exceeds the given frame size. Because
++this is a compile time check it doesn't need to be a real problem when the program
++runs. It is intended to identify functions which most probably cause
++a stack overflow. It is useful to be used in an environment with limited stack
++size e.g.@: the linux kernel.
++
++@item -mwarn-dynamicstack
++@opindex mwarn-dynamicstack
++Emit a warning if the function calls alloca or uses dynamically
++sized arrays. This is generally a bad idea with a limited stack size.
++
++@item -mstack-guard=@var{stack-guard}
++@itemx -mstack-size=@var{stack-size}
++@opindex mstack-guard
++@opindex mstack-size
++If these options are provided the s390 back end emits additional instructions in
++the function prologue which trigger a trap if the stack size is @var{stack-guard}
++bytes above the @var{stack-size} (remember that the stack on s390 grows downward).
++If the @var{stack-guard} option is omitted the smallest power of 2 larger than
++the frame size of the compiled function is chosen.
++These options are intended to be used to help debugging stack overflow problems.
++The additionally emitted code causes only little overhead and hence can also be
++used in production like systems without greater performance degradation. The given
++values have to be exact powers of 2 and @var{stack-size} has to be greater than
++@var{stack-guard} without exceeding 64k.
++In order to be efficient the extra code makes the assumption that the stack starts
++at an address aligned to the value given by @var{stack-size}.
++The @var{stack-guard} option can only be used in conjunction with @var{stack-size}.
++@end table
++
++@node Score Options
++@subsection Score Options
++@cindex Score Options
++
++These options are defined for Score implementations:
++
++@table @gcctabopt
++@item -meb
++@opindex meb
++Compile code for big endian mode. This is the default.
++
++@item -mel
++@opindex mel
++Compile code for little endian mode.
++
++@item -mnhwloop
++@opindex mnhwloop
++Disable generate bcnz instruction.
++
++@item -muls
++@opindex muls
++Enable generate unaligned load and store instruction.
++
++@item -mmac
++@opindex mmac
++Enable the use of multiply-accumulate instructions. Disabled by default.
++
++@item -mscore5
++@opindex mscore5
++Specify the SCORE5 as the target architecture.
++
++@item -mscore5u
++@opindex mscore5u
++Specify the SCORE5U of the target architecture.
++
++@item -mscore7
++@opindex mscore7
++Specify the SCORE7 as the target architecture. This is the default.
++
++@item -mscore7d
++@opindex mscore7d
++Specify the SCORE7D as the target architecture.
++@end table
++
++@node SH Options
++@subsection SH Options
++
++These @samp{-m} options are defined for the SH implementations:
++
++@table @gcctabopt
++@item -m1
++@opindex m1
++Generate code for the SH1.
++
++@item -m2
++@opindex m2
++Generate code for the SH2.
++
++@item -m2e
++Generate code for the SH2e.
++
++@item -m3
++@opindex m3
++Generate code for the SH3.
++
++@item -m3e
++@opindex m3e
++Generate code for the SH3e.
++
++@item -m4-nofpu
++@opindex m4-nofpu
++Generate code for the SH4 without a floating-point unit.
++
++@item -m4-single-only
++@opindex m4-single-only
++Generate code for the SH4 with a floating-point unit that only
++supports single-precision arithmetic.
++
++@item -m4-single
++@opindex m4-single
++Generate code for the SH4 assuming the floating-point unit is in
++single-precision mode by default.
++
++@item -m4
++@opindex m4
++Generate code for the SH4.
++
++@item -m4a-nofpu
++@opindex m4a-nofpu
++Generate code for the SH4al-dsp, or for a SH4a in such a way that the
++floating-point unit is not used.
++
++@item -m4a-single-only
++@opindex m4a-single-only
++Generate code for the SH4a, in such a way that no double-precision
++floating point operations are used.
++
++@item -m4a-single
++@opindex m4a-single
++Generate code for the SH4a assuming the floating-point unit is in
++single-precision mode by default.
++
++@item -m4a
++@opindex m4a
++Generate code for the SH4a.
++
++@item -m4al
++@opindex m4al
++Same as @option{-m4a-nofpu}, except that it implicitly passes
++@option{-dsp} to the assembler. GCC doesn't generate any DSP
++instructions at the moment.
++
++@item -mb
++@opindex mb
++Compile code for the processor in big endian mode.
++
++@item -ml
++@opindex ml
++Compile code for the processor in little endian mode.
++
++@item -mdalign
++@opindex mdalign
++Align doubles at 64-bit boundaries. Note that this changes the calling
++conventions, and thus some functions from the standard C library will
++not work unless you recompile it first with @option{-mdalign}.
++
++@item -mrelax
++@opindex mrelax
++Shorten some address references at link time, when possible; uses the
++linker option @option{-relax}.
++
++@item -mbigtable
++@opindex mbigtable
++Use 32-bit offsets in @code{switch} tables. The default is to use
++16-bit offsets.
++
++@item -mbitops
++@opindex mbitops
++Enable the use of bit manipulation instructions on SH2A.
++
++@item -mfmovd
++@opindex mfmovd
++Enable the use of the instruction @code{fmovd}.
++
++@item -mhitachi
++@opindex mhitachi
++Comply with the calling conventions defined by Renesas.
++
++@item -mrenesas
++@opindex mhitachi
++Comply with the calling conventions defined by Renesas.
++
++@item -mno-renesas
++@opindex mhitachi
++Comply with the calling conventions defined for GCC before the Renesas
++conventions were available. This option is the default for all
++targets of the SH toolchain except for @samp{sh-symbianelf}.
++
++@item -mnomacsave
++@opindex mnomacsave
++Mark the @code{MAC} register as call-clobbered, even if
++@option{-mhitachi} is given.
++
++@item -mieee
++@opindex mieee
++Increase IEEE-compliance of floating-point code.
++At the moment, this is equivalent to @option{-fno-finite-math-only}.
++When generating 16 bit SH opcodes, getting IEEE-conforming results for
++comparisons of NANs / infinities incurs extra overhead in every
++floating point comparison, therefore the default is set to
++@option{-ffinite-math-only}.
++
++@item -minline-ic_invalidate
++@opindex minline-ic_invalidate
++Inline code to invalidate instruction cache entries after setting up
++nested function trampolines.
++This option has no effect if -musermode is in effect and the selected
++code generation option (e.g. -m4) does not allow the use of the icbi
++instruction.
++If the selected code generation option does not allow the use of the icbi
++instruction, and -musermode is not in effect, the inlined code will
++manipulate the instruction cache address array directly with an associative
++write. This not only requires privileged mode, but it will also
++fail if the cache line had been mapped via the TLB and has become unmapped.
++
++@item -misize
++@opindex misize
++Dump instruction size and location in the assembly code.
++
++@item -mpadstruct
++@opindex mpadstruct
++This option is deprecated. It pads structures to multiple of 4 bytes,
++which is incompatible with the SH ABI@.
++
++@item -mspace
++@opindex mspace
++Optimize for space instead of speed. Implied by @option{-Os}.
++
++@item -mprefergot
++@opindex mprefergot
++When generating position-independent code, emit function calls using
++the Global Offset Table instead of the Procedure Linkage Table.
++
++@item -musermode
++@opindex musermode
++Don't generate privileged mode only code; implies -mno-inline-ic_invalidate
++if the inlined code would not work in user mode.
++This is the default when the target is @code{sh-*-linux*}.
++
++@item -multcost=@var{number}
++@opindex multcost=@var{number}
++Set the cost to assume for a multiply insn.
++
++@item -mdiv=@var{strategy}
++@opindex mdiv=@var{strategy}
++Set the division strategy to use for SHmedia code. @var{strategy} must be
++one of: call, call2, fp, inv, inv:minlat, inv20u, inv20l, inv:call,
++inv:call2, inv:fp .
++"fp" performs the operation in floating point. This has a very high latency,
++but needs only a few instructions, so it might be a good choice if
++your code has enough easily exploitable ILP to allow the compiler to
++schedule the floating point instructions together with other instructions.
++Division by zero causes a floating point exception.
++"inv" uses integer operations to calculate the inverse of the divisor,
++and then multiplies the dividend with the inverse. This strategy allows
++cse and hoisting of the inverse calculation. Division by zero calculates
++an unspecified result, but does not trap.
++"inv:minlat" is a variant of "inv" where if no cse / hoisting opportunities
++have been found, or if the entire operation has been hoisted to the same
++place, the last stages of the inverse calculation are intertwined with the
++final multiply to reduce the overall latency, at the expense of using a few
++more instructions, and thus offering fewer scheduling opportunities with
++other code.
++"call" calls a library function that usually implements the inv:minlat
++strategy.
++This gives high code density for m5-*media-nofpu compilations.
++"call2" uses a different entry point of the same library function, where it
++assumes that a pointer to a lookup table has already been set up, which
++exposes the pointer load to cse / code hoisting optimizations.
++"inv:call", "inv:call2" and "inv:fp" all use the "inv" algorithm for initial
++code generation, but if the code stays unoptimized, revert to the "call",
++"call2", or "fp" strategies, respectively. Note that the
++potentially-trapping side effect of division by zero is carried by a
++separate instruction, so it is possible that all the integer instructions
++are hoisted out, but the marker for the side effect stays where it is.
++A recombination to fp operations or a call is not possible in that case.
++"inv20u" and "inv20l" are variants of the "inv:minlat" strategy. In the case
++that the inverse calculation was nor separated from the multiply, they speed
++up division where the dividend fits into 20 bits (plus sign where applicable),
++by inserting a test to skip a number of operations in this case; this test
++slows down the case of larger dividends. inv20u assumes the case of a such
++a small dividend to be unlikely, and inv20l assumes it to be likely.
++
++@item -mdivsi3_libfunc=@var{name}
++@opindex mdivsi3_libfunc=@var{name}
++Set the name of the library function used for 32 bit signed division to
++@var{name}. This only affect the name used in the call and inv:call
++division strategies, and the compiler will still expect the same
++sets of input/output/clobbered registers as if this option was not present.
++
++@item -mfixed-range=@var{register-range}
++@opindex mfixed-range
++Generate code treating the given register range as fixed registers.
++A fixed register is one that the register allocator can not use. This is
++useful when compiling kernel code. A register range is specified as
++two registers separated by a dash. Multiple register ranges can be
++specified separated by a comma.
++
++@item -madjust-unroll
++@opindex madjust-unroll
++Throttle unrolling to avoid thrashing target registers.
++This option only has an effect if the gcc code base supports the
++TARGET_ADJUST_UNROLL_MAX target hook.
++
++@item -mindexed-addressing
++@opindex mindexed-addressing
++Enable the use of the indexed addressing mode for SHmedia32/SHcompact.
++This is only safe if the hardware and/or OS implement 32 bit wrap-around
++semantics for the indexed addressing mode. The architecture allows the
++implementation of processors with 64 bit MMU, which the OS could use to
++get 32 bit addressing, but since no current hardware implementation supports
++this or any other way to make the indexed addressing mode safe to use in
++the 32 bit ABI, the default is -mno-indexed-addressing.
++
++@item -mgettrcost=@var{number}
++@opindex mgettrcost=@var{number}
++Set the cost assumed for the gettr instruction to @var{number}.
++The default is 2 if @option{-mpt-fixed} is in effect, 100 otherwise.
++
++@item -mpt-fixed
++@opindex mpt-fixed
++Assume pt* instructions won't trap. This will generally generate better
++scheduled code, but is unsafe on current hardware. The current architecture
++definition says that ptabs and ptrel trap when the target anded with 3 is 3.
++This has the unintentional effect of making it unsafe to schedule ptabs /
++ptrel before a branch, or hoist it out of a loop. For example,
++__do_global_ctors, a part of libgcc that runs constructors at program
++startup, calls functions in a list which is delimited by @minus{}1. With the
++-mpt-fixed option, the ptabs will be done before testing against @minus{}1.
++That means that all the constructors will be run a bit quicker, but when
++the loop comes to the end of the list, the program crashes because ptabs
++loads @minus{}1 into a target register. Since this option is unsafe for any
++hardware implementing the current architecture specification, the default
++is -mno-pt-fixed. Unless the user specifies a specific cost with
++@option{-mgettrcost}, -mno-pt-fixed also implies @option{-mgettrcost=100};
++this deters register allocation using target registers for storing
++ordinary integers.
++
++@item -minvalid-symbols
++@opindex minvalid-symbols
++Assume symbols might be invalid. Ordinary function symbols generated by
++the compiler will always be valid to load with movi/shori/ptabs or
++movi/shori/ptrel, but with assembler and/or linker tricks it is possible
++to generate symbols that will cause ptabs / ptrel to trap.
++This option is only meaningful when @option{-mno-pt-fixed} is in effect.
++It will then prevent cross-basic-block cse, hoisting and most scheduling
++of symbol loads. The default is @option{-mno-invalid-symbols}.
++@end table
++
++@node SPARC Options
++@subsection SPARC Options
++@cindex SPARC options
++
++These @samp{-m} options are supported on the SPARC:
++
++@table @gcctabopt
++@item -mno-app-regs
++@itemx -mapp-regs
++@opindex mno-app-regs
++@opindex mapp-regs
++Specify @option{-mapp-regs} to generate output using the global registers
++2 through 4, which the SPARC SVR4 ABI reserves for applications. This
++is the default.
++
++To be fully SVR4 ABI compliant at the cost of some performance loss,
++specify @option{-mno-app-regs}. You should compile libraries and system
++software with this option.
++
++@item -mfpu
++@itemx -mhard-float
++@opindex mfpu
++@opindex mhard-float
++Generate output containing floating point instructions. This is the
++default.
++
++@item -mno-fpu
++@itemx -msoft-float
++@opindex mno-fpu
++@opindex msoft-float
++Generate output containing library calls for floating point.
++@strong{Warning:} the requisite libraries are not available for all SPARC
++targets. Normally the facilities of the machine's usual C compiler are
++used, but this cannot be done directly in cross-compilation. You must make
++your own arrangements to provide suitable library functions for
++cross-compilation. The embedded targets @samp{sparc-*-aout} and
++@samp{sparclite-*-*} do provide software floating point support.
++
++@option{-msoft-float} changes the calling convention in the output file;
++therefore, it is only useful if you compile @emph{all} of a program with
++this option. In particular, you need to compile @file{libgcc.a}, the
++library that comes with GCC, with @option{-msoft-float} in order for
++this to work.
++
++@item -mhard-quad-float
++@opindex mhard-quad-float
++Generate output containing quad-word (long double) floating point
++instructions.
++
++@item -msoft-quad-float
++@opindex msoft-quad-float
++Generate output containing library calls for quad-word (long double)
++floating point instructions. The functions called are those specified
++in the SPARC ABI@. This is the default.
++
++As of this writing, there are no SPARC implementations that have hardware
++support for the quad-word floating point instructions. They all invoke
++a trap handler for one of these instructions, and then the trap handler
++emulates the effect of the instruction. Because of the trap handler overhead,
++this is much slower than calling the ABI library routines. Thus the
++@option{-msoft-quad-float} option is the default.
++
++@item -mno-unaligned-doubles
++@itemx -munaligned-doubles
++@opindex mno-unaligned-doubles
++@opindex munaligned-doubles
++Assume that doubles have 8 byte alignment. This is the default.
++
++With @option{-munaligned-doubles}, GCC assumes that doubles have 8 byte
++alignment only if they are contained in another type, or if they have an
++absolute address. Otherwise, it assumes they have 4 byte alignment.
++Specifying this option avoids some rare compatibility problems with code
++generated by other compilers. It is not the default because it results
++in a performance loss, especially for floating point code.
++
++@item -mno-faster-structs
++@itemx -mfaster-structs
++@opindex mno-faster-structs
++@opindex mfaster-structs
++With @option{-mfaster-structs}, the compiler assumes that structures
++should have 8 byte alignment. This enables the use of pairs of
++@code{ldd} and @code{std} instructions for copies in structure
++assignment, in place of twice as many @code{ld} and @code{st} pairs.
++However, the use of this changed alignment directly violates the SPARC
++ABI@. Thus, it's intended only for use on targets where the developer
++acknowledges that their resulting code will not be directly in line with
++the rules of the ABI@.
++
++@item -mimpure-text
++@opindex mimpure-text
++@option{-mimpure-text}, used in addition to @option{-shared}, tells
++the compiler to not pass @option{-z text} to the linker when linking a
++shared object. Using this option, you can link position-dependent
++code into a shared object.
++
++@option{-mimpure-text} suppresses the ``relocations remain against
++allocatable but non-writable sections'' linker error message.
++However, the necessary relocations will trigger copy-on-write, and the
++shared object is not actually shared across processes. Instead of
++using @option{-mimpure-text}, you should compile all source code with
++@option{-fpic} or @option{-fPIC}.
++
++This option is only available on SunOS and Solaris.
++
++@item -mcpu=@var{cpu_type}
++@opindex mcpu
++Set the instruction set, register set, and instruction scheduling parameters
++for machine type @var{cpu_type}. Supported values for @var{cpu_type} are
++@samp{v7}, @samp{cypress}, @samp{v8}, @samp{supersparc}, @samp{sparclite},
++@samp{f930}, @samp{f934}, @samp{hypersparc}, @samp{sparclite86x},
++@samp{sparclet}, @samp{tsc701}, @samp{v9}, @samp{ultrasparc},
++@samp{ultrasparc3}, @samp{niagara} and @samp{niagara2}.
++
++Default instruction scheduling parameters are used for values that select
++an architecture and not an implementation. These are @samp{v7}, @samp{v8},
++@samp{sparclite}, @samp{sparclet}, @samp{v9}.
++
++Here is a list of each supported architecture and their supported
++implementations.
++
++@smallexample
++ v7: cypress
++ v8: supersparc, hypersparc
++ sparclite: f930, f934, sparclite86x
++ sparclet: tsc701
++ v9: ultrasparc, ultrasparc3, niagara, niagara2
++@end smallexample
++
++By default (unless configured otherwise), GCC generates code for the V7
++variant of the SPARC architecture. With @option{-mcpu=cypress}, the compiler
++additionally optimizes it for the Cypress CY7C602 chip, as used in the
++SPARCStation/SPARCServer 3xx series. This is also appropriate for the older
++SPARCStation 1, 2, IPX etc.
++
++With @option{-mcpu=v8}, GCC generates code for the V8 variant of the SPARC
++architecture. The only difference from V7 code is that the compiler emits
++the integer multiply and integer divide instructions which exist in SPARC-V8
++but not in SPARC-V7. With @option{-mcpu=supersparc}, the compiler additionally
++optimizes it for the SuperSPARC chip, as used in the SPARCStation 10, 1000 and
++2000 series.
++
++With @option{-mcpu=sparclite}, GCC generates code for the SPARClite variant of
++the SPARC architecture. This adds the integer multiply, integer divide step
++and scan (@code{ffs}) instructions which exist in SPARClite but not in SPARC-V7.
++With @option{-mcpu=f930}, the compiler additionally optimizes it for the
++Fujitsu MB86930 chip, which is the original SPARClite, with no FPU@. With
++@option{-mcpu=f934}, the compiler additionally optimizes it for the Fujitsu
++MB86934 chip, which is the more recent SPARClite with FPU@.
++
++With @option{-mcpu=sparclet}, GCC generates code for the SPARClet variant of
++the SPARC architecture. This adds the integer multiply, multiply/accumulate,
++integer divide step and scan (@code{ffs}) instructions which exist in SPARClet
++but not in SPARC-V7. With @option{-mcpu=tsc701}, the compiler additionally
++optimizes it for the TEMIC SPARClet chip.
++
++With @option{-mcpu=v9}, GCC generates code for the V9 variant of the SPARC
++architecture. This adds 64-bit integer and floating-point move instructions,
++3 additional floating-point condition code registers and conditional move
++instructions. With @option{-mcpu=ultrasparc}, the compiler additionally
++optimizes it for the Sun UltraSPARC I/II/IIi chips. With
++@option{-mcpu=ultrasparc3}, the compiler additionally optimizes it for the
++Sun UltraSPARC III/III+/IIIi/IIIi+/IV/IV+ chips. With
++@option{-mcpu=niagara}, the compiler additionally optimizes it for
++Sun UltraSPARC T1 chips. With @option{-mcpu=niagara2}, the compiler
++additionally optimizes it for Sun UltraSPARC T2 chips.
++
++@item -mtune=@var{cpu_type}
++@opindex mtune
++Set the instruction scheduling parameters for machine type
++@var{cpu_type}, but do not set the instruction set or register set that the
++option @option{-mcpu=@var{cpu_type}} would.
++
++The same values for @option{-mcpu=@var{cpu_type}} can be used for
++@option{-mtune=@var{cpu_type}}, but the only useful values are those
++that select a particular cpu implementation. Those are @samp{cypress},
++@samp{supersparc}, @samp{hypersparc}, @samp{f930}, @samp{f934},
++@samp{sparclite86x}, @samp{tsc701}, @samp{ultrasparc},
++@samp{ultrasparc3}, @samp{niagara}, and @samp{niagara2}.
++
++@item -mv8plus
++@itemx -mno-v8plus
++@opindex mv8plus
++@opindex mno-v8plus
++With @option{-mv8plus}, GCC generates code for the SPARC-V8+ ABI@. The
++difference from the V8 ABI is that the global and out registers are
++considered 64-bit wide. This is enabled by default on Solaris in 32-bit
++mode for all SPARC-V9 processors.
++
++@item -mvis
++@itemx -mno-vis
++@opindex mvis
++@opindex mno-vis
++With @option{-mvis}, GCC generates code that takes advantage of the UltraSPARC
++Visual Instruction Set extensions. The default is @option{-mno-vis}.
++@end table
++
++These @samp{-m} options are supported in addition to the above
++on SPARC-V9 processors in 64-bit environments:
++
++@table @gcctabopt
++@item -mlittle-endian
++@opindex mlittle-endian
++Generate code for a processor running in little-endian mode. It is only
++available for a few configurations and most notably not on Solaris and Linux.
++
++@item -m32
++@itemx -m64
++@opindex m32
++@opindex m64
++Generate code for a 32-bit or 64-bit environment.
++The 32-bit environment sets int, long and pointer to 32 bits.
++The 64-bit environment sets int to 32 bits and long and pointer
++to 64 bits.
++
++@item -mcmodel=medlow
++@opindex mcmodel=medlow
++Generate code for the Medium/Low code model: 64-bit addresses, programs
++must be linked in the low 32 bits of memory. Programs can be statically
++or dynamically linked.
++
++@item -mcmodel=medmid
++@opindex mcmodel=medmid
++Generate code for the Medium/Middle code model: 64-bit addresses, programs
++must be linked in the low 44 bits of memory, the text and data segments must
++be less than 2GB in size and the data segment must be located within 2GB of
++the text segment.
++
++@item -mcmodel=medany
++@opindex mcmodel=medany
++Generate code for the Medium/Anywhere code model: 64-bit addresses, programs
++may be linked anywhere in memory, the text and data segments must be less
++than 2GB in size and the data segment must be located within 2GB of the
++text segment.
++
++@item -mcmodel=embmedany
++@opindex mcmodel=embmedany
++Generate code for the Medium/Anywhere code model for embedded systems:
++64-bit addresses, the text and data segments must be less than 2GB in
++size, both starting anywhere in memory (determined at link time). The
++global register %g4 points to the base of the data segment. Programs
++are statically linked and PIC is not supported.
++
++@item -mstack-bias
++@itemx -mno-stack-bias
++@opindex mstack-bias
++@opindex mno-stack-bias
++With @option{-mstack-bias}, GCC assumes that the stack pointer, and
++frame pointer if present, are offset by @minus{}2047 which must be added back
++when making stack frame references. This is the default in 64-bit mode.
++Otherwise, assume no such offset is present.
++@end table
++
++These switches are supported in addition to the above on Solaris:
++
++@table @gcctabopt
++@item -threads
++@opindex threads
++Add support for multithreading using the Solaris threads library. This
++option sets flags for both the preprocessor and linker. This option does
++not affect the thread safety of object code produced by the compiler or
++that of libraries supplied with it.
++
++@item -pthreads
++@opindex pthreads
++Add support for multithreading using the POSIX threads library. This
++option sets flags for both the preprocessor and linker. This option does
++not affect the thread safety of object code produced by the compiler or
++that of libraries supplied with it.
++
++@item -pthread
++@opindex pthread
++This is a synonym for @option{-pthreads}.
++@end table
++
++@node SPU Options
++@subsection SPU Options
++@cindex SPU options
++
++These @samp{-m} options are supported on the SPU:
++
++@table @gcctabopt
++@item -mwarn-reloc
++@itemx -merror-reloc
++@opindex mwarn-reloc
++@opindex merror-reloc
++
++The loader for SPU does not handle dynamic relocations. By default, GCC
++will give an error when it generates code that requires a dynamic
++relocation. @option{-mno-error-reloc} disables the error,
++@option{-mwarn-reloc} will generate a warning instead.
++
++@item -msafe-dma
++@itemx -munsafe-dma
++@opindex msafe-dma
++@opindex munsafe-dma
++
++Instructions which initiate or test completion of DMA must not be
++reordered with respect to loads and stores of the memory which is being
++accessed. Users typically address this problem using the volatile
++keyword, but that can lead to inefficient code in places where the
++memory is known to not change. Rather than mark the memory as volatile
++we treat the DMA instructions as potentially effecting all memory. With
++@option{-munsafe-dma} users must use the volatile keyword to protect
++memory accesses.
++
++@item -mbranch-hints
++@opindex mbranch-hints
++
++By default, GCC will generate a branch hint instruction to avoid
++pipeline stalls for always taken or probably taken branches. A hint
++will not be generated closer than 8 instructions away from its branch.
++There is little reason to disable them, except for debugging purposes,
++or to make an object a little bit smaller.
++
++@item -msmall-mem
++@itemx -mlarge-mem
++@opindex msmall-mem
++@opindex mlarge-mem
++
++By default, GCC generates code assuming that addresses are never larger
++than 18 bits. With @option{-mlarge-mem} code is generated that assumes
++a full 32 bit address.
++
++@item -mstdmain
++@opindex mstdmain
++
++By default, GCC links against startup code that assumes the SPU-style
++main function interface (which has an unconventional parameter list).
++With @option{-mstdmain}, GCC will link your program against startup
++code that assumes a C99-style interface to @code{main}, including a
++local copy of @code{argv} strings.
++
++@item -mfixed-range=@var{register-range}
++@opindex mfixed-range
++Generate code treating the given register range as fixed registers.
++A fixed register is one that the register allocator can not use. This is
++useful when compiling kernel code. A register range is specified as
++two registers separated by a dash. Multiple register ranges can be
++specified separated by a comma.
++
++@item -mdual-nops
++@itemx -mdual-nops=@var{n}
++@opindex mdual-nops
++By default, GCC will insert nops to increase dual issue when it expects
++it to increase performance. @var{n} can be a value from 0 to 10. A
++smaller @var{n} will insert fewer nops. 10 is the default, 0 is the
++same as @option{-mno-dual-nops}. Disabled with @option{-Os}.
++
++@item -mhint-max-nops=@var{n}
++@opindex mhint-max-nops
++Maximum number of nops to insert for a branch hint. A branch hint must
++be at least 8 instructions away from the branch it is effecting. GCC
++will insert up to @var{n} nops to enforce this, otherwise it will not
++generate the branch hint.
++
++@item -mhint-max-distance=@var{n}
++@opindex mhint-max-distance
++The encoding of the branch hint instruction limits the hint to be within
++256 instructions of the branch it is effecting. By default, GCC makes
++sure it is within 125.
++
++@item -msafe-hints
++@opindex msafe-hints
++Work around a hardware bug which causes the SPU to stall indefinitely.
++By default, GCC will insert the @code{hbrp} instruction to make sure
++this stall won't happen.
++
++@end table
++
++@node System V Options
++@subsection Options for System V
++
++These additional options are available on System V Release 4 for
++compatibility with other compilers on those systems:
++
++@table @gcctabopt
++@item -G
++@opindex G
++Create a shared object.
++It is recommended that @option{-symbolic} or @option{-shared} be used instead.
++
++@item -Qy
++@opindex Qy
++Identify the versions of each tool used by the compiler, in a
++@code{.ident} assembler directive in the output.
++
++@item -Qn
++@opindex Qn
++Refrain from adding @code{.ident} directives to the output file (this is
++the default).
++
++@item -YP,@var{dirs}
++@opindex YP
++Search the directories @var{dirs}, and no others, for libraries
++specified with @option{-l}.
++
++@item -Ym,@var{dir}
++@opindex Ym
++Look in the directory @var{dir} to find the M4 preprocessor.
++The assembler uses this option.
++@c This is supposed to go with a -Yd for predefined M4 macro files, but
++@c the generic assembler that comes with Solaris takes just -Ym.
++@end table
++
++@node V850 Options
++@subsection V850 Options
++@cindex V850 Options
++
++These @samp{-m} options are defined for V850 implementations:
++
++@table @gcctabopt
++@item -mlong-calls
++@itemx -mno-long-calls
++@opindex mlong-calls
++@opindex mno-long-calls
++Treat all calls as being far away (near). If calls are assumed to be
++far away, the compiler will always load the functions address up into a
++register, and call indirect through the pointer.
++
++@item -mno-ep
++@itemx -mep
++@opindex mno-ep
++@opindex mep
++Do not optimize (do optimize) basic blocks that use the same index
++pointer 4 or more times to copy pointer into the @code{ep} register, and
++use the shorter @code{sld} and @code{sst} instructions. The @option{-mep}
++option is on by default if you optimize.
++
++@item -mno-prolog-function
++@itemx -mprolog-function
++@opindex mno-prolog-function
++@opindex mprolog-function
++Do not use (do use) external functions to save and restore registers
++at the prologue and epilogue of a function. The external functions
++are slower, but use less code space if more than one function saves
++the same number of registers. The @option{-mprolog-function} option
++is on by default if you optimize.
++
++@item -mspace
++@opindex mspace
++Try to make the code as small as possible. At present, this just turns
++on the @option{-mep} and @option{-mprolog-function} options.
++
++@item -mtda=@var{n}
++@opindex mtda
++Put static or global variables whose size is @var{n} bytes or less into
++the tiny data area that register @code{ep} points to. The tiny data
++area can hold up to 256 bytes in total (128 bytes for byte references).
++
++@item -msda=@var{n}
++@opindex msda
++Put static or global variables whose size is @var{n} bytes or less into
++the small data area that register @code{gp} points to. The small data
++area can hold up to 64 kilobytes.
++
++@item -mzda=@var{n}
++@opindex mzda
++Put static or global variables whose size is @var{n} bytes or less into
++the first 32 kilobytes of memory.
++
++@item -mv850
++@opindex mv850
++Specify that the target processor is the V850.
++
++@item -mbig-switch
++@opindex mbig-switch
++Generate code suitable for big switch tables. Use this option only if
++the assembler/linker complain about out of range branches within a switch
++table.
++
++@item -mapp-regs
++@opindex mapp-regs
++This option will cause r2 and r5 to be used in the code generated by
++the compiler. This setting is the default.
++
++@item -mno-app-regs
++@opindex mno-app-regs
++This option will cause r2 and r5 to be treated as fixed registers.
++
++@item -mv850e1
++@opindex mv850e1
++Specify that the target processor is the V850E1. The preprocessor
++constants @samp{__v850e1__} and @samp{__v850e__} will be defined if
++this option is used.
++
++@item -mv850e
++@opindex mv850e
++Specify that the target processor is the V850E@. The preprocessor
++constant @samp{__v850e__} will be defined if this option is used.
++
++If neither @option{-mv850} nor @option{-mv850e} nor @option{-mv850e1}
++are defined then a default target processor will be chosen and the
++relevant @samp{__v850*__} preprocessor constant will be defined.
++
++The preprocessor constants @samp{__v850} and @samp{__v851__} are always
++defined, regardless of which processor variant is the target.
++
++@item -mdisable-callt
++@opindex mdisable-callt
++This option will suppress generation of the CALLT instruction for the
++v850e and v850e1 flavors of the v850 architecture. The default is
++@option{-mno-disable-callt} which allows the CALLT instruction to be used.
++
++@end table
++
++@node VAX Options
++@subsection VAX Options
++@cindex VAX options
++
++These @samp{-m} options are defined for the VAX:
++
++@table @gcctabopt
++@item -munix
++@opindex munix
++Do not output certain jump instructions (@code{aobleq} and so on)
++that the Unix assembler for the VAX cannot handle across long
++ranges.
++
++@item -mgnu
++@opindex mgnu
++Do output those jump instructions, on the assumption that you
++will assemble with the GNU assembler.
++
++@item -mg
++@opindex mg
++Output code for g-format floating point numbers instead of d-format.
++@end table
++
++@node VxWorks Options
++@subsection VxWorks Options
++@cindex VxWorks Options
++
++The options in this section are defined for all VxWorks targets.
++Options specific to the target hardware are listed with the other
++options for that target.
++
++@table @gcctabopt
++@item -mrtp
++@opindex mrtp
++GCC can generate code for both VxWorks kernels and real time processes
++(RTPs). This option switches from the former to the latter. It also
++defines the preprocessor macro @code{__RTP__}.
++
++@item -non-static
++@opindex non-static
++Link an RTP executable against shared libraries rather than static
++libraries. The options @option{-static} and @option{-shared} can
++also be used for RTPs (@pxref{Link Options}); @option{-static}
++is the default.
++
++@item -Bstatic
++@itemx -Bdynamic
++@opindex Bstatic
++@opindex Bdynamic
++These options are passed down to the linker. They are defined for
++compatibility with Diab.
++
++@item -Xbind-lazy
++@opindex Xbind-lazy
++Enable lazy binding of function calls. This option is equivalent to
++@option{-Wl,-z,now} and is defined for compatibility with Diab.
++
++@item -Xbind-now
++@opindex Xbind-now
++Disable lazy binding of function calls. This option is the default and
++is defined for compatibility with Diab.
++@end table
++
++@node x86-64 Options
++@subsection x86-64 Options
++@cindex x86-64 options
++
++These are listed under @xref{i386 and x86-64 Options}.
++
++@node i386 and x86-64 Windows Options
++@subsection i386 and x86-64 Windows Options
++@cindex i386 and x86-64 Windows Options
++
++These additional options are available for Windows targets:
++
++@table @gcctabopt
++@item -mconsole
++@opindex mconsole
++This option is available for Cygwin and MinGW targets. It
++specifies that a console application is to be generated, by
++instructing the linker to set the PE header subsystem type
++required for console applications.
++This is the default behaviour for Cygwin and MinGW targets.
++
++@item -mcygwin
++@opindex mcygwin
++This option is available for Cygwin targets. It specifies that
++the Cygwin internal interface is to be used for predefined
++preprocessor macros, C runtime libraries and related linker
++paths and options. For Cygwin targets this is the default behaviour.
++This option is deprecated and will be removed in a future release.
++
++@item -mno-cygwin
++@opindex mno-cygwin
++This option is available for Cygwin targets. It specifies that
++the MinGW internal interface is to be used instead of Cygwin's, by
++setting MinGW-related predefined macros and linker paths and default
++library options.
++This option is deprecated and will be removed in a future release.
++
++@item -mdll
++@opindex mdll
++This option is available for Cygwin and MinGW targets. It
++specifies that a DLL - a dynamic link library - is to be
++generated, enabling the selection of the required runtime
++startup object and entry point.
++
++@item -mnop-fun-dllimport
++@opindex mnop-fun-dllimport
++This option is available for Cygwin and MinGW targets. It
++specifies that the dllimport attribute should be ignored.
++
++@item -mthread
++@opindex mthread
++This option is available for MinGW targets. It specifies
++that MinGW-specific thread support is to be used.
++
++@item -mwin32
++@opindex mwin32
++This option is available for Cygwin and MinGW targets. It
++specifies that the typical Windows pre-defined macros are to
++be set in the pre-processor, but does not influence the choice
++of runtime library/startup code.
++
++@item -mwindows
++@opindex mwindows
++This option is available for Cygwin and MinGW targets. It
++specifies that a GUI application is to be generated by
++instructing the linker to set the PE header subsystem type
++appropriately.
++@end table
++
++See also under @ref{i386 and x86-64 Options} for standard options.
++
++@node Xstormy16 Options
++@subsection Xstormy16 Options
++@cindex Xstormy16 Options
++
++These options are defined for Xstormy16:
++
++@table @gcctabopt
++@item -msim
++@opindex msim
++Choose startup files and linker script suitable for the simulator.
++@end table
++
++@node Xtensa Options
++@subsection Xtensa Options
++@cindex Xtensa Options
++
++These options are supported for Xtensa targets:
++
++@table @gcctabopt
++@item -mconst16
++@itemx -mno-const16
++@opindex mconst16
++@opindex mno-const16
++Enable or disable use of @code{CONST16} instructions for loading
++constant values. The @code{CONST16} instruction is currently not a
++standard option from Tensilica. When enabled, @code{CONST16}
++instructions are always used in place of the standard @code{L32R}
++instructions. The use of @code{CONST16} is enabled by default only if
++the @code{L32R} instruction is not available.
++
++@item -mfused-madd
++@itemx -mno-fused-madd
++@opindex mfused-madd
++@opindex mno-fused-madd
++Enable or disable use of fused multiply/add and multiply/subtract
++instructions in the floating-point option. This has no effect if the
++floating-point option is not also enabled. Disabling fused multiply/add
++and multiply/subtract instructions forces the compiler to use separate
++instructions for the multiply and add/subtract operations. This may be
++desirable in some cases where strict IEEE 754-compliant results are
++required: the fused multiply add/subtract instructions do not round the
++intermediate result, thereby producing results with @emph{more} bits of
++precision than specified by the IEEE standard. Disabling fused multiply
++add/subtract instructions also ensures that the program output is not
++sensitive to the compiler's ability to combine multiply and add/subtract
++operations.
++
++@item -mserialize-volatile
++@itemx -mno-serialize-volatile
++@opindex mserialize-volatile
++@opindex mno-serialize-volatile
++When this option is enabled, GCC inserts @code{MEMW} instructions before
++@code{volatile} memory references to guarantee sequential consistency.
++The default is @option{-mserialize-volatile}. Use
++@option{-mno-serialize-volatile} to omit the @code{MEMW} instructions.
++
++@item -mtext-section-literals
++@itemx -mno-text-section-literals
++@opindex mtext-section-literals
++@opindex mno-text-section-literals
++Control the treatment of literal pools. The default is
++@option{-mno-text-section-literals}, which places literals in a separate
++section in the output file. This allows the literal pool to be placed
++in a data RAM/ROM, and it also allows the linker to combine literal
++pools from separate object files to remove redundant literals and
++improve code size. With @option{-mtext-section-literals}, the literals
++are interspersed in the text section in order to keep them as close as
++possible to their references. This may be necessary for large assembly
++files.
++
++@item -mtarget-align
++@itemx -mno-target-align
++@opindex mtarget-align
++@opindex mno-target-align
++When this option is enabled, GCC instructs the assembler to
++automatically align instructions to reduce branch penalties at the
++expense of some code density. The assembler attempts to widen density
++instructions to align branch targets and the instructions following call
++instructions. If there are not enough preceding safe density
++instructions to align a target, no widening will be performed. The
++default is @option{-mtarget-align}. These options do not affect the
++treatment of auto-aligned instructions like @code{LOOP}, which the
++assembler will always align, either by widening density instructions or
++by inserting no-op instructions.
++
++@item -mlongcalls
++@itemx -mno-longcalls
++@opindex mlongcalls
++@opindex mno-longcalls
++When this option is enabled, GCC instructs the assembler to translate
++direct calls to indirect calls unless it can determine that the target
++of a direct call is in the range allowed by the call instruction. This
++translation typically occurs for calls to functions in other source
++files. Specifically, the assembler translates a direct @code{CALL}
++instruction into an @code{L32R} followed by a @code{CALLX} instruction.
++The default is @option{-mno-longcalls}. This option should be used in
++programs where the call target can potentially be out of range. This
++option is implemented in the assembler, not the compiler, so the
++assembly code generated by GCC will still show direct call
++instructions---look at the disassembled object code to see the actual
++instructions. Note that the assembler will use an indirect call for
++every cross-file call, not just those that really will be out of range.
++@end table
++
++@node zSeries Options
++@subsection zSeries Options
++@cindex zSeries options
++
++These are listed under @xref{S/390 and zSeries Options}.
++
++@node Code Gen Options
++@section Options for Code Generation Conventions
++@cindex code generation conventions
++@cindex options, code generation
++@cindex run-time options
++
++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 @option{-ffoo} would be @option{-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 @samp{no-} or adding
++it.
++
++@table @gcctabopt
++@item -fbounds-check
++@opindex 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
++currently only supported by the Java and Fortran front-ends, where
++this option defaults to true and false respectively.
++
++@item -ftrapv
++@opindex ftrapv
++This option generates traps for signed overflow on addition, subtraction,
++multiplication operations.
++
++@item -fwrapv
++@opindex fwrapv
++This option instructs the compiler to assume that signed arithmetic
++overflow of addition, subtraction and multiplication wraps around
++using twos-complement representation. This flag enables some optimizations
++and disables others. This option is enabled by default for the Java
++front-end, as required by the Java language specification.
++
++@item -fexceptions
++@opindex 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.
++
++@item -fnon-call-exceptions
++@opindex 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 @emph{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 @code{SIGALRM}.
++
++@item -funwind-tables
++@opindex funwind-tables
++Similar to @option{-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.
++
++@item -fasynchronous-unwind-tables
++@opindex 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).
++
++@item -fpcc-struct-return
++@opindex fpcc-struct-return
++Return ``short'' @code{struct} and @code{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.
++
++@strong{Warning:} code compiled with the @option{-fpcc-struct-return}
++switch is not binary compatible with code compiled with the
++@option{-freg-struct-return} switch.
++Use it to conform to a non-default application binary interface.
++
++@item -freg-struct-return
++@opindex freg-struct-return
++Return @code{struct} and @code{union} values in registers when possible.
++This is more efficient for small structures than
++@option{-fpcc-struct-return}.
++
++If you specify neither @option{-fpcc-struct-return} nor
++@option{-freg-struct-return}, GCC defaults to whichever convention is
++standard for the target. If there is no standard convention, GCC
++defaults to @option{-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.
++
++@strong{Warning:} code compiled with the @option{-freg-struct-return}
++switch is not binary compatible with code compiled with the
++@option{-fpcc-struct-return} switch.
++Use it to conform to a non-default application binary interface.
++
++@item -fshort-enums
++@opindex fshort-enums
++Allocate to an @code{enum} type only as many bytes as it needs for the
++declared range of possible values. Specifically, the @code{enum} type
++will be equivalent to the smallest integer type which has enough room.
++
++@strong{Warning:} the @option{-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.
++
++@item -fshort-double
++@opindex fshort-double
++Use the same size for @code{double} as for @code{float}.
++
++@strong{Warning:} the @option{-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.
++
++@item -fshort-wchar
++@opindex fshort-wchar
++Override the underlying type for @samp{wchar_t} to be @samp{short
++unsigned int} instead of the default for the target. This option is
++useful for building programs to run under WINE@.
++
++@strong{Warning:} the @option{-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.
++
++@item -fno-common
++@opindex fno-common
++In C code, controls the placement of uninitialized global variables.
++Unix C compilers have traditionally permitted multiple definitions of
++such variables in different compilation units by placing the variables
++in a common block.
++This is the behavior specified by @option{-fcommon}, and is the default
++for GCC on most targets.
++On the other hand, this behavior is not required by ISO C, and on some
++targets may carry a speed or code size penalty on variable references.
++The @option{-fno-common} option specifies that the compiler should place
++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 @code{extern}) in two different compilations,
++you will get a multiple-definition error when you link them.
++In this case, you must compile with @option{-fcommon} instead.
++Compiling with @option{-fno-common} is useful on targets for which
++it provides better performance, or if you wish to verify that the
++program will work on other systems which always treat uninitialized
++variable declarations this way.
++
++@item -fno-ident
++@opindex fno-ident
++Ignore the @samp{#ident} directive.
++
++@item -finhibit-size-directive
++@opindex finhibit-size-directive
++Don't output a @code{.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 @file{crtstuff.c}; you should not need to use it
++for anything else.
++
++@item -fverbose-asm
++@opindex 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).
++
++@option{-fno-verbose-asm}, the default, causes the
++extra information to be omitted and is useful when comparing two assembler
++files.
++
++@item -frecord-gcc-switches
++@opindex frecord-gcc-switches
++This switch causes the command line that was used to invoke the
++compiler to be recorded into the object file that is being created.
++This switch is only implemented on some targets and the exact format
++of the recording is target and binary file format dependent, but it
++usually takes the form of a section containing ASCII text. This
++switch is related to the @option{-fverbose-asm} switch, but that
++switch only records information in the assembler output file as
++comments, so it never reaches the object file.
++
++@item -fpic
++@opindex fpic
++@cindex global offset table
++@cindex PIC
++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
++@option{-fpic} does not work; in that case, recompile with @option{-fPIC}
++instead. (These maximums are 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.
++
++When this flag is set, the macros @code{__pic__} and @code{__PIC__}
++are defined to 1.
++
++@item -fPIC
++@opindex 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,
++PowerPC and SPARC@.
++
++Position-independent code requires special support, and therefore works
++only on certain machines.
++
++When this flag is set, the macros @code{__pic__} and @code{__PIC__}
++are defined to 2.
++
++@item -fpie
++@itemx -fPIE
++@opindex fpie
++@opindex fPIE
++These options are similar to @option{-fpic} and @option{-fPIC}, but
++generated position independent code can be only linked into executables.
++Usually these options are used when @option{-pie} GCC option will be
++used during linking.
++
++@option{-fpie} and @option{-fPIE} both define the macros
++@code{__pie__} and @code{__PIE__}. The macros have the value 1
++for @option{-fpie} and 2 for @option{-fPIE}.
++
++@item -fno-jump-tables
++@opindex fno-jump-tables
++Do not use jump tables for switch statements even where it would be
++more efficient than other code generation strategies. This option is
++of use in conjunction with @option{-fpic} or @option{-fPIC} for
++building code which forms part of a dynamic linker and cannot
++reference the address of a jump table. On some targets, jump tables
++do not require a GOT and this option is not needed.
++
++@item -ffixed-@var{reg}
++@opindex ffixed
++Treat the register named @var{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).
++
++@var{reg} must be the name of a register. The register names accepted
++are machine-specific and are defined in the @code{REGISTER_NAMES}
++macro in the machine description macro file.
++
++This flag does not have a negative form, because it specifies a
++three-way choice.
++
++@item -fcall-used-@var{reg}
++@opindex fcall-used
++Treat the register named @var{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 @var{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.
++
++@item -fcall-saved-@var{reg}
++@opindex fcall-saved
++Treat the register named @var{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 @var{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.
++
++@item -fpack-struct[=@var{n}]
++@opindex fpack-struct
++Without a value specified, pack all structure members together without
++holes. When a value is specified (which must be a small power of two), pack
++structure members according to this value, representing the maximum
++alignment (that is, objects with default alignment requirements larger than
++this will be output potentially unaligned at the next fitting location.
++
++@strong{Warning:} the @option{-fpack-struct} switch causes GCC to generate
++code that is not binary compatible with code generated without that switch.
++Additionally, it makes the code suboptimal.
++Use it to conform to a non-default application binary interface.
++
++@item -finstrument-functions
++@opindex 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,
++@code{__builtin_return_address} does not work beyond the current
++function, so the call site information may not be available to the
++profiling functions otherwise.)
++
++@smallexample
++void __cyg_profile_func_enter (void *this_fn,
++ void *call_site);
++void __cyg_profile_func_exit (void *this_fn,
++ void *call_site);
++@end smallexample
++
++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 @samp{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 @code{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).
++
++@item -finstrument-functions-exclude-file-list=@var{file},@var{file},@dots{}
++@opindex finstrument-functions-exclude-file-list
++
++Set the list of functions that are excluded from instrumentation (see
++the description of @code{-finstrument-functions}). If the file that
++contains a function definition matches with one of @var{file}, then
++that function is not instrumented. The match is done on substrings:
++if the @var{file} parameter is a substring of the file name, it is
++considered to be a match.
++
++For example,
++@code{-finstrument-functions-exclude-file-list=/bits/stl,include/sys}
++will exclude any inline function defined in files whose pathnames
++contain @code{/bits/stl} or @code{include/sys}.
++
++If, for some reason, you want to include letter @code{','} in one of
++@var{sym}, write @code{'\,'}. For example,
++@code{-finstrument-functions-exclude-file-list='\,\,tmp'}
++(note the single quote surrounding the option).
++
++@item -finstrument-functions-exclude-function-list=@var{sym},@var{sym},@dots{}
++@opindex finstrument-functions-exclude-function-list
++
++This is similar to @code{-finstrument-functions-exclude-file-list},
++but this option sets the list of function names to be excluded from
++instrumentation. The function name to be matched is its user-visible
++name, such as @code{vector<int> blah(const vector<int> &)}, not the
++internal mangled name (e.g., @code{_Z4blahRSt6vectorIiSaIiEE}). The
++match is done on substrings: if the @var{sym} parameter is a substring
++of the function name, it is considered to be a match.
++
++@item -fstack-check
++@opindex 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 or the language runtime must do that. The switch causes
++generation of code to ensure that they see the stack being extended.
++
++You can additionally specify a string parameter: @code{no} means no
++checking, @code{generic} means force the use of old-style checking,
++@code{specific} means use the best checking method and is equivalent
++to bare @option{-fstack-check}.
++
++Old-style checking is a generic mechanism that requires no specific
++target support in the compiler but comes with the following drawbacks:
++
++@enumerate
++@item
++Modified allocation strategy for large objects: they will always be
++allocated dynamically if their size exceeds a fixed threshold.
++
++@item
++Fixed limit on the size of the static frame of functions: when it is
++topped by a particular function, stack checking is not reliable and
++a warning is issued by the compiler.
++
++@item
++Inefficiency: because of both the modified allocation strategy and the
++generic implementation, the performances of the code are hampered.
++@end enumerate
++
++Note that old-style stack checking is also the fallback method for
++@code{specific} if no target support has been added in the compiler.
++
++@item -fstack-limit-register=@var{reg}
++@itemx -fstack-limit-symbol=@var{sym}
++@itemx -fno-stack-limit
++@opindex fstack-limit-register
++@opindex fstack-limit-symbol
++@opindex 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 @samp{0x80000000}
++and grows downwards, you can use the flags
++@option{-fstack-limit-symbol=__stack_limit} and
++@option{-Wl,--defsym,__stack_limit=0x7ffe0000} to enforce a stack limit
++of 128KB@. Note that this may only work with the GNU linker.
++
++@cindex aliasing of parameters
++@cindex parameters, aliased
++@item -fargument-alias
++@itemx -fargument-noalias
++@itemx -fargument-noalias-global
++@itemx -fargument-noalias-anything
++@opindex fargument-alias
++@opindex fargument-noalias
++@opindex fargument-noalias-global
++@opindex fargument-noalias-anything
++Specify the possible relationships among parameters and between
++parameters and global data.
++
++@option{-fargument-alias} specifies that arguments (parameters) may
++alias each other and may alias global storage.@*
++@option{-fargument-noalias} specifies that arguments do not alias
++each other, but may alias global storage.@*
++@option{-fargument-noalias-global} specifies that arguments do not
++alias each other and do not alias global storage.
++@option{-fargument-noalias-anything} specifies that arguments do not
++alias any other storage.
++
++Each language will automatically use whatever option is required by
++the language standard. You should not need to use these options yourself.
++
++@item -fleading-underscore
++@opindex fleading-underscore
++This option and its counterpart, @option{-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.
++
++@strong{Warning:} the @option{-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.
++
++@item -ftls-model=@var{model}
++@opindex ftls-model
++Alter the thread-local storage model to be used (@pxref{Thread-Local}).
++The @var{model} argument should be one of @code{global-dynamic},
++@code{local-dynamic}, @code{initial-exec} or @code{local-exec}.
++
++The default without @option{-fpic} is @code{initial-exec}; with
++@option{-fpic} the default is @code{global-dynamic}.
++
++@item -fvisibility=@var{default|internal|hidden|protected}
++@opindex fvisibility
++Set the default ELF image symbol visibility to the specified option---all
++symbols will be marked with this unless overridden within the code.
++Using this feature can very substantially improve linking and
++load times of shared object libraries, produce more optimized
++code, provide near-perfect API export and prevent symbol clashes.
++It is @strong{strongly} recommended that you use this in any shared objects
++you distribute.
++
++Despite the nomenclature, @code{default} always means public ie;
++available to be linked against from outside the shared object.
++@code{protected} and @code{internal} are pretty useless in real-world
++usage so the only other commonly used option will be @code{hidden}.
++The default if @option{-fvisibility} isn't specified is
++@code{default}, i.e., make every
++symbol public---this causes the same behavior as previous versions of
++GCC@.
++
++A good explanation of the benefits offered by ensuring ELF
++symbols have the correct visibility is given by ``How To Write
++Shared Libraries'' by Ulrich Drepper (which can be found at
++@w{@uref{http://people.redhat.com/~drepper/}})---however a superior
++solution made possible by this option to marking things hidden when
++the default is public is to make the default hidden and mark things
++public. This is the norm with DLL's on Windows and with @option{-fvisibility=hidden}
++and @code{__attribute__ ((visibility("default")))} instead of
++@code{__declspec(dllexport)} you get almost identical semantics with
++identical syntax. This is a great boon to those working with
++cross-platform projects.
++
++For those adding visibility support to existing code, you may find
++@samp{#pragma GCC visibility} of use. This works by you enclosing
++the declarations you wish to set visibility for with (for example)
++@samp{#pragma GCC visibility push(hidden)} and
++@samp{#pragma GCC visibility pop}.
++Bear in mind that symbol visibility should be viewed @strong{as
++part of the API interface contract} and thus all new code should
++always specify visibility when it is not the default ie; declarations
++only for use within the local DSO should @strong{always} be marked explicitly
++as hidden as so to avoid PLT indirection overheads---making this
++abundantly clear also aids readability and self-documentation of the code.
++Note that due to ISO C++ specification requirements, operator new and
++operator delete must always be of default visibility.
++
++Be aware that headers from outside your project, in particular system
++headers and headers from any other library you use, may not be
++expecting to be compiled with visibility other than the default. You
++may need to explicitly say @samp{#pragma GCC visibility push(default)}
++before including any such headers.
++
++@samp{extern} declarations are not affected by @samp{-fvisibility}, so
++a lot of code can be recompiled with @samp{-fvisibility=hidden} with
++no modifications. However, this means that calls to @samp{extern}
++functions with no explicit visibility will use the PLT, so it is more
++effective to use @samp{__attribute ((visibility))} and/or
++@samp{#pragma GCC visibility} to tell the compiler which @samp{extern}
++declarations should be treated as hidden.
++
++Note that @samp{-fvisibility} does affect C++ vague linkage
++entities. This means that, for instance, an exception class that will
++be thrown between DSOs must be explicitly marked with default
++visibility so that the @samp{type_info} nodes will be unified between
++the DSOs.
++
++An overview of these techniques, their benefits and how to use them
++is at @w{@uref{http://gcc.gnu.org/wiki/Visibility}}.
++
++@end table
++
++@c man end
++
++@node Environment Variables
++@section Environment Variables Affecting GCC
++@cindex environment variables
++
++@c man begin ENVIRONMENT
++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
++@option{-B}, @option{-I} and @option{-L} (@pxref{Directory Options}). These
++take precedence over places specified using environment variables, which
++in turn take precedence over those specified by the configuration of GCC@.
++@xref{Driver,, Controlling the Compilation Driver @file{gcc}, gccint,
++GNU Compiler Collection (GCC) Internals}.
++
++@table @env
++@item LANG
++@itemx LC_CTYPE
++@c @itemx LC_COLLATE
++@itemx LC_MESSAGES
++@c @itemx LC_MONETARY
++@c @itemx LC_NUMERIC
++@c @itemx LC_TIME
++@itemx LC_ALL
++@findex LANG
++@findex LC_CTYPE
++@c @findex LC_COLLATE
++@findex LC_MESSAGES
++@c @findex LC_MONETARY
++@c @findex LC_NUMERIC
++@c @findex LC_TIME
++@findex LC_ALL
++@cindex locale
++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
++@env{LC_CTYPE} and @env{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 @samp{en_GB.UTF-8} for English in the United
++Kingdom encoded in UTF-8.
++
++The @env{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 @env{LC_MESSAGES} environment variable specifies the language to
++use in diagnostic messages.
++
++If the @env{LC_ALL} environment variable is set, it overrides the value
++of @env{LC_CTYPE} and @env{LC_MESSAGES}; otherwise, @env{LC_CTYPE}
++and @env{LC_MESSAGES} default to the value of the @env{LANG}
++environment variable. If none of these variables are set, GCC
++defaults to traditional C English behavior.
++
++@item TMPDIR
++@findex TMPDIR
++If @env{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.
++
++@item GCC_EXEC_PREFIX
++@findex GCC_EXEC_PREFIX
++If @env{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 @env{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 @env{GCC_EXEC_PREFIX} is
++@file{@var{prefix}/lib/gcc/} where @var{prefix} is the prefix to
++the installed compiler. In many cases @var{prefix} is the value
++of @code{prefix} when you ran the @file{configure} script.
++
++Other prefixes specified with @option{-B} take precedence over this prefix.
++
++This prefix is also used for finding files such as @file{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 @samp{/usr/local/lib/gcc}
++(more precisely, with the value of @env{GCC_INCLUDE_DIR}), GCC tries
++replacing that beginning with the specified prefix to produce an
++alternate directory name. Thus, with @option{-Bfoo/}, GCC will search
++@file{foo/bar} where it would normally search @file{/usr/local/lib/bar}.
++These alternate directories are searched first; the standard directories
++come next. If a standard directory begins with the configured
++@var{prefix} then the value of @var{prefix} is replaced by
++@env{GCC_EXEC_PREFIX} when looking for header files.
++
++@item COMPILER_PATH
++@findex COMPILER_PATH
++The value of @env{COMPILER_PATH} is a colon-separated list of
++directories, much like @env{PATH}. GCC tries the directories thus
++specified when searching for subprograms, if it can't find the
++subprograms using @env{GCC_EXEC_PREFIX}.
++
++@item LIBRARY_PATH
++@findex LIBRARY_PATH
++The value of @env{LIBRARY_PATH} is a colon-separated list of
++directories, much like @env{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 @env{GCC_EXEC_PREFIX}. Linking
++using GCC also uses these directories when searching for ordinary
++libraries for the @option{-l} option (but directories specified with
++@option{-L} come first).
++
++@item LANG
++@findex LANG
++@cindex locale definition
++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 @env{LANG} are recognized:
++
++@table @samp
++@item C-JIS
++Recognize JIS characters.
++@item C-SJIS
++Recognize SJIS characters.
++@item C-EUCJP
++Recognize EUCJP characters.
++@end table
++
++If @env{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.
++@end table
++
++@noindent
++Some additional environments variables affect the behavior of the
++preprocessor.
++
++@include cppenv.texi
++
++@c man end
++
++@node Precompiled Headers
++@section Using Precompiled Headers
++@cindex precompiled headers
++@cindex speed of compilation
++
++Often large projects have many header files that are included in every
++source file. The time the compiler takes to process these header files
++over and over again can account for nearly all of the time required to
++build the project. To make builds faster, GCC allows users to
++`precompile' a header file; then, if builds can use the precompiled
++header file they will be much faster.
++
++To create a precompiled header file, simply compile it as you would any
++other file, if necessary using the @option{-x} option to make the driver
++treat it as a C or C++ header file. You will probably want to use a
++tool like @command{make} to keep the precompiled header up-to-date when
++the headers it contains change.
++
++A precompiled header file will be searched for when @code{#include} is
++seen in the compilation. As it searches for the included file
++(@pxref{Search Path,,Search Path,cpp,The C Preprocessor}) the
++compiler looks for a precompiled header in each directory just before it
++looks for the include file in that directory. The name searched for is
++the name specified in the @code{#include} with @samp{.gch} appended. If
++the precompiled header file can't be used, it is ignored.
++
++For instance, if you have @code{#include "all.h"}, and you have
++@file{all.h.gch} in the same directory as @file{all.h}, then the
++precompiled header file will be used if possible, and the original
++header will be used otherwise.
++
++Alternatively, you might decide to put the precompiled header file in a
++directory and use @option{-I} to ensure that directory is searched
++before (or instead of) the directory containing the original header.
++Then, if you want to check that the precompiled header file is always
++used, you can put a file of the same name as the original header in this
++directory containing an @code{#error} command.
++
++This also works with @option{-include}. So yet another way to use
++precompiled headers, good for projects not designed with precompiled
++header files in mind, is to simply take most of the header files used by
++a project, include them from another header file, precompile that header
++file, and @option{-include} the precompiled header. If the header files
++have guards against multiple inclusion, they will be skipped because
++they've already been included (in the precompiled header).
++
++If you need to precompile the same header file for different
++languages, targets, or compiler options, you can instead make a
++@emph{directory} named like @file{all.h.gch}, and put each precompiled
++header in the directory, perhaps using @option{-o}. It doesn't matter
++what you call the files in the directory, every precompiled header in
++the directory will be considered. The first precompiled header
++encountered in the directory that is valid for this compilation will
++be used; they're searched in no particular order.
++
++There are many other possibilities, limited only by your imagination,
++good sense, and the constraints of your build system.
++
++A precompiled header file can be used only when these conditions apply:
++
++@itemize
++@item
++Only one precompiled header can be used in a particular compilation.
++
++@item
++A precompiled header can't be used once the first C token is seen. You
++can have preprocessor directives before a precompiled header; you can
++even include a precompiled header from inside another header, so long as
++there are no C tokens before the @code{#include}.
++
++@item
++The precompiled header file must be produced for the same language as
++the current compilation. You can't use a C precompiled header for a C++
++compilation.
++
++@item
++The precompiled header file must have been produced by the same compiler
++binary as the current compilation is using.
++
++@item
++Any macros defined before the precompiled header is included must
++either be defined in the same way as when the precompiled header was
++generated, or must not affect the precompiled header, which usually
++means that they don't appear in the precompiled header at all.
++
++The @option{-D} option is one way to define a macro before a
++precompiled header is included; using a @code{#define} can also do it.
++There are also some options that define macros implicitly, like
++@option{-O} and @option{-Wdeprecated}; the same rule applies to macros
++defined this way.
++
++@item If debugging information is output when using the precompiled
++header, using @option{-g} or similar, the same kind of debugging information
++must have been output when building the precompiled header. However,
++a precompiled header built using @option{-g} can be used in a compilation
++when no debugging information is being output.
++
++@item The same @option{-m} options must generally be used when building
++and using the precompiled header. @xref{Submodel Options},
++for any cases where this rule is relaxed.
++
++@item Each of the following options must be the same when building and using
++the precompiled header:
++
++@gccoptlist{-fexceptions}
++
++@item
++Some other command-line options starting with @option{-f},
++@option{-p}, or @option{-O} must be defined in the same way as when
++the precompiled header was generated. At present, it's not clear
++which options are safe to change and which are not; the safest choice
++is to use exactly the same options when generating and using the
++precompiled header. The following are known to be safe:
++
++@gccoptlist{-fmessage-length= -fpreprocessed -fsched-interblock @gol
++-fsched-spec -fsched-spec-load -fsched-spec-load-dangerous @gol
++-fsched-verbose=<number> -fschedule-insns -fvisibility= @gol
++-pedantic-errors}
++
++@end itemize
++
++For all of these except the last, the compiler will automatically
++ignore the precompiled header if the conditions aren't met. If you
++find an option combination that doesn't work and doesn't cause the
++precompiled header to be ignored, please consider filing a bug report,
++see @ref{Bugs}.
++
++If you do use differing options when generating and using the
++precompiled header, the actual behavior will be a mixture of the
++behavior for the options. For instance, if you use @option{-g} to
++generate the precompiled header but not when using it, you may or may
++not get debugging information for routines in the precompiled header.
++
++@node Running Protoize
++@section Running Protoize
++
++The program @code{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 @code{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 @var{foo} is saved in a file named @file{@var{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,
++@code{protoize} and @code{unprotoize} convert only source and header
++files in the current directory. You can specify additional directories
++whose files should be converted with the @option{-d @var{directory}}
++option. You can also specify particular files to exclude with the
++@option{-x @var{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 @code{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.
++
++@code{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 @code{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 @option{-q}.
++
++The output from @code{protoize} or @code{unprotoize} replaces the
++original source file. The original file is renamed to a name ending
++with @samp{.save} (for DOS, the saved filename ends in @samp{.sav}
++without the original @samp{.c} suffix). If the @samp{.save} (@samp{.sav}
++for DOS) file already exists, then the source file is simply discarded.
++
++@code{protoize} and @code{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 @code{protoize} and
++@code{unprotoize}. Each option works with both programs unless
++otherwise stated.
++
++@table @code
++@item -B @var{directory}
++Look for the file @file{SYSCALLS.c.X} in @var{directory}, instead of the
++usual directory (normally @file{/usr/local/lib}). This file contains
++prototype information about standard system functions. This option
++applies only to @code{protoize}.
++
++@item -c @var{compilation-options}
++Use @var{compilation-options} as the options when running @command{gcc} to
++produce the @samp{.X} files. The special option @option{-aux-info} is
++always passed in addition, to tell @command{gcc} to write a @samp{.X} file.
++
++Note that the compilation options must be given as a single argument to
++@code{protoize} or @code{unprotoize}. If you want to specify several
++@command{gcc} options, you must quote the entire set of compilation options
++to make them a single word in the shell.
++
++There are certain @command{gcc} arguments that you cannot use, because they
++would produce the wrong kind of output. These include @option{-g},
++@option{-O}, @option{-c}, @option{-S}, and @option{-o} If you include these in
++the @var{compilation-options}, they are ignored.
++
++@item -C
++Rename files to end in @samp{.C} (@samp{.cc} for DOS-based file
++systems) instead of @samp{.c}. This is convenient if you are converting
++a C program to C++. This option applies only to @code{protoize}.
++
++@item -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 @code{protoize}.
++
++@item -i @var{string}
++Indent old-style parameter declarations with the string @var{string}.
++This option applies only to @code{protoize}.
++
++@code{unprotoize} converts prototyped function definitions to old-style
++function definitions, where the arguments are declared between the
++argument list and the initial @samp{@{}. By default, @code{unprotoize}
++uses five spaces as the indentation. If you want to indent with just
++one space instead, use @option{-i " "}.
++
++@item -k
++Keep the @samp{.X} files. Normally, they are deleted after conversion
++is finished.
++
++@item -l
++Add explicit local declarations. @code{protoize} with @option{-l} inserts
++a prototype declaration for each function in each block which calls the
++function without any declaration. This option applies only to
++@code{protoize}.
++
++@item -n
++Make no real changes. This mode just prints information about the conversions
++that would have been done without @option{-n}.
++
++@item -N
++Make no @samp{.save} files. The original files are simply deleted.
++Use this option with caution.
++
++@item -p @var{program}
++Use the program @var{program} as the compiler. Normally, the name
++@file{gcc} is used.
++
++@item -q
++Work quietly. Most warnings are suppressed.
++
++@item -v
++Print the version number, just like @option{-v} for @command{gcc}.
++@end table
++
++If you need special compiler options to compile one of your program's
++source files, then you should generate that file's @samp{.X} file
++specially, by running @command{gcc} on that source file with the
++appropriate options and the option @option{-aux-info}. Then run
++@code{protoize} on the entire set of files. @code{protoize} will use
++the existing @samp{.X} file because it is newer than the source file.
++For example:
++
++@smallexample
++gcc -Dfoo=bar file1.c -aux-info file1.X
++protoize *.c
++@end smallexample
++
++@noindent
++You need to include the special files along with the rest in the
++@code{protoize} command, even though their @samp{.X} files already
++exist, because otherwise they won't get converted.
++
++@xref{Protoize Caveats}, for more information on how to use
++@code{protoize} successfully.
+diff -Naur gcc-4.4.2.orig/libgcc/config/lm32/t-elf gcc-4.4.2-rtems4.10-20091015/libgcc/config/lm32/t-elf
+--- gcc-4.4.2.orig/libgcc/config/lm32/t-elf 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/libgcc/config/lm32/t-elf 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,12 @@
++# Assemble startup files.
++
++$(T)crti.o: $(gcc_srcdir)/config/lm32/crti.S $(GCC_PASSES)
++ $(GCC_FOR_TARGET) $(GCC_CFLAGS) $(MULTILIB_CFLAGS) $(INCLUDES) \
++ -c -o $(T)crti.o -x assembler-with-cpp $(gcc_srcdir)/config/lm32/crti.S
++
++$(T)crtn.o: $(gcc_srcdir)/config/lm32/crtn.S $(GCC_PASSES)
++ $(GCC_FOR_TARGET) $(GCC_CFLAGS) $(MULTILIB_CFLAGS) $(INCLUDES) \
++ -c -o $(T)crtn.o -x assembler-with-cpp $(gcc_srcdir)/config/lm32/crtn.S
++
++CRTSTUFF_T_CFLAGS = -G 0
++TARGET_LIBGCC2_CFLAGS = -G 0
+diff -Naur gcc-4.4.2.orig/libgcc/config/lm32/t-uclinux gcc-4.4.2-rtems4.10-20091015/libgcc/config/lm32/t-uclinux
+--- gcc-4.4.2.orig/libgcc/config/lm32/t-uclinux 1970-01-01 01:00:00.000000000 +0100
++++ gcc-4.4.2-rtems4.10-20091015/libgcc/config/lm32/t-uclinux 2009-10-15 18:36:00.000000000 +0200
+@@ -0,0 +1,2 @@
++CRTSTUFF_T_CFLAGS = -fPIC
++TARGET_LIBGCC2_CFLAGS = -fPIC
+diff -Naur gcc-4.4.2.orig/libgcc/config.host gcc-4.4.2-rtems4.10-20091015/libgcc/config.host
+--- gcc-4.4.2.orig/libgcc/config.host 2009-04-17 13:58:41.000000000 +0200
++++ gcc-4.4.2-rtems4.10-20091015/libgcc/config.host 2009-10-15 18:36:00.000000000 +0200
+@@ -95,6 +95,9 @@
+ hppa*-*-*)
+ cpu_type=pa
+ ;;
++lm32*-*-*)
++ cpu_type=lm32
++ ;;
+ m32r*-*-*)
+ cpu_type=m32r
+ ;;
+@@ -355,6 +358,14 @@
+ ;;
+ iq2000*-*-elf*)
+ ;;
++lm32-*-elf* | lm32-*-rtems*)
++ extra_parts="crtbegin.o crtend.o crti.o crtn.o"
++ tmake_file="lm32/t-elf"
++ ;;
++lm32-*-uclinux*)
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o crtbeginT.o"
++ tmake_file="lm32/t-uclinux"
++ ;;
+ m32r-*-elf*|m32r-*-rtems*)
+ ;;
+ m32rle-*-elf*)
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-01 06:14:36 +0000