public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95530] New: [11 regression] ICE in gfortran.dg/equiv_11.f90 after r11-594
Date: Thu, 04 Jun 2020 11:41:51 +0000 [thread overview]
Message-ID: <bug-95530-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95530
Bug ID: 95530
Summary: [11 regression] ICE in gfortran.dg/equiv_11.f90 after
r11-594
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at linux dot vnet.ibm.com
Target Milestone: ---
g:d176184d98a00ab379ae5959aed1908a79995e6b, r11-594
make -k check-gcc-fortran RUNTESTFLAGS=dg.exp=gfortran.dg/equiv_11.f90
FAIL: gfortran.dg/equiv_11.f90 -O (internal compiler error)
FAIL: gfortran.dg/equiv_11.f90 -O (test for excess errors)
# of unexpected failures 2
# of unresolved testcases 2
Executing on host:
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/equiv_11.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O -fsecond-underscore
-ffat-lto-objects -fno-ident -S -o equiv_11.s (timeout = 300)
spawn -ignore SIGHUP
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home3/seurer/gcc/git/build/gcc-test/powerpc64le-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gfortran.dg/equiv_11.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -O -fsecond-underscore -ffat-lto-objects -fno-ident -S
-o equiv_11.s
*** buffer overflow detected ***:
/home3/seurer/gcc/git/build/gcc-test/gcc/testsuite/gfortran/../../f951
terminated
f951: internal compiler error: Aborted
0x10bd92f3 crash_signal
/home/seurer/gcc/git/gcc-test/gcc/toplev.c:328
next reply other threads:[~2020-06-04 11:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 11:41 seurer at linux dot vnet.ibm.com [this message]
2020-06-04 11:55 ` [Bug fortran/95530] " rguenth at gcc dot gnu.org
2020-06-04 17:21 ` anlauf at gcc dot gnu.org
2020-06-04 19:05 ` seurer at linux dot vnet.ibm.com
2020-06-04 20:13 ` seurer at linux dot vnet.ibm.com
2020-06-04 20:17 ` seurer at linux dot vnet.ibm.com
2020-06-04 20:24 ` anlauf at gcc dot gnu.org
2020-06-04 21:06 ` anlauf at gcc dot gnu.org
2020-06-04 21:15 ` seurer at linux dot vnet.ibm.com
2020-06-04 21:18 ` seurer at linux dot vnet.ibm.com
2020-06-04 21:32 ` anlauf at gcc dot gnu.org
2020-06-04 23:31 ` seurer at linux dot vnet.ibm.com
2020-06-05 16:47 ` anlauf at gcc dot gnu.org
2020-06-05 18:30 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:35 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:37 ` anlauf 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-95530-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).