X-Mailer: exmh version 2.0.2
To: "Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
cc: eliz AT is DOT elta DOT co DOT il, mrs AT windriver DOT com, gcc AT gcc DOT gnu DOT org,
        djgpp-workers AT delorie DOT com
Subject: Re: GCC headers and DJGPP port 
In-reply-to: Your message of Mon, 17 Jul 2000 23:02:50 +0200.
             <200007172102 DOT XAA07817 AT loewis DOT home DOT cs DOT tu-berlin DOT de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 17 Jul 2000 16:39:59 -0600
Message-ID: <14100.963873599@upchuck>
From: Jeffrey A Law <law AT cygnus DOT com>
Reply-To: djgpp-workers AT delorie DOT com


  In message <200007172102 DOT XAA07817 AT loewis DOT home DOT cs DOT tu-berlin DOT de>you write:
  > Now, the exact mechanism *how* it is achieved that the header file is
  > an exact match of the target understanding of these types is a tricky
  > question, however, there is no question *that* gcc must know about
  > these types even without seeing a single target header file.
The "how" of this question is the port maintainer figures out the right
value and codes it into the target .h file.  For example:

/* Make GCC agree with types.h.  */
#undef SIZE_TYPE
#undef PTRDIFF_TYPE

#define SIZE_TYPE "long unsigned int"
#define PTRDIFF_TYPE "long int"