From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [RFA/RFT PATCH 0/3] Add TDB regset support
Date: Fri, 07 Jun 2013 15:59:00 -0000 [thread overview]
Message-ID: <87li6lud1m.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <51B1F629.5070006@redhat.com> (Pedro Alves's message of "Fri, 07 Jun 2013 16:03:05 +0100")
Pedro Alves <palves@redhat.com> writes:
> Why isn't this exposed as a new target description that includes the
> new register set?
It would require extracting the hardware capabilities from the core
file's auxiliary vector in order to distinguish between platforms with
and without the transactional-execution facility. I guess it could be
done, but I didn't consider it that important. Do you see any problems
with the current approach?
next prev parent reply other threads:[~2013-06-07 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 13:44 Andreas Arnez
2013-06-07 13:50 ` [PATCH 1/3] S/390 regmap rework Andreas Arnez
2015-05-05 19:17 ` Regression on gdb.base/checkpoint.exp on S/390 (was: Re: [PATCH 1/3] S/390 regmap rework) Sergio Durigan Junior
2015-05-06 18:16 ` Regression on gdb.base/checkpoint.exp on S/390 Andreas Arnez
2013-06-07 13:51 ` [PATCH 2/3] Add TDB regset Andreas Arnez
2013-06-07 13:53 ` [PATCH 3/3] Dynamic core regset sections support Andreas Arnez
2013-06-07 14:43 ` Luis Machado
2013-06-07 16:40 ` Andreas Arnez
2013-06-07 15:03 ` [RFA/RFT PATCH 0/3] Add TDB regset support Pedro Alves
2013-06-07 15:59 ` Andreas Arnez [this message]
2013-06-07 16:44 ` Pedro Alves
2013-06-07 18:16 ` Andreas Arnez
2013-06-07 19:06 ` Pedro Alves
2013-06-10 16:59 ` Andreas Arnez
2013-06-11 10:48 ` Pedro Alves
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=87li6lud1m.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).