public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "johannes.ziegenbalg at mailbox dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/95847] [9/10/11 Regression] Internal error when processing pFUnit generated files with --coverage
Date: Tue, 03 Nov 2020 16:47:36 +0000 [thread overview]
Message-ID: <bug-95847-4-vETRYNwgWo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95847-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95847
johannes.ziegenbalg at mailbox dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |johannes.ziegenbalg@mailbox
| |.org
--- Comment #2 from johannes.ziegenbalg at mailbox dot org ---
I get the same bug with GCC 10.2.0 in one of my c++ test-cases.
I also tested GCC 11 (GNU Fortran (GCC) 11.0.0 20201029) with the attached file
and got the same result.
After a little digging I found out that the expanded region for 'sbr' starts at
line 8 (`use foo`) and ends at line 4 (`end subroutine sbr`).
But I have no idea why `expand_location` returns line 8.
next prev parent reply other threads:[~2020-11-03 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 19:11 [Bug fortran/95847] New: " olebole at debian dot org
2020-06-23 21:07 ` [Bug gcov-profile/95847] " dominiq at lps dot ens.fr
2020-06-24 6:53 ` [Bug gcov-profile/95847] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-11-03 16:47 ` johannes.ziegenbalg at mailbox dot org [this message]
2020-11-03 16:48 ` johannes.ziegenbalg at mailbox dot org
2020-11-03 18:06 ` marxin at gcc dot gnu.org
2020-11-05 17:08 ` [Bug fortran/95847] " marxin at gcc dot gnu.org
2020-11-05 19:51 ` kargl at gcc dot gnu.org
2020-11-05 22:29 ` burnus at gcc dot gnu.org
2020-11-10 9:31 ` cvs-commit at gcc dot gnu.org
2020-11-12 13:21 ` burnus at gcc dot gnu.org
2020-11-12 14:42 ` cvs-commit at gcc dot gnu.org
2020-11-12 15:41 ` cvs-commit at gcc dot gnu.org
2020-11-12 15:43 ` burnus 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-95847-4-vETRYNwgWo@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).