public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38839] BIND(C): Allow non-digit/underscore/alphabetic binding names
Date: Sun, 08 Jun 2014 22:37:00 -0000	[thread overview]
Message-ID: <bug-38839-4-tnp2yLUypb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38839-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38839

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |fxcoudert at gcc dot gnu.org
           Assignee|unassigned at gcc dot gnu.org      |fxcoudert at gcc dot gnu.org

--- Comment #5 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Should be fixed at the same time as this patch here:
https://gcc.gnu.org/ml/fortran/2014-06/msg00090.html , which reworks the
parsing of binding labels. I intend to find what the consensus is on this
issue, incorporate it into the patch, and close this.


       reply	other threads:[~2014-06-08 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-38839-4@http.gcc.gnu.org/bugzilla/>
2014-06-08 22:37 ` fxcoudert at gcc dot gnu.org [this message]
2014-06-29 14:15 ` fxcoudert at gcc dot gnu.org
2014-06-29 14:16 ` fxcoudert at gcc dot gnu.org
2009-01-14 15:37 [Bug fortran/38839] New: " burnus at gcc dot gnu dot org
2009-01-14 16:01 ` [Bug fortran/38839] " burnus at gcc dot gnu dot org
2009-01-14 16:09 ` burnus at gcc dot gnu dot org
2009-03-29  8:46 ` fxcoudert at gcc dot gnu dot org
2009-12-10 19:11 ` dfranke at gcc dot gnu dot org
2009-12-10 19:52 ` burnus 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-38839-4-tnp2yLUypb@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: link
Be 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).