From: Markus Deuling <deuling@de.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
msnyder@specifix.com,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [rfc]: Replace current_gdbarch in sentinel-frame.c
Date: Mon, 18 Feb 2008 15:28:00 -0000 [thread overview]
Message-ID: <47B9A385.5000604@de.ibm.com> (raw)
In-Reply-To: <200802151858.m1FIwvFg007698@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Ulrich Weigand schrieb:
> Thiago Jung Bauermann wrote:
>> On Fri, 2008-02-15 at 18:43 +0100, Ulrich Weigand wrote:
>>> This is not OK -- as the sentinel frame is always the innermost
>>> frame, next_frame will always be NULL here.
>> Actually, what I observe here when running GDB is that next_frame is the
>> sentinel frame, probably because sentinel frame's next field points back
>> to itself.
>
> Ah, right, I forgot about that. Still, it seems best to try to get
> rid of this hack completely ...
>
I tested *addrp = 0 on x86 and saw no regression. I changed the patch to remove
register_offset_hack completely.
Ok ?
ChangeLog:
* sentinel-frame.c (sentinel_frame_prev_register): Do not call
register_offset_hack anymore.
* regcache.{c,h} (register_offset_hack): Remove.
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
[-- Attachment #2: diff-sentinel --]
[-- Type: text/plain, Size: 2180 bytes --]
diff -urpN src/gdb/regcache.c dev/gdb/regcache.c
--- src/gdb/regcache.c 2008-01-01 23:53:12.000000000 +0100
+++ dev/gdb/regcache.c 2008-02-18 16:19:40.000000000 +0100
@@ -761,18 +761,6 @@ regcache_cooked_write_part (struct regca
regcache_cooked_read, regcache_cooked_write);
}
-/* Hack to keep code that view the register buffer as raw bytes
- working. */
-
-int
-register_offset_hack (struct gdbarch *gdbarch, int regnum)
-{
- struct regcache_descr *descr = regcache_descr (gdbarch);
- gdb_assert (regnum >= 0 && regnum < descr->nr_cooked_registers);
- return descr->register_offset[regnum];
-}
-
-
/* Supply register REGNUM, whose contents are stored in BUF, to REGCACHE. */
void
diff -urpN src/gdb/regcache.h dev/gdb/regcache.h
--- src/gdb/regcache.h 2008-01-01 23:53:12.000000000 +0100
+++ dev/gdb/regcache.h 2008-02-18 16:21:04.000000000 +0100
@@ -104,18 +104,6 @@ extern void regcache_raw_collect (const
int regnum, void *buf);
-/* The register's ``offset''.
-
- FIXME: cagney/2002-11-07: The frame_register() function, when
- specifying the real location of a register, does so using that
- registers offset in the register cache. That offset is then used
- by valops.c to determine the location of the register. The code
- should instead use the register's number and a location expression
- to describe a value spread across multiple registers or memory. */
-
-extern int register_offset_hack (struct gdbarch *gdbarch, int regnum);
-
-
/* The type of a register. This function is slightly more efficient
then its gdbarch vector counterpart since it returns a precomputed
value stored in a table. */
diff -urpN src/gdb/sentinel-frame.c dev/gdb/sentinel-frame.c
--- src/gdb/sentinel-frame.c 2008-01-01 23:53:12.000000000 +0100
+++ dev/gdb/sentinel-frame.c 2008-02-18 16:21:39.000000000 +0100
@@ -54,7 +54,7 @@ sentinel_frame_prev_register (struct fra
onto the corresponding hardware register. */
*optimized = 0;
*lvalp = lval_register;
- *addrp = register_offset_hack (current_gdbarch, regnum);
+ *addrp = 0;
*realnum = regnum;
/* If needed, find and return the value of the register. */
next prev parent reply other threads:[~2008-02-18 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 9:27 Markus Deuling
2008-02-15 17:44 ` Ulrich Weigand
2008-02-15 18:40 ` Thiago Jung Bauermann
2008-02-15 18:59 ` Ulrich Weigand
2008-02-18 15:28 ` Markus Deuling [this message]
2008-02-18 16:05 ` Ulrich Weigand
2008-02-18 16:38 ` Markus Deuling
2008-02-15 17:44 ` Michael Snyder
2008-02-15 17:51 ` Michael Snyder
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=47B9A385.5000604@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@specifix.com \
--cc=uweigand@de.ibm.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