OSDev.org

There's a possible bug I wanted to point out with the GCC, but didn't think was important enough to create a new topic.

Foreword, I do have a rather odd toolchain layout. I'm using is Qt's i686-w64-mingw32 build and my Msys is located in the same directory as my GitHub installation.

But on to the actual issue, if you configure gcc-4.9.1 with the options It'll crash right towards the end of the build process for all-gcc with the error: After a strenuous google search, it appears no one else has had this bug before. It's probably just my own dumbassery for having such a weird toolchain setup.

Regardless, I'm starting to get fed up with the GCC. Having to wait an hour to two hours for a toolchain to build, only for it to crash near the end and having to start all over because I was missing a single option or something is just aggravating as hell. Plus I think it's kinda ridiculous that there are no 8086/i186/i286 backends. Trying to add your own backend or object file format to the bfd in binutils is pure masochism. I'm strongly considering writing my own compiler at this point.

DaemonR wrote:Regardless, I'm starting to get fed up with the GCC. ... Plus I think it's kinda ridiculous that there are no 8086/i186/i286 backends. Trying to add your own backend or object file format to the bfd in binutils is pure masochism. I'm strongly considering writing my own compiler at this point.

I did: Smaller C.

That's not a crash. That's a build error.

It likely happens because you do odd things. Stop doing that.

alexfru wrote:I did: Smaller C.

That's a frontend, not a backend. My bad, thought you were talking about modifying the GCC itself.

But yeah, the main reason I use this layout is to save time and space. Kinda running low on memory at the moment so I'm being conservative. There's no reason really to have 2 toolchains and 2 shell environments that have the same target platform anyway.

I'm thinking that it may just be a missing header or something, so I'm going to try to install MinGW's headers over the top of my Qt toolchain directory later and see if that fixes it.