public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc@gcc.gnu.org
Subject: Question regarding ICE in instantiate_virtual_regs_1, at function.c:3880
Date: Tue, 11 Dec 2001 15:18:00 -0000	[thread overview]
Message-ID: <200112112315.fBBNFjRR018504@hiauly1.hia.nrc.ca> (raw)

I am seeing a number of ICEs in the testsuite in instantiate_virtual_regs_1,
at function.c:3880, on vax-dec-ultrix4.3 with the main.  The first one that
I looked at occurs on this insn in gcc.c-torture/compile/991213-1.c:

(insn 22 21 23 (set (mem/f:DF (plus:SI (reg/f:SI 17 virtual-stack-vars)
                (const_int -20 [0xffffffec])) [0 arg+8 S8 A64])
	(subreg:DF (mem:DC (plus:SI (mult:SI (reg:SI 21)
			(const_int 16 [0x10]))
		    (mem/f:SI (reg/f:SI 16 virtual-incoming-args) [0 t+0 S4 A32])) [0 S16 A32]) 8)) -1 (nil)
   (nil))

It appears that instantiate_virtual_regs_1 ICEs because general_operand
(see recog.c:966) doesn't allow a SUBREG with a nonzero SUBREG_BYTE and
this causes the first instantiation to fail.  Should this insn have been
created in the first place if there is this limitation on SUBREG MEMs?

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

             reply	other threads:[~2001-12-11 23:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 15:18 John David Anglin [this message]
     [not found] <no.id>
2001-12-12  8:49 ` John David Anglin
2001-12-12 15:58   ` John David Anglin
2001-12-13  1:28     ` Jan Hubicka
2001-12-13 11:57       ` John David Anglin
2001-12-13 12:05         ` Jan Hubicka
2001-12-14 13:26           ` John David Anglin

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=200112112315.fBBNFjRR018504@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --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).