1
0
mirror of https://github.com/google/cpu_features.git synced 2025-04-28 07:23:37 +02:00
marquitos0119 981fbe3914
S390X Support (#274)
* support for s390x

* added z15 T01, T02 model checking

* removed z15 checking

* removed empty strings

* added s390x unit tests

* added reference url for hwcaps

* moved documentation to S390XFeatures struct, updated copyright date, removed unused include statement

* changed num_processors to int

* removed newlines from test inputs

* scripts: Add bootlin s390x support

* cmake(ci): Add s390x support

* ci: Add s390x workflow

Co-authored-by: Marcos <marcos.araque.fiallos@ibm.com>
Co-authored-by: Corentin Le Molgat <corentinl@google.com>
2022-11-02 09:38:13 +01:00
..
2022-11-02 09:38:13 +01:00

Makefile/Docker testing

To test the build on various distro, we are using docker containers and a Makefile for orchestration.

pros:

  • You are independent of third party CI runner config (e.g. github action virtual-environnments).
  • You can run it locally on your linux system.
  • Most CI provide runners with docker and Makefile installed.

cons:

  • Only GNU/Linux distro supported.

Usage

To get the help simply type:

make

note: you can also use from top directory

make --directory=cmake/ci

Example

For example to test mips32 inside an container:

make mips32_test

Docker layers

Dockerfile is splitted in several stages.

docker

Makefile/Vagrant testing

To test build for FreeBSD we are using Vagrant and VirtualBox box.

This is similar to the docker stuff but use vagrant as docker cli and VirtuaBox to replace the docker engine daemon.