linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: removing bcopy... because it's half broken
Date: Sun, 9 Jan 2005 15:38:52 -0800	[thread overview]
Message-ID: <20050109233852.GA23256@twiddle.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501091213000.2339@ppc970.osdl.org>

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~

  parent reply	other threads:[~2005-01-09 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 19:23 removing bcopy... because it's half broken Arjan van de Ven
2005-01-09 19:39 ` Ralf Baechle
2005-01-09 20:03 ` Russell King
2005-01-09 20:19 ` Linus Torvalds
2005-01-09 20:33   ` Arjan van de Ven
2005-01-09 20:34   ` Christoph Hellwig
2005-01-09 20:42     ` Linus Torvalds
2005-01-11 10:10       ` Bastian Blank
2005-01-11 10:32         ` Arjan van de Ven
2005-01-11 16:10         ` Linus Torvalds
2005-01-09 23:38   ` Richard Henderson [this message]
2005-01-10  0:43   ` Adrian Bunk
2005-01-10 16:55     ` Matthias-Christian Ott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050109233852.GA23256@twiddle.net \
    --to=rth@twiddle.net \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).