| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
(I hadn't needed before, since didn't have other libraries
installed that it tried to detect.)
|
|
dot uji dot es> in PR 23635.
User-visible changes between 0.6.1 and 0.6.2:
Bug fixes (in particular, gforth-0.6.2 compiles with gcc-3.3)
New words: LATEST, LATESTXT (LASTXT deprecated)
Operating environment: Added optional support for a C interface built
on the ffcall libraries (more portable and powerful than the old
one, but still not documented). To use it, the ffcall libraries
have to be installed before building Gforth (see INSTALL).
Miscellaneous: Gforth-fast now uses static superinstructions (some
speedup on some platforms); generally this is transparent (apart
from the speedup), but there are lots of command-line options for
controlling the static superinstruction generation.
User-visible changes between 0.6.0 and 0.6.1:
Bug fixes (installation on big-endian machines sometimes did not work)
User-visible changes between 0.5.0 and 0.6.0:
Changes in behaviour:
S": interpreted use now ALLOCATEs the string (they live until BYE).
Long word names (512MB on 32-bit systems) are now supported (change to
the header format).
New threaded code execution method: primitive-centric (allows the
following), hybrid direct/indirect threaded (easier portability),
with dynamic superinstructions (typical speedup on Athlon: factor
2). New engine gforth-itc for dealing with some potential
backwards-compatibility problems (see "Direct or Indirect Threaded?"
in the manual).
Operating environment:
Default dictionary size is now 4MB.
Large file support on OSs that support them (i.e., files with more
than 2GB on 32-bit machines).
Gforth can now deal well with broken pipes in most situations.
vi tags files can be built with tags.fs (usage like etags.fs).
gforth.el mostly rewritten.
New image file format.
New words:
Keyboard input: EDIT-LINE K-PRIOR K-NEXT K-DELETE
File input: SLURP-FILE SLURP-FID
Programming tools: ID. .ID WORDLIST-WORDS SIMPLE-SEE
Conditional execution: [DEFINED] [UNDEFINED]
Defining Words: CONST-DOES> ]]
Input stream: PARSE-WORD EXECUTE-PARSING EXECUTE-PARSING-FILE
String comparison: STR= STR< STRING-PREFIX?
String literals: S\" .\" \"-PARSE
Floating point output: F.RDP F>STR-RDP F>BUF-RDP
Miscellaneous:
Generalized prims2x.fs into Vmgen (see README.vmgen etc.); used the
new capabilities in prims (e.g., automatic handling of the return
stack and instruction stream).
|
|
|
|
Force it to use /usr/bin/cc instead.
|
|
lots of updates fixes
see http://www.go-mono.com/archive/mono-0.29.html for details
|
|
Marc Recht pointed out that install is not the install command here but
rather an argument to the Python setup program.
|
|
|
|
|
|
from Christian Limpach wrt to signal handling.
Pull in FreeBSD fixes from the FreeBSD port and disable pthread for
NetBSD and FreeBSD for libgc.
Fix a sysconfdir related path problem.
bump PKGREVISION
|
|
|
|
also add logic for NetBSD/alpha.
|
|
on NetBSD/alpha versions 1.6 and newer. Previously, this package only
worked on pre-1.6. Fixes problems noted in recent bulk builds.
|
|
and also in package Makefiles.
|
|
compiler and linker. Use them to pass CPPFLAGS and LDFLAGS from pkgsrc.
|
|
package Makefiles can refer to the directory in which they install Perl5
site modules.
|
|
the PLIST for these.
|
|
|
|
|
|
CFLAGS:= ${CFLAGS:S/-ffast-math//}
No change on default builds (without -ffast-math)
|
|
get the base PLIST. Fixes recently noted problems on alpha bulk builds
that resulted in empty packages.
|
|
Bump PKGREVISION to 1. From Jorge Acereda in PR pkg/23359.
|
|
|
|
|
|
> 2 years ago. ressurect it.
|
|
fixes build problem of apache-ant in a recent bulk build. from rtr@.
|
|
to Sun's 1.4.2_02). This is done even though we are in a freeze since
older distfiles disappear and a security vulnerability in older versions
might make people update.
Changes/bugfixes since 1.4.2_01, according to
http://java.sun.com/j2se/1.4.2/ReleaseNotes.html
- Regression: IllegalStateException:constrain(xywh) not supp. for complex transform
- AsyncGetCallTrace() on Solaris/Intel core dumps with assertion failure
- occasional crashes/deadlocks from AsyncGetCallTrace()
- JVMPI_EVENT_COMPILED_ METHOD_LOAD: "must release all locks when leaving VM" asser
- Cannot set preferences factory in web start
- crash in AsyncGetCallTrace() when invoked during Deoptimization
- AsyncGetCallTrace() is absent in linux/Intel JVM
- infinite recursion in AsyncGetCallTrace() with the server JVM
- syncGetCallTrace: assert(pc_desc != 0, "scopeDesc must exist").
- AsyncGetCallTrace: guarantee(get_thread() == thread, "must be the same thread.
- JNI GetEnv() race with ThreadLocalStorage::set_thread() guarantee
- Cache versioning fails to work in 1.4.1 and higher releases
- Get/SetThreadLocalStorage need to work with AsyncGetCallTrace
- JInternalFrame setDefaultCloseOperation ignored under Motif look-and-feel.
- OBJ_ALLOC event deadlock between VMThread and Finalizer thread
- VM crash when HeapDump requested
- Util buffer cache uses wrong release strategy
- Need general-purpose way to dispatch object invocations on Java GUI thread
- Crash in OopFlow::build_oop_map
- [mercury] Java Setup menuitem location misleading
- Update cacerts file with GeoTrust root certs
- extra pings to server if WeakReferenced CachedJarLoaders gc'ed
- Size of sliders in GTK L&F larger than original
- Open/Closing buttons on split panes are very small
|
|
platform, and there are far worse offenders these days.
|
|
of the .html files are extracted in an incorrect location). Force
use of pax instead.
|
|
|
|
|
|
|
|
|
|
Darwin.
|
|
|
|
|
|
Changes from 3.1.2 to 3.1.3
---------------------------
1. Gawk now follows POSIX in handling of local numeric formats for
input, output and number/string conversions.
2. Multibyte detection improved. See README_d/README.multibyte for more
info about multibyte locales.
3. Handling of `close' made more POSIX-compliant for POSIXLY_CORRECT,
see the documentation.
4. The record reading code was redone, again. This time it's much
better. Really!
5. For RS = "\n" and RS = "", gawk now only sets RT when it has changed.
This provides considerable performance improvement.
6. `match' now sets all the subscripts in the third argument array
correctly, even if not all subexpressions matched.
7. Updated to Automake 1.7.5. configure.in renamed configure.ac.
8. C-style switch statements are available, but must be enabled at
compile time via `configure --enable-switch'. For 3.2 they'll be
enabled by default. Thanks to Michael Benzinger for the initial
code.
9. %c now always prints no more than one character, whatever
precision is provided.
10. strtonum(<number>) now works again.
11. Gawk is now much better about scalar/array typing of global
uninitiailzed variables passed as parameters. Once the parameter
is then used one way or the other, the global var's type is
adjusted accordingly. Thanks to Stepan Kasal for the original
(considerable) changes.
12. Dynamic function loading under Windows32 should now be possible. See
README_d/README.pcdynamic. Thanks to Patrick T.J. McPhee for the changes.
13. Updated to gettext 0.12.1.
14. Gawk now follows historical practice and POSIX for the return
value of `rand': It's now 0 <= N < 1.
Changes from 3.1.1 to 3.1.2
---------------------------
1. Loops of the form:
for (iggy in foo)
next
no longer leak memory.
2. gawk -v FIELDWIDTHS="..." now sets PROCINFO["FS"] correctly.
3. All builtin operations and functions should now fully evaluate their
arguments so that side effects take place correctly.
4. Fixed a logic bug in gsub/gensub for matches to null strings that occurred
later in the string after a nonnull match.
5. getgroups code now works on Ultrix again.
6. Completely new version of the full GNU regex engine now in place.
7. Argument parsing and variable assignment has been cleaned up.
8. An I/O bug on HP-UX has been documented and worked around. See
README_d/README.hpux.
9. awklib/grcat should now compile correctly.
10. Updated to automake 1.7.3, autoconf 2.57 and gettext 0.11.5 ; thanks to
Paul Eggert for the initial automake and autoconf work.
11. As a result of #6, removed the use of the dfa code from GNU grep.
12. It is now possible to use ptys for |& two-way pipes instead of
pipes. The basic plumbing for this was provided by Paolo Bonzini.
To make this happen:
command = "unix command etc"
PROCINFO[command, "pty"] = 1
print ... |& command
command |& getline stuff
In other words, set the element in PROCINFO *before* opening the
two-way pipe, and then gawk will use ptys instead of pipes.
On systems without ptys or where all the ptys are in use, gawk
will fall back to using plain pipes.
13. Fixed a regex matching across buffer boundaries bug, with a
heuristic. See io.c:rsre_get_a_record.
14. Profiling no longer dumps core if there are extension functions in place.
15. Grammar and scanner cleaned up, courtesy of Stepen Kasal, to hopefully
once and for all fix the `/=' operator vs. `/=.../' regex ambiguity.
Lots of other grammar simplifications applied, as well.
16. BINMODE should work now on more Windows ports.
17. Updated to bison 1.875. Includes fix to bisonfix.sed script.
18. The NODE structure is now 20% (8 bytes) smaller (on x86, anyway), which
should help conserve memory.
19. Builds not in the source directory should work again.
20. Arrays now use 2 NODE's per element instead of three. Combined with
#18, (on the x86) this reduces the overhead from 120 bytes per element
to just 64 bytes: almost a 50% improvement.
21. Programs that make heavy use of changing IGNORECASE should now be
much faster, particularly if using a regular expression for FS or RS.
IGNORECASE now correctly affects RS regex record splitting, as well.
22. IGNORECASE no longer affects single-character field splitting (FS = "c"),
or single-character record splitting (RS = "c").
This cleans up some weird behavior, and makes gawk better match the
documentation, which says it only affects regex-based field splitting
and record splitting.
The documentation on this was improved, too.
23. The framework in test/ has been simplified, making it much easier to
add new tests while keeping the size of Makefile.am reasonable. Thanks
for this to Stepan Kasal.
24. --lint=invalid causes lint warnings only about stuff that's actually
invalid. This needs additional work.
25. More translations.
26. The `get_a_record' routine has been revamped (currently by splitting it
into three variants). This should improve long-term maintainability.
27. `match' now adds more entries to 3rd array arg:
match("the big dog", /([a-z]+) ([a-z]+) ([a-z]+)/, data)
fills in variables:
data[1, "start"], data[1, "length"], and so on.
28. New `asorti' function with same interface as `asort', but sorts indices
instead of values.
29. Documentation updated to FDL 1.2.
30. New `configure' option --disable-lint at compile time disables lint
checking. With GCC dead-code-elimination, cuts almost 200K off the
executable size on GNU/Linux x86. Presumably speeds up runtime.
Using this will cause some of the tests in the test suite to fail.
This option may be removed at a later date.
31. Various minor cleanups, see the ChangeLog for details.
|
|
Editors", reported by Dima Veselov <kab00m@lich.phys.spbu.ru> in
private mail.
also move hints/ patches to patch-b* to keep track of them more
easily.
|
|
|
|
* Hash Randomisation
* UTF-8 On Filehandles No Longer Activated By Locale
* Single-number v-strings are no longer v-strings before "=>"
* UTF-8 no longer default under UTF-8 locales
* Unsafe signals again available
|
|
|
|
Initial import of scm-5d8 into the NetBSD Packages Collection. Provided in
PR 22186 by David S., modified slighly by myself.
Scm is a portable R5RS Scheme implementation written in C.
* Support for SICP, R2RS, R3RS, and R5RS scheme code.
* Is fully documented in TeXinfo form, allowing documentation to be
generated in info, TeX, html, nroff, and troff formats.
* Supports inexact real and complex numbers, 30 bit immediate integers
and large precision integers.
* Many Common Lisp functions: logand, logor, logxor, lognot, ash,
logcount, integer-length, bit-extract, defmacro, macroexpand,
macroexpand1, gentemp, defvar, force-output, software-type,
get-decoded-time, get-internal-run-time, get-internal-real-time,
delete-file, rename-file, copy-tree, acons, and eval.
* Char-code-limit, most-positive-fixnum, most-negative-fixnum, and
internal-time-units-per-second constants. *Features* and
*load-pathname* variables.
* Arrays and bit-vectors. String ports and software emulation ports.
I/O extensions providing ANSI C and POSIX.1 facilities.
* Interfaces to standard libraries
* Available add-on packages including an interactive debugger, database,
X-window graphics, BGI graphics, Motif, and Open-Windows packages.
* A compiler (HOBBIT) and dynamic linking of compiled modules.
* User definable responses to interrupts and errors,
Process-syncronization primitives. Setable levels of monitoring
and timing information printed interactively (the verbose function).
|
|
|
|
the ususal: new features and fixes
notably:
New Thread Locking
Zoltan removed the big locks we had in the runtime, and now we have a
finely grained lock system in the runtime. Runtime hackers can read the
included lock matrix document which describes the requirements to use
the new fine grained locks in their code.
Ahead of Time Compiler Optimizations
Zoltan has worked extensively on the Mono ahead-of-time compilation
feature (AOT). The AOT code is now considered to be production quality,
and also for the first time precompiled code runs faster than JITed
code. This resulted in a 13% compilation speed up for the Mono C#
compiler, reducing the compile time to 3.185 seconds. A clear goal of
the team for the next release is to reach 3.1416 seconds.
for a complete list see: http://www.go-mono.com/archive/mono-0.28.html
|
|
|
|
from the pkgsrc-wip pkg by Michal Pasternak
Psyco is a specializing compiler. In a few words let us first see:
What you can do with it
In short: run your existing Python software much faster, with no change in
your source.
Think of Psyco as a kind of just-in-time (JIT) compiler, a little bit like
Java's, that emit machine code on the fly instead of interpreting your Python
program step by step. The result is that your unmodified Python programs run
faster.
Benefits
2x to 100x speed-ups, typically 4x, with an unmodified Python interpreter and
unmodified source code, just a dynamically loadable C extension module.
Drawbacks
Psyco currently uses quite a lot of memory. It only runs on Intel
386-compatible processors (under any OS) right now. There are some subtle
semantic differences (i.e. bugs) with the way Python works; they should not be
apparent in most programs.
|
|
|
