From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: randolph@tausq.org, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] function descriptor handling for push_dummy_call
Date: Sat, 05 Jun 2004 15:58:00 -0000 [thread overview]
Message-ID: <1659-Sat05Jun2004185545+0300-eliz@gnu.org> (raw)
In-Reply-To: <40C1CC51.1020706@gnu.org> (message from Andrew Cagney on Sat, 05 Jun 2004 09:36:17 -0400)
> Date: Sat, 05 Jun 2004 09:36:17 -0400
> From: Andrew Cagney <cagney@gnu.org>
> >
> > However, the change seems to be a cosmetic one: it renames a single
> > argument to push_dummy_call from `func_addr' to `function'. Why is
> > that necessary?
>
> I think it is, the parameter is now a `struct value' function and not a
> function's code address.
The suggested change doesn't indicate that in any way.
next prev parent reply other threads:[~2004-06-05 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 6:10 Randolph Chung
2004-06-04 18:44 ` Andrew Cagney
2004-06-05 10:17 ` Eli Zaretskii
2004-06-05 13:36 ` Andrew Cagney
2004-06-05 15:58 ` Eli Zaretskii [this message]
2004-06-05 16:23 ` Randolph Chung
2004-06-05 21:12 ` Eli Zaretskii
2004-06-07 2:15 ` [patch/commit] " Randolph Chung
2004-06-07 4:25 ` Eli Zaretskii
2004-06-07 4:31 ` Randolph Chung
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=1659-Sat05Jun2004185545+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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