public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pisa at cmp dot felk dot cvut dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/17810] New: internal compiler error: in verify_local_live_at_start for arm-rtems, arm-linux
Date: Sun, 03 Oct 2004 13:54:00 -0000	[thread overview]
Message-ID: <20041003135420.17810.pisa@cmp.felk.cvut.cz> (raw)

The internal compiler bug on legal code similar to bug 15342.
This bug manifest itself on specific combination of two functions
accessing structure fields and containing more return paths.
If one of the functions is moved into separate file, error seems
to disappear.

arm-linux-gcc --pipe -B/opt/rtems/arm-rtems/csb336/lib/  \
-mcpu=arm920 -mstructure-size-boundary=8 -msoft-float \
-g -Wall  -O3 -g \
-o icetest1.o \
-c icetest1.c

icetest1.c: In function `sui_get_event':
icetest1.c:172: internal compiler error: in verify_local_live_at_start, at
flow.c:546
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.


Experienced on next x86 to ARM GCC builds

GCC 3.4.1 and GCC 3.4.2
./configure --target=arm-rtems --prefix=/usr --with-cpu=arm9 \
  --enable-languages=c,c++ --with-gnu-ld --with-float=soft \
  --enable-threads=rtems --enable-target-optspace --verbose  \
  --disable-nls --host=i586-pc-linux-gnu --with-newlib
Thread model: rtems
gcc version 3.4.2

GCC 3.4.1
./configure --target=arm-linux --prefix=/usr --with-cpu=arm9 \
--enable-languages=c,c++ --with-gnu-ld --enable-shared --enable-symvers=gnu \
--with-float=soft --enable-threads=posix --enable-__cxa_atexit \
--enable-target-optspace --verbose --disable-nls --host=i586-pc-linux-gnu \
--with-headers=/usr/src/linux-2.6.8-rc1-arm/include
Thread model: posix
gcc version 3.4.1

Attached reprocessed sources length reduced form original 3150 lines
to 173 lines. More attempt to simplify code even more lead to compilation
without errors.

-- 
           Summary: internal compiler error: in verify_local_live_at_start
                    for arm-rtems, arm-linux
           Product: gcc
           Version: 3.4.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pisa at cmp dot felk dot cvut dot cz
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i586-pc-linux-gnu
  GCC host triplet: i586-pc-linux-gnu
GCC target triplet: arm-linux


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


             reply	other threads:[~2004-10-03 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-03 13:54 pisa at cmp dot felk dot cvut dot cz [this message]
2004-10-03 13:59 ` [Bug c/17810] " pisa at cmp dot felk dot cvut dot cz
2004-10-03 14:40 ` [Bug rtl-optimization/17810] " pinskia at gcc dot gnu dot org
2004-12-06 23:53 ` [Bug rtl-optimization/17810] [3.4 Regression] " belyshev at lubercy dot com
2005-02-01 19:13 ` joel at gcc dot gnu dot org
2005-03-11 12:45 ` buytenh at wantstofly dot org
2005-05-19 17:50 ` mmitchel at gcc dot gnu dot org
2005-05-20 18:05 ` dank at kegel dot com
2005-09-01 13:09 ` cvs-commit at gcc dot gnu dot org
2005-09-01 13:14 ` rearnsha at gcc dot gnu dot org
2005-09-01 14:55 ` cvs-commit 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=20041003135420.17810.pisa@cmp.felk.cvut.cz \
    --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).