public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: gcc-gnats@gcc.gnu.org
Subject: optimization/6189: Regression from 3.0.x: g++ -O3 generates wrong code
Date: Fri, 05 Apr 2002 07:56:00 -0000	[thread overview]
Message-ID: <20020405155301.11827.qmail@sources.redhat.com> (raw)


>Number:         6189
>Category:       optimization
>Synopsis:       Regression from 3.0.x: g++ -O3 generates wrong code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 05 07:56:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Volker Reichelt
>Release:        gcc version 3.1 20020325 (prerelease)
>Organization:
>Environment:
i686-pc-linux-gnu, mips-sgi-irix6.5
>Description:
The following small C++-program should return 1,
but compiling the code with "g++ -O3" I get 0 as a result.

----------------------------snip here---------------------
class A
{
  private:
    int x[2];

  public:
    int& GetFirst() { return x[0]; }
};


A foo ()
{ 
    A a;
    a.GetFirst()=1;
    return a;
}


int main()
{
    A b=foo();
    return b.GetFirst();
}
----------------------------snip here---------------------

With less optimization the problem disappears.
It even disappears when I replace "private" by "public".

The bug is a regression from gcc 3.0.x.
>How-To-Repeat:
g++ -O3 bug.cpp; a.out; echo $?
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-05 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05  7:56 reichelt [this message]
2002-06-10  5:56 Reichelt
2002-06-10  7:16 Jason Merrill
2002-10-28 13:22 reichelt

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=20020405155301.11827.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=gcc-gnats@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).