linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Re: [kvm-unit-tests PATCH v3 0/5] Support cross compiling with clang
Date: Thu, 24 Oct 2024 10:38:51 +0200	[thread overview]
Message-ID: <20241024-cecbb361d7e3f21c7053408b@orel> (raw)
In-Reply-To: <20240911091406.134240-7-andrew.jones@linux.dev>

On Wed, Sep 11, 2024 at 11:14:07AM +0200, Andrew Jones wrote:
> 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.
> 
> v3:
>  - Add README patch for cross-compiling, clang, and cross-clang [Nick]
>  - Add comment to the commenting-out of mstrict-align [Nick]
>  - Add the reason to ignore warnings vs. fix code to commit message of
>    patch2
>  - Picked up Nick's tags
> 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 (5):
>   riscv: Drop mstrict-align
>   Makefile: Prepare for clang EFI builds
>   configure: Support cross compiling with clang
>   riscv: gitlab-ci: Add clang build tests
>   README: Add cross and clang recipes
> 
>  .gitlab-ci.yml | 43 +++++++++++++++++++++++++++++++++++++++++++
>  Makefile       |  2 ++
>  README.md      | 22 ++++++++++++++++++++++
>  configure      | 11 ++++++++---
>  riscv/Makefile |  4 +++-
>  5 files changed, 78 insertions(+), 4 deletions(-)
> 
> -- 
> 2.46.0
>

Merged

Thanks,
drew


      parent reply	other threads:[~2024-10-24  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  9:14 [kvm-unit-tests PATCH v3 0/5] Support cross compiling with clang Andrew Jones
2024-09-11  9:14 ` [kvm-unit-tests PATCH v3 1/5] riscv: Drop mstrict-align Andrew Jones
2024-09-11  9:14 ` [kvm-unit-tests PATCH v3 2/5] Makefile: Prepare for clang EFI builds Andrew Jones
2024-09-11  9:14 ` [kvm-unit-tests PATCH v3 3/5] configure: Support cross compiling with clang Andrew Jones
2024-09-11  9:14 ` [kvm-unit-tests PATCH v3 4/5] riscv: gitlab-ci: Add clang build tests Andrew Jones
2024-09-11  9:14 ` [kvm-unit-tests PATCH v3 5/5] README: Add cross and clang recipes Andrew Jones
2024-10-24  8:38 ` Andrew Jones [this message]

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=20241024-cecbb361d7e3f21c7053408b@orel \
    --to=andrew.jones@linux.dev \
    --cc=atishp@rivosinc.com \
    --cc=cade.richard@berkeley.edu \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jamestiotio@gmail.com \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lvivier@redhat.com \
    --cc=nrb@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@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).