https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #12 from rguenther at suse dot de <rguenther at suse dot de> --- On Fri, 11 Jan 2019, msebor at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771 > > --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> --- > I understand what jump threading does but I don't know enough about how it > works to have a clear idea how viable marking up the created statements would > be. Jump threading just makes existing paths explicit, thus path sensitive analysis would come up with similar answers. There may be cases where we could prove such paths are unreachable and fail to do so, but the cases where the path ends up in this kind of "undefined" builtin call do not count IMHO because it is exactly those cases we want to warn about - so we cannot really reason they cannot happen because of that.
