> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> ### Purpose of Indify
>
> - **Transformation Tool**: `Indify` transforms existing class files to
>
On Wed, 24 Jul 2024 07:58:31 GMT, ExE Boss wrote:
>> This transformation is called only after the `classModel` is transformed:
>> - at line 472 and 380 when the `transformToBytes()` method is called is
>> after effectively transforming the `classModel` inside the `Logic` class.
>
> There isn’t
On Sat, 22 Jun 2024 15:55:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> ### Purpose of Indify
>>
>> - **Transf
On Tue, 25 Jun 2024 13:54:07 GMT, Oussama Louati wrote:
>> And what is the purpose of parsing a model from bytes and transforming it
>> back to bytes without a change?
>
> This transformation is called only after the `classModel` is transformed:
> - at line 472 and 380 when the `transformToByt
On Tue, 25 Jun 2024 13:49:31 GMT, Adam Sotona wrote:
>> Transforming the classModel back to the bytes array in order to write the
>> transformed classfile
>
> And what is the purpose of parsing a model from bytes and transforming it
> back to bytes without a change?
This transformation is call
On Tue, 25 Jun 2024 13:45:17 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/indify/Indify.java line 386:
>>
>>> 384:
>>> 385: byte[] transformToBytes(ClassModel classModel) {
>>> 386: return of().transform(classModel, ClassTransform.ACCEPT_ALL);
>>
>> What is the purpose o
On Tue, 25 Jun 2024 13:17:13 GMT, Adam Sotona wrote:
>> Oussama Louati has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> remove: removed unnecessary logging
>
> test/jdk/java/lang/invoke/indify/Indify.java line 386:
>
>> 384:
>> 385:
On Sat, 22 Jun 2024 15:55:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> ### Purpose of Indify
>>
>> - **Transf
On Sat, 22 Jun 2024 15:55:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> ### Purpose of Indify
>>
>> - **Transf
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Sat, 22 Jun 2024 09:39:46 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
On Mon, 17 Jun 2024 08:33:17 GMT, Adam Sotona wrote:
>> We need a boolean value to determine if we should proceed after replacing
>> the appropriate "pop" instruction with an "invokedynamic" instruction.
>> However, instead of using just a boolean field, we use a stack. The reason
>> for this
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Wed, 19 Jun 2024 12:04:27 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
On Mon, 17 Jun 2024 08:12:08 GMT, Adam Sotona wrote:
>> Oussama Louati has updated the pull request incrementally with 19 additional
>> commits since the last revision:
>>
>> - fix: fixed whitespaces
>> - fix: fixed whitespaces
>> - chore: used Class::descriptorString
>> - remove: added rem
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Fri, 24 May 2024 17:12:34 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/indify/Indify.java line 503:
>>
>>> 501:
>>> 502: Iterator instructionIterator
>>> =getInstructions(m).iterator();
>>> 503: final Stack shouldProceedAfterIndyAdded = new
>>> St
On Tue, 28 May 2024 11:03:18 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
On Fri, 24 May 2024 17:12:24 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/indify/Indify.java line 578:
>>
>>> 576: classTransform =
>>> ClassTransform.transformingMethodBodies(filter, codeTransform);
>>> 577: classModel = of().parse(
>>
On Wed, 22 May 2024 22:38:16 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/CallStaticInitOrder.java line 54:
>>
>>> 52:
>>> 53: static int Init1Tick;
>>> 54: public static class Init1 {
>>
>> Is there a reason to change all the classes and methods to public?
>
> the test thro
On Fri, 24 May 2024 17:57:28 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/indify/Indify.java line 660:
>>
>>> 658: *
>>> 659: * @return true if any marks were changed, false otherwise.
>>> 660: */
>>
>> This method does incremental analysis of the constant
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Wed, 22 May 2024 22:37:35 GMT, Oussama Louati wrote:
>> test/jdk/java/lang/invoke/CallSiteTest.java line 96:
>>
>>> 94: }
>>> 95:
>>> 96: public static class MyCCS extends ConstantCallSite {
>>
>> Any reason for this change?
>
> Otherwise, it throws an java.lang.IllegalAccessError:
On Wed, 22 May 2024 08:57:23 GMT, Adam Sotona wrote:
>> Oussama Louati has updated the pull request incrementally with 19 additional
>> commits since the last revision:
>>
>> - fix: fixed whitespaces
>> - fix: fixed whitespaces
>> - chore: used Class::descriptorString
>> - remove: added rem
On Tue, 21 May 2024 11:37:26 GMT, Adam Sotona wrote:
> Indify invocation on Microbenchmarks as a part of the JDK build (after
> application of the above patch) still fails with:
>
> ```
> Failure on
> /Applications/XcodeJIB.app/dev/github/jdk/build/macosx-aarch64/support/test/micro/classes
> E
On Fri, 24 May 2024 17:57:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
On Fri, 24 May 2024 17:57:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Mon, 20 May 2024 20:56:18 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Mon, 20 May 2024 15:34:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Mon, 20 May 2024 15:34:28 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Mon, 20 May 2024 13:20:17 GMT, Oussama Louati wrote:
>> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
>> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
>> MethodType, and CallSite constants.
>> It currently uses ad-hoc code to process
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process class files and intends to migrate
> to ASM; but since we ha
On Thu, 18 Apr 2024 13:53:34 GMT, Oussama Louati wrote:
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process cla
On Thu, 18 Apr 2024 13:53:34 GMT, Oussama Louati wrote:
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process cla
On Thu, 18 Apr 2024 14:15:12 GMT, Chen Liang wrote:
> This is going to be a difficult task because of the sheer size of indify
> tool; to migrate you really need in-depth understanding of both indify and CF
> API. Good luck!
Thank you
> test/jdk/java/lang/invoke/indify/Indify.java line 1247:
On Thu, 18 Apr 2024 13:53:34 GMT, Oussama Louati wrote:
> An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
> private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
> MethodType, and CallSite constants.
> It currently uses ad-hoc code to process cla
An indify tool in j.l.i tests (also in vmTestBase) convert some source-code
private static methods with MT_ MH_, and INDY_ prefixes into MethodHandle,
MethodType, and CallSite constants.
It currently uses ad-hoc code to process class files and intends to migrate to
ASM; but since we have the Cla
47 matches
Mail list logo
