Mail Archives: djgpp-workers/2000/05/16/00:46:14
> In message <200005152236 DOT RAA05926 AT hp2 DOT xraylith DOT wisc DOT edu>you write:
> > > Such as? Do we need to extend the things provided by gcc's float.h? Or
> > is
> > > it in our best interest to give up and use the system one?
> >
> > The extra stuff has to do with dealing with the FPU (exceptions codes,
> > control routines, and a bunch of other stuff). We could probably modify
> > the system headers to include these with math.h as well with preprocessor
> > guards, but that'll create an incompatibility with headers supplied by
> > Microsoft in it's Platform SDK and that I'd like to avoid.
> Would the #include_next trick work, or is it inappropriate?
>
These very same extras are in DJGPP's float.h and for reasons that go way back I'm
sure. I would think adding this trick will work for Mingw32, since the C runtime comes
with the compiler. But this won't work with DJGPP (at least not right away), since the
libc release is on an independant schedule. So we'd need another solution. Perhaps
adding magic to float.h to include a file that adds in the system-specific stuff. Or
perhaps including the extra stuff in the generated float.h itself?
- Raw text -