Re: mframe.m and gcc 3.x

[Adam Fedor]

Nicola Pero wrote:
> 
> Apparently, the last missing bit in porting gnustep-base to run on newer
> compilers (gcc-3.x) is mframe.m.  Once gnustep-base is done, all gnustep
> should immediately work as well.
> 
[snip]
> I think it is a C problem - the code crashes the C compiler as well.
> Removing `inline' does not fix the problem.
> 
> I can't check the gcc bug database right now as their GNATS is down for a
> software setup problem, but I think there is already a gcc bug report for
> C showing a gcc crash on compiling a nested function returning a variable
> size struct (which is a simplification of our case), but it has never been
> fixed.  My idea is that when/if that was fixed, we could compile the whole
> mframe.m again.
> 

FYI: I compiled gcc 3.x (gcc-3_0-branch) on powerpc-unknown-linux-gnu
and then compiled all the GNUstep LaunchPad libraries.

I had to comment out pretty much all of mframe_decode_return (all the
nested functions). Also I fixed some "id" syntax error problems in
guile/ScriptKit.

running gnustep-tests, gnustep-base passed all (expected) tests:

                === Summary of all tests ===

# of expected passes       1971
# of expected failures     1
# of unexpected passes     0
# of unexpected failures   1
# of unresolved testcases  0
# of unsupported testcases 0
# of untested testcases    0
# of files abandoned       0

(The unexpected failure is normal. I haven't looked into why yet).

-- 
Adam Fedor, Digital Optics            | Fudd's law of opposition: Push
address@hidden  http://www.doc.com     | something hard enough, and it 
address@hidden  http://www.gnustep.org | will fall over.