Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Ben Harris <bjh21@netbsd.org>,
	gdb-patches@sourceware.cygnus.com, Richard.Earnshaw@arm.com
Subject: Re: [Fwd: Fix arm_addr_bits_remove: 26-bit Thumb doesn't exist]
Date: Mon, 22 Oct 2001 06:18:00 -0000	[thread overview]
Message-ID: <3BD41C18.ADFBC7C5@redhat.com> (raw)
In-Reply-To: <m37ktof17j.fsf@north-pole.nickc.cambridge.redhat.com>

Thank you Nick and Richard.

I haven't heard anything on the contrary from Scott (native ARM)
so I will check this in later today or tomorrow.

Thanks for the patch Ben.

Regards to all,
Fernando


Nick Clifton wrote:
> 
> Hi Fernando, Hi Ben,
> 
> > From: Ben Harris <bjh21@netbsd.org>
> >
> > I haven't actually encountered this bug in reality yet, but it looks
> > to me as if arm_addr_bits_remove() is bogus.  Specifically, it has a
> > case for Thumb state in a 26-bit mode.  According to the ARM ARM
> > (2nd Edition, section A8.1), no processor will support both 26-bit
> > mode and thumb state at all, let alone at the same time.  I suspect
> > this might be a noticeable problem when debugging SVC mode code,
> > since then R15 will have its bottom bit set, which arm_pc_is_thumb()
> > is likely to interpret as meaning the CPU is in Thumb state.
> >
> > ChangeLog entry:
> >
> > 2001-10-20  Ben Harris  <bjh21@netbsd.org>
> >
> >       * arm-tdep.c (arm_addr_bits_remove): Don't believe in 26-bit
> >       Thumb.
> 
> This looks like a reasonable patch to me.  I do not have the authority
> to approve it, but I would certainly recommend it to the GDB
> maintainers.
> 
> Cheers
>         Nick

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


      reply	other threads:[~2001-10-22  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3BD301F6.D679AB69@redhat.com>
2001-10-22  3:00 ` Nick Clifton
2001-10-22  6:18   ` Fernando Nasser [this message]

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=3BD41C18.ADFBC7C5@redhat.com \
    --to=fnasser@redhat.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=bjh21@netbsd.org \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=nickc@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