Skip to content

Misc WARP fixes for 5.1 stable #7142

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

Closed
wants to merge 6 commits into from
Closed

Conversation

emesare
Copy link
Member

@emesare emesare commented Jul 21, 2025

These were issues caught during testing, all of which should be included in the stable.

emesare added 6 commits July 20, 2025 20:38
… regions

This removes more barriers for those working with firmware to use WARP, previously if you had defined any sections (such as a vector interrupt table) then backed segments would
end up being marked non-relocatable. This, combined with the use of ELF intermediate object files created inconsistent GUID's, using the segments backing the real functions fixes this.
…on masking

We emit jumps at the end of some blocks that the architecture is not aware of, they are not actually apart of the functions instructions
rather they are used in our analysis... somehow, I have not figured out what they are supposed to be used for but regardless, they should be
ignored by WARP.

This was just a case where the filtering was including jumps in non start instructions, where we actually wanted the opposite.
…ion guids generated

Just a sanity check so we can alert the user, they can just reanalyze their functions and the guid will be constructed
… matched functions

One day I will get the QT incantations correct
@emesare emesare self-assigned this Jul 21, 2025
@emesare emesare added this to the Helion milestone Jul 21, 2025
@emesare
Copy link
Member Author

emesare commented Jul 21, 2025

Merged with df0d8aa

@emesare emesare closed this Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant