public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65541] [5 Regression] namelist regression
Date: Tue, 24 Mar 2015 19:49:00 -0000	[thread overview]
Message-ID: <bug-65541-4-1SratzmGse@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65541-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P4
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-03-24
            Summary|namelist regression         |[5 Regression] namelist
                   |                            |regression
     Ever confirmed|0                           |1

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This is due to revision r210934 (pr55117) from:

    * trans-io.c (nml_full_name, transfer_namelist_element): Insert
    a '+' rather then '%' to differentiate namelist variable names
    that are based on extended derived types.

this seems to have been done on purpose (I did not follow the discussion in the
PR).


  parent reply	other threads:[~2015-03-24 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 15:58 [Bug fortran/65541] New: " jwmwalrus at gmail dot com
2015-03-24 17:47 ` [Bug fortran/65541] " jvdelisle at gcc dot gnu.org
2015-03-24 19:49 ` dominiq at lps dot ens.fr [this message]
2015-03-25 14:26 ` [Bug fortran/65541] [5 Regression] " dominiq at lps dot ens.fr
2015-03-26  4:15 ` jvdelisle at gcc dot gnu.org
2015-04-01 14:25 ` jwmwalrus at gmail dot com
2015-04-01 16:16 ` jvdelisle at gcc dot gnu.org
2015-04-01 16:19 ` jvdelisle at gcc dot gnu.org
2015-04-06 14:40 ` jwmwalrus at gmail 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-65541-4-1SratzmGse@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).