X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/acfa068f4a1a4652b784af1d7aaac92929399249..7a91562ff0ea0033add100295a52ded5a8be0d9b:/etc/PROBLEMS diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 4edab8a41d..441ad7b4df 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -1,7 +1,7 @@ Known Problems with GNU Emacs -Copyright (C) 1987-1989, 1993-1999, 2001-2012 - Free Software Foundation, Inc. +Copyright (C) 1987-1989, 1993-1999, 2001-2013 Free Software Foundation, +Inc. See the end of the file for license conditions. @@ -3198,39 +3198,6 @@ floating point option: -fsoft. This seems to be due to a GCC bug; it is fixed in GCC 2.8.1. -** Vax C compiler bugs affecting Emacs. - -You may get one of these problems compiling Emacs: - - foo.c line nnn: compiler error: no table entry for op STASG - foo.c: fatal error in /lib/ccom - -These are due to bugs in the C compiler; the code is valid C. -Unfortunately, the bugs are unpredictable: the same construct -may compile properly or trigger one of these bugs, depending -on what else is in the source file being compiled. Even changes -in header files that should not affect the file being compiled -can affect whether the bug happens. In addition, sometimes files -that compile correctly on one machine get this bug on another machine. - -As a result, it is hard for me to make sure this bug will not affect -you. I have attempted to find and alter these constructs, but more -can always appear. However, I can tell you how to deal with it if it -should happen. The bug comes from having an indexed reference to an -array of Lisp_Objects, as an argument in a function call: - Lisp_Object *args; - ... - ... foo (5, args[i], ...)... -putting the argument into a temporary variable first, as in - Lisp_Object *args; - Lisp_Object tem; - ... - tem = args[i]; - ... foo (r, tem, ...)... -causes the problem to go away. -The `contents' field of a Lisp vector is an array of Lisp_Objects, -so you may see the problem happening with indexed references to that. - This file is part of GNU Emacs.