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: exchange_and_add inlined in g++ 4.0.2


On Sun, Nov 06, 2005 at 02:31:52AM +0100, Paolo Carlini wrote:
> >Thanks for the reference. So do I understand correctly there is no way to
> >get the i486+ version?
> >
> No, this is incorrect. In the *.so there is the i486+ version, only,
> it's not inlined.

Ok - does the .so contain only one implementation depending on the
./configure of g++, or does it autodetect? Is my understanding correct that
when configured w/o any architecture options on "regular intel" platforms
the i386 version gets compiled in?

> >It is the top function that is related to the pdns_recursor in this system-wide profile:
> Well, certainly I should know the application in some detail in order to
> be able to tell you something meaningful, which is not the case.
> However, in general, I see numbers below 2%...

This is system wide, including kernel and idle cycles. Relative to my
application is is more like 15%, which is real enough.

> >Will do. I think I can provide my own __exchange_and_add as an inline?
> Sure! If you are willing to poke a bit into the sources (this is free
> software, after all! ;) you can very easily fix the problem to suit your

More exactly I meant, if I add an inlined __gnu_cxx::__exchange_and_add to
my binary, would that work, w/o recompling libstdc++ etc.

> needs. Thanks for filing the PR.

Doing that now, thanks.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services


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