public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "contact at ncomputers dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63364] GCC optimizer causing memory corruption
Date: Thu, 25 Sep 2014 05:13:00 -0000	[thread overview]
Message-ID: <bug-63364-4-Bjv351CNN5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63364-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63364

--- Comment #2 from ncomputers.org <contact at ncomputers dot org> ---
(In reply to Andrew Pinski from comment #1)
> >    B(A const*const&aa):a(aa){}
> 
> >    B*b=new B(this);
> 
> 
> There is a temporary variable being created there and it goes out of scope
> after the statement is finished.   The reason is because this is not a
> lvalue, prvalue.
> 
> Here is the quote from the standard:
> In the body of a non-static (9.3) member function, the keyword this is a
> prvalue expression whose value
> is the address of the object for which the function is called.

Andrew, thank you for your answer!

Yes it is true! We understand now better the reference variables.

Can we write your name in our website?

"Andrew Pinski taught us something new".


  parent reply	other threads:[~2014-09-25  5:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  3:18 [Bug c++/63364] New: " contact at ncomputers dot org
2014-09-25  3:38 ` [Bug c++/63364] " pinskia at gcc dot gnu.org
2014-09-25  5:13 ` contact at ncomputers dot org [this message]
2014-09-25  5:26 ` 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-63364-4-Bjv351CNN5@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).