On Wednesday 17 May 2006 1:45 am, Oliver Jones wrote:
I missed the beginning of this thread so my comments may be off topic
Hey the more info the better :)
but as a student games developer the subject of Assembler comes up occasionally. My advice is to avoid it like the plague but still be aware of your architecture's quirks and traits. Eg, a PlayStation 2 cache miss costs you 50 cpu cycles. Lesson, don't scatter your data all over RAM. :)
Holy cow!
Word alignment is important in languages like C too. Eg,
Yeah whoever says the way the code reads doesn't make a difference to the final program has probably never done system level stuff ;). Compilers are good, but they're not psychic. In the past I've been keen to make the code more readable, but examples like that probably crop up too often to ignore. That also explains partly why kernel code is somewhat spares sometimes. Thanks for your insight. -- It seems like once people grow up, they have no idea what's cool. -- Calvin