Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, cagney <cagney@redhat.com>,
	Daniel Jacobowitz <drow@mvista.com>
Subject: Re: [RFA] mips 32/64 register/stack fix
Date: Wed, 28 Apr 2004 21:45:00 -0000	[thread overview]
Message-ID: <409025F2.9080704@gnu.org> (raw)
In-Reply-To: <40884BEF.5070909@redhat.com>

> Andrew Cagney wrote:
> 
>>> #0  register_size (gdbarch=0x84093e8, regnum=120)
>>
>>
>>
>> 120 looks large enough to be cooked (but to confirm this can you look at "maint print raw-registers".  This will also tell us the register's type, and hence confirm the size.
> 
> 
> Yes, raw is from 0 to 89, and cooked is from 90 to 179.
> regcache->descr->sizeof_register is as follows:
> 8 for all raw
> 8 for the first 70 cooked
> 4 for the last 20 cooked
> 
> register_type looks like:
> raw:
> 38 @ int64
> 32 @ double64
> 20 @ int64
> cooked:
> 38 @ int64
> 32 @ double64
> 20 @ int32

good.

>> Given that you see 8, this suggests that the register's type is wrong (see mips_register_type).
> 
> 
> It looks to me as if mips_register_type relies on mips_regsize.
> Which returns 8.  Yep, and mips_register_type (120) returns int64_t.
> 
> But mips_saved_regsize (tdep) returns 4 (as it should, I guess).
> 
>> Also, what information is available in the object file header?
> 
> 
> Can you be more specific?
[...]
> Here's your tdep info:
> {elf_flags = 1610625025, mips_abi = MIPS_ABI_EABI32,

I was looking to see if anything like that was present -> it is clearly 
identified as a 32-bit ABI binary.

I think the bug is in mips_register_type, the tail end should probably 
be changed to read something like:

   else if (regnum >= NUM_REGS
	   && gdbarch_tdep (gdbarch)->mips64_transfers_32bit_regs_p)
     /* The target, while using a 64-bit raw register buffer, is only
        transfering 32-bits of each integer register.  Reflect this in
        the cooked/pseudo register value.  */
     return builtin_type_int32;
   else if (regnum > NUM_REGS
	   && mips_saved_regsize (gdbarch) == 4)
     /* A 32-bit ABI such as o32 possibly running on a 64-bit ISA.  */
     return builtin_type_int32;
   else if (mips_regsize (gdbarch) == 8)
     /* 64-bit ISA.  */
     return builtin_type_int64;
   else
     /* 32-bit ISA.  */
     return builtin_type_int32;

Andrew




  reply	other threads:[~2004-04-28 21:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 18:49 Michael Snyder
2004-04-22 19:59 ` Andrew Cagney
2004-04-22 21:29   ` Daniel Jacobowitz
2004-04-22 21:43   ` Michael Snyder
2004-04-22 22:04     ` Andrew Cagney
2004-04-22 22:49       ` Michael Snyder
2004-04-28 21:45         ` Andrew Cagney [this message]
2004-04-29  3:12           ` Daniel Jacobowitz
2004-04-29 13:40             ` Andrew Cagney
2004-04-29 14:34               ` Daniel Jacobowitz
2004-04-29 18:32                 ` [commit] mips_isa_regsize, mips_abi_regsize; Was: " Andrew Cagney
2004-04-29 19:45                   ` [commit] compute abi regsize; Was: Andrew Cagney
2004-04-29 17:58               ` [RFA] mips 32/64 register/stack fix Michael Snyder
2004-04-29 19:49                 ` Andrew Cagney
2004-04-29 21:15                   ` Michael Snyder
2004-04-29 21:36                     ` Andrew Cagney
2004-04-30  0:40                       ` Andrew Cagney

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=409025F2.9080704@gnu.org \
    --to=cagney@gnu.org \
    --cc=cagney@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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