[LLVMdev] Extending llvm with data types which can be accessible only through interfaces.

Justin Holewinski justin.holewinski at gmail.com
Fri Jun 22 11:32:26 PDT 2012


On Fri, Jun 22, 2012 at 1:48 PM, Villmow, Micah <Micah.Villmow at amd.com>wrote:

>  Narayan,****
>
> OpenCL has similar data type called Images. They can only be accessed
> through function calls and not directly.****
>
> ** **
>
> Micah****
>
> ** **
>
> *From:* llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On
> Behalf Of *NARAYAN HEGDE
> *Sent:* Friday, June 22, 2012 10:24 AM
> *To:* llvmdev at cs.uiuc.edu
> *Cc:* Uday Reddy
> *Subject:* [LLVMdev] Extending llvm with data types which can be
> accessible only through interfaces.****
>
> ** **
>
> Hi LLVM-Dev Team,****
>
>
> I am a graduate student working on compilation for heterogeneous multi-cores.
> As a part of my project, I need to extend llvm by adding a new data type for a commonly used data structure like queue.
> Could you please mention if there been any prior work on extending the llvm frontend to accommodate these kind of new data types and parse it to get LLVM-IR.
>
> ****
>
> ** **
>
> Can you also advice on how to bind these new data types, with interfaces through which such data types can be accessed.
> example: Data type "queue" should be accessible to the programmer only through interfaces like enqueue and dequeue.
>
>
This sounds like a front-end issue.  LLVM IR has no notion of interfaces,
it is up to the front-end which is generating LLVM IR to honor any
front-end language restrictions.


>
> ****
>
> ** **
>
> PS note: I can't expose these as library (like STL) and would like the data type to be part of language spec ****
>
> ** **
>
> Thank you****
>
> Narayan****
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>


-- 

Thanks,

Justin Holewinski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120622/1f3c8c82/attachment.html>


More information about the llvm-dev mailing list