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: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-tdep.c: Add dwarf/dwarf2 regnum mapping functions
Date: Fri, 07 Mar 2003 19:13:00 -0000	[thread overview]
Message-ID: <3E68EF61.6070601@redhat.com> (raw)
In-Reply-To: <1030307175146.ZM16168@localhost.localdomain>


>> mips_tdep could certainly gain a local tdep->fp0_regnum though.
> 
> 
> Did you notice the references to FP0_REGNUM in mips-linux-tdep.c and
> mips-nat.c?.  If we do as you suggest, an access method will need to
> be added to mips-tdep.h for getting at tdep->fp0_regnum (since you
> refuse to export the mips tdep struct).  Also, all occurrences of
> FP0_REGNUM in mips-linux-tdep.c and mips-nat.c will need to be
> rewritten to use this access method.

I ignored everything that wasn't core.
Such a rewrite goes on my to-do list.

> Certainly all of this could be done, but the need to know the first
> floating point register number is something that's shared among a
> number of ports.  Doesn't it makes sense to define (as has already
> been done) a common mechanism for determining this register number
> rather than letting each port develop ad hoc methods?

The problem is that FP0_REGNUM has no narrow and well defined meaning. 
  Same problem as with SP_REGNUM, PC_REGNUM, FP_REGNUM.

As a specific example.  Given an ISA with 64 bit FP registers that is 
running a 32 bit FP ABI (debug info refers to 32 bit FP registers). 
/proc assumes FP0_REGNUM designates the first 64 bit [raw] FP register, 
yet dwarf2 assumes that FP0_REGNUM designates the first 32 bit [cooked] 
FP register.

It doesn't work (well, ok the current mess involving register 
convertible kind of half sort of makes it appear to work).  Per previous 
  patches, that code needs an overhaul.

Andrew



  parent reply	other threads:[~2003-03-07 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 21:17 Kevin Buettner
2003-03-07 17:04 ` Andrew Cagney
2003-03-07 17:52   ` Kevin Buettner
2003-03-07 18:52     ` Andrew Cagney
2003-03-11 21:22       ` Kevin Buettner
2003-03-11 22:06         ` Andrew Cagney
2003-03-07 19:13     ` Andrew Cagney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-31 23:11 [RFA] MIPS: Add mappings for HI and LO registers Kevin Buettner
2003-04-02  3:36 ` Andrew Cagney
2003-03-04 17:24 [RFA] mips-tdep.c: Fix printing of floats in "info all-registers" Kevin Buettner
2003-03-04 18:01 ` Andrew Cagney
2002-12-17 10:35 [patch/rfc] Add get_*() to rs6000-tdep.c Andrew Cagney
     [not found] ` <ac131313@redhat.com>
2002-12-17 14:13   ` Kevin Buettner
2002-12-18  7:37     ` Andrew Cagney
2003-03-11 23:16   ` [RFA] mips-tdep.c: Add dwarf/dwarf2 regnum mapping functions Kevin Buettner
2003-03-11 23:18   ` [RFA] mips-tdep.c: Fix printing of floats in "info all-registers" Kevin Buettner
2003-04-02  5:13   ` [RFA] MIPS: Add mappings for HI and LO registers Kevin Buettner

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