Adjust the way FE_DFL_ENV is defined.

This avoids any possible issue with code possibly expecting __FE_DFL_ENV to be in the data bank when using the large memory model, although I don't think that happened in practice.
This commit is contained in:
Stephen Heumann 2022-07-11 18:30:37 -05:00
parent c3567c81a4
commit 753c9b9f20
1 changed files with 2 additions and 2 deletions

View File

@ -27,8 +27,8 @@ typedef unsigned short fexcept_t;
#define FE_TOWARDZERO 0xC0
#define FE_UPWARD 0x40
extern const fenv_t __FE_DFL_ENV;
#define FE_DFL_ENV (&__FE_DFL_ENV)
extern const fenv_t __FE_DFL_ENV[1];
#define FE_DFL_ENV (&*__FE_DFL_ENV)
int feclearexcept(int);
int fegetexceptflag(fexcept_t *, int);