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. > > I saw that Jeff approved while I was mulling over the patch, > but still have two questons: > > 1. Why did you sort this in where you did? (It's not alphabetic.)
Hi. Well, it's not easy to find a place as the options are not well ordered :) I tried to pick up a better place in v2. > > +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. Martin > > Gerald >
>From 3531cab4de82bc0899c44d5cac19f3541027be8b Mon Sep 17 00:00:00 2001 From: marxin <mli...@suse.cz> Date: Tue, 8 Dec 2015 16:54:43 +0100 Subject: [PATCH] Mention --enable-valgrind-annotations in install.texi gcc/ChangeLog: 2015-12-08 Martin Liska <mli...@suse.cz> * doc/install.texi (--enable-valgrind-annotations): Mention the configure option in configure page. --- gcc/doc/install.texi | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index 0b71bef..652b936 100644 --- a/gcc/doc/install.texi +++ b/gcc/doc/install.texi @@ -1748,6 +1748,12 @@ When this option is specified more detailed information on memory allocation is gathered. This information is printed when using @option{-fmem-report}. +@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. + @item --enable-nls @itemx --disable-nls The @option{--enable-nls} option enables Native Language Support (NLS), -- 2.6.3