public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "domob at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45776] Full implementation of variable definition contexts (and related checks) Date: Sat, 25 Sep 2010 16:49:00 -0000 [thread overview] Message-ID: <20100925164900.TeNKryOENkfzRubiFtdZBj9cnl5PqBWJksCK8MjdRZ4@z> (raw) In-Reply-To: <bug-45776-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45776 --- Comment #3 from Daniel Kraft <domob at gcc dot gnu.org> 2010-09-25 14:30:58 UTC --- This implemented all IO related checks (items 5-10), so only missing are now 14 and 15 which are the LOCK/UNLOCK related ones. These depend on implementation of locks in PR 18918, so I'm waiting for that now. -- Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
prev parent reply other threads:[~2010-09-25 14:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-24 8:06 [Bug 45776] (fortran) New: " domob at gcc dot gnu.org 2010-09-24 8:10 ` [Bug 45776] (fortran) " domob at gcc dot gnu.org 2010-09-25 16:40 ` [Bug fortran/45776] " domob at gcc dot gnu.org 2010-09-25 16:49 ` domob 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=20100925164900.TeNKryOENkfzRubiFtdZBj9cnl5PqBWJksCK8MjdRZ4@z \ --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).