public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14602] strstr broken on older i686 targets
Date: Sun, 23 Sep 2012 18:58:00 -0000 [thread overview]
Message-ID: <bug-14602-131-9afsa2hIyu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14602-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14602
--- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-09-23 18:57:49 UTC ---
On Sat, 22 Sep 2012, hjl.tools at gmail dot com wrote:
> There was a strong disagreement on IFUNC selector. I don't want
> to make any changes to IFUNC selector while Roland wants otherwise.
> I don't see how we can break the impasse here.
Start by not assuming that either your views or those of other
participants are fated to remain unchanged from those in the previous
discussion. Try to understand the arguments for both points of view and
explain them both fairly when posting your new self-contained analysis of
the issue. Maybe start the analysis with the requirements (ability to
test all the IFUNC versions of functions, easily) and high-level features
that are desirable if not absolutely required (being able to test them
without needing a special build of glibc to do so, not making it
excessively complicated to add new IFUNC versions of functions, not
affecting the efficiency of those versions) before discussing how the
possible approaches match up to those requirements and features.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-23 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 20:54 [Bug libc/14602] New: " law at redhat dot com
2012-09-21 14:03 ` [Bug libc/14602] " eblake at redhat dot com
2012-09-21 22:25 ` hjl.tools at gmail dot com
2012-09-21 22:42 ` joseph at codesourcery dot com
2012-09-21 23:37 ` hjl.tools at gmail dot com
2012-09-21 23:48 ` joseph at codesourcery dot com
2012-09-22 0:09 ` hjl.tools at gmail dot com
2012-09-22 3:56 ` ppluzhnikov at google dot com
2012-09-23 18:58 ` joseph at codesourcery dot com [this message]
2012-09-23 19:10 ` hjl.tools at gmail dot com
2012-10-05 19:21 ` [Bug libc/14602] strstr broken hjl.tools at gmail dot com
2012-10-05 22:36 ` [Bug libc/14602] string/strstr.c is broken hjl.tools at gmail dot com
2012-10-06 5:31 ` maxim.kuvyrkov at gmail dot com
2012-10-06 5:32 ` maxim.kuvyrkov at gmail dot com
2012-10-08 0:08 ` allan at archlinux dot org
2012-10-10 0:11 ` maxim.kuvyrkov at gmail dot com
2012-10-13 18:47 ` jan.kratochvil at redhat dot com
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-14602-131-9afsa2hIyu@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.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 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).