From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17447 invoked by alias); 30 Jun 2005 18:25:21 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 17387 invoked by uid 22791); 30 Jun 2005 18:25:15 -0000 Received: from adsl-110-19.38-151.net24.it (HELO develer.com) (151.38.19.110) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Thu, 30 Jun 2005 18:25:15 +0000 Received: (qmail 10297 invoked from network); 30 Jun 2005 18:25:11 -0000 Received: from mimas.trilan (HELO MIMAS) (10.3.3.191) by trinity.trilan with SMTP; 30 Jun 2005 18:25:11 -0000 Received: from 127.0.0.1 (AVG SMTP 7.0.323 [267.8.7]); Thu, 30 Jun 2005 20:25:07 +0200 Message-ID: <068401c57da1$0b0e9980$bf03030a@trilan> From: "Giovanni Bajo" To: "Joe Buck" Cc: "Bernd Schmidt" , References: <71AD0926-2DA8-4B55-828F-38A85155CC86@apple.com> <27918F7A-CBBC-4657-AB29-3242BE6DF53D@apple.com> <200506301855.19658.stevenb@suse.de> <1120153723.4621.224.camel@localhost.localdomain> <42C435FE.7040707@t-online.de> <20050630181857.GA9625@synopsys.com> Subject: Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86 Date: Thu, 30 Jun 2005 18:25:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg01319.txt.bz2 Joe Buck wrote: >>> I'd tend to agree. I'd rather see the option go away than linger on >>> if the option is no longer useful. >> >> I wouldn't mind that, but I'd also like to point out that there are >> Makefiles out there which hard-code things like -fforce-mem. Do we want >> to keep the option as a stub to avoid breaking them? > > It could produce a "deprecated" or "obsolete" warning for 4.1, and then be > removed for 4.2. Personally, I don't see a point. -fforce-mem is just an optimization option which does not affect the semantic of the program in any way. If we remove it, people would need to just drop it from their Makefiles. There is no source code adjustment required (which would justify the deprecation cycle). Or convert it to a noop as Bernd suggested. -- Giovanni Bajo