From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 6 19:43:58 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 8ADAD1065677 for ; Tue, 6 Mar 2012 19:43:58 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-hackers@FreeBSD.org Date: Tue, 6 Mar 2012 14:43:48 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201203061443.50562.jkim@FreeBSD.org> Cc: Subject: AMD confirms a CPU bug X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 19:43:58 -0000 [Moving the thread from amd64@ to hackers@] http://leaf.dragonflybsd.org/mailarchive/kernel/2012-03/msg00000.html This bug actually delayed DragonFly 3.0 release. FYI, here is Matt's detailed explanation and the hack to work around the issue for GCC 4.4: http://gitweb.dragonflybsd.org/dragonfly.git/commit/8e32ecc0a77082f1e232a3e6d12e2f163f9667a4 Jung-uk Kim