Chandler Carruth
2012-Dec-21 21:24 UTC
[LLVMdev] Heads up -- take two for renaming VMCore -> IR
Hello folks, Now that the includes are sortable and I have another chunk of free time, I'll be making another attempt at the mass renaming from VMCore to IR for LLVM. I'm also planning to move the header files currently in the top level for LLVM down into the appropriate subdirectory. I'll create an IR directory for the headers that really belong to that library component. However, I'm going to look at each header, and if I can either lift it into Support, or sink it all the way into Analysis or some other lower library, I will do that. I'll move each header one at a time so that folks can chime in on the review thread if there are questions / concerns about the layering here. -Chandler -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121221/fcf85b6c/attachment.html>
On Fri, Dec 21, 2012 at 2:24 PM, Chandler Carruth <chandlerc at gmail.com> wrote:> Now that the includes are sortable and I have another chunk of free time, > I'll be making another attempt at the mass renaming from VMCore to IR for > LLVM.Please make sure to update any documentation that references VMCore. -- Sean Silva
Chris Lattner
2012-Dec-23 05:05 UTC
[LLVMdev] Heads up -- take two for renaming VMCore -> IR
Sounds great, thanks Chandler. In addition to each file being discussed, it would be nice to have a high level plan to kick things off. -Chris On Dec 21, 2012, at 10:24 PM, Chandler Carruth <chandlerc at gmail.com> wrote:> Hello folks, > > Now that the includes are sortable and I have another chunk of free time, I'll be making another attempt at the mass renaming from VMCore to IR for LLVM. > > I'm also planning to move the header files currently in the top level for LLVM down into the appropriate subdirectory. I'll create an IR directory for the headers that really belong to that library component. However, I'm going to look at each header, and if I can either lift it into Support, or sink it all the way into Analysis or some other lower library, I will do that. I'll move each header one at a time so that folks can chime in on the review thread if there are questions / concerns about the layering here. > > -Chandler > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121223/96c28925/attachment.html>
Chandler Carruth
2012-Dec-23 07:13 UTC
[LLVMdev] Heads up -- take two for renaming VMCore -> IR
On Sat, Dec 22, 2012 at 9:05 PM, Chris Lattner <clattner at apple.com> wrote:> Sounds great, thanks Chandler. In addition to each file being discussed, > it would be nice to have a high level plan to kick things off. >What exact plan are you looking for?>From the original thread:- lib/VMCore -> lib/IR - include/llvm/Foo.h -> include/llvm/IR/Foo.h (if Foo.h belongs in that library) I didn't have a more detailed plan. ;] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121222/a93a82f1/attachment.html>
Maybe Matching Threads
- [LLVMdev] Heads up -- take two for renaming VMCore -> IR
- [LLVMdev] Heads up -- take two for renaming VMCore -> IR
- [LLVMdev] Heads up -- take two for renaming VMCore -> IR
- [LLVMdev] Heads up -- take two for renaming VMCore -> IR
- [LLVMdev] [PATCH] Moving DebugInfo module to VMCore