From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Clear upper bits during sign extension
Date: Tue, 30 Dec 2014 13:47:00 -0000 [thread overview]
Message-ID: <87vbktuu5p.fsf@codesourcery.com> (raw)
In-Reply-To: <54A29886.8030603@redhat.com> (Pedro Alves's message of "Tue, 30 Dec 2014 12:20:22 +0000")
Pedro Alves <palves@redhat.com> writes:
> So I think we should either explicitly always clear bits above TYPE_LENGTH
> after value_as_address, with a comment mentioning that we don't want
> any magic bits that gdbarch_pointer_to_address would give us,
> or, given we know the value is really an offset, simply extract the value
> that way. Like in the patch below:
The latter is fine to me.
> + byte_order = gdbarch_byte_order (get_type_arch (type));
How about getting gdbarch via get_frame_arch (frame)? How about
removing gdb_sign_extend as it is no longer used?
I'll post a full version on top of yours.
--
Yao (齐尧)
next prev parent reply other threads:[~2014-12-30 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 1:13 Yao Qi
2014-12-29 3:07 ` Joel Brobecker
2014-12-29 3:38 ` Yao Qi
2014-12-29 3:53 ` Joel Brobecker
2014-12-29 5:29 ` Doug Evans
2014-12-29 6:27 ` Yao Qi
2014-12-29 10:48 ` Pedro Alves
2014-12-30 9:20 ` Yao Qi
2014-12-30 12:20 ` Pedro Alves
2014-12-30 13:47 ` Yao Qi [this message]
2015-01-08 5:40 ` Yao Qi
2015-01-08 10:42 ` Pedro Alves
2015-01-08 13:06 ` Yao Qi
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=87vbktuu5p.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).