[Emacs-diffs] Changes to emacs/src/m/aviion.h [lexbind]

[Miles Bader]

Index: emacs/src/m/aviion.h
diff -c /dev/null emacs/src/m/aviion.h:1.9.2.1
*** /dev/null   Tue Oct 14 19:22:55 2003
--- emacs/src/m/aviion.h        Tue Oct 14 19:22:52 2003
***************
*** 0 ****
--- 1,125 ----
+ /* machine description file for Data General AViiON.
+    Copyright (C) 1985, 1986, 1991, 2002 Free Software Foundation, Inc.
+ 
+ This file is part of GNU Emacs.
+ 
+ GNU Emacs is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2, or (at your option)
+ any later version.
+ 
+ GNU Emacs is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ 
+ You should have received a copy of the GNU General Public License
+ along with GNU Emacs; see the file COPYING.  If not, write to
+ the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ Boston, MA 02111-1307, USA.  */
+ 
+ 
+ /* Define WORDS_BIG_ENDIAN iff lowest-numbered byte in a word
+    is the most significant byte.  */
+ 
+ #define WORDS_BIG_ENDIAN
+ 
+ /* Define NO_ARG_ARRAY if you cannot take the address of the first of a
+  * group of arguments and treat it as an array of the arguments.  */
+ 
+ #define NO_ARG_ARRAY
+ 
+ /* Define WORD_MACHINE if addresses and such have
+  * to be corrected before they can be used as byte counts.  */
+ 
+ #define WORD_MACHINE
+ 
+ /* Define DATA_SEG_BITS if pointers need to be corrected with
+    a segment field.  */
+ 
+ #ifdef FIX_ADDRESS
+ #define DATA_SEG_BITS 0xef000000
+ #endif
+ 
+ /* Now define a symbol for the cpu type, if your compiler
+    does not define it automatically:
+    Ones defined so far include vax, m68000, ns16000, pyramid,
+    orion, tahoe, APOLLO and many others */
+ 
+ #ifndef m88k
+ #define m88k
+ #endif
+ 
+ /* Use type int rather than a union, to represent Lisp_Object */
+ /* This is desirable for most machines.  */
+ 
+ #define NO_UNION_TYPE
+ 
+ /* Define EXPLICIT_SIGN_EXTEND if XINT must explicitly sign-extend
+    the bit field into an int.  In other words, if bit fields
+    are always unsigned.
+ 
+    If you use NO_UNION_TYPE, this flag does not matter.  */
+ 
+ #define EXPLICIT_SIGN_EXTEND
+ 
+ /* Data type of load average, as read out of kmem.  */
+ 
+ /* #define LOAD_AVE_TYPE long */
+ 
+ /* Convert that into an integer that is 100 for a load average of 1.0  */
+ 
+ /* #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE) */
+ 
+ /* Define CANNOT_DUMP on machines where unexec does not work.
+    Then the function dump-emacs will not be defined
+    and temacs will do (load "loadup") automatically unless told otherwise.  */
+ 
+ /* #define CANNOT_DUMP */
+ 
+ /* Define VIRT_ADDR_VARIES if the virtual addresses of
+    pure and impure space as loaded can vary, and even their
+    relative order cannot be relied on.
+ 
+    Otherwise Emacs assumes that text space precedes data space,
+    numerically.  */
+ 
+ /* #define VIRT_ADDR_VARIES */
+ 
+ #define alloca(x) __builtin_alloca(x)
+ 
+ /* Define NO_REMAP if memory segmentation makes it not work well
+    to change the boundary between the text section and data section
+    when Emacs is dumped.  If you define this, the preloaded Lisp
+    code will not be sharable; but that's better than failing completely.  */
+ 
+ #define NO_REMAP
+ 
+ /* Define ADDR_CORRECT(ADDR) to be a macro to correct an int which is
+    the bit pattern of a pointer to a byte into an int which is the
+    number of a byte.
+ 
+    This macro has a default definition which is usually right.
+    This default definition is a no-op on most machines (where a
+    pointer looks like an int) but not on all machines. */
+ 
+ #define       ADDR_CORRECT(ADDR) ((int)ADDR)
+ 
+ /* Cast pointers to this type to compare them. */
+ 
+ #define       PNTR_COMPARISON_TYPE    void *
+ 
+ /* Some machines that use COFF executables require that each section
+    start on a certain boundary *in the COFF file*.  Such machines should
+    define SECTION_ALIGNMENT to a mask of the low-order bits that must be
+    zero on such a boundary.  This mask is used to control padding between
+    segments in the COFF file.
+ 
+    If SECTION_ALIGNMENT is not defined, the segments are written
+    consecutively with no attempt at alignment.  This is right for
+    unmodified system V.  */
+ 
+ #define SECTION_ALIGNMENT 0x7
+ 
+ /* arch-tag: 9de8e6ed-ddd8-4480-8308-17ddd7c86559
+    (do not change this comment) */