similar to: [LLVMdev] VMKit build broken

Displaying 20 results from an estimated 500 matches similar to: "[LLVMdev] VMKit build broken"

2012 May 22
0
[LLVMdev] VMKit build broken
Hi Balachandran, If this is a bug, it should be filed to clang, since you're compiling a file located in the clang project. But it looks like your llvm tree and clang tree are not in sync. Could you svn update both and see if that fixes it? Nicolas On Mon, May 21, 2012 at 8:21 PM, Balachandran Sivakumar < benignbala at gmail.com> wrote: > Hi, > > I just thought
2012 May 22
0
[LLVMdev] VMKit build broken
Hi, On Tue, May 22, 2012 at 6:18 PM, Balachandran Sivakumar <benignbala at gmail.com> wrote: > Hi, > >      Thanks, I had done an svn up on one of the sub directories and > hence it had been out of sync. But had completely missed that point. > Just did an svn up and started off the build again. Thanks > The clang build went on fine. But subsequently, when I build
2012 May 22
2
[LLVMdev] VMKit build broken
Hi, On Tue, May 22, 2012 at 6:07 PM, Nicolas Geoffray <nicolas.geoffray at gmail.com> wrote: > Hi Balachandran, > > If this is a bug, it should be filed to clang, since you're compiling a file > located in the clang project. But it looks like your llvm tree and clang > tree are not in sync. Could you svn update both and see if that fixes it? > Thanks, I had done
2012 May 23
1
[LLVMdev] VMKit build broken
Hi Balachandran, On Tue, May 22, 2012 at 8:45 PM, Balachandran Sivakumar < benignbala at gmail.com> wrote: > Hi, > > On Tue, May 22, 2012 at 6:18 PM, Balachandran Sivakumar > <benignbala at gmail.com> wrote: > > Hi, > > > > Thanks, I had done an svn up on one of the sub directories and > > hence it had been out of sync. But had completely
2012 May 22
1
[LLVMdev] Issues with clang build
Hi, I am on r157251. When I try to build clang, I get this error. Driver.cpp:52:47: error: use of undeclared identifier 'DEFAULT_SYSROOT' ClangExecutable(ClangExecutable), SysRoot(DEFAULT_SYSROOT), ^ 1 error generated. make[4]: *** [/home/ganapathy/projects/llvm/tools/clang/lib/Driver/Release+Asserts/Driver.o] Error 1 Can
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Mmm, sorry, the patch I posted crashes if ExitBr is null (which it may be ...) , this one should be ok (and passess all the ScalarEvolution tests in LLVM): diff --git a/lib/Analysis/ScalarEvolution.cpp b/lib/Analysis/ScalarEvolution.cpp index daf7742..b10fab2 100644 --- a/lib/Analysis/ScalarEvolution.cpp +++ b/lib/Analysis/ScalarEvolution.cpp @@ -4293,9 +4293,15 @@
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Attached 2012/2/8 Marcello Maggioni <hayarms at gmail.com>: > Mmm, sorry, the patch I posted crashes if ExitBr is null (which it may > be ...) , this one should be ok (and passess all the ScalarEvolution > tests in LLVM): > > diff --git a/lib/Analysis/ScalarEvolution.cpp b/lib/Analysis/ScalarEvolution.cpp > index daf7742..b10fab2 100644 > ---
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Your patch should include a testcase, see test/Analysis/ScalarEvolution for examples. "BranchInst* " should be "BranchInst *". You should have spaces after the // in your comments. One of the comment lines isn't indented properly. Nick On 8 February 2012 12:05, Marcello Maggioni <hayarms at gmail.com> wrote: > Attached > > 2012/2/8 Marcello Maggioni
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Well, it wasn't intended as a "real" patch to be included , but more as a "proof of concept" for a solution. Do you think it is a valid solution and I'm correct in my assumption? If so then I'll clean up the patch and attach a testcase for inclusion. Thanks! Marcello 2012/2/9 Nick Lewycky <nlewycky at google.com>: > Your patch should include a testcase,
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
On 8 February 2012 15:50, Marcello Maggioni <hayarms at gmail.com> wrote: > Well, it wasn't intended as a "real" patch to be included , but more > as a "proof of concept" for a solution. Do you think it is a valid > solution and I'm correct in my assumption? If so then I'll clean up > the patch and attach a testcase for inclusion. > I'm
2012 Feb 09
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
This is the .ll for that graph (attached). I think I understand what you are saying. This particular testcase returns CNC not because the exit block doesn't have a unique predecessor, but because the unique predecessor (the inner loop block) has a successor that is inside the loop (in this case itself, because it's the inner loop block). That doesn't change, anyway, the assuption that
2012 Feb 09
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
This is instead a very simple (handmade) test case that triggers the problem (attached) Also a more conforming patch has been attached 2012/2/9 Marcello Maggioni <hayarms at gmail.com>: > This is the .ll for that graph (attached). I think I understand what > you are saying. > This particular testcase returns CNC not because the exit block > doesn't have a unique predecessor,
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Hello, I'm finding problems with BackEdgeTaken count calculation in even simple fortran loops with gfortran-4.6 + DragonEgg 3.0. Even for simple double loops like this one: program test2 integer i,j,k dimension k(100,100) do j=1,100 do i=1,100 k(i,j) = i enddo enddo write(*,*) k(1,30) end make the ScalarEvolution
2012 Feb 09
1
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
FInally I had the time to complete everything up. Now I included the test case in the patch and the testcase runs with the LLVM tests system. 2012/2/9 Marcello Maggioni <hayarms at gmail.com>: > This is instead a very simple (handmade) test case that triggers the > problem (attached) > Also a more conforming patch has been attached > > 2012/2/9 Marcello Maggioni <hayarms
2013 Jul 31
1
[LLVMdev] Problem to remove successors
Hi All, I need to remove successors from every basic block to insert new ones I tried this code, but it doesn't work void RemoveSuccessor(TerminatorInst *TI, unsigned SuccNum) { assert(SuccNum < TI->getNumSuccessors() && "Trying to remove a nonexistant successor!"); // If our old successor block contains any PHI nodes, remove the entry in the //
2004 Apr 05
1
Comboot menu crashes when it goes off screen
It works! Now, is there a way to use this handler multiple times so different submenus can have different position values. -Aaron On Fri, 2 Apr 2004, ganapathy murali krishnan wrote: > You write your own menupos_handler (like in complex.c) and register the > handler. > > So all you need to do is to copy the code for the menupos_handler from > complex.c and modify it to suit
2008 Jan 18
3
Comboot Menu System
On the SysLinux page, there is a screenshot of "COMBOOT Menu System for SYSLINUX developed by Murali Krishnan Ganapathy" (Advanced Menu System). I was wondering where I might be able to download this menu system in full to work with? If you dont want to share, I understand, but I am really intrigued by this and want to learn more, and maybe make my own design if I can figure it out.
2012 Jul 09
2
[LLVMdev] problem with visitBranchInst()
hi, my code inherits InstVisitor class, and visitBranchInst() method. however, i notice that inside the virtual method visitBranchInst(BranchInst &I), on the LLVM instruction like: br i1 %1, label %2, label %3 my code doesnt return expected info. for ex, the code I.getCondition->getName().str() would return empty string. and at the same time, the code I.getSuccessor(0)->getName()
2004 May 18
2
SYSLINUX 2.10-pre2 is out
I have released SYSLINUX 2.10-pre2. I *really* would like testing reports for this one, especially ISOLINUX, since I've included Knut Petersen's fix for Award BIOSes... Changes in 2.10: * MEMDISK: Handle images compressed with zip as well as with gzip. Some Windows-based image tools apparently generate these kinds of images by default. Patch by Patrick
2003 May 28
1
Cross Subnet WINS?
But the win wks on the other subnet is configured to use my SAMBASERVER as its WINS SERVER, and it is configured using the IP Adress of the SAMBASERVER and not the name. Shouldn't this do the trick? win wks is on a wireless subnet and hence runs at 11 MBPS, while the SAMBASERVER is on a wired subnet. I read somewhere that windows does some kind of "optimization" with slow networks.