Messages in this thread | | | Date | Fri, 26 Jun 2015 16:56:11 +0200 | Subject | Re: [GIT PULL] Cgroup writeback support for 4.2 | From | Geert Uytterhoeven <> |
| |
Hi Tejun,
On Fri, Jun 26, 2015 at 4:28 PM, Tejun Heo <tj@kernel.org> wrote: >> 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?
A handful every merge window. That's why I keep on doing this :-)
Since the release of v4.1: - https://lkml.org/lkml/2015/6/25/334 - https://lkml.org/lkml/2015/6/25/337 - https://lkml.org/lkml/2015/6/24/88
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |