|
Message
From: Matjaz Breskvar<phoenix@o...>
Date: Thu Jan 27 20:47:20 CET 2005
Subject: [openrisc] [or1ksim #7] Stricter typeing...
* György 'nog' Jeney (nog@s...) wrote:
> > > oraddr_t is used to mark addresses that the simulated processor (and
> > > peripherals) address. This is basically a reqirement to implement a 64-bit
> > > simulator (no, I'm not going to do that anytime soon). I have also defined the
> > > formating macros for these new types (PRIxADDR and PRIxREG), (What C99 has done
> > > in inttypes.h). I realise that this header and macros may not be availible on
> > > some varients of unix, but I don't know, so if you know of a place were the
> > > simulator might be used and these types are not availible, then shout and I'll
> > > stick in a configure check to fix it.
> >
> > Simulator should buid at least on Linux, Solaris, Cygwin and FreeBSD. I
> > do not think there is a need to introduce any constructs
> > that would further restrict the or1ksim portability....
>
> Would it suffice if I fixed the sim to compile and work if `inttypes.h' is not
> availible on the host system, or should I just drop this set of changes? Do
> you actually know that this will break on Solaris/FreeBSD or Cygwin? I just
> have this feeling that it will but I don't want to introduce hughe amounts of
> useless configure magic for nothing.
why not just copy the required definitions from inttypes.h (or maybe
even the whole file) and convince configure to use those if it can't
find the native one installed on system. there isn't much behind these
macros...
/* UPPERCASE hexadecimal notation. */
# define PRIX8 "X"
# define PRIX16 "X"
# define PRIX32 "X"
# define PRIX64 __PRI64_PREFIX "X"
best regards,
p.
|
 |
Browse
