• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Non human friendly error message from compiler with exceptions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Non human friendly error message from compiler with exceptions


  • Subject: Re: Non human friendly error message from compiler with exceptions
  • From: Jens Miltner <email@hidden>
  • Date: Mon, 14 Jul 2008 17:09:53 +0200


Am 14.07.2008 um 17:04 schrieb Clark Cox:

On Sun, Jul 13, 2008 at 11:38 PM, Jens Miltner <email@hidden> wrote:

Am 11.07.2008 um 14:45 schrieb Stéphane Sudre:


On Jul 11, 2008, at 10:04 AM, Ken Thomases wrote:

On Jul 11, 2008, at 2:48 AM, Stéphane Sudre wrote:

"Mac OS X version 10.5 or later is needed for zerocost-exception"

What is this sentence trying to say?

I'm not entirely sure. Are you trying to compile some Objective- C for
64-bit architecture but also specifying a deployment target of 10.4?


Here's some background: With Leopard, Apple revamped the Objective-C ABI
but only for 64-bit. They couldn't do so for 32-bit because it would break
binary compatibility. In the 64-bit ABI, Objective-C exceptions were based
on the same mechanisms as C++ exceptions, which makes them zero- cost unless
an exception actually happens.


That message seems to suggest you have asked the compiler to emit code
relying on that ABI, but also said you may deploy it on a target not
supporting that ABI.


It looks like it's what you're describing.

Does this imply that you can not build a project easily on Xcode with
exceptions support as soon as you want to test a 32/64-bit Universal Binary
application that can run on Tiger and later?


It sounds like it might be the return of the
"SDK_Deployment_ppc_32_or_something_like_this" options...

I'd assume that there would be an option to specify the exception mechanism
to use (i.e. allow for backward-compatible exception support in 64- bit
binaries, too).

Backwards compatible with what? Before Leopard, one couldn't build 64-bit Objective-C binaries.

Well, the OP was arguing that you should be able to build fat 64/32- bit binaries that run on Tiger and later...
So, at least the 32-bit version should be allowed to be backward compatible.


</jum>




_______________________________________________ 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
References: 
 >Non human friendly error message from compiler with exceptions (From: Stéphane Sudre <email@hidden>)
 >Re: Non human friendly error message from compiler with exceptions (From: Ken Thomases <email@hidden>)
 >Re: Non human friendly error message from compiler with exceptions (From: Stéphane Sudre <email@hidden>)
 >Re: Non human friendly error message from compiler with exceptions (From: Jens Miltner <email@hidden>)
 >Re: Non human friendly error message from compiler with exceptions (From: "Clark Cox" <email@hidden>)

  • Prev by Date: Re: Non human friendly error message from compiler with exceptions
  • Next by Date: Re: GDB always runs before anything else in the console
  • Previous by thread: Re: Non human friendly error message from compiler with exceptions
  • Next by thread: Re: Non human friendly error message from compiler with exceptions
  • Index(es):
    • Date
    • Thread