0
|
1 /* machine description file template.
|
|
2 Copyright (C) 1985, 1986 Free Software Foundation, Inc.
|
|
3
|
|
4 This file is part of GNU Emacs.
|
|
5
|
|
6 GNU Emacs is free software; you can redistribute it and/or modify
|
|
7 it under the terms of the GNU General Public License as published by
|
|
8 the Free Software Foundation; either version 2, or (at your option)
|
|
9 any later version.
|
|
10
|
|
11 GNU Emacs is distributed in the hope that it will be useful,
|
|
12 but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
13 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
14 GNU General Public License for more details.
|
|
15
|
|
16 You should have received a copy of the GNU General Public License
|
|
17 along with XEmacs; see the file COPYING. If not, write to
|
|
18 the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
|
|
19 Boston, MA 02111-1307, USA. */
|
|
20
|
|
21 /* Synched up with: FSF 19.31. */
|
|
22
|
|
23 /* The following line tells the configuration script what sort of
|
|
24 operating system this machine is likely to run.
|
|
25 USUAL-OPSYS="<name of system .h file here, without the .h>" */
|
|
26
|
|
27 /* Define WORD_MACHINE if addresses and such have
|
|
28 * to be corrected before they can be used as byte counts. */
|
|
29
|
|
30 #define WORD_MACHINE
|
|
31
|
|
32 /* Now define a symbol for the cpu type, if your compiler
|
|
33 does not define it automatically:
|
|
34 Ones defined so far include vax, m68000, ns16000, pyramid,
|
|
35 orion, tahoe, APOLLO and many others */
|
|
36
|
|
37 /* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend
|
|
38 the bit field into an int. In other words, if bit fields
|
|
39 are always unsigned.
|
|
40
|
|
41 If you use NO_UNION_TYPE, this flag does not matter. */
|
|
42
|
|
43 #define EXPLICIT_SIGN_EXTEND
|
|
44
|
|
45 /* Data type of load average, as read out of kmem. */
|
|
46
|
|
47 #define LOAD_AVE_TYPE long
|
|
48
|
|
49 /* Convert that into an integer that is 100 for a load average of 1.0 */
|
|
50
|
|
51 #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE)
|
|
52
|
|
53 /* Define CANNOT_DUMP on machines where unexec does not work.
|
|
54 Then the function dump-emacs will not be defined
|
|
55 and temacs will do (load "loadup") automatically unless told otherwise. */
|
|
56
|
|
57 #define CANNOT_DUMP
|
|
58
|
|
59 /* Define VIRT_ADDR_VARIES if the virtual addresses of
|
|
60 pure and impure space as loaded can vary, and even their
|
|
61 relative order cannot be relied on.
|
|
62
|
|
63 Otherwise Emacs assumes that text space precedes data space,
|
|
64 numerically. */
|
|
65
|
|
66 #define VIRT_ADDR_VARIES
|
|
67
|
|
68 /* Define C_ALLOCA if this machine does not support a true alloca
|
|
69 and the one written in C should be used instead.
|
|
70 Define HAVE_ALLOCA to say that the system provides a properly
|
|
71 working alloca function and it should be used.
|
|
72 Define neither one if an assembler-language alloca
|
|
73 in the file alloca.s should be used. */
|
|
74
|
|
75 #define C_ALLOCA
|
|
76 #define HAVE_ALLOCA
|
|
77
|
|
78 /* Define NO_REMAP if memory segmentation makes it not work well
|
|
79 to change the boundary between the text section and data section
|
|
80 when Emacs is dumped. If you define this, the preloaded Lisp
|
|
81 code will not be sharable; but that's better than failing completely. */
|
|
82
|
|
83 #define NO_REMAP
|
|
84
|
|
85 /* Some really obscure 4.2-based systems (like Sequent DYNIX)
|
|
86 * do not support asynchronous I/O (using SIGIO) on sockets,
|
|
87 * even though it works fine on tty's. If you have one of
|
|
88 * these systems, define the following, and then use it in
|
|
89 * config.h (or elsewhere) to decide when (not) to use SIGIO.
|
|
90 *
|
|
91 * You'd think this would go in an operating-system description file,
|
|
92 * but since it only occurs on some, but not all, BSD systems, the
|
|
93 * reasonable place to select for it is in the machine description
|
|
94 * file.
|
|
95 */
|
|
96
|
|
97 #define NO_SOCK_SIGIO
|
|
98
|
|
99
|
|
100 /* After adding support for a new system, modify the large case
|
|
101 statement in the `configure' script to recognize reasonable
|
|
102 configuration names, and add a description of the system to
|
|
103 `etc/MACHINES'.
|
|
104
|
|
105 If you've just fixed a problem in an existing configuration file,
|
|
106 you should also check `etc/MACHINES' to make sure its descriptions
|
|
107 of known problems in that configuration should be updated. */
|