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

Update the dependencies list in README & what platforms do we want to support #4777

Open
vlstill opened this issue Jul 3, 2024 · 1 comment
Labels
core Topics concerning the core segments of the compiler (frontend, midend, parser) documentation Topics related to compiler documentation. infrastructure Topics related to code style and build and test infrastructure.

Comments

@vlstill
Copy link
Contributor

vlstill commented Jul 3, 2024

This could be done in step with #4347, but we should decide what platforms/versions we should actually support. This list is now very conservative and the testing is even more (testing that Ubuntu 18.04 works!). I'm not sure if we have any rules on how to drop support for platforms (e.g. for Ubuntu 18). Any changes should be made in sync with what we actually test.

  • clang 6 is never tested as far as I see, we test Clang 10 in the sanitizers builds
  • GCC 9.1 is also never tested, we test 9.4 in both Ubuntu 20 and Ubuntu 18 builds -- this is probably less of a problem than Clang 6, but there could still be some bugfixes
  • BWGC is no longer required (to be installed beforehand)
  • protobuf is no longer required (to be installed beforehand)
  • we should mention macOS for M* CPUs

Somewhat related is that I think we should add Ubuntu 24.04 to tests and both 22.04 and 24.04 to the list of supported targets.

@vlstill vlstill added core Topics concerning the core segments of the compiler (frontend, midend, parser) infrastructure Topics related to code style and build and test infrastructure. documentation Topics related to compiler documentation. labels Jul 3, 2024
@fruffy
Copy link
Collaborator

fruffy commented Jul 3, 2024

#3986 is related.

Maybe there is a way to improve the Github action workflow to reuse components that have been build. This way we can instantiate a more complex test matrix while saving resources.

Not sure how much is too much, the breadth of testing can already be overwhelming but is required for a compiler that is used in many different environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Topics concerning the core segments of the compiler (frontend, midend, parser) documentation Topics related to compiler documentation. infrastructure Topics related to code style and build and test infrastructure.
Projects
None yet
Development

No branches or pull requests

2 participants