From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89229 invoked by alias); 8 Dec 2015 23:47:59 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 89219 invoked by uid 89); 8 Dec 2015 23:47:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: ainaz.pair.com Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 08 Dec 2015 23:47:58 +0000 Received: from anthias.dhcp.nue.suse.com (charybdis-ext.suse.de [195.135.221.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ainaz.pair.com (Postfix) with ESMTPSA id 4B8553F44A; Tue, 8 Dec 2015 18:47:55 -0500 (EST) Date: Tue, 08 Dec 2015 23:47:00 -0000 From: Gerald Pfeifer To: =?ISO-8859-15?Q?Martin_Li=A8ka?= cc: GCC Patches Subject: Re: [DOC, PATCH] Mention --enable-valgrind-annotations in install.texi In-Reply-To: <5666FE18.1070306@suse.cz> Message-ID: References: <5666FE18.1070306@suse.cz> MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY=------------080200080604010809050905 X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00935.txt.bz2 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --------------080200080604010809050905 Content-Type: text/plain; CHARSET=utf-8 Content-Transfer-Encoding: 8BIT Content-length: 663 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.) +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? Gerald --------------080200080604010809050905--