From: Richard Sandiford <richard@codesourcery.com>
To: gcc-patches@gcc.gnu.org
Cc: paul@codesourcery.com, nathan@codesourcery.com
Subject: Make arm-wrs-vxworks pass more options down to the assembler
Date: Wed, 04 Jul 2007 09:46:00 -0000 [thread overview]
Message-ID: <87ps38h5n1.fsf@firetop.home> (raw)
arm-wrs-vxworks is the only ARM port to include svr4.h, and its current
ASM_SPEC is based on svr4.h's (with -Q options removed). This means that
we don't pass things like -mfpu down to the assembler, leading to many
assembler errors from Julian's neon tests.
I thought the best fix would be to make VxWorks work like other ARM
ports, so the patch below removes svr4.h from $tm_file. I compared the
-dM output for the current configuration with the -dM output you get
when svr4.h is removed, and added the other differences to vxworks.h.
Tested on arm-wrs-vxworks. OK to install?
Richard
gcc/
* config.gcc (arm-wrs-vxworks): Don't include svr4.h.
* config/vxworks.h (PTRDIFF_TYPE, SIZE_TYPE, TARGET_POSIX_IO): Define.
* config/arm/vxworks.h (ASM_SPEC): Delete.
(SUBTARGET_EXTRA_ASM_SPEC): Define.
Index: gcc/config.gcc
===================================================================
--- gcc/config.gcc 2007-07-04 02:07:24.000000000 -0700
+++ gcc/config.gcc 2007-07-04 02:32:40.000000000 -0700
@@ -700,7 +700,7 @@ arm-semi-aof | armel-semi-aof)
tmake_file="arm/t-arm arm/t-semi"
;;
arm-wrs-vxworks)
- tm_file="elfos.h svr4.h arm/elf.h arm/aout.h ${tm_file} vx-common.h vxworks.h arm/vxworks.h"
+ 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*|strongarm*-*-freebsd*)
Index: gcc/config/vxworks.h
===================================================================
--- gcc/config/vxworks.h 2007-07-04 02:07:24.000000000 -0700
+++ gcc/config/vxworks.h 2007-07-04 02:32:40.000000000 -0700
@@ -106,6 +106,16 @@ #define VXWORKS_GOTT_BASE "__GOTT_BASE__
#undef VXWORKS_GOTT_INDEX
#define VXWORKS_GOTT_INDEX "__GOTT_INDEX__"
+/* As for svr4.h (which not all VxWorks targets include). */
+#undef PTRDIFF_TYPE
+#define PTRDIFF_TYPE "int"
+
+#undef SIZE_TYPE
+#define SIZE_TYPE "unsigned int"
+
+/* Both kernels and RTPs have the facilities required by this macro. */
+#define TARGET_POSIX_IO
+
/* A VxWorks implementation of TARGET_OS_CPP_BUILTINS. */
#define VXWORKS_OS_CPP_BUILTINS() \
do \
Index: gcc/config/arm/vxworks.h
===================================================================
--- gcc/config/arm/vxworks.h 2007-07-04 02:07:24.000000000 -0700
+++ gcc/config/arm/vxworks.h 2007-07-04 02:32:40.000000000 -0700
@@ -76,10 +76,8 @@ #define CC1_SPEC \
#define VXWORKS_ENDIAN_SPEC \
"%{mbig-endian|t4be|t4tbe|t5be|t5tbe|txscalebe:-EB}"
-/* The -Q options from svr4.h aren't understood and must be removed. */
-#undef ASM_SPEC
-#define ASM_SPEC \
- "%{v:-V} %{n} %{T} %{Ym,*} %{Yd,*} %{Wa,*:%*} " VXWORKS_ENDIAN_SPEC
+#undef SUBTARGET_EXTRA_ASM_SPEC
+#define SUBTARGET_EXTRA_ASM_SPEC VXWORKS_ENDIAN_SPEC
#undef LINK_SPEC
#define LINK_SPEC VXWORKS_LINK_SPEC " " VXWORKS_ENDIAN_SPEC
next reply other threads:[~2007-07-04 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 9:46 Richard Sandiford [this message]
2007-07-04 9:48 ` Nathan Sidwell
2007-07-04 9:51 ` Richard Earnshaw
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=87ps38h5n1.fsf@firetop.home \
--to=richard@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@codesourcery.com \
--cc=paul@codesourcery.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).