From: "Djordje Todorovic" <Djordje.Todorovic@rt-rk.com>
To: "Mark Wielaard" <mark@klomp.org>
Cc: "Ananthakrishna Sowda (asowda)" <asowda@cisco.com>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Latest version of dwarflint?
Date: Fri, 22 Sep 2017 13:37:00 -0000 [thread overview]
Message-ID: <815-59c51200-3-121bf9c0@123096269> (raw)
In-Reply-To: <1506020453.16945.67.camel@klomp.org>
Hi Mark,
Thank you for your comments!
>Could you take a look at the CONTRIBUTING file?
Sure.
How should I send this patches? Should I wait for you to make a new "dwarflint" branch which follows master branch or?
Thanks,
Djordje
-------- Original Message --------
Subject: Re: Latest version of dwarflint?
Date: Thursday, September 21, 2017 21:00 CEST
From: Mark Wielaard <mark@klomp.org>
To: Djordje Todorovic <djordje.todorovic@rt-rk.com>, "Ananthakrishna Sowda (asowda)" <asowda@cisco.com>
CC: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
References: <81113170-F590-4C51-BEA0-C8EF3A4422DA@contoso.com> <1501751620.3741.132.camel@klomp.org> <624331B2-472C-44AD-9034-05AD3CBBAE8A@cisco.com> <cc97238e-81a3-683b-a2ea-1e4d82382f40@rt-rk.com>
> Hi Djordje,
>
> On Thu, 2017-09-21 at 18:07 +0200, Djordje Todorovic wrote:
> > I have managed to integrate dwarflint on the top of elfutils-0.170
> > release, so dwarflint and locstats can use all conveniences and
> > improvements of the newest libdw library (such as
> > handling ops like DW_OP_GNU_entry_value).
>
> Very nice.
>
> > It is used internally by our compiler team. I have also managed to
> > add some new enhancements for locstats, such as reporting summary
> > either for formal parameter or local variable,
> > reporting some kind of verbose info about particular variable or
> > formal parameter of particular function.
> > But, beside these enhancements that were interested for our compiler
> > team, dwarflint and locstats have a lot of good utilities that can be
> > really useful to compiler developers. For
> > example, dwarflint tool can detect mistakes in debug sections such as
> > debug info, debug line etc., and help compiler developers to get rid
> > of those mistakes. Locstats can
> > apparently report useful summary and show progress of making better
> > coverage for local variables or formal parameter in debug sections,
> > so it can save a lot of time to compiler
> > developers.
>
> Yes, I know some compiler hackers have found it useful. And I was a
> little sad nobody had time to keep dwarflint up to date. It is really
> great to hear you have.
>
> > At least, maybe considering a making new branch called „dwarflint“ on
> > elfuitls git repository, which follows the newest source code, would
> > be good for the beginning, the same as it
> > was on elfutils-0.152? Because, getting more feedback from users,
> > these tools would be better and more useful, so it can be, one day,
> > merged on to master branch.
> >
> > If you are interested, I can share my patches.
>
> Yes please do share. I cannot promise to have a lot of time reviewing
> the code. But I am certainly interested. Creating a public "dwarflint"
> branch sounds like a good idea.
>
> Could you take a look at the CONTRIBUTING file? We don't have to be
> very formal for code not directly going onto master. But having at
> least a Signed-off-by line on the patches makes sure we can eventually
> integrate them officially.
>
> Thanks,
>
> Mark
next prev parent reply other threads:[~2017-09-22 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 19:47 Ananthakrishna Sowda (asowda)
2017-08-03 9:13 ` Mark Wielaard
2017-09-21 15:59 ` Ananthakrishna Sowda (asowda)
2017-09-21 16:07 ` Djordje Todorovic
2017-09-21 19:00 ` Mark Wielaard
2017-09-22 13:37 ` Djordje Todorovic [this message]
2017-09-25 16:18 ` Mark Wielaard
2017-09-26 11:39 ` Djordje Todorovic
[not found] ` <c2b5f92f-0798-1e43-2095-b282bd5d7879@rt-rk.com>
2017-09-29 12:08 ` Mark Wielaard
2017-09-29 12:26 ` Mark Wielaard
2017-09-29 12:44 ` Djordje Todorovic
2017-09-29 13:07 ` Mark Wielaard
2017-10-06 19:53 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=815-59c51200-3-121bf9c0@123096269 \
--to=djordje.todorovic@rt-rk.com \
--cc=asowda@cisco.com \
--cc=elfutils-devel@sourceware.org \
--cc=mark@klomp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).