Hi Fredrik,
> > > Can you please try flipping the bits instead then, e.g.:
> > >
> > > uint32_t fcsr0, fcsr1;
> > > asm volatile (" cfc1 %0,$31\n"
> > > " lui %1,0xfffc\n"
> >
> > Actually can you please substitute:
> >
> > " li %1,0xfffc0003\n"
> >
> > here, so that we know how RM behaves?
>
> Sure. I get "FCSR old: 01000001, new: 01800001" with the R5900.
Thanks, that is as I suspected then.
I wonder if FS=1 hardwired also means the Underflow exception cannot
happen. As the corresponding Cause and Enable bits cannot be set together
or an FPE exception will happen right away, and the Unimplemented
Operation exception is uncoditional so we need to leave it out, can you
please also try these masks in turns:
" li %1,0x0001f07c\n"
and:
" li %1,0x00000f80\n"
This will reveal if any of the Cause, Enable or Flag bits are hardwired.
> > Again, it is odd to see it set to 1 (towards zero) by default and if it
> > is hardwired, then `->fpu_csr31' and `->fpu_msk31' will have to be
> > updated, AT_FPUCW exported and glibc adjusted.
>
> Right. Quite a few details to resolve for the FPU then. Here is the
> disassembly to double-check the compiled code:
Nothing unusual here. As you can see GCC has been smart enough to
schedule temporaries right in argument registers passed to the `printf'
call. :)
Maciej
