[llvm] r234126 - [opaque pointer type] The last of the GEP IRBuilder API migrations

David Blaikie dblaikie at gmail.com
Mon Apr 27 09:37:42 PDT 2015


On Mon, Apr 27, 2015 at 9:17 AM, Paweł Bylica <chfast at gmail.com> wrote:
>
>
> On Fri, Apr 24, 2015 at 4:47 PM David Blaikie <dblaikie at gmail.com> wrote:
>>
>> On Fri, Apr 24, 2015 at 1:10 AM, Paweł Bylica <chfast at gmail.com> wrote:
>> > Will typed pointer go away completely on IR API level?
>>
>> That's my plan (if there's some reason for that not to be the case -
>> we should talk about it). Well, there will probably still be the API
>> for typed pointers to keep the bitcode parser easy to manage (I
>> suspect it would be excessively complicated to try to parse legacy
>> pointer types from the bitcode while removing the composite
>> PointerType entirely - so I might keep it around, rename it to
>> LegacyPointerType or similar & try to make sure only the bitcode
>> parser uses it)
>
>
> I was thinking about high level API that would help a LLVM user to track
> pointee types. I've checked it was discussed in the main LLVMdev thread, so
> it should close the subject here.

It was brought up, yes - some sort of ability to insert nop casts for
verification purposes, but it's not on my radar to actually do the
work there - so if you're particularly interested in that & want to
push for it/discuss how it might actually get done, here or on the
original thread, would be good to continue discussing it.

- David

>




More information about the llvm-commits mailing list