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 tree-optimization/108500] [11/12 Regression] -O -finline-small-functions results in "internal compiler error: Segmentation fault" on a very large program (700k function calls)
Date: Fri, 10 Feb 2023 16:45:44 +0000 [thread overview]
Message-ID: <bug-108500-4-YnFwQBcD4S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108500-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500
--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>:
https://gcc.gnu.org/g:3c5154d0f0d2185b518465b264ca17fb7c60c1e8
commit r13-5808-g3c5154d0f0d2185b518465b264ca17fb7c60c1e8
Author: Vladimir N. Makarov <vmakarov@redhat.com>
Date: Fri Feb 10 11:12:37 2023 -0500
RA: Use simple LRA for huge functions
The PR108500 test contains a huge function and RA spends a lot of time
to compile the test with -O0. The patch decreases compilation time
considerably for huge functions. Compilation time for the PR test
decreases from 1235s to 709s on Intel i7-13600K.
PR tree-optimization/108500
gcc/ChangeLog:
* params.opt (ira-simple-lra-insn-threshold): Add new param.
* ira.cc (ira): Use the param to switch on simple LRA.
next prev parent reply other threads:[~2023-02-10 16:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 17:30 [Bug c/108500] New: " dhekir at gmail dot com
2023-01-23 17:55 ` [Bug c/108500] " dhekir at gmail dot com
2023-01-24 2:57 ` [Bug ipa/108500] " pinskia at gcc dot gnu.org
2023-01-24 3:18 ` [Bug tree-optimization/108500] " pinskia at gcc dot gnu.org
2023-01-24 9:32 ` rguenth at gcc dot gnu.org
2023-01-24 9:43 ` rguenth at gcc dot gnu.org
2023-01-24 9:48 ` rguenth at gcc dot gnu.org
2023-01-24 12:36 ` [Bug tree-optimization/108500] [11/12/13 Regression] " rguenth at gcc dot gnu.org
2023-01-24 14:29 ` cvs-commit at gcc dot gnu.org
2023-01-24 14:30 ` [Bug tree-optimization/108500] [11/12 " rguenth at gcc dot gnu.org
2023-02-01 7:47 ` cvs-commit at gcc dot gnu.org
2023-02-01 8:42 ` rguenth at gcc dot gnu.org
2023-02-01 16:06 ` dhekir at gmail dot com
2023-02-01 16:07 ` dhekir at gmail dot com
2023-02-02 10:22 ` rguenth at gcc dot gnu.org
2023-02-02 10:34 ` rguenth at gcc dot gnu.org
2023-02-02 14:01 ` rguenth at gcc dot gnu.org
2023-02-02 17:12 ` dhekir at gmail dot com
2023-02-03 7:06 ` rguenth at gcc dot gnu.org
2023-02-03 8:20 ` rguenth at gcc dot gnu.org
2023-02-10 14:05 ` vmakarov at gcc dot gnu.org
2023-02-10 16:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-13 7:42 ` rguenth at gcc dot gnu.org
2023-03-15 9:47 ` cvs-commit at gcc dot gnu.org
2023-03-15 10:03 ` [Bug tree-optimization/108500] [11 " rguenth at gcc dot gnu.org
2023-05-05 8:09 ` 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-108500-4-YnFwQBcD4S@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).