public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "M R Swami Reddy" <MR.Swami.Reddy@nsc.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
		"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: [Fwd: ICE with crx-elf-gcc 4.5.0 20090407]
Date: Tue, 07 Apr 2009 12:55:00 -0000	[thread overview]
Message-ID: <49DB4D1F.2050107@nsc.com> (raw)

Below issue observed with -O3 -funroll-all-loops option.

-------- Original Message --------
Subject: ICE with crx-elf-gcc 4.5.0 20090407
Date: Tue, 07 Apr 2009 17:42:44 +0530
From: M R Swami Reddy <MR.Swami.Reddy@nsc.com>
To: gcc-help@gcc.gnu.org <gcc-help@gcc.gnu.org>,  GCC Patches 
<gcc-patches@gcc.gnu.org>

Hello,

Built the crx-elf-gcc tools using the trunk sources. With this gcc,
below ICE observed. Is it regression?

NOTE: crx-elf-gcc 4.2.4 no error seen.
========================================================
error: insn does not satisfy its constraints:
(insn 8 119 130 2 /scratch/user/swami/gdb/testing/plum500/conform/c67.c:149 (set
  (mem/c/i:SI (post_modify:SI (reg:SI 3 r3)
                 (plus:SI (reg:SI 3 r3)
                     (const_int 8 [0x8]))) [3 x1+0 S4 A32])
         (const_int 0 [0x0])) 91 {movsi_store} (expr_list:REG_INC (reg:SI 3 r3)
         (nil)))
/scratch/c67.c:187: internal compiler error: in copyprop_hardreg_forward_1, at
regrename.c:1603
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

bash-2.05b$ crx-elf-gcc -v
Using built-in specs.
Target: crx-elf
Configured with: /local/kafi/common/users/swami/crx/trunk/configure
--prefix=/local/kafi/common/users/swami/crx/release/linux --target=crx-elf
--disable-nls --enable-languages=c,c++ --disable-libssp
--with-gmp=/local/kafi/common/users/swami/crx/release/linux
--with-mpfr=/local/kafi/common/users/swami/crx/release/linux
Thread model: single
gcc version 4.5.0 20090407 (experimental) (GCC)
=======

Thanks
Swami


                 reply	other threads:[~2009-04-07 12:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49DB4D1F.2050107@nsc.com \
    --to=mr.swami.reddy@nsc.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc-patches@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).