Subject: Re: ksh lossage on sparc64
To: Greg A. Woods <email@example.com>
From: Martin Husemann <firstname.lastname@example.org>
Date: 11/20/2000 21:04:29
> > this happens with other ports? how is the ksh source broken? i don't see
> > why it needs the volatile casts anyway...
> If a volatile cast is needed then it should always be there on all ports
> -- the fact that it breaks only on one or two ports is just an accident
> of how the code generation and optimisation works.
It's just by accident that only sparc64 currently uses gcc 2.95.2, while
all other ports are still using egcs ;-)