One potential solution adapted from your original idea of just using the system supplied `double`, that sidesteps this issue, is to not define `double_t` for Linux and only define it for MacOS and Windows. Since glibc is guaranteed to define `double_t` (cf. [these lines](https://github.com/bminor/glibc/blob/42d359350510506b87101cf77202fefcbfc790cb/math/math.h#L154-L192) in `math.h`) it should, in theory, work.
Bug 1729459 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
One potential solution adapted from your original idea of just using the system supplied `double`, that sidesteps this issue, is to not define `double_t` for Linux and only define it for MacOS and Windows. Since glibc is guaranteed to define `double_t` (cf. [these lines](https://github.com/bminor/glibc/blob/42d359350510506b87101cf77202fefcbfc790cb/math/math.h#L154-L192) in `math.h`) it should, in theory, work. I am thinking something like ``` #if defined(__linux__) && defined(__i386__) // do nothing, rely on glibc's double_t #else // keep the original code #endif ```
One potential solution adapted from your original idea of just using the system supplied `double`, that sidesteps this issue, is to not define `double_t` for 32-bit Linux and only define it for other platforms. Since glibc is guaranteed to define `double_t` (cf. [these lines](https://github.com/bminor/glibc/blob/42d359350510506b87101cf77202fefcbfc790cb/math/math.h#L154-L192) in `math.h`) it should, in theory, work (and it shouldn't break any existing behaviour on other platforms). I am thinking something like ``` #if defined(__linux__) && defined(__i386__) // do nothing, rely on glibc's double_t #else // keep the original code #endif ```