This is the mail archive of the
mailing list for the GCC project.
Re: msan and gcc ?
- From: Toon Moene <toon at moene dot org>
- To: VandeVondele Joost <joost dot vandevondele at mat dot ethz dot ch>, 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, 01 Oct 2014 19:58:17 +0200
- 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> <908103EDB4893A42920B21D3568BFD9315116BFD at MBX23 dot d dot ethz dot ch>
On 10/01/2014 06:21 PM, VandeVondele Joost wrote:
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.
That would be interesting - valgrind is certainly impossible to use on
our Weather Forecasting code (far too large, as valgrind helpfully
Toon Moene - e-mail: firstname.lastname@example.org - phone: +31 346 214290
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news