public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "walt.brainerd at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65045] New: ICE Date: Thu, 12 Feb 2015 21:28:00 -0000 [thread overview] Message-ID: <bug-65045-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65045 Bug ID: 65045 Summary: ICE Product: gcc Version: 4.9.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: walt.brainerd at gmail dot com Created attachment 34744 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34744&action=edit Tried to use i as variable and construct name gfortran exit_if.f90 exit_if.f90:3.6: if (i>7.7) then 1 Error: Symbol at (1) is not appropriate for an expression exit_if.f90:5.7: else 1 Error: Unexpected ELSE statement at (1) exit_if.f90:6.6: i = 2.2 1 Error: 'i' at (1) is not a variable exit_if.f90:7.6: end if 1 Error: Expecting END BLOCK statement at (1) f951.exe: internal compiler error: Segmentation fault
next reply other threads:[~2015-02-12 21:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-12 21:28 walt.brainerd at gmail dot com [this message] 2015-02-13 11:08 ` [Bug fortran/65045] [4.8/4.9/5 Regression] ICE when using the same name for a block and a variable dominiq at lps dot ens.fr 2015-02-13 11:18 ` jakub at gcc dot gnu.org 2015-03-09 14:46 ` pault at gcc dot gnu.org 2015-03-12 15:59 ` burnus at gcc dot gnu.org 2015-06-23 8:23 ` [Bug fortran/65045] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:16 ` [Bug fortran/65045] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:37 ` jakub at gcc dot gnu.org 2015-10-27 17:30 ` dominiq at lps dot ens.fr 2015-10-27 17:43 ` paul.richard.thomas at gmail dot com
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-65045-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).