This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: java aliasing rules

From: Richard Henderson <rth at redhat dot com>
To: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
Cc: tromey at redhat dot com, Dan Nicolaescu <dann at godzilla dot ics dot uci dot edu>, java at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Fri, 29 Mar 2002 16:26:45 -0800
Subject: Re: java aliasing rules
References: <200203271143.aa05958@gremlin-relay.ics.uci.edu> <3CA25B77.1000108@waitaki.otago.ac.nz> <87vgbhij40.fsf@creche.redhat.com> <3CA40386.5030106@waitaki.otago.ac.nz> <873cyjoq4w.fsf@creche.redhat.com> <3CA4F734.6040706@waitaki.otago.ac.nz>

On Sat, Mar 30, 2002 at 11:22:28AM +1200, Bryce McKinlay wrote:
> The second increment of ps1.f1 should not be allowed to be 
> moved/combined ahead of the first "ps2.f2++", because it can trap/throw. 

Hum.  That's ugly.  The scheduling problem can be handled
easily.  Fixing global optimizations without practically
disabling them is harder.

> [ check it in to mainline anyway ]
> What do you guys think?

Sounds good.

r~

References:
- Re: java aliasing rules
  - From: Bryce McKinlay
- Re: java aliasing rules
  - From: Tom Tromey
- Re: java aliasing rules
  - From: Bryce McKinlay
- Re: java aliasing rules
  - From: Tom Tromey
- Re: java aliasing rules
  - From: Bryce McKinlay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]