From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: thomas@schwinge.name, rth@redhat.com, jh@suse.cz, ubizjak@gmail.com
Subject: Clean up i386/gnu.h
Date: Mon, 11 Apr 2011 19:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1104111926470.32677@digraph.polyomino.org.uk> (raw)
Now that gnu-user*.h and linux*.h config headers have more or less the
proper contents, the next stage in stopping non-Linux-kernel-based
targets from using linux*.h is to get the correct contents into the
headers for the non-Linux-kernel-based targets. This patch does so
for i386/gnu.h. GNU_USER_LINK_EMULATION is defined (to the same value
as in i386/linux.h, so just duplicating that definition until this
target stops using i386/linux.h). CPP_SPEC, duplicating the
i386/gnu-user.h definition, is removed, as is CC1_SPEC (missing
-profile support from the gnu-user version, which should be there
judging by -profile support in other specs). ENDFILE_SPEC is also
removed; the gnu-user version has additional support for crtfastmath.o
and crtprec*.o and since libgcc/config.host indicates those files get
built for GNU/Hurd, the gnu-user spec that uses those files should be
used for GNU/Hurd.
Tested building cc1 and xgcc for cross to i686-gnu. OK to commit?
2011-04-11 Joseph Myers <joseph@codesourcery.com>
* config/i386/gnu.h (GNU_USER_LINK_EMULATION): Define.
(CPP_SPEC, CC1_SPEC, ENDFILE_SPEC): Remove.
Index: gcc/config/i386/gnu.h
===================================================================
--- gcc/config/i386/gnu.h (revision 172273)
+++ gcc/config/i386/gnu.h (working copy)
@@ -20,15 +20,11 @@ You should have received a copy of the G
along with GCC. If not, see <http://www.gnu.org/licenses/>.
*/
+#define GNU_USER_LINK_EMULATION "elf_i386"
+
#undef GNU_USER_DYNAMIC_LINKER
#define GNU_USER_DYNAMIC_LINKER "/lib/ld.so"
-#undef CPP_SPEC
-#define CPP_SPEC "%{pthread:-D_REENTRANT} %{posix:-D_POSIX_SOURCE}"
-
-#undef CC1_SPEC
-#define CC1_SPEC "%(cc1_cpu)"
-
#undef STARTFILE_SPEC
#if defined HAVE_LD_PIE
#define STARTFILE_SPEC \
@@ -40,10 +36,6 @@ along with GCC. If not, see <http://www
crti.o%s %{static:crtbeginT.o%s;shared|pie:crtbeginS.o%s;:crtbegin.o%s}"
#endif
-#undef ENDFILE_SPEC
-#define ENDFILE_SPEC \
- "%{shared|pie:crtendS.o%s;:crtend.o%s} crtn.o%s"
-
/* FIXME: Is a Hurd-specific fallback mechanism necessary? */
#undef MD_UNWIND_SUPPORT
--
Joseph S. Myers
joseph@codesourcery.com
next reply other threads:[~2011-04-11 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 19:28 Joseph S. Myers [this message]
2011-04-11 21:16 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1104111926470.32677@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=rth@redhat.com \
--cc=thomas@schwinge.name \
--cc=ubizjak@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).