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 16:20:00 -0000 [thread overview] Message-ID: <bug-49791-4-HyIf2aXQT8@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 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-07-20 16:16:43 UTC --- (In reply to comment #2) > Why are you calling this a workaround. It looks like it is fixing > a bug in the user's program. In an ideal world, all code would use only standard Fortran and fixing the code would be trivial. However, in a real world, we live with more or less common vendor extensions which are used by real programs, even if there is now a better standard-conform replacement. I am sure that version of namelist predates Fortran 90. If the bug reporter can, I think he should convert all the input files to the Fortran 90 syntax of namelists. However, one needs to be careful to not inadvertently to change the meaning (e.g. remove the wrong "(1)") and it might affect many files. > I'm also not sure why you call this a regression. That's simple: It worked before, now it stopped. As the vendor extension is very common - it works at least with PGI, Intel, g95, gfortran (before the 2010-10), Sun, Open64, Pathf95 and crayftn, it makes sense to regard this as supported vendor extension. (I am sure more compiler support it, but I don't have access to them.) A different example would be: &nml tag = string / which is only supported by ifort. All other compilers fail as "string" is not quoted. If gfortran had supported such a feature as only compiler or as one of very few compilers, I would agree that breaking it, would probably fall into the WONTFIX category.
next prev parent reply other threads:[~2011-07-20 16:20 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 ` [Bug libfortran/49791] [4.4/4.5/4.6/4.7 Regression] Formatted namelist reads fails with: Cannot match namelist object burnus at gcc dot gnu.org 2011-07-20 15:43 ` kargl at gcc dot gnu.org 2011-07-20 16:20 ` burnus at gcc dot gnu.org [this message] 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-HyIf2aXQT8@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).