Messages in this thread | | | Date | Wed, 26 Feb 2003 15:19:14 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: Invalid compilation without -fno-strict-aliasing |
| |
On Wed, 26 Feb 2003, Daniel Jacobowitz wrote: [SNIPPED...]
> > It was supposed to force x, which may be cached in a register, > > to be written to memory __now__. It doesn't seem to do anything. > > I think FORCE_TO_MEM() needs to claim that it uses most all the > > registers. That will make sure that any register values get > > written to their final memory locations. > > If so it wouldn't be inside the #APP/#NOAPP markers. You didn't answer > my other question: was X in memory at the time?
It was in %ebx register and didn't go back to NNN(%esp) where it came from. Like I said, it did do anything.
> > You should be using something like __asm__ __volatile__ (""::"m"(x)) > anyway. >
Yep. Probably.
Cheers, Dick Johnson Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips). Why is the government concerned about the lunatic fringe? Think about it.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |