tags 383759 + confirmed tags 383759 - unreproducible stop Hi
On 2006-08-31 Yavor Doganov wrote: > Those two bugs are easily reproducible on CPU << Pentium Classic. It was confirmed in the upstream discussion at http://bugs.mysql.com/bug.php?id=21765 > It was downgraded, I guess, to enable the propagation of the last mysql > security uploads to testing. The problem affects only us, the "second > class" citizens that have old machines. It was tagged "wontfix" because > Christian Hammers (the mysql maintainer) believes that it won't be fixed > by upstream. I tend to agree with him with regret. Yes, upstream won't disable assembler optimization as the problem only occurs only on very early i486 and clones like Cyrix, not even on most real i486. There are just too a few of you unlucky guys left :) > > > Well, I happen to know for a fact that the processor actually does > > > have a CPUID instruction, it's just disabled by default. It can be > > > enabled quite easily, which might be an avenue of enquiry for this > > > problem. > > I would be very grateful if you tell me how to do it. It will resolve > the issue at least for our Cyrix CPUs, but will remain for 486. If you want, you can try to find and enable the suggested "TAOCRYPT_DISABLE_X86ASM" option and rebuild the package yourself (tell me if it works) or just build without --with-yassl. > For me this bug is RC, because Debian is supposed to support CPUs >=i486 > for the i386 architecture. So to latest information it does works on most i486 CPUs. Although it's just the SSL part of MySQL I have strong feelings against using inofficial compiler flags and rather leave it as maybe RC but +wontfix as 486 owners rarely run database servers ... Steve, what do you think? bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
