From: Paul Bolle <pebolle@tiscali.nl>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: silence GCC warning
Date: Mon, 01 Oct 2012 12:32:57 +0200 [thread overview]
Message-ID: <1349087577.24442.21.camel@x61.thuisdomein> (raw)
In-Reply-To: <20121001101859.GC4360@opensource.wolfsonmicro.com>
On Mon, 2012-10-01 at 11:19 +0100, Mark Brown wrote:
> I haven't actually stared hard enough at the code to figure this out
> yet but given what you're changing I'd hope it's a flow analysis bug.
> I'm certainly not seeing a warning here.
Well, you may be using another version of gcc, or using different
defaults. I'm using gcc-4.7.2-2.fc17.x86_64 (ie, the gcc currently
shipped in Fedora 17 for x86_64), in what I think to be default
settings.
Note that it's not some local oddity. Looking at the (currently) latest
log for a Fedora build of v3.6-rc7 you'll find an identical warning [0].
Apparently that build was done with gcc-4.7.1-5.fc18.x86_64 [1].
Paul Bolle
[0] http://kojipkgs.fedoraproject.org/packages/kernel/3.6.0/0.rc7.git2.2.fc18/data/logs/x86_64/build.log
[1] http://kojipkgs.fedoraproject.org/packages/kernel/3.6.0/0.rc7.git2.2.fc18/data/logs/x86_64/root.log
next prev parent reply other threads:[~2012-10-01 10:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 10:15 Paul Bolle
2012-10-01 10:03 ` Mark Brown
2012-10-01 10:16 ` Paul Bolle
2012-10-01 10:19 ` Mark Brown
2012-10-01 10:32 ` Paul Bolle [this message]
2012-10-01 11:39 ` Mark Brown
2012-10-01 19:08 ` Paul Bolle
2012-10-01 19:11 ` Mark Brown
2012-10-03 0:11 ` Valdis.Kletnieks
2012-10-03 7:23 ` Paul Bolle
2012-10-03 11:06 ` Mark Brown
2012-10-05 22:20 ` Valdis.Kletnieks
2012-10-06 8:53 ` Mark Brown
2012-10-06 9:57 ` Paul Bolle
2012-10-08 1:14 ` Mark Brown
2012-10-08 20:06 ` [PATCH v2] " Paul Bolle
2012-10-12 6:26 ` Mark Brown
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=1349087577.24442.21.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®