public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20460] Nasty extensions that should always warn Date: Wed, 10 May 2006 14:59:00 -0000 [thread overview] Message-ID: <20060510145857.10325.qmail@sourceware.org> (raw) In-Reply-To: <bug-20460-8513@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from fxcoudert at gcc dot gnu dot org 2006-05-10 14:58 ------- Subject: Bug 20460 Author: fxcoudert Date: Wed May 10 14:58:48 2006 New Revision: 113672 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=113672 Log: PR fortran/20460 * resolve.c (gfc_resolve_index): Make REAL array indices a GFC_STD_LEGACY feature. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/resolve.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20460
next prev parent reply other threads:[~2006-05-10 14:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20460-8513@http.gcc.gnu.org/bugzilla/> 2006-05-07 16:41 ` fxcoudert at gcc dot gnu dot org 2006-05-07 16:46 ` Tobias dot Schlueter at physik dot uni-muenchen dot de 2006-05-07 16:48 ` fxcoudert at gcc dot gnu dot org 2006-05-10 14:59 ` fxcoudert at gcc dot gnu dot org [this message] 2006-05-11 21:39 ` [Bug fortran/20460] [4.1 only] " fxcoudert at gcc dot gnu dot org 2006-05-11 21:40 ` [Bug fortran/20460] " fxcoudert at gcc dot gnu dot org 2005-03-13 18:39 [Bug fortran/20460] New: " tobi at gcc dot gnu dot org 2005-03-13 18:44 ` [Bug fortran/20460] " pinskia at gcc dot gnu dot org 2005-03-14 6:34 ` kargl at gcc dot gnu dot org 2005-03-14 10:56 ` tobi at gcc dot gnu dot org 2005-03-30 5:57 ` aoliva at redhat dot com 2005-03-30 18:58 ` law at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060510145857.10325.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).