[PATCH V4] gprofng: a new GNU profiler

[Jose E. Marchesi]

>> Hi Vladimir,
>>
>>> I created 4 patches to integrate gprofng into binutils-gdb.
>>> % ls -al 000*
>>> -rw-rw-r-- 1 vmezents wheel 5901152 Jan 11 12:39 0001-gprofng-add-the-gprofng-tool.patch
>>> -rw-rw-r-- 1 vmezents wheel  224725 Jan 11 12:39 0002-gprofng-add-testsuite-for-gprofng.patch
>>> -rw-rw-r-- 1 vmezents wheel  179400 Jan 11 12:39
>>> 0003-gprofng-add-the-gprofng-documentation.patch
>>> -rw-rw-r-- 1 vmezents wheel   26170 Jan 11 12:39 0004-gprofng-add-the-gprofng-build.patch
>>> The first 3 pathes add or change sources only in
>>> binutils-gdb.git/gprofng directory.
>>> 0004-gprofng-add-the-gprofng-build.patch has fixes in Makefile.def
>>> and configure.ac to configure the gprofng build.
>>> 0001-gprofng-add-the-gprofng-tool.patch is probably so big to send
>>> to binutils@sourceware.org.
>>> I have no permissions to apply pathes.
>>> What should I do to pushmy fixes for gprofng in binutils-gdb.git ?
>>
>> Send them to me (or point me at them - they are probably in the email archive somewhere
>> but I am a little bit swamped at the moment, so anything that you can do to make my life
>> simpler is a benefit).  I strongly suggest that you compress the 0001 patch first though :-)
>> xz is your friend.  Or lzip.  Or well pretty much any compression tool...
>
> I can do the push on Vlad's behalf.  Much easier.

Hm, now that I think about it... this is a new subsystem being added
here.  We can expect issues that need to be resolved fast.  Vladimir
can't rely on third persons to do that.

Nick, OK for me sponsoring Vlad for an account in sourceware and write
access to binutils-gdb.git?