From: Alan Hayward <alan.hayward@arm.com>
To: gdb-patches@sourceware.org
Cc: nd@arm.com, Alan Hayward <alan.hayward@arm.com>
Subject: [PUSHED/OBV] Fix up HAS_SVE_STATE macro
Date: Fri, 22 Jun 2018 11:08:00 -0000 [thread overview]
Message-ID: <20180622110800.487-1-alan.hayward@arm.com> (raw)
Prevents build break on aarch64 Suse.
2018-06-22 Alan Hayward <alan.hayward@arm.com>
gdb/
* nat/aarch64-sve-linux-ptrace.h (HAS_SVE_STATE): Use &.
---
gdb/ChangeLog | 4 ++++
gdb/nat/aarch64-sve-linux-ptrace.h | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 1221a54d03..de9127f70f 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2018-06-22 Alan Hayward <alan.hayward@arm.com>
+
+ * nat/aarch64-sve-linux-ptrace.h (HAS_SVE_STATE): Use &.
+
2018-06-21 Pedro Alves <palves@redhat.com>
* ada-lang.h (ada_get_task_number): Take a thread_info pointer
diff --git a/gdb/nat/aarch64-sve-linux-ptrace.h b/gdb/nat/aarch64-sve-linux-ptrace.h
index 5a7186b7aa..029e753ffe 100644
--- a/gdb/nat/aarch64-sve-linux-ptrace.h
+++ b/gdb/nat/aarch64-sve-linux-ptrace.h
@@ -32,7 +32,7 @@
/* Indicates whether a SVE ptrace header is followed by SVE registers or a
fpsimd structure. */
-#define HAS_SVE_STATE(header) ((header).flags && SVE_PT_REGS_SVE)
+#define HAS_SVE_STATE(header) ((header).flags & SVE_PT_REGS_SVE)
/* Read VQ for the given tid using ptrace. If SVE is not supported then zero
is returned (on a system that supports SVE, then VQ cannot be zero). */
--
2.15.2 (Apple Git-101.1)
reply other threads:[~2018-06-22 11:08 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=20180622110800.487-1-alan.hayward@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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).