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 c/108500] New: -O -finline-small-functions results in "internal compiler error: Segmentation fault" on a very large program (700k function calls)
Date: Mon, 23 Jan 2023 17:30:27 +0000	[thread overview]
Message-ID: <bug-108500-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108500

            Bug ID: 108500
           Summary: -O -finline-small-functions results in "internal
                    compiler error: Segmentation fault" on a very large
                    program (700k function calls)
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dhekir at gmail dot com
  Target Milestone: ---

Created attachment 54328
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54328&action=edit
compressed version of a simplified program causing the ICE

In the attached preprocessed program (compressed with .tar.gz), running
'gcc -O -finline-small-functions' results in:

gcc: internal compiler error: Segmentation fault signal terminated program cc1

The original program is more interesting than this simplified version. Still,
it does have more than 700k function calls in the main function, which is
causing the problem.

The original command line was simply 'gcc -O2', then I narrowed the options
down to -finline-small-functions.

I tried several GCC Docker images (running 'gcc -O2' on the attached file), and
I narrowed it down to:

- with gcc:10.4 (or older), compilation works without any errors;
- with gcc:11.1 (or newer; I tested up to 12.2.0), segmentation fault happens.

             reply	other threads:[~2023-01-23 17:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 17:30 dhekir at gmail dot com [this message]
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
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@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).