Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] A few more questions about DIFactory and source-level debugging."
2010 Nov 07
3
[LLVMdev] Next round of DWARF issues/questions
After to speaking to Devang and a number of other people at the developer's
conference, I was able to make some forward progress on getting debugging to
work. I'm now able to actually single-step through my program and set
breakpoints, and examine function parameters.
However, I'm also seeing a lot of new problems which weren't exposed before.
After spending the better part of two
2010 Nov 08
0
[LLVMdev] Next round of DWARF issues/questions
On Nov 6, 2010, at 7:35 PM, Talin wrote:
> After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters.
>
> However, I'm also seeing a lot of new problems which
2010 Nov 09
2
[LLVMdev] Next round of DWARF issues/questions
On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote:
>
> On Nov 6, 2010, at 7:35 PM, Talin wrote:
>
> After to speaking to Devang and a number of other people at the developer's
> conference, I was able to make some forward progress on getting debugging to
> work. I'm now able to actually single-step through my program and set
> breakpoints,
2010 Nov 09
0
[LLVMdev] Next round of DWARF issues/questions
On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote:
> On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote:
>
> On Nov 6, 2010, at 7:35 PM, Talin wrote:
>
>> After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now
2010 Nov 26
3
[LLVMdev] Next round of DWARF issues/questions
On Tue, Nov 9, 2010 at 9:04 AM, Devang Patel <dpatel at apple.com> wrote:
>
>
> On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote:
>
> On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel < <dpatel at apple.com>
> dpatel at apple.com> wrote:
>
>>
>> On Nov 6, 2010, at 7:35 PM, Talin wrote:
>>
>> After to speaking to Devang
2005 Nov 16
1
[LLVMdev] Does llvm-db work?
Problem 1:
I tried llvm-db of LLVM 1.6, in the Linux environment. However, it always
prompts the following info for different tests:
======================================
:> llvm-db a.out.bc
llvm-db: The LLVM source-level debugger
Loading program... successfully loaded 'a.out.bc'!
(llvm-db) run
Starting program: a.out.bc
Error: Error waiting for the child process to stop. It exited
2009 Sep 30
2
[LLVMdev] Internalize pass
I'm playing around with different combinations of LTO passes, and I've run
into a strange problem:
I have a 'main' function that looks like this:
define i32
@"main(tart.core.Array[tart.core.String])->int"(%"tart.core.Array[tart.core.String]"*
%args) {
entry:
call void @llvm.dbg.func.start(metadata !0)
call void @llvm.dbg.stoppoint(i32 2, i32 19, metadata
2009 Sep 30
0
[LLVMdev] Internalize pass
On Sep 30, 2009, at 12:06 AM, Talin wrote:
> I'm playing around with different combinations of LTO passes, and
> I've run into a strange problem:
>
> I have a 'main' function that looks like this:
>
> define i32 @"main(tart.core.Array[tart.core.String])-
> >int"(%"tart.core.Array[tart.core.String]"* %args) {
> entry:
> call
2009 Oct 03
2
[LLVMdev] Internalize pass
Well, after some investigation I have a few more clues as to what is
going on.
I have a module which contains a call to an external native function.
This native function lives in a static library, and there is an external
declaration for it in the module.
I find that I can run "llvm-ld -disable-opts -native -l mylibrary
test.bc" and it works fine. That is, llvm-ld is able to
2008 Oct 11
1
[LLVMdev] Debug Information
On 2008-10-11 00:34, Evan Cheng wrote:
> On Oct 10, 2008, at 1:43 PM, John Criswell wrote:
>
>
>> Dear All,
>>
>> Are there a set of libraries for easily manipulating the LLVM debug
>> information? For example, given an Instruction *, is there an
>> interface
>> that will find the nearest llvm.dbg.stoppoint(), or given an alloca,
>> is
2009 Oct 03
0
[LLVMdev] Internalize pass
Sounds like LLVM thinks the calling conventions or declarations are
mismatched. See:
http://llvm.org/docs/FAQ.html#callconvwrong
Reid
On Sat, Oct 3, 2009 at 1:16 AM, Talin <viridia at gmail.com> wrote:
> Well, after some investigation I have a few more clues as to what is
> going on.
>
> I have a module which contains a call to an external native function.
> This native
2009 May 19
1
[LLVMdev] How to get line number and source file name for IR?
Dear Staff,
I am asking this question: given a line of IR code in *.ll file,
how can I know the corresponding line number and C/C++ source file
name for this IR code?
I am investigating some code patterns with LLVM IR, I need to
know where this IR code come from (the line number in a source file
name).
An existing way is using -g option to compile my software, then I
can
2009 Sep 24
3
[LLVMdev] Is line number in DbgStopPointInst in LLVM accurate?
Dear developers,
When I try to map line numbers in source code back to LLVM
basicblocks, I meet some problems: there is a source file with 1500
lines of code, but when I use BasicBlockPass to collect all
DbgStopPoint instructions in this file, I can only get 500 lines of
code.
The source code and the collected results are both attached.
Is there any way to map line numbers
2010 Aug 29
0
[LLVMdev] "Cannot fine DIE"
On Sat, Aug 28, 2010 at 4:05 PM, Talin <viridia at gmail.com> wrote:
> On Mon, Aug 23, 2010 at 5:58 PM, Devang Patel <devang.patel at gmail.com>wrote:
>
>>
>> On Sun, Aug 22, 2010 at 12:50 PM, Talin <viridia at gmail.com> wrote:
>>
>>> I recently started getting this error when I try to debug my
>>> LLVM-compiled program in GDB:
2010 Nov 26
0
[LLVMdev] Next round of DWARF issues/questions
On Thu, Nov 25, 2010 at 5:55 PM, Talin <viridia at gmail.com> wrote:
> On Tue, Nov 9, 2010 at 9:04 AM, Devang Patel <dpatel at apple.com> wrote:
>
>>
>>
>> On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote:
>>
>> On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel < <dpatel at apple.com>
>> dpatel at apple.com> wrote:
2004 Oct 05
1
[LLVMdev] debugging info questions
Hi, It's taking me a while to get familiar with the cfe in order to
add emitting stop points for debugging. It's a lot to work through, so
in order to speed things up, I've got a few questions. Any help would
be appreciated.
I understand the design of the intrinsics once they're in the code,
but how to generate them is still a little fuzzy, mainly because
llvm_expand is a little
2010 Jun 21
1
[LLVMdev] Extracting Metadata of Variables
Hi,
Im new to llvm and I'm using llvm-2.6 and I know how to extract the metadata
in the stoppoints but what I'm interested in is the meta data regarding a
local variable. I know that the @llvm.dgb.declare such as:
call void @llvm.dbg.declare({ }* %2, { }* bitcast (%llvm.dbg.variable.type*
@llvm.dbg.variable9 to { }*))
links to meta data for @llvm.dbg.variable9 which is:
2010 Oct 23
2
[LLVMdev] Cast failure in SelectionDAGBuilder
I'm trying to track down the problem with the assertion failure in
SelectionDAGBuilder.cpp. This is the code:
*case* *Intrinsic*::gcroot:
*if* (GFI) {
*const* Value *Alloca = I.getArgOperand(0);
*const* Constant *TypeMap = cast<Constant>(I.getArgOperand(1));
* FrameIndexSDNode *FI =
cast<FrameIndexSDNode>(getValue(Alloca).getNode());*
2016 Dec 15
2
distinct DISubprograms hindering sharing inlined subprogram descriptions
On Thu, Dec 15, 2016 at 1:30 PM Teresa Johnson <tejohnson at google.com> wrote:
On Thu, Dec 15, 2016 at 11:38 AM, David Blaikie <dblaikie at gmail.com> wrote:
On Thu, Dec 15, 2016 at 11:26 AM Teresa Johnson <tejohnson at google.com>
wrote:
Trying to wrap my brain around this, so a few questions below. =)
Sure thing - sorry, did assume a bit too much arcane context here.
2011 Apr 07
1
[LLVMdev] More DWARF problems
On Apr 7, 2011, at 12:14 PM, Talin wrote:
>
> OK I've been checking this out some more, and the DIEs don't look valid to me. Take a look at this output from dwarfdump -v:
>
> 0x000000c7: TAG_subprogram [3]
> 0x000000c8: AT_name( .debug_str[0x000001bd] = "construct" )
> 0x000000cc: AT_MIPS_linkage_name( .debug_str[0x000001c7] =