From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8842 invoked by alias); 14 Sep 2004 19:20:03 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 8824 invoked from network); 14 Sep 2004 19:20:02 -0000 Received: from unknown (HELO dberlin.org) (68.164.203.246) by sourceware.org with SMTP; 14 Sep 2004 19:20:02 -0000 Received: from [129.34.20.23] (HELO [9.2.217.169]) by dberlin.org (CommuniGate Pro SMTP 4.2) with ESMTP id 7292360; Tue, 14 Sep 2004 15:20:01 -0400 In-Reply-To: <200409141411.22091.bangerth@ices.utexas.edu> References: <200409141350.43359.bangerth@ices.utexas.edu> <84fc9c00040914115855cad428@mail.gmail.com> <200409141411.22091.bangerth@ices.utexas.edu> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1314F158-0683-11D9-BD35-000D93B1B044@dberlin.org> Content-Transfer-Encoding: 7bit Cc: gcc@gcc.gnu.org, libstdc++@gcc.gnu.org, Richard Guenther , bugzilla-masters@dberlin.org From: Daniel Berlin Subject: Re: Style of libstdc++ header files Date: Tue, 14 Sep 2004 19:24:00 -0000 To: Wolfgang Bangerth X-SW-Source: 2004-09/txt/msg00878.txt.bz2 On Sep 14, 2004, at 3:11 PM, Wolfgang Bangerth wrote: > >> I would oppose to that as atleast short always-to-be-inlined methods >> are >> way easier to read/find if they are defined inline. > > In reality, I hardly ever have to _find_ a particular method. I want to > _delete_ whole blocks of code, whatever is in them. What is important > is the > number of semantic connections of other parts of a code into the block > I want > to delete. For member function definitions, there are no such > connections > because the declarations are still there. > > >> I'd rather spent >> the converting time creating a more C++-syntax aware >> testcase-reduction tool (like f.i. as you are suggesting, removing >> method definitions but retaining/creating declarations). > > Well, fact is: there is no such tool. People have tried to play around > with > Delta, but it turns out that the fastest and most efficient method is > still > brute human force. Nobody seems to know how to write a tool like you > suggest. > It depends on if you are trying to minimize a testcase for C++ FE bugs, or an optimization bug. For the case of C++ FE bugs, yer right, you will need to integrate it with some C++ syntax aware minimizer. For the case of optimization bugs, you are looking at the problem the wrong way. See LLVM's bugpoint for a tool that does this right.