Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH] sql: remove redundant goto from VDBE prologue
Date: Mon, 18 Jun 2018 21:57:29 +0300	[thread overview]
Message-ID: <b10cc995-3cbb-8ee2-3287-3833aeceab81@tarantool.org> (raw)
In-Reply-To: <27FB91D4-8386-4AE9-8A1E-B68FE60EAB6B@tarantool.org>

Thanks for the fixes!

On 18/06/2018 20:45, n.pettik wrote:
> 
>> On 18 Jun 2018, at 14:06, Vladislav Shpilevoy <v.shpilevoy@tarantool.org> wrote:
>>
>>
>>>>
>>>> 3. As far as I see, P2 in OP_Init is 1 already when we are here. It is
>>>> not? See allocVdbe function. P2 == 1 by default, and here it can be changed to
>>>> goto to ttrans.
>>> In fact, it is changed by sqlite3VdbeJumpHere(v, 0);
>>> Thus, we have to again set its value to 1, in case of omitting jump.
>>
>> It is done in the same function few lines above. How about
>> to do not do this jump + not jump? I have slightly refactored the
>> code to do not this jump. Please, see the separate commit on
>> the branch.
>>
>> (I did not check the tests).
> 
> Thx for refactoring, but it wouldn’t work this way:
> We must firstly make lable to jump (sqlite3VdbeJumpHere(v, 0);),
> then test on emitting OP_TTransaction and const exprs (or both). If we need to
> add such opcodes, then we should jump back. Otherwise, dismiss initial jump.

We do not need to change P2 until it is really needed. That is what I
mean.

Please, consider this diff:

diff --git a/src/box/sql/build.c b/src/box/sql/build.c
index a7b9d20b3..3a361cfad 100644
--- a/src/box/sql/build.c
+++ b/src/box/sql/build.c
@@ -74,7 +74,7 @@ sql_finish_coding(struct Parse *parse_context)
  	 */
  	assert(!parse_context->isMultiWrite ||
  	       sqlite3VdbeAssertMayAbort(v, parse_context->mayAbort));
-	sqlite3VdbeJumpHere(v, 0);
+	int last_instruction = v->nOp;
  	if (parse_context->initiateTTrans)
  		sqlite3VdbeAddOp0(v, OP_TTransaction);
  	if (parse_context->pConstExpr != NULL) {
@@ -101,10 +101,10 @@ sql_finish_coding(struct Parse *parse_context)
  	 *    ...
  	 * vdbe_end: OP_Goto 0 1 ...
  	 */
-	if (parse_context->initiateTTrans || parse_context->pConstExpr != NULL)
+	if (parse_context->initiateTTrans || parse_context->pConstExpr != NULL) {
+		sqlite3VdbeChangeP2(v, 0, last_instruction);
  		sqlite3VdbeGoto(v, 1);
-	else
-		sqlite3VdbeChangeP2(v, 0, 1);
+	}
  	/* Get the VDBE program ready for execution. */
  	if (parse_context->nErr == 0 && !db->mallocFailed) {
  		assert(parse_context->iCacheLevel == 0);

The tests pass ok.

  reply	other threads:[~2018-06-18 18:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 18:26 [tarantool-patches] " Nikita Pettik
2018-06-17 20:08 ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-18 10:46   ` n.pettik
2018-06-18 11:06     ` Vladislav Shpilevoy
2018-06-18 17:45       ` n.pettik
2018-06-18 18:57         ` Vladislav Shpilevoy [this message]
2018-06-18 20:55           ` n.pettik
2018-06-18 21:03             ` Vladislav Shpilevoy
2018-06-19  8:21               ` 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=b10cc995-3cbb-8ee2-3287-3833aeceab81@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH] sql: remove redundant goto from VDBE prologue' \
    /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