public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joe at confucius dot gnacademy dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/21432] gfortran does not support printing of namelists
Date: Sat, 07 May 2005 03:43:00 -0000	[thread overview]
Message-ID: <20050507034313.17003.qmail@sourceware.org> (raw)
In-Reply-To: <20050507015324.21432.joe@confucius.gnacademy.org>


------- Additional Comments From joe at confucius dot gnacademy dot org  2005-05-07 03:43 -------
Sorry for the spew.  The code is generated by a preprocessor and I didn't
realize how large it would end up.  

The bug is that gfortran apparently does not support printing of namelists.  I
don't know if this is in the fortran standard or not, but it is a very common
compiler extension, and it is one that is hugely difficult to work around.

I've loaded up a new file that compiles with ifort.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Another code sample that    |gfortran does not support
                   |gfortran dies on            |printing of namelists


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


  parent reply	other threads:[~2005-05-07  3:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-07  1:53 [Bug fortran/21432] New: Another code sample that gfortran dies on joe at confucius dot gnacademy dot org
2005-05-07  1:54 ` [Bug fortran/21432] " joe at confucius dot gnacademy dot org
2005-05-07  3:26 ` kargl at gcc dot gnu dot org
2005-05-07  3:43 ` joe at confucius dot gnacademy dot org [this message]
2005-05-07  3:45 ` [Bug fortran/21432] gfortran does not support printing of namelists joe at confucius dot gnacademy dot org
2005-05-07  4:02 ` kargl at gcc dot gnu dot org
2005-05-07  4:19 ` joe at confucius dot gnacademy dot org
2005-05-07 15:55 ` tobi at gcc dot gnu dot org
2005-05-17 13:35 ` tkoenig at gcc dot gnu dot org
2005-08-03 12:31 ` paulthomas2 at wanadoo dot fr
2005-08-14 16:16 ` cvs-commit at gcc dot gnu dot org
2005-08-14 18:45 ` cvs-commit at gcc dot gnu dot org
2005-08-14 19:30 ` pault at gcc dot gnu dot org
2005-08-14 21:43 ` cvs-commit at gcc dot gnu dot org
2005-08-14 21:46 ` cvs-commit at gcc dot gnu dot org
2005-08-23  1:54 ` pinskia at gcc dot gnu dot 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=20050507034313.17003.qmail@sourceware.org \
    --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).