From: Robert Richter <rric@kernel.org>
To: William Cohen <wcohen@redhat.com>
Cc: Anton Blanchard <anton@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
oprofile-list@lists.sf.net, linuxppc-dev@lists.ozlabs.org
Subject: Re: gcc trunk fails to build kernel on PowerPC64 due to oprofile warnings
Date: Thu, 26 Jan 2017 17:06:25 +0100 [thread overview]
Message-ID: <20170126160512.GE4906@rric.localdomain> (raw)
In-Reply-To: <fe2c2fd9-d255-61ca-5328-ca5d45827f47@redhat.com>
On 26.01.17 10:46:43, William Cohen wrote:
> From 7e46dbd7dc5bc941926a4a63c28ccebf46493e8d Mon Sep 17 00:00:00 2001
> From: William Cohen <wcohen@redhat.com>
> Date: Thu, 26 Jan 2017 10:33:59 -0500
> Subject: [PATCH] Avoid hypthetical string truncation in oprofile stats buffer
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> Increased the size of an internal oprofile driver buffer ensuring that
> the string was never truncated for any possible int value to avoid the
> following gcc-7 compiler error on ppc when building the kernel:
Please test gcc7 for other archs first. I don't think this is the only
change needed to avoid this warning in oprofile code.
Thanks,
-Robert
next prev parent reply other threads:[~2017-01-26 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 23:00 gcc trunk fails to build kernel on PowerPC64 due to oprofile warnings Anton Blanchard
2017-01-26 11:00 ` David Laight
2017-01-26 12:57 ` Arnd Bergmann
2017-01-26 15:46 ` William Cohen
2017-01-26 16:06 ` Robert Richter [this message]
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=20170126160512.GE4906@rric.localdomain \
--to=rric@kernel.org \
--cc=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=wcohen@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).