You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
(44) |
2
(9) |
3
(30) |
4
(28) |
5
(42) |
6
(14) |
7
(10) |
|
8
(7) |
9
(8) |
10
(6) |
11
(15) |
12
(13) |
13
(14) |
14
(23) |
|
15
(17) |
16
(10) |
17
(82) |
18
(14) |
19
(21) |
20
(14) |
21
(21) |
|
22
(7) |
23
(13) |
24
(16) |
25
(11) |
26
(11) |
27
(6) |
28
(7) |
|
29
(8) |
30
(13) |
31
(8) |
|
|
|
|
|
From: <js...@ac...> - 2006-10-07 13:34:36
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-10-07 09:00:02 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 214 tests, 10 stderr failures, 7 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/jm-int (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 208 tests, 10 stderr failures, 7 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/jm-int (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 09:11:45 2006 --- new.short Sat Oct 7 09:23:20 2006 *************** *** 8,10 **** ! == 208 tests, 10 stderr failures, 7 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) --- 8,10 ---- ! == 214 tests, 10 stderr failures, 7 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) |
|
From: <js...@ac...> - 2006-10-07 04:03:44
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-10-07 04:30:01 BST Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 244 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 238 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 04:47:39 2006 --- new.short Sat Oct 7 05:04:08 2006 *************** *** 10,12 **** ! == 238 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 10,12 ---- ! == 244 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) |
|
From: Tom H. <th...@cy...> - 2006-10-07 03:59:02
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-10-07 03:00:03 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 276 tests, 12 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/tls (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 270 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/tls (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 04:08:15 2006 --- new.short Sat Oct 7 04:58:52 2006 *************** *** 8,10 **** ! == 270 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,16 ---- ! == 276 tests, 12 stderr failures, 2 stdout failures, 0 posttest failures == ! memcheck/tests/leak-pool-0 (stderr) ! memcheck/tests/leak-pool-1 (stderr) ! memcheck/tests/leak-pool-2 (stderr) ! memcheck/tests/leak-pool-3 (stderr) ! memcheck/tests/leak-pool-4 (stderr) ! memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) |
|
From: Tom H. <to...@co...> - 2006-10-07 02:45:04
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-10-07 03:30:07 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 246 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 240 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 03:37:38 2006 --- new.short Sat Oct 7 03:44:57 2006 *************** *** 8,10 **** ! == 240 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,10 ---- ! == 246 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) |
|
From: Edward W. <ew...@ta...> - 2006-10-07 02:28:56
|
Hi Nick, >> So you're trying to make Valgrind go faster, or dynamic binary translation=20 >> systems in general? > Dynamic binary systems in general. I work on the NSF TeraGrid, a distributed high performance computing infrastructure in the US, and one of our biggest challenges is in supporting the plethora of ISAs that we host in our distributed infrastructure. So a research challenge is to enable _some_ HPC applications to be able to migrate between systems connected across our 30 gbps network backbone across the country. There are lots of people working on using VMMs like Xen to enable this, but I think for many situations, user-space dynamic binary translators like valgrind are sufficient, without the overhead of setting up entire OS VMs as containers for a running HPC job across sites.=20 And since I am in the area of HPC, performance (plus reliability) is a very important consideration. Fortunately, many of our systems are now multi-core, e.g. here in Texas we support a system with 1300 woodcrest compute nodes, each of which provides to the application a dual-CPU, dual-core processor. Furthermore the prospect of up to 80 core CPUs have already been announced by Intel, so things will be getting better (or worse depending on how you look at it). So if we can leverage this trend in ever increasing processor cores, provide a certain level of location transparency through processor emulation, this will be a big win for computational science in general. =20 I know valgrind is more then a processor emulator, unlike QEMU and QuickTransit. But unlike QuickTransit, Valgrind is open-source, and unlike QEMU, Valgrind is more efficient. =20 It's not absolutely critical that I pick the fastest platform for my research, but being in HPC, it's a lot easier to convince my colleagues if real performance gains can be seen fairly quickly. =20 Sorry if I did not convey all this information in my previous email. Email is sometimes not the best vehicle to convey complex motivation. =20 >> Sure. I'm in an area where I hear that comment quite often: "this >> application can't be parallelized". >I didn't say that. Sorry. I didn't mean to misinterpret your statement.=20 - Ed |
|
From: Tom H. <th...@cy...> - 2006-10-07 02:25:30
|
Nightly build on dellow ( x86_64, Fedora Core 5 ) started at 2006-10-07 03:10:04 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 274 tests, 20 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_creat (stderr) none/tests/fdleak_dup (stderr) none/tests/fdleak_dup2 (stderr) none/tests/fdleak_fcntl (stderr) none/tests/fdleak_ipv4 (stderr) none/tests/fdleak_open (stderr) none/tests/fdleak_pipe (stderr) none/tests/fdleak_socketpair (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/rlimit_nofile (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 268 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_creat (stderr) none/tests/fdleak_dup (stderr) none/tests/fdleak_dup2 (stderr) none/tests/fdleak_fcntl (stderr) none/tests/fdleak_ipv4 (stderr) none/tests/fdleak_open (stderr) none/tests/fdleak_pipe (stderr) none/tests/fdleak_socketpair (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/rlimit_nofile (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 03:17:43 2006 --- new.short Sat Oct 7 03:25:26 2006 *************** *** 8,10 **** ! == 268 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,16 ---- ! == 274 tests, 20 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/leak-pool-0 (stderr) ! memcheck/tests/leak-pool-1 (stderr) ! memcheck/tests/leak-pool-2 (stderr) ! memcheck/tests/leak-pool-3 (stderr) ! memcheck/tests/leak-pool-4 (stderr) ! memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) |
|
From: Tom H. <th...@cy...> - 2006-10-07 02:24:37
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-10-07 03:15:02 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccPn817T.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccPn817T.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.4088/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.4088/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccGhPZmw.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccGhPZmw.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.4088/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.4088/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.4088/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 03:19:47 2006 --- new.short Sat Oct 7 03:24:32 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccGhPZmw.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccGhPZmw.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 --- 7,16 ---- Last 20 lines of verbose log follow echo ! /tmp/ccPn817T.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccPn817T.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-10-07 02:20:14
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-10-07 03:05:05 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 274 tests, 12 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 268 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Oct 7 03:12:44 2006 --- new.short Sat Oct 7 03:20:00 2006 *************** *** 8,10 **** ! == 268 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leakotron (stdout) --- 8,16 ---- ! == 274 tests, 12 stderr failures, 2 stdout failures, 0 posttest failures == ! memcheck/tests/leak-pool-0 (stderr) ! memcheck/tests/leak-pool-1 (stderr) ! memcheck/tests/leak-pool-2 (stderr) ! memcheck/tests/leak-pool-3 (stderr) ! memcheck/tests/leak-pool-4 (stderr) ! memcheck/tests/leak-pool-5 (stderr) memcheck/tests/leakotron (stdout) |
|
From: Nicholas N. <nj...@cs...> - 2006-10-07 01:43:04
|
On Fri, 6 Oct 2006, Edward Walker wrote: >>> I'm researching ways of adding speculative (or non-speculative) >>> parallelism into the translation-run component in Valgrind. >> >> Can I ask what is the motivation for this? I'm curious... > > The motivation is actually pretty simple: performance. I'm > investigating alternative BB issue techniques and methods for breaking > input/output/anti dependencies. The pervasiveness of multi-core makes > this very relevant and speculative thread speculation is just _one_ > possible technique which enables this. So you're trying to make Valgrind go faster, or dynamic binary translation systems in general? >> I don't think you're doing something trivially stupid, rather something >> that Valgrind is not at all designed to handle. Valgrind's execution is >> deliberately serialised, for reasons described in the first paragraph of >> section 2.3.9 in http://www.valgrind.org/docs/phd2004.pdf. I'm surprised >> it ran successfully for as long as it did. > > Sure. I'm in an area where I hear that comment quite often: "this > application can't be parallelized". I didn't say that. > Just curious if you have any ideas as to where this stack exception > could be coming from? Any help would be greatly appreciated. I don't > have this problem if I do it in QEMU for example, but valgrind makes for > a better platform to start from because of its more efficient > implementation. Alternatively, I'll be moving back to QEMU if this is > just not possible. I don't know. Others might. Nick |
|
From: Edward W. <ew...@ta...> - 2006-10-07 00:13:53
|
>> >> I'm researching ways of adding speculative (or non-speculative) >> parallelism into the translation-run component in Valgrind. > >Can I ask what is the motivation for this? I'm curious... The motivation is actually pretty simple: performance. I'm investigating alternative BB issue techniques and methods for breaking input/output/anti dependencies. The pervasiveness of multi-core makes this very relevant and speculative thread speculation is just _one_ possible technique which enables this. > I don't think you're doing something trivially stupid, rather something that=20 > Valgrind is not at all designed to handle. Valgrind's execution is=20 > deliberately serialised, for reasons described in the first paragraph of=20 > section 2.3.9 in http://www.valgrind.org/docs/phd2004.pdf. I'm surprised it=20 > ran successfully for as long as it did. Sure. I'm in an area where I hear that comment quite often: "this application can't be parallelized". That's often not true if we can identify all the data dependencies, and investigate novel issuing techniques that can break those dependencies. Just curious if you have any ideas as to where this stack exception could be coming from? Any help would be greatly appreciated. I don't have this problem if I do it in QEMU for example, but valgrind makes for a better platform to start from because of its more efficient implementation. Alternatively, I'll be moving back to QEMU if this is just not possible. Many thanks in advance, Ed |