Re: [U-Boot] [PATCH v2 2/2] arm: Make arch specific memcpy thumb-safe.

> On 21 Apr 2018, at 19:00, Måns Rullgård wrote: > > Christoph Müllner > writes: > >>> On 21 Apr 2018, at 15:24, Måns Rullgård wrote: >>> >>> Klaus Goger writes: >>> The current arch implementation of memcpy cannot be called from t

Re: [U-Boot] [PATCH v2 2/2] arm: Make arch specific memcpy thumb-safe.

> On 21 Apr 2018, at 15:24, Måns Rullgård wrote: > > Klaus Goger writes: > >> The current arch implementation of memcpy cannot be called >> from thumb code, because it does not use bx instructions on return. >> This patch addresses that. Note, that this patch does not touch >> the hot loop of

Re: [U-Boot] [PATCH v2 2/2] arm: Make arch specific memcpy thumb-safe.

Christoph Müllner writes: >> On 21 Apr 2018, at 15:24, Måns Rullgård wrote: >> >> Klaus Goger writes: >> >>> The current arch implementation of memcpy cannot be called >>> from thumb code, because it does not use bx instructions on return. >>> This patch addresses that. Note, that this patch

Re: [U-Boot] [PATCH v2 2/2] arm: Make arch specific memcpy thumb-safe.

Klaus Goger writes: > The current arch implementation of memcpy cannot be called > from thumb code, because it does not use bx instructions on return. > This patch addresses that. Note, that this patch does not touch > the hot loop of memcpy, so performance is not affected. > > Tested on MXS (arm

[U-Boot] [PATCH v2 2/2] arm: Make arch specific memcpy thumb-safe.

The current arch implementation of memcpy cannot be called from thumb code, because it does not use bx instructions on return. This patch addresses that. Note, that this patch does not touch the hot loop of memcpy, so performance is not affected. Tested on MXS (arm926ejs) with and without thumb-mo