[Raion]

So I came back around to this and am trying to fix multilib C/C++ for 4.9 with Dodoid. The SGUG binutils patches helped, but the code for them is godawful and breaks a ton of things so I'll probably advise what I did to fix if that goes well.

[Raion]

Getting back around to this (again), I plan to try working with as many compiler yoda types I can find in the community. Sick of sitting around doing basically nothing code-wise. life sucks but it won't get any better with a bad attitude.

[Raion]

# of expected passes 80630
# of unexpected failures 438
# of expected failures 144
# of unresolved testcases 22
# of unsupported tests 1558
/root/build-4.9/gcc/xgcc version 4.9.4 (GCC)


GCC 4.9.4 on IRIX 6.5.30. Better than I was expecting. Gonna repackage it sooner or later

[vishnu]

Much as I hate to violate the local TOS, I'll state yet again that MIPSPro 7.4.4, with a working license, is available as a free download from my website. But that said, MIPS assigned one of their programmers to the GCC team a couple of years ago, so GCC compiled programs run much better on MIPS processors than previously.

[Raion]

/var/tmp//ccwkhQtm.s: Assembler messages:
/var/tmp//ccwkhQtm.s:22: Error: Illegal operands `c.eq.s $fcc1,$f12,$f13'
/var/tmp//ccwkhQtm.s:26: Error: Opcode not supported on this processor: mips3 (mips3) `movt $2,$0,$fcc1'
/var/tmp//cch2VCVr.s: Assembler messages:
/var/tmp//cch2VCVr.s:22: Error: Illegal operands `c.eq.s $fcc1,$f12,$f13'
/var/tmp//cch2VCVr.s:26: Error: Opcode not supported on this processor: mips3 (mips3) `movt $2,$0,$fcc1'
make[3]: *** [../../../gcc-4.9.4/libgcc/config/t-hardfp:71: nesf2.o] Error 1
make[3]: *** Waiting for unfinished jobs....


WHAT THE FUCK DOES THIS SHIT MEAN?

Currently trying to figure out this error. Happens in zlib shit for some reason

[robespierre]

The assembler refused to translate instructions that do not exist in its target ISA.
MIPS III does not support conditional move instructions (movt) or floating-point condition codes beyond number 0 ($fcc1).
These instructions should not be generated when the architecture level is set to MIPS3.

[vishnu]

That's what a properly configured script is supposed to set up for you. Otherwise, you can write your own Makefile, and organize it to bypass anything that doesn't align with the most didactic features of whatever compiler you're using.

[Raion]

99% sure that was a compiler problem. But I'm not 100% sure

[vishnu]

When I come across these types of issues, I skip the makefile entirely and go into the source directory and start compiling object files from the command line, with all the compiler warnings turned on, with gcc that would be -Wall. Then, depending on the output, figure out if it's even worth trying to compile it, or send hatemail to the original programmer.

[Raion]

Unfortunately I can't do that with GCC that easily but I am currently chugging along through it.