From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [pushed] Move enum noside earlier in expression.h
Date: Mon, 21 Dec 2020 13:04:11 -0700 [thread overview]
Message-ID: <20201221200411.26204-1-tom@tromey.com> (raw)
For the expression rewrite series, I needed to move enum noside
earlier in expression.h. Because this is a pure move, and because it
seems harmless and uncontroversial to move an enum definition earlier
in a file, I'm pushing it in early, to reduce the size of that series.
Tested by rebuilding.
gdb/ChangeLog
2020-12-21 Tom Tromey <tom@tromey.com>
* expression.h (enum noside): Move earlier.
---
gdb/ChangeLog | 4 ++++
gdb/expression.h | 44 ++++++++++++++++++++++----------------------
2 files changed, 26 insertions(+), 22 deletions(-)
diff --git a/gdb/expression.h b/gdb/expression.h
index c07111c316f..f30c79309ae 100644
--- a/gdb/expression.h
+++ b/gdb/expression.h
@@ -67,6 +67,28 @@ enum exp_opcode : uint8_t
OP_UNUSED_LAST
};
+/* Values of NOSIDE argument to eval_subexp. */
+
+enum noside
+ {
+ EVAL_NORMAL,
+ EVAL_SKIP, /* Only effect is to increment pos.
+ Return type information where
+ possible. */
+ EVAL_AVOID_SIDE_EFFECTS /* Don't modify any variables or
+ call any functions. The value
+ returned will have the correct
+ type, and will have an
+ approximately correct lvalue
+ type (inaccuracy: anything that is
+ listed as being in a register in
+ the function in which it was
+ declared will be lval_register).
+ Ideally this would not even read
+ target memory, but currently it
+ does in many situations. */
+ };
+
union exp_element
{
enum exp_opcode opcode;
@@ -135,28 +157,6 @@ extern expression_up parse_exp_1 (const char **, CORE_ADDR pc,
/* From eval.c */
-/* Values of NOSIDE argument to eval_subexp. */
-
-enum noside
- {
- EVAL_NORMAL,
- EVAL_SKIP, /* Only effect is to increment pos.
- Return type information where
- possible. */
- EVAL_AVOID_SIDE_EFFECTS /* Don't modify any variables or
- call any functions. The value
- returned will have the correct
- type, and will have an
- approximately correct lvalue
- type (inaccuracy: anything that is
- listed as being in a register in
- the function in which it was
- declared will be lval_register).
- Ideally this would not even read
- target memory, but currently it
- does in many situations. */
- };
-
extern struct value *evaluate_subexp_standard
(struct type *, struct expression *, int *, enum noside);
--
2.17.2
next reply other threads:[~2020-12-21 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 20:04 Tom Tromey [this message]
2021-01-09 17:30 ` Tom Tromey
2021-01-09 17:35 ` Tom Tromey
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=20201221200411.26204-1-tom@tromey.com \
--to=tom@tromey.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