From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 57161 invoked by alias); 8 Dec 2015 15:33:27 -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 57142 invoked by uid 89); 8 Dec 2015 15:33:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 08 Dec 2015 15:33:26 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id E6BE0C0B7A25; Tue, 8 Dec 2015 15:33:24 +0000 (UTC) Received: from localhost.localdomain (vpn1-5-49.ams2.redhat.com [10.36.5.49]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tB8FXNZo020194; Tue, 8 Dec 2015 10:33:24 -0500 Subject: Re: [PATCH,RFC] Introduce RUN_UNDER_VALGRIND in test-suite To: =?UTF-8?Q?Martin_Li=c5=a1ka?= , Hans-Peter Nilsson References: <564DDEF2.8090803@suse.cz> <5652DD92.2030202@suse.cz> <56604E93.5050805@redhat.com> <5666F723.1030603@suse.cz> Cc: GCC Patches From: Bernd Schmidt Message-ID: <5666F843.9000004@redhat.com> Date: Tue, 08 Dec 2015 15:33:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5666F723.1030603@suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-12/txt/msg00880.txt.bz2 On 12/08/2015 04:28 PM, Martin Liška wrote: > > Majority of them (~2600 BTs) are in fortran FE (BT contains 'gfc_'): [2]. > The rest contains some issues in CP FE, many GGC invalid read/write operations ([4]) and many > memory leaks in gcc.c (for instance option handling). > > My question is if a bug should be created for all fortran issues and whether it's realistic that > they can be eventually fixed in next stage1? It hardly seems worthwhile to file a bug for every issue, that's just unnecessary bureaucracy. Fix them as you go along would be my recommendation, that probably takes a similar amount of time. Can't say whether it's realistic that they'll be fixed. I'm not at home in the Fortran frontend. Bernd