From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.54)
id 1FaNqm-0006mw-QZ
for garchives@archives.gentoo.org; Mon, 01 May 2006 02:09:25 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k4128Ado009089;
Mon, 1 May 2006 02:08:10 GMT
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.228])
by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k411xloH025762
for <gentoo-user@lists.gentoo.org>; Mon, 1 May 2006 01:59:48 GMT
Received: by wproxy.gmail.com with SMTP id 58so483393wri
for <gentoo-user@lists.gentoo.org>; Sun, 30 Apr 2006 18:59:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
b=Gy8xuzMYpN+e7eUj7oeldYYiGIfacaJ5S6nQXYBn8L3YG2igMLcbCj5PAUSXp6llNx8WEGDttUJ73jeyI2+mRkXGhgsDd8NZl4TY94RDtrppYH1iOUJCMRYWQHB87XARtqtP6Zh1aOWRsOYuajfBZtx2M2g2fwdt1h7LshbuDno=
Received: by 10.54.70.16 with SMTP id s16mr7677168wra;
Sun, 30 Apr 2006 18:59:47 -0700 (PDT)
Received: by 10.54.69.1 with HTTP; Sun, 30 Apr 2006 18:59:47 -0700 (PDT)
Message-ID: <7573e9640604301859g30747e83se7cfc2207b2b47a0@mail.gmail.com>
Date: Sun, 30 Apr 2006 18:59:47 -0700
From: "Richard Fish" <bigfish@asmallpond.org>
Sender: richard.j.fish@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why firefox is so slow?
In-Reply-To: <20060430203436.GD6770@mainframe>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <7797aa370604300524i6b8616ebr947b762fec45f92a@mail.gmail.com>
<200604301910.21639.me+gentoo-user@modelnine.org>
<ce429d600604301052k4cf94a74hef9a9641700b29b4@mail.gmail.com>
<44550041.1080307@mid.email-server.info>
<20060430194935.GC6770@mainframe>
<8a0028260604301311w31d1a4dfw62c37897d88ed21f@mail.gmail.com>
<20060430203436.GD6770@mainframe>
X-Google-Sender-Auth: cffccc09257a89d8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k411xloH025762
X-Archives-Salt: 7c32ef53-2ec6-4b35-aa21-47cd7a2fa285
X-Archives-Hash: 7436cc90e4163f5c0561b909b28f50eb
On 4/30/06, Farhan Ahmed <farhanahmed06@gmail.com> wrote:
> Jeff Rollin wrote:
> > I didn't say DG_DISABLE_DEBUG was a USE flag, I said it was a CFLAG. And it
> > improves the speed of KDE applications too
>
> Read your earlier post.. Anyway where is this CFLAGS 'DG_DISABLE_DEBUG'
> documented? I cant find any reference to it in man gcc. No usable
> results came up when i googled it..
I did some more digging on this. Actually it looks like
-DG_DISABLE_DEBUG won't have any effect on glib/gtk/gnome
applications. There is no such thing in /usr/include, or in the
current sources for glib or gtk.
There *is* G_ENABLE_DEBUG, which is only turned on if you merge glib
or gtk with USE=debug, which configures glib/gtk with "./configure ...
--enable-debug=yes ...". The default glib/gtk debug configuration is
minimum.
Glibc and gtk also support configuring with --enable-debug=no, which
adds -DG_DISABLE_ASSERT, -DG_DISABLE_CHECKS, and/or
-DG_DISABLE_CAST_CHECKS to CFLAGS when they are built. However, there
is no USE flag currently available to set --enable-debug=no. (If you
desire this, file a bug report on bugzilla for the feature
enhancement).
It is possible you could get the effect of --enable-debug=no by adding
-UG_DISABLE_ASSERT, -UG_DISABLE_CHECKS, and -UG_DISABLE_CAST to
CFLAGS, but it depends upon whether the package build takes
user-defined CFLAGS into account before or after ./configure defined
flags. If ./configure is added after the user flags, they will have
no effect. I have not investigated this at all...
Jeff, whoever told you that -DG_DISABLE_DEBUG did something was lying.
Current gtk and glibc sources know nothing about this flag.
-Richard
--
gentoo-user@gentoo.org mailing list