[Tinycc-devel] Ready for Release 0.9.27
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 should still have? Everyone else, please test. --- grischka ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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 ago due to this, and now probably more things would not build. It was at the repo anyway, it worked, deleting them doesn't make the repo smaller since it's at the history anyway, so why make life harder for users who want to use tcc without external mingw headers which possibly require modifications, which I presume the ones you removed already have this effort put into them? IMO it is not a reasonable goal for tinycc to "maintain" windows headers in the sense of completeness or patching the files. If anything they should be replaced by newer versions taken directly from mingw or mingw-w64, preferably unchanged. If wanted a more complete or newer set could be put as a separate pack on the savannah download folder provided that someone puts one together. Other than that we have the standard ansi headers, and in addition from the windows headers what is necessary to compile the hello_win example. It's just that I like that criterion because it is well defined. Regards, --- grischka On Wednesday, February 8, 2017 9:15 PM, 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 should still have? Everyone else, please test. --- grischka ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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 should still have? Well, i still have this patch that allows multiple -rpath arguments, that would be really cool to have in by default -- after massive and repeated hints hints from Michael Matz this is clean, right? I mean, i would commit it myself, but note i have red eyes and at times start to drivel. It is extremely unlikely that i would be of any but (let me say) further testing use beside that, especially since i have to deal with C++ in the not too distant future... And then the patch which avoids segmentation faults when compiling a small unready C source still applies cleanly, i.e., that "section_ptr_add(s, 8);" in relocate_section(). I've updated from 71c5ce5..5efa75d. Hm. But i cannot reproduce the crash no more, even without that patch! On x86_64. Cool!! |Everyone else, please test. Looks good for what i have. Thank you! --steffen ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
Re: [Tinycc-devel] 0.9.27 released?
On vendredi 20 janvier 2017 22:52:59 GMT Michael Matz wrote: > Hi, > > On Fri, 20 Jan 2017, Markus Reichelt wrote: > > Aloha, > > > > http://repology.org/metapackage/tcc/versions > > > > shows tinycc 0.9.27 as the latest version available for deb unstable > > & ubuntu zesty > > > > I didn't know about that repology site at first but I've been bugged to > > update to 0.9.27 as well (I deal with the SBo side of things). And I > > tend to follow this mailinglist from time to time, but apparently I must > > have missed the 0.9.27 announcement. > > You haven't missed anything, such a release didn't happen yet. The > packagers of the above package(s) chose to call it 0.9.27 because they > package git snapshots, so 0.9.26 would have been wrong as well, and I > guess 0.9.27 is less wrong. E.g. the debian unstable snapshot is actually > version "0.9.27~git20161217.cd9514ab-3". Indeed, that's exactly my thought. I think we are closer to 0.9.27 than 0.9.26. Also the ~ in the version ensures that 0.9.27 will be a greater version than the current one (ie this indicates that it is pre 0.9.27). Best regards, Thomas signature.asc Description: This is a digitally signed message part. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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 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 checked carefully) but don't wait for me. Best regards, Thomas signature.asc Description: This is a digitally signed message part. ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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]
dlltest
../tcc -B.. -I../include -I.. -I.. -DONE_SOURCE -DCONFIG_LDDIR="\"lib64\""
-DTCC_TARGET_X86_64 -DLIBTCC_AS_DLL ../libtcc.c -lm -ldl -shared -o libtcc2
../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
make[1]: *** [dlltest] Error 1
- Raspberry Pi 3 (ARM) [KO]
...
./abitest-tcc -B.. -I../include -I.. -I..
ret_int_test... Makefile:226: recipe for target 'abitest' failed
make[1]: *** [abitest] Segmentation fault
--- ../../tests/tests2/32_led.expect2017-02-09 06:12:23.920041867 +0100
+++ 32_led.output 2017-02-09 06:13:11.539883594 +0100
@@ -1,4 +1,4 @@
- _ _ _ _
- | _| _| |_| |_ |_|
- | |_ _| | _| |_| |
+
+
+
...
Makefile:54: recipe for target '32_led.test' failed
Test: 42_function_pointer...
--- ../../tests/tests2/42_function_pointer.expect 2017-02-09
06:12:23.9300
41833 +0100
+++ 42_function_pointer.output 1970-01-01 01:00:00.0 +0100
@@ -1,2 +0,0 @@
-yo 24
-42
Makefile:54: recipe for target '42_function_pointer.test' failed
...
Test: 88_codeopt...
make[2]: Target 'all' not remade because of errors.
make[2]: Leaving directory '/home/jullien/tinycc/tests/tests2'
Makefile:85: recipe for target 'tests2-dir' failed
make[1]: *** [tests2-dir] Error 2
- APM X-Gene Mustang board (Aarch64) [KO]
Test: 42_function_pointer...
--- ../../tests/tests2/42_function_pointer.expect 2016-10-13
21:48:59.8278
35999 -0700
+++ 42_function_pointer.output 1969-12-31 16:00:00.0 -0800
@@ -1,2 +0,0 @@
-yo 24
-42
make[2]: *** [42_function_pointer.test] Error 1
-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of grischka
Sent: mercredi 8 février 2017 20:15
To: tinycc-devel@nongnu.org
Subject: [Tinycc-devel] Ready for Release 0.9.27
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 should still have?
Everyone else, please test.
--- grischka
___
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] 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 used already, then $(CC) is gcc, so why hard-code gcc? Because these are "developer only" targets. You may set CC=tcc, but then we still do not want to compare the output of tcc with the output of tcc, obviously. Actually we do not want any of the expect files to be rebuild by users and testers at all. On the downside as a developer you need to delete the .expect file manually if you want it to be rebuilt. -- gr ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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 configure. Did you ./configure? *- Raspberry Pi 3 (ARM) [KO]* ret_int_test... Makefile:226: recipe for target 'abitest' failed make[1]: *** [abitest] Segmentation fault Makefile:54: recipe for target '32_led.test' failed Makefile:54: recipe for target '42_function_pointer.test' failed Are these regressions? If so we would probably need to know by which commit it was introduced (I'm afraid) *- APM X-Gene Mustang board (Aarch64) [KO]* make[2]: *** [42_function_pointer.test] Error 1 Not sure about this 42_function_pointer.test. It's some new nifty test for the linker. Michael, is it supposed to work on ARM and/or AARCH64? Thanks, -- gr ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
