This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PING][PATCH]Improving mklog [was: Re: RFC Asan instrumentation control]

From: Tatiana Udalova <t dot udalova at samsung dot com>
To: jakub at redhat dot com, dnovillo at google dot com
Cc: gcc-patches at gcc dot gnu dot org, 'Slava Garbuzov' <v dot garbuzov at samsung dot com>, y dot gribov at samsung dot com
Date: Thu, 16 Jan 2014 12:59:12 +0400
Subject: [PING][PATCH]Improving mklog [was: Re: RFC Asan instrumentation control]
Authentication-results: sourceware.org; auth=none

Ping!

Thank you,
Tatiana Udalova


----------

Hello,

I have reproduced the problem with mklog mentioned by Jakub:

> In my experience mklog is pretty much useless, e.g. if you add a new 
> function, it will list the previous function as being modified rather 
> than the new one, etc.

My focus was on functions from headers of diff-log chunks.

I hacked a simple addition to mklog which skips unchanged functions in
diff-log while adding function names to the final ChangeLog.

New mklog results were verified by testsuite which compares reference
ChangeLogs of patches from gcc trunk with logs generated by mklog.

Patched mklog considerably reduced the number of unchanged functions in
ChangeLog.

Is it OK for trunk?

Thank you,
Tatiana Udalova

Attachment: mklog_patch.diff
Description: Binary data

Follow-Ups:
- Re: [PING][PATCH]Improving mklog [was: Re: RFC Asan instrumentation control]
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]