This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Gcc 4.0.2 RC1 checking not disabled?
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'Andrew Pinski'" <pinskia at physics dot uc dot edu>
- Cc: "'Gcc K6 testing account'" <caligula at sarijopen dot student dot utwente dot nl>,<gcc at gcc dot gnu dot org>
- Date: Wed, 14 Sep 2005 20:16:55 +0100
- Subject: RE: Gcc 4.0.2 RC1 checking not disabled?
----Original Message----
>From: Andrew Pinski
>Sent: 14 September 2005 19:56
>> ----Original Message----
>>> From: Gcc K6 testing account
>>> Sent: 14 September 2005 19:43
>>
>>> Ave gcc people
>>
>> !Hola!
>>
>>> Is "-DENABLE_CHECKING" supposed to happen in a RC/release?
>>> Or has -DENABLE_CHECKING nothing to do with the configure
>>> option --enable-checking?
>>
>> --enable-checking defaults to on these days, and has done for some
>> time. It doesn't enable _all_ the checking options by default, just some
>> of the most useful ones.
>
> Actually that is not true. It defaults to --enable-checking=release for
> release branches with building with normal checking on stage1.
I think this may just be a subtlety of wording; I don't mean the same by
>> --enable-checking defaults to on these days
as I would by saying
>> --enable-checking defaults to "on" these days
In the first form, I'm just saying that it is enabled in any way at all;
in the second form, I'm specifying the actual value of the parameter.
cheers,
DaveK
--
Can't think of a witty .sigline today....