Skip to content

perf: reduce register spillage by applying twiddle symmetry#112

Closed
smu160 wants to merge 1 commit intomainfrom
leverage-twiddle-symmetry
Closed

perf: reduce register spillage by applying twiddle symmetry#112
smu160 wants to merge 1 commit intomainfrom
leverage-twiddle-symmetry

Conversation

@smu160
Copy link
Copy Markdown
Member

@smu160 smu160 commented Apr 11, 2026

No description provided.

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.80%. Comparing base (3cebc5d) to head (fdb57be).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
- Coverage   98.87%   98.80%   -0.08%     
==========================================
  Files          10       10              
  Lines        2227     2094     -133     
==========================================
- Hits         2202     2069     -133     
  Misses         25       25              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Shnatsel
Copy link
Copy Markdown
Collaborator

I think there are really two changes here: using narrower vectors (which makes sense for radix-2^2) and using the symmetry.

We should revisit this older codelet version when we add AVX-512, where we can use 512-bit vectors natively for math and also not worry about register pressure due to 2x wider registers and 2x the number of registers.

@Shnatsel
Copy link
Copy Markdown
Collaborator

I'm seeing better results from #113 which supersedes this. So I'll likely clean up #113 and merge that instead of this. We'll see.

@smu160
Copy link
Copy Markdown
Member Author

smu160 commented Apr 17, 2026

Closing in favor of #113

@smu160 smu160 closed this Apr 17, 2026
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