This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: Add 32bit SSE2 strlen

From: Ulrich Drepper <drepper at redhat dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: GNU C Library <libc-alpha at sourceware dot org>
Date: Tue, 04 Aug 2009 17:17:45 -0700
Subject: Re: PATCH: Add 32bit SSE2 strlen
References: <20090804204810.GA5273@lucon.org> <4A78C501.7000801@redhat.com> <6dc9ffc80908041708g11f9dbc1mce40c2d163d552bd@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

H.J. Lu wrote:
> I don't want to totally disable SSE2 on Atom. So I added slow_vector.

But why?  This isn't used elsewhere?  Disabling SSE2 has not negative
effects so far.  And nothing but the string functions uses the flags.

> I can limit it to 32bit and leave 64bit alone.

At th very least.  But I see no reason so far to introduce it at all.
If the Atoms suck so badly at SSE then disable it for good.

- --
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkp4z6kACgkQ2ijCOnn/RHS/3ACgvev0DOXfCTr0XjHGyndeQPj9
iSMAn2DcgtI3uAznKjWA1AmNMk9d/Acl
=7LT8
-----END PGP SIGNATURE-----

References:
- PATCH: Add 32bit SSE2 strlen
  - From: H.J. Lu
- Re: PATCH: Add 32bit SSE2 strlen
  - From: Ulrich Drepper
- Re: PATCH: Add 32bit SSE2 strlen
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]