From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Subject: Re: completion on brace + 4 characters doesn't work
Date: Wed, 4 May 2011 11:33:17 +0200 [thread overview]
Message-ID: <20110504093317.GI5625@prunille.vinc17.org> (raw)
In-Reply-To: <20110429111557.GF5625@prunille.vinc17.org>
On 2011-04-29 13:15:58 +0200, Vincent Lefevre wrote:
> In fact, the behavior comes from glibc on x86_64. It can be
> reproduced with:
>
> #include <stdio.h>
> #include <string.h>
>
> int main (void)
> {
> static char s[] = "{abcd";
> volatile int len = 1;
>
> printf ("s = %s\n", s);
> strcpy (s, s + len);
> printf ("s = %s\n", s);
> return 0;
> }
>
> and gcc -fno-builtin (the strcpy builtin was not used anyway).
>
> According to gdb, the source in eglibc-2.11.2 is
> sysdeps/x86_64/multiarch/strcpy.S (strcpy with SSSE3). It can load
> 16 bytes at a time, and it uses special code on these 16 bytes (I'm
> not sure, but it seems to have code for each length).
FYI, this new strcpy code breaks many applications:
http://sourceware.org/bugzilla/show_bug.cgi?id=12518
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2011-05-04 9:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 11:11 Vincent Lefevre
2011-04-28 15:12 ` Bart Schaefer
2011-04-28 22:27 ` Vincent Lefevre
2011-04-29 0:31 ` Vincent Lefevre
2011-04-29 0:59 ` Vincent Lefevre
2011-04-29 1:34 ` Vincent Lefevre
2011-04-29 3:56 ` Bart Schaefer
2011-04-29 8:44 ` Vincent Lefevre
2011-04-29 11:15 ` Vincent Lefevre
2011-05-04 9:33 ` Vincent Lefevre [this message]
2011-04-29 14:20 ` Bart Schaefer
2011-05-02 8:08 ` Vincent Lefevre
2011-05-02 8:34 ` Vincent Lefevre
2011-05-02 11:54 ` Peter Stephenson
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=20110504093317.GI5625@prunille.vinc17.org \
--to=vincent@vinc17.net \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).