Skip to content

testing/development strategy for support beyond Intel #13

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

Closed
BurntSushi opened this issue Sep 17, 2017 · 2 comments
Closed

testing/development strategy for support beyond Intel #13

BurntSushi opened this issue Sep 17, 2017 · 2 comments
Labels

Comments

@BurntSushi
Copy link
Member

Other than the vendor independent interface, this repo only contains vendor intrinsics for Intel. We will of course want to add intrinsics from other vendors on different platforms (like ARM), but I'm not quite sure how to go about it. For the most part, I'd expect it to be a relatively similar process as the Intel intrinsics, but I've held off from doing it because I don't have any systems in place for testing or development of intrinsics on other platforms.

For testing, I assume this means getting CI setup so that it runs on the various platforms that we're targeting.

For development, I'm less sure. I'd like to be able to test, say, ARM intrinsics from the comfort of my local machine. Does this mean running a VM? Or is there something better?

@mattico
Copy link

mattico commented Sep 19, 2017

compiler-builtins uses Docker to run tests inside of QEMU on ARM/MIPS/PPC. There are occasionally some spurious failures which seem like they may be QEMU bugs, but otherwise it works fine.

That specific solution uses the host rustc inside the docker container so the host must be linux. If you installed rust inside the container it would be pretty straightforward to run anywhere you can install docker.

@BurntSushi
Copy link
Member Author

@mattico Awesome! That does indeed sound promising.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants