[sginsberg] 43193: - Add more padding so our gcc compatible C_ASSERT doesn't conflict with ntoskrnl.h

Author: sginsberg
Date: Sun Sep 27 22:17:52 2009
New Revision: 43193

URL: http://svn.reactos.org/svn/reactos?rev=43193&view=rev
Log:
- Add more padding so our gcc compatible C_ASSERT doesn't conflict with ntoskrnl.h

Modified:
    trunk/reactos/ntoskrnl/mm/pe.c

Modified: trunk/reactos/ntoskrnl/mm/pe.c
URL:
http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/mm/pe.c?rev=43193…
==============================================================================
--- trunk/reactos/ntoskrnl/mm/pe.c [iso-8859-1] (original)
+++ trunk/reactos/ntoskrnl/mm/pe.c [iso-8859-1] Sun Sep 27 22:17:52 2009
@@ -46,10 +46,6 @@
     return Addend1 <= (MAXULONG_PTR - Addend2);
 }
 
-#ifndef MAXLONGLONG
-#define MAXLONGLONG ((LONGLONG)((~((ULONGLONG)0)) >> 1))
-#endif
-
 static __inline BOOLEAN Intsafe_CanAddLong64(IN LONG64 Addend1, IN LONG64 Addend2)
 {
     return Addend1 <= (MAXLONGLONG - Addend2);
@@ -161,11 +157,15 @@
 
 
 
+
+
 //
 // FIXME: All this whitespace is "padding" so the C_ASSERTs aren't on the
same lines as asserts in other headers.
 // This is necessary because of the way we define C_ASSERT in a gcc compatible way.
 // This can be removed once we upgrade to gcc 4.3.x or later (which implements
__COUNTER__).
 //
+
+