>> But since you have to have a new gas anyway, wouldn't it be simpler to >> have >> a new option for gas to instruct it to choose the opcodes that are >> expected >> by the win32 applications? > This was my first idea, but Alexandre Julliard(the Wine maintainer) disliked > it and prefered a function attribute to turn it on per-function. However, > from looking at the gcc code it seems that this is the best option to > generate Win32-friendly code everywhere. I'll look at your other suggestions > and talk to Alexandre again.
Indeed the option would just have to flip the movl/movl.s default... Paolo