From owner-freebsd-current@FreeBSD.ORG  Mon May 24 15:27:28 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4333916A4CE; Mon, 24 May 2004 15:27:28 -0700 (PDT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 116B243D1F; Mon, 24 May 2004 15:27:28 -0700 (PDT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 16CA8148BB; Mon, 24 May 2004 17:27:00 -0500 (CDT)
Date: Mon, 24 May 2004 17:27:00 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: "P.D. Seniura" <pdseniura@techie.com>
In-Reply-To: <20040524203547.939D379004A@ws1-14.us4.outblaze.com>
Message-ID: <Pine.LNX.4.44.0405241724110.2276-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 25 May 2004 05:10:47 -0700
cc: freebsd-current@freebsd.org
cc: freebsd-ports@FreeBSD.org
cc: Alex Dupre <ale@FreeBSD.org>
Subject: Re: lang/ezm3 "runtime error: Segmentation violation..."
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 May 2004 22:27:28 -0000

> Do we blame the code or the compiler?

One of the things I just added to the PR Submission Guidelines is
to explain what AFAICT is the current practice within FreeBSD with
respect to anything other than -O: be prepared to send patches.
Apparently few developers have sufficient time/understanding/interest.
Executive summary: there's just not enough manpower.

Again, AFAICT.

mcl