Am 22.02.2010 17:31, schrieb ron minnich:
The complex ways in which we have to convince gcc to do __asm__ correctly make me wonder if we shouldn't start putting assembly into assembly into .s files, not .c files. If we have this much trouble with __asm__, how much are we really gaining when we use it? Why not just set up a .s?
romcc in some cases. The other issue is that in an .s file, we're bound to function calling conventions. with __asm__, we can really include code.
Patrick