Displaying 8 results from an estimated 8 matches for "executeobjcopyonbinari".
Did you mean:
executeobjcopyonbinary
2020 Aug 25
9
[Proposal][Debuginfo] dsymutil-like tool for ELF.
Hi,
We propose llvm-dwarfutil - a dsymutil-like tool for ELF.
Any thoughts on this?
Thanks in advance, Alexey.
======================================================================
llvm-dwarfutil(Apndx A) - is a tool that is used for processing debug
info(DWARF)
located in built binary files to improve debug info quality,
reduce debug info size and accelerate debug info processing.
2020 Aug 26
3
[Proposal][Debuginfo] dsymutil-like tool for ELF.
On 26.08.2020 10:58, James Henderson wrote:
> In principle, this sounds reasonable to me. I don't know enough about
> dsymutil's interface to know whether it makes sense to try to make it
> multi-format compatible or not. If it doesn't I'm perfectly happy for
> a new tool to be added using the DWARFLinker library.
>
> Some more general thoughts:
> 1)
2020 Sep 01
2
[Proposal][Debuginfo] dsymutil-like tool for ELF.
On 01.09.2020 06:27, David Blaikie wrote:
> A quick note: The feature as currently proposed sounds like it's an
> exact match for 'dwz'? Is there any benefit to this over the existing
> dwz project? Is it different in some ways I'm not aware of? (I haven't
> actually used dwz, so I might have some mistaken ideas about how it
> should work)
>
> If
2020 Sep 02
2
[Proposal][Debuginfo] dsymutil-like tool for ELF.
On 01.09.2020 20:07, David Blaikie wrote:
> Fair enough - thanks for clarifying the differences! (I'd still lean a
> bit towards this being dwz-esque, as you say "an extension of classic dwz"
I doubt a little about "llvm-dwz" since it might confuse people who
would expect exactly the same behavior.
But if we think of it as "an extension of classic dwz" and
2020 Sep 02
2
[Proposal][Debuginfo] dsymutil-like tool for ELF.
On 02.09.2020 21:44, David Blaikie wrote:
>
>
> On Wed, Sep 2, 2020 at 9:56 AM Alexey <avl.lapshin at gmail.com
> <mailto:avl.lapshin at gmail.com>> wrote:
>
>
> On 01.09.2020 20:07, David Blaikie wrote:
>> Fair enough - thanks for clarifying the differences! (I'd still
>> lean a bit towards this being dwz-esque, as you say "an
2019 Mar 19
2
AArch64 tests failing
I'm seeing a bunch of failures on AArch64 after updating this morning.
These are NOT failing on x86-64. These all seem to be caused by
segfaults (example backtrace below). Is anyone else seeing this?
-David
LLVM :: DebugInfo/symbolize-no-debug-str.test
LLVM :: tools/gold/X86/comdat.ll
LLVM :: tools/gold/X86/visibility.ll
LLVM ::
2020 Sep 03
2
[Proposal][Debuginfo] dsymutil-like tool for ELF.
On 03.09.2020 01:36, David Blaikie wrote:
>
>
> On Wed, Sep 2, 2020 at 3:26 PM Alexey <avl.lapshin at gmail.com
> <mailto:avl.lapshin at gmail.com>> wrote:
>
>
> On 02.09.2020 21:44, David Blaikie wrote:
>>
>>
>> On Wed, Sep 2, 2020 at 9:56 AM Alexey <avl.lapshin at gmail.com
>> <mailto:avl.lapshin at gmail.com>>
2020 Aug 31
6
[Proposal][Debuginfo] dsymutil-like tool for ELF.
Hi James,
Thank you for the comments.
>I think we're not terribly far from that ideal, now, for ELF. Maybe
only these three things need to be done? --
> 1. Teach lld how to emit a separated debuginfo output file directly,
without requiring an objcopy step.
> 2. Integrate DWARFLinker into lld.
> 3. Create a new tool which takes the separated debuginfo and DWO/DWP
files