similar to: [LLVMdev] misc CVS patches

Displaying 20 results from an estimated 9000 matches similar to: "[LLVMdev] misc CVS patches"

2005 Apr 20
8
[LLVMdev] misc CVS patches
On Wed, Apr 20, 2005 at 12:12:54PM +0200, Markus F.X.J. Oberhumer wrote: > Misha Brukman wrote: > >On Tue, Apr 19, 2005 at 07:01:40AM +0200, Markus F.X.J. Oberhumer > >wrote: Have you considered using bugpoint for your codegen debugging > >needs? http://llvm.cs.uiuc.edu/docs/Bugpoint.html#codegendebug > > Well, the (critical) bug in question was >
2005 Apr 21
0
[LLVMdev] misc CVS patches
On Wed, 20 Apr 2005, Markus F.X.J. Oberhumer wrote: > Misha Brukman wrote: >> On Tue, Apr 19, 2005 at 07:01:40AM +0200, Markus F.X.J. Oberhumer wrote: >> >>> While trying to hunt down a codegen bug (not yet found) ... >> >> Have you considered using bugpoint for your codegen debugging needs? >> http://llvm.cs.uiuc.edu/docs/Bugpoint.html#codegendebug >
2005 Apr 21
5
[LLVMdev] Trailing whitespace removal (important for CVS users!)
Dear LLVMers, If you live on the bleeding edge (i.e. CVS version), please read! On Wed, Apr 20, 2005 at 12:12:54PM +0200, Markus F.X.J. Oberhumer wrote: > Do you really want external patches for this ? A simple Perl script > that runs on all *.h and *.cpp files, and a local commit from your > side would be much simpler. I'm in the process of doing just this as we speak. What this
2004 Jun 23
3
[LLVMdev] weird issue with mem2reg
On Wed, Jun 23, 2004 at 03:50:09PM -0500, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter > anything, all it does is build a set of "program instructions". For > some reason even though if I run it with any other combination of > passes I've found, anytime I run it with mem2reg I get a seg fault in > dyn_cast!
2005 Apr 21
0
[LLVMdev] misc CVS patches
On Thu, Apr 21, 2005 at 05:56:43PM +0200, Markus F.X.J. Oberhumer wrote: > Reid Spencer wrote: > >This patch can't be applied. Not all platforms have getgid() and > >getuid() functions. Placing non-portable code outside of lib/System > >is deprecated. We set the values to 1000 by default because in > >general the uid/gid doesn't matter in an archive and the 1000
2004 Jun 23
4
[LLVMdev] weird issue with mem2reg, should have guessed
On Wed, 23 Jun 2004, Patrick Meredith wrote: > What's different about code that's been mem2reg'd from straight front end > code, or anything that mem2reg hasn't been run on? PHINODES! Yup, front-ends generally don't produce SSA form. :) > It appears to be crashing when I try to cast a Value* that's really a > BB* (from the PHInode operands) to a User*,
2004 Jun 23
0
[LLVMdev] weird issue with mem2reg, should have guessed
What's different about code that's been mem2reg'd from straight front end code, or anything that mem2reg hasn't been run on? PHINODES! It appears to be crashing when I try to cast a Value* that's really a BB* (from the PHInode operands) to a User*, insteresting since I am dyn_casting. I just caught this on cerr though (printing out what the Value* was each time). Let me
2004 Jun 23
2
[LLVMdev] weird issue with mem2reg, still
On Wed, 23 Jun 2004, Patrick Meredith wrote: > Somehow it fails with operand out of bounds when the number of operands > is 2 and I am asking for the second operand. Second meaning operand 1. Okay, so you have something like this: if (CallInst *CI = dyn_cast<CallInst>(...)) { ... = CI->getOperand(1); } Can you send in this snippet of code, the assertion, and the
2004 Dec 31
2
[LLVMdev] I'm almost able to build a complete tool suite of LLVM.
Hi Chris, Jeff and Reid, Today, I was almost able to build a complete tool suite of LLVM in the MinGW environment. However, llvm-db and bugpoint couldn't build due to some non-win32 intrinsics. If we could iron these errors out, then I think we could tell to jeff and others, to setup a win32 VC-project to compile the tool suite. Any suggestions? Happy new year to you all. Henrik.
2004 Jun 23
0
[LLVMdev] weird issue with mem2reg, still
Somehow it fails with operand out of bounds when the number of operands is 2 and I am asking for the second operand. ----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: <llvmdev at cs.uiuc.edu> Sent: Wednesday, June 23, 2004 4:24 PM Subject: Re: [LLVMdev] weird issue with mem2reg, should have guessed > On Wed, 23 Jun 2004, Patrick Meredith
2005 Apr 20
0
[LLVMdev] misc CVS patches
On Apr 20, 2005, at 0:01, Misha Brukman wrote: > Sure. Patches are accepted, but please separate formatting changes > from > functionality changes into different patches. Speaking of random formatting changes, I've noticed in a few pages that the doxygen documentation comments incorrectly only have two '//' characters on the line. Hence, no doxygen documentation gets
2005 Apr 20
1
[LLVMdev] misc CVS patches
On Wed, 20 Apr 2005, Evan Jones wrote: > On Apr 20, 2005, at 0:01, Misha Brukman wrote: >> Sure. Patches are accepted, but please separate formatting changes from >> functionality changes into different patches. > > Speaking of random formatting changes, I've noticed in a few pages that the > doxygen documentation comments incorrectly only have two '//'
2005 Apr 21
4
[LLVMdev] Trailing whitespace removal (important for CVS users!)
On Thu, 21 Apr 2005, Reid Spencer wrote: > Why not put all this into a pre-commit filter in CVS and be done with > it? We'd never be bothered with it again as it would never be committed > again. I'd rather not have CVS commit scripts mucking with the code. If you want to have the nightly tester whine about source code with spaces at the end of lines (like it whines about
2004 Jun 23
0
[LLVMdev] weird issue with mem2reg, still
void MetaSplit::handleProgramUses(Value *V){ if(!isa<BasicBlock>(V)) programValues.insert(V); if(User *U = dyn_cast<User>(V)){ User::op_iterator OB = U->op_begin(), OE = U->op_end(); for(; OB != OE; ++OB){ if(CallInst *CI = dyn_cast<CallInst>(*OB)){ Function *F = CI->getCalledFunction(); if(F == ii || F == fi || F == vi || F == di || F == ci
2004 Dec 23
2
[LLVMdev] [patch] native AMD64 support
On Thu, Dec 23, 2004 at 06:42:02AM +0100, Markus F.X.J. Oberhumer wrote: > with the small patch attached below the whole llvm toolchain (llvm & > llvm-gcc) will compile and run under AMD64 Linux in native 64-bit LP64 > mode. Sounds great! I'll add it to the list of supported platforms. > This means that compilation, bytecode management and CWriter output > all work as
2005 Jun 02
2
[LLVMdev] Randomizing Functions & Global variables
Aaron, On Thu, Jun 02, 2005 at 10:38:58PM +0100, Aaron Gray wrote: > http://www.st.cs.uni-sb.de/~lindig/src/quest/ I don't know about Tanu, but we can certainly use this in finding bugs in LLVM! This has been listed as an "open project" for a long time [1], but someone already implemented it, saving us the time and effort. Thanks for the link! [1]
2004 Dec 31
0
[LLVMdev] I'm almost able to build a complete tool suite of LLVM.
On Fri, Dec 31, 2004 at 09:41:24PM +0100, Henrik Bach wrote: > Today, I was almost able to build a complete tool suite of LLVM in the > MinGW environment. Great! > However, llvm-db and bugpoint couldn't build due to some non-win32 > intrinsics. If we could iron these errors out, then I think we could > tell to jeff and others, to setup a win32 VC-project to compile the >
2005 Feb 17
5
[LLVMdev] questions about installing llvm
Actually, Misha, that won't work. The -C option is used directly in docs/Makefile. So the change will have to go into docs/Makefile. Either that or upgrade install to version 5. Reid. On Thu, 2005-02-17 at 11:33, Misha Brukman wrote: > On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote: > > llvm[1]: Installing HTML documentation > >
2004 Dec 31
1
[LLVMdev] I'm almost able to build a complete tool suite of LLVM.
----Original Message Follows---- From: Misha Brukman <brukman at uiuc.edu> Reply-To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] I'm almost able to build a complete tool suite of LLVM. Date: Fri, 31 Dec 2004 15:10:47 -0600 >Great! Thank you. >As a result, to be compiled/ran on
2005 May 17
2
[LLVMdev] Register Allocation problem
Ok, i'm having a problem with understanding the allocating of registers. I've written in the "addPassesToEmitAssembly()" the passes to create the assembly code, as in the PowerPC example. I'ved tried filling up as much of the code in <Target>RegisterInfo.cpp (Register/Frame code) to handle writing and reading from stack. The allocation method I used was