Jakub Jelinek <ja...@redhat.com> writes: > There have been several man-years of work to get from the 25% var coverage > to 67%, several DWARF extensions (most of them to be available in DWARF5 or > work in progress on that) and with -fno-var-tracking-assignments that is > just returned to the old state.
This is a typical "but look at all the work we've put in, it *has* to work" argument. As always, it is completely without merit. >> In other words, anybody who relies on it has already learnt to work >> around it. Or, more likely, there just isn't anybody who relies on it. >> >> I don't understand how you guys can be so cavalier about a compiler >> bug that has already resulted in actual real problems. You bring up > > I have no problem with a -fno-var-tracking-assignments workaround for > compilers that have the PR61801 wrong-code bug. Are there any that with reasonable confidence do not? -- Måns Rullgård m...@mansr.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
