<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 17, 2010, at 1:12 PM, İsmail Dönmez wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><font size="2"><font face="tahoma,sans-serif"><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><font size="2"><font face="tahoma,sans-serif">Hi;</font></font><div>
<font size="2"><font face="tahoma,sans-serif"><br></font></font></div><div><font size="2"><font face="tahoma,sans-serif">I have a late MacBook Pro 2010 laptop, equipped with Core i7;</font></font></div><div><font size="2"><font face="tahoma,sans-serif"><br>
</font></font></div><div><font size="2"><font face="tahoma,sans-serif"><div>[~/Sources/llvm]> sysctl -a|grep -i model</div><div>hw.model = MacBookPro6,2</div><div>machdep.cpu.model: 37</div><div>machdep.cpu.extmodel: 2</div>
<div><br></div><div>[~/Sources/llvm]> sysctl -a|grep -i family</div><div>hw.cpufamily: 1463508716</div><div>machdep.cpu.family: 6</div><div>machdep.cpu.extfamily: 0</div></font></font></div></span></font></font></blockquote><br></div><div>Hey, me too! Applied in r114302. While a more encompassing solution is appreciated, this is good progress in the right direction.</div><div><br></div><div>-Chris</div><br></body></html>