Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
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: Thu, 22 Apr 2004 22:49:00 -0000	[thread overview]
Message-ID: <40884BEF.5070909@redhat.com> (raw)
In-Reply-To: <40884155.2090205@gnu.org>

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

> 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 the bfd_arch_info:
{bits_per_word = 64, bits_per_address = 64, bits_per_byte = 8,
   arch = bfd_arch_mips, mach = 64, arch_name = 0x8382960 "mips",
   printable_name = 0x8382a50 "mips:isa64", section_align_power = 3,
   the_default = 0, compatible = 0x82c36a4 <mips_compatible>,
   scan = 0x825f3c3 <bfd_default_scan>, next = 0x8382f00}

Here's your tdep info:
{elf_flags = 1610625025, mips_abi = MIPS_ABI_EABI32,
   found_abi = MIPS_ABI_EABI32, mips_fpu_type = MIPS_FPU_DOUBLE,
   mips_last_arg_regnum = 11, mips_last_fp_arg_regnum = 57,
   mips_default_saved_regsize = 4, mips_fp_register_double = 0,
   mips_default_stack_argsize = 4, default_mask_address_p = 0,
   mips64_transfers_32bit_regs_p = 0, regnum = 0x840968c,
   mips_processor_reg_names = 0x83995c0}
(GDB) p /x tdep.elf_flags
$10 = 0x60003001




  reply	other threads:[~2004-04-22 22:49 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 [this message]
2004-04-28 21:45         ` Andrew Cagney
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=40884BEF.5070909@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@gnu.org \
    --cc=cagney@redhat.com \
    --cc=drow@mvista.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