public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/55138] New: [4.7 Regression] inlining fails with -O2 on gcc 4.7.2
@ 2012-10-30 13:05 konstantin.vladimirov at gmail dot com
  2012-10-30 14:27 ` [Bug tree-optimization/55138] " rguenth at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: konstantin.vladimirov at gmail dot com @ 2012-10-30 13:05 UTC (permalink / raw)
  To: gcc-bugs


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

             Bug #: 55138
           Summary: [4.7 Regression] inlining fails with -O2 on gcc 4.7.2
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: konstantin.vladimirov@gmail.com


Created attachment 28575
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28575
reproduction

found on private target, but can be easily reproduced on x86, so I think every
target is affected.

Compile attached file on gcc-4.7.2 with -O2 -DBROKEN to make function inlined.

Next run. You will see error. Compile just with -O2, next run and you will see
no error.

This error can not be reproduced on gcc-4.6.3, everything works fine. Problems
starts with 4.7


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-10-31  4:12 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-30 13:05 [Bug tree-optimization/55138] New: [4.7 Regression] inlining fails with -O2 on gcc 4.7.2 konstantin.vladimirov at gmail dot com
2012-10-30 14:27 ` [Bug tree-optimization/55138] " rguenth at gcc dot gnu.org
2012-10-30 14:48 ` mikpe at it dot uu.se
2012-10-30 15:11 ` rguenth at gcc dot gnu.org
2012-10-30 21:57 ` mikpe at it dot uu.se
2012-10-31  4:12 ` law at redhat dot com

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).