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
|
2
(1) |
3
(5) |
4
(4) |
5
(1) |
6
|
7
|
|
8
(2) |
9
(12) |
10
|
11
(2) |
12
(16) |
13
(3) |
14
(13) |
|
15
(20) |
16
(19) |
17
(13) |
18
(20) |
19
(17) |
20
(17) |
21
(14) |
|
22
(13) |
23
(14) |
24
(15) |
25
(14) |
26
(14) |
27
(13) |
28
(2) |
|
29
(16) |
30
(3) |
31
(20) |
|
|
|
|
|
From: Carl E. L. <ce...@li...> - 2012-01-19 23:37:35
|
Valgrind Community: The following is version 2 of the proposal to add Iops to Valgrind to support the Power and s390 Decimal Floating Point (DFP) instructions. The following proposal includes adding 28 new DFP Iops to support operations on 32-bit, 64-bit and 128-bit DFP numbers. The goal is to define a minimal set of Iops that are needed to support these two architectures and hopefully any future architectures that add support for DFP. Three new types will be added to Valgrind to support these Iops, D32, D64 and D128 for the 32-bit, 64-bit and 128-bit DFP values. The proposed DFP support will not extend the existing exception support in Valgrind. The exception support will be the same as the current binary floating point support. The Instruction Set Architecture (ISA) for s390(Z-series) can be found at: http://w3.ibm.com/jct03001pt/wps/myportal, click on the link to the document SA22-7832-08.pdf. The DFP instructions are described in chapter 20. Note, you will need to obtain a free IBM login to get to the document. Follow the instructions on the web page. If you have trouble getting to the document, use the "feedback" link to let them know. The POWER 7 ISA an be found at: http://www.power.org/home Then under community at work, click on the link "Power ISA v2.06 Now Available". The DFP instructions are found in book I, chapter 5. The s390 architecture has a few instructions that may require the introduction of additional Iops to support these instructions. The specifics of how to handle these s390 specific instructions by introducing additional Iops, helper functions, or by emulating them with existing Iops has not been decided. These instructions are not part of the base set of Iops required by both POWER and s390. The discussion of how to support these s390 specific instructions has been deferred until the s390 support is implemented. The names of these Iops are left as "To Be Determined" (TBD) at the time the s3990 support is added. They are called out here for completeness of all the Iops that may need to be added for s390 DFP support. The need for the additional Iops is mentioned in this proposal for completeness sake. The decision on the Iops is deferred until the s390 support is added. The list of proposed DFP Iops will be used as a basis to implement the POWER7 and s390 DFP instruction support. Note that some of the POWER7 and s390 instructions can be implemented using one or more of the new DFP Iops and the existing integer and binary floating point Iops. The instructions that can be implemented using the existing Iops and new DFP Iops have not been explicitly listed in this proposal. I have done a proof of concept implementation for the POWER DFP instruction support in Valgrind. The implementation was intended to validate that the proposed DFP Iops are sufficient for at least the POWER architecture. I will be working on revising the proof of concept implementation for POWER to make it consistent with this version of the proposal and any additional changes the community agrees on. I hope to post the code for inclusion into Valgrind in the near future. Notation Description --------------------------------------------------------------------------- DFP: Decimal Floating Point type (D32, D64 or D128). The term is used to distinguish the value from the traditional binary floating point type. D32: 32-bit decimal floating point type. These values use F64 registers. D64: 64-bit decimal floating point type. These values use F64 registers. D128: 128-bit decimal floating point type. These values use a pair of two 64 bit floating point registers (F64). The instruction only references the first register of the register pair. The second register is implied. Quantization: Rounding a number to a specified exponent is referred to as quantizing a number. For example, the U.S. specifies a dollar amount with at most two fractional digits, for example $12.98. When doing a computation involving money, the quantization instruction would be used to round the result to two fractional digits. Note, POWER 7 and s390 use two floating point registers to hold the 128-bit DFP value. The D32 and D64 values are also stored in the floating point registers. The IEEE 754-2008 specification adds four more rounding modes for DFP that are not supported by the binary floating point numbers. A new rounding mode designator will be introduced for DFP to support all of the specified DFP rounding modes. IRRoundingModeDFP(I32): Indicates the I32 argument is used to hold the bits that specify the rounding mode to be used by the instruction. The possible rounding modes are: - Round to nearest, ties to even - Round toward Zero - Round toward +infinity - Round toward -infinity - Round to Nearest, Ties away from 0 - Round to Nearest, Ties toward 0 - Round to away from Zero - Round to Prepare for Shorter Precision Summary of proposed Iops ---------------------------------------------------------------------------- ARITHMETIC INSTRUCTIONS ----------------------- IRRoundingModeDFP(I32) X D64 X D64 -> D64 Iop_AddD64, Iop_SubD64, Iop_MulD64, Iop_DivD64 IRRoundingModeDFP(I32) X D128 X D128 -> D128 Iop_AddD128, Iop_SubD128, Iop_MulD128, Iop_DivD128 FORMAT CONVERSION INSTRUCTIONS ------------------------------ D32 -> D64 Iop_D32toD64 D64 -> D128 Iop_D64toD128 IRRoundingModeDFP(I32) x D64 -> D32 Iop_D64toD32 IRRoundingModeDFP(I32) x D128 -> D64 Iop_D128toD64 IRRoundingModeDFP(I32) x I64 -> D64 Iop_I64StoD64 IRRoundingModeDFP(I32) x D64 -> I64 Iop_D64toI64S Additional format conversion Iops for converting to/from the DFP and binary floating point formats may need to be added later for s390 support. ROUNDING INSTRUCTIONS ----------------------- IRRoundingModeDFP(I32) x D64 -> D64 Iop_RoundD64toInt IRRoundingModeDFP(I32) x D128 -> D128 Iop_RoundD128toInt COMPARE INSTRUCTIONS ----------------------- D64 x D64 -> IRCmpD64Result(I32) Iop_CmpD64 D128 x D128 -> IRCmpD64Result(I32) Iop_CmpD128 QUANTIZE AND ROUND INSTRUCTIONS ------------------------------- IRRoundingModeDFP(I32) x D64 x D64 -> D64 Iop_QuantizeD64 IRRoundingModeDFP(I32) x D128 x D128 -> D128 Iop_QuantizeD128 IRRoundingModeDFP(I32) x D64 x D64 -> D64 Iop_SignificanceRoundD64 IRRoundingModeDFP(I32) x D128 x D128 -> D128 Iop_SignificanceRoundD128 EXTRACT AND INSERT INSTRUCTIONS ------------------------------- D64 -> I32 Iop_ExtractExpD64 D128 -> I32 Iop_ExtractExpD128 I32 x I64 -> D64 Iop_InsertExpD64 I32 x I128 -> D128 Iop_InsertExpD128 SHIFT SIGNIFICAND INSTRUCTIONS ------------------------------- D64 x U8 -> D64 Iop_ShlD64, Iop_ShrD64 D128 x U8 -> D128 Iop_ShlD128, Iop_ShrD128 This section gives the detailed mapping of the proposed DFP Iops to the corresponding POWER and s390 instruction. The POWER and s390 instructions are listed in their respective Instruction Set Architecture documents referenced at the beginning of this proposal. The POWER and s390 instructions that can be implemented using a sequence of Iops are not listed. ARITHMETIC INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_AddD64 IRRoundingModeDFP(I32) X D64 X D64 -> D64 ADTR dadd ADTRA Add two 64-bit DFP numbers. If both operands are finite numbers, they are added algebraically, forming an intermediate sum. The intermediate sum, if nonzero, is rounded to the operand format and the rounded value is then placed at the result location. The ADTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the ADTR. Iop_AddD128 IRRoundingModeDFP(I32) X D128 X D128 -> D128 AXTR daddq AXTRA Add two 128-bit DFP numbers If both operands are finite numbers, they are added algebraically, forming an intermediate sum. The intermediate sum, if nonzero, is rounded to the operand format and the rounded value is then placed at the result location. The AXTRA instruction has a field to specify the desired rounding mode. Iop_SubD64 IRRoundingModeDFP(I32) X D64 X D64 -> D64 SDTR dsub SDTRA The execution of SUBTRACT is identical to that of ADD, except that the second operand, if numeric, participates in the operation with its sign bit inverted. The SXTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the SDTR. Iop_SubD128 IRRoundingModeDFP(I32) X D128 X D128 -> D128 SXTR dsubq SXTRA The execution of SUBTRACT is identical to that of ADD, except that the second operand, if numeric, participates in the operation with its sign bit inverted. The SXTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the SXTRA. Iop_MulD64 IRRoundingModeDFP(I32) X D64 X D64 -> D64 MDTR dmul MDTRA If both source operands are finite numbers, they are multiplied to form an intermediate product. The intermediate product is rounded to the target format. The MDTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the MDTR. Iop_MulD128 IRRoundingModeDFP(I32) X D128 X D128 -> D128 MXTR dmulq MXTRA If both source operands are finite numbers, they are multiplied to form an intermediate product. The intermediate product is rounded to the target format. The MXTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the MXTR. Iop_DivD64 IRRoundingModeDFP(I32) X D64 X D64 -> D64 DDTR ddiv DDTRA If divisor is nonzero and both the dividend and divisor are finite numbers, the first operand is divided by the second operand to form an intermediate quotient. The intermediate quotient, if nonzero, is rounded to the target format. The MDTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the MDTR. Iop_DivD128 IRRoundingModeDFP(I32) X D128 X D128 -> D128 DXTR ddivq DXTRA If divisor is nonzero and both the dividend and divisor are finite numbers, the first operand is divided by the second operand to form an intermediate quotient. The intermediate quotient, if nonzero, is rounded to the target format. The DXTRA instruction has a field to specify the desired rounding mode but is otherwise identical to the MXTR. FORMAT CONVERSION INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- TBD PFPO The PFPO instruction operation is specified by the code in general purpose register 0 and the condition code is set to indicate the result. The operations that can be specified for this instruction include a large list of format conversions to/from various sizes of DFP operands and various sizes of Hexadecimal floating point and Binary floating point formats. Additional Iops to support these conversions on s390 may be needed. The decision on which Iops are needed will be deferred to when the s390 support is added. Iop_D32toD64 D32 -> D64 LDETR dctdp The 32-bit DFP source operand is converted into a 64-bit DFP result. Iop_D64toD128 D64 -> D128 LXETR dctqpq The 64-bit DFP source operand is converted into a 128-bit DFP result. Iop_D64toD32 IRRoundingModeDFP(I32) x D64 -> D64 LEDTR drsp The 64-bit DFP source operand is rounded to a DFP 32-bit value, according to the rounding mode. Iop_D128toD64 IRRoundingModeDFP(I32) x D128 -> D64 LDXTR drdpq The 128-bit DFP source operand is rounded, according to the rounding mode. Iop_I64StoD64 IRRoundingModeDFP(I32) x I64 -> D64 CDGTR dcffix CDGTRA The 64-bit signed binary-integer in the second source operand is converted into a 64-bit DFP result using the rounding mode specified in the first operand. Iop_D64toI64S IRRoundingModeDFP(I32) x D64 -> I64 CGDTR dctfix CGDTRA The 64-bit DFP source operand is rounded to a signed integer, according to the rounding mode specified by the first operand, and converted into a signed 64-bit integer result with the same sign as the source. May need new Iop IRRoundingModeDFP(I32) x D64 -> I64 TBD CLGDTR The 64-bit DFP source operand is rounded to a signed integer, according to the rounding mode specified by the first operand, and converted into a signed 64-bit binary integer result with the same sign as the source. Possible implementation: the 64-bit DFP source operand is rounded into a 64-bit signed integer using the existing instruction Iop_D64toI64. Defer decision on adding a new Iop until the s390 implementation is started. May need new Iop IRRoundingModeDFP(I32) x D64 -> I32 TBD CLFDTR The 64-bit DFP source operand is rounded to a signed integer, according to the rounding mode specified by the first operand, and converted into a signed 32-bit integer result with the same sign as the source. Possible implementation: the 64-bit DFP source operand is rounded into a 64-bit signed integer using the existing instruction Iop_D64toI64, then Iop_64to32 convert to a signed 32-bit integer. Defer decision on adding a new Iop until the s390 implementation is started. May need new Iop IRRoundingModeDFP(I32) x D128 -> I64 TBD CLGXTR The 128-bit DFP source operand is rounded to a signed integer, according to the rounding mode specified by the first operand, and converted into a signed 64-bit integer result with the same sign as the source. Possible implementation: the 128-bit DFP source operand is rounded into a 64-bit DFP with the Iop_RoundD128toD64 instruction, 64-bit DFP is rounded to a 64-bit signed integer using the existing instruction Iop_D64toI64. Defer decision on adding a new Iop until the s390 implementation is started. May need new Iop IRRoundingModeDFP(I32) x D128 -> I32 TBD CLFXTR The 128-bit DFP source operand is rounded to a signed integer, according to the rounding mode specified by the first operand, and converted into a signed 32-bit integer result with the same sign as the source. Possible implementation: the 128-bit DFP source operand is rounded into a 64-bit DFP with the Iop_RoundD128toD64 instruction,the 64-bit DFP is then converted to a 64-bit signed integer using the existing instruction Iop_D64toI64, then Iop_64to32 convert to a signed 32-bit integer. Defer decision on adding a new Iop until the s390 implementation is started. ROUNDING INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_RoundD64toInt IRRoundingModeDFP(I32) x D64 -> D64 FIDTR drintx The D64 operand, if a finite number, is rounded to an integer value in the same DFP format. Iop_RoundD128toInt IRRoundingModeDFP(I32) x D128 -> D128 FIXTR drintxq The D128 operand, if a finite number, is rounded to a binary integer value, in the same DFP format. COMPARE INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_CmpD64 D64 x D64 -> IRCmpF64Result(I32) dcmpo dcmpu Perform the comparison, as specified in the instruction. The instruction sets the platform condition codes. The condition codes for the virtual machine need to be updated based on the result in this platform specific condition code register. Iop_CmpD128 D128 x D128 -> IRCmpF64Result(I32) dcmpoq dcmpuq Perform the comparison, as specified in the instruction. The instruction sets the platform condition codes. The condition codes for the virtual machine need to be updated based on the result in this platform specific condition code register. QUANTIZE AND ROUND INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_QuantizeD64 IRRoundingModeDFP(I32) x D64 x D64 -> D64 dqua The second D64 operand is converted and rounded to the form with the same exponent as that of the first DFP operand. The result is placed in the result operand. Iop_QuantizeD128 IRRoundingModeDFP(I32) x D128 x D128-> D128 dquaq The second D128 operand is converted and rounded to the form with the same exponent as that of the first DFP operand. The result is placed in the result operand. Iop_SignificanceRoundD64 IRRoundingModeDFP(I32) x D64 x D64 -> D64 RRDTR drrnd The second D64 operand is rounded to the significance specified by the first D64 operand as specified by the rounding mode. Iop_SignificanceRoundD128 IRRoundingModeDFP(I32) x D128 x D128 -> D128 RRXTR drrndq The second D128 operand is rounded to the significance specified by the first D128 operand as specified by the rounding mode. EXTRACT AND INSERT INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_ExtractExpD64 D64 -> I32 EEDTR dxex The exponent of the D64 operand is extracted. The extracted exponent is converted and stored in the floating point register as a signed 32-bit binary integer format. Iop_ExtractExpD128 D128 -> I32 EEXTR dxexq The exponent of the D128 operand is extracted. The extracted exponent is converted and stored in the floating point register as a signed 32-bit binary integer. Iop_InsertExpD64 I32 x I64 -> D64 IEDTR diex The exponent is specified by the first I32 operand the signed significand is given by the second I64 value. The result is a D64 value consisting of the specified significand and exponent whose sign is that of the specified significand. Iop_InsertExpD128 I32 x I128 -> D128 IEXTR diexq The exponent is specified by the first I32 operand the signed significand is given by the second I128 value. The result is a D128 value consisting of the specified significand and exponent whose sign is that of the specified significand. SHIFT SIGNIFICAND INSTRUCTIONS Iop s390 Power Description of instruction, implementation opcode opcode details ------------------------------------------------------------------------------- Iop_ShlD64 D64 x U8 -> D64 SLDT dscli The D32 or D64 significand is shifted left by the number of digits specified by the U8 operand. Digits shifted out of the leftmost digit are lost. Zeros are supplied to the vacated positions on the right. The sign of the result is the same as the sign of the D64 operand. Iop_ShlD128 D128 x U8 -> D128 SLDT dscliq The D128 significand is shifted left by the number of digits specified by the U8 operand. Digits shifted out of the leftmost digit are lost. Zeros are supplied to the vacated positions on the right. The sign of the result is the same as the sign of the D128 operand. Iop_ShrD64 D64 x U8 -> D64 SLDT dscri The D32 or D64 significand is shifted right by the number of digits specified by the U8 operand. Digits shifted out of the right most digit are lost. Zeros are supplied to the vacated positions on the left. The sign of the result is the same as the sign of the D64 operand. Iop_ShrD128 D128 x U8 -> D128 SLDT dscriq The D128 significand is shifted right by the number of digits specified by the U8 operand. Digits shifted out of the right most digit are lost. Zeros are supplied to the vacated positions on the left. The sign of the result is the same as the sign of the D128 operand. Thank you for your time and effort to review this proposal. Carl Love |
|
From: <sv...@va...> - 2012-01-19 19:56:53
|
Author: bart
Date: 2012-01-19 19:52:15 +0000 (Thu, 19 Jan 2012)
New Revision: 12346
Log:
drd: Fix a race condition in the pthread_create() intercept.
Avoid that the futex wake call in DRD_(sema_up)() can get invoked after the semaphore has
already been destroyed. This is most likely the real fix for the bug described in the
commit message of r12332.
Modified:
trunk/drd/drd_pthread_intercepts.c
trunk/drd/tests/fp_race_xml.stderr.exp
Modified: trunk/drd/drd_pthread_intercepts.c
===================================================================
--- trunk/drd/drd_pthread_intercepts.c 2012-01-18 09:47:12 UTC (rev 12345)
+++ trunk/drd/drd_pthread_intercepts.c 2012-01-19 19:52:15 UTC (rev 12346)
@@ -136,7 +136,8 @@
/* Local data structures. */
typedef struct {
- volatile int counter;
+ pthread_mutex_t mutex;
+ int counter;
} DrdSema;
typedef struct
@@ -180,18 +181,22 @@
static void DRD_(sema_init)(DrdSema* sema)
{
DRD_IGNORE_VAR(sema->counter);
+ pthread_mutex_init(&sema->mutex, NULL);
sema->counter = 0;
}
static void DRD_(sema_destroy)(DrdSema* sema)
{
+ pthread_mutex_destroy(&sema->mutex);
}
static void DRD_(sema_down)(DrdSema* sema)
{
int res = ENOSYS;
+ pthread_mutex_lock(&sema->mutex);
while (sema->counter == 0) {
+ pthread_mutex_unlock(&sema->mutex);
#ifdef HAVE_USABLE_LINUX_FUTEX_H
if (syscall(__NR_futex, (UWord)&sema->counter,
FUTEX_WAIT | FUTEX_PRIVATE_FLAG, 0) == 0)
@@ -207,17 +212,21 @@
*/
if (res != 0 && res != EWOULDBLOCK)
sched_yield();
+ pthread_mutex_lock(&sema->mutex);
}
sema->counter--;
+ pthread_mutex_unlock(&sema->mutex);
}
static void DRD_(sema_up)(DrdSema* sema)
{
+ pthread_mutex_lock(&sema->mutex);
sema->counter++;
#ifdef HAVE_USABLE_LINUX_FUTEX_H
syscall(__NR_futex, (UWord)&sema->counter,
FUTEX_WAKE | FUTEX_PRIVATE_FLAG, 1);
#endif
+ pthread_mutex_unlock(&sema->mutex);
}
/**
Modified: trunk/drd/tests/fp_race_xml.stderr.exp
===================================================================
--- trunk/drd/tests/fp_race_xml.stderr.exp 2012-01-18 09:47:12 UTC (rev 12345)
+++ trunk/drd/tests/fp_race_xml.stderr.exp 2012-01-19 19:52:15 UTC (rev 12346)
@@ -79,7 +79,7 @@
</other_segment_end>
</error>
- <trace><text>drd_post_thread_join joiner = 1, joinee = 2, new vc: [ 1: 4, 2: 1 ]</text></trace>
+ <trace><text>drd_post_thread_join joiner = 1, joinee = 2, new vc: [ 1: 8, 2: 3 ]</text></trace>
<trace><text>drd_thread_finished tid = 1</text></trace>
<status>
|
|
From: Carl E. L. <ce...@li...> - 2012-01-19 19:36:28
|
On Thu, 2012-01-19 at 19:12 +0100, Julian Seward wrote:
> > If there is value in adding the DFP type, I am willing to change my
> > preliminary POWER7 implementation to add the DFP types rather then using
> > the floating point types as I currently have. Having the DFP type may
> > make the overall code clearer then having Iops with the D32, D64 and D128
> > in the name but actually operate on F32, F64 and F128 values.
> >
> > Thoughts on adding DFP type?
>
> Yes, please do. It does cause the code to be a little longer, but it's
> also clearer and easier to verify as being correct. In the long run the
> latter points are much more important.
>
>
>
> > The POWER7 and s390 machines support the additional four rounding modes for
> > DFP (total of 8 not 9 modes) in the IEEE specification. After some
> > thought, I think it would be better to explicitly change the rounding mode
> > specifier from IRRoundingMode(I32) to IRRoundingModeDFP(I32). The concern
> > is if we extend the existing rounding mode specifier then there will be
> > rounding modes for which the existing binary floating point instructions
> > are not specified to support. Yes, it is some replication of code to
> > create a second super-set of rounding modes for DFP but from an overall
> > consistency, clarity and accuracy standpoint I think it might be best.
>
> I agree. +1 for IRRoundingModeDFP. It will have 8 possible values,
> yes?
>
>
>
> > OK, I had not specifically read the document above but was aware that
> > Valgrind only had limited rounding and exception support. I included
> > the full rounding and exception support for completeness. I thought it
> > better to include it at this point then to gloss over it. I added a
> > comment to the document ahead of the field definitions to that effect.
> > So, if there is no chance that the exception support will be added then
> > we can just drop the exception specification part.
> >
> > Thoughts?
>
> Drop the exception specification part. If we ever need to support FP
> exceptions then we will need to design a solution which works cleanly
> for both regular FP and DFP.
>
>
>
> > The immediate exponent value in the instruction is specific to the POWER
> > processor. I have spent some time reconsidering this. We really don't
> > need it so I will remove the IRRoundingModeAndEponent(I32).
>
> Good.
>
>
>
> > Comment from Florian:
> > > You did not describe InvOperationModes. But looking at insn LDETR
> > > (which is D32 -> D64 conversion) I gather that InvOperationModes
> > > controls whether or not the IEEE-invalid-operation-exception is
> > > delivered. It's essentially a Boolean value. I propose to ignore it
> > > and deliver the exception unconditionally (which is what we do for
> > > binary floating point).
> >
> > Julian do you agree we should remove the InvOperationModes(I32) from
> > the Iop specification? I am OK with it.
>
> Yes, please remove.
>
>
>
> > > > InvOperationModes(I32) x D64 -> D128
> > > > Iop_D64toD128
> > >
> > > ditto
> > >
> > > > IRRoundingExceptionModes(I32) x D64 -> D32
> > > > Iop_RoundD64toD32
> > > >
> > > > IRRoundingExceptionModes(I32) x D128 -> D64
> > > > Iop_RoundD128toD64
> > > >
> > > > IRRoundingExceptionModes(I32) x I64 -> D64
> > > > Iop_I64StoD64
> > >
> > > ok
> >
> > Comment from Florian:
> > > These two should be renamed to Iop_D64toD32 and Iop_D128toD64 for
> > > symmetry in naming with binary floating point ops.
> >
> > I disagree. The drsp instruction is analogous to the binary FP frsp
> > instruction, which (for ppc64) uses the Iop Iop_RoundF64ToF32. The
> > distinction is that an Iop that does not have "Round" in the name is
> > a conversion from one general type (i.e., floating point) to a different
> > general type (i.e., integer); whereas an Iop that *does* have "Round"
> > in the name is a narrowing of the same general type.
>
> Florian is correct, assuming that the types for these operations
> (D64 -> D32 etc) are really what you (Carl) intended. Problem is
> that it's unclear what behaviour you want. Your options are
>
> round and convert to a different format
> in which case you want the (eg) Iop_D64toD32 name style
> and the IR types for src and dst will then be different
> (eg D64 and D32 in this case)
>
> round (to a smaller range) but remain in the same format
> in which case you want the Iop_RoundD64toD32 names
> in this case the src and dst types are the same (D64)
> and D32 merely indicates the range to which the value is
> rounded
>
> so which is it?
>
>
The intention is the Iop_RoundD128toD64 Iop takes a value with the
physical D128 bit encoding and generates a result with the physical D64
bit encoding. Similarly for the Iop_RoundD64toD32 Iop. So based on
your definitions above, the first one (round and convert to a different
format) is correct and the Iops need to be renamed. The above
clarification was really helpful to understand the naming convention.
Thanks. I will make the Iop name changes.
>
>
> > Comment from Florian:
> > > For s390 we also need:
> > > IROp description s390 insn
> > >
> > > Iop_I64StoD128 IRRoundingMode(I32) x signed I64 -> D128 CXGTR
> > > Iop_I32StoD64 signed I32 -> D64 CDFTR
> > > Iop_I32StoD128 signed I32 -> D128 CXFTR
> > > Iop_I64UtoD64 IRRoundingMode(I32) x unsigned I64 -> D64 CDLGTR
> > > Iop_I64UtoD128 IRRoundingMode(I32) x unsigned I64 -> D128 CXLGTR
> > > Iop_I32UtoD64 unsigned I32 -> D64 CDLFTR
> > > Iop_I32UtoD128 unsigned I32 -> D128 CXLFTR
> > >
> > > We need both: conversion to signed and unsigned int
> > >
> > > IROp description s390 insn
> > >
> > > Iop_D64toI64S IRRoundingMode(I32) x D64 -> signed I64 CGDTR(A)
> > > Iop_D128toI64S IRRoundingMode(I32) x D128 -> signed I64 CGXTR(A)
> > > Iop_D64toI32S IRRoundingMode(I32) x D64 -> signed I32 CFDTR
> > > Iop_D128toI32S IRRoundingMode(I32) x D128 -> signed I32 CFXTR
> > > Iop_D64toI64U IRRoundingMode(I32) x D64 -> unsigned I64 CLGDTR
> > > Iop_D128toI64U IRRoundingMode(I32) x D128 -> unsigned I64 CLGXTR
> > > Iop_D64toI32U IRRoundingMode(I32) x D64 -> unsigned I32 CLFDTR
> > > Iop_D128toI32U IRRoundingMode(I32) x D128 -> unsigned I32 CLFXTR
> > >
> > > Note, the new IRops for conversion to 32-bit wide results and from D128.
> >
> > Comment from Christian Borntraege:
> > > > The PFPO insn is used to convert between binary floating point and
> > > > decimal floating point. Since we have 3 formats each, that makes 9
> > > > conversion ops for each direction:
> > > >
> > > > Iop_D32toF32 IRRoundingMode(I32) x D32 -> F32
> > > > Iop_D32toF64 IRRoundingMode(I32) x D32 -> F64
> > > > Iop_D32toF128 IRRoundingMode(I32) x D32 -> F128
> > > > Iop_D64toF32 IRRoundingMode(I32) x D64 -> F32
> > > > Iop_D64toF64 IRRoundingMode(I32) x D64 -> F64
> > > > Iop_D64toF128 IRRoundingMode(I32) x D64 -> F128
> > > > Iop_D128toF32 IRRoundingMode(I32) x D128 -> F32
> > > > Iop_D128toF64 IRRoundingMode(I32) x D128 -> F64
> > > > Iop_D128toF128 IRRoundingMode(I32) x D128 -> F128
> > > >
> > > > Iop_F32toD32 IRRoundingMode(I32) x F32 -> D32
> > > > Iop_F32toD64 IRRoundingMode(I32) x F32 -> D64
> > > > Iop_F32toD128 IRRoundingMode(I32) x F32 -> D128
> > > > Iop_F64toD32 IRRoundingMode(I32) x F64 -> D32
> > > > Iop_F64toD64 IRRoundingMode(I32) x F64 -> D64
> > > > Iop_F64toD128 IRRoundingMode(I32) x F64 -> D128
> > > > Iop_F128toD32 IRRoundingMode(I32) x F128 -> D32
> > > > Iop_F128toD64 IRRoundingMode(I32) x F128 -> D64
> > > > Iop_F128toD128 IRRoundingMode(I32) x F128 -> D128
> > >
> > > If you look at pfpo, then the instruction has the same tricky
> > > behaviour as EXecute. Since a self checking prefix and 18 Iops is
> > >
> > > pretty expensive I think that pfpo qualifies for a helper.
> >
> > These conversion modes are specifically support by s390 but not POWER.
> > POWER supports a subset of the conversions supported by s390. This is
> > one of the areas where I feel we should defer the decision on adding more
> > Iops, using a helper function or emulating these conversions with the
> > subset of conversions that have been proposed until the s390 team is ready
> > to add the s390 support to Valgrind. This is beyond the scope of what is
> > needed for me to add the POWER support. But I think it is important that
> > the issue has been raised to understand the full scope of what is needed
> > by both architectures.
>
> Ok. I agree .. just add the conversions needed for POWER, unless
> Christian/Florian want to also add the S390 needed conversions now
> (I am unclear if you do, or not)
I have no need to support all these on POWER. I will put the following
into version 2 of the proposal so it is clear we may need additional
Iops in the future for s390.
"Additional format conversion Iops for converting to/from
decimal floating point and binary floating point may need to be
added later for the s390 support."
I think it is important that we state some additional Iops maybe needed
for other architectures. But I would like to defer the final decision
on exactly how these conversions are supported via additional Iops or a
helper function to when the s390 support is done.
>
>
>
> >
> > > > IRRoundingExceptionModes(I32) x D64 -> I64
> > > > Iop_D64toI64
> > >
> > > this is underspecified .. you need to decide whether that's a
> > > conversion to signed or unsigned I64 (or maybe you need both)
> > > and call them Iop_D64toI64S or Iop_D64toI64U respectively.
> > > (I think you comment about this further down in the doc.)
> > > I mention this partly because sorting out such ambiguity in the
> > > past for the Fxx->Ixx conversions required a lot of hoop
> > > jumping, so we might as well get it straightened out up front.
> >
> > OK, should be convert to signed integer. Changed the name to
> > Iop_D64toI64S.
>
> Good.
>
>
>
> > > > ROUNDING INSTRUCTIONS
> > > > -----------------------
> > > > IRRoundingMode(I32) x D64 -> D64
> > > > Iop_RoundD64
> > > >
> > > > IRRoundingMode(I32) x D128 -> D128
> > > > Iop_RoundD128
> > >
> > > ok
> >
> > Comment from Florian:
> > > These should be named Iop_RoundD64toInt and Iop_RoundD128toInt for
> > > symmetry in naming with binary floating point ops.
> >
> > I am OK with the name change. Comments?
>
> /me agrees with Florian.
>
>
>
> >
> > > > COMPARE INSTRUCTIONS
> > > > -----------------------
> > > > D64 x D64 -> IRCmpF64Result(I32)
> > > > Iop_CmpD64
> > > >
> > > > D128 x D128 -> IRCmpF64Result(I32)
> > > > Iop_CmpD128
> > >
> > > ok
> >
> > Comment from Florian:
> > > OK. I would use IRCmpD64Result and IRCmpD128Result. That allows
> > > us to use a different encoding, which may be desirable.
> >
> > I am OK with the name change. Comments?
>
> Fine by me.
>
>
>
> > > > QUANTIZE AND ROUND INSTRUCTIONS
> > > > -------------------------------
> > > > IRRoundingMode(I32) x D64-> D64
> > > > Iop_QuantizeID64,
> > > >
> > > > IRRoundingMode(I32) x D128-> D128
> > > > Iop_QuantizeID128
> > > >
> > > > IRRoundingMode(I32) x D64 x D64 -> D64
> > > > Iop_QuantizeD64
> > > >
> > > > IRRoundingMode(I32) x D128 x D128 -> D128
> > > > Iop_QuantizeD128
> > >
> > > I'm not clear what the ID vs D signifies in these names. Can
> > > they instead be called Iop_Quantize{Un,Bin}{D64,D128} to denote
> > > unary vs binary ness (ignoring the rounding mode arg which is
> > > present in all 4 cases).
> >
> > The first two with the I are for immediate value of the exponent for the
> > quantization operation. Remember above, I had the
> > IRRoundingModeAndEponent(I32) specification. It was also there for
> > specifying the immediate value. I didn't realize that I had a redundant
> > way of specifying the immediate exponent value. So, as said above, we drop
> > IRRoundingModeAndEponent(I32) specification.
> >
> > > What is quantization, anyway (in the context of DFP I mean)?
> > > Does it have any analogue in traditional IEEE754 FP ?
> >
> > Quantization is the process of rounding a number to a specified exponent as
> > mentioned earlier. For example, the U.S. specifies a dollar amount with at
> > most two fractional digits, for example $12.98. When doing a computation
> > involving money, the quantization instruction would be used to round the
> > result to two fractional digits.
> >
> > The immediate value to specify the desired exponent is specific to POWER.
> > Both s390 and POWER have instructions for changing the exponent of
> > (quantizing) a value in register A to match the exponent of a value in
> > register B. I think we should remove the Iops Iop_QuantizeID64 and
> > Iop_QuantizeID128 for specify an immediate exponent. For the POWER
> > instruction that specifies the immediate exponent, I can just generate a
> > DFP number with the desired exponent and pass that as the value in
> > register B as the target exponent. This will help minimize the number of
> > new Iops.
>
> Ok by me.
>
>
>
> > > > IRRoundingMode(I32) x D64 x D64 -> D64
> > > > Iop_SignificanceRoundD64
> > > >
> > > > IRRoundingMode(I32) x D128 x D128 -> D128
> > > > Iop_SignificanceRoundD128
> > > >
> > > >
> > > > EXTRACT AND INSERT INSTRUCTIONS
> > > > -------------------------------
> > > > D64 -> I64
> > > > Iop_ExtractExpD64
> > > >
> > > > D128 -> I64
> > > > Iop_ExtractExpD128
> > >
> > > The exponent really needs 64 bits? Can it be 32 bits? That
> > > might allow for more efficient code generation for 32 bit targets.
> >
> > The biased exponent could be stored as a 32 bit biased integer. The
> > functionality of the specific instruction that this Iop was intended for
> > specifies the exponent will be stored in a floating point register in a
> > signed integer format. I agree we can make the target be I32 and then
> > just handle the I32 to I64 conversion as needed for the specific
> > instruction. The exponent for any DFP number will easily fit in less then
> > 31 bits.
> >
> > I will change the above two Iops to return an I32 value.
>
> Good.
>
>
>
>
> >
> > Comment from Florian:
> > > Do we need to support these at all? In other words, does GCC issue these
> > > or do they show up in hand crafted assembler shipped with GCC/GLIBC?
> > > I don't know but will find out (for s390).
> >
> > Yes, the libdfp and binutils use them.
> >
> > > > I64 x I64 -> D64
> > > > Iop_InsertExpD64
> > > >
> > > > I64 x I128 -> D128
> > > > Iop_InsertExpD128
> > >
> > > ditto comment
> >
> > ditto above that we do need these Iops for instructions that are used.
>
> So (unclear) as with ExtractExp, you'll change the exp value to be an I32
> instead of an I64, yes?
Sorry, missed that. Yes, we should change this to be consistent with
the ExtractExp. So, it will be:
I32 x I64 -> D64
Iop_InsertExpD64
I32 x I128 -> D128
Iop_InsertExpD128
where the I32 is the exponent and the I64/128 is the significand.
> > > > SHIFT SIGNIFICAND INSTRUCTIONS
> > > > -------------------------------
> > > > U16 x D64 -> D64
> > > > Iop_ShlD64, Iop_ShrD64
> > > >
> > > > U16 x D128 -> D128
> > > > Iop_ShlD128, Iop_ShrD128
> > >
> > > two things: (1) does the shift amount need to be 16 bits?
> > > For all the other shifting style ops we have, the shift amount
> > > is encoded in 8 bits (Ity_I8) and I would prefer to stick with
> > > that for consistency, if possible. (2) pls put the shift amount
> > > as the second argument, not the first, as that too is consistent
> > > with all other shift ops we have (eg, Iop_Shr64)
> >
> > OK, changed shift to U8 and made it D64 x U8 -> D64; D128 x U8 -> D128
>
> Good.
>
>
>
> > > ---------------
> > >
> > > > This section give the detailed mapping of Power and s390
> > > >
> > > > instructions to the proposed DFP Iops or how they would be implemented
> > > > with the existing Iops and the proposed DFP Iops.
> > >
> > > I'll comment on this second half of the proposal tomorrow.
> > >
> > > J
> >
> > I have not seen any additional comments. It is probably best to focus on
> > resolving the above issues first as the second part is just a more detailed
> > discussion of the above summary of the Iops. Once we have agreement on the
> > above discussion points, I will update and post version 2 of the proposal.
>
> Yes, good plan.
>
> J
|
|
From: Philippe W. <phi...@sk...> - 2012-01-19 19:22:43
|
> * something else? Valgrind x86 reaches the limit of 4Gb (sum of client memory + Valgrind memory). > On 64 bit platforms, V is limited to 32GB total memory use, but this is > completely artificial and so can easily be increased to 64GB or 128GB. > IOW, providing you can run your app as a 64-bit process, you should > be able to "solve" the problem by throwing physical memory at it. We would need to switch to 64 bits for our application(s), and it is not a short term objective. So, at short term, the solution is to either reduce the memory used by Valgrind ( cfr 282230 pool alloc work recently committed) or analyse more in depth the client memory (289939, still to be reviewed). With 282230 and some results obtained with 289939, we are now back below the 4 Gb. Philippe |
|
From: Julian S. <js...@ac...> - 2012-01-19 18:17:15
|
> If there is value in adding the DFP type, I am willing to change my
> preliminary POWER7 implementation to add the DFP types rather then using
> the floating point types as I currently have. Having the DFP type may
> make the overall code clearer then having Iops with the D32, D64 and D128
> in the name but actually operate on F32, F64 and F128 values.
>
> Thoughts on adding DFP type?
Yes, please do. It does cause the code to be a little longer, but it's
also clearer and easier to verify as being correct. In the long run the
latter points are much more important.
> The POWER7 and s390 machines support the additional four rounding modes for
> DFP (total of 8 not 9 modes) in the IEEE specification. After some
> thought, I think it would be better to explicitly change the rounding mode
> specifier from IRRoundingMode(I32) to IRRoundingModeDFP(I32). The concern
> is if we extend the existing rounding mode specifier then there will be
> rounding modes for which the existing binary floating point instructions
> are not specified to support. Yes, it is some replication of code to
> create a second super-set of rounding modes for DFP but from an overall
> consistency, clarity and accuracy standpoint I think it might be best.
I agree. +1 for IRRoundingModeDFP. It will have 8 possible values,
yes?
> OK, I had not specifically read the document above but was aware that
> Valgrind only had limited rounding and exception support. I included
> the full rounding and exception support for completeness. I thought it
> better to include it at this point then to gloss over it. I added a
> comment to the document ahead of the field definitions to that effect.
> So, if there is no chance that the exception support will be added then
> we can just drop the exception specification part.
>
> Thoughts?
Drop the exception specification part. If we ever need to support FP
exceptions then we will need to design a solution which works cleanly
for both regular FP and DFP.
> The immediate exponent value in the instruction is specific to the POWER
> processor. I have spent some time reconsidering this. We really don't
> need it so I will remove the IRRoundingModeAndEponent(I32).
Good.
> Comment from Florian:
> > You did not describe InvOperationModes. But looking at insn LDETR
> > (which is D32 -> D64 conversion) I gather that InvOperationModes
> > controls whether or not the IEEE-invalid-operation-exception is
> > delivered. It's essentially a Boolean value. I propose to ignore it
> > and deliver the exception unconditionally (which is what we do for
> > binary floating point).
>
> Julian do you agree we should remove the InvOperationModes(I32) from
> the Iop specification? I am OK with it.
Yes, please remove.
> > > InvOperationModes(I32) x D64 -> D128
> > > Iop_D64toD128
> >
> > ditto
> >
> > > IRRoundingExceptionModes(I32) x D64 -> D32
> > > Iop_RoundD64toD32
> > >
> > > IRRoundingExceptionModes(I32) x D128 -> D64
> > > Iop_RoundD128toD64
> > >
> > > IRRoundingExceptionModes(I32) x I64 -> D64
> > > Iop_I64StoD64
> >
> > ok
>
> Comment from Florian:
> > These two should be renamed to Iop_D64toD32 and Iop_D128toD64 for
> > symmetry in naming with binary floating point ops.
>
> I disagree. The drsp instruction is analogous to the binary FP frsp
> instruction, which (for ppc64) uses the Iop Iop_RoundF64ToF32. The
> distinction is that an Iop that does not have "Round" in the name is
> a conversion from one general type (i.e., floating point) to a different
> general type (i.e., integer); whereas an Iop that *does* have "Round"
> in the name is a narrowing of the same general type.
Florian is correct, assuming that the types for these operations
(D64 -> D32 etc) are really what you (Carl) intended. Problem is
that it's unclear what behaviour you want. Your options are
round and convert to a different format
in which case you want the (eg) Iop_D64toD32 name style
and the IR types for src and dst will then be different
(eg D64 and D32 in this case)
round (to a smaller range) but remain in the same format
in which case you want the Iop_RoundD64toD32 names
in this case the src and dst types are the same (D64)
and D32 merely indicates the range to which the value is
rounded
so which is it?
> Comment from Florian:
> > For s390 we also need:
> > IROp description s390 insn
> >
> > Iop_I64StoD128 IRRoundingMode(I32) x signed I64 -> D128 CXGTR
> > Iop_I32StoD64 signed I32 -> D64 CDFTR
> > Iop_I32StoD128 signed I32 -> D128 CXFTR
> > Iop_I64UtoD64 IRRoundingMode(I32) x unsigned I64 -> D64 CDLGTR
> > Iop_I64UtoD128 IRRoundingMode(I32) x unsigned I64 -> D128 CXLGTR
> > Iop_I32UtoD64 unsigned I32 -> D64 CDLFTR
> > Iop_I32UtoD128 unsigned I32 -> D128 CXLFTR
> >
> > We need both: conversion to signed and unsigned int
> >
> > IROp description s390 insn
> >
> > Iop_D64toI64S IRRoundingMode(I32) x D64 -> signed I64 CGDTR(A)
> > Iop_D128toI64S IRRoundingMode(I32) x D128 -> signed I64 CGXTR(A)
> > Iop_D64toI32S IRRoundingMode(I32) x D64 -> signed I32 CFDTR
> > Iop_D128toI32S IRRoundingMode(I32) x D128 -> signed I32 CFXTR
> > Iop_D64toI64U IRRoundingMode(I32) x D64 -> unsigned I64 CLGDTR
> > Iop_D128toI64U IRRoundingMode(I32) x D128 -> unsigned I64 CLGXTR
> > Iop_D64toI32U IRRoundingMode(I32) x D64 -> unsigned I32 CLFDTR
> > Iop_D128toI32U IRRoundingMode(I32) x D128 -> unsigned I32 CLFXTR
> >
> > Note, the new IRops for conversion to 32-bit wide results and from D128.
>
> Comment from Christian Borntraege:
> > > The PFPO insn is used to convert between binary floating point and
> > > decimal floating point. Since we have 3 formats each, that makes 9
> > > conversion ops for each direction:
> > >
> > > Iop_D32toF32 IRRoundingMode(I32) x D32 -> F32
> > > Iop_D32toF64 IRRoundingMode(I32) x D32 -> F64
> > > Iop_D32toF128 IRRoundingMode(I32) x D32 -> F128
> > > Iop_D64toF32 IRRoundingMode(I32) x D64 -> F32
> > > Iop_D64toF64 IRRoundingMode(I32) x D64 -> F64
> > > Iop_D64toF128 IRRoundingMode(I32) x D64 -> F128
> > > Iop_D128toF32 IRRoundingMode(I32) x D128 -> F32
> > > Iop_D128toF64 IRRoundingMode(I32) x D128 -> F64
> > > Iop_D128toF128 IRRoundingMode(I32) x D128 -> F128
> > >
> > > Iop_F32toD32 IRRoundingMode(I32) x F32 -> D32
> > > Iop_F32toD64 IRRoundingMode(I32) x F32 -> D64
> > > Iop_F32toD128 IRRoundingMode(I32) x F32 -> D128
> > > Iop_F64toD32 IRRoundingMode(I32) x F64 -> D32
> > > Iop_F64toD64 IRRoundingMode(I32) x F64 -> D64
> > > Iop_F64toD128 IRRoundingMode(I32) x F64 -> D128
> > > Iop_F128toD32 IRRoundingMode(I32) x F128 -> D32
> > > Iop_F128toD64 IRRoundingMode(I32) x F128 -> D64
> > > Iop_F128toD128 IRRoundingMode(I32) x F128 -> D128
> >
> > If you look at pfpo, then the instruction has the same tricky
> > behaviour as EXecute. Since a self checking prefix and 18 Iops is
> >
> > pretty expensive I think that pfpo qualifies for a helper.
>
> These conversion modes are specifically support by s390 but not POWER.
> POWER supports a subset of the conversions supported by s390. This is
> one of the areas where I feel we should defer the decision on adding more
> Iops, using a helper function or emulating these conversions with the
> subset of conversions that have been proposed until the s390 team is ready
> to add the s390 support to Valgrind. This is beyond the scope of what is
> needed for me to add the POWER support. But I think it is important that
> the issue has been raised to understand the full scope of what is needed
> by both architectures.
Ok. I agree .. just add the conversions needed for POWER, unless
Christian/Florian want to also add the S390 needed conversions now
(I am unclear if you do, or not)
>
> > > IRRoundingExceptionModes(I32) x D64 -> I64
> > > Iop_D64toI64
> >
> > this is underspecified .. you need to decide whether that's a
> > conversion to signed or unsigned I64 (or maybe you need both)
> > and call them Iop_D64toI64S or Iop_D64toI64U respectively.
> > (I think you comment about this further down in the doc.)
> > I mention this partly because sorting out such ambiguity in the
> > past for the Fxx->Ixx conversions required a lot of hoop
> > jumping, so we might as well get it straightened out up front.
>
> OK, should be convert to signed integer. Changed the name to
> Iop_D64toI64S.
Good.
> > > ROUNDING INSTRUCTIONS
> > > -----------------------
> > > IRRoundingMode(I32) x D64 -> D64
> > > Iop_RoundD64
> > >
> > > IRRoundingMode(I32) x D128 -> D128
> > > Iop_RoundD128
> >
> > ok
>
> Comment from Florian:
> > These should be named Iop_RoundD64toInt and Iop_RoundD128toInt for
> > symmetry in naming with binary floating point ops.
>
> I am OK with the name change. Comments?
/me agrees with Florian.
>
> > > COMPARE INSTRUCTIONS
> > > -----------------------
> > > D64 x D64 -> IRCmpF64Result(I32)
> > > Iop_CmpD64
> > >
> > > D128 x D128 -> IRCmpF64Result(I32)
> > > Iop_CmpD128
> >
> > ok
>
> Comment from Florian:
> > OK. I would use IRCmpD64Result and IRCmpD128Result. That allows
> > us to use a different encoding, which may be desirable.
>
> I am OK with the name change. Comments?
Fine by me.
> > > QUANTIZE AND ROUND INSTRUCTIONS
> > > -------------------------------
> > > IRRoundingMode(I32) x D64-> D64
> > > Iop_QuantizeID64,
> > >
> > > IRRoundingMode(I32) x D128-> D128
> > > Iop_QuantizeID128
> > >
> > > IRRoundingMode(I32) x D64 x D64 -> D64
> > > Iop_QuantizeD64
> > >
> > > IRRoundingMode(I32) x D128 x D128 -> D128
> > > Iop_QuantizeD128
> >
> > I'm not clear what the ID vs D signifies in these names. Can
> > they instead be called Iop_Quantize{Un,Bin}{D64,D128} to denote
> > unary vs binary ness (ignoring the rounding mode arg which is
> > present in all 4 cases).
>
> The first two with the I are for immediate value of the exponent for the
> quantization operation. Remember above, I had the
> IRRoundingModeAndEponent(I32) specification. It was also there for
> specifying the immediate value. I didn't realize that I had a redundant
> way of specifying the immediate exponent value. So, as said above, we drop
> IRRoundingModeAndEponent(I32) specification.
>
> > What is quantization, anyway (in the context of DFP I mean)?
> > Does it have any analogue in traditional IEEE754 FP ?
>
> Quantization is the process of rounding a number to a specified exponent as
> mentioned earlier. For example, the U.S. specifies a dollar amount with at
> most two fractional digits, for example $12.98. When doing a computation
> involving money, the quantization instruction would be used to round the
> result to two fractional digits.
>
> The immediate value to specify the desired exponent is specific to POWER.
> Both s390 and POWER have instructions for changing the exponent of
> (quantizing) a value in register A to match the exponent of a value in
> register B. I think we should remove the Iops Iop_QuantizeID64 and
> Iop_QuantizeID128 for specify an immediate exponent. For the POWER
> instruction that specifies the immediate exponent, I can just generate a
> DFP number with the desired exponent and pass that as the value in
> register B as the target exponent. This will help minimize the number of
> new Iops.
Ok by me.
> > > IRRoundingMode(I32) x D64 x D64 -> D64
> > > Iop_SignificanceRoundD64
> > >
> > > IRRoundingMode(I32) x D128 x D128 -> D128
> > > Iop_SignificanceRoundD128
> > >
> > >
> > > EXTRACT AND INSERT INSTRUCTIONS
> > > -------------------------------
> > > D64 -> I64
> > > Iop_ExtractExpD64
> > >
> > > D128 -> I64
> > > Iop_ExtractExpD128
> >
> > The exponent really needs 64 bits? Can it be 32 bits? That
> > might allow for more efficient code generation for 32 bit targets.
>
> The biased exponent could be stored as a 32 bit biased integer. The
> functionality of the specific instruction that this Iop was intended for
> specifies the exponent will be stored in a floating point register in a
> signed integer format. I agree we can make the target be I32 and then
> just handle the I32 to I64 conversion as needed for the specific
> instruction. The exponent for any DFP number will easily fit in less then
> 31 bits.
>
> I will change the above two Iops to return an I32 value.
Good.
>
> Comment from Florian:
> > Do we need to support these at all? In other words, does GCC issue these
> > or do they show up in hand crafted assembler shipped with GCC/GLIBC?
> > I don't know but will find out (for s390).
>
> Yes, the libdfp and binutils use them.
>
> > > I64 x I64 -> D64
> > > Iop_InsertExpD64
> > >
> > > I64 x I128 -> D128
> > > Iop_InsertExpD128
> >
> > ditto comment
>
> ditto above that we do need these Iops for instructions that are used.
So (unclear) as with ExtractExp, you'll change the exp value to be an I32
instead of an I64, yes?
> > > SHIFT SIGNIFICAND INSTRUCTIONS
> > > -------------------------------
> > > U16 x D64 -> D64
> > > Iop_ShlD64, Iop_ShrD64
> > >
> > > U16 x D128 -> D128
> > > Iop_ShlD128, Iop_ShrD128
> >
> > two things: (1) does the shift amount need to be 16 bits?
> > For all the other shifting style ops we have, the shift amount
> > is encoded in 8 bits (Ity_I8) and I would prefer to stick with
> > that for consistency, if possible. (2) pls put the shift amount
> > as the second argument, not the first, as that too is consistent
> > with all other shift ops we have (eg, Iop_Shr64)
>
> OK, changed shift to U8 and made it D64 x U8 -> D64; D128 x U8 -> D128
Good.
> > ---------------
> >
> > > This section give the detailed mapping of Power and s390
> > >
> > > instructions to the proposed DFP Iops or how they would be implemented
> > > with the existing Iops and the proposed DFP Iops.
> >
> > I'll comment on this second half of the proposal tomorrow.
> >
> > J
>
> I have not seen any additional comments. It is probably best to focus on
> resolving the above issues first as the second part is just a more detailed
> discussion of the above summary of the Iops. Once we have agreement on the
> above discussion points, I will update and post version 2 of the proposal.
Yes, good plan.
J
|
|
From: Philippe W. <phi...@sk...> - 2012-01-19 04:30:32
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1) Assembler: GNU assembler version 2.21.53.0.1-3.fc16 20110716 C library: GNU C Library development release version 2.14.90 uname -mrs: Linux 3.1.0-0.rc9.git0.2.fc16.kh.ppc64 ppc64 Vendor version: Fedora release 16 (Verne) Nightly build on gcc110 ( Fedora release 16 (Verne), ppc64 ) Started at 2012-01-18 20:00:06 PST Ended at 2012-01-18 20:29:54 PST 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 == 507 tests, 8 stderr failures, 8 stdout failures, 1 stderrB failure, 1 stdoutB failure, 2 post failures == gdbserver_tests/mcmain_pic (stdout) gdbserver_tests/mcmain_pic (stderr) gdbserver_tests/mcmain_pic (stdoutB) gdbserver_tests/mcmain_pic (stderrB) memcheck/tests/ppc32/power_ISA2_05 (stdout) memcheck/tests/ppc32/power_ISA2_05 (stderr) memcheck/tests/ppc64/power_ISA2_05 (stdout) memcheck/tests/ppc64/power_ISA2_05 (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/wrap8 (stdout) memcheck/tests/wrap8 (stderr) massif/tests/big-alloc (post) massif/tests/deep-D (post) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc64/jm-fp (stdout) none/tests/ppc64/jm-vmx (stdout) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) |
|
From: Rich C. <rc...@wi...> - 2012-01-19 04:26:33
|
valgrind revision: 12345
VEX revision: 2241
C compiler: gcc (SUSE Linux) 4.6.2
Assembler: GNU assembler (GNU Binutils; openSUSE Factory) 2.21.1
C library: GNU C Library stable release version 2.14.1 (20111007), by Roland McGrath et al.
uname -mrs: Linux 3.1.0-1-desktop x86_64
Vendor version: Welcome to openSUSE 12.1 "Asparagus" RC 1 - Kernel %r (%t).
Nightly build on groovy ( gcc 4.6.1 Linux 3.1.0-1-desktop x86_64 )
Started at 2012-01-18 21:55:01 CST
Ended at 2012-01-18 22:26:24 CST
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
== 600 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/overlap (stderr)
=================================================
./valgrind-new/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2012-01-18 22:10:49.354620311 -0600
+++ mssnapshot.stderrB.out 2012-01-18 22:16:22.170107574 -0600
@@ -1,5 +1,11 @@
relaying data between gdb and process ....
+Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
+Try: zypper install -C "debuginfo(build-id)=f20c99249f5a5776e1377d3bd728502e3f455a3f"
vgdb-error value changed from 0 to 999999
+Missing separate debuginfo for /lib64/libpthread.so.0
+Try: zypper install -C "debuginfo(build-id)=1f368f83b776815033caab6e389d7030bba4593e"
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=3c6112e7d6b5cd8a95263caf838fa495bc4ac337"
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc212-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc212-s390x 2012-01-18 22:10:54.005585692 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:18:08.551291283 -0600
@@ -75,17 +75,6 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2859)
- by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
- by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
- by 0x........: handle_compress (origin5-bz2.c:4753)
- by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
- by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
- by 0x........: main (origin5-bz2.c:6484)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
-
-Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -131,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc234-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc234-s390x 2012-01-18 22:10:53.960586028 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:18:08.551291283 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2012-01-18 22:10:53.937586198 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:18:08.551291283 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2012-01-18 22:10:54.023585558 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:18:08.551291283 -0600
@@ -12,7 +12,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -21,7 +21,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -30,7 +30,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -41,7 +41,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -52,7 +52,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -63,7 +63,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -74,7 +74,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -85,7 +85,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -96,7 +96,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -107,7 +107,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2012-01-18 22:10:53.933586230 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:18:08.551291283 -0600
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -10,7 +10,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -19,7 +19,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -28,7 +28,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
@@ -39,7 +39,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
@@ -50,7 +50,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
@@ -61,7 +61,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
@@ -72,7 +72,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
@@ -83,7 +83,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
@@ -94,7 +94,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
@@ -105,7 +105,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/overlap.stderr.diff
=================================================
--- overlap.stderr.exp 2012-01-18 22:10:53.970585954 -0600
+++ overlap.stderr.out 2012-01-18 22:18:15.652236816 -0600
@@ -1,9 +1,9 @@
Source and destination overlap in memcpy(0x........, 0x........, 21)
- at 0x........: memcpy (mc_replace_strmem.c:...)
+ at 0x........: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:...)
by 0x........: main (overlap.c:40)
Source and destination overlap in memcpy(0x........, 0x........, 21)
- at 0x........: memcpy (mc_replace_strmem.c:...)
+ at 0x........: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:...)
by 0x........: main (overlap.c:42)
Source and destination overlap in strncpy(0x........, 0x........, 21)
=================================================
./valgrind-old/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2012-01-18 21:55:13.879593669 -0600
+++ mssnapshot.stderrB.out 2012-01-18 22:00:48.001100491 -0600
@@ -1,5 +1,11 @@
relaying data between gdb and process ....
+Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
+Try: zypper install -C "debuginfo(build-id)=f20c99249f5a5776e1377d3bd728502e3f455a3f"
vgdb-error value changed from 0 to 999999
+Missing separate debuginfo for /lib64/libpthread.so.0
+Try: zypper install -C "debuginfo(build-id)=1f368f83b776815033caab6e389d7030bba4593e"
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=3c6112e7d6b5cd8a95263caf838fa495bc4ac337"
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc212-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc212-s390x 2012-01-18 21:55:18.504559140 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:02:33.037317380 -0600
@@ -75,17 +75,6 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2859)
- by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
- by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
- by 0x........: handle_compress (origin5-bz2.c:4753)
- by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
- by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
- by 0x........: main (origin5-bz2.c:6484)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
-
-Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -131,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc234-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc234-s390x 2012-01-18 21:55:18.461559459 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:02:33.037317380 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2012-01-18 21:55:18.437559640 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:02:33.037317380 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2012-01-18 21:55:18.523558997 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:02:33.037317380 -0600
@@ -12,7 +12,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -21,7 +21,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -30,7 +30,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -41,7 +41,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -52,7 +52,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -63,7 +63,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -74,7 +74,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -85,7 +85,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -96,7 +96,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -107,7 +107,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2012-01-18 21:55:18.434559661 -0600
+++ origin5-bz2.stderr.out 2012-01-18 22:02:33.037317380 -0600
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -10,7 +10,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -19,7 +19,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -28,7 +28,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
@@ -39,7 +39,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
@@ -50,7 +50,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
@@ -61,7 +61,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
@@ -72,7 +72,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
@@ -83,7 +83,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
@@ -94,7 +94,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
@@ -105,7 +105,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/overlap.stderr.diff
=================================================
--- overlap.stderr.exp 2012-01-18 21:55:18.471559384 -0600
+++ overlap.stderr.out 2012-01-18 22:02:40.119264587 -0600
@@ -1,9 +1,9 @@
Source and destination overlap in memcpy(0x........, 0x........, 21)
- at 0x........: memcpy (mc_replace_strmem.c:...)
+ at 0x........: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:...)
by 0x........: main (overlap.c:40)
Source and destination overlap in memcpy(0x........, 0x........, 21)
- at 0x........: memcpy (mc_replace_strmem.c:...)
+ at 0x........: memcpy@@GLIBC_2.14 (mc_replace_strmem.c:...)
by 0x........: main (overlap.c:42)
Source and destination overlap in strncpy(0x........, 0x........, 21)
|
|
From: Tom H. <to...@co...> - 2012-01-19 04:06:55
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) Assembler: GNU assembler version 2.18.50.0.6-2 20080403 C library: GNU C Library stable release version 2.8 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 9 (Sulphur) Nightly build on bristol ( x86_64, Fedora 9 ) Started at 2012-01-19 03:41:10 GMT Ended at 2012-01-19 04:06:35 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 == 588 tests, 0 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == none/tests/amd64/sse4-64 (stdout) |
|
From: Tom H. <to...@co...> - 2012-01-19 03:57:15
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2) Assembler: GNU assembler version 2.19.51.0.14-3.fc11 20090722 C library: GNU C Library stable release version 2.10.2 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 11 (Leonidas) Nightly build on bristol ( x86_64, Fedora 11 ) Started at 2012-01-19 03:31:18 GMT Ended at 2012-01-19 03:56:56 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 == 590 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/linux/stack_switch (stderr) memcheck/tests/long_namespace_xml (stderr) none/tests/amd64/sse4-64 (stdout) |
|
From: Rich C. <rc...@wi...> - 2012-01-19 03:54:07
|
valgrind revision: 12345
VEX revision: 2241
C compiler: gcc (SUSE Linux) 4.5.1 20101208 [gcc-4_5-branch revision 167585]
Assembler: GNU assembler (GNU Binutils; openSUSE 11.4) 2.21
C library: GNU C Library stable release version 2.11.3 (20110203), by Roland McGrath et al.
uname -mrs: Linux 2.6.37.6-0.7-desktop x86_64
Vendor version: Welcome to openSUSE 11.4 "Celadon" - Kernel %r (%t).
Nightly build on ultra ( gcc 4.5.1 Linux 2.6.37.6-0.7-desktop x86_64 )
Started at 2012-01-18 21:30:01 CST
Ended at 2012-01-18 21:53:57 CST
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
== 600 tests, 3 stderr failures, 0 stdout failures, 6 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stderrB)
gdbserver_tests/mcleak (stderrB)
gdbserver_tests/mcmain_pic (stderrB)
gdbserver_tests/mcvabits (stderrB)
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/linux/stack_switch (stderr)
memcheck/tests/origin5-bz2 (stderr)
drd/tests/annotate_smart_pointer (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
== 600 tests, 2 stderr failures, 0 stdout failures, 6 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcbreak (stderrB)
gdbserver_tests/mcclean_after_fork (stderrB)
gdbserver_tests/mcleak (stderrB)
gdbserver_tests/mcmain_pic (stderrB)
gdbserver_tests/mcvabits (stderrB)
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/linux/stack_switch (stderr)
memcheck/tests/origin5-bz2 (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Wed Jan 18 21:42:04 2012
--- new.short Wed Jan 18 21:53:57 2012
***************
*** 8,10 ****
! == 600 tests, 2 stderr failures, 0 stdout failures, 6 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcbreak (stderrB)
--- 8,10 ----
! == 600 tests, 3 stderr failures, 0 stdout failures, 6 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/mcbreak (stderrB)
***************
*** 17,18 ****
--- 17,19 ----
memcheck/tests/origin5-bz2 (stderr)
+ drd/tests/annotate_smart_pointer (stderr)
=================================================
./valgrind-new/drd/tests/annotate_smart_pointer.stderr.diff
=================================================
--- annotate_smart_pointer.stderr.exp 2012-01-18 21:42:32.281125215 -0600
+++ annotate_smart_pointer.stderr.out 2012-01-18 21:51:37.448849457 -0600
@@ -1,4 +1,16 @@
+Conflicting store by thread x at 0x........ size 8
+ at 0x........: AnnotateCondVarSignal (unified_annotations.h:?)
+Allocation context: unknown.
+
+Conflicting load by thread x at 0x........ size 8
+ at 0x........: AnnotateCondVarSignal (unified_annotations.h:?)
+ by 0x........: U_AnnotateHappensBefore (unified_annotations.h:?)
+ by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?)
+ by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?)
+ by 0x........: main (annotate_smart_pointer.cpp:?)
+Allocation context: unknown.
+
Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 10 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/gdbserver_tests/mcbreak.stderrB.diff
=================================================
--- mcbreak.stderrB.exp 2012-01-18 21:42:11.598994847 -0600
+++ mcbreak.stderrB.out 2012-01-18 21:45:09.133946579 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
vgdb-error value changed from 999999 to 0
n_errs_found 1 (vgdb-error 0)
vgdb-error value changed from 0 to 0
=================================================
./valgrind-new/gdbserver_tests/mcclean_after_fork.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2012-01-18 21:42:11.598994847 -0600
+++ mcclean_after_fork.stderrB.out 2012-01-18 21:45:10.763799256 -0600
@@ -1,4 +1,6 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
monitor command request to kill this process
Remote connection closed
=================================================
./valgrind-new/gdbserver_tests/mcleak.stderrB.diff
=================================================
--- mcleak.stderrB.exp 2012-01-18 21:42:11.595995114 -0600
+++ mcleak.stderrB.out 2012-01-18 21:45:29.137138476 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
10 bytes in 1 blocks are still reachable in loss record ... of ...
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: f (leak-delta.c:14)
=================================================
./valgrind-new/gdbserver_tests/mcmain_pic.stderrB.diff
=================================================
--- mcmain_pic.stderrB.exp 2012-01-18 21:42:11.601994577 -0600
+++ mcmain_pic.stderrB.out 2012-01-18 21:45:30.759991785 -0600
@@ -1,3 +1,5 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
Remote connection closed
=================================================
./valgrind-new/gdbserver_tests/mcvabits.stderrB.diff
=================================================
--- mcvabits.stderrB.exp 2012-01-18 21:42:11.602994486 -0600
+++ mcvabits.stderrB.out 2012-01-18 21:45:35.531560484 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
Address 0x........ len 10 addressable
Address 0x........ is 0 bytes inside data symbol "undefined"
Address 0x........ len 10 defined
=================================================
./valgrind-new/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2012-01-18 21:42:11.601994577 -0600
+++ mssnapshot.stderrB.out 2012-01-18 21:45:38.758268822 -0600
@@ -1,5 +1,9 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=92ec8fe859846a62345f74696ab349721415587a"
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-new/memcheck/tests/linux/stack_switch.stderr.diff
=================================================
--- stack_switch.stderr.exp 2012-01-18 21:42:15.237665936 -0600
+++ stack_switch.stderr.out 2012-01-18 21:46:40.044729224 -0600
@@ -0,0 +1,3 @@
+Syscall param clone(child_tidptr) contains uninitialised byte(s)
+ ...
+
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc212-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc212-s390x 2012-01-18 21:42:16.140584293 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:47:04.484520188 -0600
@@ -75,17 +75,6 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2859)
- by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
- by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
- by 0x........: handle_compress (origin5-bz2.c:4753)
- by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
- by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
- by 0x........: main (origin5-bz2.c:6484)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
-
-Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -131,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc234-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc234-s390x 2012-01-18 21:42:16.109587094 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:47:04.484520188 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2012-01-18 21:42:16.092588630 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:47:04.484520188 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2012-01-18 21:42:16.154583027 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:47:04.484520188 -0600
@@ -12,7 +12,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -21,7 +21,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -30,7 +30,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -41,7 +41,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -52,7 +52,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -63,7 +63,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -74,7 +74,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -85,7 +85,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -96,7 +96,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -107,7 +107,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2012-01-18 21:42:16.089588903 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:47:04.484520188 -0600
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -10,7 +10,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -19,7 +19,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -28,7 +28,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
@@ -39,7 +39,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
@@ -50,7 +50,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
@@ -61,7 +61,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
@@ -72,7 +72,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
@@ -83,7 +83,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
@@ -94,7 +94,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
@@ -105,7 +105,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
<truncated beyond 100 lines>
=================================================
./valgrind-old/gdbserver_tests/mcbreak.stderrB.diff
=================================================
--- mcbreak.stderrB.exp 2012-01-18 21:30:15.484691535 -0600
+++ mcbreak.stderrB.out 2012-01-18 21:33:19.436094728 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
vgdb-error value changed from 999999 to 0
n_errs_found 1 (vgdb-error 0)
vgdb-error value changed from 0 to 0
=================================================
./valgrind-old/gdbserver_tests/mcclean_after_fork.stderrB.diff
=================================================
--- mcclean_after_fork.stderrB.exp 2012-01-18 21:30:15.484691535 -0600
+++ mcclean_after_fork.stderrB.out 2012-01-18 21:33:21.069947320 -0600
@@ -1,4 +1,6 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
monitor command request to kill this process
Remote connection closed
=================================================
./valgrind-old/gdbserver_tests/mcleak.stderrB.diff
=================================================
--- mcleak.stderrB.exp 2012-01-18 21:30:15.479691987 -0600
+++ mcleak.stderrB.out 2012-01-18 21:33:39.213310407 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
10 bytes in 1 blocks are still reachable in loss record ... of ...
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: f (leak-delta.c:14)
=================================================
./valgrind-old/gdbserver_tests/mcmain_pic.stderrB.diff
=================================================
--- mcmain_pic.stderrB.exp 2012-01-18 21:30:15.487691265 -0600
+++ mcmain_pic.stderrB.out 2012-01-18 21:33:40.854162367 -0600
@@ -1,3 +1,5 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
Remote connection closed
=================================================
./valgrind-old/gdbserver_tests/mcvabits.stderrB.diff
=================================================
--- mcvabits.stderrB.exp 2012-01-18 21:30:15.488691175 -0600
+++ mcvabits.stderrB.out 2012-01-18 21:33:45.592734850 -0600
@@ -1,5 +1,7 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
Address 0x........ len 10 addressable
Address 0x........ is 0 bytes inside data symbol "undefined"
Address 0x........ len 10 defined
=================================================
./valgrind-old/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2012-01-18 21:30:15.487691265 -0600
+++ mssnapshot.stderrB.out 2012-01-18 21:33:48.803445177 -0600
@@ -1,5 +1,9 @@
relaying data between gdb and process ....
vgdb-error value changed from 0 to 999999
+
+
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=92ec8fe859846a62345f74696ab349721415587a"
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-old/memcheck/tests/linux/stack_switch.stderr.diff
=================================================
--- stack_switch.stderr.exp 2012-01-18 21:30:19.104364936 -0600
+++ stack_switch.stderr.out 2012-01-18 21:34:49.635952302 -0600
@@ -0,0 +1,3 @@
+Syscall param clone(child_tidptr) contains uninitialised byte(s)
+ ...
+
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc212-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc212-s390x 2012-01-18 21:30:20.016282667 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:35:13.877760382 -0600
@@ -75,17 +75,6 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2859)
- by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
- by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
- by 0x........: handle_compress (origin5-bz2.c:4753)
- by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
- by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
- by 0x........: main (origin5-bz2.c:6484)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
-
-Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -131,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc234-s390x
=================================================
--- origin5-bz2.stderr.exp-glibc234-s390x 2012-01-18 21:30:19.985285463 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:35:13.877760382 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2012-01-18 21:30:19.968286997 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:35:13.877760382 -0600
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
+ by 0x........: g_serviceFn (origin5-bz2.c:6429)
+ by 0x........: default_bzalloc (origin5-bz2.c:4470)
+ by 0x........: BZ2_decompress (origin5-bz2.c:1578)
+ by 0x........: BZ2_bzDecompress (origin5-bz2.c:5192)
+ by 0x........: BZ2_bzBuffToBuffDecompress (origin5-bz2.c:5678)
+ by 0x........: main (origin5-bz2.c:6498)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2012-01-18 21:30:20.030281403 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:35:13.877760382 -0600
@@ -12,7 +12,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -21,7 +21,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
by 0x........: handle_compress (origin5-bz2.c:4750)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -30,7 +30,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -41,7 +41,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -52,7 +52,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -63,7 +63,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -74,7 +74,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -85,7 +85,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -96,7 +96,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -107,7 +107,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 4
+Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -120,6 +120,12 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6512)
- Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6479)
+ Uninitialised value was created by a heap allocation
+ at 0x........: malloc (vg_replace_malloc.c:...)
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2012-01-18 21:30:19.965287267 -0600
+++ origin5-bz2.stderr.out 2012-01-18 21:35:13.877760382 -0600
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -10,7 +10,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -19,7 +19,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: copy_input_until_stop (origin5-bz2.c:4686)
@@ -28,7 +28,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2820)
@@ -39,7 +39,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2823)
@@ -50,7 +50,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2854)
@@ -61,7 +61,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2858)
@@ -72,7 +72,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2963)
@@ -83,7 +83,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: mainSort (origin5-bz2.c:2964)
@@ -94,7 +94,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
at 0x........: fallbackSort (origin5-bz2.c:2269)
@@ -105,7 +105,7 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 8
<truncated beyond 100 lines>
|
|
From: Tom H. <to...@co...> - 2012-01-19 03:49:54
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.4.5 20101112 (Red Hat 4.4.5-2) Assembler: GNU assembler version 2.20.51.0.2-20.fc13 20091009 C library: GNU C Library stable release version 2.12.2 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 13 (Goddard) Nightly build on bristol ( x86_64, Fedora 13 ) Started at 2012-01-19 03:21:26 GMT Ended at 2012-01-19 03:49:29 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 == 590 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/linux/stack_switch (stderr) helgrind/tests/pth_barrier3 (stderr) |
|
From: Tom H. <to...@co...> - 2012-01-19 03:43:24
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.5.1 20100924 (Red Hat 4.5.1-4) Assembler: GNU assembler version 2.20.51.0.7-8.fc14 20100318 C library: GNU C Library stable release version 2.13 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 14 (Laughlin) Nightly build on bristol ( x86_64, Fedora 14 ) Started at 2012-01-19 03:11:33 GMT Ended at 2012-01-19 03:42: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 == 604 tests, 2 stderr failures, 0 stdout failures, 1 stderrB failure, 2 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallWSRU (stderrB) gdbserver_tests/nlcontrolc (stdoutB) gdbserver_tests/nlpasssigalrm (stdoutB) memcheck/tests/linux/stack_switch (stderr) memcheck/tests/origin5-bz2 (stderr) |
|
From: Tom H. <to...@co...> - 2012-01-19 03:28:01
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.6.1 20110908 (Red Hat 4.6.1-9) Assembler: GNU assembler version 2.21.51.0.6-6.fc15 20110118 C library: GNU C Library stable release version 2.14.1 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 15 (Lovelock) Nightly build on bristol ( x86_64, Fedora 15 ) Started at 2012-01-19 03:02:36 GMT Ended at 2012-01-19 03:27:31 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 == 604 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/origin5-bz2 (stderr) memcheck/tests/overlap (stderr) |
|
From: Tom H. <to...@co...> - 2012-01-19 03:23:59
|
valgrind revision: 12345 VEX revision: 2241 C compiler: gcc (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1) Assembler: GNU assembler version 2.21.53.0.1-6.fc16 20110716 C library: GNU C Library development release version 2.14.90 uname -mrs: Linux 3.1.0-7.fc16.x86_64 x86_64 Vendor version: Fedora release 16 (Verne) Nightly build on bristol ( x86_64, Fedora 16 ) Started at 2012-01-19 02:52:18 GMT Ended at 2012-01-19 03:23:41 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 == 604 tests, 3 stderr failures, 0 stdout failures, 1 stderrB failure, 2 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallWSRU (stderrB) gdbserver_tests/nlcontrolc (stdoutB) gdbserver_tests/nlpasssigalrm (stdoutB) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/overlap (stderr) memcheck/tests/str_tester (stderr) |
|
From: Christian B. <bor...@de...> - 2012-01-19 03:14:56
|
valgrind revision: 12345 VEX revision: 2241 GCC version: gcc (SUSE Linux) 4.3.4 [gcc-4_3-branch revision 152973] C library: GNU C Library stable release version 2.11.1 (20100118), by Roland McGrath et al. uname -mrs: Linux 2.6.32.49-0.3-default s390x Vendor version: Welcome to SUSE Linux Enterprise Server 11 SP1 (s390x) - Kernel %r (%t). Nightly build on sless390 ( SUSE Linux Enterprise Server 11 SP1 gcc 4.3.4 on z196 (s390x) ) Started at 2012-01-19 03:45:01 CET Ended at 2012-01-19 04:14:46 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 == 515 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/tc04_free_lock (stderr) drd/tests/tc09_bad_unlock (stderr) |
|
From: <br...@ac...> - 2012-01-19 03:13:01
|
valgrind revision: 12345
VEX revision: 2241
C compiler: gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-3)
Assembler: GNU assembler 2.15.92.0.2 20040927
C library: GNU C Library stable release version 2.3.4
uname -mrs: Linux 2.6.9-42.EL s390x
Vendor version: Red Hat Enterprise Linux AS release 4 (Nahant Update 4)
Nightly build on z900 ( s390x build on z900 )
Started at 2012-01-18 19:30:14 EST
Ended at 2012-01-18 22:20:43 EST
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
== 479 tests, 8 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/manuel3 (stderr)
memcheck/tests/partial_load_ok (stderr)
memcheck/tests/varinfo6 (stderr)
helgrind/tests/tc09_bad_unlock (stderr)
helgrind/tests/tc18_semabuse (stderr)
helgrind/tests/tc20_verifywrap (stderr)
drd/tests/tc04_free_lock (stderr)
drd/tests/tc09_bad_unlock (stderr)
=================================================
./valgrind-new/drd/tests/tc04_free_lock.stderr.diff-ppc
=================================================
--- tc04_free_lock.stderr.exp-ppc 2012-01-18 20:56:06.000000000 -0500
+++ tc04_free_lock.stderr.out 2012-01-18 22:17:45.000000000 -0500
@@ -7,28 +7,22 @@
by 0x........: main (tc04_free_lock.c:20)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:26)
+ at 0x........: bar (tc04_free_lock.c:40)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
by 0x........: main (tc04_free_lock.c:26)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: foo (tc04_free_lock.c:47)
- by 0x........: main (tc04_free_lock.c:27)
+ at 0x........: foo (tc04_free_lock.c:49)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc04_free_lock.stderr.diff-x86
=================================================
--- tc04_free_lock.stderr.exp-x86 2012-01-18 20:56:07.000000000 -0500
+++ tc04_free_lock.stderr.out 2012-01-18 22:17:45.000000000 -0500
@@ -8,7 +8,8 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:26)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
@@ -16,19 +17,12 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: foo (tc04_free_lock.c:49)
- by 0x........: main (tc04_free_lock.c:27)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-glibc2.8
=================================================
--- tc09_bad_unlock.stderr.exp-glibc2.8 2012-01-18 20:56:07.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 22:18:05.000000000 -0500
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: (below main)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: (below main)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-ppc
=================================================
--- tc09_bad_unlock.stderr.exp-ppc 2012-01-18 20:56:06.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 22:18:05.000000000 -0500
@@ -25,8 +25,8 @@
by 0x........: main (tc09_bad_unlock.c:49)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:49)
+ at 0x........: nearly_main (tc09_bad_unlock.c:45)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:50)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/drd/tests/tc09_bad_unlock.stderr.diff-x86
=================================================
--- tc09_bad_unlock.stderr.exp-x86 2012-01-18 20:56:06.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 22:18:05.000000000 -0500
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: main (tc09_bad_unlock.c:49)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: main (tc09_bad_unlock.c:50)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/helgrind/tests/tc09_bad_unlock.stderr.diff
=================================================
--- tc09_bad_unlock.stderr.exp 2012-01-18 20:55:24.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 21:58:08.000000000 -0500
@@ -42,14 +42,6 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:49)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:49)
-
---------------------
----------------------------------------------------------------
@@ -110,16 +102,8 @@
----------------------------------------------------------------
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-----------------------------------------------------------------
-
Thread #x: Exiting thread still holds 1 lock
...
-ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 9 errors from 9 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/helgrind/tests/tc18_semabuse.stderr.diff
=================================================
--- tc18_semabuse.stderr.exp 2012-01-18 20:55:24.000000000 -0500
+++ tc18_semabuse.stderr.out 2012-01-18 21:59:01.000000000 -0500
@@ -18,13 +18,5 @@
by 0x........: sem_wait (hg_intercepts.c:...)
by 0x........: main (tc18_semabuse.c:34)
-----------------------------------------------------------------
-Thread #x's call to sem_post failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: sem_post_WRK (hg_intercepts.c:...)
- by 0x........: sem_post (hg_intercepts.c:...)
- by 0x........: main (tc18_semabuse.c:37)
-
-
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/helgrind/tests/tc20_verifywrap.stderr.diff
=================================================
--- tc20_verifywrap.stderr.exp 2012-01-18 20:55:23.000000000 -0500
+++ tc20_verifywrap.stderr.out 2012-01-18 22:00:10.000000000 -0500
@@ -1,7 +1,7 @@
------- This is output for >= glibc 2.4 ------
+------ This is output for < glibc 2.4 ------
---------------- pthread_create/join ----------------
@@ -45,13 +45,6 @@
----------------------------------------------------------------
-Thread #x's call to pthread_mutex_init failed
- with error code 95 (EOPNOTSUPP: Operation not supported on transport endpoint)
- at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:92)
-
-----------------------------------------------------------------
-
Thread #x: pthread_mutex_destroy of a locked mutex
at 0x........: pthread_mutex_destroy (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:102)
@@ -63,26 +56,8 @@
at 0x........: pthread_mutex_destroy (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:102)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_lock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_lock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:108)
-
-----------------------------------------------------------------
-Thread #x's call to pthread_mutex_trylock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_trylock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:116)
-
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_timedlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_timedlock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:121)
+make pthread_mutex_lock fail: skipped on glibc < 2.4
----------------------------------------------------------------
@@ -90,13 +65,6 @@
at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:125)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:125)
-
---------------- pthread_cond_wait et al ----------------
@@ -215,14 +183,6 @@
by 0x........: sem_wait (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:242)
-----------------------------------------------------------------
-
-Thread #x's call to sem_post failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: sem_post_WRK (hg_intercepts.c:...)
- by 0x........: sem_post (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:245)
-
FIXME: can't figure out how to verify wrap of sem_post
@@ -235,4 +195,4 @@
...
-ERROR SUMMARY: 23 errors from 23 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 17 errors from 17 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/memcheck/tests/manuel3.stderr.diff
=================================================
--- manuel3.stderr.exp 2012-01-18 20:55:37.000000000 -0500
+++ manuel3.stderr.out 2012-01-18 21:27:59.000000000 -0500
@@ -1,4 +1,3 @@
Conditional jump or move depends on uninitialised value(s)
- at 0x........: gcc_cant_inline_me (manuel3.c:22)
- by 0x........: main (manuel3.c:14)
+ at 0x........: main (manuel3.c:12)
=================================================
./valgrind-new/memcheck/tests/partial_load_ok.stderr.diff
=================================================
--- partial_load_ok.stderr.exp 2012-01-18 20:55:36.000000000 -0500
+++ partial_load_ok.stderr.out 2012-01-18 21:32:33.000000000 -0500
@@ -1,7 +1,13 @@
-Invalid read of size 4
+Invalid read of size 1
+ at 0x........: main (partial_load.c:16)
+ Address 0x........ is 0 bytes after a block of size 7 alloc'd
+ at 0x........: calloc (vg_replace_malloc.c:...)
+ by 0x........: main (partial_load.c:14)
+
+Invalid read of size 8
at 0x........: main (partial_load.c:23)
- Address 0x........ is 1 bytes inside a block of size 4 alloc'd
+ Address 0x........ is 1 bytes inside a block of size 8 alloc'd
at 0x........: calloc (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:20)
@@ -11,9 +17,9 @@
at 0x........: calloc (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:28)
-Invalid read of size 4
+Invalid read of size 8
at 0x........: main (partial_load.c:37)
- Address 0x........ is 0 bytes inside a block of size 4 free'd
+ Address 0x........ is 0 bytes inside a block of size 8 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:36)
@@ -25,4 +31,4 @@
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/memcheck/tests/partial_load_ok.stderr.diff64
=================================================
--- partial_load_ok.stderr.exp64 2012-01-18 20:55:36.000000000 -0500
+++ partial_load_ok.stderr.out 2012-01-18 21:32:33.000000000 -0500
@@ -1,4 +1,10 @@
+Invalid read of size 1
+ at 0x........: main (partial_load.c:16)
+ Address 0x........ is 0 bytes after a block of size 7 alloc'd
+ at 0x........: calloc (vg_replace_malloc.c:...)
+ by 0x........: main (partial_load.c:14)
+
Invalid read of size 8
at 0x........: main (partial_load.c:23)
Address 0x........ is 1 bytes inside a block of size 8 alloc'd
@@ -25,4 +31,4 @@
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-new/memcheck/tests/varinfo6.stderr.diff
=================================================
--- varinfo6.stderr.exp 2012-01-18 20:55:36.000000000 -0500
+++ varinfo6.stderr.out 2012-01-18 21:40:00.000000000 -0500
@@ -7,8 +7,7 @@
by 0x........: BZ2_bzCompress (varinfo6.c:4860)
by 0x........: BZ2_bzBuffToBuffCompress (varinfo6.c:5667)
by 0x........: main (varinfo6.c:6517)
- Location 0x........ is 2 bytes inside local var "budget"
- declared at varinfo6.c:3115, in frame #2 of thread 1
+ Address 0x........ is on thread 1's stack
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo6.c:34)
=================================================
./valgrind-new/memcheck/tests/varinfo6.stderr.diff-ppc64
=================================================
--- varinfo6.stderr.exp-ppc64 2012-01-18 20:55:36.000000000 -0500
+++ varinfo6.stderr.out 2012-01-18 21:40:00.000000000 -0500
@@ -1,5 +1,5 @@
Uninitialised byte(s) found during client check request
- at 0x........: croak (varinfo6.c:35)
+ at 0x........: croak (varinfo6.c:34)
by 0x........: mainSort (varinfo6.c:2999)
by 0x........: BZ2_blockSort (varinfo6.c:3143)
by 0x........: BZ2_compressBlock (varinfo6.c:4072)
@@ -10,7 +10,7 @@
Address 0x........ is on thread 1's stack
Uninitialised byte(s) found during client check request
- at 0x........: croak (varinfo6.c:35)
+ at 0x........: croak (varinfo6.c:34)
by 0x........: BZ2_decompress (varinfo6.c:1699)
by 0x........: BZ2_bzDecompress (varinfo6.c:5230)
by 0x........: BZ2_bzBuffToBuffDecompress (varinfo6.c:5715)
=================================================
./valgrind-old/drd/tests/tc04_free_lock.stderr.diff-ppc
=================================================
--- tc04_free_lock.stderr.exp-ppc 2012-01-18 19:31:09.000000000 -0500
+++ tc04_free_lock.stderr.out 2012-01-18 20:52:19.000000000 -0500
@@ -7,28 +7,22 @@
by 0x........: main (tc04_free_lock.c:20)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:26)
+ at 0x........: bar (tc04_free_lock.c:40)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
by 0x........: main (tc04_free_lock.c:26)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: foo (tc04_free_lock.c:47)
- by 0x........: main (tc04_free_lock.c:27)
+ at 0x........: foo (tc04_free_lock.c:49)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/tc04_free_lock.stderr.diff-x86
=================================================
--- tc04_free_lock.stderr.exp-x86 2012-01-18 19:31:09.000000000 -0500
+++ tc04_free_lock.stderr.out 2012-01-18 20:52:19.000000000 -0500
@@ -8,7 +8,8 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:26)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
by 0x........: bar (tc04_free_lock.c:38)
@@ -16,19 +17,12 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: foo (tc04_free_lock.c:49)
- by 0x........: main (tc04_free_lock.c:27)
+ by 0x........: process_dl_debug (in /lib64/ld-2.3.4.so)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: foo (tc04_free_lock.c:46)
by 0x........: main (tc04_free_lock.c:27)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: bar (tc04_free_lock.c:40)
- by 0x........: main (tc04_free_lock.c:28)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_lock (drd_pthread_intercepts.c:?)
- by 0x........: bar (tc04_free_lock.c:38)
- by 0x........: main (tc04_free_lock.c:28)
-
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/tc09_bad_unlock.stderr.diff-glibc2.8
=================================================
--- tc09_bad_unlock.stderr.exp-glibc2.8 2012-01-18 19:31:09.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 20:52:39.000000000 -0500
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: (below main)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: (below main)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/tc09_bad_unlock.stderr.diff-ppc
=================================================
--- tc09_bad_unlock.stderr.exp-ppc 2012-01-18 19:31:08.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 20:52:39.000000000 -0500
@@ -25,8 +25,8 @@
by 0x........: main (tc09_bad_unlock.c:49)
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:49)
+ at 0x........: nearly_main (tc09_bad_unlock.c:45)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:50)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/tc09_bad_unlock.stderr.diff-x86
=================================================
--- tc09_bad_unlock.stderr.exp-x86 2012-01-18 19:31:09.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 20:52:39.000000000 -0500
@@ -26,7 +26,7 @@
Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: main (tc09_bad_unlock.c:49)
+ by 0x........: ???
mutex 0x........ was first observed at:
at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
by 0x........: nearly_main (tc09_bad_unlock.c:31)
@@ -47,13 +47,5 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:50)
-Destroying locked mutex: mutex 0x........, recursion count 1, owner 1.
- at 0x........: nearly_main (tc09_bad_unlock.c:45)
- by 0x........: main (tc09_bad_unlock.c:50)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: nearly_main (tc09_bad_unlock.c:31)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-ERROR SUMMARY: 8 errors from 7 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 8 errors from 6 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/helgrind/tests/tc09_bad_unlock.stderr.diff
=================================================
--- tc09_bad_unlock.stderr.exp 2012-01-18 19:30:23.000000000 -0500
+++ tc09_bad_unlock.stderr.out 2012-01-18 20:32:50.000000000 -0500
@@ -42,14 +42,6 @@
by 0x........: nearly_main (tc09_bad_unlock.c:41)
by 0x........: main (tc09_bad_unlock.c:49)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:49)
-
---------------------
----------------------------------------------------------------
@@ -110,16 +102,8 @@
----------------------------------------------------------------
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: nearly_main (tc09_bad_unlock.c:41)
- by 0x........: main (tc09_bad_unlock.c:50)
-
-----------------------------------------------------------------
-
Thread #x: Exiting thread still holds 1 lock
...
-ERROR SUMMARY: 11 errors from 11 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 9 errors from 9 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/helgrind/tests/tc18_semabuse.stderr.diff
=================================================
--- tc18_semabuse.stderr.exp 2012-01-18 19:30:23.000000000 -0500
+++ tc18_semabuse.stderr.out 2012-01-18 20:33:40.000000000 -0500
@@ -18,13 +18,5 @@
by 0x........: sem_wait (hg_intercepts.c:...)
by 0x........: main (tc18_semabuse.c:34)
-----------------------------------------------------------------
-Thread #x's call to sem_post failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: sem_post_WRK (hg_intercepts.c:...)
- by 0x........: sem_post (hg_intercepts.c:...)
- by 0x........: main (tc18_semabuse.c:37)
-
-
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/helgrind/tests/tc20_verifywrap.stderr.diff
=================================================
--- tc20_verifywrap.stderr.exp 2012-01-18 19:30:23.000000000 -0500
+++ tc20_verifywrap.stderr.out 2012-01-18 20:34:45.000000000 -0500
@@ -1,7 +1,7 @@
------- This is output for >= glibc 2.4 ------
+------ This is output for < glibc 2.4 ------
---------------- pthread_create/join ----------------
@@ -45,13 +45,6 @@
----------------------------------------------------------------
-Thread #x's call to pthread_mutex_init failed
- with error code 95 (EOPNOTSUPP: Operation not supported on transport endpoint)
- at 0x........: pthread_mutex_init (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:92)
-
-----------------------------------------------------------------
-
Thread #x: pthread_mutex_destroy of a locked mutex
at 0x........: pthread_mutex_destroy (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:102)
@@ -63,26 +56,8 @@
at 0x........: pthread_mutex_destroy (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:102)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_lock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_lock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:108)
-
-----------------------------------------------------------------
-Thread #x's call to pthread_mutex_trylock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_trylock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:116)
-
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_timedlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_timedlock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:121)
+make pthread_mutex_lock fail: skipped on glibc < 2.4
----------------------------------------------------------------
@@ -90,13 +65,6 @@
at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:125)
-----------------------------------------------------------------
-
-Thread #x's call to pthread_mutex_unlock failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: pthread_mutex_unlock (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:125)
-
---------------- pthread_cond_wait et al ----------------
@@ -215,14 +183,6 @@
by 0x........: sem_wait (hg_intercepts.c:...)
by 0x........: main (tc20_verifywrap.c:242)
-----------------------------------------------------------------
-
-Thread #x's call to sem_post failed
- with error code 22 (EINVAL: Invalid argument)
- at 0x........: sem_post_WRK (hg_intercepts.c:...)
- by 0x........: sem_post (hg_intercepts.c:...)
- by 0x........: main (tc20_verifywrap.c:245)
-
FIXME: can't figure out how to verify wrap of sem_post
@@ -235,4 +195,4 @@
...
-ERROR SUMMARY: 23 errors from 23 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 17 errors from 17 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/memcheck/tests/manuel3.stderr.diff
=================================================
--- manuel3.stderr.exp 2012-01-18 19:30:37.000000000 -0500
+++ manuel3.stderr.out 2012-01-18 20:02:59.000000000 -0500
@@ -1,4 +1,3 @@
Conditional jump or move depends on uninitialised value(s)
- at 0x........: gcc_cant_inline_me (manuel3.c:22)
- by 0x........: main (manuel3.c:14)
+ at 0x........: main (manuel3.c:12)
=================================================
./valgrind-old/memcheck/tests/partial_load_ok.stderr.diff
=================================================
--- partial_load_ok.stderr.exp 2012-01-18 19:30:36.000000000 -0500
+++ partial_load_ok.stderr.out 2012-01-18 20:07:34.000000000 -0500
@@ -1,7 +1,13 @@
-Invalid read of size 4
+Invalid read of size 1
+ at 0x........: main (partial_load.c:16)
+ Address 0x........ is 0 bytes after a block of size 7 alloc'd
+ at 0x........: calloc (vg_replace_malloc.c:...)
+ by 0x........: main (partial_load.c:14)
+
+Invalid read of size 8
at 0x........: main (partial_load.c:23)
- Address 0x........ is 1 bytes inside a block of size 4 alloc'd
+ Address 0x........ is 1 bytes inside a block of size 8 alloc'd
at 0x........: calloc (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:20)
@@ -11,9 +17,9 @@
at 0x........: calloc (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:28)
-Invalid read of size 4
+Invalid read of size 8
at 0x........: main (partial_load.c:37)
- Address 0x........ is 0 bytes inside a block of size 4 free'd
+ Address 0x........ is 0 bytes inside a block of size 8 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (partial_load.c:36)
@@ -25,4 +31,4 @@
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/memcheck/tests/partial_load_ok.stderr.diff64
=================================================
--- partial_load_ok.stderr.exp64 2012-01-18 19:30:36.000000000 -0500
+++ partial_load_ok.stderr.out 2012-01-18 20:07:34.000000000 -0500
@@ -1,4 +1,10 @@
+Invalid read of size 1
+ at 0x........: main (partial_load.c:16)
+ Address 0x........ is 0 bytes after a block of size 7 alloc'd
+ at 0x........: calloc (vg_replace_malloc.c:...)
+ by 0x........: main (partial_load.c:14)
+
Invalid read of size 8
at 0x........: main (partial_load.c:23)
Address 0x........ is 1 bytes inside a block of size 8 alloc'd
@@ -25,4 +31,4 @@
For a detailed leak analysis, rerun with: --leak-check=full
For counts of detected and suppressed errors, rerun with: -v
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/memcheck/tests/varinfo6.stderr.diff
=================================================
--- varinfo6.stderr.exp 2012-01-18 19:30:36.000000000 -0500
+++ varinfo6.stderr.out 2012-01-18 20:15:00.000000000 -0500
@@ -7,8 +7,7 @@
by 0x........: BZ2_bzCompress (varinfo6.c:4860)
by 0x........: BZ2_bzBuffToBuffCompress (varinfo6.c:5667)
by 0x........: main (varinfo6.c:6517)
- Location 0x........ is 2 bytes inside local var "budget"
- declared at varinfo6.c:3115, in frame #2 of thread 1
+ Address 0x........ is on thread 1's stack
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo6.c:34)
=================================================
./valgrind-old/memcheck/tests/varinfo6.stderr.diff-ppc64
=================================================
--- varinfo6.stderr.exp-ppc64 2012-01-18 19:30:36.000000000 -0500
+++ varinfo6.stderr.out 2012-01-18 20:15:00.000000000 -0500
@@ -1,5 +1,5 @@
Uninitialised byte(s) found during client check request
- at 0x........: croak (varinfo6.c:35)
+ at 0x........: croak (varinfo6.c:34)
by 0x........: mainSort (varinfo6.c:2999)
by 0x........: BZ2_blockSort (varinfo6.c:3143)
by 0x........: BZ2_compressBlock (varinfo6.c:4072)
@@ -10,7 +10,7 @@
Address 0x........ is on thread 1's stack
Uninitialised byte(s) found during client check request
- at 0x........: croak (varinfo6.c:35)
+ at 0x........: croak (varinfo6.c:34)
by 0x........: BZ2_decompress (varinfo6.c:1699)
by 0x........: BZ2_bzDecompress (varinfo6.c:5230)
by 0x........: BZ2_bzBuffToBuffDecompress (varinfo6.c:5715)
|
|
From: Christian B. <bor...@de...> - 2012-01-19 03:06:08
|
valgrind revision: 12345 VEX revision: 2241 GCC version: gcc (GCC) 4.5.3 20110121 (Red Hat 4.5.3-4) C library: GNU C Library stable release version 2.12.1, by Roland McGrath et al. uname -mrs: Linux 3.1.0-rc9-andreas-gde346b6-dirty s390x Vendor version: unknown Nightly build on fedora390 ( Fedora 13/14/15 mix with gcc 3.5.3 on z196 (s390x) ) Started at 2012-01-19 03:45:01 CET Ended at 2012-01-19 04:06:05 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 == 514 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/tc04_free_lock (stderr) drd/tests/tc09_bad_unlock (stderr) |