This is the mail archive of the gcc@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: [boehms-gc] Performance results

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: "Laurynas Biveinis" <laurynas dot biveinis at gmail dot com>
Cc: "Daniel Berlin" <dberlin at dberlin dot org>, gcc at gcc dot gnu dot org
Date: Mon, 24 Jul 2006 06:29:10 -0700
Subject: Re: [boehms-gc] Performance results
References: <d1e3ff2b0607240145h1558bc59h61a6250150b14fd7@mail.gmail.com> <584134AA-6026-42E2-B2E3-4777425675DF@physics.uc.edu> <d1e3ff2b0607240422n704d5358g3c6d7b7225041e33@mail.gmail.com>

On Jul 24, 2006, at 4:22 AM, Laurynas Biveinis wrote:


So does that mean that there is no way to get GGC debug output with
--disable-checking? Is there any very cheap --enable-checking option
that would be give that or am I better off to hack GCC to do it with
--disable-checking?


No, GC is just not running as you have too much memory to cause it to
run with --disable-checking :).

-- Pinski

Follow-Ups:
- Re: [boehms-gc] Performance results
  - From: Laurynas Biveinis

References:
- [boehms-gc] Performance results
  - From: Laurynas Biveinis
- Re: [boehms-gc] Performance results
  - From: Andrew Pinski
- Re: [boehms-gc] Performance results
  - From: Laurynas Biveinis

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