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/30922] IMPORT fails for same symbol in multiple interface bodies of same interface block
Date: Mon, 12 Mar 2007 08:51:00 -0000 [thread overview]
Message-ID: <20070312085051.1159.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30922-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from burnus at gcc dot gnu dot org 2007-03-12 08:50 -------
Created an attachment (id=13193)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13193&action=view)
Patch draft (by Paul Thomas)
Notes by Paul:
----------------
(i) gfc_find_symbol searches via proc_name->ns to overcome standard
problem with interfaces in enclosed procedures.
(ii) Add field imported to gfc_symtree
(iii) Set it when a symbol is imported
(iv)resolve.c 5658 to use imported to stop false error for individually
imported symbols.
----------------
Note, it does not fix the problem of comment 1 (which was found later).
It causes some regressions (filelist below) with such errors:
gfortran.fortran-torture/execute/der_io.f90:55.20:
subroutine foo(t)
1
gfortran.fortran-torture/execute/der_io.f90:5.15:
type xyz_type
2
Error: The type xyz_type cannot be host associated at (1) because it is
blocked by an incompatible object of the same name at (2)
Files:
gfortran.dg/automatic_default_init_1.f90
gfortran.dg/char_result_11.f90
gfortran.dg/char_result_5.f90
gfortran.dg/char_result_6.f90
gfortran.dg/default_initialization_2.f90
gfortran.dg/dependency_19.f90
gfortran.dg/der_charlen_1.f90
gfortran.dg/der_io_2.f90
gfortran.dg/der_io_3.f90
gfortran.dg/der_pointer_3.f90
[...]
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30922
next prev parent reply other threads:[~2007-03-12 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 9:10 [Bug fortran/30922] New: " burnus at gcc dot gnu dot org
2007-03-02 16:14 ` [Bug fortran/30922] " burnus at gcc dot gnu dot org
2007-03-02 16:16 ` burnus at gcc dot gnu dot org
2007-03-12 8:51 ` burnus at gcc dot gnu dot org [this message]
2007-03-12 14:51 ` patchapp at dberlin dot org
2007-03-12 15:25 ` pault at gcc dot gnu dot org
2007-03-14 4:37 ` brooks at gcc dot gnu dot org
2007-03-14 4:39 ` brooks at gcc dot gnu dot org
2007-03-14 4:48 ` brooks at gcc dot gnu dot org
2007-03-15 6:45 ` pault at gcc dot gnu dot org
2007-03-15 6:55 ` burnus 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=20070312085051.1159.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).