From: Nicolai Stange <nicstange@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Josh Triplett <josh@joshtriplett.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Nicolai Stange <nicstange@gmail.com>
Subject: [PATCH v3 03/21] expression: examine constness of casts at evaluation only
Date: Mon, 01 Feb 2016 03:31:47 +0100 [thread overview]
Message-ID: <878u35jh4c.fsf@gmail.com> (raw)
In-Reply-To: <87lh75jh9l.fsf@gmail.com> (Nicolai Stange's message of "Mon, 01 Feb 2016 03:28:38 +0100")
Move the whole calculation of cast expressions' constness flags to the
evaluation phase such that expressions like
(int)__builtin_choose_expr(0, 0, 0)
can now be recognized as qualifying as integer constant expressions.
Signed-off-by: Nicolai Stange <nicstange@gmail.com>
---
evaluate.c | 27 ++++++++++++++++++---------
expression.c | 21 ---------------------
expression.h | 10 ++++++++++
validation/constexpr-cast.c | 25 +++++++++++++++++++++++++
4 files changed, 53 insertions(+), 30 deletions(-)
create mode 100644 validation/constexpr-cast.c
diff --git a/evaluate.c b/evaluate.c
index 7bce4fb..24a7f2f 100644
--- a/evaluate.c
+++ b/evaluate.c
@@ -323,7 +323,6 @@ static struct expression * cast_to(struct expression *old, struct symbol *type)
}
expr = alloc_expression(old->pos, EXPR_IMPLIED_CAST);
- expr->constexpr_flags = old->constexpr_flags;
expr->ctype = type;
expr->cast_type = type;
expr->cast_expression = old;
@@ -2745,14 +2744,24 @@ static struct symbol *evaluate_cast(struct expression *expr)
class1 = classify_type(ctype, &t1);
- /* cast to non-integer type -> not an integer constant expression */
- if (!is_int(class1))
- expr->constexpr_flags = CONSTEXPR_FLAG_NONE;
- /* if argument turns out to be not an integer constant expression *and*
- it was not a floating literal to start with -> too bad */
- else if (expr->constexpr_flags & CONSTEXPR_FLAG_INT_CONST_EXPR &&
- !(target->constexpr_flags & CONSTEXPR_FLAG_INT_CONST_EXPR))
- expr->constexpr_flags = CONSTEXPR_FLAG_NONE;
+ if (class1 & TYPE_NUM) {
+ expr->constexpr_flags = target->constexpr_flags &
+ ~CONSTEXPR_FLAG_DECAY_CONSTS_MASK;
+ /*
+ * Cast to float type -> not an integer constant
+ * expression [6.6(6)].
+ */
+ if (class1 & TYPE_FLOAT)
+ expr->constexpr_flags &=
+ ~CONSTEXPR_FLAG_INT_CONST_EXPR_CLEAR_MASK;
+ /*
+ * Casts of float literals to integer type results in
+ * a constant integer expression [6.6(6)].
+ */
+ else if (target->constexpr_flags & CONSTEXPR_FLAG_FP_CONST)
+ expr->constexpr_flags =
+ CONSTEXPR_FLAG_INT_CONST_EXPR_SET_MASK;
+ }
/*
* You can always throw a value away by casting to
diff --git a/expression.c b/expression.c
index f9adab6..759bee8 100644
--- a/expression.c
+++ b/expression.c
@@ -730,27 +730,6 @@ static struct token *cast_expression(struct token *token, struct expression **tr
if (!v)
return token;
cast->cast_expression = v;
-
- cast->constexpr_flags = v->constexpr_flags &
- ~CONSTEXPR_FLAG_DECAY_CONSTS_MASK;
- /*
- * Up to now, we missed the (int).0 case here
- * which should really get a
- * CONSTEXPR_FLAG_INT_CONST_EXPR marker. Also,
- * conversion to non-numeric types is not
- * properly reflected up to this point.
- * However, we do not know until evaluation.
- * For the moment, in order to preserve
- * semantics, speculatively set
- * CONSTEXPR_FLAG_INT_CONST_EXPR if
- * CONSTEXPR_FLAG_FP_CONST is
- * set. evaluate_cast() will unset
- * inappropriate flags again after examining
- * type information.
- */
- if (v->constexpr_flags & CONSTEXPR_FLAG_FP_CONST)
- cast->constexpr_flags |=
- CONSTEXPR_FLAG_INT_CONST_EXPR_SET_MASK;
return token;
}
}
diff --git a/expression.h b/expression.h
index 8a943a4..408382e 100644
--- a/expression.h
+++ b/expression.h
@@ -119,6 +119,16 @@ enum constexpr_flag {
(CONSTEXPR_FLAG_CHAR_CONST | CONSTEXPR_FLAG_INT_CONST_EXPR_SET_MASK)
/*
+ * not an integer constant expression => neither of integer,
+ * enumeration and character constant
+*/
+#define CONSTEXPR_FLAG_INT_CONST_EXPR_CLEAR_MASK \
+ (CONSTEXPR_FLAG_INT_CONST_EXPR | \
+ CONSTEXPR_FLAG_INT_CONST | \
+ CONSTEXPR_FLAG_ENUM_CONST | \
+ CONSTEXPR_FLAG_CHAR_CONST)
+
+/*
* Remove any "Constant" [6.4.4] flag, but retain the "constant
* expression" [6.6] flags.
*/
diff --git a/validation/constexpr-cast.c b/validation/constexpr-cast.c
new file mode 100644
index 0000000..2706961
--- /dev/null
+++ b/validation/constexpr-cast.c
@@ -0,0 +1,25 @@
+static int a[] = {
+ [(int)0] = 0, // OK
+ [(int)(int)0] = 0, // OK
+ [(int)0.] = 0, // OK
+ [(int)(int)0.] = 0, // OK
+ [(int)__builtin_choose_expr(0, 0, 0)] = 0, // OK
+ [(int)__builtin_choose_expr(0, 0, 0.)] = 0, // OK
+
+ [(int)(float)0] = 0, // KO
+ [(int)(float)0.] = 0, // KO
+
+ [(int)(void*)0] = 0, // KO
+ [(int)(void*)0.] = 0, // KO
+
+};
+/*
+ * check-name: Expression constness propagation in casts
+ *
+ * check-error-start
+constexpr-cast.c:9:11: error: bad integer constant expression
+constexpr-cast.c:10:11: error: bad integer constant expression
+constexpr-cast.c:12:11: error: bad integer constant expression
+constexpr-cast.c:13:11: error: bad integer constant expression
+ * check-error-end
+ */
--
2.7.0
next prev parent reply other threads:[~2016-02-01 2:31 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 2:28 [PATCH v3 00/21] improve constexpr handling Nicolai Stange
2016-02-01 2:29 ` [PATCH v3 01/21] expression: introduce additional expression constness tracking flags Nicolai Stange
2016-03-15 21:23 ` Luc Van Oostenryck
2016-02-01 2:30 ` [PATCH v3 02/21] expression: init constexpr_flags at expression allocation Nicolai Stange
2016-03-15 16:59 ` Luc Van Oostenryck
2016-02-01 2:31 ` Nicolai Stange [this message]
2016-03-15 20:43 ` [PATCH v3 03/21] expression: examine constness of casts at evaluation only Luc Van Oostenryck
2016-02-01 2:32 ` [PATCH v3 04/21] expression: examine constness of binops and alike " Nicolai Stange
2016-03-15 17:06 ` Luc Van Oostenryck
2016-02-01 2:33 ` [PATCH v3 05/21] expression: examine constness of preops " Nicolai Stange
2016-03-15 17:09 ` Luc Van Oostenryck
2016-02-01 2:34 ` [PATCH v3 06/21] expression: examine constness of conditionals " Nicolai Stange
2016-03-15 17:11 ` Luc Van Oostenryck
2016-02-01 2:35 ` [PATCH v3 07/21] expression: add support for tagging arithmetic constant expressions Nicolai Stange
2016-03-15 17:13 ` Luc Van Oostenryck
2016-02-01 2:36 ` [PATCH v3 08/21] expression, evaluate: add support for tagging address constants Nicolai Stange
2016-03-15 17:15 ` Luc Van Oostenryck
2016-02-01 2:37 ` [PATCH v3 09/21] evaluate: check static storage duration objects' intializers' constness Nicolai Stange
2016-03-15 17:28 ` Luc Van Oostenryck
2016-02-01 2:38 ` [PATCH v3 10/21] expression, evaluate: recognize static objects as address constants Nicolai Stange
2016-03-15 17:38 ` Luc Van Oostenryck
2016-02-01 2:39 ` [PATCH v3 11/21] evaluate: recognize address constants created through casts Nicolai Stange
2016-03-15 17:44 ` Luc Van Oostenryck
2016-02-01 2:39 ` [PATCH v3 12/21] evaluate: recognize address constants created through pointer arithmetic Nicolai Stange
2016-03-15 17:46 ` Luc Van Oostenryck
2016-02-01 2:40 ` [PATCH v3 13/21] evaluate: recognize members of static compound objects as address constants Nicolai Stange
2016-03-15 17:46 ` Luc Van Oostenryck
2016-02-01 2:41 ` [PATCH v3 14/21] evaluate: recognize string literals " Nicolai Stange
2016-03-15 17:46 ` Luc Van Oostenryck
2016-02-01 2:42 ` [PATCH v3 15/21] expression: recognize references to labels " Nicolai Stange
2016-03-15 17:47 ` Luc Van Oostenryck
2016-02-01 2:42 ` [PATCH v3 16/21] expression: examine constness of __builtin_offsetof at evaluation only Nicolai Stange
2016-03-15 19:52 ` Luc Van Oostenryck
2016-02-01 2:43 ` [PATCH v3 17/21] symbol: flag builtins constant_p, safe_p and warning as constexprs Nicolai Stange
2016-03-15 19:45 ` Luc Van Oostenryck
2016-02-01 2:44 ` [PATCH v3 18/21] evaluate: relax some constant expression rules for pointer expressions Nicolai Stange
2016-03-15 17:47 ` Luc Van Oostenryck
2016-03-15 19:44 ` Luc Van Oostenryck
2016-03-15 18:10 ` Luc Van Oostenryck
2016-02-01 2:45 ` [PATCH v3 19/21] expression, evaluate: support compound literals as address constants Nicolai Stange
2016-03-15 20:02 ` Luc Van Oostenryck
2016-02-01 2:46 ` [PATCH v3 20/21] symbol: do not inherit storage modifiers from base types at examination Nicolai Stange
2016-03-15 20:31 ` Luc Van Oostenryck
2016-02-01 2:47 ` [PATCH v3 21/21] evaluation: treat comparsions between types as integer constexpr Nicolai Stange
2016-03-15 20:34 ` Luc Van Oostenryck
2016-02-19 8:22 ` [PATCH v3 00/21] improve constexpr handling Nicolai Stange
2016-02-24 9:45 ` Christopher Li
2016-02-24 12:13 ` Nicolai Stange
2016-03-15 16:54 ` Luc Van Oostenryck
2016-03-15 22:36 ` Luc Van Oostenryck
2016-10-28 20:28 ` Luc Van Oostenryck
2016-11-23 3:12 ` Christopher Li
2016-11-23 4:05 ` Luc Van Oostenryck
2016-11-23 6:49 ` Christopher Li
2016-11-23 8:39 ` Nicolai Stange
2016-11-23 15:36 ` Christopher Li
2016-11-23 16:43 ` Nicolai Stange
2016-11-23 17:38 ` Christopher Li
2016-11-23 18:23 ` Christopher Li
2016-11-23 18:33 ` Nicolai Stange
2016-11-24 1:18 ` Christopher Li
2016-11-24 9:45 ` Nicolai Stange
2016-11-24 11:24 ` Christopher Li
2016-11-24 17:22 ` Luc Van Oostenryck
2016-12-06 6:00 ` Christopher Li
2016-12-06 16:54 ` Luc Van Oostenryck
2017-03-29 14:42 ` Luc Van Oostenryck
2017-03-31 5:06 ` Christopher Li
2017-03-31 8:55 ` Luc Van Oostenryck
2017-03-31 10:40 ` Christopher Li
2017-03-31 19:47 ` Luc Van Oostenryck
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=878u35jh4c.fsf@gmail.com \
--to=nicstange@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).