From: Richard Henderson <rth@redhat.com>
To: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
Cc: tromey@redhat.com, Dan Nicolaescu <dann@godzilla.ics.uci.edu>,
java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: java aliasing rules
Date: Fri, 29 Mar 2002 16:26:00 -0000 [thread overview]
Message-ID: <20020329162645.A19998@redhat.com> (raw)
In-Reply-To: <3CA4F734.6040706@waitaki.otago.ac.nz>; from bryce@waitaki.otago.ac.nz on Sat, Mar 30, 2002 at 11:22:28AM +1200
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~
next prev parent reply other threads:[~2002-03-30 0:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 11:43 Dan Nicolaescu
2002-03-27 13:53 ` Tom Tromey
2002-03-27 16:03 ` Dan Nicolaescu
2002-03-27 16:47 ` Tom Tromey
2002-03-27 20:00 ` Dan Nicolaescu
2002-03-27 15:54 ` Bryce McKinlay
2002-03-27 16:45 ` Tom Tromey
2002-03-28 22:02 ` Bryce McKinlay
2002-03-28 22:13 ` Richard Henderson
2002-03-28 22:15 ` Tom Tromey
2002-03-29 15:22 ` Bryce McKinlay
2002-03-29 16:26 ` Richard Henderson [this message]
2002-03-30 6:37 ` Jeff Sturm
2002-03-30 13:55 ` Richard Henderson
2002-03-30 15:04 ` Bryce McKinlay
2002-04-04 10:57 ` Jeff Sturm
2002-04-04 12:57 ` Andrew Haley
2002-04-04 14:20 ` Jeff Sturm
2002-04-04 17:04 ` Bryce McKinlay
2002-04-04 20:39 ` Jeff Sturm
2002-04-05 1:07 ` Bryce McKinlay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020329162645.A19998@redhat.com \
--to=rth@redhat.com \
--cc=bryce@waitaki.otago.ac.nz \
--cc=dann@godzilla.ics.uci.edu \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).