From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org, lars@nocrew.org
Subject: Re: m68k MacOS target support?
Date: Tue, 12 Sep 2000 08:11:00 -0000 [thread overview]
Message-ID: <10009121525.AA22217@vlsi1.ultra.nyu.edu> (raw)
That sounds helpful. Those kind of generic changes are probably
welcome -- especially if they don't add much maintenance overhead, and
if there are other architectures that have similarly unusual pointer
formats. (I don't know whether there are such beasts or not,
honestly).
I suspect my feeling is the same as yours. I don't *necessarily* see
these as useful for other architectures, but fell that adding support
for this, if done cleanly, is likely to be a worthwhile addition to
GCC since it may produce a level of abstraction in the handling of
pointers that might make *other* things easlier down the road.
next reply other threads:[~2000-09-12 8:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-12 8:11 Richard Kenner [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-13 8:49 Michael Sokolov
2000-09-12 18:43 Michael Sokolov
2000-09-12 19:44 ` Stan Shebs
2000-09-13 8:40 ` Joe Buck
2000-09-12 18:18 Michael Sokolov
2000-09-12 18:08 Michael Sokolov
2000-09-12 17:57 Michael Sokolov
2000-09-12 18:12 ` Richard Henderson
2000-09-12 18:19 ` Geoff Keating
2000-09-12 19:05 ` Stan Shebs
2000-09-09 12:33 Michael Sokolov
2000-09-11 20:47 ` Stan Shebs
2000-09-11 20:56 ` Michael Meissner
2000-09-11 21:33 ` Mark Mitchell
2000-09-12 0:02 ` lars brinkhoff
2000-09-12 0:15 ` Mark Mitchell
2000-09-12 3:26 ` lars brinkhoff
2000-09-12 7:23 ` Mark Mitchell
2000-09-12 11:16 ` Joe Buck
2000-09-12 11:22 ` Bernd Schmidt
2000-09-12 20:11 ` Mark Mitchell
2000-09-12 13:59 ` Stan Shebs
2000-09-12 17:55 ` Richard Henderson
2000-09-12 19:12 ` Stan Shebs
2000-09-13 3:17 ` Joseph S. Myers
2000-09-12 11:48 ` Toon Moene
2000-09-12 7:32 ` Jeffrey A Law
2000-09-12 0:03 ` lars brinkhoff
2000-09-12 9:52 ` David Huggins-Daines
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=10009121525.AA22217@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=lars@nocrew.org \
--cc=mark@codesourcery.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).