From owner-freebsd-current@FreeBSD.ORG Sat Jun 16 22:01:50 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C74516A46B for ; Sat, 16 Jun 2007 22:01:50 +0000 (UTC) (envelope-from casper@web.am) Received: from mx1.web.am (mx1.web.am [217.113.0.68]) by mx1.freebsd.org (Postfix) with ESMTP id F31C813C469 for ; Sat, 16 Jun 2007 22:01:49 +0000 (UTC) (envelope-from casper@web.am) Received: from antispam (localhost.web.am [127.0.0.1]) by localhost (Postfix) with ESMTP id A58A861C5F for ; Sun, 17 Jun 2007 02:28:38 +0500 (AMST) Received: from localhost (localhost.web.am [127.0.0.1]) by localhost (Postfix) with SMTP id 092C261C5C for ; Sun, 17 Jun 2007 02:28:38 +0500 (AMST) Received: from aldan.web.am (unknown [217.113.1.123]) by mx1.web.am (Postfix) with ESMTP id C272F61C29 for ; Sun, 17 Jun 2007 02:28:37 +0500 (AMST) Message-ID: <46745631.7000708@web.am> Date: Sun, 17 Jun 2007 02:29:21 +0500 From: Gaspar Chilingarov User-Agent: Thunderbird 2.0.0.0 (X11/20070613) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mx1.web.am X-Spam-Status: No, hits=0.0 required=7.5 tests=none autolearn=no version=2.60 X-Spam-Level: Subject: [AMD64] X.org build eats all the memory when compiled with GCC 4.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jun 2007 22:01:50 -0000 Hello! I recompiled X.org yesterday and hit the following problem (1 week old -current, yesterdays packages, AMD64) -- when compiling files in /usr/ports/x11-servers/xorg-server/work/xorg-server-1.2.0/hw/xfree86/scanpci directory, there are huge .h files - about 4mb. when compiler uses -O2 or -O option it eats all available memory and then gets killed by the system. Without -O/O2 option compile works just as expected. Now -- should I file a PR or it's known bug? /Gaspar -- Gaspar Chilingarov System Administrator, Network security consulting t +37493 419763 (mob) i 63174784 e nm@web.am w http://zanazan.am/