Anton Vayvod
2006-Aug-16 17:15 UTC
[LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
I'm willing :) I don't know how to do it. What's "to put together a patch"? :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060816/fb1f0b57/attachment.html>
Chris Lattner
2006-Aug-16 17:44 UTC
[LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
On Wed, 16 Aug 2006, Anton Vayvod wrote:> I'm willing :) I don't know how to do it. > What's "to put together a patch"? :)In your local CVS tree, change the methods to be const, and adjust any code that is neccesary for that to work. Once that is done, from the top level, type 'cvs diff -u >& patch.txt' and attach patch.txt to an email. If you're using sh instead of csh, use 'cvs diff -u 2>&1 > patch.txt'. Thanks, -Chris -- http://nondot.org/sabre/ http://llvm.org/
Anton Vayvod
2006-Aug-16 19:24 UTC
[LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
Ok, I'm in process. Do I need to checkout the latest llvm source, first? I updated last right after the 1.8 release. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20060816/fcf027c1/attachment-0001.html>
Ralph Corderoy
2006-Aug-17 10:11 UTC
[LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
Hi Chris,> On Wed, 16 Aug 2006, Anton Vayvod wrote: > > I'm willing :) I don't know how to do it. What's "to put together a > > patch"? :) > > In your local CVS tree, change the methods to be const, and adjust any > code that is neccesary for that to work. Once that is done, from the > top level, type 'cvs diff -u >& patch.txt' and attach patch.txt to an > email. > > If you're using sh instead of csh, use 'cvs diff -u 2>&1 > patch.txt'.The sh equivalent of that csh is cvs diff -u >patch.txt 2>&1 The first duplicates stderr onto stdout and then changes stdout to be patch.txt leaving stderr to go to wherever stdout used to go. The second changes stdout to be patch.txt and then duplicates stderr to go there too. This flexibility is one of sh's advantages over csh. ;-) Cheers, Ralph.
Dear guys, my llvm-gcc does not compile stdlib.h correctly. I found this explanation here: http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=567 Indeed, I am running Mac OS 10.4. Do I have to rebuild my gcc front-end from source, or there is a script in the LLVM website that could help me? Best regards, Fernando
Maybe Matching Threads
- [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
- [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
- [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
- [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction
- [LLVMdev] allocation_order_begin takes non-const reference for MachineFunction