|
From: John R. <jr...@bi...> - 2020-05-06 03:35:56
|
On 5/5/20 , Robert Henry via Valgrind-developers wrote: > I'm wondering if there has been any prior work to valgrind to make it optionally report write after write (WaW)? I'd like to use such a tool to find variables that are initialized unnecessarily. That's a job for an optimizing compiler and/or static code analysis tool. Such tools already exist and are well-developed and maintained; use them. Making drd detect WaW (with respect to initialization) is wasted effort. The output of a compiler or static analysis tool is a proof that the first Write is (or is not) superfluous. The output of a dynamic analysis tool is merely a comment that the observed execution had one such path. |