public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/114599] [14 Regression] ICE: SIGSEGV in bitmap_set_bit(bitmap_head*, int) (bitmap.cc:975) with -O2 -fcondition-coverage Date: Tue, 09 Apr 2024 07:58:00 +0000 [thread overview] Message-ID: <bug-114599-4-oiHfYiZhNV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114599 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by J?rgen Kvalsvik <jkv@gcc.gnu.org>: https://gcc.gnu.org/g:2daeb89d6f025d6daf7e560575863b3280120be8 commit r14-9863-g2daeb89d6f025d6daf7e560575863b3280120be8 Author: Jørgen Kvalsvik <j@lambda.is> Date: Mon Apr 8 09:28:27 2024 +0200 Add tree-inlined gconds to caller cond->expr map Properly add the condition -> expression mapping of inlined gconds from the caller into the callee map. This is a fix for PR114599 that works beyond fixing the segfault, as the previous fixed copied references to the source gconds, not the deep copied ones that end up in the calle body. The new tests checks this, both in the case of a calle without conditions (which triggered the segfault), and a test that shows that conditions are properly mapped, and not mixed. PR middle-end/114599 gcc/ChangeLog: * tree-inline.cc (copy_bb): Copy cond_uids into callee. (prepend_lexical_block): Remove outdated comment. (add_local_variables): Remove bad cond_uids copy. gcc/testsuite/ChangeLog: * gcc.misc-tests/gcov-19.c: New test.
prev parent reply other threads:[~2024-04-09 7:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-05 4:19 [Bug ipa/114599] New: " zsojka at seznam dot cz 2024-04-05 8:02 ` [Bug gcov-profile/114599] [14 Regression] " rguenth at gcc dot gnu.org 2024-04-05 8:04 ` rguenth at gcc dot gnu.org 2024-04-05 9:13 ` cvs-commit at gcc dot gnu.org 2024-04-05 9:13 ` rguenth at gcc dot gnu.org 2024-04-05 13:42 ` hjl.tools at gmail dot com 2024-04-05 13:43 ` hjl.tools at gmail dot com 2024-04-06 11:11 ` cvs-commit at gcc dot gnu.org 2024-04-08 6:55 ` rguenth at gcc dot gnu.org 2024-04-09 7:58 ` cvs-commit at gcc dot gnu.org [this message]
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-114599-4-oiHfYiZhNV@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).