public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: gcc-patches@gcc.gnu.org
Subject: Convert stormy16 to not use CPP_PREDEFINES
Date: Sat, 08 Mar 2003 15:35:00 -0000	[thread overview]
Message-ID: <20030308153512.GC1686@daikokuya.co.uk> (raw)

I've committed this, but I couldn't test it as the target
doesn't currently build.  The change is obvious enough, though.

Neil.

	* config/stormy16/stormy16.h (TARGET_CPU_CPP_BUILTINS): Use in
	preference to CPP_PREDEFINES.

Index: stormy16.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/stormy16/stormy16.h,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -p -r1.69 -r1.70
--- stormy16.h	6 Mar 2003 20:03:49 -0000	1.69
+++ stormy16.h	8 Mar 2003 15:32:45 -0000	1.70
@@ -67,7 +67,10 @@ Boston, MA 02111-1307, USA.  */
 \f
 /* Run-time target specifications */
 
-#define CPP_PREDEFINES "-Dxstormy16 -Amachine=xstormy16"
+#define TARGET_CPU_CPP_BUILTINS() do {	\
+  builtin_define_std ("xstormy16");	\
+  builtin_assert ("machine=xstormy16");	\
+} while (0)
 
 /* This declaration should be present.  */
 extern int target_flags;

                 reply	other threads:[~2003-03-08 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030308153512.GC1686@daikokuya.co.uk \
    --to=neil@daikokuya.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    /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).