public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55593] [4.8 Regression] Bogus error on passing DO LOOP variable
Date: Tue, 04 Dec 2012 14:50:00 -0000	[thread overview]
Message-ID: <bug-55593-4-jxBxjpTLT4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55593-4@http.gcc.gnu.org/bugzilla/>


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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P4
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |diagnostic, rejects-valid
   Last reconfirmed|                            |2012-12-04
                 CC|                            |burnus at gcc dot gnu.org
     Ever Confirmed|0                           |1
            Summary|Bogus error on passing DO   |[4.8 Regression] Bogus
                   |LOOP variable               |error on passing DO LOOP
                   |                            |variable
   Target Milestone|---                         |4.8.0

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-12-04 14:49:14 UTC ---
>From frontend-passes.c's doloop_code

    case EXEC_CALL:
      f = co->symtree->n.sym->formal;

I think one should use in this case
  co->value.function.esym

I believe co->value.function.* should always exist, given that it comes after
resolution (if not, the symtree can be used as fall back). In any case, one
needs to be careful if it isn't an "isym" instead.


  reply	other threads:[~2012-12-04 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 13:10 [Bug fortran/55593] New: " sfilippone at uniroma2 dot it
2012-12-04 14:50 ` burnus at gcc dot gnu.org [this message]
2012-12-06 22:02 ` [Bug fortran/55593] [4.8 Regression] " tkoenig at gcc dot gnu.org
2012-12-09  9:15 ` tkoenig at gcc dot gnu.org
2012-12-09  9:17 ` tkoenig at gcc dot gnu.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=bug-55593-4-jxBxjpTLT4@http.gcc.gnu.org/bugzilla/ \
    --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).