Re: register int variable being written to/read from stack

[John Regehr <regehr at cs dot utah dot edu>]

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 
register doesn't actually mean anything (in the standard, at least).

John Regehr




On Tue, 20 Jan 2009, Ian Lance Taylor wrote:

> baver <baver@thebeever.com> 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("s0");
>
> Show us the change you made to the MD file, or, if you didn't make a
> change, show us the asm statement you are using.
>
>
> > 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("s0");
>
> Are you doing this inside or outside of a function?  That is, a global
> variable or not?  The two cases act quite differently, as discussed
> briefly in the documentation.
>
> Ian