From: Cyrill G. <gor...@gm...> - 2014-05-09 16:32:29
|
On Fri, May 09, 2014 at 09:27:59AM -0700, H. Peter Anvin wrote: > On 05/09/2014 09:20 AM, Cyrill Gorcunov wrote: > >> > >> We kind of have the same problem with NASM as with Linux... the only way > >> to really find out what is being used is to break it...! > > > > Well, we can try it then -- drop rdoff by _one_ commit, and if people > > start complaing about it, we simply revert the commit. > > > > At the moment I walking throught the sources looking for parts of code > > which can be ripped off. One of them -- custom malloc/free tracker. > > There are a bunch to memory trackers (valgrind and such) so I think > > we don't need our trivial one. > > I'm wondering how much problem it causes, though. Doing some web > searches seems to imply there are some scattered users out there. We > haven't spent a lot of time working on it for a very long time, so it > doesn't seem to be causing problems, as far as I can tell. You're talking about rdoff or mem-tracker? ;) |