similar to: [LLVMdev] Associate IR instruction with corresponding assembly

Interesting. My guess is that the debug-ir pass wasn't updated when we changed some version of the debug metadata and so isn't producing good metadata. I'm not sure when I'll get to updating it though and it looks like Daniel's address is bouncing. -eric On Mon, May 19, 2014 at 8:22 AM, shruti padmanabha <shrupad at umich.edu> wrote: > No. They're both from the

Hi, Compiling for both x86 and ARM with llc aborts after this pass. I have a simple helloworld.c program. I am attaching the .ll file created by: *clang -O3 -g -emit-llvm hello.c -c -o hello.bc* *llvm-dis hello.bc* Thanks again for the response! Shruti On Mon, May 19, 2014 at 1:28 AM, Tobias Grosser <tobias at grosser.es> wrote: > On 19/05/2014 00:54, shruti padmanabha wrote: >

Hi, Thanks for the pointer. I am unfortunately running into llc problems with this pass. I did *opt -debug-ir hello.bc -o hello.deb.bc* *llc -march=arm -debug -O0 hello.deb.bc -o hello.deb.s* This is aborting with the error: llc: llvm-3.4/lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1614: void llvm::DwarfDebug::beginFunction(const llvm::MachineFunction*): Assertion `TheCU && "Unable

On Sun, May 18, 2014 at 10:28 PM, Tobias Grosser <tobias at grosser.es> wrote: > On 19/05/2014 00:54, shruti padmanabha wrote: >> >> Hi, >> >> Thanks for the pointer. I am unfortunately running into llc problems with >> this pass. >> I did >> *opt -debug-ir hello.bc -o hello.deb.bc* >> >> *llc -march=arm -debug -O0 hello.deb.bc -o

Hi, My name is shruti,When I was trying to check the package I got this error "Data sets with usage in documentation object 'data' but not in the code" Can any one help me with this.I'm attaching the file for your reference http://n4.nabble.com/file/n1695616/dataset.jpg Thank you -- View this message in context:

Hi ,My name is shruti,I'm new to R when i was checking my package i got a error message saying Running Example in pkg-Ex.R failed.can any one help me with this.I'm inserting command prompt reference for your reference. Thank you, http://n4.nabble.com/file/n1693503/running_ex.jpg -- View this message in context:

Hi, I am using Extrafont package to install more fonts for my graphs. My primary graphic tool is ggplot2. I seem to have problem installing the package, but could not pinpoint where it is. I try to follow the instruction here: https://github.com/wch/extrafont I guess (but am not sure) the fonts are successfully installed. Problem encountered: 1. The following line sometimes yields an

Hi, I'd like to modify MachineBasicBlock contents within a MachineFunctionPass on the basis of how many CPU cycles the assembly instructions corresponding to the MBB take. I'm using the AVR backend and the number of CPU cycles every AVR assembly operation takes is openly available. Is there any straightforward way of getting the opcode mnemonics corresponding to a MachineInstr? I've

Hi, I am trying to get arguments of call functions in instructions such as these: call @func(i32 %arg1, i32 %arg2). I want to get the declared variable names for arg1 and arg2. Most of these arguments are arrays, and I need to get the index of the array as well. Currently, I read arguments of the called function using getArgOperands(), and backtrace the Value* until I find an alloca

Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >> > Hi waldi, >> > >> > Are you planning to update the Xen package too 4.4 soon? Upstream have >> > released 4.4-rc6 and AIUI are planning to release the final version >> next >> > week (I've been out of the office for a bit, so I

Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >> > Hi waldi, >> > >> > Are you planning to update the Xen package too 4.4 soon? Upstream have >> > released 4.4-rc6 and AIUI are planning to release the final version >> next >> > week (I've been out of the office for a bit, so I

I didn't make it clear that I load my Common Lisp application into "lldb" and then load a compiled bundle into my application using dlopen (I'm on OS X and I'm generating a kind of shared library called a "bundle"). Once everything is loaded, the functions from the bundle are accessible to my Common Lisp environment but I don't seem to be able to access the

Hey folks, I'm wrestling with adding DWARF source code file/line information to my generated LLVM-IR from my Common Lisp compiler. I think I'm doing everything properly using the llvm::DIBuilder class - but when I load my Common Lisp application and load a compiled bundle into it I don't seem to be able to access the metadata properly. I can list source lines using "l -f

https://bugs.freedesktop.org/show_bug.cgi?id=78863 Priority: medium Bug ID: 78863 Assignee: nouveau at lists.freedesktop.org Summary: [nv50] errors when starts gnome-shell QA Contact: xorg-team at lists.x.org Severity: minor Classification: Unclassified OS: All Reporter: mattia.b89 at gmail.com

In a pass I’m working on, I’ve done some manipulation of several functions, replacing them with new copies with different types, etc. The LLVM IR passes the verifier, but when I have debug symbols enabled (“-g”), I get the following error when Clang generates the Dwarf info (using a very recent build of LLVM/Clang from Git mirror): > Assertion failed: (TheCU && "Unable to find

Hmm, are you using a version of LLVM with asserts enabled (I.e. A debug build)? I cut-and-paste your IR into a text file and ran (a debug version of) llc on it, which caused the following assertion failure that seems related to some DWARF mishap: llc: ../lib/CodeGen/AsmPrinter/DwarfDebug.cpp:1400: void llvm::DwarfDebug::beginFunction(const llvm::MachineFunction*): Assertion `TheCU &&

> I disagree on this. Table emission by itself doesn't involve code > generation and I don't think it makes sense as a per function attribute > either. You either want it for all functions or only when needed (e.g. > exceptions are possible). As such, it makes perfect sense to me as a > global flag. It has to be an attribute because of LTO. You can LTO a file compiled with

I upgraded my versions of llvm, clang and compiler-rt to the top-of-tree versions from last night (r180162, April 24). I recompiled debug versions of llvm, clang and my code. I then regenerated my test case and the results were the same - I can list lines of dwarf1.lsp in lldb but I can't set break-points or do anything else (what else should I be able to do?). The updated file that

> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: > > Hi waldi, > > > > Are you planning to update the Xen package too 4.4 soon? Upstream have > > released 4.4-rc6 and AIUI are planning to release the final version next > > week (I've been out of the office for a bit, so I don't know the precise > > state, but that was the last I heard). >

> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: > > Hi waldi, > > > > Are you planning to update the Xen package too 4.4 soon? Upstream have > > released 4.4-rc6 and AIUI are planning to release the final version next > > week (I've been out of the office for a bit, so I don't know the precise > > state, but that was the last I heard). >