> > I have been chasing a runtime failure of a very large test built with > gcc-4_9. The bad code either calls a pure function or turn a virtual > call into __builtin_unreachable (incomplete target set). The indirect > info shows the otr type to be !maybe_derived_type, and the outer-type > gets cleared during inline update. I isolated a small test case -- but > the good news is that gcc-4_9 @head already fixed the problem. > > I will check in the test case to trunk later.
Good, testcase would be welcome. I guess it was the fix for placement_new bug. It disables some valid devirtualizations (and I thus may revisit the fix for 4.10), so it would be good to know if your testcase differs from the original PR one. Honza > > thanks, > > David > > > > > > > Honza
