public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vehre at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66578] [F2008] Invalid free on allocate(...,source=a(:)) in block Date: Thu, 09 Jul 2015 10:43:00 -0000 [thread overview] Message-ID: <bug-66578-4-vfpw43LljE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66578-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66578 vehre at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #19 from vehre at gcc dot gnu.org --- No objections so far. Closing as fixed with r225507.
prev parent reply other threads:[~2015-07-09 10:43 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-17 19:29 [Bug fortran/66578] New: " tkoenig at gcc dot gnu.org 2015-06-17 19:31 ` [Bug fortran/66578] " tkoenig at gcc dot gnu.org 2015-06-17 20:49 ` dominiq at lps dot ens.fr 2015-06-18 9:37 ` vehre at gcc dot gnu.org 2015-06-18 14:32 ` vehre at gcc dot gnu.org 2015-06-18 17:14 ` tkoenig at gcc dot gnu.org 2015-06-18 18:03 ` vehre at gcc dot gnu.org 2015-06-18 18:17 ` mikael at gcc dot gnu.org 2015-06-19 6:24 ` tkoenig at gcc dot gnu.org 2015-06-19 9:06 ` mikael at gcc dot gnu.org 2015-06-19 9:45 ` vehre at gcc dot gnu.org 2015-06-21 19:03 ` mikael at gcc dot gnu.org 2015-06-21 20:11 ` tkoenig at gcc dot gnu.org 2015-06-22 11:29 ` vehre at gcc dot gnu.org 2015-07-01 14:24 ` vehre at gcc dot gnu.org 2015-07-07 11:10 ` vehre at gcc dot gnu.org 2015-07-09 10:43 ` vehre at gcc dot gnu.org [this message]
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-66578-4-vfpw43LljE@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).