public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60392] Problem with TRANSPOSE and CONTIGUOUS dummy arguments Date: Fri, 14 Mar 2014 21:30:00 -0000 [thread overview] Message-ID: <bug-60392-4-BV1WKrjvLU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60392-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60392 --- Comment #8 from Mikael Morin <mikael at gcc dot gnu.org> --- Fixed on trunk.
next prev parent reply other threads:[~2014-03-14 21:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-02 21:45 [Bug fortran/60392] New: " a.vogt at fulguritus dot com 2014-03-02 21:45 ` [Bug fortran/60392] " a.vogt at fulguritus dot com 2014-03-03 8:57 ` janus at gcc dot gnu.org 2014-03-05 20:39 ` mikael at gcc dot gnu.org 2014-03-05 20:45 ` mikael at gcc dot gnu.org 2014-03-07 21:01 ` mikael at gcc dot gnu.org 2014-03-07 21:23 ` mikael at gcc dot gnu.org 2014-03-14 21:30 ` mikael at gcc dot gnu.org [this message] 2014-03-14 21:32 ` a.vogt at fulguritus dot com 2014-05-23 15:02 ` dominiq at lps dot ens.fr 2015-05-16 9:37 ` tkoenig at gcc dot gnu.org 2015-05-16 9:45 ` a.vogt at fulguritus 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=bug-60392-4-BV1WKrjvLU@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).