[Tinycc-devel] RE :Re: New test 73_arm64 hangs if ran on RPi

[Christian JULLIEN]

Quickly reading your test, it looks like it is a pure C code that should? compile and run on any backend.
If it is the case, it should be named differently than arm64 to better understand what it tests.

This new test may exhibit a bug in arm32. Please note it also fails on x86_64, yet without core dump.

Test: 73_arm64...
--- 73_arm64.expect    2015-02-26 08:58:44.251349733 +0100
+++ 73_arm64.output    2015-02-26 08:59:12.168245410 +0100


Tcc developpers, does this test work/fail on other backend? like x86?

Christian


> ----- message d'origine -----
> De : "Edmund Grimley Evans" <address@hidden>
> date jeu. 26/02/2015 08:52 (GMT +01:00)
> À : "address@hidden" <address@hidden>
> Objet : Re: [Tinycc-devel] New test 73_arm64 hangs if ran on RPi
>
> Christian Jullien <address@hidden>:
>
> > I've a cron that tests every update on my RPi.
> > Recent change introduced 73_arm64 that that hangs (at least) on RPi.
> > As test name seems to suggest, it looks it is for arm64 (not arm32).
> > 
> > Is this test really arm64 specific? If so, can you better check the tcc
> > backend that should run this test?
>
> It's arm64-specific in the sense that it tries things that I know are
> difficult on arm64, such as passing particular kinds of struct as
> argument and return value. However, it's supposed to be written in
> correct C and should work on every architecture. It's possible that it
> has exposed a bug in the arm back end as the calling convention for
> 32-bit ARM has some of the same complexities. I think I have a 32-bit
> ARM chroot somewhere I can test it on so I'll see if I can narrow it
> down a bit.
>
> Edmund
>
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel