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/30237] [4.2 and 4.1 only] Alternate return arguments in intrinsic subroutine calls are ignored
Date: Sat, 06 Jan 2007 14:14:00 -0000 [thread overview]
Message-ID: <20070106141348.28457.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30237-13350@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pault at gcc dot gnu dot org 2007-01-06 14:13 -------
Subject: Bug 30237
Author: pault
Date: Sat Jan 6 14:13:20 2007
New Revision: 120525
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120525
Log:
2007-01-06 Paul Thomas <pault@gcc.gnu.org>
Bug fixes from trunk
PR fortran/30034
* resolve.c (resolve_formal_arglist): Exclude the test for
pointers and procedures for subroutine arguments as well as
functions.
PR fortran/30237
* intrinsic.c (remove_nullargs): Do not pass up arguments with
a label. If the actual has a label and the formal has a type
then emit an error.
PR fortran/25135
* module.c (load_generic_interfaces): If the symbol is present
and is not generic it is ambiguous.
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.
PR fortran/27900
* resolve.c (resolve_actual_arglist): If all else fails and a
procedure actual argument has no type, see if a specific
intrinsic matches.
PR fortran/24325
* resolve.c (resolve_function): If the function reference is
FL_VARIABLE this is an error.
2007-01-06 Paul Thomas <pault@gcc.gnu.org>
PR fortran/30034
* gfortran.dg/pure_formal_proc_1.f90: New test.
PR fortran/30237
* gfortran.dg/intrinsic_actual_3.f90: New test.
PR fortran/25135
* gfortran.dg/generic_11.f90: New test.
* gfortran.dg/interface_7.f90: Remove name clash between module
name and procedure 'x' referenced in the interface.
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.
PR fortran/27900
* gfortran.dg/intrinsic_actual_4.f90: New test.
PR fortran/24325
* gfortran.dg/func_decl_3.f90: New test.
Added:
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/c_by_val.c
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/c_by_val_1.f
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/c_by_val_2.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/c_by_val_3.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/func_decl_3.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/generic_11.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/intrinsic_actual_3.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/intrinsic_actual_4.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/pure_formal_proc_1.f90
Modified:
branches/gcc-4_2-branch/gcc/fortran/ChangeLog
branches/gcc-4_2-branch/gcc/fortran/interface.c
branches/gcc-4_2-branch/gcc/fortran/intrinsic.c
branches/gcc-4_2-branch/gcc/fortran/module.c
branches/gcc-4_2-branch/gcc/fortran/primary.c
branches/gcc-4_2-branch/gcc/fortran/resolve.c
branches/gcc-4_2-branch/gcc/fortran/trans-expr.c
branches/gcc-4_2-branch/gcc/testsuite/ChangeLog
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/dummy_procedure_1.f90
branches/gcc-4_2-branch/gcc/testsuite/gfortran.dg/interface_7.f90
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30237
next prev parent reply other threads:[~2007-01-06 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 9:13 [Bug fortran/30237] New: " brooks at gcc dot gnu dot org
2006-12-17 20:22 ` [Bug fortran/30237] " tobi at gcc dot gnu dot org
2006-12-19 12:48 ` pault at gcc dot gnu dot org
2006-12-19 17:09 ` pault at gcc dot gnu dot org
2006-12-28 18:41 ` pault at gcc dot gnu dot org
2007-01-06 14:14 ` pault at gcc dot gnu dot org [this message]
2007-01-06 14:16 ` [Bug fortran/30237] [4.1 only] " pault at gcc dot gnu dot org
2007-01-10 19:02 ` pinskia at gcc dot gnu dot 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=20070106141348.28457.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).