public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uttamp at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/23661] New: 'print fmt' is unclassifiable statement in gfortran Date: Wed, 31 Aug 2005 19:42:00 -0000 [thread overview] Message-ID: <20050831193916.23661.uttamp@us.ibm.com> (raw) test case: $ cat print_fmt.f95 PROGRAM print_fmt_test IMPLICIT NONE character(len=5) :: fmt = "( a)" integer :: i print fmt, ("=", i=1, 2) END PROGRAM print_fmt_test $ gfortran -c print_fmt.f95 In file print_fmt.f95:5 print fmt, ("=", i=1, 2) 1 Error: Unclassifiable statement at (1) $ gfortran -v Using built-in specs. Target: powerpc64-linux Configured with: /home/gccbuild/gcc_mline_anoncvs/gcc/configure --prefix=/opt/gcc-nightly/mline-20050823 --build=powerpc64-linux --host=powerpc64-linux --target=powerpc64-linux --with-cpu=default32 --with-as=/opt/gcc-nightly/mline-20050823/bin/as --with-ld=/opt/gcc-nightly/mline-20050823/bin/ld --enable-threads=posix --enable-shared --enable-__cxa_atexit --enable-languages=c,c++,f95,java,objc,obj-c++ --enable-checking --with-mpfr=/opt/gcc-nightly/mline-20050823 Thread model: posix gcc version 4.1.0 20050823 (experimental) "print fmt" statement is part of fortran 95 standard. -- Summary: 'print fmt' is unclassifiable statement in gfortran Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: uttamp at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23661
next reply other threads:[~2005-08-31 19:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-31 19:42 uttamp at us dot ibm dot com [this message] 2005-08-31 19:51 ` [Bug fortran/23661] " pinskia at gcc dot gnu dot org 2005-08-31 23:11 ` tobi at gcc dot gnu dot org 2005-08-31 23:34 ` tobi at gcc dot gnu dot org 2005-09-01 12:10 ` tobi at gcc dot gnu dot org 2005-09-01 12:16 ` fxcoudert at gcc dot gnu dot org 2005-09-01 14:41 ` tobi at gcc dot gnu dot org 2005-09-04 12:09 ` cvs-commit at gcc dot gnu dot org 2005-09-04 12:26 ` cvs-commit at gcc dot gnu dot org 2005-09-04 12:29 ` tobi at gcc dot gnu dot org 2005-09-07 14:11 ` 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=20050831193916.23661.uttamp@us.ibm.com \ --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).