On Tue, Oct 13, 2009 at 8:31 PM, Toon Moene <t...@moene.org> wrote: > Jeff Law wrote: > >> On 10/10/09 09:17, Daniel Jacobowitz wrote: > >>> On Sat, Oct 10, 2009 at 02:31:25PM +0200, Jan Hubicka wrote: >>> >>>> >>>> My solution would be probably to pass -fdump-ipa-inline parameter to lto >>>> compilation and read the log. It lists the inlining decisions and if >>>> something is not inlined, you get dump of reason why. > > OK, I did just that (of course, because I'm only interested in inlining > during Link-Time-Optimization, I only passed the compiler option to the link > phase of the the build). > > Now where does the resulting dump ends up - and how is it named ? > > I.e., in case of: > > gfortran -o exe -O3 -flto -fwhole-program -fdump-ipa-inline a.f lib.a > > ?
It'll be in /tmp and named after the first object file, in your case it will be ccGGS24.o.047i.inline (because the first object file will be a tempfile). A minor inconvenience that maybe is going to be fixed. Richard. > > -- > Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290 > Saturnushof 14, 3738 XG Maartensdijk, The Netherlands > At home: http://moene.org/~toon/ > Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html >
