public inbox for [email protected]
help / color / mirror / Atom feedFrom: Henson Choi <[email protected]>
To: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: Row pattern recognition
Date: Sat, 2 May 2026 13:30:25 +0900
Message-ID: <CAAAe_zCe1gj_UkapC4e_GVZmud+dxru8YONpKRhtY6c2RmXcZg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAAAe_zA3vXEPkC7=fapx0VCE5F2uSgRjKjur67Yfd+JxtWPCuQ@mail.gmail.com>
<[email protected]>
<CAAAe_zBdwAUDNs_WFdLkFF=ewhkDkv-AqizVEVzhsfremGFb4w@mail.gmail.com>
<[email protected]>
Hi Tatsuo,
I know in v47 JIT compilation supports PREV/NEXT. What about
> FIRST/LAST and compound forms?
>
Yes, those are JIT-compiled too in v47.
The JIT side only deals with two opcodes -- EEOP_RPR_NAV_SET
and EEOP_RPR_NAV_RESTORE.
FIRST/LAST and the compound forms differ only in how
ExecEvalRPRNavSet() computes target_pos for the slot swap;
the opcode interface and the call into ExecEvalRPRNavSet /
ExecEvalRPRNavRestore are unchanged.
So 0018's JIT support carries over to FIRST/LAST and
compounds without any JIT-side change.
Regards,
Henson
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Row pattern recognition
In-Reply-To: <CAAAe_zCe1gj_UkapC4e_GVZmud+dxru8YONpKRhtY6c2RmXcZg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox