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 rtl-optimization/98863] [11 Regression] WRF with LTO consumes a lot of memory in REE, FWPROP and x86 specific passes
Date: Wed, 03 Feb 2021 12:33:34 +0000 [thread overview]
Message-ID: <bug-98863-4-fpix7B8LJ4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98863-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98863
--- Comment #38 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:550bf0c50024c320b7010d1b2bf644c5c918ad98
commit r10-9341-g550bf0c50024c320b7010d1b2bf644c5c918ad98
Author: Richard Biener <rguenther@suse.de>
Date: Fri Jan 29 16:02:36 2021 +0100
rtl-optimization/98863 - tame i386 specific RPAD pass
This removes analyzing DF with expensive problems which we do not
use at all and which somehow cause 5GB of memory to leak. Instead
just do a defered rescan of added insns.
This avoids
> FAIL: gcc.c-torture/compile/20051216-1.c -O1 (internal compiler error)
> FAIL: gcc.c-torture/compile/20051216-1.c -O1 (test for excess errors)
by clearing DF_DEFER_INSN_RESCAN after calling df_process_deferred_rescans,
so that it doesn't leak into following unprepared passes that expect
non-deferred rescans.
2021-02-03 Richard Biener <rguenther@suse.de>
Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/98863
* config/i386/i386-features.c (remove_partial_avx_dependency):
Do not perform DF analysis.
(pass_data_remove_partial_avx_dependency): Remove
TODO_df_finish.
* gcc.target/i386/20051216-1.c: New test.
next prev parent reply other threads:[~2021-02-03 12:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 11:19 [Bug rtl-optimization/98863] New: WRF with LTO consumes a lot of memory in split2 pass marxin at gcc dot gnu.org
2021-01-28 11:20 ` [Bug rtl-optimization/98863] " marxin at gcc dot gnu.org
2021-01-28 13:18 ` rguenth at gcc dot gnu.org
2021-01-28 13:21 ` marxin at gcc dot gnu.org
2021-01-28 14:14 ` marxin at gcc dot gnu.org
2021-01-28 14:20 ` rguenth at gcc dot gnu.org
2021-01-28 14:24 ` rguenth at gcc dot gnu.org
2021-01-28 15:09 ` marxin at gcc dot gnu.org
2021-01-28 15:15 ` rguenth at gcc dot gnu.org
2021-01-28 15:17 ` rguenth at gcc dot gnu.org
2021-01-28 15:18 ` rguenth at gcc dot gnu.org
2021-01-28 15:30 ` rguenth at gcc dot gnu.org
2021-01-29 8:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:03 ` rguenth at gcc dot gnu.org
2021-01-29 9:47 ` rguenth at gcc dot gnu.org
2021-01-29 9:56 ` marxin at gcc dot gnu.org
2021-01-29 10:18 ` marxin at gcc dot gnu.org
2021-01-29 10:24 ` rguenther at suse dot de
2021-01-29 11:03 ` rguenth at gcc dot gnu.org
2021-01-29 11:03 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE pass rguenth at gcc dot gnu.org
2021-01-29 11:38 ` marxin at gcc dot gnu.org
2021-01-29 12:13 ` rguenth at gcc dot gnu.org
2021-01-29 12:50 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, CPROP, PRE and LRA passes rguenth at gcc dot gnu.org
2021-01-29 12:57 ` marxin at gcc dot gnu.org
2021-01-29 13:01 ` cvs-commit at gcc dot gnu.org
2021-01-29 13:23 ` rguenth at gcc dot gnu.org
2021-01-29 13:37 ` marxin at gcc dot gnu.org
2021-01-29 14:39 ` rguenth at gcc dot gnu.org
2021-01-29 15:01 ` rguenth at gcc dot gnu.org
2021-01-29 15:56 ` hjl.tools at gmail dot com
2021-01-29 16:32 ` cvs-commit at gcc dot gnu.org
2021-02-01 8:22 ` cvs-commit at gcc dot gnu.org
2021-02-01 9:31 ` marxin at gcc dot gnu.org
2021-02-01 10:41 ` rguenth at gcc dot gnu.org
2021-02-01 12:07 ` [Bug rtl-optimization/98863] WRF with LTO consumes a lot of memory in REE, FWPROP and x86 specific passes rguenth at gcc dot gnu.org
2021-02-01 12:30 ` rsandifo at gcc dot gnu.org
2021-02-01 12:32 ` rguenth at gcc dot gnu.org
2021-02-01 12:45 ` [Bug rtl-optimization/98863] [11 Regression] " rguenth at gcc dot gnu.org
2021-02-01 13:35 ` cvs-commit at gcc dot gnu.org
2021-02-03 10:27 ` cvs-commit at gcc dot gnu.org
2021-02-03 12:33 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-08 8:45 ` rsandifo at gcc dot gnu.org
2021-02-08 9:01 ` rguenther at suse dot de
2021-02-08 9:23 ` richard.sandiford at arm dot com
2021-02-08 9:46 ` rguenth at gcc dot gnu.org
2021-02-08 12:44 ` rguenth at gcc dot gnu.org
2021-02-09 12:07 ` cvs-commit at gcc dot gnu.org
2021-02-09 12:40 ` rguenth at gcc dot gnu.org
2021-02-10 13:51 ` rguenth at gcc dot gnu.org
2021-02-15 15:06 ` cvs-commit at gcc dot gnu.org
2021-02-15 15:34 ` rsandifo 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-98863-4-fpix7B8LJ4@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).