Bug 15313 - gfc_error's emitted from trans-common.c
Summary: gfc_error's emitted from trans-common.c
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: fortran (show other bugs)
Version: tree-ssa
: P2 minor
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords: diagnostic
Depends on:
Blocks:
 
Reported: 2004-05-06 11:07 UTC by Tobias Schlüter
Modified: 2006-02-12 18:35 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-12-30 18:45:53

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Schlüter 2004-05-06 11:07:17 UTC 
trans-common.c emits several gfc_error()s these should all be handled by the
resolution stage, AFAICS.

[tobi@marktplatz fortran]$ grep -n gfc_error trans-common.c
460:        gfc_error ("bad array reference at %L", &s->where);
468:        gfc_error ("illegal reference type at %L as EQUIVALENCE object",
512:    gfc_error ("inconsistent equivalence rules involving '%s' at %L and "
625:        gfc_error ("the equivalence set for '%s' cause an invalid extension "
Comment 1 Tobias Schlüter 2004-05-06 11:16:17 UTC 
(In reply to comment #0)
> [tobi@marktplatz fortran]$ grep -n gfc_error trans-common.c
> 460:        gfc_error ("bad array reference at %L", &s->where);
> 468:        gfc_error ("illegal reference type at %L as EQUIVALENCE object",
> 512:    gfc_error ("inconsistent equivalence rules involving '%s' at %L and "
> 625:        gfc_error ("the equivalence set for '%s' cause an invalid extension "

the first two should be internal_errors. It remain the latter two.
Comment 2 Andrew Pinski 2004-05-06 12:32:04 UTC 
Confirmed.
Comment 3 Tobias Schlüter 2006-02-12 18:35:36 UTC 
I don't think this is important enough to waste any time on it, also Paul Brook has added a few more in the meantime, so this is not our maintainers' policy :-)