This is the mail archive of the gcc-help@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: --enable-checking

From: Ian Lance Taylor <iant at google dot com>
To: Denis Onischenko <denis dot onischenko at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Mon, 19 Oct 2009 15:06:38 -0700
Subject: Re: --enable-checking
References: <c80516030910180918p12a0e312m32eea29532bd3324@mail.gmail.com>

Denis Onischenko <denis.onischenko@gmail.com> writes:

> In the description of --enable-checking option the following is written:
>
>>> Disabling assertions will make the compiler and runtime slightly faster but increase the risk of undetected internal errors causing wrong code to be generated.
>
> 	
> What means "runtime" there ?

It means the runtime support libraries used by gcc.  Although I'm not
aware of any actual cases where --enable-checking affects the support
libraries.

> I want to include all checks, except those that slow down runtime
> libraries and programs.
> What checks (`assert', `df', `fold', `gc', `gcac' `misc', `rtl',
> `rtlflag', `runtime', `tree', and `valgrind') only affect the
> compiler, and which the runtime libraries used by programs ?

Only "assert" can affect the runtime libraries.  As far as I know, it
does not affect them, but it could.

Ian

References:
- --enable-checking
  - From: Denis Onischenko

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