From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Jim Blandy <jimb@red-bean.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: arm_addr_bits_remove
Date: Thu, 24 Jan 2008 14:45:00 -0000 [thread overview]
Message-ID: <20080124133844.GA15771@caradoc.them.org> (raw)
In-Reply-To: <4798871B.4080207@codesourcery.com>
On Thu, Jan 24, 2008 at 12:39:55PM +0000, Pedro Alves wrote:
> Jim Blandy wrote:
>> On Jan 23, 2008 8:53 PM, Pedro Alves wrote:
>>> Would a patch removing this be more acceptable then?
>>
>> I'd certainly be more enthusiastic about it. :)
>>
>
> Well, then, here's one for the review-enthusiasts amongst us. :-)
If you're daring enough, this is OK - this could affect any target
defining gdbarch_addr_bits_remove so keep an eye out in case hppa,
m88k, mips, or s390 break. Please wait another day before checking it
in, in case someone else knows more about it.
I think the original patch should be committed too. Jim objected in
terms of "returning the wrong answer", but that's not really the case.
The 0x2 bit is never an extra piece of information about an address,
like the 0x1 bit is. It's part of the address; just if it happens
to be part of an ARM address, executing code there is unpredictable.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-24 13:39 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 ` Daniel Jacobowitz [this message]
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 ` arm_addr_bits_remove Maciej W. Rozycki
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=20080124133844.GA15771@caradoc.them.org \
--to=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