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

Include support for either a base micro-architecture as default, or compile to suit an endpoints specific micro-architecture #26

Open
atheurer opened this issue Dec 19, 2020 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@atheurer
Copy link
Contributor

Having the default avoids having builds which don't work in some endpoints (controller built for newer CPU than the endpoint).

Supporting a micro-architecture means that

  1. we need to accurately identify what the micro-architecture of the endpoint is. We probably need to rely on gcc for this, as that is what's deciding what optimizations to use.
  2. We need to include the micro-architecture in the md5sum for the container image tag
  3. We might need to support running workshop on the endpoint, especially if the userenv is different (and have a different compiler version) and if the cpu architecture is completely different (or we have to cross-compile). This could also vastly speed up container builds if we have to build for many endpoints.
@atheurer atheurer added enhancement New feature or request help wanted Extra attention is needed labels Dec 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant