public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linuxl4 at sohu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37742] New: ICE when compile mpich2-1.1.0a1
Date: Mon, 06 Oct 2008 05:18:00 -0000 [thread overview]
Message-ID: <bug-37742-15353@http.gcc.gnu.org/bugzilla/> (raw)
I don't know how to make a preprocessed source,sorry!
$gcc --version
gcc (GCC) 4.4.0 20081005 (experimental)
$cd mpich2-1.1.0a1; mkdir build; cd build
$../configure --prefix=/usr/local/mpich2; make
CC ../../../../src/mpi/coll/opsum.c
../../../../src/mpi/coll/opsum.c: In function 'MPIR_SUM':
../../../../src/mpi/coll/opsum.c:21: internal compiler error: in
vectorizable_load, at tree-vect-transform.c:6675
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [opsum.o] Error 1
make[3]: Leaving directory
`/mnt/usr/fortran/packages/mpich2-1.1.0a1/build/src/mpi/coll'
make[2]: *** [all-redirect] Error 2
make[2]: Leaving directory
`/mnt/usr/fortran/packages/mpich2-1.1.0a1/build/src/mpi'
make[1]: *** [all-redirect] Error 2
make[1]: Leaving directory `/mnt/usr/fortran/packages/mpich2-1.1.0a1/build/src'
--
Summary: ICE when compile mpich2-1.1.0a1
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: linuxl4 at sohu dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37742
next reply other threads:[~2008-10-06 5:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 5:18 linuxl4 at sohu dot com [this message]
2008-10-06 15:56 ` [Bug middle-end/37742] " rguenth at gcc dot gnu dot org
2008-10-06 16:22 ` linuxl4 at sohu dot com
2008-10-06 16:33 ` jakub at gcc dot gnu dot org
2008-10-07 5:03 ` linuxl4 at sohu dot com
2008-10-07 5:08 ` linuxl4 at sohu dot com
2008-10-07 20:47 ` pinskia at gcc dot gnu dot org
2008-10-07 21:05 ` [Bug middle-end/37742] [4.4 Regression] ICE in vectorizer with restrict pointer to struct pinskia at gcc dot gnu dot org
2008-10-07 21:06 ` pinskia at gcc dot gnu dot org
2008-10-09 20:52 ` [Bug middle-end/37742] [4.4 Regression] ICE in vectorizer with restrict pointer reichelt at gcc dot gnu dot org
2008-10-10 7:51 ` rguenth at gcc dot gnu dot org
2008-10-13 21:38 ` pinskia at gcc dot gnu dot org
2008-10-14 20:47 ` rguenth at gcc dot gnu dot org
2008-10-22 3:48 ` mmitchel at gcc dot gnu dot org
2008-11-05 12:18 ` rguenth at gcc dot gnu dot org
2008-11-05 12:19 ` rguenth at gcc dot gnu dot org
2008-11-06 1:24 ` linuxl4 at sohu dot com
2008-11-11 8:14 ` reichelt at gcc dot gnu dot org
2008-11-18 18:27 ` jakub at gcc dot gnu dot org
2008-11-18 20:14 ` jakub at gcc dot gnu dot org
2008-11-19 17:45 ` rguenther at suse dot de
2008-11-20 16:26 ` rguenth at gcc dot gnu dot org
2008-11-20 17:17 ` rguenth at gcc dot gnu dot org
2008-11-20 17:23 ` rguenth at gcc dot gnu dot org
2008-11-21 11:11 ` rguenth at gcc dot gnu dot org
2008-11-28 11:32 ` rguenth at gcc dot gnu dot org
2008-11-28 11:33 ` 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-37742-15353@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).