Skip to content

With GraalVM native, some code will box null into 0 and introduce defects#490

Open
ygyg70 wants to merge 3 commits intoobjectify:masterfrom
ygyg70:master
Open

With GraalVM native, some code will box null into 0 and introduce defects#490
ygyg70 wants to merge 3 commits intoobjectify:masterfrom
ygyg70:master

Conversation

@ygyg70
Copy link
Copy Markdown

@ygyg70 ygyg70 commented Mar 30, 2023

Trying to support GraalVM native for my project, came across this issue:
oracle/graal#5672
The change in this pull request (going back to original code flow) seems to solve the issue.
Is there anything wrong with using the old code?

@stickfigure
Copy link
Copy Markdown
Contributor

I have very mixed feelings about this. It basically means slower performance for non-graal users (ie the vast majority of folks) because of a bug in graal. Hmmmm.

@ygyg70
Copy link
Copy Markdown
Author

ygyg70 commented Jul 24, 2024

Is the difference in performance measurable/significant?

@stickfigure
Copy link
Copy Markdown
Contributor

I have no idea. The JDK authors must have thought it was significant, otherwise they wouldn't have added MethodHandle in Java7.

@ygyg70
Copy link
Copy Markdown
Author

ygyg70 commented Jul 25, 2024

One typically choose a layer like Objectify when performance/scale is less important than code readability/maintenance.
Native build save save $$ - performance hit cost $$ - good chance that the first is a winner for most

@stickfigure
Copy link
Copy Markdown
Contributor

If I believed a significant portion of Objectify's userbase was using Graal, it would be compelling :-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants