From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6891 invoked by alias); 19 Nov 2015 15:07:29 -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 6877 invoked by uid 89); 19 Nov 2015 15:07:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.9 required=5.0 tests=AWL,BAYES_50,KAM_MXURI,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=no version=3.3.2 X-HELO: mail.ud10.udmedia.de Received: from ud10.udmedia.de (HELO mail.ud10.udmedia.de) (194.117.254.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 19 Nov 2015 15:07:26 +0000 Received: (qmail 24840 invoked from network); 19 Nov 2015 16:07:22 +0100 Received: from ip5b41f88a.dynamic.kabel-deutschland.de (HELO x4) (ud10?360p3@91.65.248.138) by mail.ud10.udmedia.de with ESMTPSA (ECDHE-RSA-AES256-SHA encrypted, authenticated); 19 Nov 2015 16:07:22 +0100 Date: Thu, 19 Nov 2015 15:07:00 -0000 From: Markus Trippelsdorf To: Martin =?utf-8?B?TGnFoWth?= Cc: GCC Patches Subject: Re: [PATCH,RFC] Introduce RUN_UNDER_VALGRIND in test-suite Message-ID: <20151119150721.GA322@x4> References: <564DDEF2.8090803@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <564DDEF2.8090803@suse.cz> X-SW-Source: 2015-11/txt/msg02348.txt.bz2 On 2015.11.19 at 15:38 +0100, Martin Liška wrote: > > In last two weeks I've removed couple of memory leaks, mainly tight to > middle-end. Currently, a user of the GCC compiler can pass > '--enable-checking=valgrind' configure option that will run all > commands within valgrind environment, but as the valgrind runs just > with '-q' option, the result is not very helpful. Well, it is easy to add as many valgrind options as you like to gcc.c. (I normally add --track-origins=yes and just adjust the for loop at line 3045). The advantage of that approach is that the valgrind annotation macros for the alloc-pool and the garbage collector (etc.) are used. So no suppression file is needed. -- Markus