This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/29600] [F03] MINLOC and MAXLOC take an optional KIND argument
- From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 27 Oct 2017 02:37:18 +0000
- Subject: [Bug fortran/29600] [F03] MINLOC and MAXLOC take an optional KIND argument
- Auto-submitted: auto-generated
- References: <bug-29600-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29600
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #16 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #15)
> Out of ideas at the moment, unassigning myself.
Without looking at your attempts, it seems one could parse in the scanner for
whether there is this optional argumanet. If not, set it to NULL and in that
case do what we do now, otherwise do a kind conversion. Is this what you
tried?
Runtime would just check for the parameter and do it tat way.
Or are you trying to inline this or do it all in the frontend?