There's no need to use .code16gcc where we are writing assembler code
explicitly. It only affects word-size-ambiguous instructions, and we
should just be explicit. And we are.

Signed-off-by: David Woodhouse <david.woodho...@intel.com>
---
 src/fw/smm.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/fw/smm.c b/src/fw/smm.c
index 0f59f20..77e1e63 100644
--- a/src/fw/smm.c
+++ b/src/fw/smm.c
@@ -19,7 +19,7 @@
 extern u8 smm_relocation_start, smm_relocation_end;
 ASM32FLAT(
     ".global smm_relocation_start, smm_relocation_end\n"
-    "  .code16gcc\n"
+    "  .code16\n"
 
     /* code to relocate SMBASE to 0xa0000 */
     "smm_relocation_start:\n"
@@ -46,7 +46,7 @@ ASM32FLAT(
 extern u8 smm_code_start, smm_code_end;
 ASM32FLAT(
     ".global smm_code_start, smm_code_end\n"
-    "  .code16gcc\n"
+    "  .code16\n"
     "smm_code_start:\n"
     "  rsm\n"
     "smm_code_end:\n"
-- 
1.9.3


-- 
David Woodhouse                            Open Source Technology Centre
david.woodho...@intel.com                              Intel Corporation

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