qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Christian Borntraeger" <borntraeger@de.ibm.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Janosch Frank <frankja@linux.ibm.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: s390-ccw: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
Date: Thu, 22 Apr 2021 17:38:26 +0200	[thread overview]
Message-ID: <c95369e4-ffc9-d01d-45c1-4daad0ead6a5@redhat.com> (raw)
In-Reply-To: <e4116908-7172-fd9c-1837-82c489b61620@redhat.com>

On 22/04/2021 16.31, Philippe Mathieu-Daudé wrote:
> On 4/22/21 2:41 PM, Christian Borntraeger wrote:
>> On 22.04.21 13:47, Thomas Huth wrote:
>>> On 22/04/2021 13.24, Philippe Mathieu-Daudé wrote:
>>>> On 4/22/21 12:30 PM, Peter Maydell wrote:
>>>>> On Thu, 22 Apr 2021 at 11:18, Daniel P. Berrangé
>>>>> <berrange@redhat.com> wrote:
> 
>>>> This silents the warning however:
>>>>
>>>> -- >8 --
>>>> diff --git a/pc-bios/s390-ccw/libc.h b/pc-bios/s390-ccw/libc.h
>>>> index bcdc45732d..2dea399904 100644
>>>> --- a/pc-bios/s390-ccw/libc.h
>>>> +++ b/pc-bios/s390-ccw/libc.h
>>>> @@ -19,6 +19,8 @@ typedef unsigned short     uint16_t;
>>>>    typedef unsigned int       uint32_t;
>>>>    typedef unsigned long long uint64_t;
>>>>
>>>> +#pragma GCC diagnostic push
>>>> +#pragma GCC diagnostic ignored "-Wstringop-overflow"
>>>>    static inline void *memset(void *s, int c, size_t n)
>>>>    {
>>>>        size_t i;
>>>> @@ -30,6 +32,7 @@ static inline void *memset(void *s, int c, size_t n)
>>>>
>>>>        return s;
>>>>    }
>>>> +#pragma GCC diagnostic pop
>>>
>>> Honestly, that compiler "bug" sounds like it could trigger at any
>>> other spot in the bios code, too, since we are doing lots of direct
>>> accesses to low memory there. I think it's likely best if we shut it
>>> off with -Wno-stringop-overflow in the pc-bios/s390-ccw/Makefile ...
>>> could you please try to add it there?
>>
> 
> We are good with:
> 
> -- >8 --
> diff --git a/pc-bios/s390-ccw/Makefile b/pc-bios/s390-ccw/Makefile
> index 29fd9019b8..dcec09b6f9 100644
> --- a/pc-bios/s390-ccw/Makefile
> +++ b/pc-bios/s390-ccw/Makefile
> @@ -8,6 +8,9 @@ CFLAGS = -O2 -g
>   quiet-command = $(if $(V),$1,$(if $(2),@printf "  %-7s %s\n" $2 $3 &&
> $1, @$1))
>   cc-option = $(if $(shell $(CC) $1 -S -o /dev/null -xc /dev/null >
> /dev/null \
>                2>&1 && echo OK), $1, $2)
> +cc-c-option = $(if $(shell $(CC) $1 $2 -c -o /dev/null -xc /dev/null \
> +                >/dev/null 2>&1 && echo OK), $2, $3)
> 
>   VPATH_SUFFIXES = %.c %.h %.S %.m %.mak %.sh %.rc Kconfig% %.json.in
>   set-vpath = $(if $1,$(foreach PATTERN,$(VPATH_SUFFIXES),$(eval vpath
> $(PATTERN) $1)))
> @@ -30,6 +33,7 @@ OBJECTS = start.o main.o bootmap.o jump2ipl.o sclp.o
> menu.o \
>            virtio.o virtio-scsi.o virtio-blkdev.o libc.o cio.o dasd-ipl.o
> 
>   QEMU_CFLAGS := -Wall $(filter -W%, $(QEMU_CFLAGS))
> +QEMU_CFLAGS += $(call cc-c-option, $(QEMU_CFLAGS), -Wno-stringop-overflow)
>   QEMU_CFLAGS += -ffreestanding -fno-delete-null-pointer-checks

I think you don't need the "cc-c-option" magic here. Just add the 
-Wno-stringop-overflow. All supported versions of GCC and Clang simply 
silently ignore unknown -Wno-something options (try e.g. "gcc 
-Wno-yadayadayada" on the command line).

  Thomas



  reply	other threads:[~2021-04-22 15:39 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 [this message]
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                             ` Compiling the s390-ccw bios with clang (was: Re: s390-ccw: warning: writing 1 byte into a region of size 0) Cornelia Huck
2021-04-23  8:22                               ` 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=c95369e4-ffc9-d01d-45c1-4daad0ead6a5@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.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 \
    /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).