RFR: 8351994: Enable Extended EVEX to REX2/REX demotion when src and dst are the same [v24]
Srinivas Vamsi Parasa
sparasa at openjdk.org
Thu May 15 17:52:13 UTC 2025
> Intel APX NDD instructions are encoded using EVEX encoding. The goal of this PR is to enable optimized instruction encoding for Intel APX NDD instructions when the non-destructive destination is same as the first source.
>
> For example:
>
> `eaddl r18, r18, r25` can be encoded as `addl r18, r25` using APX REX2 encoding
> `eaddl r2, r2, r7` can be encoded as `addl r2, r7` using non-APX legacy encoding
Srinivas Vamsi Parasa has updated the pull request incrementally with one additional commit since the last revision:
Add /*MAP 4*/ comment next to VEX_OPCODE_0F_3C
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/24431/files
- new: https://git.openjdk.org/jdk/pull/24431/files/21333a5c..ca7ba027
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=24431&range=23
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=24431&range=22-23
Stats: 159 lines in 1 file changed: 0 ins; 0 del; 159 mod
Patch: https://git.openjdk.org/jdk/pull/24431.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/24431/head:pull/24431
PR: https://git.openjdk.org/jdk/pull/24431
More information about the hotspot-compiler-dev
mailing list