FYI: large number of objc failures on i686-linux-gnu
H . J . Lu
hjl@lucon.org
Sun Jan 6 10:08:00 GMT 2002
On Sun, Jan 06, 2002 at 06:55:06PM +0100, Andreas Jaeger wrote:
> "H . J . Lu" <hjl@lucon.org> writes:
>
> > On Sun, Jan 06, 2002 at 06:05:51PM +0100, Andreas Jaeger wrote:
> >>
> >> I get with current CVS a large number of failures in objc:
> >>
> >> === objc Summary ===
> >>
> >> # of expected passes 570
> >> # of unexpected failures 236
> >> # of unresolved testcases 236
> >>
> >>
> >> Most of the failures (I didn't check all) are missing symbols:
> >>
> >> FAIL: objc/execute/accessing_ivars.m compilation, -O0
> >> UNRESOLVED: objc/execute/accessing_ivars.m execution, -O0
> >> Executing on host: /builds/gcc/gcc-3.1-devel/gcc/xgcc -B/builds/gcc/gcc-3.1-devel/gcc/ /cvs/gcc/gcc/testsuite/objc/execute/accessing_ivars.m -w -O1 -I/cvs/gcc/gcc/testsuite/../../libobjc -L/builds/gcc/gcc-3.1-devel/i686-pc-linux-gnu/libobjc/.libs -lobjc -lm -o /builds/gcc/gcc-3.1-devel/gcc/testsuite/accessing_ivars.x1 (timeout = 300)
> >> /opt/binutils/bin/ld: warning: type and size of dynamic symbol `__objc_class_name_Object' are not defined
> >> output is:
> >> /opt/binutils/bin/ld: warning: type and size of dynamic symbol `__objc_class_name_Object' are not defined
> >
> > That is a very old problem. See
> >
> > http://gcc.gnu.org/ml/gcc/2000-08/msg00153.html
> > http://gcc.gnu.org/ml/gcc/2000-11/msg00944.html
> >
>
> Strange, it seems to have worked at the beginning of december, see:
> http://gcc.gnu.org/ml/gcc-testresults/2001-12/msg00016.html
>
I don't think so.
http://gcc.gnu.org/ml/gcc-testresults/2001-12/msg00016.html
has
=== objc Summary ===
# of expected passes 209
# of unexpected failures 1
/builds/gcc/gcc-3.1-devel/gcc/xgcc version 3.1 20011201 (experimental)
http://gcc.gnu.org/ml/gcc-testresults/2002-01/msg00081.html
has
=== objc Summary ===
# of expected passes 568
# of unexpected failures 237
# of unresolved testcases 236
/export/build/gnu/gcc/build-i686-linux/gcc/xgcc version 3.1 20020105 (experimental)
There are more testes now.
> But that might have been just another bug ;-)
>
> I'd just like to point out that Objective C seems to be not ready for
> GCC 3.1 on i686-linux.
>
It may have been broken on more ELF targets.
H.J.
More information about the Gcc
mailing list