From: "'Rask Ingemann Lambertsen'" <rask@sygehus.dk>
To: "Balaji V. Iyer" <bviyer@ncsu.edu>
Cc: gcc@gcc.gnu.org, openrisc@opencores.org
Subject: Re: Help with another constraint
Date: Mon, 10 Dec 2007 17:31:00 -0000 [thread overview]
Message-ID: <20071210171542.GL17368@sygehus.dk> (raw)
In-Reply-To: <000d01c83a81$85462ca0$33160e98@ece.ncsu.edu>
On Sun, Dec 09, 2007 at 11:35:32AM -0500, Balaji V. Iyer wrote:
> Hello Rask,
> I am not understanding your response, can you clarify it for me?
>
> As per the question about the error message above?
>
> ../../gcc-4.0.2/gcc/libgcc2.c -o libgcc/./_negdi2.o
> ../../gcc-4.0.2/gcc/libgcc2.c: In function '__negdi2':
> ../../gcc-4.0.2/gcc/libgcc2.c:72: error: insn does not satisfy its
> constraints:
I think this is misleading you. It seems likely that the problem is with
the predicate and not the constraint.
> (insn 15 13 16 (set (mem:SI (plus:SI (reg/f:SI 2 r2)
^^^
This has to be a register, doesn't it? If so, use -fdump-rtl-all and look
at the dump files to see where it goes wrong.
> (const_int -28 [0xffffffe4])) [0 D.1256+0 S4 A32])
> (neg:SI (reg:SI 3 r3 [orig:80 D.1255 ] [80]))) 38 {negsi2} (nil)
> (nil))
Please also post your negsi2 pattern.
--
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year
next prev parent reply other threads:[~2007-12-10 17:16 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' [this message]
2007-12-12 5:13 ` Balaji V. Iyer
2007-12-12 12:53 ` Revital1 Eres
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=20071210171542.GL17368@sygehus.dk \
--to=rask@sygehus.dk \
--cc=bviyer@ncsu.edu \
--cc=gcc@gcc.gnu.org \
--cc=openrisc@opencores.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).