public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64688] [5 Regression] internal compiler error: Max. number of generated reload insns per insn is achieved (90)
Date: Sat, 24 Jan 2015 14:40:00 -0000 [thread overview]
Message-ID: <bug-64688-4-zI8oOQbyIm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64688-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64688
--- Comment #11 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Created attachment 34566
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34566&action=edit
reduced testcase
trippels@gcc20 % g++ -c -O3 -std=c++11 -march=westmere performance.ii
performance.ii: In function ‘void performance_testtest_method()’:
performance.ii:133:1: internal compiler error: Max. number of generated reload
insns per insn is achieved (90)
}
^
0xb6e6e0 lra_constraints(bool)
../../gcc/gcc/lra-constraints.c:4335
0xb5b041 lra(_IO_FILE*)
../../gcc/gcc/lra.c:2292
0xb18da9 do_reload
../../gcc/gcc/ira.c:5418
0xb18da9 execute
../../gcc/gcc/ira.c:5589
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.
>From gcc-bugs-return-474720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 24 14:47:38 2015
Return-Path: <gcc-bugs-return-474720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15567 invoked by alias); 24 Jan 2015 14:47:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15512 invoked by uid 48); 24 Jan 2015 14:47:34 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64771] ICE(segfault) when passing coarrays around; ICE in gfc_zero_size_array in arith.c:1637
Date: Sat, 24 Jan 2015 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc short_desc
Message-ID: <bug-64771-4-8R6N84qP34@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg02714.txt.bz2
Content-length: 1431
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd771
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|ice-on-invalid-code |ice-on-valid-code
CC| |fanfarillo.gcc at gmail dot com,
| |tkoenig at gcc dot gnu.org
Summary|ICE on invalid around |ICE(segfault) when passing
|check_dummy_characteristics |coarrays around; ICE in
|/ gfc_zero_size_array |gfc_zero_size_array in
| |arith.c:1637
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Fails here the same way, and should be the same reason:
https://gcc.gnu.org/ml/fortran/2015-01/msg00145.html - besides, the test case
is shorter and valid:
program cg
implicit none
integer reduce_recv_starts(2)[0:*]
interface
subroutine conj_grad (reduce_recv_starts)
integer reduce_recv_starts(2)[0:*]
end subroutine
end interface
call conj_grad (reduce_recv_starts)
end
subroutine conj_grad (reduce_recv_starts)
implicit none
integer reduce_recv_starts(2)[0:*]
end ! end of routine conj_grad
next prev parent reply other threads:[~2015-01-24 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:34 [Bug target/64688] New: " trippels at gcc dot gnu.org
2015-01-20 16:50 ` [Bug target/64688] [5 Regression] " jakub at gcc dot gnu.org
2015-01-21 20:52 ` vmakarov at gcc dot gnu.org
2015-01-22 8:09 ` ubizjak at gmail dot com
2015-01-22 14:45 ` uros at gcc dot gnu.org
2015-01-22 20:26 ` uros at gcc dot gnu.org
2015-01-23 23:05 ` jakub at gcc dot gnu.org
2015-01-24 10:31 ` trippels at gcc dot gnu.org
2015-01-24 10:40 ` trippels at gcc dot gnu.org
2015-01-24 10:42 ` ubizjak at gmail dot com
2015-01-24 14:40 ` trippels at gcc dot gnu.org [this message]
2015-01-25 16:00 ` [Bug rtl-optimization/64688] " ubizjak at gmail dot com
2015-01-30 22:23 ` [Bug rtl-optimization/64688] [4.9/5 " vmakarov at gcc dot gnu.org
2015-01-31 2:48 ` law at redhat dot com
2015-01-31 7:18 ` trippels at gcc dot gnu.org
2015-01-31 8:53 ` [Bug rtl-optimization/64688] [4.9 " jakub at gcc dot gnu.org
2015-02-03 16:31 ` law at redhat dot com
2015-02-04 18:26 ` vmakarov at gcc dot gnu.org
2015-03-27 20:13 ` vmakarov at gcc dot gnu.org
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-04-22 12:22 ` ubizjak 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-64688-4-zI8oOQbyIm@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).