public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/16404] New: [gfortran] should reject invalid code with -pedantic -std=f95 ? (x8) Date: Wed, 07 Jul 2004 09:33:00 -0000 [thread overview] Message-ID: <20040707093303.16404.jv244@cam.ac.uk> (raw) following programs should be rejected as invalid, either as a default, or certainly with the above options gcc version 3.5.0 20040628 (experimental) ! test 1 DO I=1,5 I=1 ENDDO DO I=1,5 READ(5,*) I ENDDO END ! test 2 COMMON /BLOCKA/ A,B,C COMMON /BLOCKB/ D,E,F EQUIVALENCE(B,E) END ! test 3 REAL :: A REAL, TARGET :: B EQUIVALENCE(A,B) END ! test 4 write(6,*) ,2 END ! test 5 PROGRAM END ! test 6 MODULE TEST PRIVATE TYPE info_type INTEGER :: value END TYPE info_type TYPE all_type TYPE(info_type) :: info END TYPE PUBLIC :: all_type END MODULE END ! test 7 RETURN END ! test 8 TYPE data_type TYPE(data_type), POINTER :: next=>NULL() INTEGER :: i=0 END TYPE data_type TYPE (data_type) :: A write(6,*) A END -- Summary: [gfortran] should reject invalid code with -pedantic - std=f95 ? (x8) Product: gcc Version: 3.5.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16404
next reply other threads:[~2004-07-07 9:33 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-07 9:33 jv244 at cam dot ac dot uk [this message] 2004-07-11 12:43 ` [Bug fortran/16404] " tobi at gcc dot gnu dot org 2004-07-11 13:35 ` [Bug fortran/16404] " cvs-commit at gcc dot gnu dot org 2004-07-11 13:49 ` tobi at gcc dot gnu dot org 2004-07-11 13:54 ` tobi at gcc dot gnu dot org 2004-07-11 14:16 ` cvs-commit at gcc dot gnu dot org 2004-07-11 14:17 ` tobi at gcc dot gnu dot org 2004-07-11 23:22 ` giovannibajo at libero dot it 2004-07-11 23:40 ` tobi at gcc dot gnu dot org 2004-07-13 21:48 ` tobi at gcc dot gnu dot org 2004-07-14 7:53 ` jv244 at cam dot ac dot uk 2004-07-16 0:39 ` cvs-commit at gcc dot gnu dot org 2004-07-16 0:41 ` tobi at gcc dot gnu dot org 2004-07-16 0:57 ` cvs-commit at gcc dot gnu dot org 2004-09-01 14:36 ` tobi at gcc dot gnu dot org 2004-09-01 21:07 ` cvs-commit at gcc dot gnu dot org 2005-03-13 0:05 ` tobi at gcc dot gnu dot org 2005-06-18 21:52 ` fxcoudert at gcc dot gnu dot org 2005-09-07 16:09 ` pault at gcc dot gnu dot org 2005-09-26 19:28 ` pault at gcc dot gnu dot org 2005-10-01 7:40 ` cvs-commit at gcc dot gnu dot org 2005-10-01 15:58 ` 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=20040707093303.16404.jv244@cam.ac.uk \ --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).