Re: memcpy overlap: quickly detect, diagnose, work around

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 29, 2010 at 6:35 PM, John Reiser <jreiser@xxxxxxxxxxxx> wrote:
> While the details of inlining are subject
> to change, copying in ascending address order is the order that is
> assumed by all violators of the no-overlap requirement.

All violators? Citation needed.

I'm sure lurking somewhere there are ovelap copies which have no
'assumption' at allâ some bad luck with arithmetic makes it ovelap
during some rare alignment of the stars... though cases like that
aren't going to be the ones that get inlined by GCC.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux