cpu_features
cpu_features copied to clipboard
fix RISC-V _Z extension parsing, they don't have a defined order
I noticed that the current RISC-V ISA string parsing code assumes there is an order for the extensions. While this is true for single letter extensions, the others, e.g. with _Z prefix, don't have a defined order.
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
How do I sign the CLA without using an google account?