This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/16259] gcc pass unconditionaly "-many" to the assembler
- From: "jdubois at mc dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Jun 2004 15:48:36 -0000
- Subject: [Bug target/16259] gcc pass unconditionaly "-many" to the assembler
- References: <20040629100143.16259.jdubois@mc.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jdubois at mc dot com 2004-06-29 15:48 -------
(In reply to comment #4)
> See http://gcc.gnu.org/ml/gcc-patches/2004-05/msg01244.html
This is the patch that is applied (automatically) to GCC 3.4.0 in Dan kegel's
crosstool and I am fine with all of it except the last unconditional "-many"
that cause trouble to (at least) gas 2.14. BTW the "comment" in the applied
patch file is as follow:
<quote>
(I'm not so sure about the unconditional -many it sends to binutils;
that seems redundant?)
</quote>
It seems that gas 2.14 will reduce the number of valid instruction opcode to a
"common" subset when -many is passed to it even if -mppc is passed prior to it.
Therefore gas fails to interpret the mftbX opcodes.
If the answer is: use 2.15 because we know 2.14 has a bug, and 2.15 handles the
"-mppc -maltivec -many" correctly, I am fine with this (even if I will now have
to find out why 2.15 crashes on me :( ). But then we should try to check this
condition in the configure script and prevent gcc 3.4.0 (and later) to build
against 2.14 or prior.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16259