From patchwork Mon Nov 19 15:40:15 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 200037 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id 8B5FD2C018B for ; Tue, 20 Nov 2012 02:41:25 +1100 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1353944485; h=Comment: DomainKey-Signature:Received:Received:Received:Received:Date: From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type:Mailing-List:Precedence:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:Sender: Delivered-To; bh=MMDNOC7uxMStbvNivCAqpr4otH8=; b=yj9jaAUkb9rteVC rxvIwXYFRr3wCDgLRrjjHXX3kBIQtKW/a5mZxEGv/pROuhsvKEZa0t9oKawnw0eL WU3NqKk+1imty146zbUGYQlYssEcYCjQVSQUL0x2MpY5E5MuznxN53HUOyvEeiu8 YbKJegwhlRYQRQCrCNWEhtQ6sGuQ= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:MIME-Version:Content-Type:X-IsSubscribed:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=fmMLWAKSbRpChGNP/gql20DcBm8MbfhwXr4yXtu+gMdRqUdHBHzujRmDqAAA33 4cJLhlF3Xoej1eA9SdSnyso4o+/2TLIHzLJzNlBu5fv3H6yLCTLl4lUOr3kc0e/7 ++UAo1VnfQmA58ZnWK2zodcOKyg5XqcBZ9B4zEzxNrwi4=; Received: (qmail 21392 invoked by alias); 19 Nov 2012 15:41:19 -0000 Received: (qmail 21343 invoked by uid 22791); 19 Nov 2012 15:41:18 -0000 X-SWARE-Spam-Status: No, hits=-3.4 required=5.0 tests=AWL, BAYES_00, KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 19 Nov 2012 15:40:17 +0000 Received: from [10.24.247.199] (unknown [12.110.94.2]) by ainaz.pair.com (Postfix) with ESMTPSA id CAD3D3F410; Mon, 19 Nov 2012 10:40:15 -0500 (EST) Date: Mon, 19 Nov 2012 07:40:15 -0800 (PST) From: Gerald Pfeifer To: Tobias Burnus cc: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org Subject: Re: [wwwdocs] Update Fortran secrion in 4.8/changes.html In-Reply-To: <50A115AB.6030208@net-b.de> Message-ID: References: <502A5A1F.5050607@net-b.de> <503331CC.9010906@net-b.de> <50A115AB.6030208@net-b.de> MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org On Mon, 12 Nov 2012, Tobias Burnus wrote: > Well, "flag" is GCC teminology (see "man gcc"), though it seems to be > only used for the -f* options while I (mis)used it here for -W*. I > think it is better to use the more common term "command-line option". Okay, so I went ahead and applied the patch below. There is one sentence (preceding my patch) which I don't quite understand (specifically around the "to"): "...which diagnose when code to is inserted for automatic (re)allocation of a variable during assignment." Gerald Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.56 diff -u -3 -p -r1.56 changes.html --- changes.html 12 Nov 2012 15:19:33 -0000 1.56 +++ changes.html 19 Nov 2012 15:19:03 -0000 @@ -169,20 +169,20 @@ B b(42); // OK
  • The - -Wc-binding-type warning flag has been added (by default - disabled), which warns if the a variable might not be C interoperable. In + -Wc-binding-type warning option has been added (disabled + by default), which warns if the a variable might not be C interoperable. In particular, if the variable has been declared using an intrinsic type with default kind instead of using a kind parameter defined for C interoperability in the intrinsic ISO_C_Binding module. Before, - the warning was always printed. The -Wc-binding-type flag + the warning was always printed. The -Wc-binding-type option is enabled by -Wall.
  • The -Wrealloc-lhs and -Wrealloc-lhs-all warning - flags have been added, which diagnose when code to is inserted for automatic - (re)allocation of a variable during assignment. The flag can be used to - decide whether it is safe to use -fno-realloc-lhs. Additionally, it can be used to find automatic (re)allocation in hot loops. (For arrays, replacing var= @@ -190,8 +190,8 @@ B b(42); // OK
  • The - -Wcompare-reals flag has been added. When this flag is set, - warnings are issued when comparing REAL or + -Wcompare-reals command-line option has been added. When + this is set, warnings are issued when comparing REAL or COMPLEX types for equality and inequality; consider replacing a == b by abs(a−b) < eps with a suitable eps. -Wcompare-reals is enabled by @@ -199,9 +199,9 @@ B b(42); // OK
  • The - -Wtarget-lifetime flag has been added (enabled with - -Wall), which warns if the pointer in a pointer assignment - might outlive its target.
    • + -Wtarget-lifetime command-line option has been added + (enabled with -Wall), which warns if the pointer in a + pointer assignment might outlive its target.

  • Reading floating point numbers which use q for the exponential (such as 4.0q0) is now supported as vendor