Displaying 5 results from an estimated 5 matches for "languagetransforminfo".
2013 Aug 10
3
[LLVMdev] Address space extension
...ee with you that this mapping is a "static" property of the
contract between the frontend and the backend so it is confusing to put
this information in the module.
A solution would be something like the current "TargetTransformInfo" for
represent source language details, e.g. a LanguageTransformInfo pass:
this kind of pass would be registered by the frontend in building
process of the compiler pipeline (the information about the mapping may
be required also in the middle end indirectly, e.g. to know the bitsize
of a pointer of a given logical address space).
The address space map function wou...
2013 Aug 10
0
[LLVMdev] Address space extension
...ping is a "static" property of the contract
> between the frontend and the backend so it is confusing to put this information
> in the module.
>
> A solution would be something like the current "TargetTransformInfo" for
> represent source language details, e.g. a LanguageTransformInfo pass:
> this kind of pass would be registered by the frontend in building process of the
> compiler pipeline (the information about the mapping may be required also in
> the middle end indirectly, e.g. to know the bitsize of a pointer of a given logical
> address space).
>
> The...
2013 Aug 10
0
[LLVMdev] Address space extension
Michele,
Why can not the target triple implicitly encode the address space mapping? I would not expect address spaces to map correctly if I compile OpenCL code on an AMD device and then compile the IR on an NVidia device. Even an AMD device targeted from OpenCL could have a different mapping than the same AMD device targeted from C++AMP, DirectX or OpenGL. Address space mapping should be part of
2013 Aug 09
2
[LLVMdev] Address space extension
Hello James,
I've some doubts about what you are proposing...
> A suggestion:
> Define/describe each address space in the lower layer of LLVM. <- all
> the target specific info.
> E.g. Address space 0 is 64bits and needs specific instructions to access it.
> The LLVM IR can query the lower layer when it needs to know a
> description of address space 0 during an
2013 Aug 10
2
[LLVMdev] Address space extension
...uot; property of the
> > contract between the frontend and the backend so it is confusing to
> > put this information in the module.
> >
> > A solution would be something like the current "TargetTransformInfo"
> > for represent source language details, e.g. a LanguageTransformInfo pass:
> > this kind of pass would be registered by the frontend in building
> > process of the compiler pipeline (the information about the mapping
> > may be required also in the middle end indirectly, e.g. to know the
> > bitsize of a pointer of a given logical address spa...