public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle 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: Fri, 22 Jul 2011 13:51:00 -0000 [thread overview] Message-ID: <bug-49791-4-3M84zU7CZ2@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 #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-07-22 13:49:59 UTC --- After reviewing the listread.c and the test case I see that the touched should have nothing to do with this test case since the case has nothing to do with derived types. I think the flaw is that touched should be combined with BT_DERIVED if used here at all. This leads me to believe we are missing a parenthesis around BT_DERIVED and touched and they should be ANDed in some manner.. Tobias patch is probably safe, but it may be possible to dream up a test case with derived types that will fail. (There is probably one buried in my archives but finding it would be a chore)
next prev parent reply other threads:[~2011-07-22 13:51 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 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 [this message] 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-3M84zU7CZ2@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).