Thanks! Probably the name of the commit should be not "Make typed pointers to be yet again recognized as pointers" but "Allow typed pointers to be base of VectorType". I don't have merge rights in llvm.org, so it would be nice if someone helps with merging.

@nikic hi, would the current revision be more acceptable?

In D136768#3885671, @nikic wrote:

Why do you need this? Typed pointers have very limited use as a representational convenience. They should not be recognized or handled like normal pointers.

@ChuanqiXu hi, with this patch the generated LLVM IR snippet is looking like:

Simplified the test

Sorry for a late response and thank you very much for the feedback!

In D82174#2109576, @sidorovd wrote:

In D82174#2109491, @Anastasia wrote:

TODO: update address space numerical values for SPIR target
Regarding the TODO. Still I like an idea of detached address spaces a little bit more, but I see your point. I would love to check how it works with SPIR-V address space mapping in SPIR-V to LLVM IR translator. I know, it shall have a little impact on a clang work, but still what to see the work I have to do there first (5 and 6 are already occupied there).

Makes sense. I think conversion to SPIR-V is one of the primary use cases. However, if checking doesn't need a lot of time it would be better to commit with the final numbering scheme. Otherwise things like this are pretty hard to change once they start to be used.

Made SPIR AS map continuous.

In D82174#2109491, @Anastasia wrote:

TODO: update address space numerical values for SPIR target
Regarding the TODO. Still I like an idea of detached address spaces a little bit more, but I see your point. I would love to check how it works with SPIR-V address space mapping in SPIR-V to LLVM IR translator. I know, it shall have a little impact on a clang work, but still what to see the work I have to do there first (5 and 6 are already occupied there).

Makes sense. I think conversion to SPIR-V is one of the primary use cases. However, if checking doesn't need a lot of time it would be better to commit with the final numbering scheme. Otherwise things like this are pretty hard to change once they start to be used.

Uploaded the full diff. I have already forgot have to Phabricator properly :)

LGTM. I'm not an expert in JSON, but may be it makes sense to move the change a line earlier before creation of pointer representation?