public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45474] New: Missing definable check actuals to INTENT(INOUT) dummies of intrinsics Date: Wed, 01 Sep 2010 06:48:00 -0000 [thread overview] Message-ID: <bug-45474-13404@http.gcc.gnu.org/bugzilla/> (raw) No error is printed for: call execute_command_line("date", .true.,(1),(1),('aa')) end although the third to fifth argument are declared as INTENT(INOUT) in intrinsic.c and thus they have to be definable. The example is for execute_command_line, but I think it applies to all intrinsics. -- Summary: Missing definable check actuals to INTENT(INOUT) dummies of intrinsics Product: gcc Version: 4.6.0 Status: UNCONFIRMED Keywords: accepts-invalid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: burnus at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45474
next reply other threads:[~2010-09-01 6:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-01 6:48 burnus at gcc dot gnu dot org [this message] 2010-09-01 8:34 ` [Bug fortran/45474] " fxcoudert at gcc dot gnu dot org 2010-09-22 10:05 ` domob at gcc dot gnu dot org 2010-09-23 8:38 ` domob at gcc dot gnu dot org 2010-09-23 8:40 ` domob 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=bug-45474-13404@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: linkBe 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).