public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kloedej at knmi dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/37746] string copy fails, due to changed intent(in) parameter Date: Tue, 07 Oct 2008 11:25:00 -0000 [thread overview] Message-ID: <20081007112345.2864.qmail@sourceware.org> (raw) In-Reply-To: <bug-37746-11277@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from kloedej at knmi dot nl 2008-10-07 11:23 ------- Hi, thanks for this discussion. I do agree now that this code was invalid. I was thinking otherwise because no compiletime or runtime error was issued by any of the compilers that I tried. Checking this during compilation should at least be possible when the interface of the subroutine is known, so when it is defined inside a module, but gfortran also accepts that case without complaining. best regards, Jos de Kloe. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37746
next prev parent reply other threads:[~2008-10-07 11:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-06 11:33 [Bug fortran/37746] New: " kloedej at knmi dot nl 2008-10-06 14:48 ` [Bug fortran/37746] " kargl at gcc dot gnu dot org 2008-10-06 19:54 ` burnus at gcc dot gnu dot org 2008-10-07 11:25 ` kloedej at knmi dot nl [this message] 2008-10-12 11:35 ` [Bug fortran/37746] bounds check of string dummy arguments tkoenig at gcc dot gnu dot org 2008-12-20 19:11 ` domob at gcc dot gnu dot org 2009-01-04 8:41 ` domob at gcc dot gnu dot org 2009-01-04 8:42 ` domob at gcc dot gnu dot org 2009-04-11 16:45 ` domob at gcc dot gnu dot org 2009-04-11 16:47 ` 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=20081007112345.2864.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: 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).