public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/31594]  New: gfortran failed to compiled a 'valid' code
@ 2007-04-16 22:06 deji_aking at yahoo dot ca
  2007-04-16 22:07 ` [Bug fortran/31594] " deji_aking at yahoo dot ca
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: deji_aking at yahoo dot ca @ 2007-04-16 22:06 UTC (permalink / raw)
  To: gcc-bugs

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
@ 2007-04-16 22:07 ` deji_aking at yahoo dot ca
  2007-04-17  0:20 ` tobi at gcc dot gnu dot org
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: deji_aking at yahoo dot ca @ 2007-04-16 22:07 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #1 from deji_aking at yahoo dot ca  2007-04-16 23:07 -------
Created an attachment (id=13374)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13374&action=view)
testcase (cut and paste from original)

I can provide the whole file if necessary


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
  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
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: tobi at gcc dot gnu dot org @ 2007-04-17  0:20 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #2 from tobi at gcc dot gnu dot org  2007-04-17 01:20 -------
Your lines are too wide, hoping that bugzilla will not mess up the formatting
I'll quote an example:
         1         2         3         4         5         6         7
123456789012345678901234567890123456789012345678901234567890123456789012345
          a(m,1) = p(m,1) * F_in  (o1(m,1)-1) + p(m,2) * F_in  (o1(m,1)) + 
     %p(m,3) * F_in  (o1(m,1)+1) + p(m,4) * F_in  (o1(m,1)+2)
                                                                        ^^
Per the standard, fixed form lines are 72 characters and everything beyond is
ignored, so the plus is not read.  The -ffixed-line-length option should solve
your problem.

Closing as INVALID.


-- 

tobi at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tobi at gcc dot gnu dot org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
  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
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: steven at gcc dot gnu dot org @ 2007-04-17  6:13 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #3 from steven at gcc dot gnu dot org  2007-04-17 07:12 -------
To the reporter:
Even though this is already (correctly) closed as INVALID, please let us know
if your code does compile and run correctly if you compile with the suggested
extra command line option, -ffixed-line-length.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
                   ` (2 preceding siblings ...)
  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
  5 siblings, 0 replies; 7+ messages in thread
From: tobi at gcc dot gnu dot org @ 2007-04-17 11:14 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #4 from tobi at gcc dot gnu dot org  2007-04-17 12:14 -------
(In reply to comment #3)
> To the reporter:
> Even though this is already (correctly) closed as INVALID, please let us know
> if your code does compile and run correctly if you compile with the suggested
> extra command line option, -ffixed-line-length.

Yes, sorry, I forgot to say that.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
                   ` (3 preceding siblings ...)
  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
  5 siblings, 0 replies; 7+ messages in thread
From: deji_aking at yahoo dot ca @ 2007-04-17 12:21 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #5 from deji_aking at yahoo dot ca  2007-04-17 13:21 -------
Yes adding compiling with -ffixed-line-length-80 solved the issue for me,
thanks to you both. I've noticed the original author of that code used tabs in
a couple of space he should have used spaces, the other compilers I tried with
probably sees the tab as a single separator while gfortran fleshed it out to 3
spaces. I've added -ffixed-line-length-80 to the Makefile to handle similar
other cases in the model.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug fortran/31594] gfortran failed to compiled a 'valid' code
  2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
                   ` (4 preceding siblings ...)
  2007-04-17 12:21 ` deji_aking at yahoo dot ca
@ 2007-04-17 21:10 ` steven at gcc dot gnu dot org
  5 siblings, 0 replies; 7+ messages in thread
From: steven at gcc dot gnu dot org @ 2007-04-17 21:10 UTC (permalink / raw)
  To: gcc-bugs



------- Comment #6 from steven at gcc dot gnu dot org  2007-04-17 22:09 -------
.


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |VERIFIED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31594


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2007-04-17 21:10 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-04-16 22:06 [Bug fortran/31594] New: gfortran failed to compiled a 'valid' code deji_aking at yahoo dot ca
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

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).