Re: [Tinycc-devel] Support arm hardfloat calling convention

2012-11-11 Thread Milutin Jovanović
Hi, Sorry for resurecting an old thread, but I do believe it is related. I am having some trouble passing tests on Raspberry Pi (armv6 vfp), specifically float point ones. Below pseude code is my understanding of compiler predefines. Did I understand their meaning correctly? #if !defined(TCC_ARM

[Tinycc-devel] My Raspberry reports it is an armv6l

2012-11-11 Thread Christian Jullien
Trying to compile, tcc on my rpi box, ./configure complains because my proc (armv6l) is not supported. $ uname -m armv6l < arm|armv4l|armv5tel|armv5tejl|armv6j|armv7a|armv7l) > arm|armv4l|armv5tel|armv5tejl|armv6j|armv6l|armv7a|armv7l) Fixed the issue. Also: $ more /proc/cpui

[Tinycc-devel] __aeabi_idivmod & __aeabi_idiv are undefined

2012-11-11 Thread Christian Jullien
Sorry if this is a known issue. I'm Still running tcc on my Rpi box. 1) Download latest mob 2) Patch configure to add armv6l 3) ./configure; make <- no error, 1 warning tccelf.c:1327:12: warning: 'tcc_add_support' defined but not used 4) make install So, expect for

Re: [Tinycc-devel] Support arm hardfloat calling convention

2012-11-11 Thread Thomas Preud'homme
Le dimanche 11 novembre 2012 17:14:45, Milutin Jovanović a écrit : > Hi, > > Sorry for resurecting an old thread, but I do believe it is related. I am > having some trouble passing tests on Raspberry Pi (armv6 vfp), specifically > float point ones. > > Below pseude code is my understanding of com

Re: [Tinycc-devel] My Raspberry reports it is an armv6l

2012-11-11 Thread Thomas Preud'homme
Le dimanche 11 novembre 2012 18:14:28, Christian Jullien a écrit : > Trying to compile, tcc on my rpi box, > > ./configure complains because my proc (armv6l) is not supported. > > > > $ uname -m > > armv6l > > > > < arm|armv4l|armv5tel|armv5tejl|armv6j|armv7a|armv7l) > > > arm|armv4l|armv5

Re: [Tinycc-devel] __aeabi_idivmod & __aeabi_idiv are undefined

2012-11-11 Thread Thomas Preud'homme
Le dimanche 11 novembre 2012 19:53:27, Christian Jullien a écrit : [SNIP] > > > I get > > tcc: error: undefined symbol '__aeabi_idiv' > > tcc: error: undefined symbol '__aeabi_idivmod' > [SNIP] > > Changing int to unsigned int results in: > > tcc: error: undefined symbol '__aeabi_uidiv'

Re: [Tinycc-devel] __aeabi_idivmod & __aeabi_idiv are undefined

2012-11-11 Thread Daniel Glöckner
On Sun, Nov 11, 2012 at 08:17:43PM +0100, Thomas Preud'homme wrote: > Le dimanche 11 novembre 2012 19:53:27, Christian Jullien a écrit : > > If tcc is expected to replace gcc, imho it should not use any gcc specific > > lib. > > yes indeed. It should support both modes. You are free to add these

Re: [Tinycc-devel] __aeabi_idivmod & __aeabi_idiv are undefined

2012-11-11 Thread Christian Jullien
Tcctok defines the following __aeabi_xxx functions: DEF(TOK_memcpy, "__aeabi_memcpy") DEF(TOK_memcpy4, "__aeabi_memcpy4") DEF(TOK_memcpy8, "__aeabi_memcpy8") DEF(TOK_memset, "__aeabi_memset") DEF(TOK___aeabi_ldivmod, "__aeabi_ldivmod") DEF(TOK___aeabi_uldivmod, "__aeab