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

[Yury Gribov]

> 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.

In my experience it prints both the old and the new one. If that's a 
problem we could probably fix it (I mean I can volunteer).

Here's a draft patch for mklog which splits generated ChangeLog entry 
into several parts (so no more spurious gcc/ or gcc/testsuite/). I can 
continue working on this if people find it useful.

-Y
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mklog_patch.diff
Type: text/x-patch
Size: 2635 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20131219/7eb0f1d5/attachment.bin>