From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/4] Define enum out of the scope of struct
Date: Thu, 19 Nov 2015 13:01:00 -0000 [thread overview]
Message-ID: <1447938062-29624-4-git-send-email-yao.qi@linaro.org> (raw)
In-Reply-To: <1447938062-29624-1-git-send-email-yao.qi@linaro.org>
This patch moves the enum definition out of the scope of struct, and
fixes the following error.
gdb/gdbserver/linux-aarch64-low.c:681:18: error: 'OPERAND_REGISTER' was not declared in this scope
operand.type = OPERAND_REGISTER;
^
gdb/gdbserver:
2015-11-19 Yao Qi <yao.qi@linaro.org>
* linux-aarch64-low.c (enum aarch64_operand_type): New.
(struct aarch64_operand): Move enum out.
---
gdb/gdbserver/linux-aarch64-low.c | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/gdb/gdbserver/linux-aarch64-low.c b/gdb/gdbserver/linux-aarch64-low.c
index a145f80..7cd9b77 100644
--- a/gdb/gdbserver/linux-aarch64-low.c
+++ b/gdb/gdbserver/linux-aarch64-low.c
@@ -614,17 +614,20 @@ enum aarch64_condition_codes
LE = 0xd,
};
+enum aarch64_operand_type
+{
+ OPERAND_IMMEDIATE,
+ OPERAND_REGISTER,
+};
+
/* Representation of an operand. At this time, it only supports register
and immediate types. */
struct aarch64_operand
{
/* Type of the operand. */
- enum
- {
- OPERAND_IMMEDIATE,
- OPERAND_REGISTER,
- } type;
+ enum aarch64_operand_type type;
+
/* Value of the operand according to the type. */
union
{
--
1.9.1
next prev parent reply other threads:[~2015-11-19 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 13:01 [PATCH 0/4] [C++, AArch64] Fix warnings and errors Yao Qi
2015-11-19 13:01 ` [PATCH 2/4] Cast void * to user_fpsimd_state * Yao Qi
2015-11-19 13:01 ` [PATCH 4/4] Change argument opcode type from enum aarch64_opcodes to uint32_t Yao Qi
2015-11-19 13:01 ` [PATCH 1/4] Cast void * to struct user_pt_regs * Yao Qi
2015-11-19 13:01 ` Yao Qi [this message]
2015-11-19 13:43 ` [PATCH 0/4] [C++, AArch64] Fix warnings and errors Simon Marchi
2015-11-19 14:03 ` 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=1447938062-29624-4-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@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: 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