File:  [gforth] / gforth / arch / generic / machine.h
Revision 1.1: download - view: text, annotated - select for diffs
Mon Sep 1 23:08:23 1997 UTC (25 years, 9 months ago) by jwilke
Branches: MAIN
CVS tags: HEAD
Dos Changes:
engine/32bit.h moved to arch/generic/machine.h
cache.c moved to arch/hppa/
cleanalign.c moved to engine/
!!New Files:
envos.* *.bsh
Instead of linking arch/xy/machine.h an custom include path is used
engine.a engine.o main.o makes with engine/Makefile now
history.fs and startup.fs works for dos and unix now
environment variable osclass is set in envos.fs, wich is os-specific
any comments?
supressed some warnings in main.c

  This is a generic file for 32-bit machines with IEEE FP arithmetic (no VMS).
  It only supports indirect threading.

  Copyright (C) 1995 Free Software Foundation, Inc.

  This file is part of Gforth.

  Gforth 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
  of the License, or (at your option) any later version.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  GNU General Public License for more details.

  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

/* define this if IEEE singles and doubles are available as C data types */
#define IEEE_FP

/* the IEEE types are used only for loading and storing */
/* the IEEE double precision type */
typedef double DFloat;
/* the IEEE single precision type */
typedef float SFloat;

#ifndef USE_FTOS
#ifndef USE_NO_FTOS
/* keep top of FP stack in register. Since most processors have FP
   registers and they are hardly used in gforth, this is usually a
   good idea.  The 88100 has no separate FP regs, but many general
   purpose regs, so it should be ok */
#define USE_FTOS
/* I don't do the same for the data stack (i.e. USE_TOS), since this
   loses on processors with few registers. USE_TOS might be defined in
   the processor-specific files */

/* If you want direct threading, write a .h file for your processor! */
/* We could put some stuff here that causes a compile error, but then
   we could not use this file in the other machine.h files */

FreeBSD-CVSweb <>