From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0)
Date: Fri, 23 Apr 2021 10:07:08 +0200 [thread overview]
Message-ID: <20210423100708.262eeaf0.cohuck@redhat.com> (raw)
In-Reply-To: <8abfb851-a5d2-8608-fe96-2eb3014adb96@redhat.com>
On Fri, 23 Apr 2021 09:57:08 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 23/04/2021 08.52, Christian Borntraeger wrote:
> [...]
> > We can of course discuss if we compile the BIOS for z10 instead of z900. TCG
> > in the mean time can handle up to z13 and z10 is now also 13 years old.
>
> I'd really like to see us supporting Clang in the s390-ccw bios, too, since
> it provides additional useful compiler warnings ... but switching the -mz900
> to -mz10 here also means that we could not boot VMs anymore that use a CPU
> that is older than the z10...
We could still boot a kernel/initrd directly, couldn't we?
>
> Is anybody still using such old CPUs? Should we maybe deprecate all CPUs
> that are older than the z10 in QEMU? Alternatively, we could try to detect
> Clang in the Makefile, and only use -mz10 in that case and continue to use
> -mz900 in the other case...?
So, the issue with clang is that it compiles to at least a z10, right?
Any other issues we know about?
next prev parent reply other threads:[~2021-04-23 8:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 4:18 s390-ccw: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] Philippe Mathieu-Daudé
2021-04-22 4:47 ` Thomas Huth
2021-04-22 6:04 ` Christian Borntraeger
2021-04-22 10:15 ` Daniel P. Berrangé
2021-04-22 10:30 ` Peter Maydell
2021-04-22 11:24 ` Philippe Mathieu-Daudé
2021-04-22 11:47 ` Thomas Huth
2021-04-22 12:41 ` Christian Borntraeger
2021-04-22 14:31 ` Philippe Mathieu-Daudé
2021-04-22 15:38 ` Thomas Huth
2021-04-22 15:43 ` Philippe Mathieu-Daudé
2021-04-22 15:52 ` Stefano Garzarella
2021-04-22 16:07 ` Thomas Huth
2021-04-22 16:54 ` Philippe Mathieu-Daudé
2021-04-23 6:40 ` Stefano Garzarella
2021-04-23 6:52 ` Christian Borntraeger
2021-04-23 7:57 ` Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0) Thomas Huth
2021-04-23 8:05 ` Compiling the s390-ccw bios with clang Christian Borntraeger
2021-04-23 8:07 ` Cornelia Huck [this message]
2021-04-23 8:22 ` Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0) Thomas Huth
2021-04-23 8:47 ` Daniel P. Berrangé
2021-04-23 8:52 ` Thomas Huth
2021-04-23 9:00 ` Daniel P. Berrangé
2021-04-22 11:48 ` s390-ccw: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=] Daniel P. Berrangé
2021-04-22 14:34 ` Philippe Mathieu-Daudé
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=20210423100708.262eeaf0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sgarzare@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 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.