Displaying 13 results from an estimated 13 matches for "parseir".
2013 Jul 29
2
[LLVMdev] opt -O3 causes Assertion `New->getType() == getType() && "replaceAllUses of value with new value of different type!"' failed
...MaterializeAll(std::string*) + 78
14 llc 0x00000000014489b7
llvm::Module::MaterializeAllPermanently(std::string*) + 29
15 llc 0x00000000006c367b
llvm::ParseBitcodeFile(llvm::MemoryBuffer*, llvm::LLVMContext&,
std::string*) + 93
16 llc 0x0000000000679302
llvm::ParseIR(llvm::MemoryBuffer*, llvm::SMDiagnostic&,
llvm::LLVMContext&) + 214
17 llc 0x000000000067958a llvm::ParseIRFile(std::string
const&, llvm::SMDiagnostic&, llvm::LLVMContext&) + 374
18 llc 0x00000000006680f4
19 llc 0x0000000000668fed main + 199
2...
2016 Nov 20
3
uninitialized values in Attributes.cpp
...lyInto(llvm::MemoryBufferRef, llvm::Module&,
llvm::SMDiagnostic&, llvm::SlotMapping*) (Parser.cpp:31)
==29299== by 0x1CC5C16: llvm::parseAssembly(llvm::MemoryBufferRef,
llvm::SMDiagnostic&, llvm::LLVMContext&, llvm::SlotMapping*) (Parser.cpp:41)
==29299== by 0x158C59E: llvm::parseIR(llvm::MemoryBufferRef,
llvm::SMDiagnostic&, llvm::LLVMContext&) (IRReader.cpp:89)
==29299== by 0x158CA61: llvm::parseIRFile(llvm::StringRef,
llvm::SMDiagnostic&, llvm::LLVMContext&) (IRReader.cpp:102)
==29299==
2013 Aug 02
2
[LLVMdev] opt -O3 causes Assertion `New->getType() == getType() && "replaceAllUses of value with new value of different type!"' failed
...x00000000014489b7
>> llvm::Module::MaterializeAllPermanently(std::string*) + 29
>> 15 llc 0x00000000006c367b
>> llvm::ParseBitcodeFile(llvm::MemoryBuffer*, llvm::LLVMContext&,
>> std::string*) + 93
>> 16 llc 0x0000000000679302
>> llvm::ParseIR(llvm::MemoryBuffer*, llvm::SMDiagnostic&,
>> llvm::LLVMContext&) + 214
>> 17 llc 0x000000000067958a llvm::ParseIRFile(std::string
>> const&, llvm::SMDiagnostic&, llvm::LLVMContext&) + 374
>> 18 llc 0x00000000006680f4
>> 19 ll...
2012 Oct 26
3
[LLVMdev] Using LLVM to serialize object state -- and performance
...ot;reconstitute" function are mostly a sequence of "call" instructions with a few "store" and "getelementptr" instructions here and there -- fairly straight-forward LLVM code.
I then write out the LLVM IR code to disk and, at some later time, read it back in with ParseIR(), do getPointerToFunction(), execute that function, and the C++ iterator tree has been reconstituted.
This all works, but the JIT compile step is *slow*. For a sequence of about 8000 LLVM instructions (most of which are "call"), it takes several seconds to execute.
It occurred to me t...
2013 Aug 02
0
[LLVMdev] opt -O3 causes Assertion `New->getType() == getType() && "replaceAllUses of value with new value of different type!"' failed
...gt; 14 llc 0x00000000014489b7
> llvm::Module::MaterializeAllPermanently(std::string*) + 29
> 15 llc 0x00000000006c367b
> llvm::ParseBitcodeFile(llvm::MemoryBuffer*, llvm::LLVMContext&,
> std::string*) + 93
> 16 llc 0x0000000000679302
> llvm::ParseIR(llvm::MemoryBuffer*, llvm::SMDiagnostic&,
> llvm::LLVMContext&) + 214
> 17 llc 0x000000000067958a llvm::ParseIRFile(std::string
> const&, llvm::SMDiagnostic&, llvm::LLVMContext&) + 374
> 18 llc 0x00000000006680f4
> 19 llc 0x0000...
2013 Aug 09
0
[LLVMdev] opt -O3 causes Assertion `New->getType() == getType() && "replaceAllUses of value with new value of different type!"' failed
...t;> llvm::Module::MaterializeAllPermanently(std::string*) + 29
>>> 15 llc 0x00000000006c367b
>>> llvm::ParseBitcodeFile(llvm::MemoryBuffer*, llvm::LLVMContext&,
>>> std::string*) + 93
>>> 16 llc 0x0000000000679302
>>> llvm::ParseIR(llvm::MemoryBuffer*, llvm::SMDiagnostic&,
>>> llvm::LLVMContext&) + 214
>>> 17 llc 0x000000000067958a llvm::ParseIRFile(std::string
>>> const&, llvm::SMDiagnostic&, llvm::LLVMContext&) + 374
>>> 18 llc 0x00000000006680f...
2016 Nov 20
3
uninitialized values in Attributes.cpp
...> llvm::Module&, llvm::SMDiagnostic&, llvm::SlotMapping*) (Parser.cpp:31)
>> ==29299== by 0x1CC5C16: llvm::parseAssembly(llvm::MemoryBufferRef,
>> llvm::SMDiagnostic&, llvm::LLVMContext&, llvm::SlotMapping*) (Parser.cpp:41)
>> ==29299== by 0x158C59E: llvm::parseIR(llvm::MemoryBufferRef,
>> llvm::SMDiagnostic&, llvm::LLVMContext&) (IRReader.cpp:89)
>> ==29299== by 0x158CA61: llvm::parseIRFile(llvm::StringRef,
>> llvm::SMDiagnostic&, llvm::LLVMContext&) (IRReader.cpp:102)
>> ==29299==
>> ________________________...
2012 Oct 27
0
[LLVMdev] Using LLVM to serialize object state -- and performance
...ot;reconstitute" function are mostly a sequence of "call" instructions with a few "store" and "getelementptr" instructions here and there -- fairly straight-forward LLVM code.
I then write out the LLVM IR code to disk and, at some later time, read it back in with ParseIR(), do getPointerToFunction(), execute that function, and the C++ iterator tree has been reconstituted.
This all works, but the JIT compile step is *slow*. For a sequence of about 8000 LLVM instructions (most of which are "call"), it takes several seconds to execute.
It occurred to me t...
2011 Oct 31
1
[LLVMdev] Runtime optimization using llvm
Hello,
I am getting to know how the Runtime Optimization feature of LLVM works and
how I can use it. I want to know how I could print the results of any
analysis and transformation pass. Say, I have a program written in c and I
ran the edge-profiling pass onto it. Now I want to see the result. How
could I do it?
Also if I happen to change one of the passes inside folder
2012 Nov 06
3
[LLVMdev] Using LLVM to serialize object state -- and performance
...itute" function are mostly a sequence of "call" instructions with a few "store" and "getelementptr" instructions here and there -- fairly straight-forward LLVM code.
>
> I then write out the LLVM IR code to disk and, at some later time, read it back in with ParseIR(), do getPointerToFunction(), execute that function, and the C++ iterator tree has been reconstituted.
>
> This all works, but the JIT compile step is *slow*. For a sequence of about 8000 LLVM instructions (most of which are "call"), it takes several seconds to execute.
>
>...
2012 Nov 06
0
[LLVMdev] Using LLVM to serialize object state -- and performance
...itute" function are mostly a sequence of "call" instructions with a few "store" and "getelementptr" instructions here and there -- fairly straight-forward LLVM code.
>
> I then write out the LLVM IR code to disk and, at some later time, read it back in with ParseIR(), do getPointerToFunction(), execute that function, and the C++ iterator tree has been reconstituted.
>
> This all works, but the JIT compile step is *slow*. For a sequence of about 8000 LLVM instructions (most of which are "call"), it takes several seconds to execute.
>
>...
2013 Jul 05
0
[LLVMdev] Any suggestion for "Unknown instruction type encountered" error?
hacker cling wrote:
> Hello all,
> I was playing with LLVM pass. I changed the
> lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make
> install the pass and use an example test1.c to see whether it works or
> not. When I run example using the following command:
> clang -emit-llvm test1.c -c -o test1.bc
> opt -load
2013 Jul 05
2
[LLVMdev] Any suggestion for "Unknown instruction type encountered" error?
Hello all,
I was playing with LLVM pass. I changed the
lib/Transforms/Hello/Hello.cpp 's content to be my own pass. Then I make
install the pass and use an example test1.c to see whether it works or not.
When I run example using the following command:
clang -emit-llvm test1.c -c -o test1.bc
opt -load ../build_llvm/Debug+Asserts/lib/LLVMHello.so -hello < test1.bc >
/dev/null
It