public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93963] Select rank mishandling allocatable and pointer arguments with bind(c)
Date: Sat, 15 May 2021 03:44:43 +0000	[thread overview]
Message-ID: <bug-93963-4-ToGX003Wu6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93963-4@http.gcc.gnu.org/bugzilla/>

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

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to sandra from comment #2)
> Fiddling with the test case a bit, I observe that the RANK() intrinsic
> returns the correct result even in the functions where SELECT RANK fails. 
> Seems odd that SELECT RANK uses different logic.

Why?  The code for SELECT RANK was added in 2019 and code for
RANK() was added sometime around 2011.  It seems the individuals,
who committed each feature, are different people.  At least, one
of the two took a very long hiatus from working on gfortran, and
the other seems not to be omniscient.

  parent reply	other threads:[~2021-05-15  3:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93963-4@http.gcc.gnu.org/bugzilla/>
2020-07-23 16:07 ` dominiq at lps dot ens.fr
2021-05-15  1:58 ` sandra at gcc dot gnu.org
2021-05-15  3:44 ` kargl at gcc dot gnu.org [this message]
2021-05-19 18:07 ` jrfsousa at gcc dot gnu.org
2021-05-30 20:09 ` dominiq at lps dot ens.fr
2021-06-14 23:19 ` jrfsousa at gcc dot gnu.org
2021-06-14 23:19 ` jrfsousa at gcc dot gnu.org
2021-07-26 12:33 ` cvs-commit at gcc dot gnu.org
2021-10-19 13:29 ` burnus 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-93963-4-ToGX003Wu6@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).