archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Arjan van de Ven <>
Cc: Kernel Mailing List <>,
	Andrew Morton <>,
	Richard Henderson <>
Subject: Re: removing bcopy... because it's half broken
Date: Sun, 9 Jan 2005 12:19:09 -0800 (PST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, 9 Jan 2005, Arjan van de Ven wrote:
> Instead of fixing this inconsistency, I decided to remove it entirely,
> explicit memcpy() and memmove() are prefered anyway (welcome to the 1990's)
> and nothing in the kernel is using these functions, so this saves code size
> as well for everyone.

The problem is that at least some gcc versions would historically generate
calls to "bcopy" on alpha for structure assignments. Maybe it doesn't any
more, and no such old gcc versions exist any more, but who knows?

That's also why "bcopy" just acts like a memcpy() in many cases: it's 
simply not worth it to do the complex case, because the only valid use was 
a compiler that would never validly do overlapping ranges anyway.

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. I also don't know if it
affected any other platforms than alpha (I would assume that it matched
"target has BSD heritage", and that would likely mean HP-UX too)

Richard? You know both gcc and alpha, what's the word?


  parent reply	other threads:[~2005-01-09 20:19 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 [this message]
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
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:

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

  git send-email \ \ \ \ \ \ \

* 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).