--- gforth/BUGS	2000/10/28 08:49:02	1.47
+++ gforth/BUGS	2003/11/06 09:47:49	1.55
@@ -1,3 +1,6 @@
+You can find more recent bug reports at
+http://savannah.gnu.org/bugs/?group=gforth
+
 gforth.el: indentation does not work right on the first line of a
 buffer. anton 27jan95
 
@@ -34,3 +37,47 @@ Hendrix 3oct00 <8rdcmd$j96$1@news.IAEhv.
 
 Newline has only LF (instead of CRLF) in DOS.  Bruce Hoyt 25oct2000
 <39f7b14b$2@clear.net.nz>
+
+F. does not print trailing zeroes (e.g., "10 SET-PRECISION 125e f.")
+anton 31may01
+
+Block 0 does not work as it should: "0 block drop update save-buffers"
+does not write to the blocks file.  "0 block 1024 dump" seems to give
+the previous contents of the buffer.  Travis Bemann 10jul2001
+<3b4b4f57$0$42883$272ea4a1@news.execpc.com>
+
+When accessing a block beyond the end of the block file, the result is
+filled with spaces (this is also documented).  However, when accessing
+a previously unwritten block before the end of the block file, we will
+get a block full of zeroes on most (all?) OSs.  This inconsistency
+should be eliminated and the documentation fixed.  anton 14jul2001
+
+Path handling may have a bug:
+strace $FORTH 'fpath= .|~+/gforth s" /home/anton/threading-variations/gforth/mach32b.fs" include gforth/kernel/main.fs bye'
+tries to open gforth/kernel/gforth/kernel/aliases.fs, then
+gforth/gforth/kernel/aliases.fs, but not gforth/kernel/aliases.fs.
+anton 3 sep 2001
+
+gforth-native does not deal correctly with inline arguments in static
+superinstructions: when using lit_lit, the wrong literals are put into
+the native code (probably due to wrong assumptions about argument
+offsets).
+
+-----
+Copyright (C) 1995,1996,1997,1998,2000,2003 Free Software Foundation, Inc.
+
+This file is part of Gforth.
+
+Gforth is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.#See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.