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: Sat, 06 Apr 2024 11:11:02 +0000	[thread overview]
Message-ID: <bug-114599-4-f60oqLsHlm@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 #7 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:c6892a430a9752aea167265621c3ae7a3e11159f

commit r14-9819-gc6892a430a9752aea167265621c3ae7a3e11159f
Author: Jørgen Kvalsvik <j@lambda.is>
Date:   Fri Apr 5 21:42:07 2024 +0200

    Copy condition->expr map when inlining [PR114599]

    When a function is tree-inlined, copy the condition -> expression mapping
    from the inlined function into the caller, shifted so uids are not
    mixed.  Tree inlining was always problematic under condition coverage -
    either through a nullptr dereference (triggered by the test case), or
    through quietly mixing caller conditions with the callee conditions.

            PR middle-end/114599

    gcc/ChangeLog:

            * tree-inline.cc (add_local_variables): Copy cond_uids mappings.

    gcc/testsuite/ChangeLog:

            * gcc.misc-tests/gcov-pr114599.c: New test.

  parent reply	other threads:[~2024-04-06 11:11 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 [this message]
2024-04-08  6:55 ` rguenth at gcc dot gnu.org
2024-04-09  7:58 ` 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-114599-4-f60oqLsHlm@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).