call for libstdc++ profile mode diagnostic ideas

[Marc Glisse]

On Thu, 16 Dec 2010, Silvius Rus wrote:

> I'm planning to add a set of new performance diagnostics to the
> libstdc++ profile mode
[...]
> - container selection (e.g., replace list with deque).

Hello,

I just wanted to mention that I've had a case today where this exact 
advice would have been welcome. The list was used with only empty() and
(push_|pop_|)(front|back), and although deque is not optimal, it still 
performs better than list in this case.

It is not always very convenient that all programs use the same file name 
for their output, but we worked around that.

Do you have a convenient script to turn the call stack into something 
human-readable? Using backtrace_symbols for the .txt file would be nice.

Thank you for the profile mode,

-- 
Marc Glisse