Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Richard.Earnshaw@arm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] arm-netbsdelf cross-debugging fixes
Date: Tue, 03 Sep 2002 15:40:00 -0000	[thread overview]
Message-ID: <20020903154031.U12843@dr-evil.shagadelic.org> (raw)
In-Reply-To: <200209031923.g83JN2109855@pc960.cambridge.arm.com>; from rearnsha@cambridge.arm.com on Tue, Sep 03, 2002 at 08:23:01PM +0100

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

On Tue, Sep 03, 2002 at 08:23:01PM +0100, Richard Earnshaw wrote:

 > > While there, I also fixed a problem with arm_addr_bits_remove -- No
 > > 26-bit systems can run in Thumb mode, and so doing an arm_pc_is_thumb
 > > on them is unnecessary (and could return incorrect results if debugging
 > > code which runs in FIQ mode, since (pc & 1) == FIQ mode on those CPUs).
 > > 
 > Yep, that would be a good move, but it would be easier to say yes if it 
 > were a separate patch.

Ok, here's this one, separated out.

	* arm-tdep.c (arm_addr_bits_remove): Don't check for Thumb mode
	if arm_apcs_32 is false.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>

[-- Attachment #2: arm-addr-bits-patch --]
[-- Type: text/plain, Size: 892 bytes --]

Index: arm-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/arm-tdep.c,v
retrieving revision 1.69
diff -c -r1.69 arm-tdep.c
*** arm-tdep.c	24 Aug 2002 00:21:34 -0000	1.69
--- arm-tdep.c	3 Sep 2002 22:29:17 -0000
***************
*** 225,234 ****
  static CORE_ADDR
  arm_addr_bits_remove (CORE_ADDR val)
  {
!   if (arm_pc_is_thumb (val))
!     return (val & (arm_apcs_32 ? 0xfffffffe : 0x03fffffe));
    else
!     return (val & (arm_apcs_32 ? 0xfffffffc : 0x03fffffc));
  }
  
  /* When reading symbols, we need to zap the low bit of the address,
--- 225,234 ----
  static CORE_ADDR
  arm_addr_bits_remove (CORE_ADDR val)
  {
!   if (arm_apcs_32)
!     return (val & (arm_pc_is_thumb (val) ? 0xfffffffe : 0xfffffffc));
    else
!     return (val & 0x03fffffc);
  }
  
  /* When reading symbols, we need to zap the low bit of the address,

  parent reply	other threads:[~2002-09-03 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01 16:58 Jason R Thorpe
2002-09-02 12:56 ` Andrew Cagney
2002-09-03 12:23 ` Richard Earnshaw
2002-09-03 12:34   ` Jason R Thorpe
2002-09-04  4:10     ` Richard Earnshaw
2002-09-03 15:40   ` Jason R Thorpe [this message]
2002-09-04  2:56     ` Richard Earnshaw

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=20020903154031.U12843@dr-evil.shagadelic.org \
    --to=thorpej@wasabisystems.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sources.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