similar to: [LLVMdev] Instruction::getNext and Instruction::getPrev are private

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Instruction::getNext and Instruction::getPrev are private"

2007 May 11
0
[LLVMdev] Instruction::getNext and Instruction::getPrev are private
Thanks Antont and Gabor.. I will use the iterator instead.. On 5/11/07, Anton Korobeynikov <asl at math.spbu.ru> wrote: > Hello, Ferad. > > > I switched to the upcoming version 2.0 branch and porting my code from > > 1.9. Thanks there is not a lot to do. I found that > > Instruction::getNext and Instruction::getPrev are private. Is this > > intentional? >
2007 May 11
0
[LLVMdev] Instruction::getNext and Instruction::getPrev are private
Hi Ferad! the change has been made with <http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20070416/047931.html> You have to use iterators now and "operator ++" etc. Hope this helps, cheers, Gabor
2012 Dec 20
0
[LLVMdev] LLVM segmentation fault / need use Instruction instead of Instruction*
I may be mistaken as I just took a quick look, but in ilist_node the function "getPrevNode()" actually calls a method on the previous node: NodeTy *getPrevNode() { NodeTy *Prev = this->getPrev(); // Check for sentinel. if (!Prev->getNext()) return 0; return Prev; } http://llvm.org/docs/doxygen/html/ilist__node_8h_source.html#l00058 Try checking if
2007 Mar 28
5
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Hi, I tried to compile the GCC front end of LLVM in a 16 CPU SMP machine with 64bit intel xeon CPUs. I tried with (GCC 4.1.0, 4.1.1, 4.1.2 versions). The LLVM compiles perfectly but when compiling the gcc front end the compiler crashes with a segmentation fault by reporting for memory leakages. Probably this is for the GCC's mailing list, but decided to ask if you know anything more about
2007 Mar 29
0
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
GCC 4.1.x series is known not to compile LLVM. Its is well documented, avoid GCC 4.1. Aaron ----- Original Message ----- From: "Ferad Zyulkyarov" <feradz at gmail.com> To: <LLVMdev at cs.uiuc.edu> Sent: Wednesday, March 28, 2007 10:38 PM Subject: [LLVMdev] gcc 4.1* carashes compiling llvm-gcc > Hi, > > I tried to compile the GCC front end of LLVM in a 16 CPU
2007 Mar 29
0
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Hi Anton, > What's the version of binutils you're using? I've seen such messages > with 2.16 series, but they were only warnings... The version of binutils is 2.17 By the way. I will use the opportunity to ask you again :) I tried to compile with gcc 4.0.4. It successfully compile LLVM but fails compiling LLVM's gcc front end. The problem is architectural 32 and 64 bit.
2007 Mar 24
3
[LLVMdev] Compilation problems
Hi, I try to compile LLVM and the GCC frontend for LLVM. The steps that I follow are first to compile LLVM and later to compile GCC front end. I tried to compile LLVM 1.8, 1.9 releases and the CVS versions. I tried to compile with different GCC compilers 3.4.0, 4.1.2 and 4.2.0 GCC compilers 3.4.0 and 4.2.0 fail compiling LLVM sources. GCC 4.1.2 works. I cannot compile GCC front end. When I
2007 Mar 31
2
[LLVMdev] About implementing new intrinsic
Hi, I will try to explain by giving an example. Let's say that I have an intrinsic: int llvm.myintrinsic(int) I have a function: int myintrinsic_handler(int) When %var = call int %llvm.myintrinsic( int %arg ) is met in the code, I want the code generator put in its place: a call to function "myintrinsic_handler" (i.e. %var = call int %myintrinsic_handler( int %arg ) ) or
2009 Jan 16
1
[LLVMdev] Problem using ilist container
Hi All, I have just started using LLVM . i am facing a issue while using ilist container. Here is a struct with ilist container as its one element. typedef ilist<Instruction *> InstListType; struct list_node { int Impact; InstListType InstList; }; list_node
2011 Nov 14
0
[LLVMdev] ilist::getPrevNode asserts on list head
Hi all, I am finding a SEGFAULT in one of my passes when using getPrevNode on an instruction that is the only one in a BasicBlock. I was expecting getPrevNode to return 0 in that case (as per docs), but it breaks. I guess the code in in ilist_node.h: NodeTy *getPrevNode() { NodeTy *Prev = this->getPrev(); // Check for sentinel. if (!Prev->getNext()) return 0; return Prev; }
2007 Mar 29
1
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Hello, Ferad. > `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' referenced > in section `.rodata' of > /home/ferad/llvm/llvm-obj/Release/lib/libLLVMAnalysis.a(ScalarEvolutionExpander.o): > defined in discarded section > `.gnu.linkonce.t._ZN4llvm12SCEVExpander6expandEPNS_4SCEVE' of >
2007 Apr 01
0
[LLVMdev] About implementing new intrinsic
On Sat, 31 Mar 2007, Ferad Zyulkyarov wrote: > I will try to explain by giving an example. > Let's say that I have an intrinsic: int llvm.myintrinsic(int) > I have a function: int myintrinsic_handler(int) > When > %var = call int %llvm.myintrinsic( int %arg ) > is met in the code, I want the code generator put in its place: a call > to function >
2007 Apr 04
0
[LLVMdev] For a small help
Hi Ferad, On Wed, 2007-04-04 at 19:48 +0200, Ferad Zyulkyarov wrote: > Hi, > > I want to ask for a small help for creating an instruction that calls > e member method of an object. I suppose that this is not a headache > but I am impatient in learning :) I would be very thankful if you can > show me an example snippet code that does this in LLVM. Below is > described my
2007 Apr 02
2
[LLVMdev] About implementing new intrinsic
Hi, > > I want to implement a new intrinsic in llvm that will denote a > > parallel section within a function. > > Can you explain what you mean by a parallel section within a function? I want to see how OpenMP's parallel fit in the LLVM architecture, is it easy to implement or not. GCC is too heavy platform to work on.. Ferad -- Ferad Zyulkyarov Barcelona Supercomputing
2007 Mar 31
6
[LLVMdev] About implementing new intrinsic
Hi, I want to implement a new intrinsic in llvm that will denote a parallel section within a function. I followed the documentation for extending llvm (http://llvm.org/docs/ExtendingLLVM.html) but there is something about the working mechanism that is not clear for me. 1. Why do we have to add support for the C backend? Is this only necessary to transform the llvm assembly (bytecode) into C code
2007 Mar 29
1
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
Yes, you I read that in the docs. Do you have a preferred gcc version that you would suggest me to work best. Unfortunately, version 3.4.2 that you suggest in your docs fails in compilation too. Thanks, Ferad -- Ferad Zyulkyarov Barcelona Supercomputing Center
2007 Apr 04
4
[LLVMdev] For a small help
Hi, I want to ask for a small help for creating an instruction that calls e member method of an object. I suppose that this is not a headache but I am impatient in learning :) I would be very thankful if you can show me an example snippet code that does this in LLVM. Below is described my case. Let's say I have a class TestClass class TestClass { int testMethod(int a); } and I want to
2007 Apr 12
0
[LLVMdev] About an incident with my e-mail account
Hi LLVM, I would like to apologize to all LLVM readers for receiving an inappropriate message from LLVM mail list originating from my mail account. Today I was acknowledged by the moderators of other mail lists for posting inappropriate material CCed also to people who I know. I suppose that my e-mail account was cracked and now I am tracing the logs. Once again, sorry for this inconvenience.
2007 Mar 31
1
[LLVMdev] About implementing new intrinsic
On Sat, 31 Mar 2007, Ferad Zyulkyarov wrote: >> IntrinsicLowering already does this. It lets you lower intrinsics to >> arbitrary LLVM calls, including calls to external functions. > > I will try to do that in IntrinscLowering class. May you point me an > intrinsic implementation that lowers to an llvm call. bswap expands into a series of shifts and or's, for example.
2007 Mar 29
0
[LLVMdev] gcc 4.1* carashes compiling llvm-gcc
> i had the same errors. adding "--disable-multilib" to configure solved > the problem. but i guess this is not a general solution. Thanks, that worked. Probably it would be good if this issue is included in the readme file for gcc-front end. Regards, Ferad -- Ferad Zyulkyarov Barcelona Supercomputing Center