This is the mail archive of the
mailing list for the GCC project.
RE: msan and gcc ?
- From: "VandeVondele Joost" <joost dot vandevondele at mat dot ethz dot ch>
- To: Kostya Serebryany <kcc at google dot com>, Dmitry Vyukov <dvyukov at google dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "dvyukov at gcc dot gnu dot org" <dvyukov at gcc dot gnu dot org>, "jakub at redhat dot com" <jakub at redhat dot com>, "kcc at gcc dot gnu dot org" <kcc at gcc dot gnu dot org>
- Date: Wed, 1 Oct 2014 16:21:38 +0000
- Subject: RE: msan and gcc ?
- Authentication-results: sourceware.org; auth=none
- References: <908103EDB4893A42920B21D3568BFD9315115A1A at MBX23 dot d dot ethz dot ch> <CACT4Y+a1B=epexGa0y0baESRKgpqC5r1T8gW91xRM8_4aW=zgw at mail dot gmail dot com>,<CAN=P9pi60ukXrdqhxWMwx=+fzwBGoC+Q_s6nkffGuTyFzoX9yg at mail dot gmail dot com>
> it was certainly worth it.
since I see msan as a kind of valgrind replacement (similar functionality, but ~10x the speed, partially at the cost of more difficult deployment), I did a quick search in gcc bugzilla. 982 PRs mention valgrind, so such functionality is clearly heavily used.