From owner-freebsd-current Mon Sep 9 0: 7: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7291837B400; Mon, 9 Sep 2002 00:07:02 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07E1243E75; Mon, 9 Sep 2002 00:07:02 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g89771fO027199; Mon, 9 Sep 2002 00:07:01 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g89770vs027183; Mon, 9 Sep 2002 00:07:00 -0700 (PDT) Date: Mon, 9 Sep 2002 00:07:00 -0700 From: "David O'Brien" To: Garrett Wollman Cc: current@FreeBSD.org, kan@FreeBSD.org Subject: Re: No way to tell when `long long' is or is not supported? Message-ID: <20020909070700.GA26978@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Garrett Wollman , current@FreeBSD.org, kan@FreeBSD.org References: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200209090350.g893oHMs062192@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Sep 08, 2002 at 11:50:17PM -0400, Garrett Wollman wrote: > GCC used to define a macro __STRICT_ANSI__ when `-ansi' was given on > the command line. The current version does not do this, It seems to work for me: $ cat foo.c #ifdef __STRICT_ANSI__ #error __STRICT_ANSI__ #endif $ /usr/bin/cc -ansi foo.c foo.c:2:2: #error __STRICT_ANSI__ The problem is it is also set for this: $ /usr/bin/cc -std=c99 foo.c foo.c:2:2: #error __STRICT_ANSI__ As you mentioned, this is now not a good test to decide if 'long long' is supported. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message