Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: SH follow up, part 2 (was Re: [RFA] sh-tdep.c: Follow up patch to implement two different ABIs)
Date: Fri, 26 Sep 2003 11:15:00 -0000	[thread overview]
Message-ID: <20030926111543.GH22787@cygbert.vinschen.de> (raw)
In-Reply-To: <16243.25635.470137.318341@localhost.redhat.com>

On Thu, Sep 25, 2003 at 05:54:43PM -0400, Elena Zannoni wrote:
> Corinna Vinschen writes:
>  > Currently there's no way to differ between these two ABIs automatically
>  > though that might change at some later point.  The user has to change
>  > the ABI on the command line by hand.  The compiler option was -mhitachi,
>  > gcc is just changing to -mrenesas to reflect the company name change.
> 
> Hmm but then the user can set the calling convention to the wrong one.
> Also the finish command, I am afraid, will be confused. There should
> be something detecting the calling convention from the executable. Is
> the info recorded in the file anywhere? I.e. would readelf/objdump
> show it?

No.  I started a discussion about this on gdb four weeks ago but at this
point there is no chance to find this out.  The automatism requires some
work in gcc and gdb which is not done yet and which is not target
dependent.  It's another step.  This patch only contains the first step
necessary to allow to debug two ABIs for sh.  It requires user
intervention.  If the changes for automating the ABI stuff are done, the
next target dependent step is to add the "auto" flag and to make it the
default.

> These descriptions should be comments in the file, the more verbiage
> the better.

The comments are in the code.

> I don't have anything in particular against these patches, but I'd like
> to have a better idea about how to solve this calling convention issue
> before the changes go in.

http://sources.redhat.com/ml/gdb/2003-08/msg00252.html

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.


      reply	other threads:[~2003-09-26 11:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 16:11 [RFA] sh-tdep.c: Follow up patch to implement two different ABIs Corinna Vinschen
2003-09-23 20:34 ` Elena Zannoni
2003-09-23 21:27   ` Andrew Cagney
2003-09-24  8:44     ` Corinna Vinschen
2003-09-24  9:56   ` SH follow up, part 1 (was Re: [RFA] sh-tdep.c: Follow up patch to implement two different ABIs) Corinna Vinschen
2003-09-25 21:39     ` Elena Zannoni
2003-09-26 11:14       ` Corinna Vinschen
2003-10-01 20:26         ` Elena Zannoni
2003-10-02 10:47           ` Corinna Vinschen
2003-09-24 10:39   ` SH follow up, part 2 " Corinna Vinschen
2003-09-25 21:44     ` Elena Zannoni
2003-09-26 11:15       ` Corinna Vinschen [this message]

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=20030926111543.GH22787@cygbert.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=gdb-patches@sources.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