Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
	        Pedro Alves <pedro@codesourcery.com>,
	Jim Blandy <jimb@red-bean.com>,
	        gdb-patches <gdb-patches@sourceware.org>
Subject: Re: arm_addr_bits_remove
Date: Mon, 04 Feb 2008 14:45:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64N.0802041436060.23236@blysk.ds.pg.gda.pl> (raw)
In-Reply-To: <20080204134132.GB28485@caradoc.them.org>

On Mon, 4 Feb 2008, Daniel Jacobowitz wrote:

> >  For the record -- to ever hit this case on MIPS you would have to run the 
> > test suite in the 32-bit kernel mode, so IRIX certainly does not apply 
> > here.  One of the embedded targets might fit, e.g. using newlib and the 
> > GNU sim.  Still this would be a bug if it mattered these days as proper 
> > sign-extension of addresses is meant to be done for MIPS now.
> 
> Really?  This is for removing low bits, not high bits - I'd be more
> worried about MIPS16.

 Well, for MIPS the function only removes high bits if any at all:

static CORE_ADDR
mips_addr_bits_remove (CORE_ADDR addr)
{
  struct gdbarch_tdep *tdep = gdbarch_tdep (current_gdbarch);
  if (mips_mask_address_p (tdep) && (((ULONGEST) addr) >> 32 == 0xffffffffUL))
    return addr &= 0xffffffffUL; /* sic! */
  else
    return addr;
}

See the comment in the sources for some background which I can understand 
based on my experience with the issues over the years and which I skipped 
here due to its length.

  Maciej


  reply	other threads:[~2008-02-04 14:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 21:17 arm_addr_bits_remove Pedro Alves
2008-01-22 23:26 ` arm_addr_bits_remove Jim Blandy
2008-01-23 14:45   ` arm_addr_bits_remove Pedro Alves
2008-01-23 19:22     ` arm_addr_bits_remove Jim Blandy
2008-01-23 19:29       ` arm_addr_bits_remove Daniel Jacobowitz
2008-01-23 21:12         ` arm_addr_bits_remove Jim Blandy
2008-01-24  4:54           ` arm_addr_bits_remove Pedro Alves
2008-01-24  7:35             ` arm_addr_bits_remove Jim Blandy
2008-01-24  6:30               ` arm_addr_bits_remove Jim Blandy
2008-01-24 13:39               ` arm_addr_bits_remove Pedro Alves
2008-01-24 14:45                 ` arm_addr_bits_remove Daniel Jacobowitz
2008-01-24 14:56                   ` arm_addr_bits_remove Pedro Alves
2008-01-24 16:53                     ` arm_addr_bits_remove Jim Blandy
2008-01-24 17:01                       ` arm_addr_bits_remove Pedro Alves
2008-01-24 22:19                   ` arm_addr_bits_remove Joel Brobecker
2008-01-25  0:11                     ` arm_addr_bits_remove Pedro Alves
2008-01-25  4:13                       ` arm_addr_bits_remove Joel Brobecker
2008-01-25  9:56                         ` arm_addr_bits_remove Carlos O'Donell
2008-01-25 21:24                           ` arm_addr_bits_remove John David Anglin
2008-01-25 22:14                             ` arm_addr_bits_remove Jim Blandy
2008-01-26 13:57                               ` arm_addr_bits_remove John David Anglin
2008-02-04 10:16                     ` arm_addr_bits_remove Maciej W. Rozycki
2008-02-04 13:41                       ` arm_addr_bits_remove Daniel Jacobowitz
2008-02-04 14:45                         ` Maciej W. Rozycki [this message]
2008-02-04 14:51                           ` arm_addr_bits_remove Daniel Jacobowitz
2008-02-04 15:20                             ` arm_addr_bits_remove Maciej W. Rozycki
2008-01-24 17:18               ` arm_addr_bits_remove Mark Kettenis
2008-01-24 17:50                 ` arm_addr_bits_remove Joel Brobecker
2008-01-24 21:33                   ` arm_addr_bits_remove Jim Blandy

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=Pine.LNX.4.64N.0802041436060.23236@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    --cc=brobecker@adacore.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.com \
    --cc=pedro@codesourcery.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