From: "Stefan Dösinger" <stefan@codeweavers.com>
To: gcc@gcc.gnu.org
Cc: Paolo Bonzini <bonzini@gnu.org>
Subject: Re: MSVC hook function prologue
Date: Fri, 04 Sep 2009 11:45:00 -0000 [thread overview]
Message-ID: <200909041345.22952.stefan@codeweavers.com> (raw)
In-Reply-To: <4A9EEBFB.5020709@gnu.org>
Am Thursday 03 September 2009 00:04:43 schrieb Paolo Bonzini:
> (define_insn "vswapmov"
> [(set (match_operand 0 "register_operand" "0")
> (match_operand 1 "register_operand" "1")
> (unspec_volatile [] UNSPECV_VSWAPMOV)]
I ran into a problem with this: build/genattrtab doesn't like the empty
operand list for the unspec_volatile. So after looking at some other insns I
added a const_int 0. There was also a parenthesis missing, which I added
after the "register_operand" "1"), to close the "set".
(define_insn "vswapmov"
[(set (match_operand 0 "register_operand" "0")
(match_operand 1 "register_operand" "1"))
(unspec_volatile [(const_int 0)] UNSPECV_VSWAPMOV)]
""
"movl.s\t%1,%0"
[(set_attr "length" "2")
(set_attr "length_immediate" "0")
(set_attr "modrm" "0")])
This however leads to the following errors and warnings:
build/genrecog ../.././gcc/config/i386/i386.md \
insn-conditions.md > tmp-recog.c
../.././gcc/config/i386/i386.md:15751: operand 0 missing output reload
../.././gcc/config/i386/i386.md:15751: warning: operand 0 missing mode?
../.././gcc/config/i386/i386.md:15751: warning: operand 1 missing mode?
I guess the error isn't about the const_int 0, but about operand 0. Any ideas?
next prev parent reply other threads:[~2009-09-04 11:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 20:46 Stefan Dösinger
2009-09-02 22:05 ` Paolo Bonzini
2009-09-02 22:27 ` Kai Tietz
2009-09-02 23:39 ` Paolo Bonzini
2009-09-03 7:50 ` Stefan Dösinger
2009-09-03 7:52 ` Paolo Bonzini
2009-09-04 11:45 ` Stefan Dösinger [this message]
2009-09-04 11:47 ` Paolo Bonzini
2009-09-04 12:18 ` Stefan Dösinger
2009-09-04 12:23 ` Paolo Bonzini
2009-09-04 12:50 ` Stefan Dösinger
2009-09-04 14:35 ` Stefan Dösinger
2009-09-05 12:43 ` Paolo Bonzini
2009-09-05 13:41 ` Stefan Dösinger
2009-09-06 9:36 ` Andreas Schwab
2009-09-08 20:12 ` Stefan Dösinger
2009-09-05 15:08 Ross Ridge
2009-09-06 9:16 ` Stefan Dösinger
2009-09-07 11:11 ` Paolo Bonzini
2009-09-07 14:27 Ross Ridge
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=200909041345.22952.stefan@codeweavers.com \
--to=stefan@codeweavers.com \
--cc=bonzini@gnu.org \
--cc=gcc@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).