FrontendObjC/nonfragile-ivar.m fails on x86-32 linux

[llvmbot]

Bugzilla Link	2286
Resolution	FIXED
Resolved on	May 06, 2008 18:56
Version	unspecified
OS	Linux
Reporter	LLVM Bugzilla Contributor
CC	@isanbard

Extended Description

It looks like this test assumes a 64 bit compiler:

while running: llvm-gcc -emit-llvm -x objective-c -c test/FrontendObjC/nonfragile-ivar.m -o /dev/null -m64
test/FrontendObjC/nonfragile-ivar.m:1: sorry, unimplemented: 64-bit mode not compiled in
test/FrontendObjC/nonfragile-ivar.m:16: error: synthesized property 'whatever' must either be named the same as a compatible ivar or must explicitly name an ivar

[lattner]

You have objc support but no 64-bit support?

[llvmbot]

You have objc support but no 64-bit support?

Exactly. This is what you get when you add
objc to --enable-languages= on 32 bit linux.
In fact objc doesn't even build on 64 bit linux.

[lattner]

Does the objc front-end have any glimmer of hope of working with a non-apple target?

[llvmbot]

Does the objc front-end have any glimmer of hope of working with a non-apple
target?

Is there any reason why it shouldn't? Up to know all the tests in the
LLVM testsuite were passing for objc on linux.

[llvmbot]

Also, won't there be the same problem on 32 bit Apple platforms?

[lattner]

Sorry, to update this:

Objc and 32-bit and 64-bit use completely different ObjC ABIs, which is why this requires -m64. Linux doesn't use this ABI anywhere. The 'proper fix' is to only attempt this test on apple platforms. I don't know if there is a good way to do that though. Maybe xfail on everything but darwin? All darwin builds support 32 and 64-bit.

[lattner]

...Objc on 32-bit and 64-bit...

[isanbard]

Fixed:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080505/062087.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080505/062088.html