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] PR c++/PR48035

From: Mike Stump <mikestump at comcast dot net>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Dodji Seketeli <dseketel at redhat dot com>, Jason Merrill <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Thu, 10 Mar 2011 12:31:57 -0800
Subject: Re: [PATCH] PR c++/PR48035
References: <m3r5afuf57.fsf@redhat.com> <20110310182257.GW30899@tyan-ft48-01.lab.bos.redhat.com>

On Mar 10, 2011, at 10:22 AM, Jakub Jelinek wrote:
> The standard way of signalizing a test failure is calling abort (),
> not returning 1, see http://gcc.gnu.org/codingconventions.html

Actually, returning 0 or 1 is a perfectly fine way to signal pass/fail in the testsuites, as it exit.

Follow-Ups:
- Re: [PATCH] PR c++/PR48035
  - From: Jakub Jelinek

References:
- [PATCH] PR c++/PR48035
  - From: Dodji Seketeli
- Re: [PATCH] PR c++/PR48035
  - From: Jakub Jelinek

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