From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Jason Wang <wangborong@cdjrlc.com>,
yukuai3@huawei.com
Subject: Re: [PATCH] macintosh: no need to initilise statics to 0
Date: Tue, 17 Aug 2021 12:44:20 -0500 [thread overview]
Message-ID: <20210817174420.GG1583@gate.crashing.org> (raw)
In-Reply-To: <2105ef52-b736-cc18-def9-02ac174d1922@csgroup.eu>
On Tue, Aug 17, 2021 at 01:59:33PM +0200, Christophe Leroy wrote:
>
>
> Le 17/08/2021 à 13:51, Jason Wang a écrit :
> >Global static variables dont need to be initialised to 0. Because
> >the compiler will initilise them.
>
> It is not the compiler, it is the Kernel. It is done here:
>
> https://elixir.bootlin.com/linux/v5.14-rc6/source/arch/powerpc/kernel/early_32.c
This implements part of the C language: everything with static storage
duration (which includes all global objects, not just those marked
"static") is initialized.
> Among those 44 changes, only 2 are related to the commit's description.
Yeah. Don't do that please :-/
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Jason Wang <wangborong@cdjrlc.com>,
benh@kernel.crashing.org, yukuai3@huawei.com,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] macintosh: no need to initilise statics to 0
Date: Tue, 17 Aug 2021 12:44:20 -0500 [thread overview]
Message-ID: <20210817174420.GG1583@gate.crashing.org> (raw)
In-Reply-To: <2105ef52-b736-cc18-def9-02ac174d1922@csgroup.eu>
On Tue, Aug 17, 2021 at 01:59:33PM +0200, Christophe Leroy wrote:
>
>
> Le 17/08/2021 à 13:51, Jason Wang a écrit :
> >Global static variables dont need to be initialised to 0. Because
> >the compiler will initilise them.
>
> It is not the compiler, it is the Kernel. It is done here:
>
> https://elixir.bootlin.com/linux/v5.14-rc6/source/arch/powerpc/kernel/early_32.c
This implements part of the C language: everything with static storage
duration (which includes all global objects, not just those marked
"static") is initialized.
> Among those 44 changes, only 2 are related to the commit's description.
Yeah. Don't do that please :-/
Segher
next prev parent reply other threads:[~2021-08-17 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 11:51 [PATCH] macintosh: no need to initilise statics to 0 Jason Wang
2021-08-17 11:51 ` Jason Wang
2021-08-17 11:59 ` Christophe Leroy
2021-08-17 11:59 ` Christophe Leroy
2021-08-17 17:44 ` Segher Boessenkool [this message]
2021-08-17 17:44 ` Segher Boessenkool
2021-08-17 18:05 ` Joe Perches
2021-08-17 18:05 ` Joe Perches
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=20210817174420.GG1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wangborong@cdjrlc.com \
--cc=yukuai3@huawei.com \
/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.