qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, pbonzini@redhat.com, thuth@redhat.com,
	alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH] tests/docker: Update the Fedora image to Fedora 30
Date: Fri, 24 May 2019 15:37:41 +0200	[thread overview]
Message-ID: <6d97fa23-6ff0-998e-b698-388f2313d535@redhat.com> (raw)
In-Reply-To: <155870450828.24.7185600599110160688@549697c9ad12>

Hi Patchew,

On 5/24/19 3:28 PM, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20190504060336.21060-1-philmd@redhat.com/
> 
> 
> 
> Hi,
> 
> This series failed build test on s390x host. Please find the details below.

"20 days later", not yet a movie title.

>     inlined from ‘fill_psinfo’ at /var/tmp/patchew-tester-tmp-3g8u4fv2/src/linux-user/elfload.c:3208:12,
>     inlined from ‘fill_note_info’ at /var/tmp/patchew-tester-tmp-3g8u4fv2/src/linux-user/elfload.c:3390:5,
>     inlined from ‘elf_core_dump’ at /var/tmp/patchew-tester-tmp-3g8u4fv2/src/linux-user/elfload.c:3539:9:
> /usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Werror=stringop-truncation]
>   106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
>       |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors

This has been fixed by the following commit, merged earlier today:

commit d7eb2b928a855a2e8038e8e75f7edf1a12226bd3
Author: Alistair Francis <Alistair.Francis@wdc.com>
Date:   Tue Apr 30 23:29:01 2019 +0000

    linux-user/elfload: Fix GCC 9 build warnings

    Fix this warning when building with GCC9 on Fedora 30:
    In function ‘strncpy’,
        inlined from ‘fill_psinfo’ at
/home/alistair/qemu/linux-user/elfload.c:3208:12,
        inlined from ‘fill_note_info’ at
/home/alistair/qemu/linux-user/elfload.c:3390:5,
        inlined from ‘elf_core_dump’ at
/home/alistair/qemu/linux-user/elfload.c:3539:9:
    /usr/include/bits/string_fortified.h:106:10: error:
‘__builtin_strncpy’ specified bound 16 equals destination size
[-Werror=stringop-truncation]
      106 |   return __builtin___strncpy_chk (__dest, __src, __len,
__bos (__dest));
          |
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com

Done!


  reply	other threads:[~2019-05-24 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04  6:03 [Qemu-devel] [PATCH] tests/docker: Update the Fedora image to Fedora 30 Philippe Mathieu-Daudé
2019-05-04  6:03 ` Philippe Mathieu-Daudé
2019-05-24  7:44 ` Philippe Mathieu-Daudé
2019-05-24 12:26   ` Stefano Garzarella
2019-05-24 13:28 ` no-reply
2019-05-24 13:37   ` Philippe Mathieu-Daudé [this message]
2019-05-29  9:54 ` Alex Bennée

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=6d97fa23-6ff0-998e-b698-388f2313d535@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).