public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Lattner <sabre@nondot.org>
To: Greg McGary <greg@mcgary.org>
Cc: Zack Weinberg <zackw@stanford.edu>,
	gcc@gcc.gnu.org, bernecky@acm.org, gnu@toad.com
Subject: Re: Esthetics (or worse?) of Secure Pointers
Date: Tue, 17 Apr 2001 17:41:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0104171940090.11934-100000@nondot.org> (raw)
In-Reply-To: <msk84jhx1n.fsf@mcgary.org>

> For a backup plan, I think it's sufficient to mandate no mixing of BP
> and non-BP compilation units, distinguished by a special symbol,
> enforced by ld.  Anyone violently disagree?  (Yes, I know this is the
> purview of the binutils list, so we'll need to ask there about ld's
> role as enforcer)

If possible, that definately sounds like the best idea... GDB will still
need to be enhanced however.  If nothing else, printing out and
dereferencing fat pointers is different than normal pointers.  I assume
that this enhancement would be more clean than an outright hack (which GDB
doesn't need) to remove the prefix...

-Chris

http://www.nondot.org/~sabre/os/
http://www.nondot.org/MagicStats/
http://www.nondot.org/~sabre/

  reply	other threads:[~2001-04-17 17:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2001-04-19  2:22 Jimen Ching
2001-04-19  6:49 ` Robert Bernecky
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
2001-04-19  5:26 ` Per Abrahamsen

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=Pine.LNX.4.21.0104171940090.11934-100000@nondot.org \
    --to=sabre@nondot.org \
    --cc=bernecky@acm.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gnu@toad.com \
    --cc=greg@mcgary.org \
    --cc=zackw@stanford.edu \
    /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).