public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "deji_aking at yahoo dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code Date: Mon, 16 Apr 2007 22:06:00 -0000 [thread overview] Message-ID: <bug-31594-8911@http.gcc.gnu.org/bugzilla/> (raw) The attached fortran code (a smaller section cut and paste from original) was generated by a custom preprocessor. The code very much seems to be valid fortran 77, though its has some weird tab spacings; It compiles (and executes) fine with pgf90 and ifort-8.x. The compile time error is as below (same with gfortran-4.1.2, 4.2 and 4.3.0 trunck build); [armnlib@agape ~]$ gfortran -c -fcray-pointer adw_test.f adw_test.f:61.9: a(m,1) = p(m,1) * F_in (o1(m,1)-1) + p(m,2) * F_in (o1(m,1)) 1 Error: Unclassifiable statement at (1) adw_test.f:90.8: %(m,3) * F_in (o1(m,3)+1) + p(m,4) * F_in (o1(m,3)+2) 1 Error: Expected PARAMETER symbol in complex constant at (1) adw_test.f:94.8: %(m,3) * F_in (o3(m,3)+1) + p(m,4) * F_in (o3(m,3)+2) 1 Error: Expected PARAMETER symbol in complex constant at (1) -- Summary: gfortran failed to compiled a 'valid' code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: deji_aking at yahoo dot ca http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594
next reply other threads:[~2007-04-16 22:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-16 22:06 deji_aking at yahoo dot ca [this message] 2007-04-16 22:07 ` [Bug fortran/31594] " deji_aking at yahoo dot ca 2007-04-17 0:20 ` tobi at gcc dot gnu dot org 2007-04-17 6:13 ` steven at gcc dot gnu dot org 2007-04-17 11:14 ` tobi at gcc dot gnu dot org 2007-04-17 12:21 ` deji_aking at yahoo dot ca 2007-04-17 21:10 ` steven 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=bug-31594-8911@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).