Skip to content

Conversation

@tarcieri
Copy link
Member

The only time we actually use powers-of-H is when we have intrinsics anyway, so we might as well make use of the intrinsics when computing them.

This factors the computation into the autodetect module with autodetection support and a fallback to a stub implementation for the soft backend which only initializes and access the last element (which is layout-compatible with the intrinsics implementation, if we ever decide to add the requisite support to the soft backend)

The only time we actually use powers-of-`H` is when we have intrinsics
anyway, so we might as well make use of the intrinsics when computing
them.

This factors the computation into the `autodetect` module with
autodetection support and a fallback to a stub implementation for the
`soft` backend which only initializes and access the last element (which
is layout-compatible with the intrinsics implementation, if we ever
decide to add the requisite support to the soft backend)
@tarcieri
Copy link
Member Author

tarcieri commented Jan 27, 2026

Note: this more or less fixes a regression during refactoring where the soft backend wound up being what computed these. We previously had support for this.

@tarcieri tarcieri merged commit cb02fa6 into master Jan 27, 2026
25 checks passed
@tarcieri tarcieri deleted the polyval/use-intrinsics-for-powers-of-h branch January 27, 2026 18:36
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