Skip to content

SWDEV000000 - Migrate architecture specific intrinsics to SIMDe #170

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

Open
wants to merge 1 commit into
base: amd-staging
Choose a base branch
from

Conversation

AlexVlx
Copy link
Contributor

@AlexVlx AlexVlx commented Jun 1, 2025

Associated JIRA ticket number/Github issue number

None.

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update
  • Continuous Integration

What were the changes?

Existing unguarded uses of x86 intrinsics are replaced with equivalent calls to generic interfaces provided by the SIMDe library. SIMDe itself is added as a build dependency

Why are these changes needed?

Direct, unguarded use of architecture specific intrinsics / builtins creates challenges both when studying the library's behaviour on non-x86 targets, and when exploring different OSes.

Updated CHANGELOG?

  • Yes
  • No, Does not apply to this PR.

Added/Updated documentation?

  • Yes
  • No, Does not apply to this PR.

Additional Checks

  • I have added tests relevant to the introduced functionality, and the unit tests are passing locally.
  • Any dependent changes have been merged.

@AlexVlx AlexVlx requested a review from saleelk June 1, 2025 18:44
@AlexVlx AlexVlx added the enhancement New feature or request label Jun 1, 2025
@AlexVlx AlexVlx requested a review from dennyiriawan June 1, 2025 18:46
@AlexVlx AlexVlx requested a review from iassiour June 3, 2025 15:31
@@ -142,19 +142,20 @@ __hip_pch_wave64_size:
.long __hip_pch_wave64_size - __hip_pch_wave64
EOF

host_triple="$(uname -m)"
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this will return x86_64 (or aarch64 on arm) but don't we need the full triple i.e. x86_64-unknown-linux-gnu or aarch64-linux-gnu?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants