public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/54961] New: [4.8 Regression] FAIL: gfortran.dg/pr48757.f -O (internal compiler error) after revision 192440 Date: Wed, 17 Oct 2012 20:13:00 -0000 [thread overview] Message-ID: <bug-54961-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54961 Bug #: 54961 Summary: [4.8 Regression] FAIL: gfortran.dg/pr48757.f -O (internal compiler error) after revision 192440 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: dominiq@lps.ens.fr CC: hjl.tools@gmail.com, steven@gcc.gnu.org Target: *86*-*-* After revision 192440 (192439 is OK), compiling the test gfortran.dg/pr48757.f on *86*-*-* targets (powerpc*-*-* ones work fine) with '-w -m32 -O2' gives an ICE: /opt/gcc/work/gcc/testsuite/gfortran.dg/pr48757.f: In function 'dfconc': /opt/gcc/work/gcc/testsuite/gfortran.dg/pr48757.f:54:0: internal compiler error: in compensate_edge, at reg-stack.c:2805 END The backtrace is #9 0x000000010059d5ee in rest_of_handle_stack_regs () at ../../p_work/gcc/reg-stack.c:2805 #10 0x0000000100576aef in execute_one_pass (pass=<value optimized out>) at ../../p_work/gcc/passes.c:2320 #11 0x0000000100576efd in execute_pass_list (pass=<value optimized out>) at ../../p_work/gcc/passes.c:2381 #12 0x0000000100576f0f in execute_pass_list (pass=<value optimized out>) at ../../p_work/gcc/passes.c:2382 #13 0x0000000100576f0f in execute_pass_list (pass=<value optimized out>) at ../../p_work/gcc/passes.c:2382 #14 0x0000000100576f0f in execute_pass_list (pass=<value optimized out>) at ../../p_work/gcc/passes.c:2382 #15 0x000000010032f182 in expand_function (node=<value optimized out>) at ../../p_work/gcc/cgraphunit.c:1601 #16 0x00000001003307ba in compile () at ../../p_work/gcc/cgraphunit.c:1705 #17 0x0000000100330d7f in finalize_compilation_unit () at ../../p_work/gcc/cgraphunit.c:2080 #18 0x000000010051c3cd in write_global_declarations () at ../../p_work/gcc/langhooks.c:323 #19 0x0000000100622891 in compile_file () at ../../p_work/gcc/toplev.c:560 #20 0x00000001006242ec in toplev_main (argc=5, argv=0x7fff5fbfd678) at ../../p_work/gcc/toplev.c:1866 #21 0x000000010000a654 in start (pc=<value optimized out>, bases=0x0) at ../../../p_work/libgcc/unwind-dw2-fde.c:1055 Note that there is an additional ICE for gfortran.dg/pr40587.f on i686-pc-linux-gnu (see http://gcc.gnu.org/ml/gcc-testresults/2012-10/msg01902.html ), but I don't know how to reproduce it on x86_64-apple-darwin10.
next reply other threads:[~2012-10-17 20:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 20:13 dominiq at lps dot ens.fr [this message] 2012-10-18 9:56 ` [Bug middle-end/54961] " rguenth at gcc dot gnu.org 2012-10-19 21:58 ` steven at gcc dot gnu.org 2012-10-19 23:18 ` dominiq at lps dot ens.fr 2012-10-27 7:06 ` ubizjak at gmail dot com 2012-10-27 7:11 ` ubizjak at gmail dot com 2012-10-27 13:03 ` steven at gcc dot gnu.org 2012-10-28 11:45 ` steven at gcc dot gnu.org 2012-10-28 11:54 ` steven at gcc dot gnu.org 2012-11-09 22:11 ` [Bug middle-end/54961] " steven at gcc dot gnu.org 2013-07-27 17:03 ` dominiq at lps dot ens.fr 2013-10-05 13:05 ` dominiq at lps dot ens.fr
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-54961-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: 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).