From: Andreas Schwab <schwab@linux-m68k.org>
To: "Carlos Martín Nieto" <cmn@elego.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] valgrind: ignore SSE-based strlen invalid reads
Date: Wed, 16 Mar 2011 23:43:07 +0100 [thread overview]
Message-ID: <m2ei66ofes.fsf@igel.home> (raw)
In-Reply-To: <1300273819.7214.12.camel@bee.lab.cmartin.tk> ("Carlos Martín Nieto"'s message of "Wed, 16 Mar 2011 12:10:14 +0100")
Carlos Martín Nieto <cmn@elego.de> writes:
> Looking at that header, strlen is one of the few functions not being
> replaced by its __builtin version, and I only see __builtin_strlen in
> the C++ patches. I'll rephrase to something like "Some versions of
> strlen use SSE which then get inlined" to avoid blaming anyone in
> particular, though thinking about it, it does seem logical that it's
> GCC's builtin strlen.
All processor optimized versions of strlen in glibc are out-of-line, so
any use of SSE can only come from __builtin_strlen.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2011-03-16 22:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 9:31 [PATCH] valgrind: ignore SSE-based strlen invalid reads Carlos Martín Nieto
2011-03-16 9:56 ` Jonathan Nieder
2011-03-16 10:41 ` Carlos Martín Nieto
2011-03-16 10:47 ` Carlos Martín Nieto
2011-03-16 10:52 ` Jonathan Nieder
2011-03-16 11:10 ` Carlos Martín Nieto
2011-03-16 11:25 ` Jonathan Nieder
2011-03-16 11:46 ` Carlos Martín Nieto
2011-03-16 20:18 ` Junio C Hamano
2011-03-16 20:44 ` Carlos Martín Nieto
2011-03-16 22:43 ` Andreas Schwab [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=m2ei66ofes.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@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 NNTP newsgroup(s).