On 2015.12.09 at 10:33 +0100, Martin Liška wrote: > On 12/09/2015 12:47 AM, Gerald Pfeifer wrote: > > On Tue, 8 Dec 2015, Martin Liška wrote: > >> I would like to add a missing configure option. > > > > +Specify that the compiler should interact with valgrind runtime, where > > +selected invalid memory reads are marked as false positives and > > +garbage collected memory is properly marked for proper interaction. > > > > 2. "interact...for proper interaction" and "properly marked for > > proper" feels a little confusing to me. That is, I had to think > > twice. Any chance you can make this a little simpler to understand? > > Sure, please read v2. > > +@item --enable-valgrind-annotations > +Specify that the compiler should interact with valgrind runtime, > +where selected memory-related operations are marked as valid. > +There operations are safe and should not become a candidate > +of an undefined behavior.
Sorry, but this is simply awful ;-). How about: Mark selected memory related operations in the compiler when run under valgrind to suppress false positives. -- Markus