RE: Live range splitting in new allocator

[David Korn <dkorn at pixelpower dot com>]

>> Ummm, -finitialize-stack[=value] would seem to make more sense than
>> initialize-all, since you would not be initializing the statics or
>> globals (or possibly the registers).
>
>Right.  IIRC, statics and globals are initialized to 0 by the system
>anyway (unless otherwise initialized in the code).
>
>For the registers, I guess the function prologue could set them to
>the specified value at the same time as the stack...

  And if there was a way to initialise the variables with a value that
in some way could be tracked back to the function (a hash of the function's
name, for example) you'd be able to spot when uninitialized pointers were
used and where they came from even if the error didn't occur until a 
completely diffeent part of the test app. was running.

       DaveK

-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************