Your message dated Sun, 12 Apr 2020 18:38:14 +0200
with message-id <20200412163813.ga30...@debian.org>
and subject line Re: Bug#923698: gcc-mingw-w64 miscompiles PARI
has caused the Debian Bug report #923698,
regarding gcc-mingw-w64 miscompiles PARI
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
923698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-mingw-w64-x86-64
Version: 8.2.0-21+21.1
Severity: normal
Dear Stephen,
Since the upgrade to 8.2.0-17, gcc-mingw-w64-x86-64 miscompiles PARI/GP.
<https://pari.math.u-bordeaux.fr>
The native linux version is fine though.
The bug is caused by longjmp causing wine to crash with
0198:err:seh:setup_exception stack overflow 320 bytes in thread 0198 eip
000000007bc9a41c esp 00000000001314d0 stack 0x130000-0x131000-0x330000
when called in a function doing an unrelated setjmp _after_ the longjmp
(in other functions longjmp work fine), and it does not occurs with the debug
build.
One of the logs for the broken version is at
<https://pari.math.u-bordeaux.fr/buildlogs/e9a1cdf2-df47-4a47-8324-df35d1648c58>
(the test-suite fails under wine).
I use the following kit to crossbuild:
https://pari.math.u-bordeaux.fr/pub/pari/windows/paricrossmingwkit.tgz
So if you have a suggestion...
Cheers,
Bill.
--- End Message ---
--- Begin Message ---
Version: 21.3
Hi,
On Sun, Apr 12, 2020 at 02:55:36PM +0200, Bill Allombert wrote:
> On Sun, Apr 12, 2020 at 02:41:00PM +0200, Ivo De Decker wrote:
> > > I very much like to see a chaangelog that tell what changed betwee 8.2
> > > and 8.3 that could have fixed this.
> >
> > So I guess the current version in testing is ok, and the bug can be closed
> > there?
> >
> > If it works on gcc 8.3, does that mean it works with the version in stable
> > as
> > well? The current version in stable was built wit gcc 8.3.0-6.
>
> Yes, the gcc 8.3 I use now is the version in stable.
OK. Closing the bug.
Thanks!
Ivo
--- End Message ---
