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 middle-end/114604] Ranger allocates from uninitialized bitmap_default_obstack
Date: Tue, 09 Apr 2024 06:46:40 +0000	[thread overview]
Message-ID: <bug-114604-4-BvoUwCwLot@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114604-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:d76df699b8ff792575e9df4d214c21fed0ed3b6b

commit r14-9855-gd76df699b8ff792575e9df4d214c21fed0ed3b6b
Author: Richard Biener <rguenther@suse.de>
Date:   Mon Apr 8 10:50:18 2024 +0200

    middle-end/114604 - ranger allocates bitmap without initialized obstack

    The following fixes ranger bitmap allocation when invoked from IPA
    context where the global bitmap obstack possibly isn't initialized.
    Instead of trying to use one of the ranger obstacks the following
    simply initializes the global bitmap obstack around an active ranger.

            PR middle-end/114604
            * gimple-range.cc (enable_ranger): Initialize the global
            bitmap obstack.
            (disable_ranger): Release it.

  parent reply	other threads:[~2024-04-09  6:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 13:06 [Bug middle-end/114604] New: " rguenth at gcc dot gnu.org
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 [this message]
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-BvoUwCwLot@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).