This is a gratuitous GCC-ism. For C code actually compiled with GCC we
should be using -m16 where it's available (GCC 4.9+).

And where the only thing marked with .code16gcc is explicit assembler
code, we should just use .code16 and avoid letting the compiler make any
of the assumptions that the difference affects. Which, in fact, we
already do.

(Once upon a time with ancient versions of gas, we needed to
use .code16gcc because some instructions just wouldn't compile
otherwise. That hasn't been true for a while though.)

It still doesn't actually build with clang after this, but it's a bit
closer.

-- 
dwmw2

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
SeaBIOS mailing list
SeaBIOS@seabios.org
http://www.seabios.org/mailman/listinfo/seabios

Reply via email to