Linked by Thom Holwerda on Thu 7th Oct 2010 19:10 UTC, submitted by tyrione
Permalink for comment 444531
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2010-03-08
Oh, and another almost-mandatory compiler extension to C and derivatives that's not properly described by the relevant standards : inline assembly. As awful as GCC's syntax for it can be, it's often much better than keeping separate .s files and writing headers for them, because...
-Doing so is overkill for those assembly snippets of less than 10 lines that form most of CPU-specific code.
-When you're writing ASM, you don't write portable code anyway.
-It's better for code clarity.
-Except for that class of tiny CPU-specific code chunks, ASM is often used for high-performance code, that kind of code where even a CALL's penalty can be too much...
Edited 2010-10-08 17:00 UTC