Put scope blocks on a diet

[Mark Mitchell]

Richard Guenther wrote:

>> 1. Revert the July patches and declare that (for now) DECL_UIDs must not
>> be influenced by -g.  Pros: -g doesn't affect generated code.  Cons:
>> compiler uses more memory than it does now, though no more than 4.2.
>>
>> 2. Accept that (for now) -g may affect generated code.  Pros: compiler
>> users less memory.  Cons: -g affects generated code.
>>
>> 3. Do something that makes us depend, at most, on DECL_UID order -- but
>> not on exact values.  Pros: -g doesn't affect generated code, compiler
>> uses less memory.  Cons: have to do something hard.
>>
>> Is that right?  Nobody's going to like either (1) or (2) -- but as RM,
>> if I have to choose, I'm probably going to pick (1) because I think the
>> -g principle is critical.
> 
> I also would pick (1) for now, as ...

Alexandre will presumably pick (1) as well, since, IIUC, he values
highly getting the same code without and without -g.

So, does anyone either (a) have objections to (1), or (b) want to try
(3)?  If nobody objects within 48 hours, a patch to revert the July
patches (making whatever minor changes might be necessary given the
passage of time) is preapproved.  Of course, if there are objections,
we'll continue to discuss.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713