From owner-freebsd-bugs@FreeBSD.ORG  Tue May 20 13:35:17 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 72D7237B401; Tue, 20 May 2003 13:35:17 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1FD4D43F75; Tue, 20 May 2003 13:35:17 -0700 (PDT)
	(envelope-from gerald@FreeBSD.org)
Received: from freefall.freebsd.org (gerald@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4KKZHUp012731;
	Tue, 20 May 2003 13:35:17 -0700 (PDT)
	(envelope-from gerald@freefall.freebsd.org)
Received: (from gerald@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4KKZGDL012727;
	Tue, 20 May 2003 13:35:16 -0700 (PDT)
Date: Tue, 20 May 2003 13:35:16 -0700 (PDT)
From: Gerald Pfeifer <gerald@FreeBSD.org>
Message-Id: <200305202035.h4KKZGDL012727@freefall.freebsd.org>
To: daveturgeon@catholic.org, gerald@FreeBSD.org,
	freebsd-bugs@FreeBSD.org, gerald@FreeBSD.org
Subject: Re: i386/50760: GCC Internal Compiler Error building
	mail/cyrus-imapd
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 May 2003 20:35:17 -0000

Synopsis: GCC Internal Compiler Error building mail/cyrus-imapd

State-Changed-From-To: open->feedback
State-Changed-By: gerald
State-Changed-When: Tue May 20 13:30:57 PDT 2003
State-Changed-Why: 
It seems that this is indeed not a FreeBSD-specific problem, and that also
from the GCC-side there is little chance for a change.  32MB really is quite
little memory these days, and AFAIK FreeBSD 5 now requires a 486 or higher.

Can you reproduce the problem on a machine with more memory? And can you
reproduce it using the lang/gcc32 or lang/gcc33 ports?

(If GCC doesn't provide a proper error message, that certainly is a bug, but
you didn't provide the actual error.)


Responsible-Changed-From-To: freebsd-bugs->gerald
Responsible-Changed-By: gerald
Responsible-Changed-When: Tue May 20 13:30:57 PDT 2003
Responsible-Changed-Why: 
It seems that this is indeed not a FreeBSD-specific problem, and that also
from the GCC-side there is little chance for a change.  32MB really is quite
little memory these days, and AFAIK FreeBSD 5 now requires a 486 or higher.

Can you reproduce the problem on a machine with more memory? And can you
reproduce it using the lang/gcc32 or lang/gcc33 ports?

(If GCC doesn't provide a proper error message, that certainly is a bug, but
you didn't provide the actual error.)

http://www.freebsd.org/cgi/query-pr.cgi?pr=50760