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 fortran/54613] New: [F2003/F2008] Add FINDLOC plus support MAXLOC/MINLOC with KIND=/BACK=
Date: Tue, 18 Sep 2012 07:41:00 -0000	[thread overview]
Message-ID: <bug-54613-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 54613
           Summary: [F2003/F2008] Add FINDLOC plus support MAXLOC/MINLOC
                    with KIND=/BACK=
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: burnus@gcc.gnu.org


Fortran 2003 (cf. PR 29600) added KIND= to MINLOC/MAXLOC, Fortran 2008 added
BACK=. Additionally, Fortran 2008 added FINDLOC with a similar syntax.

See also James' post in "binary data"
https://groups.google.com/forum/?fromgroups=#!topic/comp.lang.fortran/GpaACNKn0Ds

"As can be seen from the commented out code, gfortran does not yet
 implement the BACK= argument for the MAXLOC and MINLOC intrinsics,
 doesn't yet implement MAXLOC, MAXVAL, MINLOC, MINVAL for constant
 expressions and doesn't implement FINDLOC at all."

See also his comments in
https://groups.google.com/forum/?fromgroups=#!topic/comp.lang.fortran/5eAz5ns6AG0



The first step is to implement the run-time version, i.e. extending
MINLOC/MAXLOC and adding FINDLOC.

(trans-intrinsic.c version, frontend-optimization.c and the library version,
possibly such that one doesn't cause an explosion of the intrinsics, e.g. only
returning default + index-type? If so, one needs to have a RANGE_REF copy for
the array results - and for the MASK argument.)


As a next step, one has to think of the compile-time simplification of
{MIN,MAX}{VAL,LOC},FINDLOC.


             reply	other threads:[~2012-09-18  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  7:41 burnus at gcc dot gnu.org [this message]
2012-09-18  9:17 ` [Bug fortran/54613] " burnus at gcc dot gnu.org
2012-09-18  9:25 ` dominiq at lps dot ens.fr

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