Re: [Tinycc-devel] Weird bitfield size handling, discrepancy with gcc

[Armin Steinhoff]

avih schrieb:



So it seems that gcc-mingw (6.2.0 from msys2, or 4.9.4 from MXE cross 
build on linux) is neither fully compatible with msvc nor with gcc-linux.
"Not fully compatible" means "not fully binary compatible". Alignments 
of structs are also different between different gcc versions!

Weired dreams ?

--Armin
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] How to debug code in memory

[Armin Steinhoff]

Hi,

I would only JIT compile already tested code ... the other way around 
would be overkill.


Alex Rozenman schrieb:

Hello,

We're using dynamic compilation into memory (TCC_OUTPUT_MEMORY).
Is there any possibility to load the generated stabs info into GDB 
debugging the main process ?
I looked into "add-symbol-file-from-memory" gdb command, but is there 
any convenient way to generate the ELF image in memory for this reason?


--
Best regards,
Alex Rozenman (rozen...@gmail.com ).


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] Fastest TCC version

[Armin Steinhoff]

Hi,

that's what we do with DACHSview++ :

we build our C applications as a small main module and a bunch of
submodules. We compile and place the submodule objects in a shared
object (DLL) and
JIT compile the small main module and link it dynamically against the
shared lib of the sub modules.

IMHO ... that's the best way to run/import big applications with the JIT
compiler.

Regards

--Armin

http://www.steinhoff-automation.com/DACHSview-SDL_E.pdf

Sherjil Ozair wrote:
 Thanks for the reply Daniel.

 Yes, I know. Asking for faster compile-time is strange, but my
 application is also as strange. I'm generating lots of programs
 dynamically, and then running them, and I need to do this for millions
 of programs. The programs however are very simple, and do not take
 advantage of any obscure C features. Thus, what I want is, some
 compiler which is extremely fast compile-time, even if it implements
 only a few features of the language. Any suggestions?

 Thanks,
 Sherjil


 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] libtcc1 again --- on ARMv7

[Armin Steinhoff]

Thomas Preud'homme wrote:
 Le mercredi 22 mai 2013 15:25:26, Armin Steinhoff a écrit :
 Hi All,

 I have ported tcc to the BeagleBone running QNX 6.5.

 Starting tcc-arm w/o parameters shows the expected help informations.

 The command tcc-arm -c ex5.c works ... it creates ex5.o

 Linking the executable with tcc-arm  -o x  ex5.o  produced:

 tcc: error: file 'crt1.o' not found
 tcc: error: file 'crti.o' not found
 tcc: error: file '/usr/lib/tcc/libtcc1.a' not found
 tcc: error: file 'crtn.o' not found

 Why is the linking process looking for '/usr/lib/tcc/libtcc1.a'  ??

 Do we need the run time environment for ARM ??
 Yes, for integer division for instance.

Seems not to be the case.
I'm using only the JIT feature for generation code in memory ... so I
defined in config.h the macro WITHOUT_LIBTCC and all is working for our
real-time soft PLC :)

libttc1 must only be used if you are going to create application
binaries ...

Regards

--Armin


 Regards

 --Armin
 Best regards,

 Thomas


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

[Tinycc-devel] libtcc1 again --- on ARMv7

[Armin Steinhoff]

Hi All,

I have ported tcc to the BeagleBone running QNX 6.5.

Starting tcc-arm w/o parameters shows the expected help informations.

The command tcc-arm -c ex5.c works ... it creates ex5.o

Linking the executable with tcc-arm  -o x  ex5.o  produced:

tcc: error: file 'crt1.o' not found
tcc: error: file 'crti.o' not found
tcc: error: file '/usr/lib/tcc/libtcc1.a' not found
tcc: error: file 'crtn.o' not found

Why is the linking process looking for '/usr/lib/tcc/libtcc1.a'  ??

Do we need the run time environment for ARM ??

Regards

--Armin





___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] Do we want a BSD license for tinycc?

[Armin Steinhoff]

Daniel Glöckner wrote:
 Hi,

 On Tue, Apr 30, 2013 at 09:14:58PM +0200, Marc Andre Tanner wrote:
 The fear of proprietary forks seems
 unfounded because there is already a mature BSD licensed C compiler
 (clang) available for people to base their work on.
 Let's see..
 $ size /opt/llvm/bin/clang
text  data bss dec hex filename
 38999778  1193992   54640 40248410266245a /opt/llvm/bin/clang

 I think TinyCC might be preferred by some people who just need a
 small scripting engine.

TinyCC ist the only compiler which provides JIT compiling for ARM

--Armin


   Daniel

 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel



___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] Do we want a BSD license for tinycc? / JIT

[Armin Steinhoff]

KHMan wrote:
 On 5/1/2013 7:10 PM, Armin Steinhoff wrote:
 Daniel Glöckner wrote:
 On Tue, Apr 30, 2013 at 09:14:58PM +0200, Marc Andre Tanner wrote:
 The fear of proprietary forks seems
 unfounded because there is already a mature BSD licensed C compiler
 (clang) available for people to base their work on.
 Let's see..
 $ size /opt/llvm/bin/clang
 text   databssdechexfilename
 389997781193992  5464040248410266245a   
 /opt/llvm/bin/clang

 I think TinyCC might be preferred by some people who just need a
 small scripting engine.

 TinyCC ist the only compiler which provides JIT compiling for ARM

 http://luajit.org/luajit.html
 http://luajit.org/performance_arm.html

Interesting !  Thanks !

--Armin



___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] ARM code generator / ARM tiny C compiler

[Armin Steinhoff]

Guillaume,

libtcc1.c doesn't compile for ARMv7 :)

--Armin



ggasnie...@free.fr wrote:
 Could supported more ARM architecture and instructions set be of interest ?
 I'd like to work on it on my free time (long-term roadmap).

 Guillaume

 - Mail original -
 De: Daniel Glöckner daniel...@gmx.net
 À: tinycc-devel@nongnu.org
 Envoyé: Mercredi 24 Avril 2013 23:54:49
 Objet: Re: [Tinycc-devel] ARM code generator / ARM tiny C compiler

 On Wed, Apr 24, 2013 at 10:15:29PM +0200, ggasnie...@free.fr wrote:
 So where could I find the supported ARM architecture
 The generated code should be compatible with ARMv4.
 Floating point hardware or emulator (either FPA or VFP) is a must.

 and what is the roadmap for it ?
 There is no central roadmap.

   Daniel

 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel

 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

[Tinycc-devel] libtcc1 supported for ARMv7 ?

[Armin Steinhoff]

Hello,

I'm trying to use the JIT capabilitiy of TCC for an ARMv7 environment 
(Beaglebone / QNX6 ..) but the libtcc1 can't be recompiled for ARM CPUs.

Are there any plans to support the JIT features for ARM CPUs ?

Regards

--Armin







___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] libtcc1 supported for ARMv7 ?

[Armin Steinhoff]

Stephan,

I have ported TCC to QNX6.5 running on a Beaglebone ... it will be
available soon at the Sourceforge project openqnx.
What I additionally need are the JIT features of TCC ...

--Armin



Stephan Beal wrote:

 On Wed, Apr 24, 2013 at 12:25 PM, Armin Steinhoff ar...@steinhoff.de
 mailto:ar...@steinhoff.de wrote:

 I'm trying to use the JIT capabilitiy of TCC for an ARMv7 environment
 (Beaglebone / QNX6 ..) but the libtcc1 can't be recompiled for ARM
 CPUs.


 There is at least 1 port of tcc running on ARM here:

 https://play.google.com/store/apps/details?id=com.n0n3m4.droidc

 -- 
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] libtcc1 supported for ARMv7 ?

[Armin Steinhoff]

Daniel,

thanks !  I don't know why a got the idea to use libtcc1 for the JIT
features :)

The next version of DACHSview for ARMv7 will use the JIT features
of TCC:
http://www.the-better-idea.com/res/DACHSview/dachsview_cc.jpg

--Armin

Daniel Glöckner wrote:
 Hi,

 On Wed, Apr 24, 2013 at 12:25:07PM +0200, Armin Steinhoff wrote:
 I'm trying to use the JIT capabilitiy of TCC for an ARMv7 environment 
 (Beaglebone / QNX6 ..) but the libtcc1 can't be recompiled for ARM CPUs.
 libtcc1 doesn't compile for ARM.
 ARM users shoud use libgcc.a/libgcc_s.so.1.

   Daniel 

 ___
 Tinycc-devel mailing list
 Tinycc-devel@nongnu.org
 https://lists.nongnu.org/mailman/listinfo/tinycc-devel



___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel