On Tue, 29 Jan 2019 at 23:53, Heinrich Schuchardt wrote:
>
> Memory functions may have architecture specific implementations. These
> should be tested.
>
> Provide unit tests for memset(), memcpy(), memmove().
>
> Provide a 'ut lib' sub-command to execute the tests.
>
> Signed-off-by: Heinrich Sch
Memory functions may have architecture specific implementations. These
should be tested.
Provide unit tests for memset(), memcpy(), memmove().
Provide a 'ut lib' sub-command to execute the tests.
Signed-off-by: Heinrich Schuchardt
---
v2
vary alignment and length of copied or set memory
On 1/24/19 9:03 AM, Simon Goldschmidt wrote:
> On Thu, Jan 24, 2019 at 7:51 AM Heinrich Schuchardt
> wrote:
>>
>> Memory functions may have architecture specific implementations. These
>> should be tested.
>>
>> Provide unit tests for memset(), memcpy(), memmove().
>>
>> Signed-off-by: Heinrich
On Thu, Jan 24, 2019 at 7:51 AM Heinrich Schuchardt wrote:
>
> Memory functions may have architecture specific implementations. These
> should be tested.
>
> Provide unit tests for memset(), memcpy(), memmove().
>
> Signed-off-by: Heinrich Schuchardt
Could you explain to me the changes to the fi
Memory functions may have architecture specific implementations. These
should be tested.
Provide unit tests for memset(), memcpy(), memmove().
Signed-off-by: Heinrich Schuchardt
---
Hello Alex,
you already picked up the patch correcting memmove for x86_64.
x86: do not use i386 code for x86_64 m
5 matches
Mail list logo