Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
Hi all On Mon, 27 Jul 2015 08:58:16 +0200 Peter Bex pe...@more-magic.net wrote: On Mon, Jul 27, 2015 at 08:47:56AM +0200, Sven Hartrumpf wrote: ... This is a known problem with newer GCC versions. Your 2nd machine will need 4 hours or more :-( Correct; the [panic] you noted is actually part of the test; it checks that returning twice from a callback fails (which _should_ trigger a panic). That's why it says double-return from callback failed as it should. I agree this is somewhat surprising. Indeed :) The GCC bug is known; I tried to explain this in the RC announcement mail. It will probably disappear with CHICKEN 4.11, if it includes the new argvector branch. If you would like to run the tests through to completion on this platform you can try installing the gcc-4.8 package or clang, and set the C_COMPILER variable to this compiler. Hmm, this is strange, I tried with a previous version of the GCC compiler (4.8: $ make PLATFORM=linux C_COMPILER=gcc-4.8 PREFIX=/home/tim/chicken-test/ install check Again, same thing, stuck for over two hours on that same step. So, I decided to try Clang: $ make PLATFORM=linux C_COMPILER=clang PREFIX=/home/tim/chicken-test/ install check Again, same thing. Before every run I clear out my build area so no remnants of the previous run remain. In the first few lines of the process I can see it uses the compiler I set in the variable: ... clang -L. -shared -Wl,-R. srfi-69.import.o -o srfi-69.import.so \ -lchicken \ -lm -ldl clang -L. -shared -Wl,-R. extras.import.o -o extras.import.so \ -lchicken \ -lm -ldl ... Also, when I use a compiler that does not exists, it complains so the variable is being picked up. Yet, it seems to ignore the compiler variable for the tests as such a line reads (using the lines that keeps hanging): /home/tim/chicken-test/chicken-4.10.0rc4/tests/../chicken 'apply-test.scm' -output-file 'a.c' -types ../types.db -ignore-repository -verbose -include-path /home/tim/chicken-test/chicken-4.10.0rc4/tests/.. 'gcc' 'a.c' -o 'a.o' -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -I/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -I/home/tim/chicken-test//include/chicken To my newbie eyes this looks like 'gcc' is hard-coded in there...somehow...? Whatever I do, it is picking up the correct compiler on start, but once the tests run it uses the default gcc setting...what am I messing up here? Anyway, thanks for testing, Tim! Cheers, Peter Cheers, Tim ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
Hi Peter On Mon, Jul 27, 2015 at 08:32:07PM +0900, Tim van der Linden wrote: ... Again, same thing. Before every run I clear out my build area so no remnants of the previous run remain. In the first few lines of the process I can see it uses the compiler I set in the variable: How do you clear out the build area? I think you might be doing make clean, but that just cleans the built files, whereas make confclean will also clean the configuration, which is where the C_COMPILER is written to. This is documented in the README, by the way, but the consequences might not be immediately obvious. Yes...your thinking was correct, I was using the simple old make clean. I now tried make confclean as well, but with the same effect, still using the default gcc. You can also just try deleting the dir and re-extracting the tarball. That will ensure that the build dir is clean. This crude method seemed the only way to feed a different compiler to the tests. So, it now perfectly ran on GCC 4.8, the full stats for this machine again: Debian 8 - 4 Atom CPUs D525 @ 1.80GHz - 4 Gb of DDR2 800 RAM Total install and test time: 26 minutes and 54 seconds. - Operating system: Debian 8.1 (Jessie) - Hardware platform: x86-64 - C Compiler: GCC 4.8.4 - Installation works?: Yes, no errors - Tests work?: Yes, no errors - Installation of eggs works?: Yes, no errors (installed the Pastiche egg) To my newbie eyes this looks like 'gcc' is hard-coded in there...somehow...? Whatever I do, it is picking up the correct compiler on start, but once the tests run it uses the default gcc setting...what am I messing up here? It gets hardcoded into chicken-config.h the first time you run make. If you run make with a different C_compiler later on, it will only use that C compiler to compile the C files, but csc will use the C compiler from chicken-config.h. The reason behind this probably is so that you can configure a C compiler which is different from the host compiler, for example when cross-compiling. It sure can be confusing, though :) Well, since my (cross)compiling knowledge is not that high...I would never had caught that myself. Thanks for clearing that up for me and helping me get everything tested. Apologies for the noise :) Cheers, Peter Cheers, Tim ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
On Mon, Jul 27, 2015 at 08:32:07PM +0900, Tim van der Linden wrote: The GCC bug is known; I tried to explain this in the RC announcement mail. It will probably disappear with CHICKEN 4.11, if it includes the new argvector branch. If you would like to run the tests through to completion on this platform you can try installing the gcc-4.8 package or clang, and set the C_COMPILER variable to this compiler. Hmm, this is strange, I tried with a previous version of the GCC compiler (4.8: $ make PLATFORM=linux C_COMPILER=gcc-4.8 PREFIX=/home/tim/chicken-test/ install check Again, same thing, stuck for over two hours on that same step. So, I decided to try Clang: $ make PLATFORM=linux C_COMPILER=clang PREFIX=/home/tim/chicken-test/ install check Again, same thing. Before every run I clear out my build area so no remnants of the previous run remain. In the first few lines of the process I can see it uses the compiler I set in the variable: How do you clear out the build area? I think you might be doing make clean, but that just cleans the built files, whereas make confclean will also clean the configuration, which is where the C_COMPILER is written to. This is documented in the README, by the way, but the consequences might not be immediately obvious. You can also just try deleting the dir and re-extracting the tarball. That will ensure that the build dir is clean. To my newbie eyes this looks like 'gcc' is hard-coded in there...somehow...? Whatever I do, it is picking up the correct compiler on start, but once the tests run it uses the default gcc setting...what am I messing up here? It gets hardcoded into chicken-config.h the first time you run make. If you run make with a different C_compiler later on, it will only use that C compiler to compile the C files, but csc will use the C compiler from chicken-config.h. The reason behind this probably is so that you can configure a C compiler which is different from the host compiler, for example when cross-compiling. It sure can be confusing, though :) Cheers, Peter signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] Homepage design proposal
Hi again! The prototype now runs on http://arthur.flnet.org:5280/ To test menu links, always go back to home page. The resonsive design can be tested shrinking windows widths. Best wishes, Arthur 2015-07-27 2:53 GMT-03:00 Arthur Maciel arthurmac...@gmail.com: Hi all! Since Tim's first proposal I've been thinking a lot about CHICKEN's website. Here are my two cents. Homepage - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Homepage.png - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Homepage-Mobile.png Eggs - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Eggs.png - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Eggs-Mobile.png Getting Started - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Getting%20Started.png Wiki - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Wiki.png Manual - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Manual.png Download - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Download.png Tests - https://dl.dropboxusercontent.com/u/621606/chicken-web-page/Tests.png I've chosen a minimalist approach and the focus was on readability - although the white background doesn't help much, I couldn't find a better solution. The content for the homepage is drawn from users comments on this thread (they are merely illustrative, although make sense to me). Most modifications were done to chicken.css file, so changes are immediately applicable to probably 90% of CHICKEN site (exceptions are api.call-cc.org and bugs.call-cc.org). To make the page responsive to narrow screens (i.e. mobiles) we would need to add one line of HTML into pages. This line is already inserted in the .html files on the https://dl.dropboxusercontent.com/u/621606/chicken-web-page/chicken-web-page.tar.gz bundle. It contains many .html files and I recommend opening CHICKEN Scheme.html first. The menu on this page has some directly browsable links (Get started! link at the bottom can also be clicked). Do you find it useful? Best wishes, Arthur PS: Tim, sorry for not continuing on your proposal. As I'm a newbie on web design, I preferred to stick with current code and modify it step by step, so I could understand what I was doing. Thanks for inspiration, especially on the grid section! And sorry for proposing something much simpler than your original design. ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
On Fri, Jul 24, 2015 at 01:33:24PM +0200, Peter Bex wrote: Hello everyone, The fourth release candidate for CHICKEN 4.10.0 is now available for download: http://code.call-cc.org/dev-snapshots/2015/07/24/chicken-4.10.0rc4.tar.gz (Slackwarearm 14.1 on Raspberry Pi 2) Operating system: GNU/Linux 3.18.9-v7-arm Hardware platform: armv71 C Compiler: GCC 4.9.2 Installation works?: yes Tests work?: yes Installation of eggs works?: yes Operating system: AIX 6.1 Hardware platform: PowerPC_POWER6 C Compiler: GCC 4.4.7 Installation works?: yes Tests work?: yes Installation of eggs works?: yes -- Erik Falor Registered Linux User #445632http://unnovative.net pgp1Nssfld4hk.pgp Description: PGP signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
On Jul 27, 2015, at 15:02, Peter Bex pe...@more-magic.net wrote: It gets hardcoded into chicken-config.h the first time you run make. If you run make with a different C_compiler later on, it will only use that C compiler to compile the C files, but csc will use the C compiler from chicken-config.h. The reason behind this probably is so that you can configure a C compiler which is different from the host compiler, for example when cross-compiling. It sure can be confusing, though :) I've debugged this problem some time ago. I barely remember that there was some issue with test environment itself, not the compiler. But, unfortunately, I forgot what it was exactly. AFAIR my CMake based test suite was able to run all tests just fine, but there was not much interest in including it into the core, so it stuck in works for me stage. — Regards, Oleg Art-System ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
Ok, here are some results for you, both on the same machine. The first may
be of interest because of the GCC version, which is 5.1.
CPU: AMD FX-8320E 8-core, 3.2 Ghz
Operating system: Arch Linux
Hardware platform: x86-64
C Compiler: gcc 5.1.0
Installation works?: yes
Tests work?: no [hangs on apply-test.scm]
Installation of eggs works?: not attempted
So it appears that whatever is causing apply-test.scm to hang is not yet
fixed in GCC 5.1 ... :-( . However, everything was fine with Clang:
Operating system: Arch Linux
Hardware platform: x86-64
C Compiler: clang 3.6.2
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes
'time' results
==
time make PLATFORM=linux C_COMPILER=clang PREFIX=/opt/chicken410 install
check
real 3m38.521s
user 3m5.263s
sys 0m7.263s
time /opt/chicken410/bin/chicken-install pastiche
real 3m54.964s
user 2m7.367s
sys 0m5.210s
On Fri, Jul 24, 2015 at 5:33 AM, Peter Bex pe...@more-magic.net wrote:
Hello everyone,
The fourth release candidate for CHICKEN 4.10.0 is now available for
download:
http://code.call-cc.org/dev-snapshots/2015/07/24/chicken-4.10.0rc4.tar.gz
This tarball has the following SHA-2 checksum:
8b20fbe77a47a04417eaada3a8ef2218e51dabf919957f7059f4d60ddb6e2ad5
The list of changes since version 4.9.0 is available here:
http://code.call-cc.org/dev-snapshots/2015/07/24/NEWS
The NEWS file incorrectly mentions rc3 instead of rc4, we apologise for
that.
The changes since 4.10.0rc1 are as follows:
- SIGBUS, SIGILL and SIGFPE cause proper exceptions instead of panicking
- string-translate* no longer scans beyond string boundaries
(CVE-2015-4556)
- A corner case bug in substring-index and substring-index-ci that was
introduced as part of the fix for CVE-2014-9651 has been fixed.
- chicken.h has been fixed so it does not cause an error in C++ mode.
- create-directory will not skip creation of topmost parent dir in Windows.
- The types.db entries for {read,write}-string read-u8vector have been
improved.
- The types.db entries for several SRFI-4 procedures have been fixed.
- The performance of read-u8vector has been improved.
- The scheme module now includes an export for the angle procedure.
- normalize-pathname no longer considers .//foo as the absolute /foo.
- A few small improvements have been made in the manual.
If you're wondering what happened to release candidate 2 and 3, the
rc2 was created but never announced, and rc3 was incorrectly versioned,
so it has been skipped. Sorry for that, as well :)
Please test this new version on as many platforms as you can, and let
us know if there are any problems with it. If no problems are found
we can make a 4.10.0 release soon.
As usual, you can test as follows:
$ make PLATFORM=platform PREFIX=some dir install check
$ some dir/bin/chicken-install pastiche
If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=the compiler (e.g., C_COMPILER=clang) on the make
invocation. This may be necessary if your default C compiler is a GCC
which is newer than 4.8, because there is a bug in those versions that
causes one of the tests (apply-test.scm) to hang for a very long time.
This is a known problem which we can't do much about.
If you can, please let us know the following information about the
environment you tested the RC tarball on:
Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.8.4, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no
Thanks in advance,
The CHICKEN Team
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
Hi Matt, On Mon, 27 Jul 2015 12:37:16 -0600 Matt Gushee m...@gushee.net wrote: Ok, here are some results for you, both on the same machine. The first may be of interest because of the GCC version, which is 5.1. CPU: AMD FX-8320E 8-core, 3.2 Ghz Operating system: Arch Linux Hardware platform: x86-64 C Compiler: gcc 5.1.0 Installation works?: yes Tests work?: no [hangs on apply-test.scm] Installation of eggs works?: not attempted So it appears that whatever is causing apply-test.scm to hang is not yet fixed in GCC 5.1 ... :-( . However, everything was fine with Thanks for sharing your findings. That test eventually finishes with success, if you wait long enough. :-) Some users reported that it may take about 2 hours. Best wishes. Mario -- http://parenteses.org/mario ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
And here's a result for FreeBSD 9.1:
This is a VPS, so I'm not sure if this info is accurate, but:
$ sysctl hw.model
hw.model: Intel(R) Xeon(TM) CPU 2.80GHz
$ sysctl hw.physmem
hw.physmem: 17166430208
[However, I'm pretty sure I don't really have access to that much memory]
Anyway:
Operating system: FreeBSD 9.1
Hardware platform: x86-64
C Compiler: gcc 4.2.1
Installation works?: yes
Tests work?: yes
Installation of eggs works?: yes
timings
==
time gmake PLATFORM=bsd PREFIX=/opt/chicken410rc4 install check
real 15m37.533s
user 14m30.196s
sys 0m30.172s
time /opt/chicken410rc4/bin/chicken-install pastiche
real 10m38.702s
user 9m5.376s
sys 0m21.890s
On Fri, Jul 24, 2015 at 5:33 AM, Peter Bex pe...@more-magic.net wrote:
Hello everyone,
The fourth release candidate for CHICKEN 4.10.0 is now available for
download:
http://code.call-cc.org/dev-snapshots/2015/07/24/chicken-4.10.0rc4.tar.gz
This tarball has the following SHA-2 checksum:
8b20fbe77a47a04417eaada3a8ef2218e51dabf919957f7059f4d60ddb6e2ad5
The list of changes since version 4.9.0 is available here:
http://code.call-cc.org/dev-snapshots/2015/07/24/NEWS
The NEWS file incorrectly mentions rc3 instead of rc4, we apologise for
that.
The changes since 4.10.0rc1 are as follows:
- SIGBUS, SIGILL and SIGFPE cause proper exceptions instead of panicking
- string-translate* no longer scans beyond string boundaries
(CVE-2015-4556)
- A corner case bug in substring-index and substring-index-ci that was
introduced as part of the fix for CVE-2014-9651 has been fixed.
- chicken.h has been fixed so it does not cause an error in C++ mode.
- create-directory will not skip creation of topmost parent dir in Windows.
- The types.db entries for {read,write}-string read-u8vector have been
improved.
- The types.db entries for several SRFI-4 procedures have been fixed.
- The performance of read-u8vector has been improved.
- The scheme module now includes an export for the angle procedure.
- normalize-pathname no longer considers .//foo as the absolute /foo.
- A few small improvements have been made in the manual.
If you're wondering what happened to release candidate 2 and 3, the
rc2 was created but never announced, and rc3 was incorrectly versioned,
so it has been skipped. Sorry for that, as well :)
Please test this new version on as many platforms as you can, and let
us know if there are any problems with it. If no problems are found
we can make a 4.10.0 release soon.
As usual, you can test as follows:
$ make PLATFORM=platform PREFIX=some dir install check
$ some dir/bin/chicken-install pastiche
If you want to build CHICKEN with a compiler other than the default one,
just use C_COMPILER=the compiler (e.g., C_COMPILER=clang) on the make
invocation. This may be necessary if your default C compiler is a GCC
which is newer than 4.8, because there is a bug in those versions that
causes one of the tests (apply-test.scm) to hang for a very long time.
This is a known problem which we can't do much about.
If you can, please let us know the following information about the
environment you tested the RC tarball on:
Operating system: (e.g., FreeBSD 10.1, Debian 8, Windows 7 mingw-msys)
Hardware platform: (e.g., x86, x86-64, PPC)
C Compiler: (e.g., GCC 4.8.4, clang 3.6)
Installation works?: yes or no
Tests work?: yes or no
Installation of eggs works?: yes or no
Thanks in advance,
The CHICKEN Team
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
Hi, Mario-- On Mon, Jul 27, 2015 at 12:42 PM, Mario Domenech Goulart mario.goul...@gmail.com wrote: On Mon, 27 Jul 2015 12:37:16 -0600 Matt Gushee m...@gushee.net wrote: Tests work?: no [hangs on apply-test.scm] Installation of eggs works?: not attempted So it appears that whatever is causing apply-test.scm to hang is not yet fixed in GCC 5.1 ... :-( . However, everything was fine with That test eventually finishes with success, if you wait long enough. :-) So I gathered. I was not willing to wait long enough. -- Matt Gushee ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
On Fri, 24 Jul 2015 13:33:24 +0200 Peter Bex pe...@more-magic.net wrote: Hello everyone, Hi Gang, The fourth release candidate for CHICKEN 4.10.0 is now available for download: http://code.call-cc.org/dev-snapshots/2015/07/24/chicken-4.10.0rc4.tar.gz Nice! Thanks for the persistent hard work in pushing this forward. Hoping to do more with CHICKEN in the future, for now I can help to test at least. ... As usual, you can test as follows: $ make PLATFORM=platform PREFIX=some dir install check $ some dir/bin/chicken-install pastiche Installed tested on two different systems: 1. Debian 7 - 8 Core i7-4790K CPUs @ 4.00GHz - 8 Gb of DDR3 1600 RAM Total install and test time: 72.011 seconds. - Operating system: Debian 7.8 (Wheezy) - Hardware platform: x86-64 - C Compiler: GCC 4.7.2 - Installation works?: Yes, no errors - Tests work?: Yes, no errors - Installation of eggs works?: Yes, no errors (installed the Pastiche egg) 2. Debian 8 - 4 Atom CPUs D525 @ 1.80GHz - 4 Gb of DDR2 800 RAM Total install and test time: did not complete. - Operating system: Debian 8.1 (Jessie) - Hardware platform: x86-64 - C Compiler: GCC 4.9.2 - Installation works?: Yes, no errors - Tests work?: No, possible error - Installation of eggs works?: Unknown Output during tests on this Atom system: callback tests ... /home/tim/chicken-test/chicken-4.10.0rc4/tests/../chicken 'callback-tests.scm' -output-file 'a.c' -types ../types.db -ignore-repository -verbose -include-path /home/tim/chicken-test/chicken-4.10.0rc4/tests/.. 'gcc' 'a.c' -o 'a.o' -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -I/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -I/home/tim/chicken-test//include/chicken rm a.c 'gcc' 'a.o' -o 'a.out' -L/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -Wl,-R/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -L/home/tim/chicken-test//lib -Wl,-R/home/tim/chicken-test//lib -lchicken -lm -ldl rm a.o callbacks ... hi! callbacks ... hi! hi! [panic] callback returned twice - execution terminated callback-tests.scm:16: print callback-tests.scm:17: ##sys#gc callback-tests.scm:17: g11 callback-tests.scm:7: call/cc callback-tests.scm:9: print callback-tests.scm:19: command-line-arguments callback-tests.scm:20: k1 callback-tests.scm:9: print -- double-return from callback failed as it should. runtime tests ... many arguments supported. testing 'apply' with 0..2048 (maximum apply argument count)... If this segfaults on x86-64, try updating GCC (4.5 has a code-generation bug): invoking directly with 0..50... invoking directly with 1998..2048 (maximum interpreted direct argument count)... testing 'apply' can detect calls of too many arguments... testing direct invocation can detect calls of too many arguments... /home/tim/chicken-test/chicken-4.10.0rc4/tests/../chicken 'apply-test.scm' -output-file 'a.c' -types ../types.db -ignore-repository -verbose -include-path /home/tim/chicken-test/chicken-4.10.0rc4/tests/.. 'gcc' 'a.c' -o 'a.o' -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -I/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -I/home/tim/chicken-test//include/chicken The [panic] line (marked with in front) might be a possible failed test? Furthermore, as you can see, the system does progress a bit but hangs at the last line. I have let it run for 2 hours, and it did not get past this GCC compiling step. Either this Atom system is too weak to run these test in a timely fashion, or something else is going wrong... ... Thanks in advance, The CHICKEN Team I hope these metrics are of use! Cheers, Tim ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
On Mon, 27 Jul 2015 18:51:53 +1200 Evan Hanson ev...@foldling.org wrote: Hi Tim, Hi Evan (and Sven) Thanks for the report, it's much appreciated. You are welcome, happy to help out. On 2015-07-27 15:31, Tim van der Linden wrote: The [panic] line (marked with in front) might be a possible failed test? That panic line is fine and expected -- it's part of the test. Understood. Furthermore, as you can see, the system does progress a bit but hangs at the last line. I have let it run for 2 hours, and it did not get past this GCC compiling step. Either this Atom system is too weak to run these test in a timely fashion, or something else is going wrong... Looks like you're running into an issue with GCC 4.9 that a few others have encountered, as well -- the runtime tests do indeed run indefinitely on some platforms when that compiler is used.9. If possible, could you rerun that build with C_PLATFORM=some other gcc so that we can see the whether the remaining tests pass, that GCC bug notwithstanding? Damn, I feel like an idiot ... reread Peter's announcement and it clearly states this issue with GCC versions above 4.8. Sorry for the noise folks. I'm now rerunning the full install/test with GCC 4.8 on the Atom system ... will report back soon. Thanks again, Evan Cheers, Tim ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
Hi Tim. Tim wrote: many arguments supported. testing 'apply' with 0..2048 (maximum apply argument count)... If this segfaults on x86-64, try updating GCC (4.5 has a code-generation bug): invoking directly with 0..50... invoking directly with 1998..2048 (maximum interpreted direct argument count)... testing 'apply' can detect calls of too many arguments... testing direct invocation can detect calls of too many arguments... /home/tim/chicken-test/chicken-4.10.0rc4/tests/../chicken 'apply-test.scm' -output-file 'a.c' -types ../types.db -ignore-repository -verbose -include-path /home/tim/chicken-test/chicken-4.10.0rc4/tests/.. 'gcc' 'a.c' -o 'a.o' -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -I/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -I/home/tim/chicken-test//include/chicken The [panic] line (marked with in front) might be a possible failed test? Furthermore, as you can see, the system does progress a bit but hangs at the last line. I have let it run for 2 hours, and it did not get past this GCC compiling step. Either this Atom system is too weak to run these test in a timely fashion, or something else is going wrong... This is a known problem with newer GCC versions. Your 2nd machine will need 4 hours or more :-( Ciao Sven ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] CHICKEN 4.10.0 release candidate 4 available
Hi Tim, Thanks for the report, it's much appreciated. On 2015-07-27 15:31, Tim van der Linden wrote: The [panic] line (marked with in front) might be a possible failed test? That panic line is fine and expected -- it's part of the test. Furthermore, as you can see, the system does progress a bit but hangs at the last line. I have let it run for 2 hours, and it did not get past this GCC compiling step. Either this Atom system is too weak to run these test in a timely fashion, or something else is going wrong... Looks like you're running into an issue with GCC 4.9 that a few others have encountered, as well -- the runtime tests do indeed run indefinitely on some platforms when that compiler is used.9. If possible, could you rerun that build with C_PLATFORM=some other gcc so that we can see the whether the remaining tests pass, that GCC bug notwithstanding? Thanks again, Evan ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] [Chicken-announce] CHICKEN 4.10.0 release candidate 4 available
On Mon, Jul 27, 2015 at 08:47:56AM +0200, Sven Hartrumpf wrote: Hi Tim. Tim wrote: many arguments supported. testing 'apply' with 0..2048 (maximum apply argument count)... If this segfaults on x86-64, try updating GCC (4.5 has a code-generation bug): invoking directly with 0..50... invoking directly with 1998..2048 (maximum interpreted direct argument count)... testing 'apply' can detect calls of too many arguments... testing direct invocation can detect calls of too many arguments... /home/tim/chicken-test/chicken-4.10.0rc4/tests/../chicken 'apply-test.scm' -output-file 'a.c' -types ../types.db -ignore-repository -verbose -include-path /home/tim/chicken-test/chicken-4.10.0rc4/tests/.. 'gcc' 'a.c' -o 'a.o' -c -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENABLE_PTABLES -Os -fomit-frame-pointer -I/home/tim/chicken-test/chicken-4.10.0rc4/tests/.. -I/home/tim/chicken-test//include/chicken The [panic] line (marked with in front) might be a possible failed test? Furthermore, as you can see, the system does progress a bit but hangs at the last line. I have let it run for 2 hours, and it did not get past this GCC compiling step. Either this Atom system is too weak to run these test in a timely fashion, or something else is going wrong... This is a known problem with newer GCC versions. Your 2nd machine will need 4 hours or more :-( Correct; the [panic] you noted is actually part of the test; it checks that returning twice from a callback fails (which _should_ trigger a panic). That's why it says double-return from callback failed as it should. I agree this is somewhat surprising. The GCC bug is known; I tried to explain this in the RC announcement mail. It will probably disappear with CHICKEN 4.11, if it includes the new argvector branch. If you would like to run the tests through to completion on this platform you can try installing the gcc-4.8 package or clang, and set the C_COMPILER variable to this compiler. Anyway, thanks for testing, Tim! Cheers, Peter signature.asc Description: Digital signature ___ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
