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: Thu, 28 Jul 2011 05:48:00 -0000 [thread overview] Message-ID: <bug-49791-4-pANDUCxwvD@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 #18 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-07-28 05:47:39 UTC --- The issue of the original report (comment 0) is now fixed for GCC 4.4 to the trunk (4.7): The vendor extension extended array read of normal arrays in namelists works again. However, the following program still fails. It uses the same vendor extension but for array components of derived types. The program works with gfortran (before the 2010-10-xx commits), g95, sunf95, openf90, pathf95, pgf90 and crayftn. It does not work with ifort. TODO: Either one allows this test case (cf. comment 13) - or one decides that that part (extended array read for derived-type components) of the vendor extension won't be support anymore and updates the manual. ! { dg-do run } ! ! PR fortran/49791 ! type t integer :: array(4) end type t type(t) :: a namelist /nml/a a%array = [ 1,2,3,4] open(999, status='scratch') write(999,'(a)') '&nml a%array(1) = 99, 192 /' rewind(999) read(999, nml=nml) if (any (a%array /= [ 99, 192, 3, 4])) call abort () !write(*,nml=nml) end
next prev parent reply other threads:[~2011-07-28 5:48 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 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 [this message] 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-pANDUCxwvD@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).