public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at kernel dot crashing dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39765]  New: internal compiler error: in copyprop_hardreg_forward_1
Date: Tue, 14 Apr 2009 15:29:00 -0000	[thread overview]
Message-ID: <bug-39765-1673@http.gcc.gnu.org/bugzilla/> (raw)

This is with 4.4.0-RC-20090414, with --enable-checking=yes,rtl,tree if that
matters.

$ cris-linux-gcc -O2 -S buffer.i 
/home/segher/src/kernel/fs/buffer.c: In function 'block_page_mkwrite':
/home/segher/src/kernel/fs/buffer.c:2409: error: insn does not satisfy its
constraints:
(insn 146 52 147 7 /home/segher/src/kernel/fs/buffer.c:2391 (set (reg/v:SI 1 r1
[orig:30 end ] [30])
        (zero_extend:SI (reg:HI 16 srp))) 58 {zero_extendhisi2} (nil))
/home/segher/src/kernel/fs/buffer.c:2409: internal compiler error: in
copyprop_hardreg_forward_1, at regrename.c:1603

It needs -O2 or -O3 to fail, -Os is not enough.


-- 
           Summary: internal compiler error: in copyprop_hardreg_forward_1
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: segher at kernel dot crashing dot org
  GCC host triplet: x86_64-linux
GCC target triplet: cris-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39765


             reply	other threads:[~2009-04-14 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 15:29 segher at kernel dot crashing dot org [this message]
2009-04-14 15:30 ` [Bug middle-end/39765] " segher at kernel dot crashing dot org
2009-05-24 11:43 ` rguenth at gcc dot gnu dot org

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=bug-39765-1673@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).