[...redirecting to stdcxx-dev...]
Eric Lemings wrote:
Also are you aware of lots of warnings about inlining in optimized
builds? Warnings like this:
"warning: inlining failed in call to..."
It's gcc 4.1.1 on RHAP 5.
I am but we're not keeping track of 'em all. There are two
separate issues for them so far, I'm almost positive there
are more:
https://issues.apache.org/jira/browse/STDCXX-416
https://issues.apache.org/jira/browse/STDCXX-415
Please open new Jira issues for each set of related warnings
like this.
Martin
-----Original Message-----
From: Eric Lemings
Sent: Tuesday, May 22, 2007 11:19 AM
To: Martin Sebor
Subject: RE: EASTL
I'm fairly certain that was not an optimized build. The benchmark
was built with optimization but not the library.
I'm redoing it now.
-----Original Message-----
From: Eric Lemings
Sent: Friday, May 11, 2007 12:36 PM
To: Martin Sebor
Subject: RE: EASTL
-----Original Message-----
From: Martin Sebor
Sent: Friday, May 11, 2007 12:20 PM
To: Eric Lemings
Subject: Re: EASTL
...
Without optimization the numbers don't mean much. Those who
care about optimum runtime performance will almost certainly
use -O2 if not -O3.
Optimized results (-O2 level)
...