------- Comment #11 from rguenther at suse dot de 2009-12-30 23:37 ------- Subject: Re: -fdump-tree-all for lto does not work as expected
On Wed, 30 Dec 2009, hjl dot tools at gmail dot com wrote: > ------- 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. I think that -flto should use the same temporary file names as -save-temps enabled compiles do. The only sane way to implement your suggestion would be to strip -fdump-* options for the lto1 invocations which would make debugging impossible. Richard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41564
