On 2023-07-31 14:25, Morten Brørup wrote:
From: Thomas Monjalon [mailto:tho...@monjalon.net]
Sent: Monday, 31 July 2023 14.14
Hello,
What's the status of this feature?
I haven't given up on upstreaming this feature, but there doesn't seem to be
much demand for it, so working on it has low pr
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Monday, 31 July 2023 14.14
>
> Hello,
>
> What's the status of this feature?
I haven't given up on upstreaming this feature, but there doesn't seem to be
much demand for it, so working on it has low priority.
>
>
> 10/10/2022 08:46
Hello,
What's the status of this feature?
10/10/2022 08:46, Morten Brørup:
> This patch provides a function for memory copy using non-temporal store,
> load or both, controlled by flags passed to the function.
>
> Applications sometimes copy data to another memory location, which is only
> used
On 2022-10-10 08:46, Morten Brørup wrote:
This patch provides a function for memory copy using non-temporal store,
load or both, controlled by flags passed to the function.
Applications sometimes copy data to another memory location, which is only
used much later.
In this case, it is inefficient
On 2022-10-10 08:46, Morten Brørup wrote:
This patch provides a function for memory copy using non-temporal store,
load or both, controlled by flags passed to the function.
Applications sometimes copy data to another memory location, which is only
used much later.
In this case, it is inefficient
This patch provides a function for memory copy using non-temporal store,
load or both, controlled by flags passed to the function.
Applications sometimes copy data to another memory location, which is only
used much later.
In this case, it is inefficient to pollute the data cache with the copied
d
6 matches
Mail list logo
