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: Mark Mitchell <mark at codesourcery dot com>
To: Nathan Sidwell <nathan at codesourcery dot com>
Cc: "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 09:25:17 -0700
Subject: Re: [PATCH] add gcc_assert
Organization: CodeSourcery, LLC
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:

Mark Mitchell wrote:

Also, is there a way to make that sentence a little more explicit about what exactly should be done? Perhaps an example of what the release-branch code should look like would help.
I fixed it this way, by introducing an is_release variable.  Thus removing
two error-prone steps with one simple step.

Yay.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

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]