[Bug tree-optimization/56618] New: inline assembler with too many lines causes ICE in account_size_time, at ipa-inline-analysis.c

[Bug tree-optimization/56618] New: inline assembler with too many lines causes ICE in account_size_time, at ipa-inline-analysis.c

[andi-gcc at firstfloor dot org]

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

[Bug tree-optimization/56618] inline assembler with too many lines causes ICE in account_size_time, at ipa-inline-analysis.c

[pinskia at gcc dot gnu.org]

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-03-14 16:24:23 UTC ---
In a mean time, it was already filed by someone else.

*** This bug has been marked as a duplicate of bug 56580 ***