> Would this be portable check, guaranteeing that compilation on other > machine with other gcc version will not do opposite ? You are right, this is definitely NOT portable > And anyway, why not always putting it to volatile ? Once you started > embedding asm code, I guess you had a good reason for it to appear in > the output code... Good point. Andi