First, off the volatile qualifier means "source-level reads/write must
turn into real loads and stores" so take that out of your declaration and
see how the code looks then. I don't know if the standard addresses the
interaction of volatile and register, but I'd expect volatile to win since
re
baver writes:
> A sample code listing is at the bottom of the email, as well as the lines
> we've added to opcodes/mips-opc.c for our opcodes.
>
>
>
> Anyone know how to stop the register from being stored and read from on the
> stack? We've defined it as
>
> volatile register int idx asm(
Hi all,
Not sure if this fits in more with GCC or binutils.
We have amodified binutils/gcc to add a few opcodes to the MIPS-I ISA for a
processor we've designed as part of our academics. One of these opcodes writes
an index into a register we specify.
This works, but we're seeing
1) the valu
