From: Russell King <rmk@arm.linux.org.uk>
To: Thomas Hood <jdthood@mail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Combined APM patch
Date: Fri, 11 Jan 2002 15:40:16 +0000 [thread overview]
Message-ID: <20020111154016.D31366@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1010762545.788.2.camel@thanatos>
In-Reply-To: <1010762545.788.2.camel@thanatos>; from jdthood@mail.com on Fri, Jan 11, 2002 at 10:22:24AM -0500
On Fri, Jan 11, 2002 at 10:22:24AM -0500, Thomas Hood wrote:
> This is useful information,
> because if someone later wants to modify the code to make
> this variable non-static, the comment tells that person that
> the variable will need an initializer.
Whether a variable is static or not doesn't change whether it ends up in
the bss segment or not.
/* top level */
static int foo;
int bar;
Both foo and bar will be initialised to 0 - since they're both placed
into the BSS segment (or maybe its common subsection):
$ gcc -S -o - t.c
@ Generated by gcc 2.96 20000731 (Red Hat Linux 7.1 2.96-80) for ARM/elf
.file "t.c"
gcc2_compiled.:
.bss
.align 2
foo:
.space 4
.comm bar, 4 @ 4
$ gcc -S -o - t.c -fno-common
@ Generated by gcc 2.96 20000731 (Red Hat Linux 7.1 2.96-80) for ARM/elf
.file "t.c"
gcc2_compiled.:
.bss
.align 2
foo:
.space 4
.global bar
.align 2
.type bar,object
.size bar,4
bar:
.space 4
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-01-11 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 15:22 [PATCH] Combined APM patch Thomas Hood
2002-01-11 15:40 ` Russell King [this message]
2002-01-18 10:43 ` Thomas Hood
2002-01-18 10:57 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 18:37 Bob Toxen
2002-01-10 16:20 David Balazic
2002-01-07 4:52 Stephen Rothwell
2002-01-10 12:51 ` Thomas Hood
2002-01-12 9:43 ` Borsenkow Andrej
2002-01-27 8:39 ` Borsenkow Andrej
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=20020111154016.D31366@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jdthood@mail.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