Re: [Valgrind-developers] valgrind: r6640 - trunk/memcheck

[Dirk M. <dm...@gm...>]

On Friday, 30. March 2007, Julian Seward wrote:

> - could you change 'int result' to 'Word result' (64-bit paranoia
>   w.r.t the horrible CALL_FN_W.. macros)

done.

> - how do we stop some future gcc-5.7.2 from noticing that
>   "if (p) while (*p++) ;" does not compute anything useful and
>   and therefore optimising it away?

it is a documented feature of gcc to not optimize away empty loops. 

>   Since gcc has no way to know what is going in inside the asm, it
>   has to believe our claim that it reads p.

another solution would be to calculate len and store it in a volatile 
variable. 


Dirk