diff options
| author | Paul Eggert | 2013-02-10 16:35:37 -0800 |
|---|---|---|
| committer | Paul Eggert | 2013-02-10 16:35:37 -0800 |
| commit | e37778785ab978f64141e87392e8e651945f040e (patch) | |
| tree | 99e34afa8d138a540f7159c0b321b38a2ca97687 /etc/PROBLEMS | |
| parent | a4ba3963957c289a913b32bca9531aadcc3f377f (diff) | |
| download | emacs-e37778785ab978f64141e87392e8e651945f040e.tar.gz emacs-e37778785ab978f64141e87392e8e651945f040e.zip | |
Remove obsolete references to VAX in comments.
Diffstat (limited to 'etc/PROBLEMS')
| -rw-r--r-- | etc/PROBLEMS | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 2a588c159c9..441ad7b4df4 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS | |||
| @@ -3198,39 +3198,6 @@ floating point option: -fsoft. | |||
| 3198 | 3198 | ||
| 3199 | This seems to be due to a GCC bug; it is fixed in GCC 2.8.1. | 3199 | This seems to be due to a GCC bug; it is fixed in GCC 2.8.1. |
| 3200 | 3200 | ||
| 3201 | ** Vax C compiler bugs affecting Emacs. | ||
| 3202 | |||
| 3203 | You may get one of these problems compiling Emacs: | ||
| 3204 | |||
| 3205 | foo.c line nnn: compiler error: no table entry for op STASG | ||
| 3206 | foo.c: fatal error in /lib/ccom | ||
| 3207 | |||
| 3208 | These are due to bugs in the C compiler; the code is valid C. | ||
| 3209 | Unfortunately, the bugs are unpredictable: the same construct | ||
| 3210 | may compile properly or trigger one of these bugs, depending | ||
| 3211 | on what else is in the source file being compiled. Even changes | ||
| 3212 | in header files that should not affect the file being compiled | ||
| 3213 | can affect whether the bug happens. In addition, sometimes files | ||
| 3214 | that compile correctly on one machine get this bug on another machine. | ||
| 3215 | |||
| 3216 | As a result, it is hard for me to make sure this bug will not affect | ||
| 3217 | you. I have attempted to find and alter these constructs, but more | ||
| 3218 | can always appear. However, I can tell you how to deal with it if it | ||
| 3219 | should happen. The bug comes from having an indexed reference to an | ||
| 3220 | array of Lisp_Objects, as an argument in a function call: | ||
| 3221 | Lisp_Object *args; | ||
| 3222 | ... | ||
| 3223 | ... foo (5, args[i], ...)... | ||
| 3224 | putting the argument into a temporary variable first, as in | ||
| 3225 | Lisp_Object *args; | ||
| 3226 | Lisp_Object tem; | ||
| 3227 | ... | ||
| 3228 | tem = args[i]; | ||
| 3229 | ... foo (r, tem, ...)... | ||
| 3230 | causes the problem to go away. | ||
| 3231 | The `contents' field of a Lisp vector is an array of Lisp_Objects, | ||
| 3232 | so you may see the problem happening with indexed references to that. | ||
| 3233 | |||
| 3234 | 3201 | ||
| 3235 | This file is part of GNU Emacs. | 3202 | This file is part of GNU Emacs. |
| 3236 | 3203 | ||