public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: <anton@samba.org>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Detect 64-bit-ness in PowerPC Book III-E
Date: Fri, 19 Dec 2014 08:06:00 -0000	[thread overview]
Message-ID: <87ioh8qd0w.fsf@codesourcery.com> (raw)
In-Reply-To: <201412111530.sBBFUxsi023697@d03av02.boulder.ibm.com> (Ulrich	Weigand's message of "Thu, 11 Dec 2014 16:30:57 +0100")

Ulrich Weigand <uweigand@de.ibm.com> writes:

> Hmm.  If it actually is Book III-S, then bit 32 is "reserved", so I'm
> not sure including it in the check is safe.

Yeah, in fact, I borrow such check from strace 4.9.

>
> Anton, what would you suggest a user program to use to safely detect
> whether a ptrace-attached child is 64-bit or not, on either Book III-S
> or Book III-E systems?

Maybe, we can first detect the Book III-S vs. Book III-E, and then
detect 64-bit-ness.  However, I go through PowerISA, but don't find a
way to differentiate Book III-S and Book III-E.

>
> In any case, whatever we do, we should do both in native GDB and
> gdbserver.

Agreed.

-- 
Yao (齐尧)

  reply	other threads:[~2014-12-19  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:15 Yao Qi
2014-12-11 15:31 ` Ulrich Weigand
2014-12-19  8:06   ` Yao Qi [this message]
2014-12-19 15:49     ` Ulrich Weigand
2015-01-11  8:27       ` [PATCH 0/2, V2] " Yao Qi
2015-01-11  8:27         ` [PATCH 2/2] " Yao Qi
2015-01-13 17:00           ` Ulrich Weigand
2015-01-14  2:54             ` Yao Qi
2015-01-14 12:47               ` Ulrich Weigand
2015-01-14 14:22                 ` Yao Qi
2015-01-11  8:27         ` [PATCH 1/2] Move some ppc macros to nat/ppc-linux.h Yao Qi
2015-01-13 16:57           ` Ulrich Weigand

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=87ioh8qd0w.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=anton@samba.org \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).