qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Beraldo Leal" <bleal@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Yonggang Luo" <luoyonggang@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Bin Meng" <bin.meng@windriver.com>
Subject: Re: [PATCH] gitlab: remove duplication between msys jobs
Date: Fri, 28 Jul 2023 10:35:35 +0200	[thread overview]
Message-ID: <a56c06a0-a6b4-cee6-be97-3586a836f4d3@redhat.com> (raw)
In-Reply-To: <ZMJJS5lUtPKpld0q@redhat.com>

On 27/07/2023 12.39, Daniel P. Berrangé wrote:
> On Wed, Jul 26, 2023 at 08:21:33PM +0200, Thomas Huth wrote:
>> On 26/07/2023 18.19, Daniel P. Berrangé wrote:
...
>> Anyway, before we unify the compiler package name suffix between the two
>> jobs, I really would like to see whether the mingw Clang builds QEMU faster
>> in the 64-bit job ... but so far I failed to convince meson to accept the
>> Clang from the mingw package ... does anybody know how to use Clang with
>> MSYS2 properly?
> 
> AFAIK it shouldn't be anything worse than
> 
>    CC=clang ./configure ....
> 
> if that doesn't work then its a bug IMHO

No, it's not that easy ... As Marc-André explained to me, MSYS2 maintains a 
completely separate environment for Clang, i.e. you have to select this 
different environment with $env:MSYSTEM = 'CLANG64' and then install the 
packages that have the "mingw-w64-clang-x86_64-" prefix.

After lots of trial and error, I was able to get a test build here:

  https://gitlab.com/thuth/qemu/-/jobs/4758605925

I had to disable Spice and use --disable-werror in that build to make it 
succeed, but at least it shows that Clang seems to be a little bit faster - 
the job finished in 58 minutes. So if we can get the warnings fixed, this 
might be a solution for the timeouts here...

  Thomas



  reply	other threads:[~2023-07-28  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 16:19 [PATCH] gitlab: remove duplication between msys jobs Daniel P. Berrangé
2023-07-26 18:21 ` Thomas Huth
2023-07-26 18:42   ` Marc-André Lureau
2023-07-27 10:39   ` Daniel P. Berrangé
2023-07-28  8:35     ` Thomas Huth [this message]
2023-07-28  8:58       ` Daniel P. Berrangé
2023-07-28  9:32         ` Marc-André Lureau
2023-07-28  9:50           ` Thomas Huth
2023-07-28 10:01             ` Thomas Huth
2023-07-28 10:39               ` Daniel P. Berrangé

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=a56c06a0-a6b4-cee6-be97-3586a836f4d3@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=bin.meng@windriver.com \
    --cc=bleal@redhat.com \
    --cc=luoyonggang@gmail.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wainersm@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).