From: Revital1 Eres <ERES@il.ibm.com>
To: "Balaji V. Iyer" <bviyer@ncsu.edu>
Cc: gcc@gcc.gnu.org, openrisc@opencores.org,
"'Rask Ingemann Lambertsen'" <rask@sygehus.dk>
Subject: RE: Help with another constraint
Date: Wed, 12 Dec 2007 12:53:00 -0000 [thread overview]
Message-ID: <OF55758D8C.871C0678-ONC22573AF.003D4671-C22573AF.00433D08@il.ibm.com> (raw)
In-Reply-To: <002601c83c7c$b3763960$33160e98@ece.ncsu.edu>
Hello,
I think you should add the pair of constraints m and I respectively to
the description of the instruction in your md file (and a relevant
case 8 to handle such instruction), i.e.:
(define_insn "movqi"
- [(set (match_operand:QI 0 "nonimmediate_operand" "=p,q,m,m,p,q,p,q")
- (match_operand:QI 1 "general_operand" "m,m,p,q,p,q,I,I"))]
+ [(set (match_operand:QI 0 "nonimmediate_operand" "=p,q,m,m,p,q,p,q,m")
+ (match_operand:QI 1 "general_operand" "m,m,p,q,p,q,I,I,I"))]
""
"*
switch(which_alternative)
@@ -17,6 +17,8 @@
case 6:
case 7:
return \"l.addi \\t%0,r0,%1\\t # move immediate\";,
+ case 8:
+ return ...;
default:
return \"invalid alternative\";
}
It seems that the pair m and I is missing (which indicate the memory =
constant instruction). You could look for which_alternative variable
in GCC internals for more details on this.
Revital
next prev parent reply other threads:[~2007-12-12 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 13:07 Balaji V. Iyer
2007-12-09 14:28 ` Rask Ingemann Lambertsen
2007-12-09 22:06 ` Balaji V. Iyer
2007-12-10 17:31 ` 'Rask Ingemann Lambertsen'
2007-12-12 5:13 ` Balaji V. Iyer
2007-12-12 12:53 ` Revital1 Eres [this message]
2007-12-12 13:01 ` Balaji V. Iyer
2007-12-12 14:35 ` Dave Korn
2007-12-12 17:50 ` Rask Ingemann Lambertsen
2007-12-16 14:24 ` Hans-Peter Nilsson
2007-12-16 17:18 ` Hans-Peter Nilsson
2007-12-12 15:21 ` 'Rask Ingemann Lambertsen'
2007-12-17 18:38 ` Rask Ingemann Lambertsen
2007-12-17 20:31 ` Balaji V. Iyer
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=OF55758D8C.871C0678-ONC22573AF.003D4671-C22573AF.00433D08@il.ibm.com \
--to=eres@il.ibm.com \
--cc=bviyer@ncsu.edu \
--cc=gcc@gcc.gnu.org \
--cc=openrisc@opencores.org \
--cc=rask@sygehus.dk \
/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).