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
(32) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(11) |
2
(8) |
|
3
(8) |
4
(8) |
5
(8) |
6
(19) |
7
(17) |
8
(12) |
9
(10) |
|
10
(15) |
11
(18) |
12
(14) |
13
(16) |
14
(24) |
15
(16) |
16
(12) |
|
17
(25) |
18
(23) |
19
(12) |
20
(10) |
21
(9) |
22
(12) |
23
(13) |
|
24
(19) |
25
(7) |
26
(39) |
27
(22) |
28
(22) |
29
(16) |
30
(13) |
|
31
(23) |
|
|
|
|
|
|
|
From: Tom H. <to...@co...> - 2006-12-10 03:53:30
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-10 03:30:07 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 252 tests, 8 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) |
|
From: <sv...@va...> - 2006-12-10 02:59:18
|
Author: sewardj Date: 2006-12-10 02:59:16 +0000 (Sun, 10 Dec 2006) New Revision: 6389 Log: Fix 'make html-docs' and 'make print-docs'. Modified: trunk/cachegrind/docs/cg-manual.xml trunk/docs/xml/manual-writing-tools.xml trunk/docs/xml/tech-docs.xml Modified: trunk/cachegrind/docs/cg-manual.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/cachegrind/docs/cg-manual.xml 2006-12-10 02:58:27 UTC (rev 6388= ) +++ trunk/cachegrind/docs/cg-manual.xml 2006-12-10 02:59:16 UTC (rev 6389= ) @@ -1,6 +1,7 @@ <?xml version=3D"1.0"?> <!-- -*- sgml -*- --> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" - "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> + "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" +[ <!ENTITY % vg-entities SYSTEM "../../docs/xml/vg-entities.xml"> %vg-en= tities; ]> =20 =20 <chapter id=3D"cg-manual" xreflabel=3D"Cachegrind: a cache-miss profiler= "> Modified: trunk/docs/xml/manual-writing-tools.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/xml/manual-writing-tools.xml 2006-12-10 02:58:27 UTC (rev = 6388) +++ trunk/docs/xml/manual-writing-tools.xml 2006-12-10 02:59:16 UTC (rev = 6389) @@ -198,7 +198,7 @@ <computeroutput>VG_DETERMINE_INTERFACE_VERSION</computeroutput> (which a= lso checks that the core/tool interface of the tool matches that of the core= ). The last three are registered using the -<computeroutput>VG_(basic_tool_funcs)</computeroutput> function. +<computeroutput>VG_(basic_tool_funcs)</computeroutput> function.</para> =20 <para>In addition, if a tool wants to use some of the optional services provided by the core, it may have to define other functions and tell the Modified: trunk/docs/xml/tech-docs.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/xml/tech-docs.xml 2006-12-10 02:58:27 UTC (rev 6388) +++ trunk/docs/xml/tech-docs.xml 2006-12-10 02:59:16 UTC (rev 6389) @@ -21,7 +21,7 @@ xmlns:xi=3D"http://www.w3.org/2001/XInclude" /> <xi:include href=3D"../../callgrind/docs/cl-format.xml" parse=3D"xml" = =20 xmlns:xi=3D"http://www.w3.org/2001/XInclude" /> - <xi:include href=3D"writing-tools.xml" parse=3D"xml" =20 + <xi:include href=3D"manual-writing-tools.xml" parse=3D"xml" =20 xmlns:xi=3D"http://www.w3.org/2001/XInclude" /> =20 </book> |
|
From: <sv...@va...> - 2006-12-10 02:58:30
|
Author: sewardj Date: 2006-12-10 02:58:27 +0000 (Sun, 10 Dec 2006) New Revision: 6388 Log: Update. Modified: trunk/docs/README Modified: trunk/docs/README =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/README 2006-12-10 02:26:50 UTC (rev 6387) +++ trunk/docs/README 2006-12-10 02:58:27 UTC (rev 6388) @@ -119,7 +119,16 @@ in recent distros. =20 =20 +Notes [Dec. 2006] +----------------- +pdfxmltex still bombs when building the print docs. On SuSE 10.1 I +edited /etc/texmf/web2c/texmf.cnf and changed + pool_size.pdfxmltex =3D 500000 +to + pool_size.pdfxmltex =3D 1500000 +and that fixes it. =20 + Notes [Nov. 2005] ----------------- After upgrading to Suse 10, found a (known) bug in PassiveTex which=20 |
|
From: <sv...@va...> - 2006-12-10 02:26:55
|
Author: sewardj Date: 2006-12-10 02:26:50 +0000 (Sun, 10 Dec 2006) New Revision: 6387 Log: Fix installation of libmpiwrap.so on the primary platform. Modified: trunk/auxprogs/Makefile.am Modified: trunk/auxprogs/Makefile.am =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/auxprogs/Makefile.am 2006-12-08 21:29:46 UTC (rev 6386) +++ trunk/auxprogs/Makefile.am 2006-12-10 02:26:50 UTC (rev 6387) @@ -87,7 +87,7 @@ # convert (eg) X86_LINUX to x86-linux # really should use sed here, rather than assume tr is available pD=3D`echo @VG_PLATFORM_PRI@ | tr A-Z_ a-z-` ; \ - $(mkinstalldirs) $(DESTDIR)$(valdir)/$$pD; + $(mkinstalldirs) $(DESTDIR)$(valdir)/$$pD; \ rm -f ./libmpiwrap.so; \ cp ./libmpiwrap-@VG_PLATFORM_PRI@.so ./libmpiwrap.so; \ $(INSTALL_PROGRAM) ./libmpiwrap.so \ |
|
From: <js...@ac...> - 2006-12-10 01:16:37
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2006-12-10 02:00:01 CET Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 221 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) 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/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-int (stdout) none/tests/ppc64/jm-int (stdout) |
|
From: Julian S. <js...@ac...> - 2006-12-09 17:10:31
|
> As promised I have reworked the integration of drd into Valgrind such > that the number of core changes is now minimal. Good. > - Data-race analysis for regular POSIX threads (non-detached POSIX > threads) can only be performed once pthread_join() finished. Can you clarify what this means? I thought that as soon as a=20 segment is finished, it can be checked against all other finished segments which are unordered relative to it. > The patch: > http://home.euphonynet.be/bvassche/valgrind/valgrind-6386-drd-2006-12-09.= pa >tch.gz How to apply the patch: gzcat valgrind-6386-drd-2006-12-09.patch.gz= | > patch -p0 (don't forget the -p0 !) > > Can the proposed core changes please be reviewed/commented ? I had a brief look just now. I'll look in more detail in the week. One problem is it's a huge patch, with 3 components: new drd/ stuff, coregrind/ changes, and removal of m_{p}threadmodel.c. =2D----- When inspecting drd code before I think I saw what might be a bug. =46rom memory: Suppose thread T1 releases a lock L and some time later thread T2 acquires L. I think what drd does when T2 gets the lock is to set T2's vector clock to union(T2's current vector clock, T1's=20 current vector clock). This seemed wrong to me -- shouldn't it use the=20 vector clock from T1 at the point T1 released the lock? In other words,=20 shouldn't locks have an associated vector clock saying when they were most recently unlocked? J |
|
From: Bart V. A. <bar...@gm...> - 2006-12-09 10:59:20
|
As promised I have reworked the integration of drd into Valgrind such that the number of core changes is now minimal. A few comments on the remaining core changes (for the location of the patch, see below): - I have removed all tracking functions from the interface between the core and the tools that were never called by the core (track_post_thread_join and the mutex-related tracking functions). - The following infrastructure has been added for tracking detached POSIX threads: * A new boolean state has been added to ThreadState, called joinable. Its default value is false, but this value can be changed from the client via a client request. * One new tracking function has been added: track_detached_thread_finished. This tracking function is called after a client thread finished. - Data-race analysis for regular POSIX threads (non-detached POSIX threads) can only be performed once pthread_join() finished. I had to modify the thread state machine in order to avoid that the core reuses thread ID's after a client thread finishes and before pthread_join() finished. This works as follows: * drd ensures that joinable threads finish with ThreadState::joinable == true. * the thread state machine in the core has been modified such that if a thread finishes with ThreadState::joinable == true, then the transition of the thread state from VgTs_Zombie into VgTs_empty is deferred until the client triggers a call to the new function VG_(join_thread). All this last function does is changing the thread state into VgTs_Empty. - One non-essential but nice-to-have feature I added is that clients can now associate a name with each thread. I already use this thread name instead of the thread number for drd's error reporting (client request VG_USERREQ__SET_THREAD_NAME, core functions VG_(get_thread_name) and VG_(set_thread_name)). Maybe it is a good idea to let memcheck also print these thread names in its error reports. The patch: http://home.euphonynet.be/bvassche/valgrind/valgrind-6386-drd-2006-12-09.patch.gz How to apply the patch: gzcat valgrind-6386-drd-2006-12-09.patch.gz | patch -p0 (don't forget the -p0 !) Can the proposed core changes please be reviewed/commented ? Bart. |
|
From: <js...@ac...> - 2006-12-09 05:03:50
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-12-09 04:30:01 GMT 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 == 250 tests, 9 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (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 == 250 tests, 9 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Dec 9 04:47:54 2006 --- new.short Sat Dec 9 05:03:48 2006 *************** *** 10,12 **** ! == 250 tests, 9 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) --- 10,12 ---- ! == 250 tests, 9 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) *************** *** 21,23 **** none/tests/mremap2 (stdout) - none/tests/pth_detached (stdout) --- 21,22 ---- |
|
From: <js...@ac...> - 2006-12-09 04:33:43
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-12-09 09:00:01 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 215 tests, 12 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/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (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) |
|
From: Tom H. <to...@co...> - 2006-12-09 03:47:27
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-09 03:30:06 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 252 tests, 8 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-09 03:24:54
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-12-09 03:00:01 GMT 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 == 282 tests, 15 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/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_fcntl (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 == 282 tests, 15 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/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (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 Dec 9 03:13:28 2006 --- new.short Sat Dec 9 03:24:22 2006 *************** *** 8,10 **** ! == 282 tests, 15 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) --- 8,10 ---- ! == 282 tests, 15 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) *************** *** 25,27 **** none/tests/mremap2 (stdout) - none/tests/tls (stdout) --- 25,26 ---- |
|
From: Tom H. <th...@cy...> - 2006-12-09 03:23:46
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-12-09 03:15:01 GMT 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/ccliJhQ1.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccliJhQ1.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.8652/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.8652/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.8652/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.8652/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.8652/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/ccRmbePu.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccRmbePu.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.8652/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.8652/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.8652/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.8652/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.8652/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat Dec 9 03:18:50 2006 --- new.short Sat Dec 9 03:23:16 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccRmbePu.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccRmbePu.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/ccliJhQ1.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccliJhQ1.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-12-09 03:23:30
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2006-12-09 03:10:02 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 280 tests, 13 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/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-09 03:18:10
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-12-09 03:05:09 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 280 tests, 14 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/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: <js...@ac...> - 2006-12-09 01:40:43
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2006-12-09 02:00:01 CET Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 221 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) 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/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-int (stdout) none/tests/ppc64/jm-int (stdout) |
|
From: <sv...@va...> - 2006-12-08 21:29:50
|
Author: sewardj
Date: 2006-12-08 21:29:46 +0000 (Fri, 08 Dec 2006)
New Revision: 6386
Log:
Get rid of the use of explicit register variables in the ppc32-linux
magic macros.
Modified:
trunk/include/valgrind.h
Modified: trunk/include/valgrind.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/include/valgrind.h 2006-12-07 15:34:04 UTC (rev 6385)
+++ trunk/include/valgrind.h 2006-12-08 21:29:46 UTC (rev 6386)
@@ -299,8 +299,8 @@
_zzq_arg1, _zzq_arg2, _zzq_arg3, _zzq_arg4, _zzq_arg5) \
\
{ unsigned int _zzq_args[6]; \
- register unsigned int _zzq_result __asm__("r3"); \
- register unsigned int* _zzq_ptr __asm__("r4"); \
+ unsigned int _zzq_result; \
+ unsigned int* _zzq_ptr; \
_zzq_args[0] =3D (unsigned int)(_zzq_request); \
_zzq_args[1] =3D (unsigned int)(_zzq_arg1); \
_zzq_args[2] =3D (unsigned int)(_zzq_arg2); \
@@ -308,24 +308,28 @@
_zzq_args[4] =3D (unsigned int)(_zzq_arg4); \
_zzq_args[5] =3D (unsigned int)(_zzq_arg5); \
_zzq_ptr =3D _zzq_args; \
- __asm__ volatile(__SPECIAL_INSTRUCTION_PREAMBLE \
+ __asm__ volatile("mr 3,%1\n\t" /*default*/ \
+ "mr 4,%2\n\t" /*ptr*/ \
+ __SPECIAL_INSTRUCTION_PREAMBLE \
/* %R3 =3D client_request ( %R4 ) */ \
- "or 1,1,1" \
- : "=3Dr" (_zzq_result) \
- : "0" (_zzq_default), "r" (_zzq_ptr) \
- : "cc", "memory"); \
+ "or 1,1,1\n\t" \
+ "mr %0,3" /*result*/ \
+ : "=3Db" (_zzq_result) \
+ : "b" (_zzq_default), "b" (_zzq_ptr) \
+ : "cc", "memory", "r3", "r4"); \
_zzq_rlval =3D _zzq_result; \
}
=20
#define VALGRIND_GET_NR_CONTEXT(_zzq_rlval) \
{ volatile OrigFn* _zzq_orig =3D &(_zzq_rlval); \
- register unsigned int __addr __asm__("r3"); \
+ unsigned int __addr; \
__asm__ volatile(__SPECIAL_INSTRUCTION_PREAMBLE \
/* %R3 =3D guest_NRADDR */ \
- "or 2,2,2" \
- : "=3Dr" (__addr) \
+ "or 2,2,2\n\t" \
+ "mr %0,3" \
+ : "=3Db" (__addr) \
: \
- : "cc", "memory" \
+ : "cc", "memory", "r3" \
); \
_zzq_orig->nraddr =3D __addr; \
}
|
|
From: Julian S. <js...@ac...> - 2006-12-08 13:16:37
|
> > I even hope to reduce the amount of code in the core if we can. > > Specifically, are m_threadmodel.c and m_pthreadmodel.c really necessary? > > I don't think they are used at present and if not we should delete > > them and/or move drd-required parts into drd/. > > Regarding the core changes I proposed, I'll move them as much as > possible to the drd tool. Great. You should understand that I'm not unsympathetic to the split you proposed. But a permanent background problem is the complexity and maintainability of the core -- in the past we have gotten into some serious difficulties with that. > And about m_threadmodel.c and > m_pthreadmodel.c: as far as I know the code in these files is not used > by any tool. Ok, these should then be removed. They can of course be brought back (or parts of them) from source control if we need them later. > The presence of this code was confusing for me when I > tried to understand how Valgrind handles threads, since I was > searching through the code with grep. Yes. I think this is a historical artefact left over from development of Helgrind. J |
|
From: Bart V. A. <bar...@gm...> - 2006-12-08 13:00:34
|
On 12/8/06, Julian Seward <js...@ac...> wrote: > > > Maybe I can keep the wrappers for pthread_create()/pthread_join() in > > vg_preloaded.c, and move the other wrappers to a drd/... file ? > > I see what you're saying, but I still prefer all the wrappers to be > drd-specific. The real reason is that there is already an overwhelming > level of complexity in coregrind/, and I am reluctant to add more, > especially considering that at the moment we do not have any other > tools which require to see thread create/exit events. > > I even hope to reduce the amount of code in the core if we can. > Specifically, are m_threadmodel.c and m_pthreadmodel.c really necessary? > I don't think they are used at present and if not we should delete > them and/or move drd-required parts into drd/. Regarding the core changes I proposed, I'll move them as much as possible to the drd tool. And about m_threadmodel.c and m_pthreadmodel.c: as far as I know the code in these files is not used by any tool. The presence of this code was confusing for me when I tried to understand how Valgrind handles threads, since I was searching through the code with grep. I propose to remove these two source files from the Valgrind source tree. Bart. |
|
From: Julian S. <js...@ac...> - 2006-12-08 12:10:39
|
> Maybe I can keep the wrappers for pthread_create()/pthread_join() in > vg_preloaded.c, and move the other wrappers to a drd/... file ? I see what you're saying, but I still prefer all the wrappers to be drd-specific. The real reason is that there is already an overwhelming level of complexity in coregrind/, and I am reluctant to add more, especially considering that at the moment we do not have any other tools which require to see thread create/exit events. I even hope to reduce the amount of code in the core if we can. Specifically, are m_threadmodel.c and m_pthreadmodel.c really necessary? I don't think they are used at present and if not we should delete them and/or move drd-required parts into drd/. J |
|
From: <js...@ac...> - 2006-12-08 05:03:44
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-12-08 04:30:01 GMT 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 == 250 tests, 9 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: <js...@ac...> - 2006-12-08 04:29:17
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-12-08 09:00:02 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 215 tests, 12 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/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (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) |
|
From: Tom H. <to...@co...> - 2006-12-08 03:47:48
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-08 03:30:06 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 252 tests, 8 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-08 03:24:10
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-12-08 03:15:03 GMT 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/ccIqLEcw.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccIqLEcw.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.23773/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.23773/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.23773/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.23773/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.23773/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/ccME7iDv.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccME7iDv.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.23773/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.23773/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.23773/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.23773/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.23773/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Dec 8 03:19:35 2006 --- new.short Fri Dec 8 03:23:55 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccME7iDv.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccME7iDv.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/ccIqLEcw.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccIqLEcw.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-12-08 03:23:30
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2006-12-08 03:10:03 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 280 tests, 13 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/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-08 03:17:58
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-12-08 03:05:05 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 280 tests, 14 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/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |