discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GCC 3.4 / libobjc / mframe issues


From: David Ayers
Subject: GCC 3.4 / libobjc / mframe issues
Date: Fri, 06 Aug 2004 15:03:49 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707

Hello everyone,

so here's my current scoop on the situation:

GCC encodes method signatures (objc_act.c:encode_method_prototype).  In
the FSF gcc < 3.4 these signatures included platform stack layout
information.  I believe this layout information was intended for our
mframe code.  Yet as the new Testing/nsmethodsignature test shows, gcc
and mframe don't always agree even for i686-pc-gnu-linux.  Even worse,
for some archs (hppa/linux) gcc < 3.4 could generate negative offsets in
the signature that certain parts of libobjc would bail out on with
objc_error->abort().  As of gcc 3.4 the signature does not have the
detailed layout information anymore and instead only indicates the sizes
of the types.

GNUstep hasn't been effected by this change (except for warnings)
because the libffi/ffcall code ignores the layout information provided
by the signature and only uses the types as libffi/ffcall figure out the
layout themselves.  -base's ./configure will bailout if both libffi and
ffcall are not available when DO is supposed to be supported, so the
fallback for mframe is actually currently not in use.

Now if there is any interest in reenabling mframe based DO, someone
should consider opening a bug report with gcc to reenable the layout
information in the signatures.  But beware that then libobjc will also
need to be able to support negative offsets and the mframe code should
match what gcc's layout (assuming gcc's layout information is
correct(ed)).  i.e. Testing/nsmethodsignature would need more tests and
they actually should be somehow converted into gcc's test suite which
seems like it would then need to contain the correct(ed) mframe code.

Instead, my suggestion is to s/NSWarnLog/NSDebugLog/ the warnings about
changed method signatures in -base before the release as these will pop
up sooner or later when more people mix gcc < 3.4 and 3.4+ code.  It's
already pestering folks who's mframe code doesn't match gcc signature
(e.g. hppa/linux, SPARC/Solaris).  (Actually I know of no platform where
it always matches, it just so happens to match most signatures on common
archs.  But I'd be interested in archs that actually pass the
Testing/nsmethodsignature test I committed this week.)

For platforms that have negative offsets (where libobjc will bailout),
I'd suggest updating to gcc 3.4.x.

After the release we should consider removing the mframe code and
signature manipulation, as any effort put into resurrecting mframe for a
given arch is probably better invested in libffi/ffcall support for that
arch.

I'll be gone for a week, but I'd appreciate if someone could update
those warnings before the release is made (and maybe remove some/all of
the deprecated functions at least in GSObjCRuntime).

For the curious, here is an example signature set (I chose one where gcc
< 3.4 and mframe have always disagreed):

-(MyLargeStruct)largeStruct_id:(id)_id
                          char:(char)_char
                         short:(short)_short
                           int:(int)_int
                          long:(long)_long
                         float:(float)_float
                        double:(double)_double
                   largeStruct:(MyLargeStruct)_lstr
                   smallStruct:(MySmallStruct)_sstr;

i686-pc-gnu-linux:
< 3.4
runtime:address@hidden:address@hidden
mframe :address@hidden:address@hidden
3.4
runtime:address@hidden:address@hidden
mframe :address@hidden:address@hidden

hppa-unknown-gnu-linux:
< 3.4
runtime:address@hidden:address@hidden
mframe :address@hidden:address@hidden
3.4
runtime:address@hidden:address@hidden
mframe :address@hidden:address@hidden(??=c}44

PS: I've replaced {_MyLargeStruct=dd}  with {??=dd} and
{_MySmallStruct=c} with {??=c} to insure that mail doesn't wrap.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]