public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33689] [Regression 4.3] Array with constant bound rejected as automatic array
Date: Mon, 08 Oct 2007 17:58:00 -0000	[thread overview]
Message-ID: <20071008175836.345.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33689-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from burnus at gcc dot gnu dot org  2007-10-08 17:58 -------
Works: r129068; fails: r129069.

http://gcc.gnu.org/ml/gcc-cvs/2007-10/msg00174.html

r129069 | tobi | 2007-10-07 13:45:15 +0200 (So, 07 Okt 2007) | 14 lines

PR 20851
fortran/
* expr.c (check_inquiry): Typo fix in error message.
(check_init_expr): Same * 3.
(check_restricted): Verify that no dummy arguments appear in
restricted expressions in ELEMENTAL procedures.
* resolve.c (resolve_fl_variable): Exchange order of checks to
avoid side-effect.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tobi at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33689


  parent reply	other threads:[~2007-10-08 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08  9:02 [Bug fortran/33689] New: " burnus at gcc dot gnu dot org
2007-10-08  9:07 ` [Bug fortran/33689] " burnus at gcc dot gnu dot org
2007-10-08 10:11 ` dominiq at lps dot ens dot fr
2007-10-08 17:58 ` burnus at gcc dot gnu dot org [this message]
2007-10-08 18:02 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2007-10-08 18:25 ` tobi at gcc dot gnu dot org
2007-10-08 20:26 ` patchapp at dberlin dot org
2007-10-08 20:55 ` tobi at gcc dot gnu dot org
2007-10-08 22:10 ` tobi at gcc dot gnu dot org

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=20071008175836.345.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: link
Be 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).