From owner-freebsd-ppc@FreeBSD.ORG  Thu Aug  3 18:23:32 2006
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
X-Original-To: freebsd-ppc@FreeBSD.org
Delivered-To: freebsd-ppc@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 83EF816A4DA
	for <freebsd-ppc@FreeBSD.org>; Thu,  3 Aug 2006 18:23:32 +0000 (UTC)
	(envelope-from sobomax@FreeBSD.org)
Received: from sippysoft.com (gk.360sip.com [72.236.70.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 16B0D43D55
	for <freebsd-ppc@FreeBSD.org>; Thu,  3 Aug 2006 18:23:30 +0000 (GMT)
	(envelope-from sobomax@FreeBSD.org)
Received: from [192.168.1.56] ([204.244.149.125]) (authenticated bits=0)
	by sippysoft.com (8.13.6/8.13.6) with ESMTP id k73INRnq045962
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <freebsd-ppc@freebsd.org>; Thu, 3 Aug 2006 11:23:29 -0700 (PDT)
	(envelope-from sobomax@FreeBSD.org)
Message-ID: <44D23F02.9020709@FreeBSD.org>
Date: Thu, 03 Aug 2006 11:22:58 -0700
From: Maxim Sobolev <sobomax@FreeBSD.org>
Organization: Sippy Software, Inc.
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: freebsd-ppc@FreeBSD.org
Content-Type: text/plain; charset=KOI8-U; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Unaligned 64-bits access on FreeBSD/powerpc
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2006 18:23:32 -0000

Hi,

I came over a problem that unaligned 64-bits access to a memory (via 
uint8_t or long long pointer) causes SIGBUS. Is it expected behavior or not?

-Maxim