From: Keith Owens <kaos@ocs.com.au>
To: Ron Gage <ron@rongage.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about module.[c,h] - kernel 2.4.18
Date: Sun, 12 May 2002 11:06:47 +1000 [thread overview]
Message-ID: <17380.1021165607@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "11 May 2002 20:33:09 -0400." <1021163601.558.32.camel@portable>
On 11 May 2002 20:33:09 -0400,
Ron Gage <ron@rongage.org> wrote:
>I came across a fairly major inconsistancy in module.c and module.h and
>I was hoping someone could tell me just how whacked my view of this
>is...
>In essence, there are 20 elements to the module struct (i386), but
>module.c only initializes 9 of those elements. This gives 11
>uninitialized elements (and compile warnings). These warnings are what
>I am trying to kill off.
struct module has static storage duration, all elements are
automatically set to 0 unless otherwise defined.
Which compiler is giving warnings? If you are using a compiler that
requires all elements of a static storage variable be initialized then
it appears to be in violation of the C standard.
6.7.8 Initialization
19 The initialization shall occur in initializer list order, each
initializer provided for a particular subobject overriding any
previously listed initializer for the same subobject; all
subobjects that are not initialized explicitly shall be
initialized implicitly the same as objects that have static
storage duration.
Static storage duration objects are set to 0.
prev parent reply other threads:[~2002-05-12 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 0:33 Ron Gage
2002-05-12 1:06 ` Keith Owens [this message]
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=17380.1021165607@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ron@rongage.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®