No Xcode needed :)<br>
<br>
Make sure you build x264 with ./configure --enable-debug as this will
make using shark quite a bit easier. Once you launch shark, you can
either launch x264 from within shark or attach to the running process
one you have already spawned it. I tend to do the latter since I can
tweak settings as I wish in the terminal without having to set up the
target again. Hot spots change widely with the settings used. <br>
<br>
Don't always count on shark being helpful - data mining, especially of
alignment has proven to give the most profound results for code
improvement so far. While Alignment isn't always perfect, you'll be
surprised how consistently out of alignment it is, and I do mean by out
of Alignment by an x amount of bytes :P. There's even a nice way to
handle contiguous accesses that start at an unaligned address. Remember
that the PowerPC architecture is roughly limited by the speed of which
it can do loads and stores - requesting more loads and stores that are
needed hurts performance considerably.<br>
<br>
<br>
Also be weary of GCC's ability or inability to correctly unroll/schedule loops.<br>
<br>
<br>
If you really, really want to build x264 from within XCode, your best
bet is to set up a target using an external make file. Make sure you
set the x264 Makefile as the target. It may make organization of the
source easier, it may not.<br>
<br>
Anyway, I'll see as to what I can do with the code I have.<br>
<br>
<br><br><div><span class="gmail_quote">On 3/13/06, <b class="gmail_sendername">Eric Petit</b> <<a href="mailto:titer@m0k.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">titer@m0k.org</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You don't need Xcode for Shark - you can use Shark on any running<br>application.<br><br>Firas Al-Tahan wrote:<br>> I'm certainly willing to try!<br>><br>> Tim - have you been able to get the x264 code into XCode
2.1? I<br>> haven't had much experience with XCode, and the book I bought ("The<br>> Mac XCode 2 Book" by Michael Cohen & Dennis Cohen) is a pile of crap.<br>><br>> Having read the Apple pages, the Shark tool should help identify areas
<br>> needing optimization. Once I get XCode working with the x264 project,<br>> il be happy.<br>><br>> Now, just to finish off the coursework and the exams first....<br>><br>> Firas<br>><br>> On 3/13/06, Tim Greatrex <
<a href="mailto:tim.greatrex@mac.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tim.greatrex@mac.com</a>> wrote:<br>>> I'm guessing the issue may be that he has worked on this in his spare
<br>>> time, while he works for a company that develops a different codec
<br>>> which it then sells (so x264 is classed as the competition). I<br>>> doesn't sound like there are any legal issues with the code he's<br>>> developed, but maybe moral issues for his position within his day-job.
<br>>><br>>> As a mac user (who is very new to c and at the moment can't make head-<br>>> nor-tail of the x264 code (though it works great!), let alone altivec<br>>> optimisations) it would be great if you could make it available,
<br>>> especially with some good annotations describing what does what if<br>>> possible, so that myself and people like Firas can learn from you.<br>>><br><br>--<br>This is the x264-devel mailing-list<br>
To unsubscribe, go to: <a href="http://developers.videolan.org/lists.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://developers.videolan.org/lists.html</a><br><br></blockquote></div><br>