public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: marcusd@cathcart.sysc.pdx.edu (Marcus G. Daniels)
To: Ovidiu Predescu <ovidiu@aracnet.com>
Cc: Scott Christley <scottc@net-community.com>, egcs@cygnus.com
Subject: Re: GCC/ObjC enhancements, comments requested
Date: Sun, 08 Feb 1998 13:12:00 -0000	[thread overview]
Message-ID: <rfira5dlsnh.fsf@cathcart.sysc.pdx.edu> (raw)
In-Reply-To: <199802081830.KAA04236@net-community.com>

>>>>> "OP" == Ovidiu Predescu <ovidiu@aracnet.com> writes:

OP> The way I originally saw this runtime construction of a call is to
OP> make GCC generate this knowledge and implement generic functions
OP> in a runtime library (libgcc or libobjc) that uses that knowledge
OP> to build the call.

Hey, if worse came to worst, "gcc -g" generates this knowledge. 
Looks to me like "objdump --debugging" reports everything that's needed.
Link in GNU BFD and load up them reflection data structures!


  reply	other threads:[~1998-02-08 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-07 18:11 Scott Christley
1998-02-07 22:43 ` Richard Henderson
1998-02-08 10:21   ` Scott Christley
1998-02-10  3:34     ` Richard Henderson
1998-02-10 14:45   ` Anthony Green
1998-02-08 10:27 ` Ovidiu Predescu
1998-02-08 13:12   ` Marcus G. Daniels [this message]
1998-02-08 22:32     ` Ovidiu Predescu
1998-02-09  7:43       ` Bruno Haible
1998-02-09 15:33         ` Ovidiu Predescu
     [not found]           ` <199802092146.WAA04183@halles.ilog.fr>
1998-02-10 10:58             ` Ovidiu Predescu
1998-02-10 14:45               ` Joern Rennecke
1998-02-09 11:31       ` Marcus G. Daniels
1998-02-10  3:34       ` Richard Henderson
1998-02-10 10:58         ` Ovidiu Predescu
1998-02-09 14:46     ` Anthony Green

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=rfira5dlsnh.fsf@cathcart.sysc.pdx.edu \
    --to=marcusd@cathcart.sysc.pdx.edu \
    --cc=egcs@cygnus.com \
    --cc=ovidiu@aracnet.com \
    --cc=scottc@net-community.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).