Tom Evans wrote:
On Fri, 2007-05-04 at 18:03 +0400, valiy wrote:
<SNIP>
TEST1
FreeBSD idx 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #1: Wed Nov 8 18:59:20 UTC 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/SMP amd64


19:07:15 [EMAIL PROTECTED] ~ $ g++ ./test_set.cpp
19:07:23 [EMAIL PROTECTED] ~ $ ./a.out
filling
clearing
done
alloc time 1.938        clear time 15.290
<SNIP>
TEST2
FreeBSD proton 5.5-RELEASE FreeBSD 5.5-RELEASE #0: Mon Jun 26 21:47:56 MSD 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/PROTON i386
[EMAIL PROTECTED] ~]# g++ test_set.cpp
[EMAIL PROTECTED] ~]# ./a.out
filling
clearing
done
alloc time 2.529        clear time 5.685

<SNIP>
TEST3:
FreeBSD hotdog 4.9-RELEASE FreeBSD 4.9-RELEASE #3: Fri Jul 1 19:35:10 MSD 2005 [EMAIL PROTECTED]:/usr/src/sys/compile/HOTDOG i386

19:18 [EMAIL PROTECTED] vvolodin $ ./a.out
filling
clearing
done
alloc time 4.001        clear time 0.305

pentium3 2x700MHz

how to fix?


(Couldnt see your 6.2 result, did I snip it?)

Upgrade to 6.2, or for better results, 7-CURRENT $ uname -a && ./stl_test FreeBSD zoot.mintel.co.uk 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Wed Mar 28
12:29:25 BST 2007     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZOOT
i386
filling
clearing
done
alloc time 2.252        clear time 0.441
(CURRENT with no INVARIANTS nor WITNESS, and MALLOC_PRODUCTION defined)


$ uname -a && ./stl_test
FreeBSD bob.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Thu Jan 18
14:18:05 GMT 2007     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOB
i386
filling
clearing
done
alloc time 2.705        clear time 5.691

Is your test for 4 using GCC 2.95 ? C++ in GCC 2.95 is «interesting» in
the shortcuts it takes.
We didn't include 6.2 report in mail, but we experience same probles. results are exactly as yours above (alloc time 2.7 clear time 5.6)

BSD 4 test was using compiler 2.95

Is there any way to fix it without upgrading to 7.0?
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to