public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/12092] strstr broken for some inputs on pre-SSE4 machines Date: Mon, 30 Jun 2014 07:54:00 -0000 [thread overview] Message-ID: <bug-12092-131-1Ac9UqT4r4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12092-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=12092 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-06-30 7:54 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-05 5:56 [Bug libc/12092] New: " ppluzhnikov at google dot com 2010-10-05 5:58 ` [Bug libc/12092] " ppluzhnikov at google dot com 2010-10-05 17:08 ` ppluzhnikov at google dot com 2010-10-05 17:36 ` ppluzhnikov at google dot com 2010-10-05 18:17 ` ian at airs dot com 2010-10-05 18:18 ` ian at airs dot com 2010-10-05 18:31 ` eblake at redhat dot com 2010-10-05 22:10 ` eblake at redhat dot com 2010-10-05 22:24 ` eblake at redhat dot com 2010-10-05 22:29 ` jakub at redhat dot com 2010-10-06 15:44 ` eblake at redhat dot com 2010-10-06 15:54 ` [Bug libc/12092] memmem broken on some inputs on all machines; strstr and strcasestr likewise broken " eblake at redhat dot com 2010-10-06 17:50 ` [Bug libc/12092] strstr broken for some inputs " drepper.fsp at gmail dot com 2010-10-06 17:59 ` eblake at redhat dot com 2010-10-11 20:07 ` pasky at suse dot cz 2010-11-01 21:36 ` pasky at suse dot cz 2014-06-30 7:54 ` fweimer at redhat dot com [this message]
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-12092-131-1Ac9UqT4r4@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).