Re: [Tinycc-devel] Segmentation Faults and test failures on ARM (Raspbian/Raspberry Pi)

[Thomas Preud'homme]

Thomas Preud'homme <address@hidden> wrote:

>Jerry Reed <address@hidden> wrote:
>
>>Thank you so much for all your work, Thomas.
>>
>>On the BeagleBone briefly.  When I configure with
>>
>>./configure
>>
>>Then the tests fail like this:
>>
>>Test: 11_precedence...
>>tcc: error: undefined symbol '__aeabi_idiv'
>
>We'll work on this after the release.
>
>>make[1]: *** [11_precedence.test] Error 255
>>make[1]: Leaving directory `/home/root/tinycc/tests2'
>>make: *** [test] Error 2
>>
>>An error I remember seeing before.  So I rebuilt with
>>
>>./configure --with-libgcc
>>
>>Later tests spew lots of diff's related to math/floating point, but I
>>haven't seen a Segmentation fault in 30 runs or so on the BeagleBone. 
>>I'll
>>leave the test looping, but it does seem that the build would have Seg
>>faulted on the Pi by now.
>>
>>Building on the Pi with-libgcc still gives Segmentation fault however,
>>so
>>perhaps the chip/environment on the Pi makes the problem worse either
>>with
>>libtcc or with libgcc?
>
>I have a fix for the random segfaults. However I'll probably only push
>tomorrow as I didn't manage to connect to the wifi with my laptop so
>far.

I managed to do a quick push. Please try extensively. I'll see for the header 
issue on the raspbian as soon as I have a better connectivity.

Cheers.

Thomas