From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7544 invoked by alias); 30 Dec 2009 23:27:21 -0000 Received: (qmail 7503 invoked by uid 48); 30 Dec 2009 23:27:09 -0000 Date: Wed, 30 Dec 2009 23:27:00 -0000 Message-ID: <20091230232709.7502.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug driver/41564] -fdump-tree-all for lto does not work as expected In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hjl dot tools at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-12/txt/msg02850.txt.bz2 ------- Comment #10 from hjl dot tools at gmail dot com 2009-12-30 23:27 ------- (In reply to comment #9) > Subject: Re: -fdump-tree-all for lto does not work as > expected > > On Wed, 23 Dec 2009, hjl dot tools at gmail dot com wrote: > > > ------- Comment #8 from hjl dot tools at gmail dot com 2009-12-23 21:01 ------- > > Since LTO tree dump is quite different, can't we give it a different > > command line option, something like -fdump-tree-lto-all, instead of > > enabling it with -fdump-tree-all? > > It isn't really different. This is a driver issue, the dumps use > possibly temporary file names as bases. > By different, I meant that LTO tree dumps are in a different directory and have different file name suffix that the normal tree dumps. You can't easily tell which tree dumps in the temporary directory are the ones generated by -fdump-tree-all you just ran. It is even worse when -fdump-tree-all -flto is run a few times by the same or different person. I don't think -fdump-tree-all should dump LTO tree by default. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41564