Author: Diego Novillo Date: To: Kaveh R. GHAZI CC: gcc, gcc-patches Subject: Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
On Thu, Jul 3, 2008 at 19:02, Kaveh R. GHAZI <ghazi@???> wrote:
> Actually it's --enable-gather-detailed-mem-stats ("mem" not "memory"),
> this threw me for a while as I was unable to reproduce any failures until
> I figured that out. :-)
Oops, sorry! I composed the message in a hurry and didn't actually
cut-n-paste the flag name.
>
> * alloc-pool.c (hash_descriptor, eq_descriptor,
> alloc_pool_descriptor): Fix -Wc++-compat warnings.
> * bitmap.c (hash_descriptor, eq_descriptor, bitmap_descriptor):
> Likewise.
> * ggc-common.c (hash_descriptor, eq_descriptor, hash_ptr, eq_ptr,
> loc_descriptor, ggc_prune_ptr, ggc_free_overhead,
> final_cmp_statistic, cmp_statistic, dump_ggc_loc_statistics):
> Likewise.
> * varray.c (hash_descriptor, eq_descriptor, varray_descriptor):
> Likewise.
OK, thanks.
I wonder if other major configuration modes may also trigger
warnings (e.g., --disable-checking). I tried
--enable-checking=release and that works fine.
