> > The only difference I see (that really matters) is how the bytes are
> > copied to the result-pointer (i.e. using movzbl vs. movsbl)... but that's
> > it.
>
> It is a cast. The generic C version for the other architectures makes
> this more obvious.
>
> > If there is some deeper reason behind
Clemens Kolbitsch wrote:
> hi everyone!
> i have a (maybe rather tricky) question:
>
> why do you define 2 different inline load-functions in softmmu_header:
>
> static inline int glue(glue(lds, SUFFIX), MEMSUFFIX)(target_ulong ptr)
>
> vs.
>
> static inline RES_TYPE glue(glue(ld, USUFFIX), MEM
hi everyone!
i have a (maybe rather tricky) question:
why do you define 2 different inline load-functions in softmmu_header:
static inline int glue(glue(lds, SUFFIX), MEMSUFFIX)(target_ulong ptr)
vs.
static inline RES_TYPE glue(glue(ld, USUFFIX), MEMSUFFIX)(target_ulong ptr)
??
Obviously this
