From patchwork Mon Jan 7 22:33:02 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gerald Pfeifer X-Patchwork-Id: 210256 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 2C5A42C0087 for ; Tue, 8 Jan 2013 09:33:37 +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=1358202818; 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=aAkgCoMvbtn79Mug4c4m/u8Keu0=; b=ywsMrZxpl/u4Pze UwV+P08rHStKZEJDF/TLtYGjKv1mvbwRn5Dth9DvuCe8El7+6OLc/pEvWYqpMHmR l96w9mg7ETyst+q7as0+y+yYUdxylQOfYek29uqNwNVZYVe5L+ly+Kxr6/xKVOs0 3UqYzDxz6V80RaQ5OLEwRFqSvR8c= 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=hBUFANVpWC5Rb2Et4RCjadow7mh1bLgbv/LN3xIgMzkgyBcMIoXQqe1NCKEGsv Y4ruc9nqtSwssEf7plFoNR6FseNPr0GG7drU4gquyzsQgmgG892eadGXTWxyEgvp e6CWRAFCrZunhY35zPNzFNco/Z6K8zxSRNI6HwbzpyYFs=; Received: (qmail 26425 invoked by alias); 7 Jan 2013 22:33:30 -0000 Received: (qmail 26405 invoked by uid 22791); 7 Jan 2013 22:33:28 -0000 X-SWARE-Spam-Status: No, hits=-3.3 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, 07 Jan 2013 22:33:24 +0000 Received: from [192.168.176.26] (unknown [202.90.70.78]) by ainaz.pair.com (Postfix) with ESMTPSA id 75BC13F410; Mon, 7 Jan 2013 17:33:13 -0500 (EST) Date: Mon, 7 Jan 2013 12:33:02 -1000 (TAHT) From: Gerald Pfeifer To: Tobias Burnus , gcc-patches@gcc.gnu.org cc: fortran@gcc.gnu.org Subject: Re: [Patch, wwwdocs] Update Fortran part of the GCC 4.8 release notes In-Reply-To: <50D2E0A0.7000201@net-b.de> Message-ID: References: <50D2E0A0.7000201@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 Thu, 20 Dec 2012, Tobias Burnus wrote: > The following patch updates the Fortran part of the GCC 4.8 release > notes at http://gcc.gnu.org/gcc-4.8/changes.html#fortran Nice! I had a look and made a couple of editorial changes which should not change any of the statements. If you'd like to see some adjusted (or clarified) or have further suggestions, let me know and I'll take care. Gerald Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.77 retrieving revision 1.78 diff -u -3 -p -r1.77 -r1.78 --- changes.html 3 Jan 2013 05:11:30 -0000 1.77 +++ changes.html 7 Jan 2013 22:31:45 -0000 1.78 @@ -246,20 +246,21 @@ B b(42); // OK
  • Compatibility notice:
      -
    • Module files: The version of the module files (.mod) +
    • Module files: The version of module files (.mod) has been incremented. Fortran MODULEs compiled by earlier GCC versions have to be recompiled, when they are USEd by - files compiled with GCC 4.8, because GCC 4.8 is not able to read - .mod file of earlier GCC versions; attempting to do so - gives an error message. Note: The ABI of the produced assembler data - itself has not changed; object files and libraries are fully compatible - to older versions. (Except as noted below.)
    • -
    • ABI: Some internal names (name in the assembler/object file) have + files compiled with GCC 4.8. GCC 4.8 is not able to read + .mod files created by earlier versions; attempting to do so + gives an error message.
      + Note: The ABI of the produced assembler data itself has not changed; + object files and libraries are fully compatible + with older versions except as noted below.
    • +
    • ABI: Some internal names (used in the assembler/object file) have changed for symbols declared in the specification part of a module. - If the module – or a file using such a symbol via use - association – is recompiled, the module and all files which - directly use such symbols have to be recompiled. The change only - affects the following kind of module symbols: + If an affected module – or a file using it via use + association – is recompiled, the module and all files which + directly use such symbols have to be recompiled as well. This change + only affects the following kind of module symbols:
      • Procedure pointers. Note: C-interoperable function pointers (type(c_funptr)) are not affected nor are @@ -276,12 +277,12 @@ B b(42); // OK
      • The -Wc-binding-type warning option has been added (disabled - by default), which warns if the a variable might not be C interoperable. In + by default). It 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 option - is enabled by -Wall.
      • + interoperability in the intrinsic ISO_C_Binding module. + Before, this warning was always printed. The -Wc-binding-type + option is enabled by -Wall.
      • The @@ -334,7 +335,7 @@ B b(42); // OK
      • Fortran 2003:
        • Support for unlimited polymorphic variables (CLASS(*)) - has been added. Note that nonconstant character lengths are not yet + has been added. Nonconstant character lengths are not yet supported.