Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-14 Thread Vladimir Ivanov
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-13 Thread Yasumasa Suenaga
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-06 Thread Yasumasa Suenaga
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-02 Thread Jorn Vernee
On Thu, 3 Aug 2023 04:07:27 GMT, Yasumasa Suenaga wrote: > then shuffling would remain somewhare even if we could eliminate them from > NEP stub. Since things on the Java side are visible to the JIT, it should be able to avoid the extra data motion. > Thus this topic would be lower priority i

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-02 Thread Yasumasa Suenaga
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-02 Thread Jorn Vernee
On Wed, 2 Aug 2023 12:35:50 GMT, Yasumasa Suenaga wrote: > I guess you suggested that ArgumentShuffle in HotSpot moves into > DowncallLinker, right? No, ArgumentShuffle should stay inside HotSpot. We can not do all the shuffling on the Java side. We can only eliminate some of the register move

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-02 Thread Yasumasa Suenaga
On Wed, 2 Aug 2023 02:12:43 GMT, Jorn Vernee wrote: >> In FFM, native function would be called via `nep_invoker_blob`. If the >> function has two arguments, it would be following: >> >> >> Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 >> ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-01 Thread Jorn Vernee
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-08-01 Thread Jorn Vernee
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

Re: RFR: 8313406: nep_invoker_blob can be simplified more

2023-07-31 Thread Jorn Vernee
On Mon, 31 Jul 2023 12:22:00 GMT, Yasumasa Suenaga wrote: > In FFM, native function would be called via `nep_invoker_blob`. If the > function has two arguments, it would be following: > > > Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 > ---

RFR: 8313406: nep_invoker_blob can be simplified more

2023-07-31 Thread Yasumasa Suenaga
In FFM, native function would be called via `nep_invoker_blob`. If the function has two arguments, it would be following: Decoding RuntimeStub - nep_invoker_blob 0x7fcae394cd10 0x7fcae394cd80: pushq %rbp