From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19824 invoked by alias); 1 Jan 2010 12:32:11 -0000 Received: (qmail 19761 invoked by uid 48); 1 Jan 2010 12:31:59 -0000 Date: Fri, 01 Jan 2010 12:32:00 -0000 Message-ID: <20100101123159.19760.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: "rguenth at gcc dot gnu dot org" 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: 2010-01/txt/msg00015.txt.bz2 ------- Comment #14 from rguenth at gcc dot gnu dot org 2010-01-01 12:31 ------- What about -fdump-rtl-* and -fdump-ipa-*? They have the same problem. Note that this still wouldn't get what I would expect when doing gcc -flto -fdump-tree-all -O2 -o t t.c as you'd get a t.c.*.optimized tree dump that has nothing to do with what ends up in the executable. So I don't think the patch would be a strict improvement but instead it causes another confusion (not that the current situation is not confusing but at least it is known). I would like to see an idea how to address the dump-files-in-/tmp with tempfile names issue instead (I'd unconditionally use object file names as dumpbase as -save-temps or separating compiling and linking would do). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41564