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