This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/55593] [4.8 Regression] Bogus error on passing DO LOOP variable
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 04 Dec 2012 14:49:14 +0000
- Subject: [Bug fortran/55593] [4.8 Regression] Bogus error on passing DO LOOP variable
- Auto-submitted: auto-generated
- References: <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.