Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: arm_addr_bits_remove
Date: Thu, 24 Jan 2008 04:54:00 -0000	[thread overview]
Message-ID: <479819E2.1030603@portugalmail.pt> (raw)
In-Reply-To: <8f2776cb0801231311o19c31781h8a4663c405bcd22b@mail.gmail.com>

Jim Blandy wrote:
> On Jan 23, 2008 11:28 AM, Daniel Jacobowitz wrote:
>> It was for Thumb in the first place.
>>
>> http://sourceware.org/ml/gdb-patches/2001-03/msg00182.html
>> http://sourceware.org/ml/gdb-patches/2001-04/msg00012.html
>>
>> That may not be true on new toolchains though.
> 
> Rats.  If it'd be quick for you to check current toolchains, could you?
> 

Jim Blandy wrote:
 > 2001-04-06  Fernando Nasser  <fnasser@redhat.com>
 >
 > 	* buildsym.c (record_line): Turn off unused addr bits.
 >
 > Could we try simply removing this?
 >

Removing this shows no regressions on arm-eabi or arm-linux-gnueabi.

I've also ran the testsuite on arm-linux-gnueabi arm/thumb
replacing the stripping in record_line by logging the pc being
stripped, and no odd address was ever printed.

Would a patch removing this be more acceptable then?

-- 
Pedro Alves


  reply	other threads:[~2008-01-24  4:54 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           ` Pedro Alves [this message]
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                         ` 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=479819E2.1030603@portugalmail.pt \
    --to=pedro_alves@portugalmail.pt \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.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