FYI: Upcoming changes in GraalVM

[Foivos Zakkak]

Hi all,

You might find the following github issues (planned for future GraalVM
releases) of interest:

1. Minimize Build-Time Initialization of the JDK feature native-image [1]
2. Restrict the Expressivity of Patterns in resource-config.json
feature native-image [2]
3. Inspecting and Testing the Reachability Metadata used in
Native-Image Builds feature native-image [3]
4. Introduce Runtime Checks for typeReachable and Change the Name feature [4]
5. Ability to Express all JVM Types in Reachability Metadata feature
native-image [5]

[1] https://github.com/oracle/graal/issues/7488
[2] https://github.com/oracle/graal/issues/7487
[3] https://github.com/oracle/graal/issues/7482
[4] https://github.com/oracle/graal/issues/7480
[5] https://github.com/oracle/graal/issues/7476

Regards,
--
Foivos Zakkak
Senior Software Engineer, R&D Product Middleware
Red Hat
7B4069D929BAAE91C0B3220A0846BFD103F04EA1

[Max Rydahl Andersen]

Any of these that you see would be good to utilise or some that would be problematic for us?

/max

> --
> You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CA%2BXL9jFLsskK13cn2T0qhEL4K4EmZzSscZqev9qjmskp5V%3DQxg%40mail.gmail.com.

[Foivos Zakkak]

1. might turn out to be problematic, as it probably means we will now need to do any necessary substitutions on the Quarkus side, while till now they were handled on the GraalVM side.

2. shouldn't affect Quarkus, as long as users don't heavily rely on the exclude pattern which will no longer be supported. Quarkus already uses glob patterns in the include pattern anyway.

3. will hopefully help us better understand why something is being added to the metadata. I don't think there is anything we can do on the Quarkus side for this. Although Galder is looking into some kind of integration of the native-image agent with Quarkus.

4. AFAIU doesn't affect Quarkus.

5. Will probably require some adaptation in our json configuration generator. It will also allow us to introduce new annotations for registering lambda-proxy and Java-proxy types.

On Wed, Oct 25, 2023 at 10:06 PM Max Rydahl Andersen <mand...@redhat.com> wrote:

Any of these that you see would be good to utilise or some that would be problematic for us?

/max

On 4 Oct 2023, at 13:12, Foivos Zakkak wrote:

> Hi all,
>
> You might find the following github issues (planned for future GraalVM
> releases) of interest:
>
> 1. Minimize Build-Time Initialization of the JDK feature native-image [1]
> 2. Restrict the Expressivity of Patterns in resource-config.json
> feature native-image [2]
> 3. Inspecting and Testing the Reachability Metadata used in
> Native-Image Builds feature native-image [3]
> 4. Introduce Runtime Checks for typeReachable and Change the Name feature [4]
> 5. Ability to Express all JVM Types in Reachability Metadata feature
> native-image  [5]
>
> [1] https://github.com/oracle/graal/issues/7488
> [2] https://github.com/oracle/graal/issues/7487

> [3] https://github.com/oracle/graal/issueThis s/7482

> [4] https://github.com/oracle/graal/issues/7480
> [5] https://github.com/oracle/graal/issues/7476
>
> Regards,
> --
> Foivos Zakkak
> Senior Software Engineer, R&D Product Middleware
> Red Hat
> 7B4069D929BAAE91C0B3220A0846BFD103F04EA1
>
> --
> You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CA%2BXL9jFLsskK13cn2T0qhEL4K4EmZzSscZqev9qjmskp5V%3DQxg%40mail.gmail.com.