Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: msnyder@redhat.com
Cc: brobecker@adacore.com, gdb-patches@sources.redhat.com, fnf@specifics.com
Subject: Re: [RFA] mips, eabi64, addr_bit == 32
Date: Sat, 17 Jun 2006 23:15:00 -0000	[thread overview]
Message-ID: <200606172314.k5HNEeqM013325@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <447E25F0.3010009@redhat.com> (message from Michael Snyder on 	Wed, 31 May 2006 16:25:36 -0700)

> Date: Wed, 31 May 2006 16:25:36 -0700
> From: Michael Snyder <msnyder@redhat.com>
> 
> Disagreement between gcc and gdb about the size of an addr
> causes numerous dwarf2-related complaints of the form:
> 
> (gdb) advance foo^M
> foo (a=dwarf2_read_address: Corrupted DWARF expression.^M
> ) at 
> /opt/redhat/gnupro-06r1-1/sources/tools/cross/gdb/testsuite/gdb.base/advan\ce.c:6^M
> 6         int b = a + 10;^M
> (gdb) FAIL: gdb.base/advance.exp: advance function called as param

Is this patch still on the table?  It looks highly suspicious to me.
I mean, you have 64-bit pointers, but 32-bit addresses?

Shouldn't we just fix GCC to emit the correct debug info?

> 2006-05-31  Michael Snyder  <msnyder@redhat.com>
> 
> 	* mips-tdep.c (mips_gdbarch_init): EABI64, addr_bit is 32.
> 	(mips_write_pc): Difference between addr_bit and ptr_bit
> 	requires sign_extension when setting $pc.
> 	
> Index: mips-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/mips-tdep.c,v
> retrieving revision 1.393
> diff -p -r1.393 mips-tdep.c
> *** mips-tdep.c	31 May 2006 23:15:50 -0000	1.393
> --- mips-tdep.c	31 May 2006 23:18:47 -0000
> *************** mips_unwind_dummy_id (struct gdbarch *gd
> *** 838,843 ****
> --- 838,847 ----
>   static void
>   mips_write_pc (CORE_ADDR pc, ptid_t ptid)
>   {
> +   /* If addr_bit is 32, force sign extension.  */
> +   if (gdbarch_addr_bit (current_gdbarch) == 32)
> +     if ((pc & 0xffffffff80000000LL) == 0x80000000)
> +       pc |= 0xffffffff00000000LL;
>     write_register_pid (mips_regnum (current_gdbarch)->pc, pc, ptid);
>   }
>   
> *************** mips_gdbarch_init (struct gdbarch_info i
> *** 4976,4981 ****
> --- 4980,4986 ----
>         tdep->default_mask_address_p = 0;
>         set_gdbarch_long_bit (gdbarch, 64);
>         set_gdbarch_ptr_bit (gdbarch, 64);
> +       set_gdbarch_addr_bit (gdbarch, 32);
>         set_gdbarch_long_long_bit (gdbarch, 64);
>         break;
>       case MIPS_ABI_N32:


  parent reply	other threads:[~2006-06-17 23:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 23:32 Michael Snyder
2006-05-31 23:39 ` Daniel Jacobowitz
2006-05-31 23:47   ` Michael Snyder
2006-06-01  1:55     ` Daniel Jacobowitz
2006-06-08 19:21       ` Michael Snyder
2006-06-08 19:39         ` Fred Fish
2006-06-17 23:15 ` Mark Kettenis [this message]
2006-06-20 20:29   ` Daniel Jacobowitz

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=200606172314.k5HNEeqM013325@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=fnf@specifics.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