-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: lazily initialize global BuiltinLoader #46256
Conversation
Using simdutf during startup can fail when compilation units are linked in the wrong order by a static initialization order issue. nodejs#46235 would also solve this, but since that is a larger effort, this patch focuses on solving the immediate problem. Alternatively, simdutf should arguably be made usable during static initialization, but that is also not as straightforward as this patch. Fixes: nodejs#46235
Review requested:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me 👍
Working on a patch in simdutf. I flagged the issue in simdutf back in 2021... simdutf/simdutf#87 but it was theoretical at the time and I never revisited it. |
@addaleax If you prefer, I have the following patch in simdutf: simdutf/simdutf#209 It should solve the issue. |
Upgrading to simdutf 3.1.0 is an alternative fix. |
Using simdutf during startup can fail when compilation units are linked in the wrong order by a static initialization order issue.
#45942 would also solve this, but since that is a larger effort, this patch focuses on solving the immediate problem. Alternatively, simdutf should arguably be made usable during static initialization, but that is also not as straightforward as this patch.
Fixes: #46235