> Do not forget the gcc-4.0/libvgahw.a bug as well. I would like to ship > well-built code in testing. As Eugene stated a couple of days ago, there are > spreaded volatile's all along the code, not only in libvgbahw.a.
Yeah. Well, my proposed change to the macros in compiler.h should catch most if not all of them! You want me to work on it now? :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
