From: "Jan Beulich" <JBeulich@novell.com>
To: <gcc-patches@gcc.gnu.org>
Subject: bad assembly generated for __builtin_ia32_clflush
Date: Thu, 08 Jul 2004 13:40:00 -0000 [thread overview]
Message-ID: <s0ed4bf8.043@emea1-mh.id2.novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
This fixes one of the problems uncovered by the previously sent ix86
MMX/SSE
testsuite additions.
Jan
2004-07-08 Jan Beulich <jbeulich@novell.com>
* config/i386/i386.md (sse2_clflush): Use correct operand for
clflush.
---
/home/jbeulich/src/gcc/mainline/2004-07-05.10.09/gcc/config/i386/i386.md 2004-07-02
15:20:47.000000000 +0200
+++ 2004-07-05.10.09/gcc/config/i386/i386.md 2004-07-07
15:26:23.029339392 +0200
@@ -23906,7 +23906,7 @@
[(unspec_volatile [(match_operand 0 "address_operand" "p")]
UNSPECV_CLFLUSH)]
"TARGET_SSE2"
- "clflush %0"
+ "clflush\t%a0"
[(set_attr "type" "sse")
(set_attr "memory" "unknown")])
[-- Attachment #2: gcc-mainline-x86-clflush.patch --]
[-- Type: application/octet-stream, Size: 704 bytes --]
This fixes one of the problems (bad assembler code generated for
__builtin_ia32_clflush) uncovered by the previously sent ix86 MMX/SSE
testsuite additions.
Jan
2004-07-08 Jan Beulich <jbeulich@novell.com>
* config/i386/i386.md (sse2_clflush): Use correct operand for clflush.
--- /home/jbeulich/src/gcc/mainline/2004-07-05.10.09/gcc/config/i386/i386.md 2004-07-02 15:20:47.000000000 +0200
+++ 2004-07-05.10.09/gcc/config/i386/i386.md 2004-07-07 15:26:23.029339392 +0200
@@ -23906,7 +23906,7 @@
[(unspec_volatile [(match_operand 0 "address_operand" "p")]
UNSPECV_CLFLUSH)]
"TARGET_SSE2"
- "clflush %0"
+ "clflush\t%a0"
[(set_attr "type" "sse")
(set_attr "memory" "unknown")])
next reply other threads:[~2004-07-08 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 13:40 Jan Beulich [this message]
2004-07-10 1:29 ` 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=s0ed4bf8.043@emea1-mh.id2.novell.com \
--to=jbeulich@novell.com \
--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).