public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102527] [12 regression] out of memory compiling insn-emit.c
Date: Thu, 30 Sep 2021 06:22:41 +0000	[thread overview]
Message-ID: <bug-102527-4-FZbB6k16kw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102527-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #11)
> This looks mighty suspicious ;-)
> 
> diff --git a/gcc/tree-vrp.c b/gcc/tree-vrp.c
> index 69a3ab0ea9d..c24c67f8874 100644
> --- a/gcc/tree-vrp.c
> +++ b/gcc/tree-vrp.c
> @@ -4408,6 +4408,7 @@ hybrid_threader::~hybrid_threader ()
>    delete m_threader;
>    delete m_state;
>    delete m_ranger;
> +  delete m_query;
> 
>    scev_finalize ();
>    loop_optimizer_finalize ();

FWIW, all the patches so far proposed have been pushed to trunk, if you want to
try again.

  parent reply	other threads:[~2021-09-30  6:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 13:45 [Bug bootstrap/102527] New: " ro at gcc dot gnu.org
2021-09-29 13:46 ` [Bug bootstrap/102527] " ro at gcc dot gnu.org
2021-09-29 14:28 ` dje at gcc dot gnu.org
2021-09-29 14:31 ` aldyh at gcc dot gnu.org
2021-09-29 14:33 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-09-29 15:06 ` aldyh at gcc dot gnu.org
2021-09-29 15:18 ` aldyh at gcc dot gnu.org
2021-09-29 15:22 ` aldyh at gcc dot gnu.org
2021-09-29 21:04 ` ro at gcc dot gnu.org
2021-09-29 21:05 ` ro at gcc dot gnu.org
2021-09-29 22:15 ` ro at gcc dot gnu.org
2021-09-29 22:16 ` ro at gcc dot gnu.org
2021-09-30  0:19 ` aldyh at redhat dot com
2021-09-30  6:22 ` aldyh at gcc dot gnu.org [this message]
2021-09-30 10:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-09-30 10:46 ` aldyh 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-102527-4-FZbB6k16kw@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).