On 2025-06-13 Bruno Haible wrote:
> Lasse Collin wrote:
> > I mentioned this thread on #mingw-w64 on OFTC. I was asked if I
> > could ask the Gnulib developers to report the bugs with minimal
> > reproducible examples to the mingw-w64-public mailing list[1].
>
> I usually don't spend much time r
Lasse Collin wrote:
> I mentioned this thread on #mingw-w64 on OFTC. I was asked if I
> could ask the Gnulib developers to report the bugs with minimal
> reproducible examples to the mingw-w64-public mailing list[1].
I usually don't spend much time reporting bugs for packages that are
not part of
On 2025-06-11 Bruno Haible via Gnulib discussion list wrote:
> In summary, the mingw approach that considers both the 387 unit and
> the SSE floating-point unit basically works. But, as usual with
> mingw, it comes with bugs:
> - The older mingw bugs in this area are still present.
> - They add
Hi Bruno,
Bruno Haible writes:
> Collin Funk wrote:
>> But, I think most of my issues came from trying to implement 'fegetenv'
>> and 'fesetenv'.
>
> Well, you started with the wrong module. Because the module
> 'fenv-environment' depends on 'fenv-exceptions-tracking-c99'
> and 'fenv-exceptions-
Collin Funk wrote:
> But, I think most of my issues came from trying to implement 'fegetenv'
> and 'fesetenv'.
Well, you started with the wrong module. Because the module
'fenv-environment' depends on 'fenv-exceptions-tracking-c99'
and 'fenv-exceptions-trapping', you need to have these two working
Hi Collin,
> > already did. How far did you get on this topic?
>
> I had a look a few weekends ago, but was not able to get it working.
> Then forgot about it... Sorry, I do not have much done for you.
Nothing to be sorry about. It's OK that you have different priorities.
> +# if defined _MSC_V
Hi Bruno,
Bruno Haible writes:
> On the GitHub CI machines, I now see compilation failures on mingw:
> [...]
> This means that the mingw people made a release with that change included,
> and it is active in the GitHub CI environments.
>
> I want to get this fixed ASAP, but I don't want to dupli
Hi Collin,
you wrote on 2025-04-25:
> > But that mingw change is likely to not work at all. Because gcc can
> > emit instructions that use the old i386/387 unit:
> > (a) When the program uses 'long double' values,
> > (b) When the option -mfpmath=387 is used, cf.
> > https://gcc.gnu.org/
Bruno Haible writes:
> When working on the floating-point code, one needs to have the hardware
> specification handy. In this case, it is the
> Intel® 64 and IA-32 Architectures Software Developer’s Manual
> Combined Volumes: 1, 2A, 2B, 2C, 2D, 3A, 3B, 3C, 3D and 4
> (4700 pages)
>
> Then,
Hi Collin,
> I can look at porting it but I have no knowledge of x86 floating point,
Thanks for volunteering to handle this.
When working on the floating-point code, one needs to have the hardware
specification handy. In this case, it is the
Intel® 64 and IA-32 Architectures Software Developer
10 matches
Mail list logo
