Ok, its more than 2 times slower for what I'm doing, but I guess that's gcc3's fault too, as was saw on Darwin. Do you know if there's any way to use gcc2, rather than 3? I can probably figure some way to set it up manually, but it would be nice if they had setup a hook like what was done in Darwin.
DaR > -----Original Message----- > From: Anton Ertl [mailto:anton@;a0.complang.tuwien.ac.at] > Sent: Sunday, October 27, 2002 12:06 AM > To: [EMAIL PROTECTED] > Subject: Re: [gforth] --enable-direct-threaded on cygwin? > > > Dennis Ruffer wrote: > > > > Thanks Anton, > > > > That seems to work, and doesn't hurt Darwin either. > However, I took the > > opportunity ;(foolishly); to update my cygwin to the > latest, and that > > managed to loose the ability to do direct-threading. I > updated the subject > > line to reflect the change in topic, so here's what's happening. > ... > > $ gcc -v > > Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.2/specs > > gcc-3.0 and later break an assumption that direct threaded gforth > uses. Indirect threaded code works fine (and is significantly faster > on P6 and Athlon for some real-world programs). > > - anton > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
