This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Can you commit this to gcc-4.0?
- From: Feng Wang <wf_cs at yahoo dot com>
- To: roger at eyesopen dot com
- Cc: fortran at gcc dot gnu dot org
- Date: Sun, 10 Jul 2005 22:46:28 +0800 (CST)
- Subject: Can you commit this to gcc-4.0?
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=l/qi134sG4sBaawzVCa6hWXbN0dSTkoBLZHQgdbdmKexUnhvTx3oXqTNBw92QllM7Xc/pZlb9YaQ65NuEBu1xYAO7EOPKncn+Ow5H+l8se0EYpVM6Oun4XXAHpj6OUE3l/JGJ+vbhFKnQWSEm++DjrQ2AGK5pqAcGH1nIqRTwXk= ;
Hi Roger,
Can you port and commit your changes to gcc-4.0? I need the patch:
2005-05-30 Roger Sayle <roger@eyesopen.com>
* gfortran.h (GFC_STD_LEGACY): New "standard" macro. Reindent.
* options.c (gfc_init_options): By default, allow legacy extensions
but warn about them.
(gfc_post_options): Make -pedantic warn about legacy extensions
even with -std=legacy.
(gfc_handle_option): Make -std=gnu follow the default behaviour
of warning about legacy extensions, but allowing them. Make the
new -std=legacy accept everything and warn about nothing.
* lang.opt (std=legacy): New F95 command line option.
* invoke.texi: Document both -std=f2003 and -std=legacy.
* gfortran.texi: Explain the two types of extensions and document
how they are affected by the various -std= command line options.
Best Regards,
Feng Wang
--
Creative Compiler Research Group,
National University of Defense Technology, China.
__________________________________________________
赶快注册雅虎超大容量免费邮箱?
http://cn.mail.yahoo.com