Date: Mon, 11 Dec 2006 19:41:02 -0800 (PST)
Message-Id: <20061211.194102.74749040.davem@davemloft.net>
To: matthltc@us.ibm.com
Cc: zaitcev@redhat.com, erikj@sgi.com, guillaume.thouvenin@bull.net,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] connector: Some fixes for ia64 unaligned access errors
From: David Miller <davem@davemloft.net>
In-Reply-To: <1165892956.24721.129.camel@localhost.localdomain>
References: <20061211172907.305473cf.zaitcev@redhat.com>
	<20061211.175050.55478586.davem@davemloft.net>
	<1165892956.24721.129.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 641
Lines: 16

From: Matt Helsley <matthltc@us.ibm.com>
Date: Mon, 11 Dec 2006 19:09:16 -0800

> Hmm, that GCC assumption conflicts with the prototypes of memcpy() I've
> seen.

When GCC expands __builtin_memcpy() internally it looks at the types
of the arguments, and what it knows about their guarenteed alignment.

memcpy()'s declaration of the first argument as "void *" has
zero influence upon any of this.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/