From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>,
Corinna Vinschen <vinschen@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: [RFC] Supporting alternative ABIs
Date: Sat, 13 Sep 2003 19:58:00 -0000 [thread overview]
Message-ID: <3F6376E7.30601@redhat.com> (raw)
In-Reply-To: <3F609BA0.3060106@redhat.com>
> Corinna Vinschen <vinschen@redhat.com> writes:
>
>
> - EXTRACT_RETURN_VALUE, STORE_RETURN_VALUE, USE_STRUCT_CONVENTION and
> gdbarch_push_dummy_code gdbarch methods would be changed to expect
> the type of the function, not the type of its return value. They
> can use TYPE_TARGET_TYPE to get the return value type, but this will
> also give them access to the `calling_convention' for the function type.
I just looked at infcall.c:find_function_addr. GDB sometimes needs to
compute the function's type and address from incomplete information.
Andrew
next prev parent reply other threads:[~2003-09-13 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 8:41 Corinna Vinschen
2003-08-22 12:57 ` Daniel Jacobowitz
2003-08-22 21:11 ` Mark Kettenis
2003-09-11 15:58 ` Andrew Cagney
2003-09-13 19:58 ` Andrew Cagney [this message]
2003-08-22 15:42 Michael Elizabeth Chastain
2003-08-22 18:16 ` Andrew Cagney
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=3F6376E7.30601@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=vinschen@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