From: Frank.Heldt@t-online.de (Frank Heldt)
To: egcs mailing list <egcs@cygnus.com>
Subject: Little cleanups for i386 - Target
Date: Sun, 02 Nov 1997 03:47:00 -0000 [thread overview]
Message-ID: <345C6782.8B3E185C@t-online.de> (raw)
Hello everybody,
the attached patches clean up the i386 - Target a little bit.
* in i386.h better readable use of the prozessor TARGET defines
* in i386.md put the define_attr "cpu" at top and delete a
double comment for it
* in i386.md combine identical define_insn with
"&& TARGET_MOVE" and "&& !TARGET_MOVE"
Bye
Frank
--
Frank Heldt
mailto:Frank.Heldt@t-online.de *** Linux, for IQ's higher than 95
mailto:Frank.Heldt@mahr.de
--- i386.h.org Sun Nov 2 09:26:20 1997
+++ i386.h Sun Nov 2 09:31:27 1997
@@ -151,23 +151,23 @@
#define TARGET_MOVE ((target_flags & MASK_NO_MOVE) == 0) /* Don't generate memory->memory */
#define TARGET_PSEUDO ((target_flags & MASK_NO_PSEUDO) == 0) /* Move op's args into pseudos */
+#define TARGET_STACK_PROBE (target_flags & MASK_STACK_PROBE)
+
#define TARGET_386 (ix86_cpu == PROCESSOR_I386)
#define TARGET_486 (ix86_cpu == PROCESSOR_I486)
#define TARGET_PENTIUM (ix86_cpu == PROCESSOR_PENTIUM)
#define TARGET_PENTIUMPRO (ix86_cpu == PROCESSOR_PENTIUMPRO)
-#define TARGET_USE_LEAVE (ix86_cpu == PROCESSOR_I386)
-#define TARGET_PUSH_MEMORY (ix86_cpu == PROCESSOR_I386)
-#define TARGET_ZERO_EXTEND_WITH_AND (ix86_cpu != PROCESSOR_I386 \
- && ix86_cpu != PROCESSOR_PENTIUMPRO)
-#define TARGET_DOUBLE_WITH_ADD (ix86_cpu != PROCESSOR_I386)
-#define TARGET_USE_BIT_TEST (ix86_cpu == PROCESSOR_I386)
-#define TARGET_UNROLL_STRLEN (ix86_cpu != PROCESSOR_I386)
-#define TARGET_USE_Q_REG (ix86_cpu == PROCESSOR_PENTIUM \
- || ix86_cpu == PROCESSOR_PENTIUMPRO)
-#define TARGET_USE_ANY_REG (ix86_cpu == PROCESSOR_I486)
+
+#define TARGET_USE_LEAVE (TARGET_386)
+#define TARGET_PUSH_MEMORY (TARGET_386)
+#define TARGET_ZERO_EXTEND_WITH_AND (TARGET_486 || TARGET_PENTIUM)
+#define TARGET_DOUBLE_WITH_ADD (!TARGET_386)
+#define TARGET_USE_BIT_TEST (TARGET_386)
+#define TARGET_UNROLL_STRLEN (!TARGET_386)
+#define TARGET_USE_Q_REG (TARGET_PENTIUM || TARGET_PENTIUMPRO)
+#define TARGET_USE_ANY_REG (TARGET_486)
+#define TARGET_DEEP_BRANCH_PREDICTION (TARGET_PENTIUMPRO)
#define TARGET_CMOVE (ix86_arch == PROCESSOR_PENTIUMPRO)
-#define TARGET_DEEP_BRANCH_PREDICTION (ix86_cpu == PROCESSOR_PENTIUMPRO)
-#define TARGET_STACK_PROBE (target_flags & MASK_STACK_PROBE)
#define TARGET_SWITCHES \
{ { "80387", MASK_80387 }, \
reply other threads:[~1997-11-02 3:47 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=345C6782.8B3E185C@t-online.de \
--to=frank.heldt@t-online.de \
--cc=egcs@cygnus.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).