public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andi-gcc at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56618] New: inline assembler with too many lines causes ICE in account_size_time, at ipa-inline-analysis.c
Date: Thu, 14 Mar 2013 13:12:00 -0000	[thread overview]
Message-ID: <bug-56618-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56618

             Bug #: 56618
           Summary: inline assembler with too many lines causes ICE in
                    account_size_time, at ipa-inline-analysis.c
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: andi-gcc@firstfloor.org


A 6.4 mio lines inline assembler statement (happened in some auto generated
real code) causes an overflow in the inliner cost estimation per cpu, resulting
in a ICE.

Reproducer

#!/usr/bin/python
print "int foo(void) {"
print "  asm("
for i in range(6400000):
    print r'    "\n"'
print "  );"
print "}"

./longasm.py > l.c

gcc l.c

Observed back to 4.7 at least, but much older compilers should be ok. So it's a
regression

Patch has been posted at 
http://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg50027.html
There was some discussion, but no approval


             reply	other threads:[~2013-03-14 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 13:12 andi-gcc at firstfloor dot org [this message]
2013-03-14 16:24 ` [Bug tree-optimization/56618] " pinskia 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-56618-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).