https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86452
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 10 Jul 2018, marxin at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86452 > > --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- > (In reply to Richard Biener from comment #1) > > Well, what flags do you use? (-g1?) Any CUs with differing flags? > > Yes, it's w/ -g1. I was also reproduce that on libxul.so with -g1. So that I > can confirm that all CUs have same debug info flags. > > > > > Nothing to do w/o a testcase... > > That would be fun :) Might be as easy as make -k check RUNTESTFLAGS="--target_board=unix/-flto/-g1" ... Similar "interesting" bugs should be turned up when compiling with -g0 and linking with -g1+ (not easy to retrofit in the testsuite harness if you don't do sth like darwin/mingw and reset debug_info_level around LTO-out) Separate bug for each backtrace please.
