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
(20) |
2
(10) |
3
(18) |
4
(10) |
5
(16) |
6
(8) |
|
7
|
8
(17) |
9
(22) |
10
(10) |
11
(9) |
12
(21) |
13
(15) |
|
14
(10) |
15
(11) |
16
(9) |
17
(13) |
18
(9) |
19
(11) |
20
(11) |
|
21
(23) |
22
(20) |
23
(10) |
24
(11) |
25
(20) |
26
(20) |
27
(21) |
|
28
(8) |
29
(7) |
30
(7) |
31
(9) |
|
|
|
|
From: Tom H. <th...@cy...> - 2006-05-27 02:30:17
|
Nightly build on ginetta ( i686, Red Hat 8.0 ) started at 2006-05-27 03:10:02 BST 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 == 236 tests, 6 stderr failures, 0 stdout failures, 0 posttest failures == 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) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-05-27 02:22:24
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2006-05-27 03:05:08 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 == 260 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leakotron (stdout) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (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 == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sat May 27 03:13:43 2006 --- new.short Sat May 27 03:22:03 2006 *************** *** 8,10 **** ! == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) --- 8,11 ---- ! == 260 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/leakotron (stdout) memcheck/tests/stack_switch (stderr) |
|
From: Julian S. <js...@ac...> - 2006-05-26 20:56:58
|
> See attached patch; Julian: may I commit it now or later? I prefer that we fix all known stability problems before release, so I guess commit now. How well is this change tested? Are you able to test on ppc? J |
|
From: Josef W. <Jos...@gm...> - 2006-05-26 18:18:42
|
On Friday 26 May 2006 01:22, Julian Seward wrote:
> Naturally, if there is any critical breakage that should be fixed
> before 3.2.0, please shout now.
I have an important bug fix for callgrind here to close 4 bug reports
(privately by mail): Callgrind fails with an assertion failure when
reinstrumenting rep or cmov instructions (e.g. because of plugin reloading).
Since some time I was not able to reproduce it, as it happened only with big
programs.
See attached patch; Julian: may I commit it now or later?
Josef
==
Fix a failed assertion on retranslation of rep or cmov instructions.
Bug description: Very similar to cachegrind, callgrind stores
metainformation per guest instruction; this meta information is
given when calling into the simulator. In contrast to cachegrind,
callgrind keeps this info when the source is discarded, and checks
on retranslation whether the same meta info is generated.
This check sometimes fails: E.g. for rep x86 instructions, 2 simulator calls
are usually generated for one x86 instruction (the instruction fetch and a
data access), thus overwriting the data_size meta information for one x86
instruction first with 0, and afterwards e.g. with 1. The check on retranslation
fails because of this. The fix is to only write/check data_size values >0.
===================================================================
--- bb.c (Revision 5933)
+++ bb.c (Arbeitskopie)
@@ -120,16 +120,17 @@
UInt instr_count, UInt cjmp_count, Bool cjmp_inverted)
{
BB* new;
- UInt new_idx;
+ UInt new_idx, size;
/* check fill degree of bb hash table and resize if needed (>80%) */
bbs.entries++;
if (10 * bbs.entries / bbs.size > 8)
resize_bb_table();
- new = (BB*) CLG_MALLOC(sizeof(BB) +
- instr_count * sizeof(InstrInfo) +
- (cjmp_count+1) * sizeof(CJmpInfo));
+ size = sizeof(BB) + instr_count * sizeof(InstrInfo)
+ + (cjmp_count+1) * sizeof(CJmpInfo);
+ new = (BB*) CLG_MALLOC(size);
+ VG_(memset)(new, 0, size);
new->obj = obj;
new->offset = offset;
Index: main.c
===================================================================
--- main.c (Revision 5933)
+++ main.c (Arbeitskopie)
@@ -272,29 +272,44 @@
es = insert_simcall(bbOut, ii, dataSize, instrIssued,
loadAddrExpr, storeAddrExpr);
+ CLG_DEBUG(5, " Instr +%2d (Size %d, DSize %d): ESet %s (Size %d)\n",
+ instr_offset, instrLen, dataSize,
+ es ? es->name : (Char*)"(no instrumentation)",
+ es ? es->size : 0);
+
if (bb_seen_before) {
+ CLG_DEBUG(5, " before: Instr +%2d (Size %d, DSize %d)\n",
+ ii->instr_offset, ii->instr_size, ii->data_size);
+
CLG_ASSERT(ii->instr_offset == instr_offset);
CLG_ASSERT(ii->instr_size == instrLen);
- CLG_ASSERT(ii->data_size == dataSize);
CLG_ASSERT(ii->cost_offset == *cost_offset);
CLG_ASSERT(ii->eventset == es);
+
+ /* Only check size if data size >0.
+ * This is needed: e.g. for rep or cmov x86 instructions, the same InstrInfo
+ * is used both for 2 simulator calls: for the pure instruction fetch and
+ * separately for an memory access (which may not happen depending on flags).
+ * If checked always, this triggers an assertion failure on retranslation.
+ */
+ if (dataSize>0) CLG_ASSERT(ii->data_size == dataSize);
+
}
else {
ii->instr_offset = instr_offset;
ii->instr_size = instrLen;
- ii->data_size = dataSize;
ii->cost_offset = *cost_offset;
ii->eventset = es;
+
+ /* data size only relevant if >0 */
+ if (dataSize > 0) ii->data_size = dataSize;
+
CLG_(stat).distinct_instrs++;
}
*cost_offset += es ? es->size : 0;
- CLG_DEBUG(5, " Instr +%2d (Size %d, DSize %d): ESet %s (Size %d)\n",
- instr_offset, instrLen, dataSize,
- es ? es->name : (Char*)"(no Instr)",
- es ? es->size : 0);
}
|
|
From: <sv...@va...> - 2006-05-26 16:06:25
|
Author: sewardj Date: 2006-05-26 17:06:10 +0100 (Fri, 26 May 2006) New Revision: 5938 Log: Wording wibble. Modified: trunk/NEWS Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/NEWS 2006-05-26 13:51:37 UTC (rev 5937) +++ trunk/NEWS 2006-05-26 16:06:10 UTC (rev 5938) @@ -9,8 +9,8 @@ removed, Callgrind has been added, PPC64/Linux support has been added, Lackey has been improved, and MPI support has been added. In detail: =20 -- Memcheck has improved speed and reduced memory use. Programs - typically run 20-40% faster, averaging about 30% for SPEC CPU2000. +- Memcheck has improved speed and reduced memory use. Run times are + typically reduced by 15-30%, averaging about 24% for SPEC CPU2000. The other tools have smaller but noticeable speed improvments. We are interested to hear what improvements users get. =20 @@ -156,7 +156,7 @@ 126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624 126938 bad checking for syscalls linkat, renameat, symlinkat =20 -(3.2.0RC1: 26 May 2006, vex r1626, valgrind r5937). +(3.2.0RC1: 26 May 2006, vex r1626, valgrind r5938). =20 =20 Release 3.1.1 (15 March 2006) |
|
From: <js...@ac...> - 2006-05-26 15:34:49
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-05-26 16:00:02 BST 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 == 206 tests, 11 stderr failures, 5 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) 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: <sv...@va...> - 2006-05-26 13:51:42
|
Author: sewardj Date: 2006-05-26 14:51:37 +0100 (Fri, 26 May 2006) New Revision: 5937 Log: 3.2.0rc1, hopefully. Modified: trunk/NEWS trunk/configure.in Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/NEWS 2006-05-26 12:00:26 UTC (rev 5936) +++ trunk/NEWS 2006-05-26 13:51:37 UTC (rev 5937) @@ -5,21 +5,20 @@ usual collection of bug fixes. This release supports X86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux. =20 -Performance, especially of Memcheck, is much improved, Addrcheck has -been removed, Callgrind has been added, PPC64/Linux support has been -added, Lackey has been improved, and MPI support has been added. In -detail: +Performance, especially of Memcheck, is improved, Addrcheck has been +removed, Callgrind has been added, PPC64/Linux support has been added, +Lackey has been improved, and MPI support has been added. In detail: =20 - Memcheck has improved speed and reduced memory use. Programs typically run 20-40% faster, averaging about 30% for SPEC CPU2000. - There are smaller but noticeable speed improvements for the other - tools. We are interested to hear what improvements users get. + The other tools have smaller but noticeable speed improvments. We + are interested to hear what improvements users get. =20 Memcheck uses less memory, due to the introduction of a compressed - representation for Memcheck's shadow memory. The space overhead has - been reduced by a factor of more than four on most programs. This - means you should be able to run programs that use more memory than - before without hitting problems. + representation for shadow memory. The space overhead has been + reduced by a factor of up to four, depending on program behaviour. + This means you should be able to run programs that use more memory + than before without hitting problems. =20 - Addrcheck has been removed. It has not worked since version 2.4.0, and the speed and memory improvements to Memcheck make it redundant. @@ -27,13 +26,14 @@ errors, you can use the new Memcheck option --undef-value-errors=3Dno to get the same behaviour. =20 -- Further reduced rates of incorrectly reported undefined-value-errors - in Memcheck (it was already very low). In particular, efforts have - been made to ensure Memcheck works really well with gcc - 4.0/4.1-generated code on X86/Linux and AMD64/Linux. +- The number of undefined-value errors incorrectly reported by + Memcheck has been reduced (such false reports were already very + rare). In particular, efforts have been made to ensure Memcheck + works really well with gcc 4.0/4.1-generated code on X86/Linux and + AMD64/Linux. =20 - Josef Weidendorfer's popular Callgrind tool has been added. Folding - it in is in a logical step given its popularity and usefulness, and + it in was a logical step given its popularity and usefulness, and makes it easier for us to ensure it works "out of the box" on all supported targets. The associated KDE KCachegrind GUI remains a separate project. @@ -156,7 +156,7 @@ 126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624 126938 bad checking for syscalls linkat, renameat, symlinkat =20 -(3.2.0: ?? May 2006, vex r??, valgrind r??) +(3.2.0RC1: 26 May 2006, vex r1626, valgrind r5937). =20 =20 Release 3.1.1 (15 March 2006) Modified: trunk/configure.in =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/configure.in 2006-05-26 12:00:26 UTC (rev 5936) +++ trunk/configure.in 2006-05-26 13:51:37 UTC (rev 5937) @@ -8,7 +8,7 @@ ##------------------------------------------------------------## =20 # Process this file with autoconf to produce a configure script. -AC_INIT(Valgrind, 3.2.0.SVN, val...@li...) +AC_INIT(Valgrind, 3.2.0rc1, val...@li...) AC_CONFIG_SRCDIR(coregrind/m_main.c) AM_CONFIG_HEADER(config.h) AM_INIT_AUTOMAKE |
|
From: <sv...@va...> - 2006-05-26 12:00:44
|
Author: sewardj
Date: 2006-05-26 13:00:26 +0100 (Fri, 26 May 2006)
New Revision: 5936
Log:
Sigh .. now fix for 32-bit targets.
Modified:
trunk/memcheck/tests/sh-mem.c
Modified: trunk/memcheck/tests/sh-mem.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/memcheck/tests/sh-mem.c 2006-05-26 11:31:15 UTC (rev 5935)
+++ trunk/memcheck/tests/sh-mem.c 2006-05-26 12:00:26 UTC (rev 5936)
@@ -141,7 +141,7 @@
Ty* aNb =3D (Ty*)(((U1*)aN) + h); /* set offset from a[] */ \
Ty* bNb =3D (Ty*)(((U1*)bN) + h); /* set offset from b[] */ \
\
- fprintf(stderr, "h =3D %d (checking %d..%ld) ", h, h, n-NNN+h); =
\
+ fprintf(stderr, "h =3D %d (checking %d..%d) ", h, h, (int)(n-NNN=
+h)); \
\
/* For each of the 256 possible V byte values... */ \
for (j =3D 0; j < 256; j++) { \
|
|
From: <sv...@va...> - 2006-05-26 11:31:23
|
Author: sewardj
Date: 2006-05-26 12:31:15 +0100 (Fri, 26 May 2006)
New Revision: 5935
Log:
Replace the obviously-bogus piece of inline asm with a probably
equally bogus new version. In fact if I actually understood the
magical "earlyclobber" (&) asm constraint this would probably be
unnecessary, but I don't. Ah well.
Modified:
trunk/coregrind/m_debuglog.c
Modified: trunk/coregrind/m_debuglog.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_debuglog.c 2006-05-26 11:29:17 UTC (rev 5934)
+++ trunk/coregrind/m_debuglog.c 2006-05-26 11:31:15 UTC (rev 5935)
@@ -98,23 +98,33 @@
}
=20
#elif defined(VGP_amd64_linux)
-
+__attribute__((noinline))
static UInt local_sys_write_stderr ( HChar* buf, Int n )
{
- UInt __res;
+ Long block[2];
+ block[0] =3D (Long)buf;
+ block[1] =3D n;
__asm__ volatile (
- "movq $1, %%rax\n" /* set %rax =3D __NR_write */
- "movq $2, %%rdi\n" /* set %rdi =3D stderr */
- "movq %1, %%rsi\n" /* set %rsi =3D buf */
- "movl %2, %%edx\n" /* set %edx =3D n */
- "syscall\n" /* write(stderr, buf, n) */
- "movl %%eax, %0\n" /* set __res =3D %eax */
- : "=3Dmr" (__res)
- : "g" (buf), "g" (n)
- : "rax", "rdi", "rsi", "rdx" );
- if (__res < 0)=20
- __res =3D -1;
- return __res;
+ "subq $256, %%rsp\n" /* don't trash the stack redzone */
+ "pushq %%r15\n" /* r15 is callee-save */
+ "movq %0, %%r15\n" /* r15 =3D &block */
+ "pushq %%r15\n" /* save &block */
+ "movq $1, %%rax\n" /* rax =3D __NR_write */
+ "movq $2, %%rdi\n" /* rdi =3D stderr */
+ "movq 0(%%r15), %%rsi\n" /* rsi =3D buf */
+ "movq 8(%%r15), %%rdx\n" /* rdx =3D n */
+ "syscall\n" /* write(stderr, buf, n) */
+ "popq %%r15\n" /* reestablish &block */
+ "movq %%rax, 0(%%r15)\n" /* block[0] =3D result */
+ "popq %%r15\n" /* restore r15 */
+ "addq $256, %%rsp\n" /* restore stack ptr */
+ : /*wr*/
+ : /*rd*/ "g" (block)
+ : /*trash*/ "rax", "rdi", "rsi", "rdx", "memory", "cc"
+ );
+ if (block[0] < 0)=20
+ block[0] =3D -1;
+ return (UInt)block[0];
}
=20
static UInt local_sys_getpid ( void )
|
|
From: <sv...@va...> - 2006-05-26 11:29:27
|
Author: sewardj
Date: 2006-05-26 12:29:17 +0100 (Fri, 26 May 2006)
New Revision: 5934
Log:
Fix gcc pedantry on 64-bit platforms
Modified:
trunk/memcheck/tests/sh-mem.c
Modified: trunk/memcheck/tests/sh-mem.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/memcheck/tests/sh-mem.c 2006-05-26 00:50:41 UTC (rev 5933)
+++ trunk/memcheck/tests/sh-mem.c 2006-05-26 11:29:17 UTC (rev 5934)
@@ -141,7 +141,7 @@
Ty* aNb =3D (Ty*)(((U1*)aN) + h); /* set offset from a[] */ \
Ty* bNb =3D (Ty*)(((U1*)bN) + h); /* set offset from b[] */ \
\
- fprintf(stderr, "h =3D %d (checking %d..%d) ", h, h, n-NNN+h); \
+ fprintf(stderr, "h =3D %d (checking %d..%ld) ", h, h, n-NNN+h); =
\
\
/* For each of the 256 possible V byte values... */ \
for (j =3D 0; j < 256; j++) { \
|
|
From: <js...@ac...> - 2006-05-26 03:09:36
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-05-26 03:30:05 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 == 235 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) ================================================= == 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 == 237 tests, 6 stderr failures, 0 stdout failures, 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/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:50:54 2006 --- new.short Fri May 26 04:09:20 2006 *************** *** 10,12 **** ! == 237 tests, 6 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 10,12 ---- ! == 235 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) *************** *** 15,18 **** memcheck/tests/x86/scalar_supp (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 15,16 ---- |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:58:49
|
Nightly build on ford ( i686, Fedora Core 4 ) started at 2006-05-26 03:25:13 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 == 235 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == 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) ================================================= == 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 == 237 tests, 7 stderr failures, 0 stdout failures, 0 posttest failures == 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/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:43:26 2006 --- new.short Fri May 26 03:58:41 2006 *************** *** 8,10 **** ! == 237 tests, 7 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 8,10 ---- ! == 235 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) *************** *** 14,17 **** memcheck/tests/x86/scalar_supp (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 14,15 ---- |
|
From: <js...@ac...> - 2006-05-26 02:56:57
|
Nightly build on g5 ( YDL 4.0, ppc970 ) started at 2006-05-26 04:40:00 CEST 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 == 212 tests, 6 stderr failures, 3 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/ppc32/mftocrf (stdout) |
|
From: Tom H. <to...@co...> - 2006-05-26 02:46:18
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-05-26 03:30: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 == 237 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (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 == 239 tests, 7 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:38:08 2006 --- new.short Fri May 26 03:46:06 2006 *************** *** 8,10 **** ! == 239 tests, 7 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,10 ---- ! == 237 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) *************** *** 14,17 **** memcheck/tests/xml1 (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 14,15 ---- |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:41:41
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2006-05-26 03:05:12 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 == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (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 == 263 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) none/tests/amd64/faultstatus (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:15:51 2006 --- new.short Fri May 26 03:25:17 2006 *************** *** 8,11 **** ! == 263 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/stack_switch (stderr) --- 8,10 ---- ! == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) *************** *** 14,18 **** memcheck/tests/xml1 (stderr) - none/tests/amd64/faultstatus (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 13,14 ---- |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:41:35
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-05-26 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 == 260 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) 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 == 263 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/amd64/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:09:49 2006 --- new.short Fri May 26 03:26:06 2006 *************** *** 8,11 **** ! == 263 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/stack_switch (stderr) --- 8,10 ---- ! == 260 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/stack_switch (stderr) *************** *** 13,18 **** memcheck/tests/x86/scalar_supp (stderr) - none/tests/amd64/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) ! none/tests/x86/faultstatus (stderr) ! none/tests/x86/int (stderr) --- 12,15 ---- memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) ! none/tests/tls (stdout) |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:41:29
|
Nightly build on dellow ( x86_64, Fedora Core 5 ) started at 2006-05-26 03:10:18 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 == 260 tests, 2 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (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 == 263 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/amd64/faultstatus (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:23:33 2006 --- new.short Fri May 26 03:32:38 2006 *************** *** 8,16 **** ! == 263 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/amd64/sse_memory (stdout) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) - none/tests/amd64/faultstatus (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 8,12 ---- ! == 260 tests, 2 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:41:25
|
Nightly build on ginetta ( i686, Red Hat 8.0 ) started at 2006-05-26 03:10:16 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 == 236 tests, 6 stderr failures, 0 stdout failures, 0 posttest failures == 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) memcheck/tests/xml1 (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 == 238 tests, 8 stderr failures, 0 stdout failures, 0 posttest failures == 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) memcheck/tests/xml1 (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:24:08 2006 --- new.short Fri May 26 03:34:58 2006 *************** *** 8,10 **** ! == 238 tests, 8 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,10 ---- ! == 236 tests, 6 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) *************** *** 15,18 **** memcheck/tests/xml1 (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 15,16 ---- |
|
From: Tom H. <th...@cy...> - 2006-05-26 02:41:24
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-05-26 03:15:17 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 == 236 tests, 19 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (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 == 238 tests, 21 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) none/tests/x86/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri May 26 03:26:13 2006 --- new.short Fri May 26 03:36:24 2006 *************** *** 8,10 **** ! == 238 tests, 21 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) --- 8,10 ---- ! == 236 tests, 19 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) *************** *** 28,31 **** memcheck/tests/xml1 (stderr) - none/tests/x86/faultstatus (stderr) - none/tests/x86/int (stderr) --- 28,29 ---- |
|
From: <sv...@va...> - 2006-05-26 00:50:47
|
Author: sewardj Date: 2006-05-26 01:50:41 +0100 (Fri, 26 May 2006) New Revision: 5933 Log: Disable tests none/tests/amd64/faultstatus, none/tests/x86/faultstatus and none/tests/x86/int. They always fail, the tested functionality isn't going to get fixed in a hurry, and it's just generally annoying. Added: trunk/none/tests/amd64/faultstatus.disabled trunk/none/tests/x86/faultstatus.disabled trunk/none/tests/x86/int.disabled Removed: trunk/none/tests/amd64/faultstatus.vgtest trunk/none/tests/x86/faultstatus.vgtest trunk/none/tests/x86/int.vgtest Modified: trunk/none/tests/amd64/Makefile.am trunk/none/tests/x86/Makefile.am Modified: trunk/none/tests/amd64/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/none/tests/amd64/Makefile.am 2006-05-26 00:47:13 UTC (rev 5932) +++ trunk/none/tests/amd64/Makefile.am 2006-05-26 00:50:41 UTC (rev 5933) @@ -6,7 +6,7 @@ =20 EXTRA_DIST =3D $(noinst_SCRIPTS) \ clc.vgtest clc.stdout.exp clc.stderr.exp \ - faultstatus.vgtest faultstatus.stderr.exp \ + faultstatus.disabled faultstatus.stderr.exp \ fcmovnu.vgtest fcmovnu.stderr.exp fcmovnu.stdout.exp \ fxtract.vgtest fxtract.stderr.exp fxtract.stdout.exp \ $(addsuffix .stderr.exp,$(INSN_TESTS)) \ Copied: trunk/none/tests/amd64/faultstatus.disabled (from rev 5930, trunk= /none/tests/amd64/faultstatus.vgtest) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/amd64/faultstatus.disabled (= rev 0) +++ trunk/none/tests/amd64/faultstatus.disabled 2006-05-26 00:50:41 UTC (= rev 5933) @@ -0,0 +1,3 @@ +# Currently disabled because the necessary magic in sigframe-amd64-linux= .c +# doesn't work well enough, so the test always fails. +prog: faultstatus Deleted: trunk/none/tests/amd64/faultstatus.vgtest =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/amd64/faultstatus.vgtest 2006-05-26 00:47:13 UTC (re= v 5932) +++ trunk/none/tests/amd64/faultstatus.vgtest 2006-05-26 00:50:41 UTC (re= v 5933) @@ -1 +0,0 @@ -prog: faultstatus Modified: trunk/none/tests/x86/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/none/tests/x86/Makefile.am 2006-05-26 00:47:13 UTC (rev 5932) +++ trunk/none/tests/x86/Makefile.am 2006-05-26 00:50:41 UTC (rev 5933) @@ -9,14 +9,14 @@ bt_literal.stderr.exp bt_literal.stdout.exp bt_literal.vgtest \ cpuid.stderr.exp cpuid.stdout.exp cpuid.vgtest \ cmpxchg8b.stderr.exp cmpxchg8b.stdout.exp cmpxchg8b.vgtest \ - faultstatus.vgtest faultstatus.stderr.exp \ + faultstatus.disabled faultstatus.stderr.exp \ fcmovnu.vgtest fcmovnu.stderr.exp fcmovnu.stdout.exp \ fpu_lazy_eflags.stderr.exp fpu_lazy_eflags.stdout.exp \ fpu_lazy_eflags.vgtest \ fxtract.stdout.exp fxtract.stderr.exp fxtract.vgtest \ getseg.stdout.exp getseg.stderr.exp getseg.vgtest \ incdec_alt.stdout.exp incdec_alt.stderr.exp incdec_alt.vgtest \ - int.stderr.exp int.stdout.exp int.vgtest \ + int.stderr.exp int.stdout.exp int.disabled \ $(addsuffix .stderr.exp,$(INSN_TESTS)) \ $(addsuffix .stdout.exp,$(INSN_TESTS)) \ $(addsuffix .vgtest,$(INSN_TESTS)) \ Copied: trunk/none/tests/x86/faultstatus.disabled (from rev 5930, trunk/n= one/tests/x86/faultstatus.vgtest) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/x86/faultstatus.disabled (re= v 0) +++ trunk/none/tests/x86/faultstatus.disabled 2006-05-26 00:50:41 UTC (re= v 5933) @@ -0,0 +1,4 @@ +# Currently disabled because the necessary magic in sigframe-x86-linux.c +# doesn't work well enough, so the test always fails. It did work back +# in 2.4.X days and could be made to do so again if required. +prog: faultstatus Deleted: trunk/none/tests/x86/faultstatus.vgtest =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/x86/faultstatus.vgtest 2006-05-26 00:47:13 UTC (rev = 5932) +++ trunk/none/tests/x86/faultstatus.vgtest 2006-05-26 00:50:41 UTC (rev = 5933) @@ -1 +0,0 @@ -prog: faultstatus Copied: trunk/none/tests/x86/int.disabled (from rev 5930, trunk/none/test= s/x86/int.vgtest) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/x86/int.disabled (rev 0) +++ trunk/none/tests/x86/int.disabled 2006-05-26 00:50:41 UTC (rev 5933) @@ -0,0 +1,4 @@ +# This is currently disabled because vex doesn't deal with x86 +# int $n for n !=3D 0x80 and so the test is pointless (at the moment). +prog: int +cleanup: rm -f vgcore.pid* Deleted: trunk/none/tests/x86/int.vgtest =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/x86/int.vgtest 2006-05-26 00:47:13 UTC (rev 5932) +++ trunk/none/tests/x86/int.vgtest 2006-05-26 00:50:41 UTC (rev 5933) @@ -1,2 +0,0 @@ -prog: int -cleanup: rm -f vgcore.pid* |
|
From: <sv...@va...> - 2006-05-26 00:47:17
|
Author: sewardj
Date: 2006-05-26 01:47:13 +0100 (Fri, 26 May 2006)
New Revision: 5932
Log:
Push towards a final version for 3.2.0.
Modified:
trunk/NEWS
Modified: trunk/NEWS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/NEWS 2006-05-26 00:13:21 UTC (rev 5931)
+++ trunk/NEWS 2006-05-26 00:47:13 UTC (rev 5932)
@@ -1,90 +1,99 @@
-Release 3.2.0 (19 May 2006)
+
+Release 3.2.0 (?? May 2006)
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-3.2.0 is a feature release with a number of significant improvements:
-Performance (especially of Memcheck) is much improved, Addrcheck has bee=
n
-removed, Callgrind has been added, PPC64/Linux support has been added,
-Lackey has been improved, and MPI support has been added. In detail:
+3.2.0 is a feature release with many significant improvements and the
+usual collection of bug fixes. This release supports X86/Linux,
+AMD64/Linux, PPC32/Linux and PPC64/Linux.
=20
-- Performance is much improved: programs typically run 1.20--1.40 times
- faster under Memcheck (much more for some unusual programs) with an
- average of about 1.30 for the programs we tested it on. The improveme=
nts
- for Nulgrind are similar. We haven't measured Cachegrind and Massif, =
they
- should be also be faster, but with smaller improvements. We are
- interested to hear what improvements users get.
+Performance, especially of Memcheck, is much improved, Addrcheck has
+been removed, Callgrind has been added, PPC64/Linux support has been
+added, Lackey has been improved, and MPI support has been added. In
+detail:
=20
- Also, Memcheck uses much less memory, due to the introduction of a
- "compressed V bits" representation for Memcheck's shadow memory. The
- amount of shadow memory used -- which accounts for a large percentage =
of
- Memcheck's memory overhead -- has been reduced by a factor of more tha=
n 4
- on most programs. This means you should be able to run programs that =
use
- more memory than before without hitting problems. This change in
- representation also contributes to the speed improvements.
+- Memcheck has improved speed and reduced memory use. Programs
+ typically run 20-40% faster, averaging about 30% for SPEC CPU2000.
+ There are smaller but noticeable speed improvements for the other
+ tools. We are interested to hear what improvements users get.
=20
-- Addrcheck has been removed. It has not worked since version 2.4.0, an=
d
- with the speed and memory improvements to Memcheck it is no longer wor=
th
- having around. If you liked using Addrcheck because it didn't give
- undefined value errors, you can use the new Memcheck option
- --undef-value-errors=3Dno to obtain this behaviour.
+ Memcheck uses less memory, due to the introduction of a compressed
+ representation for Memcheck's shadow memory. The space overhead has
+ been reduced by a factor of more than four on most programs. This
+ means you should be able to run programs that use more memory than
+ before without hitting problems.
=20
-- Josef Weidendorfer's popular Callgrind tool has been added. [XXX:
- more details] [XXX: say something about KCachegrind and why it has not
- been folded in... I guess because its development is quite independen=
t]
+- Addrcheck has been removed. It has not worked since version 2.4.0,
+ and the speed and memory improvements to Memcheck make it redundant.
+ If you liked using Addrcheck because it didn't give undefined value
+ errors, you can use the new Memcheck option --undef-value-errors=3Dno
+ to get the same behaviour.
=20
+- Further reduced rates of incorrectly reported undefined-value-errors
+ in Memcheck (it was already very low). In particular, efforts have
+ been made to ensure Memcheck works really well with gcc
+ 4.0/4.1-generated code on X86/Linux and AMD64/Linux.
+
+- Josef Weidendorfer's popular Callgrind tool has been added. Folding
+ it in is in a logical step given its popularity and usefulness, and
+ makes it easier for us to ensure it works "out of the box" on all
+ supported targets. The associated KDE KCachegrind GUI remains a
+ separate project.
+
- Valgrind now works on PPC64/Linux. As with the AMD64/Linux port,
- this supports programs using to 32G of address space. On
- 64-bit capable PPC64/Linux setups, you get a dual architecture
- build so that both 32-bit and 64-bit executables can be run.
- Linux on POWER5 is supported, and POWER4 is also believed to
- work. Both 32-bit and 64-bit DWARF2 is supported. This port is
- known to work well with both gcc-compiled and xlc/xlf-compiled code.
+ this supports programs using to 32G of address space. On 64-bit
+ capable PPC64/Linux setups, you get a dual architecture build so
+ that both 32-bit and 64-bit executables can be run. Linux on POWER5
+ is supported, and POWER4 is also believed to work. Both 32-bit and
+ 64-bit DWARF2 is supported. This port is known to work well with
+ both gcc-compiled and xlc/xlf-compiled code.
=20
-- Floating point accuracy has been improved for PPC32/Linux. =20
- Specifically, the floating point rounding mode is observed on all
- FP arithmetic operations, and multiply-accumulate instructions are
- preserved by the compilation pipeline. This means you should
- get FP results which are bit-for-bit identical to a native run.
- These improvements are also present in the PPC64/Linux port.
+- Floating point accuracy has been improved for PPC32/Linux.
+ Specifically, the floating point rounding mode is observed on all FP
+ arithmetic operations, and multiply-accumulate instructions are
+ preserved by the compilation pipeline. This means you should get FP
+ results which are bit-for-bit identical to a native run. These
+ improvements are also present in the PPC64/Linux port.
=20
- Lackey, the example tool, has been improved:
=20
- * It has a new option --detailed-counts (off by default) which causes
- it to print out a count of loads, stores and ALU operations done, an=
d
- their sizes.
+ * It has a new option --detailed-counts (off by default) which
+ causes it to print out a count of loads, stores and ALU operations
+ done, and their sizes.
=20
- * It has a new option --trace-mem (off by default) which causes it to
- print out a trace of all memory accesses performed by a program. It=
's a
- good starting point for building Valgrind tools that need to track
- memory accesses. Read the comments at the top of the file
- lackey/lk_main.c for details.
+ * It has a new option --trace-mem (off by default) which causes it
+ to print out a trace of all memory accesses performed by a
+ program. It's a good starting point for building Valgrind tools
+ that need to track memory accesses. Read the comments at the top
+ of the file lackey/lk_main.c for details.
=20
- * The original instrumentation (counting numbers of instructions, jump=
s,
- etc) is now controlled by a new option --basic-counts. It is on by
- default.
+ * The original instrumentation (counting numbers of instructions,
+ jumps, etc) is now controlled by a new option --basic-counts. It
+ is on by default.
=20
- MPI support: partial support for debugging distributed applications
- using the MPI library specification has been added. Valgrind is=20
+ using the MPI library specification has been added. Valgrind is
aware of the memory state changes caused by a subset of the MPI
functions, and will carefully check data passed to the (P)MPI_
interface.
=20
-- A new flag, --error-exitcode=3D, has been added. This allows changing=
the
- exit code in runs where Valgrind reported errors, which is useful when
- using Valgrind as part of an automated test suite.
+- A new flag, --error-exitcode=3D, has been added. This allows changing
+ the exit code in runs where Valgrind reported errors, which is
+ useful when using Valgrind as part of an automated test suite.
=20
-- XXX: others...
+- Various segfaults when reading old-style "stabs" debug information
+ have been fixed.
=20
-Please note that Helgrind is still not working. We have made an importa=
nt
-step towards making it work again, however, with the addition of functio=
n
-wrapping (see below).
+Please note that Helgrind is still not working. We have made an
+important step towards making it work again, however, with the
+addition of function wrapping (see below).
=20
Other user-visible changes:
=20
-- Valgrind now has the ability to intercept and wrap arbitrary functions=
.
- This is a preliminary step towards making Helgrind work again, and
- was required for MPI support.
+- Valgrind now has the ability to intercept and wrap arbitrary
+ functions. This is a preliminary step towards making Helgrind work
+ again, and was required for MPI support.
=20
-- There are some changes to Memcheck's client requests. Some of them ha=
ve
- changed names:
+- There are some changes to Memcheck's client requests. Some of them
+ have changed names:
=20
MAKE_NOACCESS --> MAKE_MEM_NOACCESS
MAKE_WRITABLE --> MAKE_MEM_UNDEFINED
@@ -94,9 +103,9 @@
CHECK_READABLE --> CHECK_MEM_IS_DEFINED
CHECK_DEFINED --> CHECK_VALUE_IS_DEFINED
=20
- The reason for the change is that the old names are subtly misleading.
- The old names will still work, but they are deprecated and may be remo=
ved
- in a future release.
+ The reason for the change is that the old names are subtly
+ misleading. The old names will still work, but they are deprecated
+ and may be removed in a future release.
=20
We also added a new client request:
=20
@@ -108,9 +117,48 @@
=20
BUGS FIXED:
=20
-XXX
+108258 NPTL pthread cleanup handlers not called=20
+117290 valgrind is sigKILL'd on startup
+117295 =3D=3D 117290
+118703 m_signals.c:1427 Assertion 'tst->status =3D=3D VgTs_WaitSys'
+118466 add %reg, %reg generates incorrect validity for bit 0
+123210 New: strlen from ld-linux on amd64
+123244 DWARF2 CFI reader: unhandled CFI instruction 0:18
+123248 syscalls in glibc-2.4: openat, fstatat, symlinkat
+123258 socketcall.recvmsg(msg.msg_iov[i] points to uninit
+123535 mremap(new_addr) requires MREMAP_FIXED in 4th arg
+123836 small typo in the doc
+124029 ppc compile failed: `vor' gcc 3.3.5
+124222 Segfault: @@don't know what type ':' is
+124475 ppc32: crash (syscall?) timer_settime()
+124499 amd64->IR: 0xF 0xE 0x48 0x85 (femms)
+124528 FATAL: aspacem assertion failed: segment_is_sane
+124697 vex x86->IR: 0xF 0x70 0xC9 0x0 (pshufw)
+124892 vex x86->IR: 0xF3 0xAE (REPx SCASB)
+126216 =3D=3D 124892
+124808 ppc32: sys_sched_getaffinity() not handled
+n-i-bz Very long stabs strings crash m_debuginfo
+n-i-bz amd64->IR: 0x66 0xF 0xF5 (pmaddwd)
+125492 ppc32: support a bunch more syscalls
+121617 ppc32/64: coredumping gives assertion failure
+121814 Coregrind return error as exitcode patch
+126517 =3D=3D 121814
+108528 NPTL pthread cleanup handlers not called=20
+125607 amd64->IR: 0x66 0xF 0xA3 0x2 (btw etc)
+125651 amd64->IR: 0xF8 0x49 0xFF 0xE3 (clc?)
+126253 x86 movx is wrong
+126451 3.2 SVN doesn't work on ppc32 CPU's without FPU
+126217 increase # threads
+126243 vex x86->IR: popw mem
+126583 amd64->IR: 0x48 0xF 0xA4 0xC2 (shld $1,%rax,%rdx)
+126668 amd64->IR: 0x1C 0xFF (sbb $0xff,%al)
+126696 support for CDROMREADRAW ioctl and CDROMREADTOCENTRY fix
+126722 assertion: segment_is_sane at m_aspacemgr/aspacemgr.c:1624
+126938 bad checking for syscalls linkat, renameat, symlinkat
=20
+(3.2.0: ?? May 2006, vex r??, valgrind r??)
=20
+
Release 3.1.1 (15 March 2006)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3.1.1 fixes a bunch of bugs reported in 3.1.0. There is no new
|
|
From: <sv...@va...> - 2006-05-26 00:13:30
|
Author: sewardj
Date: 2006-05-26 01:13:21 +0100 (Fri, 26 May 2006)
New Revision: 5931
Log:
Read extra args for all tests from $EXTRA_REGTEST_OPTS, which is=20
useful (eg) for running tests with --sanity-level=3D set. Print a
big warning before and after the tests if it is set.
Modified:
trunk/tests/vg_regtest.in
Modified: trunk/tests/vg_regtest.in
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/tests/vg_regtest.in 2006-05-25 18:37:49 UTC (rev 5930)
+++ trunk/tests/vg_regtest.in 2006-05-26 00:13:21 UTC (rev 5931)
@@ -67,6 +67,12 @@
# If results don't match, the output can be found in <test>.std<strm>.ou=
t,
# and the diff between expected and actual in <test>.std<strm>.diff[0-9]=
*.
#
+# Sometimes it is useful to run all the tests at a high sanity check
+# level or with arbitrary other flags. To make this simple, extra=20
+# options, applied to all tests run, are read from $EXTRA_REGTEST_OPTS,
+# and handed to valgrind prior to any other flags specified by the=20
+# .vgtest file.
+#
# Notes on adding regression tests for a new tool are in
# coregrind/docs/coregrind_tools.html.
#-----------------------------------------------------------------------=
-----
@@ -272,6 +278,11 @@
my $name =3D $1;
my $fullname =3D "$dir/$name";=20
=20
+ # Pull any extra options (for example, --sanity-level=3D4)
+ # from $EXTRA_REGTEST_OPTS.
+ my $maybe_extraopts =3D $ENV{"EXTRA_REGTEST_OPTS"};
+ my $extraopts =3D $maybe_extraopts ? $maybe_extraopts : "";
+
read_vgtest_file($vgtest);
=20
if (defined $prereq) {
@@ -281,7 +292,7 @@
}
}
=20
- printf("%-16s valgrind $vgopts $prog $args\n", "$name:");
+ printf("%-16s valgrind $extraopts $vgopts $prog $args\n", "$name:");
=20
# Pass the appropriate --tool option for the directory (can be overr=
idden
# by an "args:" line, though). Set both VALGRIND_LIB and
@@ -290,7 +301,7 @@
my $tool=3Ddetermine_tool();
mysystem("VALGRIND_LIB=3D$tests_dir/.in_place VALGRIND_LIB_INNER=3D$=
tests_dir/.in_place "
. "$valgrind --command-line-only=3Dyes --memcheck:leak-check=3D=
no "
- . "--tool=3D$tool $vgopts "
+ . "--tool=3D$tool $extraopts $vgopts "
. "$prog $args > $name.stdout.out 2> $name.stderr.out");
=20
# Filter stdout
@@ -408,10 +419,22 @@
#-----------------------------------------------------------------------=
-----
# main(), sort of
#-----------------------------------------------------------------------=
-----
+sub warn_about_EXTRA_REGTEST_OPTS()
+{
+ print "WARNING: \$EXTRA_REGTEST_OPTS is set. You probably don't wan=
t\n";
+ print "to run the regression tests with it set, unless you are doing=
some\n";
+ print "strange experiment, and/or you really know what you are doing=
.\n";
+ print "\n";
+}
=20
# nuke VALGRIND_OPTS
$ENV{"VALGRIND_OPTS"} =3D "";
=20
+if ($ENV{"EXTRA_REGTEST_OPTS"}) {
+ print "\n";
+ warn_about_EXTRA_REGTEST_OPTS();
+}
+
my @fs =3D process_command_line();
foreach my $f (@fs) {
if (-d $f) {
@@ -434,6 +457,10 @@
}
summarise_results();
=20
+if ($ENV{"EXTRA_REGTEST_OPTS"}) {
+ warn_about_EXTRA_REGTEST_OPTS();
+}
+
if (0 =3D=3D $num_failures{"stdout"} &&
0 =3D=3D $num_failures{"stderr"} &&
0 =3D=3D $num_failures{"posttest"}) {
|
|
From: Julian S. <js...@ac...> - 2006-05-25 23:23:07
|
I'm trying to wrap up the (long overdue) RC1 tarball in the next couple of days, so it would be good if as few commits as possible happened to the trunk, from pretty now until 3.2.0 finally rolls, at which point of course branches/3_2_0_BRANCH will be created. Naturally, if there is any critical breakage that should be fixed before 3.2.0, please shout now. J |
|
From: Julian S. <js...@ac...> - 2006-05-25 22:58:34
|
> thank you very much for the proofreading and corrections! No problem. One useful side effect is I learned about just how many different options callgrind has. An impressive tool. J |
|
From: Josef W. <Jos...@gm...> - 2006-05-25 21:36:25
|
On Thursday 25 May 2006 20:37, sv...@va... wrote: > Author: sewardj > Date: 2006-05-25 19:37:25 +0100 (Thu, 25 May 2006) > New Revision: 5929 > > Log: > Various minor edits. Julian, thank you very much for the proofreading and corrections! Josef |