| To: | Dror Maydan <maydan@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Bug in sgicc version 0.01.0-13 |
| From: | Nenad Nedeljkovic <nenad@xxxxxxxxxxxxx> |
| Date: | Mon, 16 Apr 2001 15:29:53 -0700 |
| Cc: | Michael Murphy <mpm@xxxxxxxxxxxxxxxxx>, "'pro64-support@xxxxxxxxxxx'" <pro64-support@xxxxxxxxxxx>, "Robboy, David G" <david.g.robboy@xxxxxxxxx> |
| References: | <200104162149.OAA66376@rohi.engr.sgi.com> <3ADB6B31.A6FC03C1@tensilica.com> |
| Sender: | owner-pro64-support@xxxxxxxxxxx |
Dror Maydan wrote: > > Michael Murphy wrote: > > > This is indeed a bug. It is LNO that removes the loop. > > I'll file a bug about this, but I'm not sure when it will be fixed. > > Any LNO experts on the list want to take a look at this? :-) > > > > -- Mike Murphy > > Actually, preopt removes the loop, not LNO. > > Dror Actually, it seems that the front end is at fault -- it doesn't mark the type for 'foo' as volatile. If 'foo' is a standalone variable (not a struct member), its type is marked as volatile, and the loop is not removed. Nenad |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Bug in sgicc version 0.01.0-13, Dror Maydan |
|---|---|
| Next by Date: | sgicc and -fvolatile, Sterling Augustine |
| Previous by Thread: | Re: Bug in sgicc version 0.01.0-13, Dror Maydan |
| Next by Thread: | sgicc and -fvolatile, Sterling Augustine |
| Indexes: | [Date] [Thread] [Top] [All Lists] |