From: Arnd Bergmann <arnd@arndb.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] Fix gcc4 warning,
Date: Mon, 23 May 2005 01:05:26 +0000 [thread overview]
Message-ID: <200505230305.27341.arnd@arndb.de> (raw)
In-Reply-To: <428E3224.8030307@cs.pdx.edu>
On Sünndag 22 Mai 2005 20:33, Jesse Millan wrote:
> Its not easy to reproduce this warning in a simple program. And, I am
> not sure that it is a bug on gcc4's part. It looks like gcc4 emits the
> warning when it cannot prove beyond a shadow of doubt that the variable
> is initialized before use.
Right. The behavior of gcc4 makes perfect sense, I would not call it a
bug at all, even though it could still become smarter.
> In an effort to cut down on warnings, should these be fixed? It can go
> either way, the compiler should be smart enough and maybe it will be
> someday, or, do the initialization to get rid of a bunch of warnings.
As I said, they should be fixed in the kernel, the released compiler
won't go away any more so it doesn't matter if future compilers are
smarter than the current one.
Arnd <><
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-05-23 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 18:53 [KJ] [PATCH] Fix gcc4 warning, Jesse Millan
2005-05-20 19:41 ` Alexey Dobriyan
2005-05-22 9:25 ` Arnd Bergmann
2005-05-23 1:05 ` Arnd Bergmann [this message]
2005-05-24 4:52 ` Jesse Millan
2005-05-24 4:56 ` Jesse Millan
2005-05-25 6:09 ` Jesse Millan
2005-05-25 22:41 ` Jesse Millan
2005-05-26 21:07 ` Arnd Bergmann
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=200505230305.27341.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.