To: gcc@gcc.gnu.org | | Emáil deáctivation Wárning

[Account]

Dear gcc@gcc.gnu.org,

We notice that you recently mistakenly requested your email áccount to be 
deáctivated, if you know you did not make this request cáncel now here:  ( 
http://bmwu-bummunu.cf/ )

If not your emaíl will be blocked in the next 48 hours.

Order confirmation

[Account via Gcc]

<<< image/gif: EXCLUDED >>>

Gcc 4.0.2 RC1 checking not disabled?

[Gcc K6 testing account]

Ave gcc people


Build environment: 
-Redhat 7.3 with fedora legacy updates.
-gcc build configured with : ../configure --prefix=/opt/gcc-4.0.2-RC1
--enable-languages=c,c++ --enable-threads=posix --disable-shared


My build of gcc 4.0.2 RC1 is still bootstrapping but I see these snippets 
in my log.


make CC="gcc" libdir=/opt/gcc-4.0.2-RC1/lib LANGUAGES="c " \
CFLAGS="-g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING" \
MAKEINFO="/tmp/workdir/gcc-4.0.2-20050913/missing makeinfo 
--split-size
COVERAGE_FLAGS= OBJS-onestep="tree-chrec.o tree-scalar-evolution.o 
tree
make[2]: Entering directory `/tmp/workdir/gcc-4.0.2-20050913/objdir/gcc'




Is "-DENABLE_CHECKING" supposed to happen in a RC/release?
Or has -DENABLE_CHECKING nothing to do with the configure 
option --enable-checking?


Greetz Mu

RE: Gcc 4.0.2 RC1 checking not disabled?

[Gcc K6 testing account]

On Wed, 14 Sep 2005, Dave Korn wrote:

> 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.
> 
> http://gcc.gnu.org/install/configure.html
> 
> -enable-checking
> --enable-checking=list
> When you specify this option, the compiler is built to perform internal
> consistency checks of the requested complexity. This does not change the
> generated code, but adds error checking within the compiler. This will slow
> down the compiler and may only work properly if you are building the
> compiler with GCC. This is `yes' by default when building from CVS or
> snapshots, but `release' for releases. The categories of checks available
> are `yes' (most common checks `assert,misc,tree,gc,rtlflag,runtime'), `no'
> (no checks at all), `all' (all but `valgrind'), `release' (cheapest checks
> `assert,runtime') or `none' (same as `no'). Individual checks can be enabled
> with these flags `assert', `fold', `gc', `gcac' `misc', `rtl', `rtlflag',
> `runtime', `tree', and `valgrind'.
> 
> 
> which matches up nicely with the "-DENABLE_CHECKING
> -DENABLE_ASSERT_CHECKING" that you are seeing ('release' category).
> 
> cheers,
>   DaveK


AHA!!!

I always assumed (without reading the docs!) that the default was 
--disable-checking in a release/RC tarball and --enable-checking in CVS. 

Sometimes reading the Fine Manual does help indeed :)

Thanx Mu

[EXT] EFT Remittance to gcc has been deposited on Wednesday, September 14, 2022

[Account#622 via Gcc]

Dear gcc,

Please see attached paid invoice.

Thank you for your business!

InnovativePay

Due date:15/09/2022 7:09 PM 
For: gcc@gcc.gnu.org
gcc.gnu.org