From owner-freebsd-sparc64@FreeBSD.ORG Sat Mar 20 20:50:06 2010 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81B18106566C for ; Sat, 20 Mar 2010 20:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 70D1B8FC16 for ; Sat, 20 Mar 2010 20:50:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o2KKo6GE062434 for ; Sat, 20 Mar 2010 20:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o2KKo66K062433; Sat, 20 Mar 2010 20:50:06 GMT (envelope-from gnats) Date: Sat, 20 Mar 2010 20:50:06 GMT Message-Id: <201003202050.o2KKo66K062433@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/144900: [patch] SPARC64 Floating point fixes X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Mar 2010 20:50:06 -0000 The following reply was made to PR sparc64/144900; it has been noted by GNATS. From: Marius Strobl To: Peter Jeremy Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: sparc64/144900: [patch] SPARC64 Floating point fixes Date: Sat, 20 Mar 2010 21:49:41 +0100 On Sat, Mar 20, 2010 at 08:11:20PM +1100, Peter Jeremy wrote: > - Parts of the emulator code must be compiled with no-strict-aliasing > specified to function correctly. CFLAGS is updated to include the > relevant gcc option. (This will add -fno-strict-aliasing to all of > libc - which is excessive but I don't believe it's possible to compile > only part of libc that way). Could you please elaborate on what exactly breaks when compiling with strict aliasing rules? I think there actually is a way to limit -no-strict-aliasing to the emulator part but I'd like to understand what's going on and make sure there's no way it can be solved by the code affected before turning it on. Marius