Joakim Tjernlund writes:
> unsigned short my__arch_swab16(unsigned short value)
> {
> __asm__("rlwimi %0,%0,16,0x00ff"
> : "+r" (value));
You are creating a value that does not fit in a short.
Andreas.
--
Andreas Schwab, sch...@redhat.com
GPG Key fingerprint = D4E8 DBE
Andreas Schwab wrote on 2011/08/11 10:45:42:
>
> Joakim Tjernlund writes:
>
> > unsigned short my__arch_swab16(unsigned short value)
> > {
> >__asm__("rlwimi %0,%0,16,0x00ff"
> > : "+r" (value));
>
> You are creating a value that does not fit in a short.
Short is passed in a 32 bit
> Joakim Tjernlund writes:
>
> > unsigned short my__arch_swab16(unsigned short value)
> > {
> > __asm__("rlwimi %0,%0,16,0x00ff"
> > : "+r" (value));
>
> You are creating a value that does not fit in a short.
Which is a problem because the compiler could schedule
it be writt
"David Laight" wrote on 2011/08/11 10:56:26:
>
> > Joakim Tjernlund writes:
> >
> > > unsigned short my__arch_swab16(unsigned short value)
> > > {
> > >__asm__("rlwimi %0,%0,16,0x00ff"
> > > : "+r" (value));
> >
> > You are creating a value that does not fit in a short.
>
> Which is
> > Which is a problem because the compiler could schedule
> > it be written back to real memory between the instructions.
>
> It can? There is no memory here, just registers. Even if it
> is written to memory, how would that affect the register?
Although the function argument is passed in a re
"David Laight" wrote on 2011/08/11 11:29:33:
>
>
> > > Which is a problem because the compiler could schedule
> > > it be written back to real memory between the instructions.
> >
> > It can? There is no memory here, just registers. Even if it
> > is written to memory, how would that affect the re
