-
Notifications
You must be signed in to change notification settings - Fork 162
Updated XED from 2022 to 2025 #731
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
base: master
Are you sure you want to change the base?
Conversation
|
|
c1f9dbe to
d84ad70
Compare
| val = new llvm::BitCastInst(val, int_type, llvm::Twine::createNull(), block); | ||
|
|
||
| val_type = int_type; | ||
| } else if (val_type->isArrayTy()) { |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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?
d84ad70 to
14f1352
Compare
Update Intel XED to v2025 with Compatibility Fixes
Overview Section
Commit Details (5 commits)
Additional Sections
The document is ready for you to use as your PR description!