public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakub@gcc.gnu.org
To: feeley@iro.umontreal.ca, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, lucier@math.purdue.edu, nobody@gcc.gnu.org
Subject: Re: target/6512: 3.1 segfault in copyprop_hardreg_forward_1 on sparc-sun-solaris2.8
Date: Tue, 30 Apr 2002 02:12:00 -0000	[thread overview]
Message-ID: <20020430091206.24614.qmail@sources.redhat.com> (raw)

Synopsis: 3.1 segfault in copyprop_hardreg_forward_1 on sparc-sun-solaris2.8

State-Changed-From-To: open->analyzed
State-Changed-By: jakub
State-Changed-When: Tue Apr 30 02:12:05 2002
State-Changed-Why:
    Weird. I get on the same code using the same options
    following ICE instead:
    nucleic.c: In function `___H__20_nucleic':
    nucleic.c:21747: insn does not satisfy its constraints:
    (insn 25599 25597 25601 (set (reg:SF 72 %f40 [127])
            (mem:SF (plus:SI (reg/v:SI 18 %l2 [116])
                    (const_int 19 [0x13])) [0 S4 A64])) 85 {*movsf_insn_novis} (nil)
        (nil))
    
    nucleic.c:21747: Internal compiler error in final_scan_insn, at final.c:2551
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6512


             reply	other threads:[~2002-04-30  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30  2:12 jakub [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-02  8:44 davem
2002-04-30  3:36 jakub
2002-04-29 17:46 lucier

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=20020430091206.24614.qmail@sources.redhat.com \
    --to=jakub@gcc.gnu.org \
    --cc=feeley@iro.umontreal.ca \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=lucier@math.purdue.edu \
    --cc=nobody@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).