From: Tejun Heo <tj@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jens Axboe <axboe@fb.com>,
torvalds@linuxfoundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Cgroup writeback support for 4.2
Date: Fri, 26 Jun 2015 10:28:58 -0400 [thread overview]
Message-ID: <20150626142858.GD15805@mtj.duckdns.org> (raw)
In-Reply-To: <CAMuHMdWg-Nosb4pk=uB_hS=cZHgKirV-MmCXh+PBd=e=82if8g@mail.gmail.com>
Hello, Geert.
On Fri, Jun 26, 2015 at 03:57:18PM +0200, Geert Uytterhoeven wrote:
> > Can you please tell me the version of gcc which triggered the above
> > warnings?
>
> gcc 4.1.2
I see. I read wrong.
> That's why I keep on using gcc 4.1.2: it still gives build warnings for
> many "used uninitialized" cases that later gcc versions let pass silently.
>
> Granted, some of these are false positives (that's why it was disabled in
> later gcc versions), but some of these are valid and real bugs.
That's kinda surprising. My impression has been that later gcc
versions are doing a lot better job both at actually detecting
problematic ones and avoiding false positives. I'm surprised that
4.1.2 is still catching uninitialized usages later gcc's (and other
static analyzers) can't. Can you roughly say how often it detects
actual problems that later ones can't?
> Anyway, as a casual reader, it took me a while to notice all four warnings
> listed above are false positives...
4.1.2 is more than 8 years old at this point. I really don't want to
kludge the code w/ unnecessary initializations as that'll actually
harm our ability to detect actual problems. The only option would be
refactoring the code so that larger blocks of code are put into
#ifdefed functions but I'm not really sure whether keeping 4.1.2 happy
should be a guideline that we follow when organizing code.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-06-26 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 14:44 Jens Axboe
2015-06-26 9:49 ` Geert Uytterhoeven
2015-06-26 13:43 ` Tejun Heo
2015-06-26 13:57 ` Geert Uytterhoeven
2015-06-26 14:28 ` Tejun Heo [this message]
2015-06-26 14:56 ` Geert Uytterhoeven
2015-06-26 15:23 ` Tejun Heo
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=20150626142858.GD15805@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=axboe@fb.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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®