similar to: [LLVMdev] MP1: Constructor for AllocaInst

> AllocaInst. I did a recent "cvsupdate", but the code still hadn't > changed. Has this code already been updated ? If not, I request that it > be updated as soon as possible, as it simplifies our implementation of > MP1 (we need to insert the alloca's at the beginning of the function). The plan is to update the CSIL CVS tree soon. When that happens you should get

After I did a cvsupdate, my old code which was working fine before, now breaks. It says "Pure virtual method" called and aborts. This happens even for the Hello Pass example (I didn't make any modifications to this). I remember somone in the class had the same problem and managed to fix it. Did anyone else encounter this problem ? I'd be much obliged if somone could tell me how

Hello How to create plots dynamically with results of several analysis ? I got many outputs from lm fuction like: mp1.lm mp2.lm mp3.lm mp4.lm mp5.lm ... I'd like to make experimental versus predicted response plots of all analysis in a 'for loop': for( i in 1:10){ x11() plot( mp*i*$experimental_response, fitted( mp*i* ) ); abline(0,1) } I tried: paste( 'mp', i,

ISSUE: In CommandLine.h, gcc 2.96 thinks that the apply() template function, when called as: apply("Some text string", x) should be expanded to applicator<const char[n]>("Some text string", x) instead of applicator<char[n]>("Some text string", x). ACTION: Duplicate the template specialization for applicator<char[n]> as applicator<const

I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This is on persephone. Are you not getting this error? Perhaps I should check out a fresh tree and try to compile it? Rob On Apr 7, 2006, at 11:40 AM, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: >> I just updated from CVS, and after doing a clean rebuild I get >> this

I'm running Samba 3.0.4 with Kerberos 5 v 1.3.4. I'm accessing Win2k shares from the Samba box without a hitch, but whenever I try to open up Samba shares on the Win2K clients, I get a password prompt. If I access the shares via the IP address of the Samba machine, there's no problem. I don't know if this is relevant, but my Win2k PDC is showing the following error on a

Hi, all. When I run the llvm using the inline option. I always got the following error message. So I cannot even use inline option. suna14|~/MP1|[37]% opt -inline < scalarize.llvm.bc > /dev/null ../../../include/Support/ilist:104: failed assertion `Traits::getNext(NodePtr) != 0 && "Dereferencing end()!"' Abort I didn't use my own pass. Please let me know if you

Openssh 4.4p1 and 4.5p1 SCO Openserver 6 w/mp1, mp2 While installing v4.5p1, I noticed this sshd syslog error which began appearing when I upgraded from v4.3p2 to v4.4p1: Sep 1 17:54:41 tenzing sshd[12837]: error: Bind to port 22 on :: failed: \ Network is unreachable. sshd -d reports: debug1: Bind to port 22 on ::. Bind to port 22 on :: failed: Network is unreachable. debug1: Bind

Does our pass need to ensure that the new names it creates for the field allocations are, in fact, unique? -- Casey Carter Casey at Carter.net ccarter at uiuc.edu AIM: cartec69

The following is legal LLVM code in which ptr, ptr2, and ptr3 are all aliases: %struct = type { int, int } implementation int %p() { %ptr1 = alloca %struct %ptr2 = getelementptr %struct* %ptr1 %ptr3 = getelementptr %struct* %ptr2, uint 0 %pint = getelementptr %struct* %ptr3, uint 0, ubyte 0 %rval = load int* %pint ret int %rval } Should our pass a) ignore this, not replace %ptr1,

Just a note: I just checked in a change that corrects some very non-intuitive behavior of the AllocaInst & MallocInst classes. Before, the constructor would take a Type which would specify the return type of the instruction, instead of the operand type. Now it takes the operand type directly. More concretely: LLVM Code: X = alloca int ; int* Y = malloc int * ; int** Old C++

On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > is on persephone. > > Are you not getting this error? Perhaps I should check out a fresh tree and > try to compile it? Nope, I don't think anyone else is getting this error. If you could try a fresh build that would be great, I'll fire

I've done several CVS head builds today .. no problems on Linux. Reid. On Fri, 2006-04-07 at 11:53 -0500, Chris Lattner wrote: > On Fri, 7 Apr 2006, Robert L. Bocchino Jr. wrote: > > > I did a utils/cvsupdate, and there are no conflicts. srcdir != objdir. This > > is on persephone. > > > > Are you not getting this error? Perhaps I should check out a fresh

Hi, In the quest for better test cases for my MP, I thought of trying the Stepanov Abstraction Penalty benchmark. But apparently llvm-g++ is not ready for such terrible things. Let me know if you want me to send the source code (it is widely available). gaeke|csil-suna37|~/cs/426/MP1/step|[1177]% /usr/dcs/projects/cs426/Software/gcc_install/bin/g++ stepanov.cpp -o stepanov In file included from

I'm trying to run multiple simulations using R on a cluster of pentiums running Solaris X86 by batching the R routines and simultaneously farming them out to the cluster nodes. This works fine on some of the machines, but on others the directory structure is mapped differently, so that when I try to run R, it can't be found, I can get around this by running /net/mp1/space/local/bin/R

I'm guessing the problem occurred because I hadn't updated in a while (maybe a couple of weeks?) and I had an old Intrinsics.gen file hanging around in my source directory that was getting picked up by the makefile for some reason. This is a bug, but maybe it's harmless because there's a onetime workaround (delete the file by hand) and it won't be a problem for

Hi, For the following code const Type * Int32Type = IntegerType::getInt32Ty(getGlobalContext()); AllocaInst* newInst = new AllocaInst(Int32Type, 0, "flag", Bb); Bb->getInstList().push_back(newInst); It gives me the error " error: no matching constructor for initialization of 'llvm::AllocaInst' AllocaInst* newInst = new

Add the 'label' optional argument to the mkfs action, so it is possible to set a filesystem label direct when creating it. There may be filesystems not supporting changing the label of existing filesystems but only setting it at creation time, so this new optarg will help. Implement it for the most common filesystems (ext*, fat, ntfs, btrfs, xfs), giving an error for all the others, just

Hi, I'm trying to get my head around c++ - IR - c++ API and getting used tramform manual information to code. The manual states alloca is defined for <type>. FunstionType is a type, so alloca for functionType should be possible? Not? If we have a valid Module *m we can get an allocate instruction allocating space for a non-argumented function as follows: AllocaInst* pa2 = new

Hello all When using llvm-ld to link several bitcode files produced by LLVM-GCC, I ran into the problem that the resulting linked file had missing dbg entries for AllocaInst values. After some digging I found that llvm::MapValue returns NULL when it encounters an AllocaInst. The attached trivial patch fixes the problem. Is this behaviour intended? Regards, Jacob -- Jacob Zimmermann Oracle