> 2. In the delay loop tip there's a function definition: >> >> "static void __inline__ brief_pause(register unsigned int n)" >> >> Why there's a "register" modifier? >> >> AFAIK this kind of thing isn't useful with _optimizing_ compiler, >> GCC is. >> > It certainly does no harm. It doesn't seem to be completely ignored by > modern compilers, though it certainly doesn't have the major effect on > compilation that it did in the 80's. I don't think GCC, or other modern > compilers, actually make a clear statement that it is completely > obsolete and ineffective. >
Sure. But this "register" thing is a assemblerizm in the C code. so to speak. And you, according to your posts, do not advise to dig in to assembler, while in C. If one wants really optimize something in such specific routine with assembler, one must use a macro for that, because static inline with C, is the first thing GCC will optimize in various ways [0:], but `asm volatile' OTOH isn't _for optimization_ thing. That is what i meant. [0:] http://article.gmane.org/gmane.comp.gcc.help/19227 > Steve > -- -o--=O`C info emacs : not found #oo'L O info make : not found <___=E M man gcc : not found
