Re: The bug where terminal and xcode ran "different"
Re: The bug where terminal and xcode ran "different"
- Subject: Re: The bug where terminal and xcode ran "different"
- From: Rob Probin <email@hidden>
- Date: Sun, 11 Feb 2007 09:48:55 +0000
Hi Theodore,
I'm not trying to flame or troll here.
But they are unavoidable when you are writing high performance
stuff, because in these cases
you can't rely on vectors or other easy stuff to "do the right
thing", speedwise.
I thought that the C++ containers had specific dynamics for specific
operations? I wonder if anyone knows how good a job the gcc shipping
with xcode does at optimized versions of these? And you can tell
vector to reserve space - a very similar technique to mallocing a
large section of memory?
I'm also not sure you can entirely rely on multiple mallocs either
across operating systems or operating system versions to give you a
very high performance characteristics? Surely the call can go away
for long periods? Surely you can get task switches that vastly
outweigh time spend in either vector or malloc?
40 years on and we are still getting basic memory management issues,
what a shame.
C (which I assume you are writing) and malloc are, what, 35 years old
(?) and the basic techniques of both of them are older. It's not
entirely surprising that you are getting (these rather well know, if
very annoying) "40 year old" problems. I guess this has driven a lot
of people to classes (allocation = initialization) and containers.
Are people using C++ containers for high-performance stuff (on xcode)?
Regards,
Rob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden