From: Matthias-Christian Ott <email@example.com>
To: Adrian Bunk <firstname.lastname@example.org>
Cc: Linus Torvalds <email@example.com>,
Arjan van de Ven <firstname.lastname@example.org>,
Kernel Mailing List <email@example.com>,
Andrew Morton <firstname.lastname@example.org>,
Richard Henderson <email@example.com>
Subject: Re: removing bcopy... because it's half broken
Date: Mon, 10 Jan 2005 17:55:52 +0100 [thread overview]
Message-ID: <41E2B398.firstname.lastname@example.org> (raw)
Adrian Bunk wrote:
>On Sun, Jan 09, 2005 at 12:19:09PM -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.
>>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?
> * GCC of any recent vintage doesn't do stupid things with bcopy.
> * EGCS 1.1 knows all about expanding memcpy inline, others don't.
> * Similarly for a memset with data = 0.
>And Arjan's patch is pretty low-risk:
>If it breaks on any architecture with any supported compiler (>= 2.95),
>it will break at compile time and there will pretty fast be reports of
>this breakage in which case it would be easy to revert his patch.
Jep and most people are using a newer gcc and newer glibc. Linux has to
stay up2date, so I think it's the best choise to create a modern and
clean (without broken functions) OS.
prev parent reply other threads:[~2005-01-10 16:59 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
2005-01-10 0:43 ` Adrian Bunk
2005-01-10 16:55 ` Matthias-Christian Ott [this message]
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).