public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dhekir at gmail dot com" <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: Wed, 01 Feb 2023 16:07:01 +0000 [thread overview] Message-ID: <bug-108500-4-LEDQbWyr3q@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 #13 from dhekir at gmail dot com --- Thank you very much for the work. Running the attached file with `-O -finline-small-functions` does compile in under 30 seconds on my computer. However, when trying to compile the original program (which is about 1 million lines, and each call passes 2 structures as arguments, instead of just calling a function without any arguments), it's taking several dozen minutes. I tried preprocessing it (5s to obtain the .i) file, and then running it with `-O -finline-small-functions`, or `-O2`, or `-O3`, and without any options at all, and in all cases, I ended up terminating the program before it finished (after more than 10 minutes; in some cases I waited up to 30 minutes). I tried re-simplifying the program. After preprocessing, I tried the following variants, with options `-O -finline-small-functions`: - 1M calls, no arguments, function returning a (global) struct: compiles in 30s; - 1M calls, each with a single argument of type `struct s`, function returns that same argument (that is, `struct s f(struct s s1) {return s1;}`): compiles in <2 minutes; - 1M calls, each with 2 arguments of types `struct s1` and `struct s2`, returning the second argument (that is, `struct s2 f(struct s1 arg1, struct s2 arg2) {return arg2;}`): >50 minutes (I had to terminate it). The last version, with -O2, I left it compiling for almost 3h before having to stop it. In any case, this bug seems definitely solved for me, and I no longer have the original stack overflow. However, I am still unable to compile my original code, so I'll have to try something else. It's possibly not a regression, however. I'm attaching it in case you may want to try it, but feel free to ignore it.
next prev parent reply other threads:[~2023-02-01 16:07 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 [this message] 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-LEDQbWyr3q@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).