1 /* machine description file template.
2 Copyright (C) 1985, 1986 Free Software Foundation, Inc.
4 This file is part of GNU Emacs.
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)
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.
16 You should have received a copy of the GNU General Public License
17 along with GNU Emacs; see the file COPYING. If not, write to
18 the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. */
21 /* The following line tells the configuration script what sort of
22 operating system this machine is likely to run.
23 USUAL-OPSYS="<name of system .h file here, without the s- or .h>" */
25 /* The following three symbols give information on
26 the size of various data types. */
28 #define SHORTBITS 16 /* Number of bits in a short */
30 #define INTBITS 32 /* Number of bits in an int */
32 #define LONGBITS 32 /* Number of bits in a long */
34 /* Define BIG_ENDIAN iff lowest-numbered byte in a word
35 is the most significant byte. */
39 /* Define NO_ARG_ARRAY if you cannot take the address of the first of a
40 * group of arguments and treat it as an array of the arguments. */
44 /* Define WORD_MACHINE if addresses and such have
45 * to be corrected before they can be used as byte counts. */
49 /* Now define a symbol for the cpu type, if your compiler
50 does not define it automatically:
51 Ones defined so far include vax, m68000, ns16000, pyramid,
52 orion, tahoe, APOLLO and many others */
54 /* Use type int rather than a union, to represent Lisp_Object */
55 /* This is desirable for most machines. */
59 /* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend
60 the 24-bit bit field into an int. In other words, if bit fields
63 If you use NO_UNION_TYPE, this flag does not matter. */
65 #define EXPLICIT_SIGN_EXTEND
67 /* Data type of load average, as read out of kmem. */
69 #define LOAD_AVE_TYPE long
71 /* Convert that into an integer that is 100 for a load average of 1.0 */
73 #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE)
75 /* Define CANNOT_DUMP on machines where unexec does not work.
76 Then the function dump-emacs will not be defined
77 and temacs will do (load "loadup") automatically unless told otherwise. */
81 /* Define VIRT_ADDR_VARIES if the virtual addresses of
82 pure and impure space as loaded can vary, and even their
83 relative order cannot be relied on.
85 Otherwise Emacs assumes that text space precedes data space,
88 #define VIRT_ADDR_VARIES
90 /* Define C_ALLOCA if this machine does not support a true alloca
91 and the one written in C should be used instead.
92 Define HAVE_ALLOCA to say that the system provides a properly
93 working alloca function and it should be used.
94 Define neither one if an assembler-language alloca
95 in the file alloca.s should be used. */
100 /* Define NO_REMAP if memory segmentation makes it not work well
101 to change the boundary between the text section and data section
102 when Emacs is dumped. If you define this, the preloaded Lisp
103 code will not be sharable; but that's better than failing completely. */
107 /* Some really obscure 4.2-based systems (like Sequent DYNIX)
108 * do not support asynchronous I/O (using SIGIO) on sockets,
109 * even though it works fine on tty's. If you have one of
110 * these systems, define the following, and then use it in
111 * config.h (or elsewhere) to decide when (not) to use SIGIO.
113 * You'd think this would go in an operating-system description file,
114 * but since it only occurs on some, but not all, BSD systems, the
115 * reasonable place to select for it is in the machine description
119 #define NO_SOCK_SIGIO
122 /* After adding support for a new system, modify the large case
123 statement in the `configure' script to recognize reasonable
124 configuration names, and add a description of the system to
127 If you've just fixed a problem in an existing configuration file,
128 you should also check `etc/MACHINES' to make sure its descriptions
129 of known problems in that configuration should be updated. */