Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing

[Mark W. <ma...@kl...>]

Hi,

On Thu, Oct 20, 2022 at 01:25:44PM -0700, Carl Love wrote:
> The only issue noted, as discussed on #valgrind-dev channel, is the
> addition of four post errors for the 3.20RC tree on all of the Power
> platforms.  Specifically:
> 
> cachegrind/tests/ann1                    (post)
> cachegrind/tests/ann2                    (post)
> callgrind/tests/ann1                     (post)
> callgrind/tests/ann2                     (post)
> 
> The output from  cachegrind/tests/ann1.post.diff is:
> 
> --- ann1.post.exp	2021-01-21 09:09:33.000000000 -0600
> +++ ann1.post.out	2022-10-20 14:07:33.272141328 -0500
> @@ -33,6 +33,13 @@
>  --------------------------------------------------------------------
> -----------
> -
>  -- Auto-annotated source: a.c
>  --------------------------------------------------------------------
> -----------
> -
> +@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @@@@@@@@@
> +@@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@
> WARNING @@
> +@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @@@@@@@@@
> +@ Source file 'a.c' is more recent than input file 'cgout-test'.
> +@ Annotations may not be correct.
> +@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @@@@@@@@@
> +
>  Ir        I1mr ILmr 
>  
>          2    0    0  int main(void) {
> 
> As discussed on the #valgrind-dev channel, this appears to be a
> timestamp issue.  Doing a touch * in directory cachegrind/tests seems
> to fix all four post errors.
> 
> No other issues were noted.  I would vote to do the touch * command and
> go ahead with the release.

I added the touch to the testcases as attached. That makes sure the
cgout-test file is always newer.

Cheers,

Mark