public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55381] New: [4.8 Regression]: build fails on cris-elf building libgfortran with host-gcc-4.4, ICE compiling matmul_i1.c
Date: Sun, 18 Nov 2012 16:53:00 -0000	[thread overview]
Message-ID: <bug-55381-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55381
           Summary: [4.8 Regression]: build fails on cris-elf building
                    libgfortran with host-gcc-4.4, ICE compiling
                    matmul_i1.c
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: build, ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: dnovillo@gcc.gnu.org
              Host: x86_64-unknown-linux-gnu
            Target: cris-axis-elf


Created attachment 28724
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28724
cc1 -fpreprocessed matmul_i1.i -melf -g -O2  -std=gnu99 -version
-fcx-fortran-rules -ffunction-sections -fdata-sections -ftree-vectorize
-funroll-loops -o matmul_i1.s

Revision r193595 caused the build for cris-elf to fail as follows, with
host-gcc gcc-4.4.3-4.fc12.x86_64 as well as gcc-4.4.4-10.fc12.x86_64:

libtool: compile:  /tmp/hpautotest-gcc0/cris-elf/gccobj/./gcc/xgcc
-B/tmp/hpautotest-gcc0/cris-elf/gccobj/./gcc/ -nostdinc
-B/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/newlib/ -isystem
/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/newlib/targ-include -isystem
/tmp/hpautotest-gcc0/gcc/newlib/libc/include
-B/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libgloss/cris
-L/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libgloss/libnosys
-L/tmp/hpautotest-gcc0/gcc/libgloss/cris
-B/tmp/hpautotest-gcc0/cris-elf/pre/cris-elf/bin/
-B/tmp/hpautotest-gcc0/cris-elf/pre/cris-elf/lib/ -isystem
/tmp/hpautotest-gcc0/cris-elf/pre/cris-elf/include -isystem
/tmp/hpautotest-gcc0/cris-elf/pre/cris-elf/sys-include -DHAVE_CONFIG_H -I.
-I/tmp/hpautotest-gcc0/gcc/libgfortran
-iquote/tmp/hpautotest-gcc0/gcc/libgfortran/io
-I/tmp/hpautotest-gcc0/gcc/libgfortran/../gcc
-I/tmp/hpautotest-gcc0/gcc/libgfortran/../gcc/config -I../.././gcc
-I/tmp/hpautotest-gcc0/gcc/libgfortran/../libgcc -I../libgcc -std=gnu99 -Wall
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wextra
-Wwrite-strings -fcx-fortran-rules -ffunction-sections -fdata-sections
-ftree-vectorize -funroll-loops -g -O2 -MT matmul_i1.lo -MD -MP -MF
.deps/matmul_i1.Tpo -c
/tmp/hpautotest-gcc0/gcc/libgfortran/generated/matmul_i1.c -o matmul_i1.o
/tmp/hpautotest-gcc0/gcc/libgfortran/generated/matmul_i1.c: In function
'matmul_i1':
/tmp/hpautotest-gcc0/gcc/libgfortran/generated/matmul_i1.c:79:1: internal
compiler error: Illegal instruction
 matmul_i1 (gfc_array_i1 * const restrict retarray, 
 ^
0x85fbc5 crash_signal
        /tmp/hpautotest-gcc0/gcc/gcc/toplev.c:334
0xb37574 analyze_overlapping_iterations
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:2958
0xb381d1 subscript_dependence_tester_1
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:3510
0xb383aa subscript_dependence_tester
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:3561
0xb398b6 compute_affine_dependence(data_dependence_relation*, loop*)
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:4190
0xb3a38f compute_all_dependences(vec<data_reference*, va_heap, vl_ptr>,
vec<data_dependence_relation*, va_heap, vl_ptr>*, vec<loop*, va_heap, vl_ptr>,
bool)
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:4259
0xb3a908 compute_data_dependences_for_loop(loop*, bool, vec<loop*, va_heap,
vl_ptr>*, vec<data_reference*, va_heap, vl_ptr>*,
vec<data_dependence_relation*, va_heap, vl_ptr>*)
        /tmp/hpautotest-gcc0/gcc/gcc/tree-data-ref.c:4545
0xb5de2c vect_analyze_data_refs(_loop_vec_info*, _bb_vec_info*, int*)
        /tmp/hpautotest-gcc0/gcc/gcc/tree-vect-data-refs.c:2975
0x9fcf40 vect_analyze_loop_2
        /tmp/hpautotest-gcc0/gcc/gcc/tree-vect-loop.c:1598
0x9fcf40 vect_analyze_loop(loop*)
        /tmp/hpautotest-gcc0/gcc/gcc/tree-vect-loop.c:1774
0xa1425b vectorize_loops()
        /tmp/hpautotest-gcc0/gcc/gcc/tree-vectorizer.c:114
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [matmul_i1.lo] Error 1
make[3]: Leaving directory
`/tmp/hpautotest-gcc0/cris-elf/gccobj/cris-elf/libgfortran'

Committer of r193595 CC:ed.
Preprocessed matmul_i1.c attached.


             reply	other threads:[~2012-11-18 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 16:53 hp at gcc dot gnu.org [this message]
2012-11-18 17:04 ` [Bug middle-end/55381] " hp at gcc dot gnu.org
2012-11-18 19:48 ` hp at gcc dot gnu.org
2012-11-18 20:17 ` hp at gcc dot gnu.org
2012-11-19  5:46 ` venkataramanan.kumar at amd dot com
2012-11-19 17:50 ` pthaugen at gcc dot gnu.org
2012-11-19 22:08 ` bergner at gcc dot gnu.org
2012-11-20 13:02 ` schwab@linux-m68k.org
2012-11-20 16:51 ` dnovillo at gcc dot gnu.org
2012-11-20 18:12 ` hp at gcc dot gnu.org
2012-11-25 15:55 ` rguenth at gcc dot gnu.org
2012-11-25 21:01 ` hp at gcc dot gnu.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-55381-4@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).