Displaying 2 results from an estimated 2 matches for "libllvmtargetinfo".
2014 Oct 24
2
[LLVMdev] Target specific info available to Clang (and others)
On 24 October 2014 13:13, Rafael Espíndola <rafael.espindola at gmail.com> wrote:
> lib/Target/ARM: only built if the ARM target is enabled.
> lib/TargetInfo/ARM: always build. Include only info that clang wants
> to use: parse fpu name, construct the datalayout.
Yes! That's the final plan!
So, TableGen would generate two sets of files, one public and another
private. The
2014 Oct 24
4
[LLVMdev] Target specific info available to Clang (and others)
...ects' paths,
>> too. We also may need to get these new classes into a library on its
>> own, no?
>
> Yes, a fpu-name to fpu-enum function would live is such a library. In
> the above example TargetInfo would not be just a directory
> organization, there would be a lib/libLLVMTargetInfo.a in the build
> directory.
We also need a way to know which intrinsics are available for the current target. Currently clang accepts all of them and you get a “cannot select” error from the backend if the intrinsic is not available. We now have the mechanism to provide a better diagnostic from...