public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "john.harper at vuw dot ac.nz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52101] New: Obsolescence warning for non-obs. feature character name*length Date: Fri, 03 Feb 2012 00:11:00 -0000 [thread overview] Message-ID: <bug-52101-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52101 Bug #: 52101 Summary: Obsolescence warning for non-obs. feature character name*length Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: john.harper@vuw.ac.nz Gfortran 4.6.2 -std=f95 says a declaration character name*length is obsolescent. IMHO it is not; the obsolescent form is character*length name. Gfortran 4.4.4 is correct on this matter. See below. rimu[~]$ cat obschar.f90 ! Character*length is obsolescent, not character name*length character greet*11 greet = 'Hello world' print *,greet end rimu[~]$ gfortran -v Using built-in specs. Target: i386-redhat-linux6E Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --disable-gnu-unique-object --enable-languages=c,c++,fortran --disable-libgcj --with-mpfr=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-i386-redhat-linux6E/mpfr-install/ --with-ppl=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-i386-redhat-linux6E/ppl-install --with-cloog=/builddir/build/BUILD/gcc-4.4.4-20100726/obj-i386-redhat-linux6E/cloog-install --with-tune=generic --with-arch=i586 --build=i386-redhat-linux6E Thread model: posix gcc version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC) rimu[~]$ gfortran -std=f95 obschar.f90 rimu[~]$ ./a.out Hello world rimu[~]$ /tmp/gf/bin/gfortran -v Using built-in specs. COLLECT_GCC=/tmp/gf/bin/gfortran Target: i686-pc-linux-gnu Configured with: /tmp/gcc-4.6.2/configure --prefix=/tmp/gf --enable-languages=c,c++,fortran --disable-libada --with-gmp=/home/harperj1 --with-mpfr-include=/home/harperj1/mpfr-3.0.0 --with-mpfr-lib=/home/harperj1/mpfr-3.0.0/.libs --with-mpc=/home/harperj1/mpc-0.9 Thread model: posix gcc version 4.6.2 (GCC) rimu[~]$ /tmp/gf/bin/gfortran -std=f95 obschar.f90 obschar.f90:2.18: character greet*11 1 Warning: Obsolescent feature: Old-style character length at (1) rimu[~]$
next reply other threads:[~2012-02-03 0:11 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-03 0:11 john.harper at vuw dot ac.nz [this message] 2012-02-03 7:22 ` [Bug fortran/52101] " burnus at gcc dot gnu.org 2012-02-03 7:31 ` burnus at gcc dot gnu.org 2012-02-03 20:51 ` John.Harper at msor dot vuw.ac.nz 2012-02-03 21:17 ` kargl at gcc dot gnu.org 2012-02-03 22:48 ` sgk at troutmask dot apl.washington.edu 2012-02-04 0:01 ` sgk at troutmask dot apl.washington.edu 2012-02-05 9:59 ` burnus at gcc dot gnu.org 2012-02-05 18:01 ` sgk at troutmask dot apl.washington.edu 2012-02-05 18:12 ` burnus at gcc dot gnu.org 2012-07-16 19:38 ` burnus at gcc dot gnu.org 2012-07-17 9:40 ` burnus at gcc dot gnu.org 2012-07-17 11:28 ` burnus 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-52101-4@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).