public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/28183] New: [4.0/4.1/4.2 regression] assembler error "FATAL: can't close x.o" on m68k with new binutils Date: Tue, 27 Jun 2006 21:24:00 -0000 [thread overview] Message-ID: <bug-28183-12387@http.gcc.gnu.org/bugzilla/> (raw) [ 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
next reply other threads:[~2006-06-27 21:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-27 21:24 tbm at cyrius dot com [this message] 2006-06-27 22:21 ` [Bug target/28183] " tbm at cyrius dot com 2006-06-28 4:50 ` tbm at cyrius dot com 2006-06-28 11:21 ` pinskia at gcc dot gnu dot org 2006-08-07 23:12 ` schwab at suse dot de 2006-08-07 23:13 ` schwab at suse dot de 2006-09-10 16:56 ` jsm28 at gcc dot gnu dot org 2006-09-20 22:24 ` mmitchel at gcc dot gnu dot org 2007-01-31 18:20 ` [Bug target/28183] [4.0/4.1/4.2/4.3 " zippel at linux-m68k dot org 2007-01-31 18:27 ` pinskia 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-28183-12387@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).