From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: -Wshadow
Date: Mon, 1 Mar 2004 10:04:28 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403010958240.31041@chaos> (raw)
Don't know about the latest version(s), but with 2.4.25, compiling
with -Wshadow brings up a lot of potential problems. One can
turn off (temporarily) the built in functions to get rid of the
spurious warnings about memcpy(), etc., then you see that too many
variables to mention here are shadowed (probably thousands). Some
of them may be hazardous because they are spin-lock variables and
semaphores. There are also some shadowed functions. NotGood(tm)!
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
reply other threads:[~2004-03-01 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.53.0403010958240.31041@chaos \
--to=root@chaos.analogic.com \
--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®