public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20779] ALLOCATEing the STAT variable not detected Date: Tue, 05 Apr 2005 23:11:00 -0000 [thread overview] Message-ID: <20050405231119.3772.qmail@sourceware.org> (raw) In-Reply-To: <20050405231017.20779.tobi@gcc.gnu.org> ------- Additional Comments From tobi at gcc dot gnu dot org 2005-04-05 23:11 ------- Same problem, more ocmplicated testcase: program fc012 ! Submitted by Walt Brainerd, The Fortran Company ! Windows XP ! Reading specs from /usr/local/bin/../lib/gcc-lib/i686-pc-cygwin/4.0.0//specs ! Configured with: /gcc/configure --enable-languages=c ! Thread model: single ! gcc version 4.0.0 20050129 (experimental) (g95!) Feb 22 2005 ! This program violates the following rule, identified below. integer, allocatable :: ALLOCS(:) ! The stat-variable must not be allocated within the same statement. ! This is not a constraint as in general it cannot be detected at ! compile-time (for example, the stat variable can be a subscripted variable ! whose subscript is determined at run time). allocate (ALLOCS(10),stat=ALLOCS(1)) deallocate (ALLOCS) print *, 'This program has one error' end program fc012 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20779
next prev parent reply other threads:[~2005-04-05 23:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-05 23:10 [Bug fortran/20779] New: " tobi at gcc dot gnu dot org 2005-04-05 23:11 ` tobi at gcc dot gnu dot org [this message] 2005-04-05 23:35 ` [Bug fortran/20779] " pinskia at gcc dot gnu dot org [not found] <bug-20779-8513@http.gcc.gnu.org/bugzilla/> 2006-09-05 19:39 ` pault at gcc dot gnu dot org 2006-09-17 17:40 ` patchapp at dberlin dot org 2006-10-03 21:40 ` pault at gcc dot gnu dot org 2006-10-03 21:41 ` pault 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=20050405231119.3772.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: 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).