[llvm-dev] Various Intermediate Representations. IR

David Blaikie via llvm-dev llvm-dev at lists.llvm.org
Wed Apr 15 09:28:31 PDT 2020

opaque pointers don't exist in the IR yet - the goal is to reduce the
places that use non-opacity of pointer types already/today and then opacify
the existing pointer type, rather than introducing an opaque pointer type &
having it concurrently with non-opaque pointer types. (though in retrospect
such a migration might've been worth considering and/or might still be used
as part of the migration, I guess)

On Wed, Apr 15, 2020 at 3:17 AM James Courtier-Dutton via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On Tue, 14 Apr 2020 at 21:24, Michael Kruse <llvmdev at meinersbur.de> wrote:
> >
> > Currently, LLVM often uses the *i8 type (pointer to char) to represent
> > a pointer to some not-specified type. We are also working on replacing
> > the pointer-to-type pointer types by a single pointer type without a
> > specific pointee-type. Look for "opaque pointer" on llvm-dev and the
> > repository commits.
> >
> Hi Michael,
> Thank you for your reply.
> Does the LLVM IRBuilder currently allow adding an opaque pointer to a
> LLVM .bc file?
> Even if it does not compile, just being able to add it, would be helpful.
> I could then run my own experimental passes against it.
> Does using opaque pointers, adversely affect alias analysis?
> Kind Regards
> James
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200415/5fde40e2/attachment.html>

More information about the llvm-dev mailing list