Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>,
	       Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches ml <gdb-patches@sourceware.org>, macro@linux-mips.org
Subject: Re: [patch] Fix BZ15121 -- x/a broken for addresses in shared libraries
Date: Thu, 10 Sep 2015 15:07:00 -0000	[thread overview]
Message-ID: <55F19CC3.8080001@redhat.com> (raw)
In-Reply-To: <CALoOobPcZOgjJ6F2Ufc72y5ZQ+OfiY-xru5B-B4jkAG_qswtow@mail.gmail.com>

On 09/10/2015 04:00 PM, Paul Pluzhnikov wrote:
> On Thu, Sep 10, 2015 at 7:33 AM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> 
>>> From: Pedro Alves <palves@redhat.com>
> 
>>> Do we need to keep sign-extending on MIPS?  Adding Maciej.
>>
>> I'm pretty sure you do.
> 
> What makes MIPS special?
> 
> I can't imagine any reason why (upper levels of) 64-bit GDB would need
> to be lied to that the 32-bit inferior's 0x80000004 pointer has
> CORE_ADDR value of 0xFFFFFFFF80000004.

MIPS has signed addresses, at the hardware level.  Thus a 32-bit ABI on
a 64-bit machine ends up seeing with sign-extended addresses.

See e.g.:
 https://www.sourceware.org/ml/gdb/2002-09/msg00084.html

Thanks,
Pedro Alves


  reply	other threads:[~2015-09-10 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 20:03 Paul Pluzhnikov
     [not found] ` <55F19100.30600@redhat.com>
2015-09-10 14:33   ` Mark Kettenis
2015-09-10 15:00     ` Paul Pluzhnikov
2015-09-10 15:07       ` Pedro Alves [this message]
2015-09-10 15:19         ` Maciej W. Rozycki
2015-09-10 15:02     ` Maciej W. Rozycki
2015-09-12 21:41       ` Paul Pluzhnikov
2015-09-12 21:56         ` Maciej W. Rozycki

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=55F19CC3.8080001@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=ppluzhnikov@google.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