qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v2] configure: Only build the s390-ccw bios if the compiler supports -march=z900
Date: Mon, 14 Jan 2019 18:51:35 +0100	[thread overview]
Message-ID: <f054089a-25e7-3b01-ac6d-41f43ccac207@redhat.com> (raw)
In-Reply-To: <20190114162003.274d5921.cohuck@redhat.com>

On 2019-01-14 16:20, Cornelia Huck wrote:
> On Mon, 14 Jan 2019 13:52:26 +0100
> Thomas Huth <thuth@redhat.com> wrote:
> 
>> We want to build our s390-ccw bios with -march=z900 so that it also
>> works with the oldest s390x CPU that we support with TCG. However,
>> Clang on s390x does not support -march=z900 anymore, so we can not
>> use this compiler to build the s390-ccw bios. Thus add a proper test
>> to the configure script to see whether the compiler is usable.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>  v2: Use compile_prog as suggested by Peter
>>
>>  configure | 6 +++++-
>>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> With this, the fpu/softfloat patch, and Marcel's rdma patches, I can
> compile with clang on my Fedora 29 s390x system. Yeah!
> 
> Should this patch go through the s390 tree, or take some other path?

There is no dedicated maintainer for the configure script, so please
take it through the s390 tree.

 Thanks,
  Thomas

  reply	other threads:[~2019-01-14 17:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 12:52 [Qemu-devel] [PATCH v2] configure: Only build the s390-ccw bios if the compiler supports -march=z900 Thomas Huth
2019-01-14 15:20 ` Cornelia Huck
2019-01-14 17:51   ` Thomas Huth [this message]
2019-01-14 18:13 ` Cornelia Huck
2019-01-15 11:54 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger

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=f054089a-25e7-3b01-ac6d-41f43ccac207@redhat.com \
    --to=thuth@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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 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).