public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alain.filbois at laposte dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17074] New memset for x86 SSE & x86-64 Date: Fri, 11 Jul 2014 08:34:00 -0000 [thread overview] Message-ID: <bug-17074-131-HYINCIOhTG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17074-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17074 --- Comment #1 from alain.filbois <alain.filbois at laposte dot net> --- Created attachment 7694 --> https://sourceware.org/bugzilla/attachment.cgi?id=7694&action=edit Fast x86 & x64 memsets code. Hi, Version 1.1 of the memsets: all 64 bits memsets are now Position Independant Code and are OK on OpenBSD for example. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-11 8:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-19 17:30 [Bug libc/17074] New: " alain.filbois at laposte dot net 2014-06-20 11:14 ` [Bug libc/17074] " fweimer at redhat dot com 2014-06-25 15:01 ` zimmerma+gcc at loria dot fr 2014-07-11 8:34 ` alain.filbois at laposte dot net [this message] 2015-08-27 22:22 ` [Bug string/17074] " jsm28 at gcc dot gnu.org
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=bug-17074-131-HYINCIOhTG@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).