Bug 472405 - RFE: give Note about instructions on current hardware that are not supported by VEX
Summary: RFE: give Note about instructions on current hardware that are not supported ...
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (other bugs)
Version First Reported In: unspecified
Platform: PCLinuxOS Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-19 16:29 UTC by John Reiser
Modified: 2023-07-19 16:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John Reiser 2023-07-19 16:29:11 UTC 
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Request For Enhancement (RFE): At run-time initialization, then memcheck should give a Note about cpu instructions on the current executing hardware, that VEX does not support.  Such as: "Note: this version of valgrind does not support these instructions of this CPU: aes bmi1 bmi2".  Such a Note would enhance usability by giving early warning of Unrecognized Instruction.  Getting a friendly warning at the beginning, instead of "vex amd64->IR: unhandled instruction bytes: 0x..." and several lines of spew, is much more pleasant.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION