Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!umd5!mimsy!aplcen!osiris!phil
From: phil@osiris.UUCP (Philip Kos)
Newsgroups: comp.arch
Subject: Re: RISC machines and scoreboarding
Summary: sometimes
Message-ID: <1639@osiris.UUCP>
Date: 29 Jun 88 14:39:07 GMT
References: <1082@nud.UUCP> <2438@winchester.mips.COM> <1098@nud.UUCP> <318@mucmot.UUCP>
Organization: Johns Hopkins Hospital
Lines: 14

In article <318@mucmot.UUCP>, ron@mucmot.UUCP (Ron Voss) writes:
> Are there really *good* reasons to put more trust in RISC optimizers?

I have to agree.  I once saw an old version of the Pyramid cc optimizer
totally trash a for(i = 0; i < 7; i++) loop with a printf() in the middle.
I guess that bit of code didn't really do anything.  :-)  (Talk about FUN
to debug...)  And we've been told to avoid the global optimizer like the
plague when any of the code to be tuned is asynchronous, like the signal
handlers we have in 99.99% of our applications...

                                                                 Phil Kos
                                                      Information Systems
...!uunet!pyrdc!osiris!phil                    The Johns Hopkins Hospital
                                                            Baltimore, MD