similar to: [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

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

Right, I just meant which specific header files should move. Pass manager doesn't seem like it should, for example. -Chris On Dec 23, 2012, at 8:13 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > 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

On Sun, Dec 23, 2012 at 6:49 PM, Chris Lattner <clattner at apple.com> wrote: > Right, I just meant which specific header files should move. Pass manager > doesn't seem like it should, for example. > lib/VMCore/PassManager.cpp indicates to me that include/llvm/PassManager.h should become include/llvm/IR/PassManager.h It feels like what you're really interested in is

Hi all, This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In fact, the lib/VMCore/AsmWriter.cpp file performs a layering violation, because it calculates the DWARF tag

On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. > > Why? Because this module has nothing to do with analysis. It simply defines an interface to the debug info MDNodes. In

On Jun 27, 2012, at 4:20 PM, Eric Christopher wrote: > > On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > >> Hi all, >> >> This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to lib/VMCore/DebugInfo.cpp and include/llvm/Analysis/DebugInfo.h to include/llvm/DebugInfo.h. >> >> Why? Because this module has

2012/11/22 Chandler Carruth <chandlerc at google.com>: > Hello LLVM & Clang hackers! > > Based on a discussion with Chris, I would like to propose a Great > Renaming of Things for the 3.3-era LLVM and Clang codebase. > > First and foremost, the two most significant changes I would like to make: > > 1) llvm/lib/VMCore/... -> llvm/lib/IR/... > > I've

Hello LLVM & Clang hackers! Based on a discussion with Chris, I would like to propose a Great Renaming of Things for the 3.3-era LLVM and Clang codebase. First and foremost, the two most significant changes I would like to make: 1) llvm/lib/VMCore/... -> llvm/lib/IR/... I've discussed potential names for the VMCore (or LLVMCore) library with lots of folks, and the best idea anyone

On Thu, Nov 22, 2012 at 1:53 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > 2012/11/22 Chandler Carruth <chandlerc at google.com>: >> Hello LLVM & Clang hackers! >> >> Based on a discussion with Chris, I would like to propose a Great >> Renaming of Things for the 3.3-era LLVM and Clang codebase. >> >> First and foremost, the two most

Evening, I was writing some code that tried to insert calls to the llvm.annotation intrinsic function, which has a signature of (i32, i8*, i8*, i32). The code is below. void addAnnotation( BasicBlock *block, Function *F) { string foo = "foo"; string bar = "barr"; Type *charTy = Type::getInt8Ty(block->getContext()); ArrayType *s1Ty =

Andrew Ruef wrote: > Evening, > > I was writing some code that tried to insert calls to the > llvm.annotation intrinsic function, which has a signature of (i32, > i8*, i8*, i32). The code is below. > > void addAnnotation( BasicBlock *block, Function *F) > { > string foo = "foo"; > string bar = "barr"; > > Type

I have several RHEL AS 4 systems, and when we get a vmcore, I would like to view them in my centos box.. How can I do that? Is that even possible? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070918/af909c9b/attachment.html>

I would like to analyze a kernel vmcore. Are there any docs you can recommend for me to read to understand the process? TIA

On Nov 22, 2012, at 3:02 AM, Chandler Carruth <chandlerc at google.com> wrote: >>> First and foremost, the two most significant changes I would like to make: >>> >>> 1) llvm/lib/VMCore/... -> llvm/lib/IR/... >>> >>> I've discussed potential names for the VMCore (or LLVMCore) library >>> with lots of folks, and the best idea

On 11/22/12 04:53 PM, NAKAMURA Takumi wrote: > 2012/11/22 Chandler Carruth<chandlerc at google.com>: >> Hello LLVM& Clang hackers! >> >> Based on a discussion with Chris, I would like to propose a Great >> Renaming of Things for the 3.3-era LLVM and Clang codebase. >> >> First and foremost, the two most significant changes I would like to make:

On Thu, Jun 28, 2012 at 4:22 AM, Bill Wendling <wendling at apple.com> wrote: > On Jun 27, 2012, at 4:20 PM, Eric Christopher wrote: > > > > > On Jun 27, 2012, at 4:08 PM, Bill Wendling <wendling at apple.com> wrote: > > > >> Hi all, > >> > >> This patch, though large, simply moves lib/Analysis/DebugInfo.cpp to >

Hi, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

There are some bugs against it that state the current progress. The problem is that it depends on how the libraries are being used. Even if you get past the linking problems, you will end up with re-registration of passes and options, etc., which causes asserts. So, for now, there aren't many good solutions. Reid. On Thu, 2006-06-22 at 17:21 -0500, John Criswell wrote: > Has anything

The recent change in the library structure to make libLLVMCore.a instead of LLVMCore.o has caused a little fallout. The problem is LLVM tools that take a --load option to load a module dynamically may now cause those modules to fail to load at runtime. This occurs because the tool with the --load option might not be linking in all of libLLVMCore.a, but only the object modules actually needed by