pgsql: jit: Stop emitting some unnecessary instructions - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: jit: Stop emitting some unnecessary instructions
Date
Msg-id E1tBrOe-001uIb-Fe@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
jit: Stop emitting some unnecessary instructions

In EEOP_BOOL_AND_STEP* and EEOP_BOOL_OR_STEP*, we emitted pointlesss
store instructions to store to resnull/resvalue values that were just
loaded from the same fields in the previous instructions. They will
surely get optimized away by LLVM if any optimizations are enabled,
but it's better to not emit them in the first place. In
EEOP_BOOL_NOT_STEP, similar story with resnull.

In EEOP_NULLIF, when it returns NULL, there was also a redundant store
to resvalue just after storing a 0 to it. The value of resvalue
doesn't matter when resnull is set, so in fact even storing the 0 is
unnecessary, but I kept that because we tend to do that for general
tidiness.

Author: Xing Guo <higuoxing@gmail.com>
Reviewed-by: Andreas Karlsson <andreas@proxel.se>
Discussion:
https://www.postgresql.org/message-id/CACpMh%2BC%3Dg13WdvzLRSponsVWGgxwDSMzQWM4Gz0heOyaA0-N6g@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/cfd7f36c83cdcf6322c7ea0d1d9ef62bc2b00375

Modified Files
--------------
src/backend/jit/llvm/llvmjit_expr.c | 24 +++++++-----------------
1 file changed, 7 insertions(+), 17 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Add an assertion in get_object_address()
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Proper object locking for GRANT/REVOKE