This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [c++ patch] avoid inlining twice

From: Mark Mitchell <mark at codesourcery dot com>
To: Jan Hubicka <hubicka at ucw dot cz>
Cc: Gabriel Dos Reis <gdr at integrable-solutions dot net>, Jan Hubicka <jh at suse dot cz>, gcc-patches at gcc dot gnu dot org
Date: Thu, 05 Feb 2004 10:13:46 -0800
Subject: Re: [c++ patch] avoid inlining twice
Organization: CodeSourcery, LLC
References: <20040205122954.GN21096@kam.mff.cuni.cz> <m3smhp7el9.fsf@uniton.integrable-solutions.net> <20040205172253.GA7319@atrey.karlin.mff.cuni.cz>

Jan Hubicka wrote:

Jan Hubicka <jh@suse.cz> writes:
| 	* tree.h (optimize_function): Kill prototype.
| 	* optimize.c (dump_function, optimize_function, dump_finction): Kill.
| 	* semantics.c (expand_body): Kill.
Is "kill" the right word for "remove" in the ChangeLog?


Not sure, I just feel better when I am killing old code rather than
removing it.  I can use remove if it sounds better.

"Remove" is definitely better.

--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

References:
- [c++ patch] avoid inlining twice
  - From: Jan Hubicka
- Re: [c++ patch] avoid inlining twice
  - From: Gabriel Dos Reis
- Re: [c++ patch] avoid inlining twice
  - From: Jan Hubicka

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]