Displaying 4 results from an estimated 4 matches for "gettargetfeature".
2018 Dec 19
2
Command line -mcpu= and -march=
Hi
I'm doing a port of Clang/LLVM - purely for the educational value - to the MC6809 (and HD6309 as a dub target) processors. I'll also want to eventually provide direct support for the AM9511 floating-point coprocessor as an option. I'm working with bleeding-edge code from the Git mirror.
I've made some pretty decent progress; I copied the llvm/lib/Targets/MSP430 Target to
2016 May 09
2
LLVM issuse:AArch64 TargetParser
Hi all,
Actually,I found there is a same problem for arm.For this case,I think
> maybe we can play a trick in the clang.
> Checking whether the given arch valid or not,before we throw it to the
> parser,which can be used for both arm
> and aarch64.
For the actions I mentioned above,I wrote a check function as below, basing
on the naming rules of the arm architecture.
+//Only if
2015 Jul 30
0
[LLVMdev] The Trouble with Triples
Hi Daniel,
> (from the context, you might have meant 'tuple' where you've written
> 'triple'. I'm answering based on the assumption you meant 'triple')
>
>
I did mean what I wrote.
> The GNU triple is already used as a way of encoding a large amount of the
> target data in a string but unfortunately, while this data is passed
> throughout
2015 Jul 30
3
[LLVMdev] The Trouble with Triples
Hi Eric,
Thanks for getting back to me on this.
> I'm not sure I agree with the basic idea of using the target triple as a way of
> encoding all of the pieces of target data as a string. I think in a number of
> cases what we need to do is either open up API to the back end to specify things,
> or encode the information into the IR when it's different from the generic triple.