[Bug target/28183] New: [4.0/4.1/4.2 regression] assembler error "FATAL: can't close x.o" on m68k with new binutils

["tbm at cyrius dot com" <gcc-bugzilla at gcc dot gnu dot org>]

[ forwarded from http://bugs.debian.org/375519 ]

We get the following assembler error when compiling the application cln.  The
error goes away when you drop -fPIC or when you use gcc 3.4.  Additionally, the
error does not show up with older releases of binutils.  While 2.16.91 20060413
produces the error, 2.16.91 20051117 works fine.

I'm not sure if this is a bug in binutils but given that gcc 3.4 works I'm
filing it as a gcc bug.  Andreas, since you're also involved in binutils, I
hope you know where to put the blame. ;-)

crest% g++-4.1 -fPIC -DPIC -c cl_MI.ii
crest% g++-4.1 -fPIC -DPIC -c -O2 cl_MI.ii
cl_MI.o: No error
/tmp/ccjCp4mS.s: Assembler messages:
/tmp/ccjCp4mS.s:18716: FATAL: can't close cl_MI.o
: No error
crest% g++-4.0 -fPIC -DPIC -c -O2 cl_MI.ii
cl_MI.o: No error
/tmp/ccreQBwI.s: Assembler messages:
/tmp/ccreQBwI.s:19590: FATAL: can't close cl_MI.o
: No error
crest% g++-3.4 -fPIC -DPIC -c -O2 cl_MI.ii
crest% as --version
GNU assembler 2.16.91 20060413 Debian GNU/Linux
Copyright 2005 Free Software Foundation, Inc.


-- 
           Summary: [4.0/4.1/4.2 regression] assembler error "FATAL: can't
                    close x.o" on m68k with new binutils
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tbm at cyrius dot com
 GCC build triplet: m68k-linux-gnu
GCC target triplet: m68k-linux-gnu


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