Re: [Tinycc-devel] Ready for Release 0.9.27

om: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: samedi 11 février 2017 14:34 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 Hi, On Sat, 11 Feb 2017, Michael Matz wrote: Your commit: http://repo.or.cz/

Re: [Tinycc-devel] Ready for Release 0.9.27

Hi, On Fri, 10 Feb 2017, grischka wrote: FYI, GCC 6 behaves in the same way with -std=c89, -std=c99 and -std=c11. Ditto for Clang 3.9. I wouldn't really mind if we change the behavior. I think we should. If still for 0.9.27 I don't know. It's a subtle change breaking stuff in strange

Re: [Tinycc-devel] Ready for Release 0.9.27

or appears also directly when running ./42_function_pointer.exe from shell. -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Michael Matz Sent: samedi 11 février 2017 14:34 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-de

Re: [Tinycc-devel] Ready for Release 0.9.27

Hi, On Sat, 11 Feb 2017, Michael Matz wrote: Your commit: http://repo.or.cz/tinycc.git/blobdiff/cd9514abc4f4d7d90acce108b98ea2af58a1b8 0a..77d7ea04acb56f839031993c102366e30cad5c25:/tests/tests2/Makefile Is the source of this error Well, that means it uncovered a pre-existing bug in the

Re: [Tinycc-devel] Ready for Release 0.9.27

Hi On Sat, 11 Feb 2017, Christian Jullien wrote: Michael, Your commit: http://repo.or.cz/tinycc.git/blobdiff/cd9514abc4f4d7d90acce108b98ea2af58a1b8 0a..77d7ea04acb56f839031993c102366e30cad5c25:/tests/tests2/Makefile Is the source of this error Well, that means it uncovered a

Re: [Tinycc-devel] Ready for Release 0.9.27

Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: samedi 11 février 2017 10:56 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 Thanks for your fix, now the only rem

Re: [Tinycc-devel] Ready for Release 0.9.27

[mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: samedi 11 février 2017 11:40 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 About test 42 Comparing by hand the 42_function_pointer output and 42_function_pointer expect files

Re: [Tinycc-devel] Ready for Release 0.9.27

om: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Christian Jullien Sent: samedi 11 février 2017 10:56 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 Thanks for your fix, now the only remaining issue on RPi is: Test: 42_function_p

Re: [Tinycc-devel] Ready for Release 0.9.27

; > Is enough. > > I'm not sure if PICFLAGS should be globally set or inside the ifeq section. > I let you deicde. > > Christian > > > -Original Message- > From: Tinycc-devel > [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] > On Behalf

Re: [Tinycc-devel] Ready for Release 0.9.27

Steffen Nurpmeso wrote: Well, i still have this patch that allows multiple -rpath arguments, that would be really cool to have in by default -- Ok, you had luck ;) http://repo.or.cz/tinycc.git/commitdiff/ee5425fe952fdf02fdcdf94f440ee482b6be61ad Because as I said I don't in general push other

Re: [Tinycc-devel] Ready for Release 0.9.27

ristian -Original Message- From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of grischka Sent: vendredi 10 février 2017 09:11 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 Christian Jullien wrote: Here is the complete log I get

Re: [Tinycc-devel] Ready for Release 0.9.27

: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of grischka Sent: vendredi 10 février 2017 09:11 To: tinycc-devel@nongnu.org Subject: Re: [Tinycc-devel] Ready for Release 0.9.27 Christian Jullien wrote: > Here is the complete log I get this morning with c

Re: [Tinycc-devel] Ready for Release 0.9.27

Grischka, It would be a real pleasure to investiate that if I only have time. The best I can do is to test and find commit that breaks tcc on RPi. Christian P.S. I'll try to find few hours this week-end, but not sure I can. Le:10 février 2017 à 09:11 (GMT +01:00) De:"grischka" gris...@gmx.de

Re: [Tinycc-devel] Ready for Release 0.9.27

Christian Jullien wrote: Here is the complete log I get this morning with current mob and especially ... make[1]: *** [abitest] Segmentation fault test3 ../tcc -B.. -I../include -I.. -I.. -DCONFIG_TRIPLET="\"arm-linux-gnueabihf\"" ... Segmentation fault I think we

Re: [Tinycc-devel] Ready for Release 0.9.27

Vincent Lefevre wrote: Note that according to C99, a bit-field is a type ("unsigned int" here is just a type specifier). Just like an array is not the same type of the type of its elements. See 6.7.2.1p9 in C99: A bit-field is interpreted as a signed or unsigned integer type consisting of

Re: [Tinycc-devel] Ready for Release 0.9.27

04 ... PPTest 05 ... PPTest 06 ... PPTest 07 ... PPTest 08 ... PPTest 09 ... PPTest 10 ... PPTest 11 ... PPTest 12 ... PPTest 13 ... PPTest 14 ... PPTest 15 ... PPTest 16 ... PPTest 17 ... make[2]: Leaving directory '/home/jullien/tinycc/tests/pp' make[1]: Target 'all' not remade because of errors. make[

Re: [Tinycc-devel] Ready for Release 0.9.27

On 2017-02-09 21:01:11 +, Thomas Preud'homme wrote: > On jeudi 9 février 2017 18:40:13 GMT grischka wrote: > > Vincent Lefevre wrote: > > > The C standard says: > > > 6.3.1.1 Boolean, characters, and integers > > > > > > [...] > > > > > > If an int can represent all values of the

Re: [Tinycc-devel] Ready for Release 0.9.27

On Thu, Feb 09, 2017 at 01:35:31PM +0100, Vincent Lefevre wrote: > If an int can represent all values of the original type (as > restricted by the width, for a bit-field), the value is converted > to an int; otherwise, it is converted to an unsigned int. These are > called the integer

Re: [Tinycc-devel] Ready for Release 0.9.27

On jeudi 9 février 2017 18:40:13 GMT grischka wrote: > Vincent Lefevre wrote: > > The C standard says: > > 6.3.1.1 Boolean, characters, and integers > > > > [...] > > > > If an int can represent all values of the original type (as > > restricted by the width, for a bit-field), the

Re: [Tinycc-devel] Ready for Release 0.9.27

Vincent Lefevre wrote: The C standard says: 6.3.1.1 Boolean, characters, and integers [...] If an int can represent all values of the original type (as restricted by the width, for a bit-field), the value is converted to an int; otherwise, it is converted to an unsigned int. These

Re: [Tinycc-devel] Ready for Release 0.9.27

Hi, On 2017-02-08 23:09:05 +, Thomas Preud'homme wrote: > On mercredi 8 février 2017 20:15:10 GMT grischka wrote: > > Anyone else any patches that that 0.9.27 should still have? > > I'd like to fix > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832759 (if it is > indeed a bug, I haven't

Re: [Tinycc-devel] Ready for Release 0.9.27

Sure, I always do ./configure. I've just made a new test from a brand new checkout and error is gone. For ARM32/64 I always do a clean checkout, I have the impression that failing tests are new (and probably never tested before on RPi). I'll try today or tomorrow to find the first commit that

Re: [Tinycc-devel] Ready for Release 0.9.27

Christian Jullien wrote: *- Linux CentOS 6.x [KO]* ../tcc -B.. -I../include -I.. -I.. -DCONFIG_LDDIR="\"lib64\"" -DTCC_TARGET_X86_64 ../tcc.c libtcc2 -lm -ldl -Wl,-rpath=. -o tcc2 libtcc2:0: error: unrecognized character \x7f Strange, should be libtcc2.so Seems DLLEXT=.so was not set from

Re: [Tinycc-devel] Ready for Release 0.9.27

avih wrote: (I might be sending this exact same message again. Not sure if my first attempt got sent correctly) grischka, why does commit 5efa75d9 revert commit 9b3e4c58 ? (using gcc instead of $(CC) at the tests). This breaks self-hosting when gcc is not available. If gcc is available and

Re: [Tinycc-devel] Ready for Release 0.9.27

Great news, Here is a quick test with mod on 5 systems (fails on Linux ARM/ARM64/x64 for different reasons) - Windows 32bit {OK] - only tested with my OpenLisp huge non-regression test - Windows 64bit [OK] - only tested with my OpenLisp huge non-regression test - Linux CentOS 6.x [KO]

Re: [Tinycc-devel] Ready for Release 0.9.27

On mercredi 8 février 2017 20:15:10 GMT grischka wrote: > Hi all, Hi, > > I pushed some last patches that I found and updated the version > number: http://repo.or.cz/w/tinycc.git?a=shortlog;h=refs/heads/mob > > So, as far as I'm concerned it would be ready for release. Yay! > Anyone else any

Re: [Tinycc-devel] Ready for Release 0.9.27

Hello. grischka wrote: |Hi all, | |I pushed some last patches that I found and updated the version |number: http://repo.or.cz/w/tinycc.git?a=shortlog;h=refs/heads/mob | |So, as far as I'm concerned it would be ready for release. |Anyone else any patches that that 0.9.27

Re: [Tinycc-devel] Ready for Release 0.9.27

avih wrote: It's not really clear to me why you keep removing windows headers. Now, and also the previous time few months ago when you removed a lot of network related headers. I know for a fact that some things which use network and built cleanly with stock tcc stopped building few months