In article <FF6AB92D97A23A409701CDBF66F03FCD2E96AD17 at 505fuji>,
Ian King <IanK at vulcan.com> writes:
And too few people who take the trouble to learn the
assembly bother
to learn the machine representation of the instructions--or the
architecture of the implementation. Even fewer learn how to time
instruction execution--perhaps it's no longer relevant.
All of this is now the job of the compiler.
It ain't 1980 anymore.
You've never found a compiler bug? :-)
To be honest, no.
Every time I *thought* it was a compiler bug, it was mine. Then
again, I don't work in anything remotely like embedded computing where
the quality of the compiler can vary considerably I'm told. I often
hear from game programmers that game console C++ compilers are pretty
shitty. Apparently the console vendors insist on making their own
compilers or licensing a shitty one instead of making a decent back
end for gcc or something reasonably like that.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>