This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

fortran/9501: Warning from g77 -ffixed-line-length-132


>Number:         9501
>Category:       fortran
>Synopsis:       Warning from g77 -ffixed-line-length-132
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 29 17:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     scott snyder
>Release:        3.4 20030127 (experimental)
>Organization:
<organization of PR author (multiple lines)>
>Environment:
System: Linux karma 2.4.19-emp_2419p5a829i #1 Tue Sep 3 17:42:17 EST 2002 i686 unknown
Architecture: i686

	<machine, os, target, libraries (multiple lines)>
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure --prefix=/usr/local/gcc --enable-threads=posix --enable-long-long
>Description:

Compiling a .F source (thus requesting preprocessing) with the
-ffixed-line-length-132 option gives a bogus warning:

$ touch x.F
$ g77 -c -ffixed-line-length-132 x.F
cc1: warning: unknown register name: line-length-132
$

It looks like the fortran option is getting passed to the cc1 invocation
used for preprocessing:

[sss@karma test2]$ g77 -v -c -ffixed-line-length-132 x.F
Reading specs from /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.4/specs
Configured with: ../gcc/configure --prefix=/usr/local/gcc --enable-threads=posix --enable-long-long
Thread model: posix
gcc version 3.4 20030127 (experimental)
 /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.4/cc1 -E -traditional-cpp -D_LANGUAGE_FORTRAN -quiet -v -D__GNUC__=3 -D__GNUC_MINOR__=4 -D__GNUC_PATCHLEVEL__=0 x.F -ffixed-line-length-132 /tmp/ccK71Jts.f
cc1: warning: unknown register name: line-length-132
ignoring nonexistent directory "/usr/local/gcc/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /usr/local/gcc/include
 /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.4/include
 /usr/include
End of search list.
 /usr/local/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.4/f771 /tmp/ccK71Jts.f -quiet -dumpbase x.F -auxbase x -version -ffixed-line-length-132 -o /tmp/cc2zUtBN.s
GNU F77 version 3.4 20030127 (experimental) (i686-pc-linux-gnu)
	compiled by GNU C version 3.4 20030127 (experimental).
 as -V -Qy -o x.o /tmp/cc2zUtBN.s
GNU assembler version 2.13.90.0.4 (i686-pc-linux-gnu) using BFD version 2.13.90.0.4 20020814
$


>How-To-Repeat:

See above.

>Fix:
	<how to correct or work around the problem, if known (multiple lines)>
>Release-Note:
>Audit-Trail:
>Unformatted:


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]