I'll try to pull the code which i was using when i released r33 here. This one was working flawlessly. If that code compiles with devkitpro r35 (which is GCC v8.3.0) then i think there is something else very odd.
I have to try some different approaches. I'm currently working on that - using every free minute i have available at the time.
So Wii-DOOM r33 was somewhat back in 2015.
As i said: i've made some more changes and additions since r33. These changes did compile with devkitpro r27 (GCC v4.8.2) fine and they were working without any problems so far (on LINUX). Now with devkitpro r35 (GCC v8.3.0) it compiles but hangs at initialization. devkitpro r27 compiles but has a performance related problem (compiled under Windows using CodeWarrior which only links to the tools). Even using the exact same libraries from back the day won't help for the current state of the project. So we rather test old code and look at the changes... I hope that won't take too much time. I just wanna see these things running once again...
EDIT:
So it turns out: Freshly pulled source code of Wii-DOOM R33 from the day back at March, 29th 2015 compiles under devkitpro r27 with GCC v4.8.2 and the libraries of that time. Compiled under Windows using CodeWarrior - but with "some" errors - easy to fix anyway. It runs perfectly... no performance dropping. Runs on the NDEV. No warning or error regarding ".bss"-section.
Next step: compiling the exact same stuff using devkitpro r35 tools (GCC v8.3.0) and it's CRT binaries with freshly compiled libraries. Let's see what happens...
EDIT #2:
Compiled R33 under devkitpro r35 with GCC v8.3.0 and all libraries of that time compiled using the same tools. So everything is very fresh. Linked against MetroTRK. Runs on the NDEV. No performance related issues. Debugger SEEMS to be working (it actually IS currently executing while i'm running a game). Though, the game will hang - music playing right after 2 minutes. This is no debugger related thing as i then tried to compile libOGC against NON-MetroTRK-Integration. So... switch back to devkitpro r27 once again (incl. libraries) and try there...
Things i realized first compared between GCC v4.8.2 of devkitpro r27 and GCC v8.3.0 of devkitpro r35:
GCC v4.8.2 of devkitpro r27 throws ONLY 13 warnings of which 4 are of interest. The other ones are just empty text messages pointing to the previous warning.
GCC v8.3.0 of devkitpro r35 throws OVER !!!240!!! warnings. ---> SERIOUSLY?!
If this is a devkitpro related thing and caused by Wintermute's change to the variables then i will most likely NOT change my code because of his own change to the tools. If i would do that then it's only a matter of time until Wintermute changes one more thing and you have to change your own stuff then once again. That's not i wanna go through as i wouldn't only have to change MY code. I would also have to change the code of all the libraries required to compile these ports - which are like 18 libraries in a row btw..
EDIT #3:
So it turns out that the game doesn't hang when using the old stuff of the days when i compiled R33 of Wii-DOOM which means that it looks like we have to use devkitpro r27 with GCC v4.8.2. This one won't let the debugger run ATM. I don't know the reason for that so i think i have to compile 2 ELF's (one of devkitpro r27 and one of devkitpro r35) and compare them using IDA.
Anyway i forgot to say: THANKS WINTERMUTE!!