|
From: Jay F. <jay...@gm...> - 2009-05-06 11:36:14
|
> > These ones are always tricky, where the language spec doesn't match > > what happens in practice. This case is particularly annoying because > > we can't distinguish between a user-inserted memcpy() and a > > GCC-generated one. It's arguably that GCC shouldn't generate such > > code -- you say you assume glibc will not explode in this case, but > > that is an assumption. > > I think you should file this as a gcc bug. Looks like it has already been filed and fixed here: http://gcc.gnu.org/ml/gcc-patches/2009-04/msg00932.html Cheers, Jay. |