Am 11.09.2008 um 18:15 schrieb Bill Bumgarner:
On Sep 11, 2008, at 8:47 AM, Frank Illenberger wrote:
As I understand it, try/catch blocks should be very fast (zero
cost) in the 64 bit evironment. As I can't observe the generation
of any exceptions, there has to be some other reason for the
On Sep 11, 2008, at 8:47 AM, Frank Illenberger wrote:
As I understand it, try/catch blocks should be very fast (zero cost)
in the 64 bit evironment. As I can't observe the generation of any
exceptions, there has to be some other reason for the slow
performance. I can't find any documentation
On Sep 11, 2008, at 6:07 AM, Matt Gough wrote:
Dunno, maybe now that the Obj-C exception ABI is the same as the C++
one for 64-bit apps, there is a lot of extra stuff that needs
preparing in case the exception is going to be caught by some C++
code.
This is a known issue and has been addre
As I understand it, try/catch blocks should be very fast (zero cost)
in the 64 bit evironment. As I can't observe the generation of any
exceptions, there has to be some other reason for the slow
performance. I can't find any documentation about
objc_addExceptionHandler, so I don't know if i
On 11 Sep 2008, at 14:49, Frank Illenberger wrote:
I breaked at objc_addExceptionHandler and it gets called a lot. Here
are some example traces:
...
I guess this is normal behavior as these are regular cocoa calls.
But why does this consume so much CPU time?
Cheers
Dunno, maybe now t
Am 11.09.2008 um 14:04 schrieb Jean-Daniel Dupas:
Le 11 sept. 08 à 13:01, Frank Illenberger a écrit :
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit
but when started in x86_64 mode, it runs ab
Le 11 sept. 08 à 13:01, Frank Illenberger a écrit :
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit
but when started in x86_64 mode, it runs about 3-4 times slower.
A shark profile reveals the fo
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit but
when started in x86_64 mode, it runs about 3-4 times slower.
A shark profile reveals the following hot traces:
8.9%libgcc_s.1.dylib_U
Le 11 sept. 08 à 10:44, Frank Illenberger a écrit :
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit but
when started in x86_64 mode, it runs about 3-4 times slower.
A shark profile reveals the foll
