From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p
Date: Wed, 25 Apr 2012 11:02:00 -0000 [thread overview]
Message-ID: <4F97D686.70306@codesourcery.com> (raw)
In-Reply-To: <1334755073-26528-1-git-send-email-yao@codesourcery.com>
On 04/18/2012 09:17 PM, Yao Qi wrote:
> Hi, this patch series is about fixing return values in C++ in GDB inf-call.
>
> In C++ ABI, section 3.1.4:
>
> "...if the return value type has a non-trivial copy constructor or
> destructor, the caller allocates space for a temporary, and passes a
> pointer to the temporary as an implicit first parameter preceding both
> the this parameter and user parameters. The callee constructs the return
> value into this temporary."
>
> Looks GDB is correct on handling C++ inf-call of return value (by checking
> language_pass_by_reference). Unfortunately, GCC is not correct here.
> currently GCC processes the return value RTL expanding like this, in
> gcc/function.c:assign_parms_augmented_arg_list():
>
> /* If struct value address is treated as the first argument, make it
> so. */
> if (aggregate_value_p (DECL_RESULT (fndecl), fndecl)
> && ! cfun->returns_pcc_struct
> && targetm.calls.struct_value_rtx (TREE_TYPE (fndecl), 1) == 0)
> {
> tree type = build_pointer_type (TREE_TYPE (fntype));
> tree decl;
> ...
>
> The use of the TARGET_STRUCT_VALUE_RTX hook to determine whether to
> honor this convention, effectively makes what should be a
> language-dependent rule, into a target-dependent convention instead.
>
> The ia64 hook takes care to detect the C++ types to return NULL (which
> is referred to in the comments as an ABI bug resolved in G++ 3.4).
> Looking across other targets, sh, c6x, m68k, are examples of targets
> which always return non-NULL in their TARGET_STRUCT_VALUE_RTX hooks, and
> are exactly those that I also predicted and reproduced the same
> symptoms.
>
> C++ ABI is intended to be cross-architecture, but C++ ABI ends up being
> target-dependent at some points. In practice, GDB has to know which
> architecture is special.
>
> As I said above, GCC changes a language-dependent rule to a
> target-dependent rule 'by mistake', so GDB has to be aware of this. That
> is the motivation to create this new gdbarch hook. If the hook is not
> installed, the default version still complies to existing GDB's behavior,
> nothing is changed.
>
> gdb:
>
> 2012-04-16 Yao Qi <yao@codesourcery.com>
> Chung-Lin Tang <cltang@codesourcery.com>
>
> * arch-utils.c (default_return_with_first_hidden_param_p): New.
> * arch-utils.h: Declare.
> * gdbarch.sh: Add return_with_first_hidden_param_p.
> * gdbarch.c, gdbarch.h: Regenerated.
> * infcall.c (call_function_by_hand): Call gdbarch_return_with_first_hidden_param_p
> instead of language_pass_by_reference.
Ping. http://sourceware.org/ml/gdb-patches/2012-04/msg00565.html
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-04-25 10:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 13:28 Yao Qi
2012-04-18 13:18 ` [PATCH 3/4] sh: Install return_with_first_hidden_param_p Yao Qi
2012-05-16 21:00 ` Tom Tromey
2012-04-18 13:18 ` [PATCH 4/4] m68k: " Yao Qi
2012-05-16 21:01 ` Tom Tromey
2012-04-18 13:18 ` [PATCH 2/4] tic6x: " Yao Qi
2012-05-16 20:59 ` Tom Tromey
2012-04-25 11:02 ` Yao Qi [this message]
2012-05-03 0:43 ` [ping 2] : [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p Yao Qi
2012-05-03 1:15 ` Joel Brobecker
2012-05-03 7:00 ` Yao Qi
2012-05-04 17:58 ` Joel Brobecker
2012-05-07 3:39 ` Yao Qi
2012-05-07 20:14 ` Joel Brobecker
2012-05-09 8:39 ` Yao Qi
2012-05-10 21:21 ` Joel Brobecker
2012-05-11 10:35 ` Yao Qi
2012-05-14 17:15 ` Joel Brobecker
2012-05-15 6:51 ` Yao Qi
2012-05-15 15:01 ` Joel Brobecker
2012-05-16 1:37 ` Yao Qi
2012-05-16 15:31 ` Joel Brobecker
2012-05-16 21:03 ` Tom Tromey
2012-05-15 18:03 ` Mark Kettenis
2012-05-16 1:55 ` Yao Qi
2012-05-17 21:02 ` Mark Kettenis
2012-07-06 13:17 ` Gary Benson
2012-05-15 15:35 ` Thomas Schwinge
2012-05-15 21:30 ` Joel Brobecker
2012-05-03 14:04 ` Chung-Lin Tang
2012-05-16 20:56 ` Tom Tromey
2012-05-16 23:03 ` Mark Kettenis
2012-06-08 14:30 ` Yao Qi
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=4F97D686.70306@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.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