public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23060] %VAL, %REF and %DESCR constructs not implemented
Date: Sun, 31 Dec 2006 06:55:00 -0000	[thread overview]
Message-ID: <20061231065531.10477.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23060-11040@http.gcc.gnu.org/bugzilla/>



------- Comment #13 from pault at gcc dot gnu dot org  2006-12-31 06:55 -------
Subject: Bug 23060

Author: pault
Date: Sun Dec 31 06:55:16 2006
New Revision: 120295

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120295
Log:
2006-12-31  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/23060
        * intrinsic.c (compare_actual_formal ): Distinguish argument
        list functions from keywords.
        * intrinsic.c (sort_actual): If formal is NULL, the presence of
        an argument list function actual is an error.
        * trans-expr.c (conv_arglist_function) : New function to
        implement argument list functions %VAL, %REF and %LOC.
        (gfc_conv_function_call): Call it.
        * resolve.c (resolve_actual_arglist): Add arg ptype and check
        argument list functions.
        (resolve_function, resolve_call): Set value of ptype before
        calls to resolve_actual_arglist.
        * primary.c (match_arg_list_function): New function.
        (gfc_match_actual_arglist): Call it before trying for a
        keyword argument.

2006-12-31  Paul Thomas  <pault@gcc.gnu.org>

        PR fortran/23060
        * gfortran.dg/c_by_val.c: Called by c_by_val_1.f.
        * gfortran.dg/c_by_val_1.f: New test.
        * gfortran.dg/c_by_val_2.f: New test.
        * gfortran.dg/c_by_val_3.f: New test.

Added:
    trunk/gcc/testsuite/gfortran.dg/c_by_val.c
    trunk/gcc/testsuite/gfortran.dg/c_by_val_1.f
    trunk/gcc/testsuite/gfortran.dg/c_by_val_2.f90
    trunk/gcc/testsuite/gfortran.dg/c_by_val_3.f90
    trunk/gcc/testsuite/gfortran.dg/char_length_1.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/interface.c
    trunk/gcc/fortran/intrinsic.c
    trunk/gcc/fortran/primary.c
    trunk/gcc/fortran/resolve.c
    trunk/gcc/fortran/trans-expr.c
    trunk/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2006-12-31  6:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23060-11040@http.gcc.gnu.org/bugzilla/>
2005-12-07 15:28 ` [Bug fortran/23060] %VAL construct " martinol at nrlssc dot navy dot mil
2006-09-28  7:58 ` fxcoudert at gcc dot gnu dot org
2006-10-12 12:43 ` pault at gcc dot gnu dot org
2006-10-12 13:19 ` fxcoudert at gcc dot gnu dot org
2006-11-03 14:12 ` [Bug fortran/23060] %VAL, %REF and %DESCR constructs " fxcoudert at gcc dot gnu dot org
2006-11-14 10:16 ` pault at gcc dot gnu dot org
2006-12-29 17:25 ` patchapp at dberlin dot org
2006-12-31  6:55 ` pault at gcc dot gnu dot org [this message]
2007-01-06 14:14 ` pault at gcc dot gnu dot org
2007-01-06 14:18 ` pault at gcc dot gnu dot org
2007-01-10 19:12 ` pinskia at gcc dot gnu dot org
2007-01-26  1:05 ` dmarkman at mac dot com
2007-01-26  1:45 ` dmarkman at mac dot com
     [not found] <bug-23060-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:15 ` jackie.rosen at hushmail dot com

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=20061231065531.10477.qmail@sourceware.org \
    --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).