Skip to content

Conversation

@tomcur
Copy link
Member

@tomcur tomcur commented Jan 25, 2026

This fixes the remainder of clippy::cast_possible_wrap warnings on x86.

Very similarly to #186, explicitly reinterpret these bit patterns as signed (i.e., this again is explicitly a no-op at the instruction-level, but effectively checks bit width remains the same). Also uses cast_signed for splatting on x86, which just takes the bit pattern as a signed numeric type for broadcasting.

@tomcur tomcur force-pushed the push-oozwvvuptrsq branch from cf9ea87 to d9f5880 Compare January 25, 2026 16:25
@LaurenzV
Copy link
Collaborator

Is this specific lint not caught in CI? 🤔 Otherwise CI should have failed, no?

@tomcur
Copy link
Member Author

tomcur commented Jan 25, 2026

It would be caught when we update to lint set v8, it's not included in v6.1 (which main is on).

@tomcur tomcur force-pushed the push-oozwvvuptrsq branch from d9f5880 to 78ec6a4 Compare January 25, 2026 16:37
Like linebender#186, explicitly
reinterpret the bit patterns as signed (i.e., this is explicitly a no-op
at the instruction-level). Also uses `cast_signed` for splatting on x86,
which just broadcasts the bit pattern.

Fixes the remainder of `clippy::cast_possible_wrap` warnings on x86.
@tomcur tomcur force-pushed the push-oozwvvuptrsq branch from 78ec6a4 to 1ebaf09 Compare January 25, 2026 16:40
@tomcur tomcur added this pull request to the merge queue Jan 25, 2026
Merged via the queue into linebender:main with commit 6f70c9d Jan 25, 2026
18 checks passed
@tomcur tomcur deleted the push-oozwvvuptrsq branch January 25, 2026 16:49
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.

3 participants