Skip to content

Conversation

@wizardengineer
Copy link
Collaborator

@wizardengineer wizardengineer commented Nov 25, 2025

Update Intel XED to v2025 with Compatibility Fixes

Overview Section

  • Clear title: "Update Intel XED to v2025 with Compatibility Fixes"
  • Closes Test error with XED v2023.04.16 #651 prominently displayed
  • The Problem: Explains the test_dependencies failure with the exact error message
  • The Solution: Bullet list of all fixes
  • Test Results: All 1443 tests pass

Commit Details (5 commits)

    • XED version bump
    • LZCNT/TZCNT enablement (links to XED commit)
    • MULX/RORX iform name changes
    • SQRTSS/SQRTSD extra operand + FADD suppressed ST0

Additional Sections

  • Files changed summary table
  • Breaking changes reference for future maintainers
  • Testing commands

The document is ready for you to use as your PR description!

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@wizardengineer wizardengineer marked this pull request as ready for review November 26, 2025 05:42
val = new llvm::BitCastInst(val, int_type, llvm::Twine::createNull(), block);

val_type = int_type;
} else if (val_type->isArrayTy()) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not feeling the best about this, but the alternatives aren't great. We can

  • Abuse ExtractValue with a chain of SHIFT/OR operations to build the integer, but that's extremely bloated
  • Convert from Array -> Vector -> Integer, I think this is just silly
  • Rewrite LoadRegValue with a special case to load certain array sizes as their native integer compliments

I think ultimately, the 3rd option is something worth exploring, but is out of scope for this current PR and I want to trigger a larger discussion for this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, we can look into the 3rd option. I think it might be more viable?

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.

Test error with XED v2023.04.16

4 participants