All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zack@codesourcery.com>
To: Richard Henderson <rth@redhat.com>
Cc: Andreas Jaeger <aj@suse.de>,
	libc-alpha@sources.redhat.com, linux-gcc@vger.kernel.org,
	gcc@gcc.gnu.org
Subject: Re: i386 inline-asm string functions - some questions
Date: Sun, 28 Dec 2003 18:22:08 -0800	[thread overview]
Message-ID: <871xqol5wv.fsf@codesourcery.com> (raw)
In-Reply-To: <20031229015820.C6728@zzz.ward.six> (Denis Zaitsev's message of "Mon, 29 Dec 2003 01:58:20 +0500")

Denis Zaitsev <zzz@anda.ru> writes:

> On Sat, Dec 27, 2003 at 10:38:49AM -0800, Zack Weinberg wrote:
>> Denis Zaitsev <zzz@anda.ru> writes:
>> 
>> >> so, first off, I don't think this kind of optimization is libc's
>> >> business; we have the tools to do a better job over here in the
>> >> compiler.
>> >
>> > Should the compiler implement all the string functions?
>> 
>> That is the trend.  The compiler can make a better decision about
>> whether memcpy (for example) should be inlined at all, if it knows
>> the properties.
>
> Yes, but even if it can, it is rather a kinda political question -
> should it do so, or this must be defined by the programmer.  I
> personally like the latter approach, but who knows...

Meh.  I personally am convinced that the compiler can do a *much*
better job, and that trying to improve bits/string.h and
bits/string2.h is a waste of time; in fact, I've felt that they have
*always* caused the generated code to get worse, from the day they
were introduced.  I once tried to get Uli to take them out again, with
hard numbers to back me up, but he ignored me.

So I have very little interest in pursuing any of your suggestions.
If you want to keep at them, though, and come up with patches, feel
free.

zw

  reply	other threads:[~2003-12-29  2:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-25  0:20 i386 inline-asm string functions - some questions Denis Zaitsev
2003-12-25  0:38 ` Richard Henderson
2003-12-25  1:15   ` Denis Zaitsev
2003-12-25  1:21     ` Zack Weinberg
2003-12-25  1:45       ` Denis Zaitsev
2003-12-26  3:40         ` Zack Weinberg
2003-12-27  4:58           ` Richard Henderson
2003-12-27 10:24             ` Zack Weinberg
2003-12-27 11:35               ` Denis Zaitsev
2003-12-27 18:38                 ` Zack Weinberg
2003-12-28 20:58                   ` Denis Zaitsev
2003-12-29  2:22                     ` Zack Weinberg [this message]
2003-12-29  2:44                       ` Denis Zaitsev
2003-12-29  2:46                         ` Zack Weinberg
2003-12-29  2:53                           ` Denis Zaitsev
2003-12-29  3:35                       ` Ulrich Drepper
2003-12-29  3:54                         ` Andrew Pinski
2003-12-29  6:57                           ` Jakub Jelinek
2003-12-29  3:56                         ` Zack Weinberg
2003-12-29  5:31                           ` Daniel Jacobowitz
2003-12-29  5:55                             ` Zack Weinberg
2003-12-29 18:37                             ` Denis Zaitsev
2003-12-29 19:09                               ` Zack Weinberg
2003-12-29 19:31                                 ` Denis Zaitsev
2003-12-29 19:37                                   ` Denis Zaitsev
2003-12-29 18:51                           ` Denis Zaitsev
2003-12-29 19:15                             ` Zack Weinberg
2003-12-27 10:52           ` Denis Zaitsev
     [not found]   ` <20031225060850.C7419@zzz.ward.six>
     [not found]     ` <20031225012711.GD13447@redhat.com>
2003-12-25  1:38       ` Denis Zaitsev
2003-12-25  1:53         ` Richard Henderson
2003-12-25  2:08           ` Denis Zaitsev
2003-12-25  0:39 ` Roland McGrath
2003-12-25  1:13   ` Denis Zaitsev

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=871xqol5wv.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-gcc@vger.kernel.org \
    --cc=rth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.