Displaying 2 results from an estimated 2 matches for "__386__".
Did you mean:
__i386__
2001 May 18
1
RFC-interupt31-sv/restore
...the
following code as a template for a save/restore function. I'm not sure
about the whole thing and would like some help please.
Thanks.
Best regards,
Bob Goodwin
This code is incomplete and has syntax and other errors.
VOID _Int31_SvRestoreHandler()
/* this one is just for INTEL */
#ifdef __386__
/* an array to save the context in */
WORD svctx[];
/* return the address of the SaveRestore function */
/* assembly code to get the function call address of
SaveRestore() and return the address in the form CX:DX */
VOID SaveRestore()
{
_GET_CONTEXT;
if AL_reg(context) /...
2006 Nov 16
0
Building wine on rhel or centos 4 get compile error
...or: conflicting types for 'CONTEXT'
../../include/winnt.h:726: error: previous declaration of 'CONTEXT' was here
../../include/winnt.h:1896: warning: `__stdcall__' attribute ignored
../../include/winnt.h:1915: warning: `__stdcall__' attribute ignored
Seems like the defines __386__ and __x86_64__ are both defined for some
reason in winnt.h
I dont card if the compile is for 386 or x86_64. I just would like it to
compile.
What am I missing to get this to compile.
Jerry