This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] strcpy optimizations


On 01/29/13 14:22, Andi Kleen wrote:
>> The behavior of strcpy is undefined in that case.

> Normally you have to handle this situation for any string code
> that does accesses larger than a byte, because users can create
> this by using offsets into strings.

Sorry, I must be slow today, but I'm still not following.
Can you give an example of a strcpy use, where it's required
that the strcpy implementation must access its arguments
in a particular order?  Because my understanding is that
there's no requirement that strcpy must operate left-to-right,
or anything like that.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]