Removing leftover traces of mmalloc?

Removing leftover traces of mmalloc?

[Nathanael Nerode]

With the removal of mmalloc support from gdb, nothing in src or gcc is
actually using mmalloc.  Furthermore, support appears to have been removed
prior to the branching of GDB 6.1.

Would it be appropriate to delete the mmalloc directory and all the trailing
references thereto?  If not, would it at any rate be appropriate to stop
shipping it with GDB and delete the various trailing references?

Reply to list please.  :-)

-- 
There are none so blind as those who will not see.

Re: Removing leftover traces of mmalloc?

[Andrew Cagney]

> With the removal of mmalloc support from gdb, nothing in src or gcc is
> actually using mmalloc.  Furthermore, support appears to have been removed
> prior to the branching of GDB 6.1.
> 
> Would it be appropriate to delete the mmalloc directory and all the trailing
> references thereto?  If not, would it at any rate be appropriate to stop
> shipping it with GDB and delete the various trailing references?

I think it is fine to break the the GDB <-> mmalloc connection (by 
zapping it from config et.al.).

As for removing it (cvs rm -f), perhaphs we can avoid it (although I 
don't care).

GDB has a growing list of top-level src directories that it doesn't need 
to be included in a distro (src/mmalloc/ is one).  I think its time to 
prune the `gdb' module (which, I know, is not a very backward compatible 
thing to do).

Andrew

PS: But `what-if' GDB needs to replace obstacks with something more like 
mmalloc (ah, the irony)? We can then revive it - here we need to deal 
with `what-is' :-)

Re: Removing leftover traces of mmalloc?

[Andrew Cagney]

>> With the removal of mmalloc support from gdb, nothing in src or gcc is
>> actually using mmalloc.  Furthermore, support appears to have been removed
>> prior to the branching of GDB 6.1.
>>
>> Would it be appropriate to delete the mmalloc directory and all the trailing
>> references thereto?  If not, would it at any rate be appropriate to stop
>> shipping it with GDB and delete the various trailing references?
> 
> 
> I think it is fine to break the the GDB <-> mmalloc connection (by zapping it from config et.al.).

Hmm, I just noted some lingering calls to [x]mmalloc in the objfile 
reader.  I'll replace them (their reason for being there is gone).

Since GDB works around the lack of mmalloc this wouldn't have been noticed.

Andrew

> As for removing it (cvs rm -f), perhaphs we can avoid it (although I don't care).
> 
> GDB has a growing list of top-level src directories that it doesn't need to be included in a distro (src/mmalloc/ is one).  I think its time to prune the `gdb' module (which, I know, is not a very backward compatible thing to do).
> 
> Andrew
> 
> PS: But `what-if' GDB needs to replace obstacks with something more like mmalloc (ah, the irony)? We can then revive it - here we need to deal with `what-is' :-)