On Mon, Jul 12, 2010 at 2:25 AM, Gabe Black wrote:
> Steve Reinhardt wrote:
> > On Sat, Jul 10, 2010 at 11:37 PM, Gabe Black
> wrote:
> >
> >> In ARM's SIMD instruction set extension Neon, there are some
> >> instructions which can load or store 3 of something, and that something
> >> can be 1,
On Sun, Jul 11, 2010 at 11:25 PM, Gabe Black wrote:
>
> Lets say I'm trying to read 3 uint16_ts. If I take the data from the
> packet and just case it to a uint16_t *, the host memory used as the
> packet payload may not be 2 byte aligned. What I'd need to do to ensure
> I can pass around and/or m
Steve Reinhardt wrote:
> On Sat, Jul 10, 2010 at 11:37 PM, Gabe Black wrote:
>
>> In ARM's SIMD instruction set extension Neon, there are some
>> instructions which can load or store 3 of something, and that something
>> can be 1, 2, 4, or 8 bytes. To implement this properly, I'm planning to
>>
On Sat, Jul 10, 2010 at 11:37 PM, Gabe Black wrote:
> In ARM's SIMD instruction set extension Neon, there are some
> instructions which can load or store 3 of something, and that something
> can be 1, 2, 4, or 8 bytes. To implement this properly, I'm planning to
> add readBytes and writeBytes func
In ARM's SIMD instruction set extension Neon, there are some
instructions which can load or store 3 of something, and that something
can be 1, 2, 4, or 8 bytes. To implement this properly, I'm planning to
add readBytes and writeBytes functions to the various ExecContexts which
would load/store some
