From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [PATCH 7/8] sql: clean-up affinity from SQL source code Date: Tue, 5 Feb 2019 18:08:16 +0300 [thread overview] Message-ID: <a8756505-2272-346b-51d1-1e9741af6c70@tarantool.org> (raw) In-Reply-To: <239B8EBA-F577-4C9A-BDD9-D76DE10FEB76@tarantool.org> Thanks for the fixes! > diff --git a/src/box/sql/vdbe.c b/src/box/sql/vdbe.c > index 358b69754..dae05e80f 100644 > --- a/src/box/sql/vdbe.c > +++ b/src/box/sql/vdbe.c > @@ -2153,13 +2153,13 @@ case OP_Ge: { /* same as TK_GE, jump, in1, in3 */ > } else { > /* > * Neither operand is NULL. Do a comparison. 'Neither operand is NULL' - this is 'else' branch of "(flags1 | flags3)&MEM_Null", so I guess it is obvious. > - * 15 is 1111 in a binary form. > - * Since all existing types can be fitted in 4 bits > - * (field_type_MAX == 10), it is enough to 'and' > - * p5 with this constant. Node that all other flags > - * that can be stored in p5 are >= 16. > + * Since all existing types can be fitted in 4 > + * bits (field_type_MAX == 9), it is enough to > + * 'and' p5 with field mask. Note that values of > + * other flags that can be stored in p5 of these > + * opcodes are >= FIELD_TYPE_MASK. They can not be == FIELD_TYPE_MASK. Please, again, do not try to write here any constants, including bit counts. A definition named MASK is already enough to make it clear, that p5 'and' mask give a type. > */ > - enum field_type type = pOp->p5 & 15; > + enum field_type type = pOp->p5 & FIELD_TYPE_MASK; > Please, apply the diff below. I made enum field_type_mask an anonymous enum, as we usually do with independent constants. Also, I used FIELD_TYPE_MASK instead of 15 in static assertion, and removed the comment from vdbe.c about what a mask is. diff --git a/src/box/field_def.h b/src/box/field_def.h index 3b8eb0ccf..3eda0e38f 100644 --- a/src/box/field_def.h +++ b/src/box/field_def.h @@ -87,21 +87,22 @@ affinity_type_str(enum affinity_type type); /** \endcond public */ +enum { + /** + * This mask allows to store in VdbeOp.p5 operand of + * OP_Eq, OP_Lt etc opcodes field type alonside with + * flags. + */ + FIELD_TYPE_MASK = 15 +}; + /** * For detailed explanation see context of OP_Eq, OP_Lt etc * opcodes in vdbe.c. */ -static_assert(field_type_MAX <= 15, "values of enum field_type "\ +static_assert(field_type_MAX <= FIELD_TYPE_MASK, "values of enum field_type "\ "should fit into 4 bits of VdbeOp.p5"); -/** - * This mask allows to store in p5 operand of OP_Eq, OP_Lt etc - * opcodes field type alonside with other flags. - */ -enum field_type_mask { - FIELD_TYPE_MASK = 15 -}; - extern const char *field_type_strs[]; extern const char *on_conflict_action_strs[]; diff --git a/src/box/sql/vdbe.c b/src/box/sql/vdbe.c index dae05e80f..a66ab4992 100644 --- a/src/box/sql/vdbe.c +++ b/src/box/sql/vdbe.c @@ -2151,14 +2151,6 @@ case OP_Ge: { /* same as TK_GE, jump, in1, in3 */ break; } } else { - /* - * Neither operand is NULL. Do a comparison. - * Since all existing types can be fitted in 4 - * bits (field_type_MAX == 9), it is enough to - * 'and' p5 with field mask. Note that values of - * other flags that can be stored in p5 of these - * opcodes are >= FIELD_TYPE_MASK. - */ enum field_type type = pOp->p5 & FIELD_TYPE_MASK; if (sql_type_is_numeric(type)) { if ((flags1 | flags3)&MEM_Str) {
next prev parent reply other threads:[~2019-02-05 15:08 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-28 9:34 [tarantool-patches] [PATCH 0/8] Eliminate affinity from " Nikita Pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 1/8] sql: remove SQLITE_ENABLE_UPDATE_DELETE_LIMIT define Nikita Pettik 2018-12-29 17:42 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-16 14:25 ` n.pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 2/8] sql: use field type instead of affinity for type_def Nikita Pettik 2018-12-29 17:42 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-16 14:26 ` n.pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 3/8] sql: remove numeric affinity Nikita Pettik 2018-12-29 9:01 ` [tarantool-patches] " Konstantin Osipov 2018-12-29 17:42 ` Vladislav Shpilevoy 2019-01-09 8:26 ` Konstantin Osipov 2019-01-16 14:26 ` n.pettik 2019-01-22 15:41 ` Vladislav Shpilevoy 2019-01-28 16:39 ` n.pettik 2019-01-30 13:04 ` Vladislav Shpilevoy 2019-02-01 16:39 ` n.pettik 2019-01-09 8:20 ` Konstantin Osipov 2018-12-28 9:34 ` [tarantool-patches] [PATCH 4/8] sql: replace affinity with field type for func Nikita Pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 5/8] sql: replace field type with affinity for VDBE runtime Nikita Pettik 2018-12-29 17:42 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-16 14:26 ` n.pettik 2019-01-22 15:41 ` Vladislav Shpilevoy 2019-01-28 16:39 ` n.pettik 2019-01-30 13:04 ` Vladislav Shpilevoy 2019-02-01 16:39 ` n.pettik 2019-02-05 15:08 ` Vladislav Shpilevoy 2019-02-05 17:46 ` n.pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 6/8] sql: replace affinity with field type in struct Expr Nikita Pettik 2018-12-29 17:42 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-16 14:26 ` n.pettik 2019-01-22 15:41 ` Vladislav Shpilevoy 2019-01-28 16:39 ` n.pettik 2019-01-30 13:04 ` Vladislav Shpilevoy 2019-02-01 16:39 ` n.pettik 2019-02-05 15:08 ` Vladislav Shpilevoy 2019-02-05 17:46 ` n.pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 7/8] sql: clean-up affinity from SQL source code Nikita Pettik 2018-12-29 17:42 ` [tarantool-patches] " Vladislav Shpilevoy 2019-01-16 14:26 ` n.pettik 2019-01-22 15:41 ` Vladislav Shpilevoy 2019-01-28 16:40 ` n.pettik 2019-01-30 13:04 ` Vladislav Shpilevoy 2019-02-01 16:39 ` n.pettik 2019-02-05 15:08 ` Vladislav Shpilevoy [this message] 2019-02-05 17:46 ` n.pettik 2018-12-28 9:34 ` [tarantool-patches] [PATCH 8/8] Remove affinity from field definition Nikita Pettik 2019-02-05 19:41 ` [tarantool-patches] Re: [PATCH 0/8] Eliminate affinity from source code Vladislav Shpilevoy 2019-02-08 13:37 ` Kirill Yukhin
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=a8756505-2272-346b-51d1-1e9741af6c70@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=korablev@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH 7/8] sql: clean-up affinity from SQL source code' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox