This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/39480] generated memcpy causes trouble in assignment
- From: "fpbeekhof at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 17 Mar 2009 12:21:29 -0000
- Subject: [Bug libstdc++/39480] generated memcpy causes trouble in assignment
- References: <bug-39480-14973@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from fpbeekhof at gmail dot com 2009-03-17 12:21 -------
Subject: Re: generated memcpy causes trouble in assignment
paolo dot carlini at oracle dot com wrote:
> ------- Comment #5 from paolo dot carlini at oracle dot com 2009-03-17 11:28 -------
> By the way, I don't see what could be possibly wrong in libstdc++: can you
> please tell us which specific line of code you are suspecting? Certainly, not
> the entire swap implementation, which is definitely the correct one, no other
> options.
>
>
Well, a specific line of code I cannot give, because this bug is in the
operator=() that is generated by the compiler. Given comment #6 by Falk,
I think we can safely say that there is an actual bug here.
Perhaps libstdc++ is wrong place to submit this bug, but I originally
encountered it whilst using iter_swap() from <algorithm> and assumed
that to be the cause of the problem.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39480