<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Nick,<br>
<br>
On 8/27/2013 12:45 AM, Nick Kledzik wrote:<br>
</div>
<blockquote
cite="mid:C3178FDB-A019-4276-900A-489BE2C0C0C6@apple.com"
type="cite">
<pre wrap="">
On Aug 26, 2013, at 10:20 PM, Shankar Easwaran wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Can we add deadStrip() to undefinedAtoms as well ?
This will enable to choose whether we want to set the property deadStripNormal or deadStripNever on them.
Also I think it will be cleaner for atoms to be added to deadStripRoot set using a single API.
</pre>
</blockquote>
<pre wrap="">
Can you give more more background on this? When would you want and undef that causes the whatever defined atom replaces it to be never dead stripped?</pre>
</blockquote>
We have these options<br>
<br>
a) -entry <symbolname><br>
b) -init <symbolname><br>
c) -fini <symbolname><br>
<br>
The atoms created for this shouldnot be dead stripped, as there is
an explicit reference from the command line.<br>
<br>
The other options such as<br>
<br>
a) --defsym newsymbol = oldsymbol + 100<br>
b) --wrap newsymbol<br>
<br>
have the other effect that if there is no reference to the symbols <i>newsymbol,
and __wrap_newsymbol, </i>the atoms are removed.<br>
<br>
Also rather than having the symbols seperately considered in the
Driver, on whether we want to add to the deadStripRoot set or not,
we can just use the attributes on the atom to place <br>
them in the deadStripRoot set / not. <br>
<br>
On the similiar lines, I think it should become an atom property
itself (having absoluteAtoms also have this property set) ?<br>
<br>
What do you think ?<br>
<br>
Thanks<br>
<br>
Shankar Easwaran<br>
</body>
</html>