emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/src/m/ia64.h,v


From: Dan Nicolaescu
Subject: [Emacs-diffs] Changes to emacs/src/m/ia64.h,v
Date: Wed, 16 Jul 2008 07:42:43 +0000

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Dan Nicolaescu <dann>   08/07/16 07:42:42

Index: m/ia64.h
===================================================================
RCS file: /cvsroot/emacs/emacs/src/m/ia64.h,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- m/ia64.h    13 Jul 2008 07:35:23 -0000      1.21
+++ m/ia64.h    16 Jul 2008 07:42:41 -0000      1.22
@@ -32,9 +32,7 @@
 #define NO_ARG_ARRAY
 
 /* 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 */
+   does not define it automatically.  */
 
 /* __ia64__ defined automatically */
 
@@ -59,47 +57,11 @@
 
 #define LOAD_AVE_CVT(x) (int) (((double) (x)) * 100.0 / FSCALE)
 
-/* 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 the following if GNU malloc and the relocating allocator do
-   not work together with X.  */
-
-/* #define SYSTEM_MALLOC */
-
-/* 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 */
-
-/* Some really obscure 4.2-based systems (like Sequent DYNIX) do not
-   support asynchronous I/O (using SIGIO) on sockets, even though it
-   works fine on tty's.  If you have one of these systems, define the
-   following, and then use it in config.h (or elsewhere) to decide
-   when (not) to use SIGIO.
-
-   You'd think this would go in an operating-system description file,
-   but since it only occurs on some, but not all, BSD systems, the
-   reasonable place to select for it is in the machine description
-   file.  */
-
-/* #define NO_SOCK_SIGIO */
-
 #ifdef __ELF__
 #undef UNEXEC
 #define UNEXEC unexelf.o
 #endif
 
-#define PNTR_COMPARISON_TYPE unsigned long
-
 #ifndef NOT_C_CODE
 
 #ifdef REL_ALLOC




reply via email to

[Prev in Thread] Current Thread [Next in Thread]