[vishnu]

I neglected to mention that turning on all the compiler warnings with Mipspro is the "fullwarn" command line option.

[Raion]

Unfortunately I don't think I can build GCC 4.9 with mips pro but I appreciate the sentiment here.

On an unrelated note I think you would be dismayed to learn that SGI decided instead of fixing certain types of code they have a pragma that literally shuts off certain warnings for pieces of code for the system. So just think about that every time LOL. They will literally turn their warnings off for sections of the code using the pragma control

[Raion]

So after I am finished finally figuring out a way to get through GCC building, I'm going to give people a bit of a lecture on why there's some shit going on with the SGUG compilers. This is not going to be me throwing shade, I'm going to provide samples and examples of the issue and if someone wants to point out the obvious and tell me that I'm an idiot about something that's okay.

As of right now my goal is to first get a working GCC and document the process, flags, provide config logs and a prepared distribution of source along with proper instructions.

What I'm about to say is not necessarily meant to minimize their contributions, but:

A side effect of cross compiling and not even doing a bootstrap has resulted in a lot of really weird nasty bugs that I've encountered some of which might be my fault/a result of me being less versed in this than i wish. However I have done the best I can to work through these problems and consulted with developers and stuff and everybody that I spoke to, when I share these problems, weren't very nice in their criticism.

I am hoping that this GCC build i am working on will be a lesson, and that the lesson can be carried over into GCC for SGUG.

If people wonder why I'm talking this way it's because I'm trying to specifically be very direct with my communication, but also not just be me throwing a bunch of explodes or whatever because I think that would not solve anything. Trust me there's been a lot of nasty swearing on my end from how things have been set up. Ideally, my GCC will replace:

The Onre builds of 4.7.4 and 8.2.0
Didbs (Daniel Hams/thinlysliced/silenceoftheass/everyonelovesp*nis, yes these are all his aliases) builds of GCC which similarly have some really odd design choices including that mips3 error that does not occur on anything else, this is being built on a tezro...
The 4.7.3 and 4.7.1 community builds hanging around.
neko_gcc; I will be updating my mirrors with a nekoware package sooner or later with an appropriate package for this.

This is the so-called great realignment of GCC on IRIX, I hope at least. Lol.

[vishnu]

Where I work, it's a job requirement to create warning-free code.

[Raion]

Ok, finally got somewhere:

=== gcc Summary ===

# of expected passes 76205
# of unexpected failures 235
# of expected failures 139
# of unresolved testcases 23
# of unsupported tests 1408
/root/build-4.8/gcc/xgcc version 4.8.5 (GCC)

[Raion]

https://pastebin.com/aiGtgpXR

First GCC with all relevant info. This ain't a replicable build. I'll have one sooner or later!

[Raion]

All right that compilers broken unfortunately.

Figured out my problem partially. I'm using a tezro to build, and Onre's GCC is mips3. As a result, it is trying to , I think, do invalid shit for mipsIV or vice versa. Not sure, but something's broken. Looks like I got to start over on another system. Yay (sarcasm)

[Raion]

Starting over with 4.7.1 from nekoware. Last time I had issues, but I'm gonna try again!

[vishnu]

Using gcc on an SGI is like swimming in dirty water. Oh I did NOT just say that! Yes I did...

[Raion]

It's like trying to pick the contaminants in a line of speed out of your nose after snorting it. There's a lot of blood and screaming.

(Not that I have experience with doing speed)