From: Elena Zannoni <ezannoni@redhat.com>
To: vinschen@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-tdep.c (sh_use_struct_convention): Restructure and fix
Date: Thu, 09 Oct 2003 22:51:00 -0000 [thread overview]
Message-ID: <16261.50096.713531.701890@localhost.redhat.com> (raw)
In-Reply-To: <20031004180852.GA29063@cygbert.vinschen.de>
Corinna Vinschen writes:
> On Sat, Oct 04, 2003 at 11:54:09AM -0400, Andrew Cagney wrote:
> > > * sh-tdep.c (sh_use_struct_convention): Clean up to have a
> > > more readable code. Accomodate 4 byte structs with 4 byte sized
> > > first field (e.g. bitfields).
> >
> > Corinna,
> >
> > 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.
>
> I think my patch is fine. I'm fixing non-deprecated functions to
> work better than before. There's nothing wrong with this and I
> don't see any gain to use an entirely new technique (2 days old!)
> to get probably new errors which I don't have using this method.
>
> Fixing the bugs is step 1. Converting them to a new technique is
> another, later step.
Hmm, I think you guys are all getting worked up for nothing, really.
Rereading the thread, I think Andrew was referring to a different way
to implement this set of ABI related functions, so that it would
become easier to do something else that Corinna had posted earlier,
namely supporting the Renesas ABI based on the current function,
i.e. here:
http://sources.redhat.com/ml/gdb-patches/2003-09/msg00524.html
To do what needed, we would have to pass the function address as
parameter to these sh-tdep.c functions. If we tighten the lot into
fewer methods, then there are less things to change. So at this
point, what is still unresolved is whether or not somebody is going to
do the work, i.e. add an automatic mechanism to detect the abi.
If not, what Andrew is suggesting is not a priority.
If yes, it will need to be done.
And, really, this discussion belongs to the other thread.
As far as the change posted in this thread, I'll reply separately.
elena
>
> Corinna
>
> --
> Corinna Vinschen
> Cygwin Developer
> Red Hat, Inc.
next prev parent reply other threads:[~2003-10-09 22:51 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
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 [this message]
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=16261.50096.713531.701890@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.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