This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/29272] [4.2 Regression] memcpy optimization causes wrong-code
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Sep 2006 11:47:03 -0000
- Subject: [Bug middle-end/29272] [4.2 Regression] memcpy optimization causes wrong-code
- References: <bug-29272-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #10 from rguenther at suse dot de 2006-09-30 11:47 -------
Subject: Re: [4.2 Regression] memcpy optimization
causes wrong-code
On Sat, 29 Sep 2006, mrs at apple dot com wrote:
> ------- Comment #8 from mrs at apple dot com 2006-09-29 23:15 -------
> > If it is a VAR_DECL, then I believe the optimization is always safe
>
> Not in C++.
As safe as using memcpy, which does not add any semantics to an
access using the VAR_DECL. So I believe this is safe even for C++.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29272