public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66073] [6 Regression] 465.tonto in SPEC CPU 2006 failed to build Date: Fri, 08 May 2015 16:52:00 -0000 [thread overview] Message-ID: <bug-66073-4-4vS5DzspzB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66073-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66073 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-05-08 CC| |tkoenig at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- It is caused by r222864: gfortran -c -o cluster.fppized.o -O2 -ffast-math cluster.fppized.f90 cluster.fppized.f90:1199:0: in_pos = matmul(self%crystal%unitcell%direct_matrix,self%geometry(:,in_atom)) 1 internal compiler error: in gfc_walk_array_ref, at fortran/trans-array.c:8900 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. specmake: *** [cluster.fppized.o] Error 1 specmake: *** Waiting for unfinished jobs....
next prev parent reply other threads:[~2015-05-08 16:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-08 13:17 [Bug fortran/66073] New: " hjl.tools at gmail dot com 2015-05-08 15:25 ` [Bug fortran/66073] " rguenth at gcc dot gnu.org 2015-05-08 16:52 ` hjl.tools at gmail dot com [this message] 2015-05-08 16:56 ` dominiq at lps dot ens.fr 2015-05-08 17:53 ` hjl.tools at gmail dot com
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-66073-4-4vS5DzspzB@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: linkBe 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).