From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: removing bcopy... because it's half broken
Date: Sun, 09 Jan 2005 21:33:19 +0100 [thread overview]
Message-ID: <1105302799.4173.58.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0501091213000.2339@ppc970.osdl.org>
On Sun, 2005-01-09 at 12:19 -0800, Linus Torvalds wrote:
>
> 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.
>
> 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)
actually I think that is called -ffreestanding, and
ChangeSet 1.2088, 2005/01/04 21:29:33-08:00, bunk@stusta.de
added that to the compiler flags in your tree ....
next prev parent reply other threads:[~2005-01-09 20:33 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 [this message]
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:
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=1105302799.4173.58.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--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).