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
(4) |
3
(2) |
4
|
|
5
(1) |
6
|
7
(1) |
8
(2) |
9
(3) |
10
(1) |
11
(6) |
|
12
|
13
(2) |
14
(4) |
15
(2) |
16
(1) |
17
(1) |
18
(24) |
|
19
(1) |
20
(4) |
21
(1) |
22
|
23
|
24
(5) |
25
(2) |
|
26
(6) |
27
(3) |
28
(5) |
|
|
|
|
|
From: Ivo R. <iv...@iv...> - 2017-02-24 19:21:12
|
Dear Valgrind community, We are pleased to announce an imminent migration of Valgrind sources from existing Subversion SCM to modern git SCM, as discussed during our FOSDEM 2017 Valgrind devroom. What is going on now? ~~~~~~~~~~~~~~~~~ The migration has just started. We are now in beta testing stage. We still use the official SVN Valgrind repository for our work until the final migration step. If you have some patches ready now, send them for review. You can contribute to the migration process - read below. What will be migrated: ~~~~~~~~~~~~~~~~~ Valgrind and VEX sources. Precisely sources available today under svn://svn.valgrind.org/valgrind and svn://svn.valgrind.org/vex, including all production release branches and tags. Valgrind and VEX repos will be merged into one, so no more SVN externals. Where I will find the new repo: ~~~~~~~~~~~~~~~~~~~~~~~ At sourceware.org. Precisely at: git://sourceware.org/git/valgrind.git/ http://sourceware.org/git/valgrind.git/ Right now a snapshot of SVN sources as of 2017-02-21 is available for you to test. How the test migration was performed: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ See recipes at https://github.com/ivosh/valgrind-git-migration What is the plan for the migration to go forward: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Test migration has been performed and initial tests were successful. 2. The test repo is now available to test and play for others with - see below for details. 3. Prepare www (website) and nightly build script changes and have them reviewed. 4. Proceed once 2+3 are successfully done. 5. Announce the final migration. 6. Completely eradicate contents in the GIT repository so the migration can start from scratch. 7. Switch SVN valgrind+vex repo readonly. 8. Perform the final migration to sourceware.org. 9. Enable email notifications from new git repo. 10. Push www and nightly script changes to the new repo. What will not be migrated: ~~~~~~~~~~~~~~~~~~~~ - Valgrind www (website) repo. Not now, but later. - Non production release branches and tags from old SVN Valgrind+VEX repos. If you need to preserve some other branches or tags, let us know: https://sourceware.org/git/?p=valgrind.git;a=heads https://sourceware.org/git/?p=valgrind.git;a=tags I have a write access to existing SVN repo. What shall I do for the new one? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Please contact Julian Seward. He will point you to specific instructions. What will be my simple workflow in new git SCM? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Not much will be changed from the way we worked in SVN. We still prepare patches, send them for review, have someone with write access to push them. A minimalistic workflow would be: git clone git://sourceware.org/git/valgrind.git/ valgrind edit/compile git status/add/show git pull origin/master build + test git commit [git push - if you have write access] There are a lot of good tutorials on simple git workflows, so please have a look. If you are using something more complicated, please share with us and ideally send us a write up. I would like to help with the migration. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Yes, please! Send us your positive and negative feedback. For example: - It worked for me! - This and that did not work for me... - How do I do such and such thing now? The test repository is there for you to play with. The contents will be deleted before the final migration so no reason to worry about potential mistakes. It is also quite likely that the contents will be regenerated during the beta testing, to fix any problems found. We also need a help documenting possible workflows. Especially when preparing a release - we need to test and document how to work with branches and releases. |
|
From: Ivo R. <iv...@iv...> - 2017-02-24 11:10:51
|
2017-02-24 11:21 GMT+01:00 Mark Wielaard <ma...@kl...>: > On Fri, Feb 24, 2017 at 11:11:20AM +0100, Ivo Raisr wrote: >> On arches which require aligned access (mips, sparc), gcc emits >> dozilions of warnings with -Wcast-align. >> However we don't want to disable this clo globally - that way we would >> loose important compiler >> diagnostic. The intention here is to use this macro only at >> (preferably) few places where: >> - the problem has been studied thoroughly >> - and the alignment is actually ok but the compiler cannot deduce it itself > > So, is the intention on arm32 to remove this configure check eventually? > > # On ARM we do not want to pass -Wcast-align as that produces loads > # of warnings. GCC is just being conservative. See here: > # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65459#c4 > if test "X$VGCONF_ARCH_PRI" = "Xarm"; then > AC_SUBST([FLAG_W_CAST_ALIGN], [""]) > else > AC_SUBST([FLAG_W_CAST_ALIGN], [-Wcast-align]) > fi Eventually, yes. Good point. I. |
|
From: Ivo R. <iv...@iv...> - 2017-02-24 10:11:30
|
2017-02-24 10:58 GMT+01:00 Mark Wielaard <ma...@kl...>: > On Fri, Feb 24, 2017 at 01:04:36AM +0100, Ivo Raisr wrote: >> Please state if you have any objections to patch 1/4 attached at bug: >> 370028 Reduce the number of compiler warnings on MIPS platforms >> https://bugs.kde.org/show_bug.cgi?id=370028 >> >> The patch itself: >> https://bugsfiles.kde.org/attachment.cgi?id=104201 >> >> Aleksandar tested it extensively on mips32/64, arm32, ppc32/64, s390 and amd64. >> I've tested it on amd64/Linux and sparcv9/Linux. >> Works great. > > I don't have any particular objection. But I don't fully understand the > issue either. How is this different from disabling -Wcast-align as we > do in configure.ac for arm? Is the intention to enable that warning on > all arches and use the new macro to silence it when we know the alignment > adds up? Good question. On arches which require aligned access (mips, sparc), gcc emits dozilions of warnings with -Wcast-align. However we don't want to disable this clo globally - that way we would loose important compiler diagnostic. The intention here is to use this macro only at (preferably) few places where: - the problem has been studied thoroughly - and the alignment is actually ok but the compiler cannot deduce it itself That particular place in vki-linux.h is a prime example because it satisfies all the conditions above and it produces 100+ warnings alone. Other places could be possibly solved with a bit of extending/redesigning Valgrind API. I. |
|
From: <sv...@va...> - 2017-02-24 08:33:08
|
Author: iraisr
Date: Fri Feb 24 08:32:59 2017
New Revision: 16255
Log:
Follow up to SVN r16253 (fix expected output of gdbserver_tests/solaris/nlcontrolc)
SVN r16253 (follow up to r16251) was not complete.
Modified:
trunk/gdbserver_tests/solaris/nlcontrolc.stderr.exp
trunk/gdbserver_tests/solaris/nlcontrolc.vgtest
Modified: trunk/gdbserver_tests/solaris/nlcontrolc.stderr.exp
==============================================================================
--- trunk/gdbserver_tests/solaris/nlcontrolc.stderr.exp (original)
+++ trunk/gdbserver_tests/solaris/nlcontrolc.stderr.exp Fri Feb 24 08:32:59 2017
@@ -3,7 +3,7 @@
(action at startup) vgdb me ...
-loops/sleep_ms/burn/threads_spec/affinity: 1000000000 5000 1000000000 BSBSBSBS 0
+loops/sleep_ms/burn/threads_spec/affinity: 1000000000 5000 1000000000 BSBSBSBS 1
Brussels ready to sleep and/or burn
London ready to sleep and/or burn
Petaouchnok ready to sleep and/or burn
Modified: trunk/gdbserver_tests/solaris/nlcontrolc.vgtest
==============================================================================
--- trunk/gdbserver_tests/solaris/nlcontrolc.vgtest (original)
+++ trunk/gdbserver_tests/solaris/nlcontrolc.vgtest Fri Feb 24 08:32:59 2017
@@ -6,7 +6,7 @@
# sleepers is started with argument so that it will compute during ages.
# The variable modifications means it will exit in a reasonable time.
prog: ../sleepers
-args: 1000000000 5000 1000000000 BSBSBSBS
+args: 1000000000 5000 1000000000 BSBSBSBS 1
vgopts: --tool=none --vgdb=yes --vgdb-error=0 --vgdb-prefix=./vgdb-prefix-solaris-nlcontrolc
stderr_filter: filter_stderr
prereq: test -e ../gdb -a -f ../vgdb.invoker
|
|
From: Ivo R. <iv...@iv...> - 2017-02-24 00:04:45
|
Please state if you have any objections to patch 1/4 attached at bug: 370028 Reduce the number of compiler warnings on MIPS platforms https://bugs.kde.org/show_bug.cgi?id=370028 The patch itself: https://bugsfiles.kde.org/attachment.cgi?id=104201 Aleksandar tested it extensively on mips32/64, arm32, ppc32/64, s390 and amd64. I've tested it on amd64/Linux and sparcv9/Linux. Works great. I. |