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/114601] ICE: SIGSEGV in hash_table_mod1 (hash-table.h:344) with -fcondition-coverage -finstrument-functions-once
Date: Tue, 09 Apr 2024 11:49:05 +0000	[thread overview]
Message-ID: <bug-114601-4-TS3UGpzWv0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114601-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114601

--- Comment #2 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:dd78e6a3cbd8f7c678d90ca0d05787faeb2e9c9a

commit r14-9870-gdd78e6a3cbd8f7c678d90ca0d05787faeb2e9c9a
Author: Jørgen Kvalsvik <j@lambda.is>
Date:   Tue Apr 9 13:39:03 2024 +0200

    Guard function->cond_uids access [PR114601]

    PR114601 shows that it is possible to reach the condition_uid lookup
    without having also created the fn->cond_uids, through
    compiler-generated conditionals. Consider all lookups on non-existing
    maps misses, which they are from the perspective of the source code, to
    avoid the NULL access.

            PR gcov-profile/114601

    gcc/ChangeLog:

            * tree-profile.cc (condition_uid): Guard fn->cond_uids access.

    gcc/testsuite/ChangeLog:

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

      parent reply	other threads:[~2024-04-09 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 11:53 [Bug gcov-profile/114601] New: " zsojka at seznam dot cz
2024-04-07  5:09 ` [Bug gcov-profile/114601] " zsojka at seznam dot cz
2024-04-09 11:49 ` 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-114601-4-TS3UGpzWv0@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).