public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/49791] [4.4/4.5/4.6/4.7 Regression] Formatted namelist reads fails with: Cannot match namelist object
Date: Wed, 20 Jul 2011 09:31:00 -0000	[thread overview]
Message-ID: <bug-49791-4-wochofJIM0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49791-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49791

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |wrong-code
   Last reconfirmed|                            |2011.07.20 09:30:41
                 CC|                            |burnus at gcc dot gnu.org,
                   |                            |jvdelisle at gcc dot
                   |                            |gnu.org
     Ever Confirmed|0                           |1
            Summary|[4.6 Regression] Formatted  |[4.4/4.5/4.6/4.7
                   |namelist reads of arrays    |Regression] Formatted
                   |don't work                  |namelist reads fails with:
                   |                            |Cannot match namelist
                   |                            |object
   Target Milestone|---                         |4.4.7

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-07-20 09:30:41 UTC ---
CONFIRMED.

 * * *

Note: The format is not standard conform. Issues: "$" vs "&", "$end" vs "/".
However, the real problem is:
 xpos(1)= 0.00, 0.10, 0.20, 0.30, 0.40,
instead of (working)
 xpos(1:5)= 0.00, 0.10, 0.20, 0.30, 0.40,
or
 xpos= 0.00, 0.10, 0.20, 0.30, 0.40,
or
 xpos(:)= 0.00, 0.10, 0.20, 0.30, 0.40,
or
 xpos(1:)= 0.00, 0.10, 0.20, 0.30, 0.40,
or ...

Thus, the workaround is to fix the array bounds in the namelist file.

Note: The program works with ifort, g95, pathf95, openf95, pgf90; it fails with
the pedantic NAG - and (this PR) with the current gfortran versions.

 * * *

Working: (4.6 trunk) 2010-09-28-r164677
             gcc-4.5-2010-07-23-r162436
Failing:
         4.7 trunk: current, 2011-05-10, 2011-05-28-r174379
              gcc-4.5-x86_64-2010-11-13-r166693

Combining the 4.6/4.7 and the 4.5 data, I think the following patch is the
culprit. As it has been back-ported to 4.4/4.5, I have now adapted the summary.
When we know how obvious the patch is, we can still adjust the target milestone
- currently it is 4.4.7.


Author: jvdelisle
Date: Tue Oct 26 19:05:08 2010
New Revision: 165979

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=165979
Log:
2010-10-26  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

    PR libgfortran/46010
    * io/list_read.c (nml_parse_qualifier): Add additional conditions for
    setting the end index for loop specification. Fix some whitespace.
    * io/write.c (write_default_char4): Const-ify the source argument.

Modified:
    trunk/libgfortran/ChangeLog
    trunk/libgfortran/io/list_read.c
    trunk/libgfortran/io/write.c


  reply	other threads:[~2011-07-20  9:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  8:05 [Bug libfortran/49791] New: [4.6 Regression] Formatted namelist reads of arrays don't work quantum.analyst at gmail dot com
2011-07-20  9:31 ` burnus at gcc dot gnu.org [this message]
2011-07-20 15:43 ` [Bug libfortran/49791] [4.4/4.5/4.6/4.7 Regression] Formatted namelist reads fails with: Cannot match namelist object kargl at gcc dot gnu.org
2011-07-20 16:20 ` burnus at gcc dot gnu.org
2011-07-20 17:16 ` sgk at troutmask dot apl.washington.edu
2011-07-20 17:25 ` burnus at gcc dot gnu.org
2011-07-20 21:09 ` quantum.analyst at gmail dot com
2011-07-20 21:23 ` sgk at troutmask dot apl.washington.edu
2011-07-20 21:55 ` burnus at gcc dot gnu.org
2011-07-21 18:33 ` jvdelisle at gcc dot gnu.org
2011-07-22  1:28 ` jvdelisle at gcc dot gnu.org
2011-07-22 13:51 ` jvdelisle at gcc dot gnu.org
2011-07-22 22:45 ` burnus at gcc dot gnu.org
2011-07-23 10:27 ` burnus at gcc dot gnu.org
2011-07-23 15:26 ` jvdelisle at gcc dot gnu.org
2011-07-27 17:46 ` burnus at gcc dot gnu.org
2011-07-27 21:35 ` burnus at gcc dot gnu.org
2011-07-28  5:40 ` burnus at gcc dot gnu.org
2011-07-28  5:48 ` burnus at gcc dot gnu.org
2011-08-01 14:08 ` rguenth at gcc dot gnu.org
2012-02-05 23:01 ` burnus at gcc dot gnu.org
2012-02-06 22:19 ` burnus at gcc dot gnu.org
2012-03-13 14:24 ` [Bug libfortran/49791] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 14:04 ` [Bug libfortran/49791] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-07-02 14:05 ` orion at cora dot nwra.com
2013-01-02 17:18 ` jvdelisle at gcc dot gnu.org
2013-03-30  3:18 ` [Bug libfortran/49791] [4.6/4.7/4.8/4.9 " jvdelisle at gcc dot gnu.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-49791-4-wochofJIM0@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).