This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: Optimising std::find on x86 and PPC

From: Paolo Carlini <pcarlini at suse dot de>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: Chris Jefferson <caj at cs dot york dot ac dot uk>,libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Tue, 14 Dec 2004 17:06:16 +0100
Subject: Re: Optimising std::find on x86 and PPC
References: <41BEF98C.3000403@cs.york.ac.uk> <41BF07B8.1020504@suse.de> <41BF0CE8.9000701@cs.york.ac.uk> <41BF0E71.30106@suse.de>

Paolo Carlini wrote:

Besided what Gaby and Benjamin already replied, out of curiosity, what the loop unroller is doing, right now?!? Nothing!?!

More explicitly, and in the "right" spirit for the library: let's suppose we remove completely any ad-hoc loop-unrolling by hand, can we trust the loop-unroller to do a decent work both on x86-linux and darwin-powerpc? This is something worth investigating, IMHO... and in case the loop unroller does crazy things file immediately a PR.

Paolo.

Follow-Ups:
- Re: Optimising std::find on x86 and PPC
  - From: Chris Jefferson

References:
- Optimising std::find on x86 and PPC
  - From: Chris Jefferson
- Re: Optimising std::find on x86 and PPC
  - From: Paolo Carlini
- Re: Optimising std::find on x86 and PPC
  - From: Chris Jefferson
- Re: Optimising std::find on x86 and PPC
  - From: Paolo Carlini

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