From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 33630 invoked by alias); 13 May 2016 13:04:56 -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 33620 invoked by uid 89); 13 May 2016 13:04:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=2.30, SECTION, 9015, UD:drive.google.com X-HELO: mx2.suse.de Received: from mx2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (CAMELLIA256-SHA encrypted) ESMTPS; Fri, 13 May 2016 13:04:46 +0000 Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id E6149AB1A; Fri, 13 May 2016 13:04:42 +0000 (UTC) Subject: RUN_UNDER_VALGRIND statistics for GCC 7 To: Jeff Law , Bernd Schmidt , Hans-Peter Nilsson References: <564DDEF2.8090803@suse.cz> <5652DD92.2030202@suse.cz> <56604E93.5050805@redhat.com> <5666F723.1030603@suse.cz> <5666F843.9000004@redhat.com> <5666FF9A.2010306@redhat.com> Cc: GCC Patches From: =?UTF-8?Q?Martin_Li=c5=a1ka?= Message-ID: <5735D0EA.4070201@suse.cz> Date: Fri, 13 May 2016 13:04:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <5666FF9A.2010306@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-05/txt/msg00980.txt.bz2 Hello. I've tried to apply the same patch for the current trunk and tried to separate reported errors to a different categories by a simple script ([1]). There are number (complete report: [2]): SECTION: gfortran error types: 3534, total errors: 113282 error types: 90.15%, total errors: 27.11% SECTION: c++ error types: 161, total errors: 7260 error types: 4.11%, total errors: 1.74% SECTION: c error types: 90, total errors: 6320 error types: 2.30%, total errors: 1.51% SECTION: c-common error types: 39, total errors: 205033 error types: 0.99%, total errors: 49.06% SECTION: Other error types: 96, total errors: 86037 error types: 2.45%, total errors: 20.59% Type in the dump means a back trace, while 'total errors' represent total # of errors. The second line shows a percentage ratio compared to all errors seen. As seen fortran has very big variety of back traces. Well, it shows that we have multiple PRs reported, they are references in the following PR: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68800 C++ FE looks quite good, same as C. c-common contains very interesting group: are possibly lost: 204032 occurences malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) xmalloc (xmalloc.c:148) new_buff (lex.c:3158) _cpp_get_buff (lex.c:3191) cpp_create_reader(c_lang, ht*, line_maps*) (init.c:251) c_common_init_options(unsigned int, cl_decoded_option*) (c-opts.c:219) toplev::main(int, char**) (toplev.c:2070) main (main.c:39) (which is in fact majority of errors in the section). That's something I'm going to look at. The last category (called Other) is dominated by are definitely lost: 20740 occurences calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) xcalloc (xmalloc.c:163) main (collect2.c:975) which is probably option handling allocation stuff. Apart from that, there are just ~90 types of different back traces. It's doable to remove majority of these in this stage1. OTOH as I'm not familiar with a FE (mainly Fortran), solving Fortran FE would be not trivial. Note: The dump comes from one week old build. Martin [1] https://github.com/marxin/script-misc/blob/master/valgrind-grep.py [2] https://drive.google.com/open?id=0B0pisUJ80pO1M1VOd2pObUVXSEU