public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/96212] new test case libgomp.fortran/alloc-3.F fails in r11-2101
Date: Wed, 15 Jul 2020 21:10:31 +0000	[thread overview]
Message-ID: <bug-96212-4-a6RfiWhxjP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96212-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Bill Seurer from comment #1)
> After running on a few more machines this appears to be a BE only issue.

alloc-1.F90 uses a proper interface (Fortran module). alloc-3.F uses a header
file with the old-style Fortran 66/77 way of just having
   external subroutine_name
or
   external function_name
   integer function_name  ! <- data type the function returns.

Thus, by this declaration the compiler does not know how the interface actually
looks like. In principle, it could (and should?!?) deduce the interface from
the first procedure call – and create the declaration from the use. However, it
doesn't do this.

My bet is that the actually used argument-passing of caller and callee differs
on PowerPC and, hence, it fails.

Solution?
* XFAIL?
* Changing the way in gfortran how the external-function declaration is
generated?

      parent reply	other threads:[~2020-07-15 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 20:24 [Bug testsuite/96212] New: " seurer at linux dot vnet.ibm.com
2020-07-15 20:43 ` [Bug testsuite/96212] " seurer at linux dot vnet.ibm.com
2020-07-15 21:10 ` burnus at gcc dot gnu.org [this message]

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-96212-4-a6RfiWhxjP@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).