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 rtl-optimization/98144] REE needs 6GB DF memory when compiling insn-extract.c with RTL checking enabled Date: Fri, 29 Jan 2021 11:04:19 +0000 [thread overview] Message-ID: <bug-98144-4-42y8ZvoDsC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98144-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98144 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |11.0 --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk, planning to do backports after a while.
next prev parent reply other threads:[~2021-01-29 11:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-04 14:23 [Bug rtl-optimization/98144] New: " rguenth at gcc dot gnu.org 2020-12-04 14:24 ` [Bug rtl-optimization/98144] " rguenth at gcc dot gnu.org 2020-12-04 14:34 ` rguenth at gcc dot gnu.org 2020-12-07 8:36 ` doko at debian dot org 2020-12-07 13:43 ` rguenth at gcc dot gnu.org 2020-12-09 14:36 ` amacleod at redhat dot com 2020-12-09 14:42 ` jakub at gcc dot gnu.org 2020-12-17 18:37 ` amacleod at redhat dot com 2021-01-29 9:22 ` rguenth at gcc dot gnu.org 2021-01-29 11:02 ` cvs-commit at gcc dot gnu.org 2021-01-29 11:03 ` rguenth at gcc dot gnu.org 2021-01-29 11:04 ` rguenth at gcc dot gnu.org [this message] 2021-02-03 10:23 ` cvs-commit at gcc dot gnu.org 2021-02-04 18:11 ` sirl at gcc dot gnu.org 2021-02-05 7:50 ` rguenth at gcc dot gnu.org 2021-05-04 13:54 ` cvs-commit at gcc dot gnu.org 2021-05-04 13:56 ` 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-98144-4-42y8ZvoDsC@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: linkBe 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).