From: Andrew Haley <aph@redhat.com>
To: Vijay Kamath <vijay.kamath@wipro.com>
Cc: gcc@gcc.gnu.org
Subject: Query
Date: Thu, 24 Apr 2003 12:25:00 -0000 [thread overview]
Message-ID: <16039.49830.90675.755117@cuddles.redhat.com> (raw)
In-Reply-To: <3EA7BD19.7060700@wipro.com>
Vijay Kamath writes:
> Forgive me, if this is not the right address for this question, atleast
> direct me to the right place.
> I'm having gcc version 3.2 release 7 that comes with Redhat 8.0 . I find
> that the option -fcheck-memory-usage is missing. I couldn't find
> information about this anywhere on the net. Could you please tell me
> what happened to this option?
Quoth Oliva: "Basically, it just didn't work any more, and it was
decided to take it out to not create false expectations. If anyone
feels like resurrecting this feature, the patch that took the feature
out can always be used as a starting point"
http://gcc.gnu.org/ml/gcc/2002-02/msg00666.html
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg00587.html
Andrew.
next prev parent reply other threads:[~2003-04-24 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 11:48 Query Vijay Kamath
2003-04-24 12:25 ` Andrew Haley [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-01 21:14 query sunil suhas petwe
2002-03-10 4:44 ` query Andrea 'Fyre Wyzard' Bocci
2001-12-06 1:37 Query Bansal, Shashank
2001-12-06 1:45 ` Query Bansal, Shashank
2001-12-06 5:19 ` Query Jack Lloyd
2001-12-06 7:44 ` Query Tim Prince
2001-04-19 3:29 Query MNShukla
2001-04-19 5:51 ` Query Nick Clifton
2001-04-19 21:54 ` Query MNShukla
2001-04-20 3:29 ` Query Philip Blundell
2001-04-19 9:47 ` Query Toshi Morita
2001-01-22 6:20 Query MNShukla
2001-01-22 6:27 ` Query Richard Earnshaw
2001-01-22 12:28 ` Query Philip Blundell
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=16039.49830.90675.755117@cuddles.redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=vijay.kamath@wipro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).