From: Tom Tromey <tromey@cygnus.com>
To: gcc@gcc.gnu.org
Subject: Re: Need advice on bounds checking approaches
Date: Tue, 04 Sep 2001 23:52:00 -0000 [thread overview]
Message-ID: <87vh26okd7.fsf@cygnus.com> (raw)
In-Reply-To: <msvh26olpm.fsf@gkm-dsl-194.ascend.com>
>>>>> "Greg" == Greg McGary <gkm@eng.ascend.com> writes:
Greg> Is there some other advantage to memory-barrier semantics
Greg> wrt. bounds checks that I'm overlooking?
You once mentioned the idea of changing gcj to use your bounds
checking code. Java has strict rules about when the exception must be
thrown. (Whether it is feasible to change the gcj front end to use
this stuff, I don't know.)
Tom
next prev parent reply other threads:[~2001-09-04 23:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 11:18 Greg McGary
2000-03-24 12:08 ` Joern Rennecke
2000-03-24 12:28 ` Greg McGary
2000-03-24 16:18 ` Jeffrey A Law
2000-03-24 16:50 ` Greg McGary
2000-03-24 17:27 ` Jamie Lokier
2000-03-27 12:30 ` Jeffrey A Law
2000-03-27 12:45 ` Mark Mitchell
2000-03-27 13:05 ` Greg McGary
2000-03-27 13:54 ` Geoff Keating
2000-03-27 14:21 ` Greg McGary
2000-03-27 14:30 ` Jeffrey A Law
2000-03-27 19:23 ` Michael Hayes
2000-03-27 14:34 ` Geoff Keating
2000-03-27 22:07 ` Greg McGary
2000-03-28 1:55 ` Richard Henderson
2000-03-28 7:05 ` Jeffrey A Law
2000-03-28 9:28 ` Greg McGary
2000-03-28 9:48 ` Jeffrey A Law
2000-03-28 11:30 ` Geoff Keating
2000-03-28 12:26 ` Greg McGary
2000-03-28 12:30 ` Geoff Keating
2000-03-28 12:59 ` Greg McGary
2000-03-28 13:12 ` Greg McGary
2000-03-29 10:17 ` Joe Buck
2000-03-28 13:41 ` Alan Lehotsky
2000-03-28 14:25 ` Greg McGary
2001-09-04 23:52 ` Tom Tromey [this message]
2000-03-28 14:21 ` Greg McGary
2000-03-28 9:57 ` Joern Rennecke
2000-03-29 12:22 ` Jeffrey A Law
2000-03-29 13:35 ` Geoff Keating
2000-04-07 9:57 ` Greg McGary
2000-04-09 11:01 ` Jeffrey A Law
2000-04-09 11:38 ` Greg McGary
2000-04-10 10:13 ` Jeffrey A Law
2000-04-09 16:26 ` Greg McGary
2000-04-10 10:20 ` Jeffrey A Law
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=87vh26okd7.fsf@cygnus.com \
--to=tromey@cygnus.com \
--cc=gcc@gcc.gnu.org \
/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).