From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-72480-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9154 invoked by alias); 24 Apr 2003 10:56:14 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 9146 invoked from network); 24 Apr 2003 10:56:12 -0000
Received: from unknown (HELO mx1.redhat.com) (66.187.233.31)
  by sources.redhat.com with SMTP; 24 Apr 2003 10:56:12 -0000
Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254])
	by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h3OAu3D17954;
	Thu, 24 Apr 2003 06:56:03 -0400
Received: from redhat.com (IDENT:vM6rdydjZAkbHtZpFIH1gf6uFXH2QMwP@vpn50-15.rdu.redhat.com [172.16.50.15])
	by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h3OAu3q13543;
	Thu, 24 Apr 2003 06:56:03 -0400
Received: (from aph@localhost)
	by redhat.com (8.11.6/8.11.0) id h3OAtYq14150;
	Thu, 24 Apr 2003 11:55:34 +0100
From: Andrew Haley <aph@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16039.49830.90675.755117@cuddles.redhat.com>
Date: Thu, 24 Apr 2003 12:25:00 -0000
To: Vijay Kamath <vijay.kamath@wipro.com>
Cc: gcc@gcc.gnu.org
Subject: Query
In-Reply-To: <3EA7BD19.7060700@wipro.com>
References: <3EA7BD19.7060700@wipro.com>
X-SW-Source: 2003-04/txt/msg01223.txt.bz2

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.