On Tue, Nov 17, 2020 at 09:54:46AM -0700, Jeff Law wrote:
> > So, e.g. if we had __builtin_warning (dunno where Martin S. is with that),
> > we could e.g. queue a __builtin_warning and add __builtin_unreachable (or
> > other possibilities), or e.g. during VRP just canonicalize proven always
> > out of bound shifts to shifts by an out of bound constant and let some later
> > pass warn and/or add __builtin_warning.
> So the idea is to start funneling this through the path isolation code
> and handle the various strategies there.
If the path isolation code would use the ranger for this, it wouldn't need
to be in VRP but could be anywhere, sure.
> __builtin_warning is on hold pending a rework to make it act more like a
> debug statement than a builtin function call. The latter impacts
> various heuristics, which would mean that it could impact codegen which
> would highly undesirable.
Agreed on that.
Jakub
