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 libfortran/65234] Output descriptor (*(1E15.7)) not accepted
Date: Fri, 27 Feb 2015 12:24:00 -0000	[thread overview]
Message-ID: <bug-65234-4-533S4Mn7eI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65234-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-02-27
     Ever confirmed|0                           |1

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed.

> What for example if one wants to emit/read an even number of floats like
> with: '(*(2E15.7))'? 

I think this expectation is wrong, i.e., writing an array with an odd number of
elements will print the whole army as demonstrated by the following test

real :: a(11) = [(i,i=1,11)]
print '(*(2(E15.3)))', a
end

which gives at run time

      0.100E+01      0.200E+01      0.300E+01      0.400E+01      0.500E+01    
 0.600E+01      0.700E+01      0.800E+01      0.900E+01      0.100E+02     
0.110E+02


  parent reply	other threads:[~2015-02-27 11:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 12:19 [Bug libfortran/65234] New: " vehre at gcc dot gnu.org
2015-02-27 12:24 ` [Bug libfortran/65234] " vehre at gcc dot gnu.org
2015-02-27 12:24 ` dominiq at lps dot ens.fr [this message]
2015-02-27 20:33 ` jvdelisle at gcc dot gnu.org
2015-03-01  4:25 ` jvdelisle at gcc dot gnu.org
2015-04-12  7:49 ` dominiq at lps dot ens.fr
2015-04-21 18:23 ` jvdelisle at gcc dot gnu.org
2015-04-21 18:29 ` jvdelisle at gcc dot gnu.org
2015-04-21 18:29 ` 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-65234-4-533S4Mn7eI@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).