0
|
1 /* machine description file for Data General AViiON.
|
|
2 Copyright (C) 1985, 1986, 1991 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 /* Define WORD_MACHINE if addresses and such have
|
|
24 * to be corrected before they can be used as byte counts. */
|
|
25
|
|
26 #define WORD_MACHINE
|
|
27
|
|
28 /* Define DATA_SEG_BITS if pointers need to be corrected with
|
|
29 a segment field. */
|
|
30
|
|
31 #ifdef FIX_ADDRESS
|
|
32 #define DATA_SEG_BITS 0xef000000
|
|
33 #endif
|
|
34
|
|
35 /* Now define a symbol for the cpu type, if your compiler
|
|
36 does not define it automatically:
|
|
37 Ones defined so far include vax, m68000, ns16000, pyramid,
|
|
38 orion, tahoe, APOLLO and many others */
|
|
39
|
82
|
40 /*#ifndef m88k*/
|
|
41 /*#define m88k*/
|
|
42 /*#endif*/
|
0
|
43
|
|
44 /* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend
|
|
45 the bit field into an int. In other words, if bit fields
|
|
46 are always unsigned.
|
|
47
|
|
48 If you use NO_UNION_TYPE, this flag does not matter. */
|
|
49
|
|
50 #define EXPLICIT_SIGN_EXTEND
|
|
51
|
|
52 /* Data type of load average, as read out of kmem. */
|
|
53
|
|
54 /* #define LOAD_AVE_TYPE long */
|
|
55
|
|
56 /* Convert that into an integer that is 100 for a load average of 1.0 */
|
|
57
|
|
58 /* #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE) */
|
|
59
|
|
60 /* Define CANNOT_DUMP on machines where unexec does not work.
|
|
61 Then the function dump-emacs will not be defined
|
|
62 and temacs will do (load "loadup") automatically unless told otherwise. */
|
|
63
|
|
64 /* #define CANNOT_DUMP */
|
|
65
|
|
66 /* Define VIRT_ADDR_VARIES if the virtual addresses of
|
|
67 pure and impure space as loaded can vary, and even their
|
|
68 relative order cannot be relied on.
|
|
69
|
|
70 Otherwise Emacs assumes that text space precedes data space,
|
|
71 numerically. */
|
|
72
|
|
73 /* #define VIRT_ADDR_VARIES */
|
|
74
|
|
75 /* Define C_ALLOCA if this machine does not support a true alloca
|
|
76 and the one written in C should be used instead.
|
|
77 Define HAVE_ALLOCA to say that the system provides a properly
|
|
78 working alloca function and it should be used.
|
|
79 Define neither one if an assembler-language alloca
|
|
80 in the file alloca.s should be used. */
|
|
81
|
|
82 /* #define C_ALLOCA */
|
|
83 #define HAVE_ALLOCA
|
|
84 #define alloca(x) __builtin_alloca(x)
|
|
85
|
|
86 /* Define NO_REMAP if memory segmentation makes it not work well
|
|
87 to change the boundary between the text section and data section
|
|
88 when Emacs is dumped. If you define this, the preloaded Lisp
|
|
89 code will not be sharable; but that's better than failing completely. */
|
|
90
|
|
91 #define NO_REMAP
|
|
92
|
|
93 /* Define ADDR_CORRECT(ADDR) to be a macro to correct an int which is
|
|
94 the bit pattern of a pointer to a byte into an int which is the
|
|
95 number of a byte.
|
|
96
|
|
97 This macro has a default definition which is usually right.
|
|
98 This default definition is a no-op on most machines (where a
|
|
99 pointer looks like an int) but not on all machines. */
|
|
100
|
|
101 #define ADDR_CORRECT(ADDR) ((int)ADDR)
|
|
102
|
|
103 /* Some machines that use COFF executables require that each section
|
|
104 start on a certain boundary *in the COFF file*. Such machines should
|
|
105 define SECTION_ALIGNMENT to a mask of the low-order bits that must be
|
|
106 zero on such a boundary. This mask is used to control padding between
|
|
107 segments in the COFF file.
|
|
108
|
|
109 If SECTION_ALIGNMENT is not defined, the segments are written
|
|
110 consecutively with no attempt at alignment. This is right for
|
|
111 unmodified system V. */
|
|
112
|
|
113 #define SECTION_ALIGNMENT 0x7
|
|
114
|