From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13550 invoked by alias); 12 Aug 2014 14:54:12 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 13531 invoked by uid 89); 12 Aug 2014 14:54:09 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 12 Aug 2014 14:54:07 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1XHDSe-0001yR-05 from joseph_myers@mentor.com ; Tue, 12 Aug 2014 07:54:04 -0700 Received: from SVR-IES-FEM-02.mgc.mentorg.com ([137.202.0.106]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Aug 2014 07:54:03 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-02.mgc.mentorg.com (137.202.0.106) with Microsoft SMTP Server id 14.2.247.3; Tue, 12 Aug 2014 15:54:01 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.76) (envelope-from ) id 1XHDSa-0004Li-5w; Tue, 12 Aug 2014 14:54:00 +0000 Date: Tue, 12 Aug 2014 14:54:00 -0000 From: "Joseph S. Myers" To: Thomas Preud'homme CC: Subject: RE: [PATCH, C/C++] Add -fno-float to forbid floating point data types In-Reply-To: <000801cfb617$304428b0$90cc7a10$@arm.com> Message-ID: References: <000701cfb60f$5b859700$1290c500$@arm.com> <000801cfb617$304428b0$90cc7a10$@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2014-08/txt/msg01132.txt.bz2 On Tue, 12 Aug 2014, Thomas Preud'homme wrote: > 3) __builtin_sqrt > > True, I shall try if it works with builtins. Thanks for the advice. In addition to built-in functions, you have built-in typedefs. I don't think your code would catch uses of __fp16, __float128 etc. (such types are defined as built-in typedefs by back ends at present, not as keywords). Rather than making back ends have their own conditionals, the built-in typedef issue could be dealt with by checking whether the type given by a sequence of declspecs (in a declaration or type name) is a floating-point type (in or after c_finish_declspecs - in the __auto_type case, getting a floating-point type means the initializer has such a type and you should catch things when handling the initializer). Also consider built-in typedefs and functions involving vectors of floating-point types, as well as the simple real and complex types. > 4) Objective C > > As said in the description, I'm not opposed to adding other language. > It's easier to add another language than remove one after the fact > because very few people use it. Therefore I preferred to have > just C and C++ for now which is what I expect most of the users of > such a switch to be interested in. Do you think I should add support > for that language up front or can it wait a later version of the patch > once people started to use it? The presumption should be that an option for C also applies to Objective-C (and likewise for C++ options and Objective-C++), unless there is a concrete reason this is problematic (i.e. an Objective-C feature that needs special handling to implement the option). -- Joseph S. Myers joseph@codesourcery.com