src\libc\dpmi\api\d0306.S, line 2-line 4.
code before fix:
#define USE_EBX
#define USE_EDI
#include "dpmidefs.h"
possible fix:
#define USE_EBX
#define USE_EDI
#define USE_ESI
#include "dpmidefs.h"
src\libc\dpmi\api\d0306.S, line 2-line 4.
code before fix:
#define USE_EBX
#define USE_EDI
#include "dpmidefs.h"
possible fix:
#define USE_EBX
#define USE_EDI
#define USE_ESI
#include "dpmidefs.h"
Yes, looks very reasonable, given that the DPMI call explicitly changes (e)si.
From: "Ozkan Sezer (sezeroz@gmail.com) [via djgpp@delorie.com]" <djgpp@delorie.com>
Date: Sun, 7 Aug 2022 07:14:22 +0300
On 8/6/22, Stefan Ring (stefanrin@gmail.com) [via djgpp@delorie.com] <djgpp@delorie.com> wrote:
src\libc\dpmi\api\d0306.S, line 2-line 4.
code before fix:
#define USE_EBX
#define USE_EDI
#include "dpmidefs.h"
possible fix:
#define USE_EBX
#define USE_EDI
#define USE_ESI
#include "dpmidefs.h"
Yes, looks very reasonable, given that the DPMI call explicitly changes (e)si.
OK then, is the following patch OK to apply?
From: "Ozkan Sezer (sezeroz@gmail.com) [via djgpp@delorie.com]"
<djgpp@delorie.com>
Date: Sun, 7 Aug 2022 07:14:22 +0300
On 8/6/22, Stefan Ring (stefanrin@gmail.com) [via djgpp@delorie.com]
<djgpp@delorie.com> wrote:
src\libc\dpmi\api\d0306.S, line 2-line 4.
code before fix:
#define USE_EBX
#define USE_EDI
#include "dpmidefs.h"
possible fix:
#define USE_EBX
#define USE_EDI
#define USE_ESI
#include "dpmidefs.h"
Yes, looks very reasonable, given that the DPMI call explicitly changes
(e)si.
OK then, is the following patch OK to apply?
Yes, thanks.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 251 |
Nodes: | 16 (0 / 16) |
Uptime: | 30:17:30 |
Calls: | 5,571 |
Calls today: | 1 |
Files: | 11,685 |
Messages: | 5,128,450 |