This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [DOC, PATCH] Mention --enable-valgrind-annotations in install.texi
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: Martin LiÅka <mliska at suse dot cz>
- Cc: gcc-patches at gcc dot gnu dot org, gerald at pfeifer dot com
- Date: Wed, 9 Dec 2015 11:01:55 +0100
- Subject: Re: [DOC, PATCH] Mention --enable-valgrind-annotations in install.texi
- Authentication-results: sourceware.org; auth=none
- References: <5666FE18 dot 1070306 at suse dot cz> <alpine dot LSU dot 2 dot 20 dot 1512090045500 dot 2651 at anthias> <5667F562 dot 7070306 at suse dot cz>
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