public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: uweigand@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 6682d9595ed8d9b9bba5470bfd7fd1ccd378f19a Date: Wed, 06 Nov 2013 20:45:00 -0000 [thread overview] Message-ID: <20131106204515.17615.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 6682d9595ed8d9b9bba5470bfd7fd1ccd378f19a (commit) from 1d946cb356d22867128b40b9560857f930b2b0b0 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6682d9595ed8d9b9bba5470bfd7fd1ccd378f19a commit 6682d9595ed8d9b9bba5470bfd7fd1ccd378f19a Author: Andreas Arnez <arnez at linux dot vnet dot ibm dot com> Date: Tue Nov 5 18:43:50 2013 +0100 S390: Fix TDB regset recognition When checking for the presence of the TDB regset, the current code interprets ENODATA from PTRACE_GETREGSET as an indication that the TDB regset *could* occur on this system, but the inferior stopped outside a transaction. However, the Linux kernel actually reports ENODATA even on systems without the transactional execution facility. Thus the logic is now changed to check the TE field in the HWCAP as well. This version also checks the existence of the TDB regset -- just to be on the safe side when running on TE-enabled hardware with a kernel that does not offer the TDB regset for some reason. gdb/ * s390-linux-nat.c (s390_read_description): Consider the TE field in the HWCAP for determining 'have_regset_tdb'. gdbserver/ * linux-s390-low.c (HWCAP_S390_TE): New define. (s390_arch_setup): Consider the TE field in the HWCAP for determining 'have_regset_tdb'. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 5 ++++ gdb/gdbserver/ChangeLog | 6 +++++ gdb/gdbserver/linux-s390-low.c | 48 +++++++++++++++++++++++++--------------- gdb/s390-linux-nat.c | 5 ++- 4 files changed, 44 insertions(+), 20 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2013-11-06 20:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131106204515.17615.qmail@sourceware.org \ --to=uweigand@sourceware.org \ --cc=src-cvs@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: linkBe 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).