Skip to content
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

Add support for ARMv8-m Extensions #69

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

avi-jois
Copy link

ARMv8-m supports 8 different optional extensions. Instead of supporting a curated set permutations, create new constraint setting for each extension.

This is modeled after #63

ARMv8-m supports 8 different optional extensions. Instead of supporting
a curated set permutations, create new constraint setting for each
extension.
@google-cla
Copy link

google-cla bot commented May 18, 2023

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.

Copy link
Contributor

@aiuto aiuto left a comment

Choose a reason for hiding this comment

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

The biggest question is if the extensions apply to only arm8-m, or if they are names used throughout the arm 64 big architecture.
I would prefer a solution where we can reuse the names.


Defines a `constraint_setting`, <name>_setting and two `constraint_values`,
no_<name> and <name>.
The setting defaults to `no_<name>` for maximum compatibility, since
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't believe this is needed.
Just create the singleton pair of constraint_setting and constraint_value.
If someone really, really needs to test for a constraint being unset, they can do a select on the constraint value vs. conditions_default.

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.

2 participants