Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261976AbVAIXjG (ORCPT ); Sun, 9 Jan 2005 18:39:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261979AbVAIXjG (ORCPT ); Sun, 9 Jan 2005 18:39:06 -0500 Received: from are.twiddle.net ([64.81.246.98]:28800 "EHLO are.twiddle.net") by vger.kernel.org with ESMTP id S261976AbVAIXjD (ORCPT ); Sun, 9 Jan 2005 18:39:03 -0500 Date: Sun, 9 Jan 2005 15:38:52 -0800 From: Richard Henderson To: Linus Torvalds Cc: Arjan van de Ven , Kernel Mailing List , Andrew Morton Subject: Re: removing bcopy... because it's half broken Message-ID: <20050109233852.GA23256@twiddle.net> Mail-Followup-To: Linus Torvalds , Arjan van de Ven , Kernel Mailing List , Andrew Morton References: <20050109192305.GA7476@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 971 Lines: 24 On Sun, Jan 09, 2005 at 12:19:09PM -0800, Linus Torvalds wrote: > Gcc _used_ to have a target-specific "do I use bcopy or memcpy" setting, > and I just don't know if that is still true. Yes, TARGET_MEM_FUNCTIONS. It's never not set for Linux targets. Or for OSF/1 for that matter... Indeed, it would take me some time to figure out which targets it's *not* set for. (Yet another thing that ought to get cleaned up -- either invert the default value or simply require the target to either provide the libc entry point or add a version to libgcc.) I'm not sure how far back you'd have to go to find an Alpha compiler that needs this. Prolly back to at least gcc 2.6, but I don't have sources that old handy to check. r~ - 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/