From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, mec.gnu@mindspring.com
Cc: cagney@redhat.com, eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa] delete more mmalloc remnants
Date: Mon, 19 Jan 2004 22:53:00 -0000 [thread overview]
Message-ID: <20040119225306.3EEA84B359@berman.michael-chastain.com> (raw)
> I agree with anything user visible being removed. For the remaining
> internal stuff perhaphs hold off a little.
Ummm, could you say which of these files/symbols it's okay to
delete now:
* MAINTAINERS: Delete mmalloc.
* Makefile.in: Delete MMALLOC, MMALLOC_CFLAGS, -lmmalloc, mmalloc_h.
* NEWS: Mention removal of --with-malloc.
* acconfig.h: Delete USE_MMALLOC, MMCHECK_FORCE.
* config.in: Regenerate.
* configure: Regenerate.
* configure.in: Delete MMALLOC_CFLAGS, MMALLOC, --with-mmalloc, USE_MMALLOC, MMCHECK_FORCE.
* gdbinit.in: Remove mmalloc.
* utils.c: Delete USE_MMALLOC, NO_MMCHECK, MMCHECK_FORCE, malloc_botch.
* config/alpha/alpha-linux.mh: Delete MMALLOC, MMALLOC_CFLAGS.
* config/i386/go32.mh: Likewise.
* config/i386/interix.mh: Likewise.
* config/powerpc/xm-linux.h: Delete MMAP_BASE_ADDRESS, MMAP_INCREMENT.
I'll be happy to make a revised patch with just the stuff that
it's okay to delete.
Michael C
next reply other threads:[~2004-01-19 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 22:53 Michael Elizabeth Chastain [this message]
2004-01-19 23:12 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 9:41 Michael Elizabeth Chastain
2004-01-19 22:26 Michael Elizabeth Chastain
2004-01-19 22:45 ` Andrew Cagney
2004-01-20 6:09 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040119225306.3EEA84B359@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=cagney@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox