From: DJ Delorie <dj@redhat.com>
To: gcc@gcc.gnu.org
Subject: hard_regno_nregs == 0 ?
Date: Tue, 08 Jan 2008 20:13:00 -0000 [thread overview]
Message-ID: <200801082013.m08KDLeU011644@greed.delorie.com> (raw)
In rtlanal.c we have these lines:
nregs_ymode = hard_regno_nregs[xregno][ymode];
...
&& (GET_MODE_SIZE (ymode) % nregs_ymode) == 0)
The m32c cc1 crashes here because xregno is 1 and ymode is QI, and
register 1 cannot hold a QI value (there are no QImode ops that take
that register), so hard_regno_nregs[1][QI] is zero, which causes a
SIGFPE.
Which assumption is wrong? That hard_regno_nregs can be zero (m32c),
or that hard_regno_nregs will never be zero (rtlanal)?
next reply other threads:[~2008-01-08 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 20:13 DJ Delorie [this message]
2008-01-09 16:43 ` Ian Lance Taylor
2008-01-09 16:47 ` DJ Delorie
2008-01-09 16:56 ` Ian Lance Taylor
2008-01-09 20:18 ` Jim Wilson
2008-01-09 19:27 ` Jim Wilson
2008-01-09 20:39 ` DJ Delorie
2008-01-09 21:48 ` Paul Brook
2008-01-09 22:02 ` DJ Delorie
2008-01-11 0:12 ` Jim Wilson
2008-01-11 0:16 ` DJ Delorie
2008-01-12 0:48 ` Jim Wilson
2008-01-21 22:41 ` DJ Delorie
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=200801082013.m08KDLeU011644@greed.delorie.com \
--to=dj@redhat.com \
--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).