From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 127274 invoked by alias); 10 May 2017 20:52:15 -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 127249 invoked by uid 89); 10 May 2017 20:52:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_00,LIKELY_SPAM_BODY,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 spammy=H*MI:sk:2017051, sum X-HELO: smtp.ispras.ru Received: from bran.ispras.ru (HELO smtp.ispras.ru) (83.149.199.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 10 May 2017 20:52:12 +0000 Received: from monopod.intra.ispras.ru (monopod.intra.ispras.ru [10.10.3.121]) by smtp.ispras.ru (Postfix) with ESMTP id 26BC86128D; Wed, 10 May 2017 23:52:13 +0300 (MSK) Date: Wed, 10 May 2017 20:57:00 -0000 From: Alexander Monakov To: Jakub Jelinek cc: Richard Biener , Nathan Sidwell , GCC Patches Subject: Re: [PATCH] Kill -fdump-translation-unit In-Reply-To: <20170510175826.GH1809@tucnak> Message-ID: References: <964bab70-9a78-6812-4697-7c0c0f2dc096@acm.org> <20170510175826.GH1809@tucnak> User-Agent: Alpine 2.20.13 (LNX 116 2015-12-14) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-SW-Source: 2017-05/txt/msg00831.txt.bz2 On Wed, 10 May 2017, Jakub Jelinek wrote: > Can it at least be taken out of -fdump-tree-all? It is huge, often larger > than the sum of all the other dump files, and don't remember ever using it > for anything. Yes, apart from advertising the capability I don't imagine it's useful to produce that dump without a special flag. > Instead of trying to write a parser for it and reconstructing > something you can then later analyze, isn't it better to just write a plugin > that can analyze it directly? I think I can understand people writing a parser when it's sufficient; it won't need to be recompiled for a specific compiler version (with headers from that compiler), won't crash the compiler if you did something wrong. For people more familiar with a dynamic language like Python than C/C++ it may be just more comfortable to do it that way. Alexander