|
From: Robert H. <rob...@mi...> - 2020-05-06 01:49:10
|
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. I realize it may produce so many positives as to be useless, but careful filtering may help me in my situation. Robert Henry |
|
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. |
|
From: Robert H. <rob...@mi...> - 2020-05-06 03:49:40
|
I am trying to evaluate the code quality of a JIT, which in our case does not yet have the quality intra and inter procedural data flow analysis that the mature compilers you speak of already have. So the dynamic trace would provide additional insight on where our low hanging fruit is. ________________________________ From: John Reiser <jr...@bi...> Sent: Tuesday, May 5, 2020 7:23 PM To: val...@li... <val...@li...> Subject: [EXTERNAL] Re: [Valgrind-developers] Finding write-after-write 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. _______________________________________________ Valgrind-developers mailing list Val...@li... https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fvalgrind-developers&data=02%7C01%7Crobhenry%40microsoft.com%7Cb751f7b8c244457b028208d7f16ea2ae%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637243330290588999&sdata=ZBfph8OHeQrwBHPqFVjdD3W9Zg%2B3kIhr43QdiTdfO0Q%3D&reserved=0 |