Torsten Rohlfing writes:
> Andrew Haley wrote:
>
> > > When I run the two binaries on the exact same box and time them, I get
> > > the following outputs:
> > >
> > > time ./testlog64
> > > 13.264u 0.000s 0:13.26 100.0% 0+0k 0+0io 0pf+0w
> > >
> > > time ./testlog32
> > > 6.960u 0.0
Andrew Haley wrote:
> When I run the two binaries on the exact same box and time them, I get
> the following outputs:
>
> time ./testlog64
> 13.264u 0.000s 0:13.26 100.0% 0+0k 0+0io 0pf+0w
>
> time ./testlog32
> 6.960u 0.004s 0:06.96 100.0%0+0k 0+0io 0pf+0w
You have weird hardware.
[
Torsten Rohlfing writes:
> Greetings.
>
> I am experiencing a major performance problem with the log() function on
> the x86_64 platform. It can be illustrated with the following little
> test program:
>
> testlog.cxx===
> #include
>
> main()
> {
> float f = 0;
>
I think it is a glibc issue.
H.J.
-
On Tue, Mar 14, 2006 at 01:18:34PM -0800, Torsten Rohlfing wrote:
> Greetings.
>
> I am experiencing a major performance problem with the log() function on
> the x86_64 platform. It can be illustrated with the following little
> test program:
>
> te
Greetings.
I am experiencing a major performance problem with the log() function on
the x86_64 platform. It can be illustrated with the following little
test program:
testlog.cxx===
#include
main()
{
float f = 0;
for ( int i = 0; i < 1e8; ++i )
f += log(
