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
(1) |
2
(3) |
3
(1) |
4
(2) |
|
5
|
6
|
7
(4) |
8
|
9
(2) |
10
|
11
(2) |
|
12
|
13
(3) |
14
(7) |
15
(4) |
16
(2) |
17
|
18
|
|
19
|
20
(1) |
21
(2) |
22
|
23
|
24
|
25
|
|
26
|
27
(1) |
28
|
29
|
30
|
|
|
|
From: Philippe W. <phi...@sk...> - 2017-11-13 22:15:10
|
On Mon, 2017-11-13 at 11:43 +0100, Ivo Raisr wrote: > 2017-11-11 23:27 GMT+01:00 Philippe Waroquiers <phi...@sk...>: > > This mail gives some measurements of the perf impact of using link time > > optimisations when building valgrind with lto (NB: some hacks > > documented below were used to build with -flto). > > > > A summary of the perf impact is: > > * callgrind : all perf tests are faster (between 5 to 10%). > > * memcheck : many tests are faster, some are equal, one degraded > > (I retried this one later, there was then no degradation). > > * helgrind : many tests are faster, a few are slower. > > > > The regression tests seem basically ok (some 30 failures mostly > > due to some stacktraces differences, as the tests were also > > compiled with -flto). > > Splendid job, Philippe! > > Some of the problems could go away if "fat" object files were used > (-ffat-lto-objects). Yes, providing fat objects will allow to produce only one library version, usable to link with or without lto. > > What I am worrying now is about observability of LTO-built valgrind binaries. > Every section of gcc manual says that support for debugging information with LTO > is experimental and that it can produce unexpected results. > What are your findings here? Were you able to get some useful information > for example from Valgrind C source code, and from VEX helper functions > called by generated code? I did not had to debug anything, so I cannot really judge but I just tried now some debugging by doing --wait-for-gdb=yes, then put a few breakpoints, look at so,e variables and args, next and step. In this small experiment, I had no particular problem to debug. So, the debugging experience seems not particularly worse than the current -O2 setup. But in any case, I think we should probably support both lto and non lot versions, just in case ... Philippe |
|
From: Petar J. <pe...@so...> - 2017-11-13 12:14:27
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=286d05eea0fc1059492bec127d4121770902c98c commit 286d05eea0fc1059492bec127d4121770902c98c Author: Petar Jovanovic <mip...@gm...> Date: Mon Nov 13 13:12:25 2017 +0100 synchronize access to vgdb_interrupted_tid Delay writing to the global vgdb_interrupted_tid until all the threads are in interruptible state. This ensures that valgrind_wait() will see correct value. This solves occasional failures of gdbserver_tests/hgtls test. Diff: --- coregrind/m_gdbserver/m_gdbserver.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/coregrind/m_gdbserver/m_gdbserver.c b/coregrind/m_gdbserver/m_gdbserver.c index 648d543..24716ad 100644 --- a/coregrind/m_gdbserver/m_gdbserver.c +++ b/coregrind/m_gdbserver/m_gdbserver.c @@ -876,7 +876,7 @@ void VG_(invoke_gdbserver) ( int check ) gdbserver. Otherwise, we let the valgrind scheduler invoke gdbserver at the next poll. This poll will be made very soon thanks to a call to VG_(force_vgdb_poll). */ - int n_tid; + int n_tid, vgdb_interrupted_tid_local = 0; vg_assert (check == 0x8BADF00D); @@ -894,7 +894,8 @@ void VG_(invoke_gdbserver) ( int check ) /* interruptible states. */ case VgTs_WaitSys: case VgTs_Yielding: - if (vgdb_interrupted_tid == 0) vgdb_interrupted_tid = n_tid; + if (vgdb_interrupted_tid_local == 0) + vgdb_interrupted_tid_local = n_tid; break; case VgTs_Empty: @@ -912,6 +913,8 @@ void VG_(invoke_gdbserver) ( int check ) } } + vgdb_interrupted_tid = vgdb_interrupted_tid_local; + /* .... till here. From here onwards, function calls are ok: it is safe to call valgrind core functions: all threads are blocked in |
|
From: Ivo R. <iv...@iv...> - 2017-11-13 10:43:52
|
2017-11-11 23:27 GMT+01:00 Philippe Waroquiers <phi...@sk...>: > This mail gives some measurements of the perf impact of using link time > optimisations when building valgrind with lto (NB: some hacks > documented below were used to build with -flto). > > A summary of the perf impact is: > * callgrind : all perf tests are faster (between 5 to 10%). > * memcheck : many tests are faster, some are equal, one degraded > (I retried this one later, there was then no degradation). > * helgrind : many tests are faster, a few are slower. > > The regression tests seem basically ok (some 30 failures mostly > due to some stacktraces differences, as the tests were also > compiled with -flto). Splendid job, Philippe! Some of the problems could go away if "fat" object files were used (-ffat-lto-objects). What I am worrying now is about observability of LTO-built valgrind binaries. Every section of gcc manual says that support for debugging information with LTO is experimental and that it can produce unexpected results. What are your findings here? Were you able to get some useful information for example from Valgrind C source code, and from VEX helper functions called by generated code? I. |