From: Greg McGary <gkm@eng.ascend.com>
To: law@cygnus.com
Cc: Greg McGary <gkm@eng.ascend.com>, Jim Wilson <wilson@cygnus.com>,
Dave Love <d.love@dl.ac.uk>,
burley@gnu.org, egcs@cygnus.com
Subject: Re: array bounds checking?
Date: Fri, 22 May 1998 00:32:00 -0000 [thread overview]
Message-ID: <msra1myh0n.fsf@tucson-net-82.eng.ascend.com> (raw)
In-Reply-To: <11492.895806192@hurl.cygnus.com>
Jeffrey A Law <law@hurl.cygnus.com> writes:
> My biggest concern is the change in pointer size; yes BP has
> mechanisms to handle this, but it just makes me uneasy.
It does take some getting used to. Having a BP C library helps
immensely.
> It sounds like you use a CONCAT like rtx to represent a bounded
> pointer. Is that correct?
I invented a new rtx CONCAT3. I don't much like it and think both
special-cases CONCAT and CONCAT3 should be replaced with a
variable-length rtx where XEXP (foo, 0) is the length.
> If so, then we're going to need to actually fix the CONCAT support.
> It's got some problems right now.
Whatever you can tell me about CONCAT problems would be a great help.
I already fixed a few CONCAT bugs in 2.7.2.
> It would also be good to get some sense of the changes involved;
> particularly for front-ends.
As promised in an earlier message, I'll send you a useless patch you
can review. (Useless because it's either for 2.7.2 or untested for
2.8.1)
> We'd want to be able to hook into the Fortran front end initially.
> The gpc guys would probably also benefit from this code, so we'll
> want them to be able to hook in as well.
What's "gpc"? Pascal?
next prev parent reply other threads:[~1998-05-22 0:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-18 16:05 Idea: Eliminate libf2c/f2c.h installation from g77 entirely? Craig Burley
1998-04-18 20:56 ` Mumit Khan
1998-04-19 0:11 ` Jeffrey A Law
1998-04-19 1:49 ` Craig Burley
1998-04-19 5:18 ` Dave Love
1998-04-19 11:19 ` Craig Burley
1998-04-19 5:37 ` array bounds checking? Dave Love
1998-04-21 19:10 ` Jim Wilson
1998-05-03 22:27 ` Greg McGary
1998-05-08 16:04 ` Gerald Pfeifer
1998-05-08 16:08 ` Greg McGary
1998-05-22 0:21 ` Jeffrey A Law
1998-05-22 0:32 ` Greg McGary [this message]
1998-05-22 5:42 ` Greg McGary
1998-05-22 12:21 ` Per Bothner
1998-05-22 12:14 ` Jeffrey A Law
1998-05-22 16:41 ` Pieter Nagel
1998-05-22 16:41 ` Dave Love
1998-05-22 20:21 ` Greg McGary
1998-05-26 2:32 ` Ken Raeburn
1998-04-19 8:15 ` using libtool Dave Love
1998-05-22 12:21 array bounds checking? Niall Smart
1998-05-22 16:41 ` Greg McGary
1998-05-24 4:18 Geert Bosch
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=msra1myh0n.fsf@tucson-net-82.eng.ascend.com \
--to=gkm@eng.ascend.com \
--cc=burley@gnu.org \
--cc=d.love@dl.ac.uk \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=wilson@cygnus.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).