Skip to content

Conversation

@stevenfontanella
Copy link
Member

@stevenfontanella stevenfontanella commented Jan 13, 2026

Followup to #8169. Fixes the fuzzer which currently generates code with --enable-relaxed-atomics which isn't supported in v8. To test, I ran the fuzzer successfully for ~20 minutes locally.

Part of #8165.

In the future, we'll also add fuzzing support for relaxed atomics by generating acqrel instructions.


CLOSED_WORLD_FLAG = '--closed-world'

DISALLOWED_FEATURES_IN_V8 = ['shared-everything', 'strings', 'stack-switching', 'relaxed-atomics']
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other two files here set --disable-fp16, should that be here too?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. @brendandahl do you know the status of fp16 support in v8, or who to ask?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

V8 supports the whole current proposal and nothing has changed recently that I know of. However, the future of the proposal is still up in the air, so I'm not sure we should be fuzzing yet. Maybe @dtig has thoughts?

@stevenfontanella stevenfontanella changed the title Disable relaxed atomics for v8 code in the fuzzer Disable relaxed atomics for v8 tests in the fuzzer Jan 13, 2026
@stevenfontanella stevenfontanella marked this pull request as ready for review January 13, 2026 18:23
Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm % last comment

We can decide on fp16 in a separate PR, to keep this one narrow.

@stevenfontanella stevenfontanella merged commit a8ccf99 into main Jan 14, 2026
33 of 34 checks passed
@stevenfontanella stevenfontanella deleted the fuzzer-fix branch January 14, 2026 01:44
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.

4 participants