Author: hbelusca
Date: Sun Oct 26 11:50:14 2014
New Revision: 65009

URL: http://svn.reactos.org/svn/reactos?rev=65009&view=rev
Log:
[FAST486][NTVDM]: Do not compile some FPU functions when FAST486_NO_FPU is 
defined (fixes build).

Modified:
    trunk/reactos/lib/fast486/fpu.c
    trunk/reactos/subsystems/ntvdm/cpu/registers.c

Modified: trunk/reactos/lib/fast486/fpu.c
URL: 
http://svn.reactos.org/svn/reactos/trunk/reactos/lib/fast486/fpu.c?rev=65009&r1=65008&r2=65009&view=diff
==============================================================================
--- trunk/reactos/lib/fast486/fpu.c     [iso-8859-1] (original)
+++ trunk/reactos/lib/fast486/fpu.c     [iso-8859-1] Sun Oct 26 11:50:14 2014
@@ -32,6 +32,8 @@
 
 /* PRIVATE FUNCTIONS 
**********************************************************/
 
+#ifndef FAST486_NO_FPU
+
 static ULONGLONG
 UnsignedMult128(ULONGLONG Multiplicand,
                 ULONGLONG Multiplier,
@@ -302,6 +304,8 @@
     UNREFERENCED_PARAMETER(TempResult);
     UNIMPLEMENTED;
 }
+
+#endif
 
 /* PUBLIC FUNCTIONS 
***********************************************************/
 

Modified: trunk/reactos/subsystems/ntvdm/cpu/registers.c
URL: 
http://svn.reactos.org/svn/reactos/trunk/reactos/subsystems/ntvdm/cpu/registers.c?rev=65009&r1=65008&r2=65009&view=diff
==============================================================================
--- trunk/reactos/subsystems/ntvdm/cpu/registers.c      [iso-8859-1] (original)
+++ trunk/reactos/subsystems/ntvdm/cpu/registers.c      [iso-8859-1] Sun Oct 26 
11:50:14 2014
@@ -39,6 +39,7 @@
         IntelRegPtr.Dr7 = EmulatorContext.DebugRegisters[FAST486_REG_DR7];
     }
 
+#ifndef FAST486_NO_FPU
     if (IntelRegPtr.ContextFlags & CONTEXT_FLOATING_POINT)
     {
         // IntelRegPtr.FloatSave = ;
@@ -52,6 +53,7 @@
         // IntelRegPtr.FloatSave.RegisterArea  = ; // This is a region of size 
SIZE_OF_80387_REGISTERS == 80 bytes
         // IntelRegPtr.FloatSave.Cr0NpxState   = ;
     }
+#endif
 
     if (IntelRegPtr.ContextFlags & CONTEXT_SEGMENTS)
     {


Reply via email to