[Tinycc-devel] New error found on RPi3 buster with gcc 8.3 on test 93

Test: 93_integer_promotion... --- 93_integer_promotion.expect 2019-06-25 23:11:21.865155888 +0200 +++ 93_integer_promotion.output 2019-06-25 23:12:31.445089726 +0200 @@ -6,7 +6,7 @@ signed : (1 ? s.ub : 1) unsigned : (1 ? s.u : 1) - signed : (1 ? s.ullb : 1) + unsigned : (1 ?

[Tinycc-devel] "Try fixing asm_dot_test on Windows" few more cases

Hello, I missed to run few tests on Windows that I tried to add after commit "Try fixing asm_dot_test on Windows" There are few remaining offending pseudo-op: /cygdrive/f/tinycc/win32/tcc -run ../examples/ex1.c || (set -x; ../tcc -vv; ldd ../tcc; exit 1) Hello World cc -o tcctest.gcc

Re: [Tinycc-devel] libtest fails on mingw since d04ce77 (2019-05-30)

There are two more cases to handle in this file: asm volatile (".globl some_symbol\n" "jmp .+6\n" "1:\n" "some_symbol: .long 0\n" ".pushsection __bug_table, \"a\"\n" ".globl bug_table\n"

Re: [Tinycc-devel] undefined sanitizer

. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Vincent Lefevre Sent: Sunday, June 23, 2019 12:42 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] undefined sanitizer On 2019-06-23 06:51:04 +0200, Christian Jullien wrote

Re: [Tinycc-devel] undefined sanitizer

> Yes, it's implementation defined, but I assume that -fsanitize=undefined > warns only when the implementation has decided that this was incorrectly > aligned. It's nice to have this warning even if implementation supports incorrect alignment. Suppose I provide a portable C library which will

Re: [Tinycc-devel] match formats and arguments exactly

Don't misunderstand me, this check is a very valuable addition. For an uncounted number of years I use any possible warnings and my code (almost) pass with all sanitizer, splint, code analyzers ... You should also understand that many code slowly moved from K to ANSI, to C98 .. C11 and it's a pain

Re: [Tinycc-devel] match formats and arguments exactly

is.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] match formats and arguments exactly > On 21 Jun 2019, at 14:56, Christian Jullien wrote: > > This is a valuable check but IMHO, it should be controlled by -Wformat (as > GNU gcc) and set of false by default. > Oth

Re: [Tinycc-devel] match formats and arguments exactly

This is a valuable check but IMHO, it should be controlled by -Wformat (as GNU gcc) and set of false by default. Otherwise, I suspect tcc users will have a lot a new warnings. I'll personally definitely will adopt this flag as I do with gcc. -Original Message- From: Tinycc-devel

Re: [Tinycc-devel] Avoid allocating a VLA of size zero

Thank you for your first contribution to tcc ... and mod is not broken :o)) A first step starting a long journey? C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Pascal Cuoq Sent: Wednesday, June 19, 2019 21:07 To: Michael

Re: [Tinycc-devel] test 104 fails on windows: missing mkstemps

"en_US.UTF-8" > LC_MESSAGES="en_US.UTF-8" > LC_ALL= > > Please don't push this patch to mob, because it adds another potential > complexity by mixing unix/windows tools. > > I'll try to modify 104_inline_test.c such that it uses only one system > invocat

Re: [Tinycc-devel] test 104 fails on windows: missing mkstemps

ll -c "" so that it effectively becomes a shell script, and post the result of my attempt here to get some feedback. Thanks again, Avi On Wednesday, June 19, 2019 8:20 AM, Christian Jullien wrote: Avih, I quickly hacked 104 test to start to make it work but I’m not the a

Re: [Tinycc-devel] test 104 fails on windows: missing mkstemps

the recent breakage specifically on windows from related code, I think it would be beneficial if this test could be made to work on windows, On Monday, June 17, 2019 11:54 PM, avih wrote: Wouldn't it be better to just create a known/fixed file instead? (assuming the test doesn't

Re: [Tinycc-devel] ANSI C refers to which standard , C89 or C99?

Paul, I agree with you that it’s not clear. What I’ve learnt all these years is: - Tcc supports as much as it can C99 - It supports “some” C11 feature by default or using –std=c11 if there is possible name collision with C99 - Tcc internal source code should not

Re: [Tinycc-devel] test 104 fails on windows: missing mkstemps

Yes it has been previously reported. Michael, as said in a private mail, I agree with you that this test should be skipped on Windows. C. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of avih Sent: Monday, June 17, 2019 22:46 To: Tinycc-devel

[Tinycc-devel] mkstemps error on Windows

Recent patch gives this error when compiling the test suite on Windows + Cygwin: -noinst_extern_inline_postdeclared2 -noinst_extern_inline_undeclared +104_inline_test.c:30: warning: implicit declaration of function 'mkstemps' +tcc: error: undefined symbol 'mkstemps' make[2]: ***

Re: [Tinycc-devel] minor patches + standard compliant inline functions

Hello Michael, Your patch gives many new warnings when I do a reproducible tcc build on Windows (i.e. tcc is first compiled by Cygwin/gcc then it is used to produce a native Windows tcc binary - see https://sourceforge.net/projects/wintcc/). Bootstrapping 32bits and 64bits tools with gcc -m64

Re: [Tinycc-devel] tcc crashes at the dlltest in Fedora 30

Yes this known, See thread started by "https://lists.nongnu.org/archive/html/tinycc-devel/2019-03/msg0.html; And my investigations with (possible?) fix https://lists.nongnu.org/archive/html/tinycc-devel/2019-03/msg00017.html

Re: [Tinycc-devel] minor patches + standard compliant inline functions

for finding the problem! Cheers, Petr S. On 6/12/19 12:00 PM, Christian Jullien wrote: > Hi Petr, > > I prefer to let __CRT_INLINE as is. TinyCC shares Windows header with > mingw64. I don't think it's a good idea to start to patch them. > > Please note that TinyCC reports a

Re: [Tinycc-devel] minor patches + standard compliant inline functions

inkage. C. -Original Message- From: Petr Skočík [mailto:psko...@gmail.com] Sent: Wednesday, June 12, 2019 11:49 To: Christian Jullien; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] minor patches + standard compliant inline functions Hi, Christian Jullien. Thanks for the feedback. I

Re: [Tinycc-devel] minor patches + standard compliant inline functions

Thanks for your patch, FYI, for Windows compatibility: turn -fdollars-in-identifiers on by default is Ol as it also applies to cl on Windows (the old VMS days :o) Also ok to remove __STDC_ISO_10646__ as is not defined on Windows too. Please note that a conforming C11 implementation should have

Re: [Tinycc-devel] tcc_relocate is missing in libtcc.dll

Antoni, If it helps, I maintain https://sourceforge.net/projects/wintcc/ Which easily builds a tcc multi-arch standalone archive for Windows. It bootstraps tcc from Cygwin gcc and finally generates tcc buit by tcc Windows build (i.e. a reproducible build). It contains only a Makefile you

Re: [Tinycc-devel] Few files are missing for socket programming on Windows

For those following this thread, all stuff has been pushed on mod. Socket now works on Windows from mod without to have to download additional files. C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

15, 2019 20:06 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler. Hello, On Mon, 15 Apr 2019, Christian Jullien wrote: > Do you want I push your patch that works great at handling SIGS

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

Michael, Do you want I push your patch that works great at handling SIGSEGV? As it is your patch, I prefer if you do it yourself. Not related, as I've got no complain, do you allow me to push the few files that are missing from win32 to allow BSD socket programming ROOTB from git on Windows? C.

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

Hi Michael, Not only your patch lets the signal.c sample work on Windows x64/tcc -m64 but it also makes OpenLisp REPL happy on invalid code: ? (cons . 1) ** : OpenLisp : machine-error : 11 Cherry on the cake, tcc is now promoted a Gold port :o)) There is no functional differences between VC++,

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

BUG, SIGSEV is not correctly handled by installed signal handler. Hi, On Tue, 9 Apr 2019, Christian Jullien wrote: > For the context, I'm trying to make tcc a "Gold" Windows port of my OpenLisp > ISLISP compiler, i.e. a Gold port runs the full test suite and introduces no > per

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

l Message- From: Michael Matz [mailto:matz@frakked.de] Sent: Tuesday, April 09, 2019 15:08 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler. Hi, On Tue, 9 Apr 2019, Christian Jullien

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

Hi, On Mon, 8 Apr 2019, Christian Jullien wrote: > Hum!? > My machine is a quite old Core i7 processor which has not all modern > instructions (like AVX2). > Could it be related to a generated instruction which does not exist on my > processor. No, TCC doesn't generate AVX (or AV

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

: Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler. Hello, On Mon, 8 Apr 2019, Christian Jullien wrote: > c:\tmp>tcc -m64 signal.c && signal > > Waiting for SIGSEGV <<= program terminates after this print!!

Re: [Tinycc-devel] Few files are missing for socket programming on Windows

:matz@frakked.de] Sent: Monday, April 08, 2019 19:24 To: jull...@eligis.com; tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Few files are missing for socket programming on Windows Hi, On Sun, 7 Apr 2019, Christian Jullien wrote: > Programming with sockets on Windows require: &g

[Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.

Using mob, the code below works on Windows 10 with PE (i386) but hangs on PE+ (x86_64) handler function is not entered with x86_64. Expected behavior with -m32: c:\tmp>tcc -m32 signal.c && signal Waiting for SIGSEGV Got signal 11!! Want to exit? [y/n] y Exiting from handler...

[Tinycc-devel] Few files are missing for socket programming on Windows

Programming with sockets on Windows require: - qos.h - winsock2.h - ws2ipdef.h And - ws2_32.def Which are missing from standard tinycc git repository (under win32). Ok I've grabbed .h from winapi-full-for-0.9.27 and "./tcc -impdef $(WINDIR)/System32/ws2_32.dll -o lib/ws2_32.def" produced

Re: [Tinycc-devel] TCC segfault on Fedora 29 (more info toward a fix)

else section is never called on Debian ARM (RPi) and called on the section that hangs on Fedora 29. Not sure if SHT_NULL is the right value to set in this case. C. From: Christian Jullien [mailto:eli...@orange.fr] Sent: jeudi 7 mars 2019 08:23 To: 'tinycc-devel@nongnu.org' Subject: RE: [Ti

Re: [Tinycc-devel] TCC segfault on Fedora 29 (more info toward a fix)

19, s->sh_type = 6 (4), s->sh_info = 0, s1->sections[s->sh_info] = (nil) i = 20, s->sh_type = 1 (4), s->sh_info = 0, s1->sections[s->sh_info] = (nil) i = 21, s->sh_type = 4 (4), s->sh_info = 20, s1->sections[s->sh_info] = 0x2346c10 i = 22, s->sh_type = 1 (4), s-&

Re: [Tinycc-devel] TCC segfault on Fedora 29

Matz Sent: lundi 4 mars 2019 18:48 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] TCC segfault on Fedora 29 Hi, On Mon, 4 Mar 2019, Christian Jullien wrote: > Ooops, not quite. > I missed this line on log file (from Fedora 29). > Btw, as suggested by ./configure, Fedora

Re: [Tinycc-devel] TCC segfault on Fedora 29

Ooops, not quite. I missed this line on log file (from Fedora 29). Btw, as suggested by ./configure, Fedora 29 requires --with-selinux dlltest ../tcc -B.. -I../include -I.. -I.. -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 -DHAVE_SELINUX -DLIBTCC_AS_DLL ../libtcc.c

Re: [Tinycc-devel] TCC segfault on Fedora 29

Many thanks Michael, I confirm it works now on Fedora 29 and no regression found on Windows 32/64 or Linux ARM. Good job. C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: lundi 4 mars 2019 16:58 To:

Re: [Tinycc-devel] TCC segfault on Fedora 29

With mod and Fedora 29 updated, I confirm it hands as you said. Can't help you further. C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Klaus Ebbe Grue Sent: vendredi 1 mars 2019 22:45 To: tinycc-devel@nongnu.org Subject:

Re: [Tinycc-devel] Bug in _Bool return values

Thanks for the sample. On ARM nothing has to be done as it returns the expected result. I let other maintainers to see if your patch for Intel 32/64 is Ok. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Louis Botha Sent: lundi 4 février 2019 23:32

Re: [Tinycc-devel] Bug in _Bool return values

Hello Louis, To help maintainers, can you please give us a complete working example on gcc / VC++ that fails with tcc? I’ll see how it goes on ARM 32/64. C. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Louis Botha Sent: lundi 4 février 2019 01:54

Re: [Tinycc-devel] tcc coding style question

, Vincent Lefevre wrote: > On 2019-01-24 16:10:03 +, Michael Matz wrote: > > On Thu, 24 Jan 2019, Christian Jullien wrote: > > > > > Question (to maintainers): do you allow me to fix them all? > > > > Please don't. It makes git blame unnecessarily hard. >

Re: [Tinycc-devel] tcc coding style question

-devel] tcc coding style question Hi, On Thu, 24 Jan 2019, Christian Jullien wrote: > Question (to maintainers): do you allow me to fix them all? Please don't. It makes git blame unnecessarily hard. You can fix style issues when you change the code in question for other reasons. (I'm proba

[Tinycc-devel] tcc coding style question

>From CodingStyle I see : Indentation Turn on a "fill tabs with spaces" option in your editor. Remove tabs and trailing spaces from any lines that are modified. And I fully agree with this style. Unfortunately, I see many source codes having few to many tabs. Question (to

Re: [Tinycc-devel] Add gcc cleanup attribute support

cleanup attribute support fix, sorry for the bug. On Wed, Jan 23, 2019 at 5:59 PM Christian Jullien wrote: > > Thanks, > > It work on ARM too, but only because my RPi uses gcc 6.x which is C99. > > On an Aarch64, using gcc 4.8, boostrap fails with: > > tccgen.c: In fun

Re: [Tinycc-devel] Add gcc cleanup attribute support

w, it work, So I've push. Thanks for your help Matthias On Mon, Jan 21, 2019 at 11:42 AM Christian Jullien wrote: > > Hi, > > Windows x64, Linux Intel 32/64 is already nice, esp. if a test exists. I'll > make other tests when pushed on mob. > > C. > > -Original Mes

Re: [Tinycc-devel] Missing C99 standard headers in win32

Sent: lundi 21 janvier 2019 19:49 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Missing C99 standard headers in win32 Hi, On Sun, 13 Jan 2019, Christian Jullien wrote: > ISO/IEC 9899 :1999 (E) specifies that (Section 7.1.2 p. 165), Standard > headers are: > > Those already i

Re: [Tinycc-devel] Add gcc cleanup attribute support

-devel@nongnu.org Subject: Re: [Tinycc-devel] Add gcc cleanup attribute support On Sun, Jan 20, 2019 at 9:19 AM Christian Jullien wrote: > > Thank you for your patch. I adopt the same process: propose a patch then, if > nobody protest after a reasonable period of time, I push it on mod. > B

Re: [Tinycc-devel] Add gcc cleanup attribute support

Thank you for your patch. I adopt the same process: propose a patch then, if nobody protest after a reasonable period of time, I push it on mod. Btw, have you a compressible set of tests for added feature? My **very modest** role I affect to myself in this project is to test mob on the different

Re: [Tinycc-devel] TinyCC for bootstrapping (with patches)

It looks true for float and double, see also long double which differs greatly On Windows: 32 and 64 bit with cl sizeof(float) 4 sizeof(double) 8 sizeof(long double) 8 On Linux ARM32 (Rpi) sizeof(float) 4 sizeof(double) 8 sizeof(long double) 8 On Linux ARM64 sizeof(float)

Re: [Tinycc-devel] Missing C99 standard headers in win32

Christian Jullien Those already in win32 lack complex (and imaginary) support restricted character set support via digraphs type-generic math macros To make tcc a little bit more C99 conformant I added More includes are missing

[Tinycc-devel] Missing C99 standard headers in win32

ISO/IEC 9899 :1999 (E) specifies that (Section 7.1.2 p. 165), Standard headers are: Those already in win32 lack complex (and imaginary) support restricted character set support via digraphs type-generic math macros To make tcc a

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

his, I don't object to the patches that now went in. Ciao, Michael. > > Petr S. > > > On 1/10/19 11:47 PM, uso ewin wrote: >> On Thu, Jan 10, 2019 at 2:47 PM Christian Jullien wrote: >>> >>> Matthias, >>> >>> >>> I'm happy

[Tinycc-devel] When -std=c11 I added some 6.10.8.3 Conditional feature macros related to C11

Especially those that allow to know if a specific C11 feature exists in the current implementation. It would be interesting to see what 6.10.8.2 Environment macros should be defined as well ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

-devel] Add max_align_t to stddef.h and C11 On Fri, Jan 11, 2019 at 7:56 AM Christian Jullien wrote: > > Petr, I also agree with you. > > If gcc more or less "governs" tcc behavior, _Alignof and _Generic should be > defined by default whatever -std=cxx is used. > >

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

edantic`). Unlike max_align_t, _Generic and _Alignof are reserved identifiers in any C version. They shouldn't ever need to be hidden. Hiding them can unnecessarily break some project builds that use tcc with _Generic or _Alignof and without -std=c11. Petr S. On 1/10/19 11:47 PM, uso ewin wrote: >

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

=orange...@nongnu.org] On Behalf Of uso ewin Sent: jeudi 10 janvier 2019 11:13 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Add max_align_t to stddef.h and C11 On Tue, Jan 8, 2019 at 6:02 PM Christian Jullien wrote: > > > Maybe add a global variable > > Not global b

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

> Maybe add a global variable Not global but a new member of TCCState, for example cversion If (s->cversion >= 201112) { /* Hello C11 */ } Diff becomes: jullien@sims3:~/new-tcc $ git diff diff --git a/libtcc.c b/libtcc.c index df7adab..7883734 100644 --- a/libtcc.c +++ b/libtcc.c @@ -1790,8

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

&& ./foo __STDC_VERSION__ == 201102 jullien@sims3:~/new-tcc $ ./tcc -std=c42 foo.c -o foo && ./foo __STDC_VERSION__ == 199901 -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of uso ewin Sent: mardi 8 janvier 2019 15

Re: [Tinycc-devel] Add max_align_t to stddef.h and C11

ike _Generic, but since _Generic is a reserved word in all contexts, there are no name conflicts. max_align_t is conflicting, IMO. I've reverted the patch. Thanks. Best regards, Petr Skocik On 1/8/19 7:51 AM, Christian Jullien wrote: > Hi all, > >   > > Last commit made by Petr

[Tinycc-devel] Add max_align_t to stddef.h and C11

Hi all, Last commit made by Petr Skocik introduces definition of max_align_t which is ISO/IEC 9899:2011 p. 286 "max_align_t which is an object type whose alignment is as great as is supported by the implementation in all contexts" But, currently, tcc is supposed to implement C99

Re: [Tinycc-devel] OpenBSD/amd64 build failure

It looks that OpenBSD is only half supported. FYI, FreeBSD is better supported but does not completely (I can't remember where exactly it fails). You must identify all references to *BSD* in the source code, add logic for OpenBSD, based on triplet returned by conftest (./conftest t), pass

Re: [Tinycc-devel] Add gcc cleanup attribute support

Hi Matthias, I speak only for myself but, if you implement a gcc extension in fully compatible way and have a non-regression test for it. It's Ok for me. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of uso ewin Sent: mercredi 2

Re: [Tinycc-devel] OpenBSD/amd64 build failure

Hi Alexander, The similar segfault was related to wrong configuration detection. The "fix" was to supply the right options to configure (like ./configure --triplet=arm-linux-gnueabihf --prefix=/usr --crtprefix=/usr/lib) Could it be also the root of your problem? -Original Message- From:

Re: [Tinycc-devel] Function pointers declared in a particular way result in a miscompilation

and bundle them with the next release if possible. - Jonathan On Tue, 1 Jan 2019, 07:29 Christian Jullien Which winnls.h have we the rights to include in standard tcc distrib? We could take the one from MinGW but includes many others includes not present in tcc (should we take them all

Re: [Tinycc-devel] Function pointers declared in a particular way result in a miscompilation

Thanks Michael and Jonathan. Unless I’m missing something in flag or config, sqlite does not compile ROOTB. I add to include this dirty patch in sqlite3.c int MultiByteToWideChar(void); int WideCharToMultiByte(void); #define CP_ACP 0 #define CP_UTF8 65001 #define CP_OEMCP 1 In fact,

Re: [Tinycc-devel] When is planned to be released the next versionof Tcc?

gcc/armv7l-unknown-linux-gnueabihf/8.2.0/../../../libgcc_s.so.1) /usr/lib/gcc/armv7l-unknown-linux-gnueabihf/8.2.0/crtendS.o /usr/lib/gcc/armv7l-unknown-linux-gnueabihf/8.2.0/../../../crtn.o On 12/23/18 4:35 PM, Christian Jullien wrote: On RPi, crti.o is located on /usr/lib/arm-linux-gnueabihf/cr

Re: [Tinycc-devel] When is planned to be released the next versionof Tcc?

;). Sidenote: this triplet thing is the most shittiest thing in autotools (I know, tcc does not use autotools). That's why I prefer scconfig (http://repo.hu/projects/scconfig/) for my projects. [ON] Aron On 12/23/18 3:07 PM, Christian Jullien wrote: > As said, it's a temporary tool dele

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

nueabihf Although, it is strange, I do not have this executable after running configure. Maybe configure decided to not use it? On 12/23/18 2:43 PM, Christian Jullien wrote: > Triplet is given by the temporary conftest tool. You can make it with: > > $ gcc conftest.c -o conftest &&

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

o:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Barath Aron Sent: dimanche 23 décembre 2018 14:32 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] When is planned to be released the next version of Tcc? What is in your triplet? Mine is empty. On 12/23/18 2:22 PM, Christian

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

On Raspbian, running ./configure I get: jullien@sims3:~/tinycc $ more config.mak # Automatically generated by configure - do not modify prefix=/usr/local bindir=$(DESTDIR)/usr/local/bin tccdir=$(DESTDIR)/usr/local/lib/tcc libdir=$(DESTDIR)/usr/local/lib includedir=$(DESTDIR)/usr/local/include

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

lanned to be released the next version of Tcc? Scroll back to my mail dated on 12/3/18, 5:34 PM for details of the crash. On 12/23/18 10:07 AM, Christian Jullien wrote: > Ouch! I don’t know about ARCH ARM Linux, I can just say it works nicely on > RPi ARM board: > > jullien@sims3:~ $ tc

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

ntation fault (core dumped) I suppose this is not the intended behavior. Same effect with official package and with mob. (I already reported this bug, but it seems nobody cares.) Aron On 12/23/18 8:25 AM, Christian Jullien wrote: I’m not the maintainer of tcc but I’ve no sign of a new versio

Re: [Tinycc-devel] When is planned to be released the next version of Tcc?

I’m not the maintainer of tcc but I’ve no sign of a new version anytime soon. What I can say however is that: - 0.9.27 released last year is damn good and almost bug free on supported platforms (I personally tested) - Since last release, tcc activity has been rather low and I

Re: [Tinycc-devel] Fix gcall_or_jmp to VT_CONST symbol in arm-gen.c

I tested your patch on ARM board (RPi) and it works. I reintroduced zfunc test for this system in 07_function.c Thanks -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Pursuer Sent: samedi 22 décembre 2018 14:05 To: tinycc-devel

Re: [Tinycc-devel] Commit 'x86-64: Fix calls via absolute function pointers' makes 07 test fail on ARM

for this architecture until ARM maintainers * see what happens with this test. */ void zfunc() { ((void (*)(void))0) (); } #endif From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: mardi 11 décembre 2018 08:53 To: tinycc-devel@nongnu.org Subject

Re: [Tinycc-devel] tcc no longer compiles on Windows

As nobody complained, I suppose it’s Ok so I pushed the fix on mob. C. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: dimanche 9 décembre 2018 17:15 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] tcc no longer

Re: [Tinycc-devel] SQLite miscompiles on Windows 32-bit

I’ve absolute no ideas how to explain tcc x86_64 backend to generate this code. M2c. C. From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: dimanche 16 décembre 2018 08:21 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc

Re: [Tinycc-devel] SQLite miscompiles on Windows 32-bit

Jonathan, I second you for a full SQLite support with tcc. You may also ping SQLite guys to see if they see an interest to support tcc in their toolchain. Maybe they can do halt the road adapting the source code so that it better compiles with tcc? From: Tinycc-devel

[Tinycc-devel] Commit 'x86-64: Fix calls via absolute function pointers' makes 07 test fail on ARM

Michael made this patch "x86-64: Fix calls via absolute function pointers" for x86-64 and ARM64. On ARM 32bits (as RPi), test 07 fails: Test: 07_function... --- 07_function.expect 2018-07-02 01:57:29.0 +0200 +++ 07_function.output 2018-12-11 08:42:22.439364314 +0100 @@ -1,4 +1 @@

Re: [Tinycc-devel] tcc no longer compiles on Windows

int sym_index = ELFW(R_SYM)(rel->r_info); +#endif switch(type) { #if defined(TCC_TARGET_I386) || defined(TCC_TARGET_X86_64) #if defined(TCC_TARGET_I386) From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: vendre

[Tinycc-devel] tcc no longer compiles on Windows

Tccelf.c has an undefined reference to sym_index with R_X86_64_PC32 case line 897. The declaration of sym_index at line 877 is not covered by this case. static int prepare_dynamic_rel(TCCState *s1, Section *sr) { ElfW_Rel *rel; int type, count; count = 0;

Re: [Tinycc-devel] TCC segfault on Fedora 29

BTW, I already reported this BUG in the past: http://lists.nongnu.org/archive/html/tinycc-devel/2017-10/msg00033.html From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: samedi 3 novembre 2018 16:35 To: tinycc-devel

Re: [Tinycc-devel] Mis-parse in some situations involving a function pointer with attributes (breaks SQLite build)

I would love to have SQLite working with tcc. Two of my favorite projects. Especially, SQLite is an optional component of my own Lisp (OpenLisp) which currently lacks this module when compiled with tcc. My contribution will be to test SQLite on all OS/processor tcc currently supports.

Re: [Tinycc-devel] New ARM warning. Does it reveal an issue?

two cases that use it. From: Christian Jullien [mailto:eli...@orange.fr] Sent: lundi 30 avril 2018 07:28 To: tinycc-devel@nongnu.org Subject: New ARM warning. Does it reveal an issue? Hi all, Recompiling mod on ARM gives me this new Warning : tccelf.c:869:9: warning: variable 'sym_in

[Tinycc-devel] New ARM warning. Does it reveal an issue?

Hi all, Recompiling mod on ARM gives me this new Warning : tccelf.c:869:9: warning: variable 'sym_index' set but not used [-Wunused-but-set-variable] int sym_index, type, count; ^ On: /* count the number of dynamic relocations so that we can reserve their

Re: [Tinycc-devel] #line directive with file name

Yakov, with mod on Windows I tried this: c:\tmp>type foo.c int main() { #line 30 "demo.c" printf("hello\n"); #line 40 "demo.c" return 0; } c:\tmp>tcc -E foo.c # 1 "foo.c" int main() { # 30 "demo.c" printf("hello\n"); # 40 "demo.c" return 0; } On

Re: [Tinycc-devel] Building native tcc for Windows

Of Mikhail Zaycev Sent: mardi 10 avril 2018 08:42 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Building native tcc for Windows 10:33, 8 апреля 2018 г., Christian Jullien <eli...@orange.fr>: You can install tcc-0.9.27-x86_64-win32.tar.gz standalone tcc native compiler on any Windows m

[Tinycc-devel] Building native tcc for Windows

Hi all, few months ago, Grischka took the time (and had the patience) to explain me how to build native tcc Windows from Cygwin. (see thread [Tinycc-devel] Push reproducible builds script? (for windows) ) I recognize it

Re: [Tinycc-devel] A wish for 2018? C->JVM compiler

rested in a tinycc javscript target? On Sat, Mar 10, 2018 at 11:43 AM, Christian Jullien <eli...@orange.fr> wrote: First link looks especially interesting. thanks My question is if tinycc could generate JVM code which any java engine can use. IMHO setjmp/longjmp is probably not very

Re: [Tinycc-devel] A wish for 2018? C->JVM compiler

ler-to-java-runtime.html https://stackoverflow.com/questions/4934707/is-it-possible-to-transform-llvm-bytecode-into-java-bytecode I am not a Java guy, so not sure if that's what you imagine, but it seems close. Yash 2017-12-31 12:13 GMT+05:45 Christian Jullien <eli...@orange.fr>: Hi all

Re: [Tinycc-devel] "_winstart not defined"

] "_winstart not defined" Christian Jullien wrote: > Grischka, > FYI The link on http://download.savannah.nongnu.org/releases/tinycc/ > is not working => 404 Not YET working, I suppose: Downloads will redirect to your nearest mirror site. Files on mirrors may be subject

Re: [Tinycc-devel] "_winstart not defined"

Grischka, FYI The link on http://download.savannah.nongnu.org/releases/tinycc/ is not working => 404 C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of grischka Sent: samedi 10 février 2018 18:32 To: tinycc-devel@nongnu.org

Re: [Tinycc-devel] performance

Daniel, Tcc is wonderful C compiler that compiles your code blazing fast. As there is no free lunch, it achieves this **compilation** speed in only one pass. It is definitively NOT competing with top notch professional quality multi-pass optimizing compilers. Tcc could probably marginally be

[Tinycc-devel] A wish for 2018? C->JVM compiler

Hi all, I don't how much it could cost nor it's even feasible, but it would be nice to have a JVM backend. (as other languages already use, see https://en.wikipedia.org/wiki/List_of_JVM_languages) This could be a nice student project. Main goal: - Have a portable C on top on JVM

Re: [Tinycc-devel] TCC version 0.9.27 is out

Drougge Carlos Montiers Changming Xu Christian Jullien Claudio Bley Daniel Glöckner Dave Dodge Dave Long David Mertens Dennis Yurichev Detlef Riekenberg Domingo Alvarez Duarte Edmund Grimley Evans emekoi Emil Fabrice Bellard Felix Nawothnig Filip Navara Frédéric Féret Gabriel

Re: [Tinycc-devel] Unify C and asm symbols

job all. -Original Message- From: grischka [mailto:gris...@gmx.de] Sent: mardi 12 décembre 2017 19:22 To: Christian Jullien Cc: tinycc-devel@nongnu.org; Michael Matz Subject: Re: [Tinycc-devel] Unify C and asm symbols Christian Jullien wrote: > Before it is released, can you please anno

Re: [Tinycc-devel] Unify C and asm symbols

> I'd then make one more commit with other small fixes, and then I'd > pack the release, say next Sun (17.12.) > > How does that sound? Nice to see the new release is knocking at the door. Before it is released, can you please announce it goes to BETA stage so that I can test the release

Re: [Tinycc-devel] Unify C and asm symbols (was: forward asm symbols vs static)

Hi Michael, Using native Windows 32/64 builds from mob, I see no errors on tests suite. My RPi 3 box installed with Debian 32bit is also very happy. Good job C. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz

Re: [Tinycc-devel] main does not returns 0 by default (at least on Windows)

tw, I added a TinyCC link to https://en.wikipedia.org/wiki/ANSI_C C. -Original Message- From: Edmund Grimley Evans [mailto:edmund.grimley.ev...@gmail.com] Sent: mercredi 22 novembre 2017 14:20 To: Christian JULLIEN Subject: Re: [Tinycc-devel] main does not returns 0 by default (

Re: [Tinycc-devel] plans to 0.9.27

Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of grischka Sent: vendredi 13 octobre 2017 20:37 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] plans to 0.9.27 Christian Jullien wrote: > But worse, I've also the impression that, after

<    1   2   3   4   5   6   7   8   9   >