public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.vladimirov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55138] New: [4.7 Regression] inlining fails with -O2 on gcc 4.7.2
Date: Tue, 30 Oct 2012 13:05:00 -0000	[thread overview]
Message-ID: <bug-55138-4@http.gcc.gnu.org/bugzilla/> (raw)


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


             reply	other threads:[~2012-10-30 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 13:05 konstantin.vladimirov at gmail dot com [this message]
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

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