public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/97652] [11 Regression] New gfortran.dg/pdt_14.f03 failure after g:617695cdc2b3d950f1e4deb5ea85d5cc302943f4
Date: Mon, 02 Nov 2020 13:58:35 +0000 [thread overview]
Message-ID: <bug-97652-4-DkmCOKBXsr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97652-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97652
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Oh, btw:
> /home/rguenther/obj-gcc2-g/gcc/testsuite/gfortran/../../gfortran -B/home/rguenther/obj-gcc2-g/gcc/testsuite/gfortran/../../ -B/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libgfortran/ /home/rguenther/src/gcc2/gcc/testsuite/gfortran.dg/pdt_14.f03 -fdiagnostics-plain-output -fdiagnostics-plain-output -O2 -pedantic-errors -B/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libgfortran/.libs -L/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libgfortran/.libs -L/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libgfortran/.libs -L/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libatomic/.libs -B/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libquadmath/.libs -L/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libquadmath/.libs -L/home/rguenther/obj-gcc2-g/x86_64-pc-linux-gnu/./libquadmath/.libs -lm -o ./pdt_14.exe -fno-ipa-cp -fno-ipa-vrp -fno-ipa-icf -fdump-ipa-all
during IPA pass: inline
dump file: ./pdt_14.f03.081i.inline
/home/rguenther/src/gcc2/gcc/testsuite/gfortran.dg/pdt_14.f03:85:0: internal
compiler error: Segmentation fault
0x14896d3 crash_signal
/home/rguenther/src/gcc2/gcc/toplev.c:330
0xd26c14 cgraph_edge::redirect_call_stmt_to_callee(cgraph_edge*)
/home/rguenther/src/gcc2/gcc/cgraph.c:1513
0x156e11a redirect_all_calls(copy_body_data*, basic_block_def*)
/home/rguenther/src/gcc2/gcc/tree-inline.c:2963
0x156e906 copy_cfg_body
/home/rguenther/src/gcc2/gcc/tree-inline.c:3118
0x156f0e5 copy_body
/home/rguenther/src/gcc2/gcc/tree-inline.c:3294
0x1574028 expand_call_inline
/home/rguenther/src/gcc2/gcc/tree-inline.c:5084
0x1574dca gimple_expand_calls_inline
next prev parent reply other threads:[~2020-11-02 13:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 8:05 [Bug fortran/97652] New: New pdt14 " hubicka at gcc dot gnu.org
2020-10-31 8:18 ` [Bug fortran/97652] " hubicka at gcc dot gnu.org
2020-11-02 11:30 ` hubicka at gcc dot gnu.org
2020-11-02 13:39 ` [Bug fortran/97652] [11 Regression] New gfortran.dg/pdt_14.f03 " rguenth at gcc dot gnu.org
2020-11-02 13:48 ` rguenth at gcc dot gnu.org
2020-11-02 13:56 ` rguenth at gcc dot gnu.org
2020-11-02 13:58 ` rguenth at gcc dot gnu.org [this message]
2020-11-02 14:25 ` rguenth at gcc dot gnu.org
2020-11-02 14:27 ` hubicka at ucw dot cz
2020-11-02 14:29 ` [Bug ipa/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:29 ` rguenth at gcc dot gnu.org
2020-11-02 14:32 ` hubicka at ucw dot cz
2020-11-02 14:51 ` [Bug fortran/97652] " rguenth at gcc dot gnu.org
2020-11-02 14:52 ` rguenth at gcc dot gnu.org
2020-11-03 7:25 ` rguenth at gcc dot gnu.org
2020-11-03 11:15 ` rguenth at gcc dot gnu.org
2020-11-06 7:27 ` cvs-commit at gcc dot gnu.org
2020-11-06 13:01 ` rguenth at gcc dot gnu.org
2020-11-06 15:32 ` cvs-commit at gcc dot gnu.org
2020-11-06 16:57 ` cvs-commit 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-97652-4-DkmCOKBXsr@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).