Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Corinna Vinschen <vinschen@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-tdep.c (sh_use_struct_convention): Restructure and fix
Date: Sat, 04 Oct 2003 17:35:00 -0000	[thread overview]
Message-ID: <3F7F04D4.3060506@redhat.com> (raw)
In-Reply-To: <1031004170432.ZM27387@localhost.localdomain>

> On Oct 4, 11:54am, Andrew Cagney wrote:
> 
> 
>> See: http://sources.redhat.com/ml/gdb-patches/2003-10/msg00033.html.
>> The ppc64_sysv_return_value code in ppc-sysv-tdep.c, has been written in 
>> a way that allows a quick update to this new iterface.
> 
> 
> Andrew,
> 
> There are pros and cons to the approach that you used in
> ppc64_sysv_abi_return_value().
> 
> On the pro side - and this is definitely a good thing - you keep the
> struct convention information together with the implementation of how
> to return a value.

It is stronger than that, it moves all of the ABIs struct convention 
logic to one place.  At present key parts of the logic are scattered 
inconsistently across core parts of GDB

The result is a longer but more correct function.

> But this is also a con because you've spread the definition of
> "use_struct_convention" out over a much larger number of lines.  It
> isn't (IMO) as easy to comprehend when arranged in this way.

As my spec for the interface points out, if this were an OO language it 
would have a different interface.

> The jury is still out (at least as far as I'm concerned) as to
> which approach is better.  I do happen to think that your approach
> is better for ppc64 (and ppc too), but this may not necessarily be the
> case for other architectures.

This is a technical problem.  The return_value patch fixes the problem 
of GDB not being able to handle all cases of:

	return return-value-in-register

correctly.  If Corinna instead implements use_struct_convention, then 
that bug won't be fixed.

Andrew


  reply	other threads:[~2003-10-04 17:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 11:39 Corinna Vinschen
2003-10-04 15:54 ` Andrew Cagney
2003-10-04 17:04   ` Kevin Buettner
2003-10-04 17:35     ` Andrew Cagney [this message]
2003-10-04 18:13       ` Kevin Buettner
2003-10-06 16:31         ` Andrew Cagney
2003-10-04 18:08   ` Corinna Vinschen
2003-10-06 15:52     ` Andrew Cagney
2003-10-07 14:52       ` Corinna Vinschen
2003-10-08 17:39         ` Andrew Cagney
2003-10-09 22:51     ` Elena Zannoni
2003-10-11 20:05       ` Andrew Cagney
2003-10-09 22:51 ` Elena Zannoni
2003-10-10  7:29   ` Corinna Vinschen
2003-10-10 15:01     ` Corinna Vinschen
2003-10-10 16:32       ` Elena Zannoni
2003-10-10 16:59         ` Corinna Vinschen
2003-10-10 17:56           ` Elena Zannoni
2003-10-10 19:14             ` Corinna Vinschen
2003-10-10 16:28     ` Elena Zannoni

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=3F7F04D4.3060506@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --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