From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-118008-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25252 invoked by alias); 2 Aug 2005 21:11:20 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 25233 invoked by uid 22791); 2 Aug 2005 21:11:16 -0000
Received: from us01smtp1.synopsys.com (HELO boden.synopsys.com) (198.182.44.79)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 02 Aug 2005 21:11:16 +0000
Received: from maiden.synopsys.com (maiden.synopsys.com [146.225.100.170])
	by boden.synopsys.com (Postfix) with ESMTP
	id 9FE9FDA75; Tue,  2 Aug 2005 14:10:11 -0700 (PDT)
Received: from piper.synopsys.com (localhost [127.0.0.1])
	by maiden.synopsys.com (8.9.1/8.9.1) with ESMTP id OAA21886;
	Tue, 2 Aug 2005 14:11:13 -0700 (PDT)
Received: from piper.synopsys.com (localhost [127.0.0.1])
	by piper.synopsys.com (8.12.10/8.12.3) with ESMTP id j72LBCOe000559;
	Tue, 2 Aug 2005 14:11:12 -0700
Received: (from jbuck@localhost)
	by piper.synopsys.com (8.12.10/8.12.10/Submit) id j72LBCPl000557;
	Tue, 2 Aug 2005 14:11:12 -0700
Date: Tue, 02 Aug 2005 21:11:00 -0000
From: Joe Buck <Joe.Buck@synopsys.COM>
To: Mike Stump <mrs@apple.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>,
	Dave Korn <dave.korn@artimi.com>,
	Paul Koning <pkoning@equallogic.com>, gcc@sources.redhat.com,
	Shaun Jackman <sjackman@gmail.com>
Subject: Re: memcpy to an unaligned address
Message-ID: <20050802211112.GB30893@synopsys.com>
References: <200508022037.j72Kbr4T012558@earth.phy.uc.edu> <33EADFBB-0C16-4FD9-BC0D-E681C0A61C46@apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <33EADFBB-0C16-4FD9-BC0D-E681C0A61C46@apple.com>
User-Agent: Mutt/1.4.1i
X-SW-Source: 2005-08/txt/msg00089.txt.bz2

On Tue, Aug 02, 2005 at 02:04:16PM -0700, Mike Stump wrote:
> Shaun, want to do up an entry in the manual describing this?  We have  
> known about this for years and years, but, we don't do a good job  
> communicating it to users.  Essentially, & doesn't work as one would  
> expect on unaligned data, as it produces a pointer to an aligned  
> object instead of a pointer to unaligned object.

I suppose we could make & on an unaligned project return a void*.  That
isn't really right, but it would at least prevent the cases that we know
don't work from compiling.