Commit a89ea0df by Nathanael Nerode

config.host: New file.

	* config.host: New file.
	* config.gcc: Remove some host-specific stuff and some
	logic needed only for repeated invocation.
	* configure.in: Use config.host.
	* configure: Regenerate.

From-SVN: r70975
parent 31934da7
2003-09-01 Nathanael Nerode <neroden@gcc.gnu.org>
* config.host: New file.
* config.gcc: Remove some host-specific stuff and some
logic needed only for repeated invocation.
* configure.in: Use config.host.
* configure: Regenerate.
2003-09-01 Josef Zlomek <zlomekj@suse.cz> 2003-09-01 Josef Zlomek <zlomekj@suse.cz>
* c-typeck.c (build_binary_op): Kill BIT_ANDTC_EXPR. * c-typeck.c (build_binary_op): Kill BIT_ANDTC_EXPR.
......
# GCC host- and target-specific configuration file. # GCC target-specific configuration file.
# Copyright 1997, 1998, 1999, 2000, 2001, 2002, 2003 # Copyright 1997, 1998, 1999, 2000, 2001, 2002, 2003
# Free Software Foundation, Inc. # Free Software Foundation, Inc.
...@@ -19,13 +19,11 @@ ...@@ -19,13 +19,11 @@
#Software Foundation, 59 Temple Place - Suite 330, Boston, MA #Software Foundation, 59 Temple Place - Suite 330, Boston, MA
#02111-1307, USA. #02111-1307, USA.
# This is the GCC host- and target-specific configuration file # This is the GCC target-specific configuration file
# where a configuration type, as recognized and generated by config.bfd, # where a configuration type is mapped to different system-specific
# is mapped to different system-specific definitions and files. This is # definitions and files. This is invoked by the autoconf-generated
# invoked by the autoconf-generated configure script, called for # configure script. Putting it in a separate shell file lets us skip
# host and target in that order, setting ${machine} to each. Putting it # running autoconf when modifying target-specific information.
# in a separate shell file lets us skip running autoconf when modifying
# host- and target-specific information.
# This file switches on the shell variable ${machine}, and also uses the # This file switches on the shell variable ${machine}, and also uses the
# following shell variables: # following shell variables:
...@@ -2176,11 +2174,7 @@ am33_2.0-*-linux*) ...@@ -2176,11 +2174,7 @@ am33_2.0-*-linux*)
esac esac
# Support for --with-cpu and related options (and a few unrelated options, # Support for --with-cpu and related options (and a few unrelated options,
# too). Only do this if $machine is the target, or we'll try to validate # too).
# the CPU argument against the wrong machine type.
if test "x$pass2done" = xyes
then
case "x$with_cpu" in case "x$with_cpu" in
xyes | xno) xyes | xno)
echo "--with-cpu must be passed a value" 1>&2 echo "--with-cpu must be passed a value" 1>&2
...@@ -2693,18 +2687,3 @@ then ...@@ -2693,18 +2687,3 @@ then
target_cpu_default=$target_cpu_default2 target_cpu_default=$target_cpu_default2
fi fi
fi fi
fi
# Save data on host machine in vars host_xm_file and host_xmake_file.
if test x$pass2done = x ; then
if test x$xm_file != x ; then
host_xm_file=$xm_file
fi
host_xm_defines=$xm_defines
host_xmake_file="$xmake_file"
host_extra_gcc_objs=$extra_gcc_objs
host_extra_objs=$extra_host_objs
host_exeext=$exeext
out_host_hook_obj=$host_hook_obj
pass2done=yes
fi
This diff is collapsed. Click to expand it.
...@@ -965,17 +965,13 @@ fi ...@@ -965,17 +965,13 @@ fi
# Collect build-machine-specific information. # Collect build-machine-specific information.
. ${srcdir}/config.build . ${srcdir}/config.build
# Collect host-machine-specific information.
. ${srcdir}/config.host
target_gtfiles= target_gtfiles=
host_xm_file=
host_xm_defines= # Collect target-machine-specific information.
host_xmake_file= for machine in $target ; do
host_exeext=
# Decode the host machine, then the target machine.
# For the host machine, we save the xm_file variable as host_xm_file;
# then we decode the target machine and forget everything else
# that came from the host machine.
for machine in $host $target; do
. ${srcdir}/config.gcc . ${srcdir}/config.gcc
done done
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment