From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-293419-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 14323 invoked by alias); 1 Jun 2011 20:37:16 -0000
Received: (qmail 14294 invoked by uid 22791); 1 Jun 2011 20:37:15 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST
X-Spam-Check-By: sourceware.org
Received: from mail-wy0-f175.google.com (HELO mail-wy0-f175.google.com) (74.125.82.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 01 Jun 2011 20:37:00 +0000
Received: by wye20 with SMTP id 20so170870wye.20        for <gcc-patches@gcc.gnu.org>; Wed, 01 Jun 2011 13:36:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.152.132 with SMTP id g4mr7644502wbw.24.1306960618772; Wed, 01 Jun 2011 13:36:58 -0700 (PDT)
Received: by 10.227.37.152 with HTTP; Wed, 1 Jun 2011 13:36:58 -0700 (PDT)
In-Reply-To: <BANLkTim89r_RsLCqYjuWZMA=9Lic_4UXThZ2JJM--ajYb8epew@mail.gmail.com>
References: <BANLkTim89r_RsLCqYjuWZMA=9Lic_4UXThZ2JJM--ajYb8epew@mail.gmail.com>
Date: Wed, 01 Jun 2011 20:37:00 -0000
Message-ID: <BANLkTinUmryLsmRCUxzg+R2HTpB-H=K=rQ@mail.gmail.com>
Subject: Re: Dump before flag
From: Richard Guenther <richard.guenther@gmail.com>
To: Xinliang David Li <davidxl@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
X-SW-Source: 2011-06/txt/msg00104.txt.bz2

On Wed, Jun 1, 2011 at 10:26 PM, Xinliang David Li <davidxl@google.com> wrote:
> Hi, this is a simple patch that support dump_before flag. E.g,
>
> -fdump-tree-pre-before
>
> This is useful for diffing the the IR before and after a pass.
>
> Gcc dumping needs more cleanups -- such as allowing IR only dump,
> allowing IR dumping for a particular function etc. The exposure of
> 'dumpfile' (instead of a dumping_level () function) makes those change
> a little messy, but can be done.
>
> Ok for trunk?

-ENOPATCH

> Thanks,
>
> David
>