kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>
Subject: [kvm-unit-tests PATCH 0/4] Test compiling with Clang in the Travis-CI
Date: Tue, 22 Jun 2021 15:55:13 +0200	[thread overview]
Message-ID: <20210622135517.234801-1-thuth@redhat.com> (raw)

Travis-CI recently changed their policy so that builds on the non-x86
build machines are possible without consuming any credits again.
While we're already testing the non-x86 builds in the gitlab-CI with
the GCC cross-compilers, we could still benefit from the non-x86
builders in the Travis-CI by compiling the code with Clang there, too
(since there are AFAIK no Clang cross-compilers available in the usual
distros on x86).

Thomas Huth (4):
  configure: Add the possibility to specify additional cflags
  powerpc: Probe whether the compiler understands -mabi=no-altivec
  lib/s390x: Fix the epsw inline assembly
  Test compilation with Clang on aarch64, ppc64le and s390x in Travis-CI

 .travis.yml              | 44 ++++++++++++++++++++++++++++++++++++++++
 Makefile                 |  3 ---
 configure                | 10 +++++++--
 lib/s390x/asm/arch_def.h |  2 +-
 powerpc/Makefile.common  |  4 +++-
 5 files changed, 56 insertions(+), 7 deletions(-)
 create mode 100644 .travis.yml

-- 
2.27.0


             reply	other threads:[~2021-06-22 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 13:55 Thomas Huth [this message]
2021-06-22 13:55 ` [kvm-unit-tests PATCH 1/4] configure: Add the possibility to specify additional cflags Thomas Huth
2021-06-22 13:55 ` [kvm-unit-tests PATCH 2/4] powerpc: Probe whether the compiler understands -mabi=no-altivec Thomas Huth
2021-06-22 13:55 ` [kvm-unit-tests PATCH 3/4] lib/s390x: Fix the epsw inline assembly Thomas Huth
2021-06-22 14:12   ` Claudio Imbrenda
2021-06-22 16:40     ` Thomas Huth
2021-06-23  7:33   ` Janosch Frank
2021-06-22 13:55 ` [kvm-unit-tests PATCH 4/4] Test compilation with Clang on aarch64, ppc64le and s390x in Travis-CI Thomas Huth
2021-06-22 16:25 ` [kvm-unit-tests PATCH 0/4] Test compiling with Clang in the Travis-CI Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210622135517.234801-1-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).