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/45077] ICE with -fwhole-file in fold_convert_loc, at fold-const.c:2021
Date: Thu, 29 Jul 2010 17:00:00 -0000	[thread overview]
Message-ID: <20100729170010.14414.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45077-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from burnus at gcc dot gnu dot org  2010-07-29 17:00 -------
(In reply to comment #4)
> Fixed for the unmodified example in comment 1 - and also for PR 40011 comment
> 47.
> 
> However, the following remains to be done: It still fails if one moves "module
> iso_red" into a separate file (cf. PR 44945). The reason is that then "gsym"
> will come up as NULL and every
> module user uses a different decl.

The challenge to handle truly external procedures correctly is to use - if
possible - the correct interface. For EXTERNAL this is not quite possible - but
one should try to merge the different declarations while one parses the file,
e.g. when one encounters "EXTERNAL" one generates a GSYM - which later gets
updated with the interface (if present somewhere), by procedure usage ("call"),
or by the actual external procedure if it comes later in the file. At the same
time, a consistency check for type and arguments can be done.


-- 


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


  parent reply	other threads:[~2010-07-29 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 13:11 [Bug fortran/45077] New: " burnus at gcc dot gnu dot org
2010-07-27  9:50 ` [Bug fortran/45077] " burnus at gcc dot gnu dot org
2010-07-28  7:44 ` burnus at gcc dot gnu dot org
2010-07-28  8:45 ` burnus at gcc dot gnu dot org
2010-07-28  8:47 ` burnus at gcc dot gnu dot org
2010-07-29 17:00 ` burnus at gcc dot gnu dot org [this message]
     [not found] <bug-45077-4@http.gcc.gnu.org/bugzilla/>
2011-02-20 13:45 ` pault at gcc dot gnu.org
2011-02-20 14:18 ` burnus at gcc dot gnu.org
2011-02-20 15:16 ` dominiq at lps dot ens.fr
2011-02-20 16:28 ` pault at gcc dot gnu.org
2011-02-20 16:50 ` pault 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=20100729170010.14414.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).