Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: davem@davemloft.net
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow struct 'return' on 32-bit sparc.
Date: Tue, 05 Feb 2013 20:19:00 -0000	[thread overview]
Message-ID: <201302052018.r15KIwKZ025007@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <20130204.200254.1810401167797646953.davem@davemloft.net>	(message from David Miller on Mon, 04 Feb 2013 20:02:54 -0500 (EST))

> Date: Mon, 04 Feb 2013 20:02:54 -0500 (EST)
> From: David Miller <davem@davemloft.net>
> 
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> Date: Tue, 5 Feb 2013 00:57:15 +0100 (CET)
> 
> > The sparc-tdep.c bits are correct as far as I can see.
> > 
> > I think it would be better if your new function would still have
> > "struct_return" in its name.  My suggestion would be
> > "struct_return_convention".
> > 
> > Also,
>  ...
> > Return RETURN_VALUE_REGISTER_CONVENTION if there is nothing to return
> > seems to be a bit odd.  But since convention_for_return() is never
> > called with code being TYPE_CODE (there is an explicit check for that
> > in stack.c:return_command()) you could simply leave the check in
> > using_struct_return().
> 
> Agreed on all counts, thanks for the feedback.
> 
> Here is the updated patch:
> 
> gdb/
> 
> 	* sparc-tdep.c (sparc32_return_value): Handle writing return value when
> 	using RETURN_VALUE_ABI_PRESERVES_ADDRESS.
> 	* value.c (struct_return_convention): New function.
> 	(using_struct_return): Implement in terms of struct_return_convention.
> 	* value.h (struct_return_convention): Declare.
> 	* stack.c (return_command): Allow successful overriding of the return
> 	value when RETURN_VALUE_ABI_PRESERVES_ADDRESS.

Thanks, that looks good to me.  Perhaps wait a day or two to give
other people a chance to comment on the stack.c/value.c changes.

Mark


  reply	other threads:[~2013-02-05 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 21:13 David Miller
2013-02-04 23:57 ` Mark Kettenis
2013-02-05  1:03   ` David Miller
2013-02-05 20:19     ` Mark Kettenis [this message]
2013-02-05 20:31       ` David Miller
2013-02-06 19:41     ` David Miller
2013-02-08 18:17 ` Ulrich Weigand
2013-02-08 19:10   ` David Miller
2013-02-08 19:13     ` David Miller

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=201302052018.r15KIwKZ025007@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=davem@davemloft.net \
    --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