Displaying 20 results from an estimated 800 matches similar to: "PATypeHolder, refineAbstractTypeTo(), addTypeName not found"
2018 Aug 14
2
Error: ‘class llvm::PassManager<llvm::Module>’ has no member named ‘add’
Hi Philip,
I also tried that including file:
#include "llvm/IR/LegacyPassManager.h"
but error remain same. Please help.
On Tue, Aug 14, 2018, 2:58 AM Philip Pfaffe <philip.pfaffe at gmail.com> wrote:
> Hi Ratnesh,
>
> the PassManager used in that example has moved into the legacy namespace:
> http://llvm.org/doxygen/classllvm_1_1legacy_1_1PassManager.html
>
>
2018 Aug 20
2
Using VMKit to convert Java Bytecode to LLVM IR
Hi,
I wanted to use VMKit project to convert Java Bytecode to LLVM IR bitcode.
But I do not know how to start, since I came to know that VMkit is written
for llvm -3.3 version, but I want it for latest LLVM version 6.0.1.
So, could you please suggest me, whether I have to write it whole project
from scratch to meet my requirement of latest llvm version, or can use
existing project by building
2018 Jul 31
2
LLJVM make error
Hi fellow devs,
I was looking for converting LLVM IR to JavaBytecode by using lljvm
project of https://github.com/davidar/lljvm
They don't seem to compile, once i run *make* in the root directory it give
me the error :
cd include && make all
make[1]: Entering directory `/home/rtiwari1/llvm_new/lljvm/include'
make[1]: Nothing to be done for `all'.
make[1]: Leaving
2018 Aug 01
2
LLJVM make error
That source file was removed from LLVM in r232397 on March 16, 2015.
It looks like lljvm hasn't been updated in a long time. LLVM's C++ APIs are not stable, so there is no expectation that a project built against LLVM's C++ API in 2015 would build or reasonably function against LLVM trunk.
The project probably works against LLVM 3.6.2 which was (I believe) the last LLVM release to
2018 Aug 24
3
OpaqueType:: get()
I have code that uses OpaqueType::get(), it was used to be in
llvm/IR/DerivedType.h , but it is removed now. What should I use for it
replacement.
Also, it is using #include <llvm/Bytecode/WriteBytecodePass.h> , but I do
not found any WriteBytecodePass.h in my source code. Please tell me, what
should I use in replacement of these.
Thanks& Regards,
Ratnesh Tiwari
-------------- next
2018 Aug 13
2
Error: ‘class llvm::PassManager<llvm::Module>’ has no member named ‘add’
Hi, I am begineer to llvm, implementing a main.cpp from
https://github.com/davidar/lljvm/blob/master/backend/main.cpp
A) : When I am declaring a command:
* PassManager PM*
* PM.add(new DataLayout td)*
It shows error:
>
*error: missing template arguments before ‘PM’*
* PassManager PM;*
^
>*main_test.cpp:48:2: error: ‘PM’ was not declared in this scope*
*
2008 Oct 03
1
[LLVMdev] Question about recursive types
Dear all,
I'm trying to run the example of recursive type construction examples
in LLVM Programmer's Manual, here is the code:
// Create the initial outer struct
PATypeHolder StructTy = OpaqueType::get();
std::vector<const Type*> Elts;
Elts.push_back(PointerType::get(StructTy));
Elts.push_back(Type::Int32Ty);
StructType *NewSTy = StructType::get(Elts);
// At this point, NewSTy =
2008 Feb 25
2
[LLVMdev] small patch to add an assert to PATypeHolder
Hello,
I ran into an issue with the ocaml bindings where PATypeHolder was getting a
null pointer, which eventually caused a segfault. This patch copies what
PATypeHandle does and adds the assert in the PATypeHolder::addRef method.
Also, I'm using git's gateway to subversion to track llvm and send this
patch. The patch applies fine according to my tests, but if there are any
problems,
2008 Jun 12
0
[LLVMdev] code generation order revisited.
On Jun 12, 2008, at 13:25, Hendrik Boom wrote:
> So it appears that types are processed for identity the moment they
> are made during parse tree construction?
Yes.
> This means that a type has to be completely known on creation.
Yes.
> Presumably there's some mechanism tor a type that isn't completely
> known yet -- or is thet avoided by having a type
2009 Jul 10
0
[LLVMdev] void llvm::PATypeHolder::addRef(): Assertion `Ty && "Type Holder has a null type!"' failed.
Hi,
I am using current SVN and in the last week or so, something causing the
following assertion failure has changed.
void llvm::PATypeHolder::addRef(): Assertion `Ty && "Type Holder has a
null type!"' failed.
The corresponding stack trace is:
#0 0x000000339ec332f5 in raise () from /lib64/libc.so.6
#1 0x000000339ec34b20 in abort () from /lib64/libc.so.6
#2
2008 Oct 03
0
[LLVMdev] Making Sense of ISel DAG Output
On Fri, October 3, 2008 9:10 am, David Greene wrote:
> On Thursday 02 October 2008 19:32, Dan Gohman wrote:
>
>> Looking at your dump() output above, it looks like the pre-selection
>> loads have multiple uses, so even though you've managed to match a
>> larger pattern that incorporates them, they still need to exist to
>> satisfy some other users.
>
> Yes,
2008 Jun 13
1
[LLVMdev] code generation order revisited.
On Thu, 12 Jun 2008 16:05:19 -0400, Gordon Henriksen wrote:
>
> Partially opaque types can be refined. This section of the programmer's
> manual is applicable:
>
> http://llvm.org/docs/ProgrammersManual.html#BuildRecType
>
> — Gordon
Here it is:
: // Create the initial outer struct
: PATypeHolder StructTy = OpaqueType::get();
: std::vector<const Type*> Elts;
:
2005 Mar 08
3
[LLVMdev] Recursive Types using the llvm support library
As far as I can tell, when you construct a type using the support
library StructType::get, you have to pass in a list of types. How can
you make a Recursive type by passing in a pointer to the type you are
constucting.
An example where something really simple like the line below was output
would be perfect.
%struct.linked_list = type { %struct.linked_list*, %sbyte* }
Thanks for any help,
2008 Jun 12
2
[LLVMdev] code generation order revisited.
>>
>> I think I may have found an exception to this -- the API seems to
>> require me to have all the fields for a struct ready before I
>> construct the struct. I don't have the ability to make a struct
>> type, use it to declare some variables, and still contribute fields
>> to it during the rest of the compilation.
>>
>> Is there a
2005 Mar 08
0
[LLVMdev] Recursive Types using the llvm support library
On Mon, 7 Mar 2005, John Carrino wrote:
> As far as I can tell, when you construct a type using the support
> library StructType::get, you have to pass in a list of types. How can
> you make a Recursive type by passing in a pointer to the type you are
> constucting.
>
> An example where something really simple like the line below was output
> would be perfect.
>
>
2008 Oct 03
3
[LLVMdev] Making Sense of ISel DAG Output
On Thursday 02 October 2008 19:32, Dan Gohman wrote:
> Looking at your dump() output above, it looks like the pre-selection
> loads have multiple uses, so even though you've managed to match a
> larger pattern that incorporates them, they still need to exist to
> satisfy some other users.
Yes, I looked at that too. It looks like these other uses end up being
chains to
2005 Mar 08
2
[LLVMdev] Recursive Types using the llvm support library
>> An example where something really simple like the line below was output
>> would be perfect.
>>
>> %struct.linked_list = type { %struct.linked_list*, %sbyte* }
>
> Use something like this:
>
> PATypeHolder StructTy = OpaqueType::get();
> std::vector<const Type*> Elts;
> Elts.push_back(PointerType::get(StructTy));
>
2005 Mar 15
2
[LLVMdev] Dynamic Creation of a simple program
Thanks for the information
I am trying to use one of your examples for recursive data structures:
=========================
PATypeHolder StructTy = OpaqueType::get();
std::vector<const Type*> Elts;
Elts.push_back(PointerType::get(StructTy));
Elts.push_back(PointerType::get(Type::SByteTy));
StructType *NewSTy = StructType::get(Elts);
// At this point, NewSTy = "{ opaque*, sbyte*
2010 Jun 14
2
[LLVMdev] Adding fields in a already built type?
Hi,
We build a type with StructType::get(fModule->getContext(), fDspFields, false); with a fDspFields (std::vector<const llvm::Type*> fDspFields;) that is not yet completely known when we have to build the type. It is possible to add fields in a already build type?
Thanks
Stéphane Letz
2010 Jun 14
0
[LLVMdev] Adding fields in a already built type?
On Jun 14, 2010, at 1:22 PM, Stéphane Letz wrote:
> Hi,
>
> We build a type with StructType::get(fModule->getContext(), fDspFields, false); with a fDspFields (std::vector<const llvm::Type*> fDspFields;) that is not yet completely known when we have to build the type. It is possible to add fields in a already build type?
Nope, types are immutable once created. The only