From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: yao@codesourcery.com, gdb-patches@sourceware.org,
cltang@codesourcery.com
Subject: Re: [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p
Date: Wed, 16 May 2012 23:03:00 -0000 [thread overview]
Message-ID: <201205162303.q4GN3JK4001896@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <87zk97n8ve.fsf@fleche.redhat.com> (message from Tom Tromey on Wed, 16 May 2012 14:55:49 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 16 May 2012 14:55:49 -0600
>
> >>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
>
> Yao> Hi, this patch series is about fixing return values in C++ in GDB inf-call.
>
> Thanks. I read through the whole thread and dug into the code a bit as
> well. I think your approach is fine.
>
> Yao> Unfortunately, GCC is not correct here. currently GCC processes
> Yao> the return value RTL expanding like this, in
> Yao> gcc/function.c:assign_parms_augmented_arg_list():
>
> I suppose it would be nice to get some commitment on the GCC side to
> declare this a non-bug, and part of the ABI.
>
> Yao> +int
> Yao> +default_return_with_first_hidden_param_p (struct gdbarch *gdbarch,
> Yao> + struct type *type)
>
> This could use an introductory comment, just explaining it is an
> implementation suitable for use by such-and-such gdbarch method.
>
> Yao> +# Return true if the return value of function is stored in the first hidden parameter.
> Yao> +# In theory, this feature should be language-dependent, specified by language and its ABI,
> Yao> +# such as C++. Unfortunately, compiler may implement it to a target-dependent feature.
> Yao> +# So that we need such hook here to be aware of this in GDB.
>
> Over-long lines.
>
> Ok with those fixes.
If this hasn't been committed yet, please wait.
next prev parent reply other threads:[~2012-05-16 23:03 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 2/4] tic6x: Install return_with_first_hidden_param_p Yao Qi
2012-05-16 20:59 ` 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 3/4] sh: " Yao Qi
2012-05-16 21:00 ` Tom Tromey
2012-04-25 11:02 ` [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p Yao Qi
2012-05-03 0:43 ` [ping 2] : " 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 [this message]
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=201205162303.q4GN3JK4001896@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=cltang@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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