public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davidsch at fedoraproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102460] New: fortran internal compile error in coverage.c Date: Wed, 22 Sep 2021 18:01:38 +0000 [thread overview] Message-ID: <bug-102460-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460 Bug ID: 102460 Summary: fortran internal compile error in coverage.c Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: davidsch at fedoraproject dot org Target Milestone: --- Created attachment 51495 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51495&action=edit two source files and the compile commands to reproduce the issue the exact version of GCC: gcc-gfortran-11.2.1-1.fc34.x86_64 GNU Fortran (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1) the system type: Fedora 34 the options given when GCC was configured/built: Not sure, Fedoras default the complete command line that triggers the bug: f95 -ftest-coverage -save-temps -c MOD2.f the compiler output (error messages, warnings, etc.): during IPA pass: profile MOD2.f:6:9: 6 | USE MOD1,only : f1 | ^ internal compiler error: in coverage_begin_function, at coverage.c:662 Please submit a full bug report, with preprocessed source if appropriate. the preprocessed file (*.i*) that triggers the bug: No *.i* files are generated. I have attached two source files and the compile commands as attachment. PS: I have observed the same issue on debian with gcc 10, while gcc 8 works. PPS: Without coverage instruction, no error is raised.
next reply other threads:[~2021-09-22 18:01 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-22 18:01 davidsch at fedoraproject dot org [this message] 2021-09-23 12:26 ` [Bug fortran/102460] " davidsch at fedoraproject dot org 2021-09-23 20:10 ` anlauf at gcc dot gnu.org 2021-09-23 20:14 ` anlauf at gcc dot gnu.org 2021-09-27 13:57 ` marxin at gcc dot gnu.org 2021-09-27 13:58 ` marxin at gcc dot gnu.org 2021-09-27 15:35 ` davidsch at fedoraproject dot org 2021-10-01 9:40 ` marxin at gcc dot gnu.org 2021-11-04 10:11 ` marxin 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-102460-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).