public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114604] New: Ranger allocates from uninitialized bitmap_default_obstack
Date: Fri, 05 Apr 2024 13:06:12 +0000	[thread overview]
Message-ID: <bug-114604-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114604
           Summary: Ranger allocates from uninitialized
                    bitmap_default_obstack
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org
  Target Milestone: ---

Visible at least from gcc.dg/torture/pr52429.c when instrumenting
bitmap_alloc with

bitmap
bitmap_alloc (bitmap_obstack *bit_obstack MEM_STAT_DECL)
{
  bitmap map;

  if (!bit_obstack)
    {
      gcc_assert (bitmap_default_obstack_depth > 0);
      bit_obstack = &bitmap_default_obstack;

gcc.dg/torture/pr52429.c:24:1: internal compiler error: in bitmap_alloc, at
bitmap.cc:785^M
0xf3d95b bitmap_alloc(bitmap_obstack*)^M
        /home/rguenther/src/trunk/gcc/bitmap.cc:785^M
0x2e89005 update_list::update_list()^M
        /home/rguenther/src/trunk/gcc/gimple-range-cache.cc:900^M
0x2e893a2 ranger_cache::ranger_cache(int, bool)^M
        /home/rguenther/src/trunk/gcc/gimple-range-cache.cc:976^M
0x2e815a9 gimple_ranger::gimple_ranger(bool)^M
        /home/rguenther/src/trunk/gcc/gimple-range.cc:44^M
0x2e83e88 enable_ranger(function*, bool)^M
        /home/rguenther/src/trunk/gcc/gimple-range.cc:693^M
0x13bfd62 ipa_analyze_node(cgraph_node*)^M
        /home/rguenther/src/trunk/gcc/ipa-prop.cc:3191^M

             reply	other threads:[~2024-04-05 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 13:06 rguenth at gcc dot gnu.org [this message]
2024-04-05 13:10 ` [Bug middle-end/114604] " rguenth at gcc dot gnu.org
2024-04-05 13:14 ` rguenth at gcc dot gnu.org
2024-04-08  9:49 ` rguenth at gcc dot gnu.org
2024-04-09  6:46 ` cvs-commit at gcc dot gnu.org
2024-04-09  6:50 ` rguenth 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-114604-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: 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).