Hi!
> > I am aware of a couple of cases where code relied on static
> > variables being allocated contiguously, but, in both cases, those
> > variables were either all zeros or all non-zeros, so my proposed
> > change would not break such code.
>
> Continuous placement is not the only proper
Followup to: <[EMAIL PROTECTED]>
By author:Ulrich Drepper <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> "Adam J. Richter" <[EMAIL PROTECTED]> writes:
>
> > >Shouldn't a compiler be able to deal with this instead?
> >
> > Yes.
>
> No. gcc must not do this. There are situation
>Thanks, but Andrey Panin did you one better -- he produced a patch which
>fixes up a good number of these. You should follow lkml more closely :)
I missed that patch and have been unable to find it on google/dejanews.
However, my point is to provide an exhaustive list with sizes (and the tool
f
>> I am aware of a couple of cases where code relied on static
>> variables being allocated contiguously, but, in both cases, those
>> variables were either all zeros or all non-zeros, so my proposed
>> change would not break such code.
>Continuous placement is not the only property defined
"Adam J. Richter" wrote:
> For anyone who is interested, I have produced a list of all
> of the .data variables that contain all zeroes and could be moved to
> .bss within the kernel and all of the modules (all of the modules
> that we build at Yggdrasil for x86, which is almost all). The
"Adam J. Richter" <[EMAIL PROTECTED]> writes:
> I am aware of a couple of cases where code relied on static
> variables being allocated contiguously, but, in both cases, those
> variables were either all zeros or all non-zeros, so my proposed
> change would not break such code.
Continuous
"Adam J. Richter" <[EMAIL PROTECTED]> writes:
> >Shouldn't a compiler be able to deal with this instead?
>
> Yes.
No. gcc must not do this. There are situations where you must place
a zero-initialized variable in .data. It is a programmer problem.
--
---.
[EMAIL PROTECTED] writes:
>Shouldn't a compiler be able to deal with this instead?
Yes. I sent some email to bug-gcc about this a couple of
months ago and even posted some (probably horribly incorrect) code
showing roughly the change I had in mind in the gcc source code
for the simple ca
On Thu, 12 Apr 2001 [EMAIL PROTECTED] wrote:
> Shouldn't a compiler be able to deal with this instead?
> (Just a thought.)
> /Johan
The compiler does deal with it. That's why you have a choice when
you write code.
The defacto standard has been that initialized data, regardless of
whether it's i
On Thu, Apr 12, 2001 at 04:44:48PM +0200, [EMAIL PROTECTED] wrote:
> Shouldn't a compiler be able to deal with this instead?
> (Just a thought.)
Search the lkml archives for discussion on this topic around Christmas.
--
Russell King ([EMAIL PROTECTED])The developer of ARM Linux
Shouldn't a compiler be able to deal with this instead?
(Just a thought.)
/Johan
- Original Message -
From: Adam J. Richter <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 12, 2001 2:36 PM
Subject: List of all-zero .data variables in linux-2.4.3 availab
For anyone who is interested, I have produced a list of all
of the .data variables that contain all zeroes and could be moved to
.bss within the kernel and all of the modules (all of the modules
that we build at Yggdrasil for x86, which is almost all). These
are global or static variables
12 matches
Mail list logo
