Displaying 20 results from an estimated 6000 matches similar to: "hi, Is there any solution about how to add some dwarf info to the IR bitcode file."
2017 Nov 15
2
答复: hi, Is there any solution about how to add some dwarf info to the IR bitcode file.
Hi Andrew
I am newbie. There are many headers and classes, I do not know how to use to add dwarf info to bc file.
Can you show me the demo or example, is there any info about how to use these classes step by step.
BR
Owen
发件人: Andrew Kelley [mailto:superjoe30 at gmail.com]
发送时间: 2017年11月15日 12:51
收件人: Wuweijia <wuweijia at huawei.com>
抄送: 陳韋任
2017 Nov 11
2
[Help]Is there any information or examples about how to build the application with llvm api?（about how to preprocess, compile , opt)
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html;
2013 Jun 28
3
[LLVMdev] Hi, people, I propose to move Debug and Object File related headers out of Support
For example,
ELF.h MachO.h and COFF.h
should moved into Object directory with new name.
and Dwarf.h should moved into DebugInfo directory.
2013/6/29 Eric Christopher <echristo at gmail.com>:
> Where would you like to move them?
>
> -eric
>
> On Fri, Jun 28, 2013 at 10:38 AM, 罗勇刚(Yonggang Luo)
> <luoyonggang at gmail.com> wrote:
>> From my point of view, the
2013 Jun 28
0
[LLVMdev] Hi, people, I propose to move Debug and Object File related headers out of Support
Going to be interesting layering issues if you do the latter. Then you
have CodeGen depending upon DebugInfo instead of just a header in
Support.
-eric
On Fri, Jun 28, 2013 at 11:08 AM, 罗勇刚(Yonggang Luo)
<luoyonggang at gmail.com> wrote:
> For example,
> ELF.h MachO.h and COFF.h
> should moved into Object directory with new name.
> and Dwarf.h should moved into DebugInfo
2014 May 07
2
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
Hi,
I am looking for a way to get unmangled subprogram names from a
DWARFContext. The name I want is available in the attribute `DW_AT_name`
[1], but as far as I can tell this is only returned as a fallback in
`DWARFDebugInfoEntryMinimal::getSubroutineName` when the linkage name is
not available [2].
If this is not currently possible, is there any interest in adding such
access to the public
2011 Nov 02
1
[LLVMdev] supporting dwarf relocations
In ELF .o files with debug info, there are relocations applied to the DWARF
sections. For example, when emitting offsets into the stringpool, we emit a
relocation.
How should we support this? llvm-dwarfdump currently works by finding the
relevant dwarf sections and passing them in to lib/DebugInfo. The
relocations can be iterated over in lib/Object using the
relocation_iterator.
Should dwarfdump
2014 May 07
2
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
That doesn't seem possible with the public API or am I mistaking?
On Wed, May 7, 2014 at 12:13 AM, Eric Christopher <echristo at gmail.com>wrote:
> On Tue, May 6, 2014 at 8:09 PM, Isaiah Norton <isaiah.norton at gmail.com>
> wrote:
> > Hi,
> >
> > I am looking for a way to get unmangled subprogram names from a
> > DWARFContext. The name I want is
2013 Jan 18
0
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
On Fri, Jan 18, 2013 at 3:13 PM, Eli Bendersky <eliben at google.com> wrote:
> >> > I'm fine with this as long as llvm-dwarfdump gets maintained.
> >> >
> >>
> >> I agree, and as I said in the original email, in the long term I
> >> believe llvm-dwarfdump is the correct solution.
> >>
> >
> > The problem is that if
2014 May 07
2
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
The use case is getting the short name for backtraces. There are other
options, but I figured it was worth a shot trying to access from the DWARF
structure because what we need is already stored there anyway.
Thanks,
Isaiah
On Wed, May 7, 2014 at 12:24 PM, Alexey Samsonov <samsonov at google.com>wrote:
> Yeah, public API of DebugInfo library is quite minimalistic. But I agree
>
2013 Jan 18
3
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
>> > I'm fine with this as long as llvm-dwarfdump gets maintained.
>> >
>>
>> I agree, and as I said in the original email, in the long term I
>> believe llvm-dwarfdump is the correct solution.
>>
>
> The problem is that if no one is working on testing these sorts of things
> with llvm-dwarfdump then it won't be maintained for this
2019 Mar 20
3
DWARF debug info unit tests: Tests for wrong triple?
The DWARF debug info unit tests in llvm/unittests/DebugInfo/DWARF/ forms a
generator based on the host triple. This is problematic for cross-compile
configurations where LLVM does not fully support code generation for the
host platform.
I have found no rationale for why the host triple was chosen (ref:
https://reviews.llvm.org/D27326?id=80002#inline-236026).
I would imagine that it is more
2013 Jan 18
0
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
On Fri, Jan 18, 2013 at 1:00 PM, Eli Bendersky <eliben at google.com> wrote:
> Hi All,
>
> While working on some recent patches for x32 support, I ran into an
> unpleasant limitation the LLVM eco-system has with testing DWARF
> emission. We currently have several approaches, neither of which is
> great:
>
> 1. llvm-dwarfdump: the best approach when it works. But
2013 Jan 22
0
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
On Fri, Jan 18, 2013 at 4:00 PM, Eli Bendersky <eliben at google.com> wrote:
> Hi All,
>
> While working on some recent patches for x32 support, I ran into an
> unpleasant limitation the LLVM eco-system has with testing DWARF
> emission. We currently have several approaches, neither of which is
> great:
>
> 1. llvm-dwarfdump: the best approach when it works. But
2014 May 07
2
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
On Wed, May 7, 2014 at 11:33 AM, Eric Christopher <echristo at gmail.com>wrote:
> Have you checked out llvm-symbolize? It's what the asan folk
> (including Alexey) have created for backtrace symbolication.
>
Yeah, we potentially can add some kind of option: "llvm-symbolizer
-print-short-function-names", I don't yet see why this would be valuable.
What's wrong
2019 Apr 24
2
[DebugInfo] DWARF C API
Hi folks,
I am trying to implement the C bindings API for DebugInfo::DWARF::DWARFDie.
My goal is to have a C library that reads and parses DWARF debugging format
(just like how llvm-dwarfdump does, but maybe more than just dumping debug
info)
I've started with creating C structure for DebugInfo::DWARF::DWARFContext
which contains all DWARF DIEs in the object file. For this I used
```
2019 Dec 06
2
[DWARF5][SplitDwarf] question on using fsplit-dwarf-inlining option
Hi DebugInfo folks,
I have a question on using fsplit-dwarf-inlining option:
"-fsplit-dwarf-inlining, -fno-split-dwarf-inlining
Provide minimal debug info in the object/executable to facilitate online
symbolication/stack traces in the absence of .dwo/.dwp files when using
Split DWARF"
i.e. it puts some debug info into compilation unit from First
partition(with Skeleton unit).
At
2013 Jan 22
0
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
>>> 2. Relying of assembly directive emissions (i.e. .cfi_*), which is
>>> cumbersome and misses a lot of things like actual DWARF encoding.
>>
>> I'm not sure what you mean by "actual DWARF encoding" here.
>> (disclaimer: I've only recently started dabbling with debug info, so I
>> may be missing obvious things)
>
> I mean that it
2013 Jan 18
7
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
Hi All,
While working on some recent patches for x32 support, I ran into an
unpleasant limitation the LLVM eco-system has with testing DWARF
emission. We currently have several approaches, neither of which is
great:
1. llvm-dwarfdump: the best approach when it works. But unfortunately
lib/DebugInfo supports only a (small) subset of DWARF. Tricky sections
like debug_frame aren't supported.
2.
2013 Jan 18
0
[LLVMdev] RFC: Improving our DWARF (and ELF) emission testing capabilities
+ other debug info people (Eric & Paul)
On Fri, Jan 18, 2013 at 1:00 PM, Eli Bendersky <eliben at google.com> wrote:
> Hi All,
>
> While working on some recent patches for x32 support, I ran into an
> unpleasant limitation the LLVM eco-system has with testing DWARF
> emission. We currently have several approaches, neither of which is
> great:
>
> 1.
2018 Aug 22
2
[DebugInfo] DIBuilder missing interface to generate DWARF info for packed_decimal basic type.
Adding tags on subject line
From: Chirag Patel
Sent: 22 August 2018 11:20
To: llvm-dev at lists.llvm.org
Subject: DIBuilder missing interface to generate DWARF info for packed_decimal basic type.
Hello,
I am working on a llvm based compiler frontend in which, I am using the packed_decimal type encoding.
During using the llvm DIBuilder, I found out that the interface to create BasicType with