Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!princeton!udel!gatech!bloom-beacon!tut.cis.ohio-state.edu!mailrus!iuvax!pur-ee!a.cs.uiuc.edu!uxc.cso.uiuc.edu!urbsdc!aglew
From: aglew@urbsdc.UUCP
Newsgroups: comp.arch
Subject: Re: RISC machines and scoreboarding
Message-ID: <28200170@urbsdc>
Date: 30 Jun 88 20:20:00 GMT
References: <1082@nud.UUCP>
Lines: 14
Nf-ID: #R:nud.UUCP:1082:urbsdc:28200170:000:744
Nf-From: urbsdc.Urbana.Gould.COM!aglew    Jun 30 15:20:00 1988


>              ... 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

I'm interested... at first I thought you said that 99.99% of your applications
were in the signal handlers, but that was wrong. Still, what do you do in
the signal handlers - set flags that other steps can use? Sounds like you
need volatile.