public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45009]  New: [4.6 Regression]: cris-elf libgcc build failure due to fix for PR45003, PR45006
Date: Tue, 20 Jul 2010 21:32:00 -0000	[thread overview]
Message-ID: <bug-45009-507@http.gcc.gnu.org/bugzilla/> (raw)

With revision 162328 cris-elf built.
>From revision 162339 and on, build has failed.  First like in PR45006, then
(162328:162348] as below:

/tmp/hpautotest-gcc1/cris-elf/gccobj/./gcc/xgcc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/./gcc/ -nostdinc
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/newlib/ -isystem
/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/newlib/targ-include -isystem
/tmp/hpautotest-gcc1/gcc/newlib/libc/include
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libgloss/cris
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libgloss/libnosys
-L/tmp/hpautotest-gcc1/gcc/libgloss/cris
-B/tmp/hpautotest-gcc1/cris-elf/pre/cris-elf/bin/
-B/tmp/hpautotest-gcc1/cris-elf/pre/cris-elf/lib/ -isystem
/tmp/hpautotest-gcc1/cris-elf/pre/cris-elf/include -isystem
/tmp/hpautotest-gcc1/cris-elf/pre/cris-elf/sys-include    -g -O2 -march=v32
-mbest-lib-options -O2  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall
-Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition  -isystem ./include   -g  -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc  -I. -I. -I../../.././gcc
-I/tmp/hpautotest-gcc1/gcc/libgcc -I/tmp/hpautotest-gcc1/gcc/libgcc/.
-I/tmp/hpautotest-gcc1/gcc/libgcc/../gcc
-I/tmp/hpautotest-gcc1/gcc/libgcc/../include  -DHAVE_CC_TLS -DUSE_EMUTLS -o
_muldc3.o -MT _muldc3.o -MD -MP -MF _muldc3.dep -DL_muldc3 -c
/tmp/hpautotest-gcc1/gcc/libgcc/../gcc/libgcc2.c \

/tmp/hpautotest-gcc1/gcc/libgcc/../gcc/libgcc2.c: In function '__muldc3':
/tmp/hpautotest-gcc1/gcc/libgcc/../gcc/libgcc2.c:1885:1: internal compiler
error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Author CC:ed, preprocessed code and gdb backtrace to be added.

Since the other report was for ia64, it might matter that the only similarity
with crisv32 (aka. cris-*-* -march=v32) is that neither target takes offseted
expressions as addresses (mem (plus reg ...)), just indirect (mem reg).


-- 
           Summary: [4.6 Regression]: cris-elf libgcc build failure due to
                    fix for PR45003, PR45006
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, build
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: cris-*-* and crisv32-*-*


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


             reply	other threads:[~2010-07-20 21:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 21:32 hp at gcc dot gnu dot org [this message]
2010-07-20 21:38 ` [Bug middle-end/45009] " hp at gcc dot gnu dot org
2010-07-20 21:46 ` hp at gcc dot gnu dot org
2010-07-20 21:56 ` hp at gcc dot gnu dot org
2010-07-20 23:21 ` jakub at gcc dot gnu dot org
2010-07-20 23:30 ` hp at gcc dot gnu dot org
2010-07-20 23:46 ` bernds at gcc dot gnu dot org
2010-07-21  9:10 ` rguenth at gcc dot gnu dot org
2010-07-21 15:54 ` [Bug middle-end/45009] [4.6 Regression]: cris-elf libgcc build failure due to "New optimization for reload_combine" hp at gcc dot gnu dot org
2010-07-21 22:49 ` bernds at gcc dot gnu dot org
2010-07-22  2:43 ` hp 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-45009-507@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).