From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27283 invoked by alias); 2 Aug 2003 17:17:05 -0000 Mailing-List: contact guile-gtk-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: guile-gtk-owner@sources.redhat.com Received: (qmail 27274 invoked from network); 2 Aug 2003 17:17:05 -0000 Received: from unknown (HELO octopussy.utanet.at) (213.90.36.45) by sources.redhat.com with SMTP; 2 Aug 2003 17:17:05 -0000 Received: from paris.utanet.at ([213.90.36.7]) by octopussy.utanet.at with esmtp (Exim 4.12) id 19j008-00084L-00 for guile-gtk@sources.redhat.com; Sat, 02 Aug 2003 19:17:04 +0200 Received: from dsl-159-4.utaonline.at ([62.218.159.4] helo=rotty-ipv4.yi.org) by paris.utanet.at with esmtp (Exim 4.12) id 19j008-0001zh-00 for guile-gtk@sources.redhat.com; Sat, 02 Aug 2003 19:17:04 +0200 Received: from alice.rhinosaur.lan ([192.168.1.3] ident=mail) by rotty-ipv4.yi.org with esmtp (Exim 3.36 #1 (Debian)) id 19j00a-0001m6-00 for ; Sat, 02 Aug 2003 19:17:32 +0200 Received: from andy by alice.rhinosaur.lan with local (Exim 4.20) id 19j00a-0003U3-KM for guile-gtk@sources.redhat.com; Sat, 02 Aug 2003 19:17:32 +0200 To: guile-gtk@sources.redhat.com Subject: Compiling guile-gobject experiences From: Andreas Rottmann Date: Sat, 02 Aug 2003 17:17:00 -0000 Message-ID: <87ptjornbn.fsf@alice.rotty.yi.org> User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q3/txt/msg00016.txt.bz2 Hi! I've just tried a rebuild of a new guile-gobject CVS checkout. The build takes extremly long (I've cancelled it, after my machine started heavy trashing). The problem is the generated guile-gnome-gw-gtk.c, which has 154075 lines (:-O). My machine is not really that low-end: AMD Athlon 900Mhz, 384MB RAM, over 1G Swap. I used gcc 3.3.1 20030728 (Debian prerelease), default optimization settings (-O2). After over 10 minutes of running, needing over 100MB of RAM, consuming 100% CPU, gcc got even more greedy and memory usage got up to ~825MB, which caused my machine to trash, of course, and CPU consumption fell to near zero. In short, the solution would be to break the big C file into several junks, or reduce the size of the autogenerated code (if that's feasible at all). For comparison, I had a look at the python GTK wrappers, and their gtk.c file only (;-)) has 37060 lines, which is less than 25%... Regards, Andy -- Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 It's GNU/Linux dammit!