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: [PATCH] add gcc_assert

From: Jonathan Lennox <lennox at cs dot columbia dot edu>
To: Nathan Sidwell <nathan at codesourcery dot com>
Cc: Mark Mitchell <mark at codesourcery dot com>, "Joseph S. Myers" <jsm at polyomino dot org dot uk>, GCC Patches <gcc-patches at gcc dot gnu dot org>, Giovanni Bajo <rasky at develer dot com>
Date: Fri, 27 Aug 2004 14:04:21 -0400
Subject: Re: [PATCH] add gcc_assert
References: <412F1701.7050805@codesourcery.com> <Pine.LNX.4.61.0408271229300.28828@digraph.polyomino.org.uk> <412F2B3D.1050804@codesourcery.com> <412F5887.4030309@codesourcery.com> <412F5FD6.7070909@codesourcery.com>

Nathan Sidwell wrote:
> I fixed it this way, by introducing an is_release variable.  Thus removing
> two error-prone steps with one simple step.

Is it possible to make the configure --help output vary depending on the
is_release setting?  (Presumably is_release would need to be an m4 variable
rather than a shell variable, but that may not be a bad thing.)

-- 
Jonathan Lennox
lennox@cs.columbia.edu

References:
- [PATCH] add gcc_assert
  - From: Nathan Sidwell
- Re: [PATCH] add gcc_assert
  - From: Joseph S. Myers
- Re: [PATCH] add gcc_assert
  - From: Nathan Sidwell
- Re: [PATCH] add gcc_assert
  - From: Mark Mitchell
- Re: [PATCH] add gcc_assert
  - From: Nathan Sidwell

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