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

[Feature Request] Expose arguments for Mojo build target options. #3794

Open
1 task done
owenhilyard opened this issue Nov 21, 2024 · 0 comments
Open
1 task done

[Feature Request] Expose arguments for Mojo build target options. #3794

owenhilyard opened this issue Nov 21, 2024 · 0 comments
Labels
enhancement New feature or request mojo-repo Tag all issues with this label

Comments

@owenhilyard
Copy link

Review Mojo's priorities

What is your request?

Expose the arguments for the following build flags:

  • --target-triple
  • --target-cpu
  • --target-features
  • --march
  • --mcpu
  • --mtune

For example, include flags to dump all target triples, all features supported for the selected architecture, and the known CPUs.

What is your motivation for this change?

While we can tell people to go look at the clang docs, we don't know what targets Mojo's copy of LLVM has enabled. For example, if amd64-unknown-linux-musl or the mingw windows targets exist, or whether Mojo supports the amx-transpose feature. This is also helpful for stdlib developers because ideally every single CPU feature should be exposed in sys.info. It also helps people with very new hardware determine if the current stable Mojo release supports their hardware.

Any other details?

If there's a way to make the output structured (json or otherwise), we might be able to automatically generate parts of sys.info instead of hand-writing them.

@owenhilyard owenhilyard added enhancement New feature or request mojo-repo Tag all issues with this label labels Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request mojo-repo Tag all issues with this label
Projects
None yet
Development

No branches or pull requests

1 participant