This is the mail archive of the gcc@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: Error reporting functions

From: Ian Lance Taylor <iant at google dot com>
To: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Thu, 4 Oct 2012 20:51:20 -0700
Subject: Re: Error reporting functions
References: <BF230D13CA30DD48930C31D40993300016C844DA@FMSMSX102.amr.corp.intel.com>

On Thu, Oct 4, 2012 at 5:21 PM, Iyer, Balaji V <balaji.v.iyer@intel.com> wrote:

>         This question is mainly for some future submission. Am I allowed to use "fatal_error (..)"? Mainly, I want to use it in cases where I want to say "if this error has occurred, I see no reason to go forward with compilation."

You are allowed to use it in exceptional circumstances.  Not normally
"I see no reason to go forward" but "I can not go forward because some
critical operation has failed."  There is also internal_error for,
well, internal errors; use that for data corruption.  And gcc_assert
and gcc_unreachable for things that can not happen.

Ian

References:
- Error reporting functions
  - From: Iyer, Balaji V

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