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 tree-optimization/108500] -O -finline-small-functions results in "internal compiler error: Segmentation fault" on a very large program (700k function calls) Date: Tue, 24 Jan 2023 09:48:07 +0000 [thread overview] Message-ID: <bug-108500-4-rcy4bVKxTu@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- Created attachment 54332 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54332&action=edit do not compute fast-query from CFG cleanup This is the more obvious workaround (as said, the bug is the recursive DFS number assignment). I'm going to test this variant.
next prev parent reply other threads:[~2023-01-24 9:48 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 [this message] 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 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-rcy4bVKxTu@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).