From: Joe Buck <jbuck@racerx.synopsys.com>
To: greg@mcgary.org (Greg McGary)
Cc: bernecky@acm.org (Robert Bernecky), gcc@gcc.gnu.org, gnu@toad.com
Subject: Re: Esthetics (or worse?) of Secure Pointers
Date: Tue, 17 Apr 2001 18:49:00 -0000 [thread overview]
Message-ID: <200104180147.SAA03582@racerx.synopsys.com> (raw)
In-Reply-To: <msn19fggo5.fsf@mcgary.org>
I wrote:
> > It might be possible, for specific libraries, to write a set of thunks
> > that would allow bounds-checked code to call the non-bounds-checked C
> > library...
> > Such things might be necessary for people on OSes that don't
> > have a free C library to use the bounds checking compiler.
Greg writes:
> We have limited resources. Bending over backwards to support non-free
> OSes is a poor use of those resources. Much better to press forward
> in the land of the free.
By mentioning it I didn't mean to imply that you should do it!
Certainly you shouldn't waste your time implementing this. Once BP-gcc
is successful, other folks might be interested in contributing it.
There might be speed advantages to doing it this way even with the free
glibc, or memory savings for folks running a mix of BP and non-BP apps,
but then improving gcc's optimization might make it unnecessary.
next prev parent reply other threads:[~2001-04-17 18:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 11:52 Robert Bernecky
2001-04-17 12:29 ` Geoff Keating
2001-04-17 16:28 ` Greg McGary
2001-04-17 16:41 ` Robert Bernecky
2001-04-17 17:52 ` Joe Buck
2001-04-17 18:07 ` Greg McGary
2001-04-17 18:49 ` Joe Buck [this message]
2001-04-19 5:26 ` Per Abrahamsen
2001-04-17 15:00 Chris Lattner
2001-04-17 15:46 ` Robert Bernecky
2001-04-17 16:06 ` Chris Lattner
2001-04-17 16:32 ` Robert Bernecky
2001-04-17 17:00 ` Greg McGary
2001-04-17 16:52 ` Greg McGary
2001-04-18 10:00 ` Joern Rennecke
2001-04-17 16:43 ` Greg McGary
2001-04-17 19:20 ` John Gilmore
2001-04-18 9:22 ` Joe Buck
2001-04-18 13:14 ` Toon Moene
2001-04-17 16:36 ` Greg McGary
2001-04-17 17:03 ` Zack Weinberg
2001-04-17 17:28 ` Greg McGary
2001-04-17 17:41 ` Chris Lattner
2001-04-17 18:01 ` Greg McGary
2001-04-17 19:40 ` John Gilmore
2001-04-17 19:46 ` David Edelsohn
2001-04-17 20:01 ` Michael Meissner
2001-04-18 10:03 ` Joern Rennecke
2001-04-18 10:37 ` Robert Bernecky
2001-04-18 11:02 ` Neil Booth
2001-04-18 11:10 ` Joern Rennecke
2001-04-19 0:04 ` Fergus Henderson
2001-04-17 19:59 ` Michael Meissner
2001-04-17 17:56 ` Fergus Henderson
2001-04-19 2:22 Jimen Ching
2001-04-19 6:49 ` Robert Bernecky
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=200104180147.SAA03582@racerx.synopsys.com \
--to=jbuck@racerx.synopsys.com \
--cc=bernecky@acm.org \
--cc=gcc@gcc.gnu.org \
--cc=gnu@toad.com \
--cc=greg@mcgary.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).