Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Maxim Grigoriev <maxim@tensilica.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [commit] gdb_7_0-branch -- Fix Xtensa Call0 ABI prologue analysis
Date: Sat, 19 Sep 2009 16:39:00 -0000	[thread overview]
Message-ID: <4AB5092A.8090708@tensilica.com> (raw)
In-Reply-To: <4AB45637.3070203@tensilica.com>

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

Same patch committed onto GDB 7.0 branch.

Maxim Grigoriev wrote:
> On Xtensa CALL0 ABI, prologue analysis does not work, when MSB is set in 
> the address(es).
>
>   


[-- Attachment #2: xtensa-call0-MSB.diff --]
[-- Type: text/x-patch, Size: 682 bytes --]

2009-09-18  Maxim Grigoriev  <maxim2405@gmail.com>

        * xtensa-tdep.c (call0_analyze_prologue): Replace INT_MAX by UNIT_MAX.

Index: gdb/xtensa-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/xtensa-tdep.c,v
retrieving revision 1.39
diff -u -r1.39 xtensa-tdep.c
--- gdb/xtensa-tdep.c	14 Aug 2009 00:32:32 -0000	1.39
+++ gdb/xtensa-tdep.c	19 Sep 2009 03:48:44 -0000
@@ -2125,7 +2125,7 @@
      Assume we may be in the prologue until we hit a flow control instr.  */
 
   rtmp = NULL;
-  body_pc = INT_MAX;
+  body_pc = UINT_MAX;
   end_pc = 0;
 
   /* Find out, if we have an information about the prologue from DWARF.  */

      parent reply	other threads:[~2009-09-19 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19  3:56 [commit] " Maxim Grigoriev
2009-09-19  4:09 ` Maxim Grigoriev
2009-09-19  5:03   ` Joel Brobecker
2009-09-19 16:39 ` Maxim Grigoriev [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=4AB5092A.8090708@tensilica.com \
    --to=maxim@tensilica.com \
    --cc=gdb-patches@sourceware.org \
    /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