On Wed, Jun 1, 2011 at 8:48 PM, Sun Chan <sun.c...@gmail.com> wrote: > I don't know who the STL gatekeeper is. It seemed to be better if this > is submitted to STL community? If there is no suggestion within a > couple of days, I might forward? Shin, any suggestion? > For what it's worth, the open64 compiler's base (i.e. SGI compiler) > used to have a lot of input improving STL's API, performance etc, it > will be great to reinvigorate this tradition again. :-)
g++ STL isn't known to be very good so the first step in that direction would likely be switching over to STDCXX or libc++. I've not seen benchmarks for libc++, but it's rumored to get gains by using the new C++0x standard. The STL "community" would mean upstream gcc? That would possibly be problematic for 2 reasons 1) The STL Open64 has pulled into the codebase is *very* old 2) I highly doubt upstream will take the patch in it's current form. (Sorry - I don't know how to offer something constructive past this) ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
