This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/50095] New: -ffixed-REG and -ffixed-line-length-132 conflict
- From: "kargl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 Aug 2011 23:53:04 +0000
- Subject: [Bug lto/50095] New: -ffixed-REG and -ffixed-line-length-132 conflict
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50095
Bug #: 50095
Summary: -ffixed-REG and -ffixed-line-length-132 conflict
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: kargl@gcc.gnu.org
When using -flto and -ffixed-line-length-132 options with gfortran,
the lto driver interprets the gfortran option as the gcc option
-ffixed-REG where REG becomes line-length-132
troutmask:sgk[212] gfc4x -v
Using built-in specs.
COLLECT_GCC=/home/sgk/work/4x/bin/gfortran
COLLECT_LTO_WRAPPER=/usr/home/sgk/work/4x/bin/../libexec/gcc/x86_64-unknown-freebsd9.0/4.7.0/lto-wrapper
Target: x86_64-unknown-freebsd9.0
Configured with: ../gcc4x/configure --prefix=/home/sgk/work/4x
--enable-languages=c,fortran --disable-libmudflap --disable-bootstrap
Thread model: posix
gcc version 4.7.0 20110606 (experimental) (GCC)
troutmask:sgk[213] gfc4x -flto -o z -ffixed-line-length-0 h.f90
lto1: warning: unknown register name: line-length-0 [enabled by default]
lto1: warning: unknown register name: line-length-0 [enabled by default]