public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/96073] [11.0 regression] regression in gfc_format_decoder
Date: Sat, 11 Jul 2020 09:57:55 +0000	[thread overview]
Message-ID: <bug-96073-4-fviZr1WpPA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96073-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96073

--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
What we have here is, in gfc_check_externals0,

(gdb) call debug(def_sym->formal) 

|| symbol: '_formal_0'    
  type spec : (INTEGER 4)
  attributes: (VARIABLE  ARTIFICIAL DUMMY)
|| symbol: '_formal_1'    
  type spec : (REAL 4)
  attributes: (VARIABLE  ARTIFICIAL DUMMY)
(gdb) call debug(sym->formal)

|| symbol: 'set'          
  type spec : (INTEGER 4)
  attributes: (VARIABLE  DUMMY(IN))
|| symbol: 'xmin'         
  type spec : (REAL 4)
  attributes: (VARIABLE  DUMMY(OUT))

so the inferred argument list from the call does not match the
interface.  And, since the location is not set, we get an ICE
on top of it.

I think resolution should have found the interface in addition
to the EXTERNAL statement.

  parent reply	other threads:[~2020-07-11  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  9:42 [Bug fortran/96073] New: " juergen.reuter at desy dot de
2020-07-06 12:23 ` [Bug fortran/96073] " juergen.reuter at desy dot de
2020-07-06 15:32 ` [Bug fortran/96073] [11 Regression] " rguenth at gcc dot gnu.org
2020-07-06 16:03 ` [Bug fortran/96073] [11.0 regression] " juergen.reuter at desy dot de
2020-07-06 17:51 ` tkoenig at gcc dot gnu.org
2020-07-07  8:56 ` marxin at gcc dot gnu.org
2020-07-11  9:42 ` tkoenig at gcc dot gnu.org
2020-07-11  9:57 ` tkoenig at gcc dot gnu.org [this message]
2020-07-11 13:11 ` tkoenig at gcc dot gnu.org
2020-07-11 17:19 ` cvs-commit at gcc dot gnu.org
2020-07-11 17:25 ` tkoenig at gcc dot gnu.org
2020-07-11 17:25 ` 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-96073-4-fviZr1WpPA@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).