Displaying 4 results from an estimated 4 matches for "ll_filenam".
Did you mean:
ll_filename
2014 Sep 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...;m not using
> "target-cpu" argument now as "cortex-a8" is not supported for this triple).
>
> Next i'm trying to interpret it (source code is copy-pasted from lli tool
> source code):
>
> // lli with my default arguments
> int llvm_interpret(const char *ll_filename) {
> std::string InputFile(ll_filename);
>
> return llvm_interpret(
> InputFile,
> std::vector<std::string>(), // argv
> false, // ForceInterpreter
> false, // UseMCJIT
> false, // DebugIR
> false, // RemoteMCJIT
> "", /...
2014 Sep 17
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
Both Clang/LLVM 3.4 -> Clang/LLVM 3.5
And i will also try using MCJIT.
2014-09-17 18:56 GMT+06:00 Anton Smirnov <dev at antonsmirnov.name>:
> Hi, Tim.
>
> I've used Clang 3.4 final release and now i'm going to test it with 3.5
> release (since i've read about arm64 improvements).
> I will report my results.
>
> BTW, is it possible to get smth like
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...t now as "cortex-a8" is not supported for this triple).
>>>
>>> Next i'm trying to interpret it (source code is copy-pasted from lli
>>> tool source code):
>>>
>>> // lli with my default arguments
>>> int llvm_interpret(const char *ll_filename) {
>>> std::string InputFile(ll_filename);
>>>
>>> return llvm_interpret(
>>> InputFile,
>>> std::vector<std::string>(), // argv
>>> false, // ForceInterpreter
>>> false, // UseMCJIT
>>> false, //...
2014 Sep 18
2
[LLVMdev] [cfe-dev] exc_bad_instruction on arm
...for this triple).
>>>>>
>>>>> Next i'm trying to interpret it (source code is copy-pasted from lli
>>>>> tool source code):
>>>>>
>>>>> // lli with my default arguments
>>>>> int llvm_interpret(const char *ll_filename) {
>>>>> std::string InputFile(ll_filename);
>>>>>
>>>>> return llvm_interpret(
>>>>> InputFile,
>>>>> std::vector<std::string>(), // argv
>>>>> false, // ForceInterpreter
>>>&g...