From: PCS <pcs@olympe.ch>
To: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] (1/3) cpufreq_ondemand - 01_ignore-nice.diff
Date: Sun, 20 Feb 2005 21:59:48 +0100 [thread overview]
Message-ID: <200502202159.48580.pcs@olympe.ch> (raw)
In-Reply-To: <20050220181448.GA5277@inskipp>
Le Dimanche 20 Février 2005 19.14, Alexander Clouter a écrit :
(snip)
> Along similar lines, I was told that initialising statics to zero *must* be
> done and not assumed; friends have told me its a 'gcc specific extension'.
> Last time I was told this was not necessary...
I'm really not sure it is a "gcc specific extension", re-read paragraph 6.7.8
from the ISO 9899:1999 norm, especially point 10. It explicitly say :
10 If an object that has automatic storage duration is not initialized
explicitly, its value is indeterminate. If an object that has static
storage duration is not initialized explicitly, then:
- if it has pointer type, it is initialized to a null pointer;
- if it has arithmetic type, it is initialized to (positive or unsigned
zero;
- if it is an aggregate, every member is initialized (recursively)
according to these rules;
- if it is a union, the first named member is initialized (recursively)
according to these rules.
Regards,
Pcs
next prev parent reply other threads:[~2005-02-20 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 13:15 [PATCH] (1/3) cpufreq_ondemand - 01_ignore-nice.diff Alexander Clouter
2005-02-20 14:12 ` Arjan van de Ven
2005-02-20 14:51 ` Dominik Brodowski
2005-02-20 14:53 ` Dominik Brodowski
2005-02-20 18:14 ` Alexander Clouter
2005-02-20 20:59 ` PCS [this message]
2005-02-21 11:41 ` Bruno Ducrot
2005-02-20 16:14 ` Eric Piel
2005-02-21 10:20 ` Eric Piel
2005-02-21 10:27 ` Alexander Clouter
2005-02-21 12:58 ` Eric Piel
2005-02-21 15:54 ` Dominik Brodowski
2005-02-21 13:11 ` Stefan Seyfried
2005-02-21 13:31 ` Eric Piel
-- strict thread matches above, loose matches on Subject: below --
2005-02-21 18:05 Pallipadi, Venkatesh
2005-05-10 22:30 Alexander Clouter
2005-05-11 1:30 ` Dave Jones
2005-05-11 2:38 ` Dave Jones
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=200502202159.48580.pcs@olympe.ch \
--to=pcs@olympe.ch \
--cc=cpufreq@lists.linux.org.uk \
/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.