There's a new version of gforth available. I can't even remember how long ago the current version came out! I'll be testing on my AMD64 from upstream, probably tonight. :) Here's the announcement: You can find the latest snapshot on http://www.complang.tuwien.ac.at/forth/gforth/Snapshots/gforth-0.6.9-20070604.tar.gz It has not had much portability testing, and some things are still incomplete. User-visible changes between 0.6.2 and 0.6.9 (up to 2007-06-01): Installation: support for DESTDIR, POST_INSTALL, INSTALL_SCRIPT report performance and functionality problems at end of "make" Bug fixes Now works with address-space randomization. The single-step debugger works again in some engines. Many others. Ports: AMD64, ARM, IA-64 (Itanium): better performance PPC: disassembler and assembler (32-bit) Gforth EC: R8C, Lego NXT (complete?) Invocation: New flags --ignore-async-signals, --vm-commit (default overcommit) Forth 200x: extension queries (produce true for all implemented extensions) REQUIRED etc. (not new) [DEFINED] and [UNDEFINED] PARSE-NAME (new name) deferred words (new: DEFER@ DEFER! ACTION-OF) Unicode support (incomplete, documentation probably not up-to-date): added xchars words for dealing with variable-width multi-byte characters provide 8bit (ISO Latin 1) and UTF-8 support for xchars Number prefixes: 0x is a hex prefix: 0xff and 0XfF now produces (decimal) 255 # is a decimal prefix: #10 now produces (decimal) 10 ' now only handles a single (x)char: 'ab is no longer accepted, 'a' now produces (decimal) 97 New words: \C C-FUNCTION (C interface) OUTFILE-EXECUTE INFILE-EXECUTE BASE-EXECUTE (limited change of global state) 16-bit and 32-bit memory acces: UW@ UL@ SW@ SL@ W! L! W@ L@ /W /L NEXT-ARG SHIFT-ARGS (OS command-line argument processing) NOTHROW (for backtrace control) FTRUNC FMOD (undocumented) Improvements/changes of existing words: TRY...ENDTRY changed significantly, compatibility files available (see docs). The disassembler (DISCODE) can now use gdb to disassemble code Uninitialized defered words now give a warning when executed Division is floored (disable with "configure --enable-force-cdiv") Gforth (not gforth-fast) reports division by zero and overflow on division on all platforms. Newly documented words: S>NUMBER? S>UNUMBER? EKEY keypress names: K-LEFT K-RIGHT K-UP K-DOWN K-HOME K-END K-PRIOR K-NEXT K-INSERT K-DELETE K1 K2 K3 K4 K5 K6 K7 K8 K9 K10 K11 K12 S-K1 S-K2 S-K3 S-K4 S-K5 S-K6 S-K7 S-K8 S-K9 S-K10 S-K11 S-K12 CLEARSTACKS FORM Environment variable GFORTHSYSTEMPREFIX (used by word SYSTEM and friends) C interface: exported symbols now start with "gforth_" (for referencing them from C code) support for use of libffi (supplied with gcc) and a C-compiler-based approach (requires C compiler at run-time) (incomplete). Libraries: depth-changes.fs: report stack depth changes during interpretation ans-report.fs now reports CfV extensions fsl-util.4th: FSL support files (undocumented) regexp.fs for regular expressions (undocumented) complex.fs for complex numbers (undocumented) fft.fs for Fast Fourier Transform (undocumented) wf.fs, a Wiki implementation (undocumented) httpd.fs, a web server (undocumented) status.fs, show interpreter status in separate xterm (undocumented) profile.fs for profiling (undocumented, incomplete) endtry-iferror.fs, recover-endtry.fs to ease the TRY change transition compat library: compat/execute-parsing.fs Speed improvements: static stack caching (good speedup on PPC) mixed-precision division is now faster support for int128 types on AMD64 workarounds for gcc performance bugs (in particular, PR 15242) - anton --------------------------------------------------------------------- To unsubscribe, e-mail: gforth-unsubscribe@chaossolutions.org For additional commands, e-mail: gforth-help@chaossolutions.org
preliminary test results: works fine on AMD64, crashes on Athlon Thunderbird, both with both of the performance enhancement options enabled and GCC 4.1.2. I'm going to play around a bit with the Thunderbird version before sending it upstream, but the vanilla version will play on the Athlon Thunderbird. I have no more Pentia upon which to test. ;)
(In reply to comment #1) > preliminary test results: works fine on AMD64, crashes on Athlon Thunderbird, > both with both of the performance enhancement options enabled and GCC 4.1.2. > I'm going to play around a bit with the Thunderbird version before sending it > upstream, but the vanilla version will play on the Athlon Thunderbird. I have > no more Pentia upon which to test. ;) > Anton Ertl just released a new snapshot, so this package is still alive and kicking upstream. I've been building in off and on from CVS over the past couple of months on my AMD64 and it works fine. The email is attached.
Created attachment 160851 [details] Announcement of latest snapshot
(In reply to comment #2) > (In reply to comment #1) > > preliminary test results: works fine on AMD64, crashes on Athlon Thunderbird, > > both with both of the performance enhancement options enabled and GCC 4.1.2. > > I'm going to play around a bit with the Thunderbird version before sending it > > upstream, but the vanilla version will play on the Athlon Thunderbird. I have > > no more Pentia upon which to test. ;) > > > > Anton Ertl just released a new snapshot, so this package is still alive and > kicking upstream. I've been building in off and on from CVS over the past > couple of months on my AMD64 and it works fine. The email is attached. > Builds fine on my Athlon64 X2 / 2.6.26 / gcc 4.3.1. That's not a great surprise since the CVS code has been running for a few weeks.
(In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #1) > > > preliminary test results: works fine on AMD64, crashes on Athlon Thunderbird, > > > both with both of the performance enhancement options enabled and GCC 4.1.2. > > > I'm going to play around a bit with the Thunderbird version before sending it > > > upstream, but the vanilla version will play on the Athlon Thunderbird. I have > > > no more Pentia upon which to test. ;) > > > > > > > Anton Ertl just released a new snapshot, so this package is still alive and > > kicking upstream. I've been building in off and on from CVS over the past > > couple of months on my AMD64 and it works fine. The email is attached. > > > > Builds fine on my Athlon64 X2 / 2.6.26 / gcc 4.3.1. That's not a great surprise > since the CVS code has been running for a few weeks. > Do you have an ebuild for the latest version?
http://directory.fsf.org/project/gforth/ - still shows 0.6.2. ftp://ftp.gnu.org/gnu/gforth/ - still shows 0.6.2 Do we trust this snapshot directory? Is it a fork? What is the deal?
(In reply to comment #6) > http://directory.fsf.org/project/gforth/ - still shows 0.6.2. > > ftp://ftp.gnu.org/gnu/gforth/ - still shows 0.6.2 > > Do we trust this snapshot directory? Is it a fork? What is the deal? > gForth 0.6.2 is quite old. The master source in the GNU repositories probably hasn't been updated. Anton Ertl's 0.6.9 tarball is probably the right one to go into the tree, but I don't know what needs to be done to the ebuild to make that happen. Anton is usually pretty good about responding to questions, bug reports, etc., on the gForth mailing list. I guess the thing to do is leave this package "maintainer needed" and send out an announcement that it's leaving the tree if no one picks it up in 30 days. That should clarify things a bit. :)
gforth 0.7.0 was released on 2008/11/02, and is available at: ftp://ftp.gnu.org/pub/gnu/gforth/gforth-0.7.0.tar.gz I'm attaching the ebuild I put together for gforth 0.7.0 because the 0.6.2 build breaks on my amd64 machine. I did some very basic testing on stable x86 and amd64. I do get a QA notice about an executable stack for: * RWX --- --- usr/lib/gforth/0.7.0/libcc-named/fflib.so.0.0.0 Not sure how to address that.
Created attachment 176492 [details] ebuild for gforth-0.7.0
Wheeeeee: +*gforth-0.7.0 (04 Jan 2009) + + 04 Jan 2009; Patrick Lauer <patrick@gentoo.org> +gforth-0.7.0.ebuild: + Bumping to 0.7. Fixes #180918. Thanks to Scott McClung for the ebuild +
