On Thu, 2018-02-15 at 10:54 +0100, Richard Biener wrote: > On Wed, 14 Feb 2018, Martin Sebor wrote: > > > I was excited to find out about the recent enhancement to > > the LTO test harness to support the new dg-lto-warning and > > dg-lto-message directives (thanks, David). > > > > To make them easier to find and use (there is a C++ LTO test > > that uses them but no C tests yet) the attached patch updates > > the README to document them. While I was at it I made a few > > minor cosmetic improvements to the README as well. > > > > Let me know if I didn't get something quite right or if there > > is something else that might be worth mentioning in the README. > > Looks good to me. > > Btw, do the new dg-lto-warning/message directives handle > fat LTO objects correctly where diagnostics usually appear twice, > once for the fat part generation and once for the ltrans part?
I didn't implement any logic for that, so I suspect not. > I wonder if we can build upon those new directives to finally > add scan-lto-tree-dump for dg-final as well... (the complication > here is to get at the dump file name but if we know the link > stage is executed we can provide a prefix to the driver IIRC). > > Richard.
