This is the mail archive of the gcc-patches@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: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats

From: Diego Novillo <dnovillo at google dot com>
To: "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>
Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Thu, 3 Jul 2008 20:05:02 -0400
Subject: Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
References: <b798aad50807030856l10b18949n8ec9eaa02629f24b@mail.gmail.com> <Pine.GSO.4.58.0807031858540.18846@caipclassic.rutgers.edu> <b798aad50807031647g37121026l33039e3ede599496@mail.gmail.com> <Pine.GSO.4.58.0807031950460.18970@caipclassic.rutgers.edu>

On Thu, Jul 3, 2008 at 19:57, Kaveh R. GHAZI <ghazi@caip.rutgers.edu> wrote:

> Based on history there's a good chance they'll each have a few minor nits.

Yeah.

> Can you suggest a few things to try?  E.g. I did --with-gc=zone and a
> couple of errors cropped up.  If there are other configurations that come
> to mind, let me know.

I had these in mind:

--disable-checking
--enable-checking=all,valgrind  (you got time to go on holiday with this one)
--enable-coverage


Diego.

Follow-Ups:
- Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
  - From: Kaveh R. GHAZI

References:
- Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
  - From: Kaveh R. GHAZI
- Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
  - From: Diego Novillo
- Re: Bootstrap failures due to C++ warnings with --enable-gather-detailed-memory-stats
  - From: Kaveh R. GHAZI

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