public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/2910 Date: Mon, 28 May 2001 04:36:00 -0000 [thread overview] Message-ID: <20010528113602.22834.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/2910; it has been noted by GNATS. From: nathan@gcc.gnu.org To: Christoph.Pesch@web.de, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/2910 Date: 28 May 2001 11:29:55 -0000 Synopsis: dynamic_cast seems to lose or change information State-Changed-From-To: analyzed->closed State-Changed-By: nathan State-Changed-When: Mon May 28 04:29:54 2001 State-Changed-Why: further email from originator points out this invokes undefined effects. specifically we bind a temporary to a reference, and then the temporary goes out of scope. The dynamic cast version fails, as they dynamic cast is implemented by a function call which clobbers the memory of that temporary. The static cast case does not fail, because memory happens to have the right things in it. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2910&database=gcc
next reply other threads:[~2001-05-28 4:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-28 4:36 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-28 3:16 c++/2910 nathan
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=20010528113602.22834.qmail@sourceware.cygnus.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).