public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/41564] -fdump-tree-all does not work as expected lto Date: Sun, 04 Oct 2009 09:20:00 -0000 [thread overview] Message-ID: <20091004092005.7854.qmail@sourceware.org> (raw) In-Reply-To: <bug-41564-6528@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2009-10-04 09:20 ------- It works - look into /tmp. $ ./xgcc -B. -o t t.i -flto -fdump-tree-all $ ls /tmp/ ccJKyW5f.o.140t.optimized ccJKyW5f.o.221t.statistics you need to use -save-temps to get nice names here. It also works with your lto1 invocation which would dump in /tmp/lua.o. So, is your complaint that it dumps to /tmp or that it dumps with a cc*.o base if not using -save-temps? -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Component|lto |driver Keywords| |lto Summary|-fdump-tree-all does not |-fdump-tree-all does not |work with lto |work as expected lto http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41564
next prev parent reply other threads:[~2009-10-04 9:20 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-10-04 6:07 [Bug lto/41564] New: -fdump-tree-all does not work with lto pinskia at gcc dot gnu dot org 2009-10-04 9:20 ` rguenth at gcc dot gnu dot org [this message] 2009-10-04 16:13 ` [Bug driver/41564] -fdump-tree-all does not work as expected lto pinskia at gcc dot gnu dot org 2009-10-04 18:58 ` [Bug driver/41564] -fdump-tree-all does not work as expected rguenth at gcc dot gnu dot org 2009-10-14 16:21 ` pinskia at gcc dot gnu dot org 2009-10-14 16:23 ` rguenth at gcc dot gnu dot org 2009-11-03 20:03 ` [Bug driver/41564] -fdump-tree-all for lto " pinskia at gcc dot gnu dot org 2009-11-04 9:32 ` rguenther at suse dot de 2009-11-04 13:57 ` Andrew Pinski 2009-11-04 13:58 ` pinskia at gmail dot com 2009-12-23 21:01 ` hjl dot tools at gmail dot com 2009-12-30 23:16 ` rguenther at suse dot de 2009-12-30 23:27 ` hjl dot tools at gmail dot com 2009-12-30 23:37 ` rguenther at suse dot de 2009-12-31 21:55 ` hjl dot tools at gmail dot com 2009-12-31 21:57 ` hjl dot tools at gmail dot com 2010-01-01 12:32 ` rguenth at gcc dot gnu dot org 2010-01-02 1:14 ` hjl dot tools at gmail dot com 2010-01-02 1:26 ` hjl dot tools at gmail dot com 2010-01-02 11:29 ` rguenth at gcc dot gnu dot org 2010-01-02 17:09 ` hjl dot tools at gmail dot com 2010-01-03 17:04 ` hjl at gcc dot gnu dot org 2010-01-03 17:37 ` hjl dot tools at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20091004092005.7854.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).