From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: value to function?
Date: Wed, 01 Oct 2003 06:01:00 -0000 [thread overview]
Message-ID: <vt2fzidmree.fsf@zenia.home> (raw)
In-Reply-To: <3F799B8C.8030601@redhat.com>
Andrew Cagney <ac131313@redhat.com> writes:
> > Andrew Cagney <ac131313@redhat.com> writes:
> >
> >> If the proposal to pass a function value to push_dummy_call is going
> >> to fly there's going to need to be a method that converts an arbitrary
> >> value into a function/method value.
> > A new gdbarch method to be called from where, specifically? This
> > area
> > is a mess (just try describing the behavior of find_function_addr...),
> > so I'm not sure what you mean.
>
> Now I think I'm missing something. What new architecture method?
> What mess?
Never mind. You said "there's going to need to be a method that
converts..." Since you said "method", I assumed you didn't mean
"function", so I was trying to figure out what sort of method you
meant.
> > Kind of like find_function_addr() and the oposite of value_coerce_function.
>
> pre (I guess that value isn't void or NULL);
> struct value *foo (struct value *);
> post (VALUE_TYPE (foo (value)) == TYPE_CODE_FUNC
> || VALUE_TYPE (foo (value)) == TYPE_CODE_METHOD));
>
> it would be used in relative proximity to push_dummy_call and
> return_value (ex, replace find_function_addr).
Sure, this is just a nicer packaging of find_function_addr, which
seems to be doing two separable jobs:
- coercing various non-function values into callable things, and
- extracting that callable thing's entry point address and return
type.
A function value carries both those data in a handy and obvious way.
prev parent reply other threads:[~2003-10-01 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 16:07 Andrew Cagney
2003-09-30 12:13 ` Jim Blandy
2003-09-30 16:53 ` Andrew Cagney
2003-10-01 6:01 ` Jim Blandy [this message]
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=vt2fzidmree.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.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).