Processed: issetugid

Processing commands for cont...@bugs.debian.org: forcemerge 718181 635205 Bug #718181 {Done: Adam Conrad adcon...@0c3.net} [libc0.1-dev] missing declaration for issetugid Bug #718181 {Done: Adam Conrad adcon...@0c3.net} [libc0.1-dev] missing declaration for issetugid Marked as found in

Bug#718577: libc6: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

Package: libc6 Version: 2.17-7 Severity: important Dear Maintainer, * What led up to the situation? I tried to upgrade my debian testing 64 bits, based on a 3.2.0-amd64 kernel (and libc6/libm-2.13.so) to use the current testing/jessie debian based on a 3.9.8-amd64 kernel (and

Bug#718577: libc6: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

On Fri, Aug 2, 2013 at 12:10 PM, bugsbuster hal.bugsbus...@gmail.com wrote: * What led up to the situation? Upstream glibc fixed a number of correctness issues in non-default rounding modes. These correctness issues had a performance impact which has only just been fixed in 2.18. I suggest

Bug#718577: libc6: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

Hello, First of all, thank you for this quick answer and sorry for this (long) answer... However, I am not sure (sorry) to understand the full consequences of what you called a justified tradeoff... I cannot fully explain what I am doing exactly but I am working on soft real-time avionic

Processed: Re: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

Processing commands for cont...@bugs.debian.org: tags 718577 + upstream patch Bug #718577 [libc6] libc6: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations Added tag(s) upstream and patch. quit Stopping processing here. Please contact me if you need assistance. --

Bug#718577: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

tags 718577 + upstream patch quit Hal BugsBuster wrote: Do you mean that all these catastrophic overheads are no longer existing in libm-2.18 ? Yes, I believe Carlos was saying that glibc 2.18 has a fix for the performance regression, which Debian should apply: commit

Bug#718577: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

Hello, Thank you again for this quick answer... It would be REALLY good news (for me). Thank you again, BB 2013/8/3 Jonathan Nieder jrnie...@gmail.com tags 718577 + upstream patch quit Hal BugsBuster wrote: Do you mean that all these catastrophic overheads are no longer existing

Bug#718577: libc6: Libc6/libm-2.17 almost two times slower than 2.13 in trigonometric calculations

On Fri, Aug 2, 2013 at 7:45 PM, Hal BugsBuster hal.bugsbus...@gmail.com wrote: I cannot fully explain what I am doing exactly but I am working on soft real-time avionic problems and the use of libm2-17 is ... IMPOSSIBLE since it multiplies by two the duration of all our computations... I'm