Subject: re: ksh lossage on sparc64
To: Martin Husemann <>
From: matthew green <>
List: tech-toolchain
Date: 11/21/2000 01:32:18
   > + #ifdef __sparc64__
   > + 	int	f;
   > + 
   > + 	*(volatile int *)&f = j->state;
   > + #endif
   I can't parse that. Still talking C here? In C++ that would nearly make sense,

this is C.  we take the address of f, cast it to a volatile int pointer, and
then assign the value of j->state to it's dereference.
   Anyway: this bug is not related to sparc64 at all, it's a generic gcc 2.95.2
   problem and the ksh source in tree is broken. So this is not the way to fix
   it, it will hit other ports when they migrate to the newer gcc too.

this happens with other ports?  how is the ksh source broken?  i don't see
why it needs the volatile casts anyway...