On Mon, May 2, 2016 at 4:14 PM, Hal Finkel via cfe-commits < cfe-commits@lists.llvm.org> wrote:
> hfinkel added a comment. > > In http://reviews.llvm.org/D19678#416127, @rcox2 wrote: > > > Actually, the Intel compiler distinguishes between an optimization > report (-qopt-report) and an annotated listing (-qopt-report-annotate). > The optimization report lists the info for optimizations in a hierarchical > fashion. To use you example, > > > > icc -c -O3 -qopt-report=1 -qopt-report-file=stderr v.c > > > > yields: > > > Robert, John, (et al.), do you think I should change this to have an > -foptimization-report-file=<filename> and -foptimization-report, instead of > -foptimization-report=<filename>? In the future, when we have multiple > kinds of reports (a detailed inlining report, for example), maybe we want > to use -foptimization-report=inlining,somethingelse,andmore? > If we have `-foptimization-report=foo,bar`, would we want them to share the same output file? Or maybe `-foptimization-report-file=<path>` would result in `<path>.foo` and `<path>.bar` for the different reports? -- Sean Silva > > > http://reviews.llvm.org/D19678 > > > > _______________________________________________ > cfe-commits mailing list > cfe-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits >
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
