<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=koi8-r">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><span style="font-size: 12pt; color: rgb(33, 33, 33);">>></span><span style="font-size: 12pt; color: rgb(33, 33, 33);">Not sure I un</span><span style="font-size: 12pt; color: rgb(33, 33, 33);">derstand what you're suggesting here, sorry :/ </span></p>
<div dir="ltr" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<div>
<div style="color:rgb(33,33,33)">
<div>
<div dir="ltr">
<div class="gmail_quote">
<div>> </div>
<div>>Ah, looks it is that:<br>
</div>
<div>>"t<span style="font-family:"Segoe UI","Segoe WP","Segoe UI WPC",Tahoma,Arial,sans-serif; font-size:15px">hat's why something like Apple's scheme (leave the debug info in the object files, but have the linker ignore them -</span>
<div style="color:rgb(33,33,33); font-family:Calibri,Arial,Helvetica,sans-serif; font-size:16px; background-color:rgb(255,255,255)">
<span style="font-family:"Segoe UI","Segoe WP","Segoe UI WPC",Tahoma,Arial,sans-serif; font-size:15px">>then merge the debug info separately in dsymutil) wasn't applicabl</span>e".<br>
</div>
> </div>
<div>So instead of splitting debug info into separate files, info could be still included into linker output.<br>
>But difference with current traditional flow is that linker would <span style="font-size:12pt">not process debug relocations</span></div>
<div><span style="font-size:12pt">>(because technically info can be (probably) close/the same as split debug has)</span><span style="font-size:12pt">, what could (probably</span><span style="font-size:12pt">)</span></div>
<div>>resolve issues with relocations processing (too large values). Could keep the single output file, but save time<br>
</div>
<div>>that linker normally spends on resolving relocations. And allows to do things like deduplications inside linker</div>
<div>>(what can be convinent). Though increases output size (not sure it is still a problem nowadays).<br>
</div>
<div><span style="font-size:12pt">> </span></div>
<div><span style="font-size:12pt">>Have to run away now, sorry.</span></div>
<div><span style="font-size:12pt">> </span></div>
<div><span style="font-size:12pt">>George.</span><br>
</div>
<div><span style="font-size:12pt"><br>
</span></div>
<div><span style="font-size:12pt">Ok. That above looks sound wierd. I think I just need to read more about how all DWARF things work then.</span></div>
<div><span style="font-size:12pt">(particularry about split debug output details and dsymutil, though their logic looks transparent for me atm). </span></div>
<div><span style="font-size:12pt"></span><span style="font-size: 12pt;">Or that brief description I mentioned I saw somewhere was dead</span></div>
<div><span style="font-size: 12pt;">from start or it </span><span style="font-size: 12pt;">most
</span><span style="font-size: 12pt;">likely it </span><span style="font-size: 12pt;">was just something else/different suggested, probably with involving</span></div>
<div><span style="font-size: 12pt;">a compiler/debugger side changes too </span><span style="font-size: 12pt;">a</span><span style="font-size: 12pt;">s well</span><span style="font-size: 12pt;">. Can only guess now :/</span></div>
<div><span style="font-size: 12pt;"><br>
</span></div>
<div><span style="font-size: 12pt;">George.</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>