From: Andrew Jones <andrew.jones@linux.dev>
To: kvm-riscv@lists.infradead.org
Subject: [kvm-unit-tests PATCH v2 0/4] Support cross compiling with clang
Date: Wed, 4 Sep 2024 12:50:21 +0200 [thread overview]
Message-ID: <20240904105020.1179006-6-andrew.jones@linux.dev> (raw)
Modify configure to allow --cc=clang and a cross-prefix to be specified
together (as well as --cflags). This allows compiling with clang, but
using cross binutils for everything else, including the linker. So far
tested on riscv 32- and 64-bit and aarch64 (with some hacks to the code
to get it to compile - which is why there's no gitlab-ci patch for aarch64
in this series). I suspect it should work for other architectures too.
v2:
- fix building with clang and --config-efi by suppressing a warning
- added riscv clang efi build to CI
- picked up Thomas's tags
Andrew Jones (4):
riscv: Drop mstrict-align
Makefile: Prepare for clang EFI builds
configure: Support cross compiling with clang
riscv: gitlab-ci: Add clang build tests
.gitlab-ci.yml | 43 +++++++++++++++++++++++++++++++++++++++++++
Makefile | 2 ++
configure | 11 ++++++++---
riscv/Makefile | 2 +-
4 files changed, 54 insertions(+), 4 deletions(-)
--
2.46.0
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <andrew.jones@linux.dev>
To: kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
kvmarm@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org
Cc: pbonzini@redhat.com, thuth@redhat.com, lvivier@redhat.com,
frankja@linux.ibm.com, imbrenda@linux.ibm.com, nrb@linux.ibm.com,
atishp@rivosinc.com, cade.richard@berkeley.edu,
jamestiotio@gmail.com
Subject: [kvm-unit-tests PATCH v2 0/4] Support cross compiling with clang
Date: Wed, 4 Sep 2024 12:50:21 +0200 [thread overview]
Message-ID: <20240904105020.1179006-6-andrew.jones@linux.dev> (raw)
Modify configure to allow --cc=clang and a cross-prefix to be specified
together (as well as --cflags). This allows compiling with clang, but
using cross binutils for everything else, including the linker. So far
tested on riscv 32- and 64-bit and aarch64 (with some hacks to the code
to get it to compile - which is why there's no gitlab-ci patch for aarch64
in this series). I suspect it should work for other architectures too.
v2:
- fix building with clang and --config-efi by suppressing a warning
- added riscv clang efi build to CI
- picked up Thomas's tags
Andrew Jones (4):
riscv: Drop mstrict-align
Makefile: Prepare for clang EFI builds
configure: Support cross compiling with clang
riscv: gitlab-ci: Add clang build tests
.gitlab-ci.yml | 43 +++++++++++++++++++++++++++++++++++++++++++
Makefile | 2 ++
configure | 11 ++++++++---
riscv/Makefile | 2 +-
4 files changed, 54 insertions(+), 4 deletions(-)
--
2.46.0
next reply other threads:[~2024-09-04 10:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:50 Andrew Jones [this message]
2024-09-04 10:50 ` [kvm-unit-tests PATCH v2 0/4] Support cross compiling with clang Andrew Jones
2024-09-04 10:50 ` [kvm-unit-tests PATCH v2 1/4] riscv: Drop mstrict-align Andrew Jones
2024-09-04 10:50 ` Andrew Jones
2024-09-11 0:08 ` Nicholas Piggin
2024-09-11 0:08 ` Nicholas Piggin
2024-09-11 8:19 ` Andrew Jones
2024-09-11 8:19 ` Andrew Jones
2024-09-04 10:50 ` [kvm-unit-tests PATCH v2 2/4] Makefile: Prepare for clang EFI builds Andrew Jones
2024-09-04 10:50 ` Andrew Jones
2024-09-04 10:57 ` Thomas Huth
2024-09-04 10:57 ` Thomas Huth
2024-09-11 0:21 ` Nicholas Piggin
2024-09-11 0:21 ` Nicholas Piggin
2024-09-11 8:21 ` Andrew Jones
2024-09-11 8:21 ` Andrew Jones
2024-09-04 10:50 ` [kvm-unit-tests PATCH v2 3/4] configure: Support cross compiling with clang Andrew Jones
2024-09-04 10:50 ` Andrew Jones
2024-09-11 0:24 ` Nicholas Piggin
2024-09-11 0:24 ` Nicholas Piggin
2024-09-11 8:24 ` Andrew Jones
2024-09-11 8:24 ` Andrew Jones
2024-09-04 10:50 ` [kvm-unit-tests PATCH v2 4/4] riscv: gitlab-ci: Add clang build tests Andrew Jones
2024-09-04 10:50 ` Andrew Jones
2024-09-11 0:26 ` Nicholas Piggin
2024-09-11 0:26 ` Nicholas Piggin
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=20240904105020.1179006-6-andrew.jones@linux.dev \
--to=andrew.jones@linux.dev \
--cc=kvm-riscv@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.