[llvm-dev] Why does GEP allow src and destination type to have different address spaces?

[Siddharth Bhat via llvm-dev]

The GEP constructor does not assert that the source and destination types
match. Of course, this is incorrect and causes random failures somewhere
down the line.

Could I add general sanity checks to the GEP constructor?

In general, is an Instruction allowed to be in an inconsistent state? If
so, is there some well known method to "verify" whether an instruction is
consistent or not?

Thanks,
~Siddharth
-- 
Sending this from my phone, please excuse any typos!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171013/45f2c0ec/attachment.html>