[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: Changing clang defaults for 3.1

From: Sebastian Reitenbach
Subject: Re: RFC: Changing clang defaults for 3.1
Date: Fri, 06 Apr 2012 08:09:16 +0200
User-agent: SOGoMail 1.3.14

On Thursday, April 5, 2012 13:06 CEST, David Chisnall <address@hidden> wrote: 
> Hi Everyone,
> I am considering, for the 3.1 release, making blocks, the non-fragile ABI and 
> the non-legacy dispatch mechanism (objc_msgSend(), at least on x86[-64] and 
> ARM) the default on FreeBSD, and possibly other platforms.  The old modes 
> will still be available, via -fblocks, -fno-objc-nonfragile-abi and 
> -fno-objc-nonlegacy-dispatch, but they'll need to be explicitly specified.
> Would this break anything for anyone?  Would any other platforms (OpenBSD?) 
> like to have the same defaults.  It's probably worth keeping GNU/Linux 
> defaulting to the GCC-runtime-compatible mode for everything, at least for 
> now.

Does gnustep-make handle all those new clang parameters? If not, I'd prefer to 
keep everything as is for OpenBSD.
I still have one or two ports in the tree that don't work with non-fragile-abi.


> David
> _______________________________________________
> Discuss-gnustep mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep

reply via email to

[Prev in Thread] Current Thread [Next in Thread]