linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	rric@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, oprofile-list@lists.sf.net
Subject: gcc trunk fails to build kernel on PowerPC64 due to oprofile warnings
Date: Thu, 26 Jan 2017 10:00:44 +1100	[thread overview]
Message-ID: <20170126100044.7e439f72@kryten> (raw)

Hi,

gcc trunk has failed to build PowerPC64 kernels for a month or so. The issue
is in oprofile, which is common code but ends up being sucked into
arch/powerpc and therefore subject to the -Werror applied to arch/powerpc:
=20
linux/arch/powerpc/oprofile/../../../drivers/oprofile/oprofile_stats.c: In =
function =E2=80=98oprofile_create_stats_files=E2=80=99:
linux/arch/powerpc/oprofile/../../../drivers/oprofile/oprofile_stats.c:55:2=
5: error: =E2=80=98%d=E2=80=99 directive output may be truncated writing be=
tween 1 and 11 bytes into a region of size 7 [-Werror=3Dformat-truncation=
=3D]
   snprintf(buf, 10, "cpu%d", i);
                         ^~
linux/arch/powerpc/oprofile/../../../drivers/oprofile/oprofile_stats.c:55:2=
1: note: using the range [1, -2147483648] for directive argument
   snprintf(buf, 10, "cpu%d", i);
                     ^~~~~~~
linux/arch/powerpc/oprofile/../../../drivers/oprofile/oprofile_stats.c:55:3=
: note: format output between 5 and 15 bytes into a destination of size 10
   snprintf(buf, 10, "cpu%d", i);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  LD      crypto/async_tx/built-in.o
  CC      lib/random32.o
cc1: all warnings being treated as errors

Anton

             reply	other threads:[~2017-01-25 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 23:00 Anton Blanchard [this message]
2017-01-26 11:00 ` gcc trunk fails to build kernel on PowerPC64 due to oprofile warnings David Laight
2017-01-26 12:57   ` Arnd Bergmann
2017-01-26 15:46 ` William Cohen
2017-01-26 16:06   ` Robert Richter
2017-01-30 15:35     ` William Cohen
2017-02-02 17:21     ` William Cohen

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=20170126100044.7e439f72@kryten \
    --to=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oprofile-list@lists.sf.net \
    --cc=paulus@samba.org \
    --cc=rric@kernel.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).