From: Michael Brunnbauer <brunni@netestate.de>
To: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Cc: cottrell@wfu.edu, libc-help <libc-help@sourceware.org>
Subject: Re: my strstr is broken
Date: Tue, 11 Sep 2018 14:41:00 -0000 [thread overview]
Message-ID: <20180911144138.GA2030@netestate.de> (raw)
In-Reply-To: <CAAHN_R3e0rEgUK5vyKb55QEKmO6+mFVwUQ11w3Ujn97cnmMwkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
Hello Siddhesh,
On Tue, Sep 11, 2018 at 07:51:02PM +0530, Siddhesh Poyarekar wrote:
> Is this a non-x86 architecture?
No it's i686-pc-linux-gnu (output from gcc -dumpmachine).
arch reports x86_64 because the kernel is 64 bit but everything else is 32 bit.
> I can reproduce this on the glibc
> 2.28 tag when I hack the ifunc resolver to ignore
> __strstr_sse2_unaligned and always use the stock __strstr.
So the stock __strstr has a bug?
A 32 bit glibc would not use __strstr_sse2_unaligned, right?
cu,
brunni
--
++ Michael Brunnbauer
++ netEstate GmbH
++ Geisenhausener Straße 11a
++ 81379 München
++ Tel +49 89 32 19 77 80
++ Fax +49 89 32 19 77 89
++ E-Mail brunni@netestate.de
++ https://www.netestate.de/
++
++ Sitz: München, HRB Nr.142452 (Handelsregister B München)
++ USt-IdNr. DE221033342
++ Geschäftsführer: Michael Brunnbauer, Franz Brunnbauer
++ Prokurist: Dipl. Kfm. (Univ.) Markus Hendel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2018-09-11 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:47 Michael Brunnbauer
2018-09-11 10:27 ` Michael Brunnbauer
2018-09-11 12:58 ` Allin Cottrell
2018-09-11 13:54 ` Michael Brunnbauer
2018-09-11 14:21 ` Siddhesh Poyarekar
2018-09-11 14:41 ` Michael Brunnbauer [this message]
2018-09-11 14:51 ` Siddhesh Poyarekar
2018-09-11 15:21 ` Paul Pluzhnikov via libc-help
2018-09-11 15:38 ` Siddhesh Poyarekar
2018-09-11 18:46 Wilco Dijkstra
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=20180911144138.GA2030@netestate.de \
--to=brunni@netestate.de \
--cc=cottrell@wfu.edu \
--cc=libc-help@sourceware.org \
--cc=siddhesh.poyarekar@gmail.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 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).