Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!sri-spam!robert
From: robert@spam.istc.sri.com
Newsgroups: comp.sys.hp
Subject: time.h header files on HP9000/300.
Message-ID: <12279@sri-spam.istc.sri.com>
Date: 26 Apr 88 17:02:45 GMT
Sender: nobody@sri-spam.istc.sri.com
Reply-To: robert@spam.istc.sri.com ()
Organization: SRI International
Lines: 28


    As I've mentioned in this forum before, I'm working on porting
    various programs written in C from Sun computers to HP9000/300
    computers.  One system header file which is on the VAX/Sun but
    not on the HP is /usr/include/sys/time.h.  Fortunately (?) the
    majority of the contents of this file is on the HP, in /usr/include/
    time.h.  The most noticeable difference, and one which concerns
    me, is in the declaration of 'struct timeval'.  On the Sun/Vax
    the 'tv_sec' field is a "long".  On the HP the same field is an
    "unsigned long".

    I would like to hear from anyone who has ported code which uses
    the struct timeval.  In particular I'm interested in anyone who
    has used timers, or time variables, to key actions in their software.
    If you had problems I definately want to hear about it, but if you
    didn't have problems I'd also like to know, so that I can make
    a SWAG regarding the level of effort I'm likely to encounter in
    my porting efforts (ie. is it hopeless or not?).

    I would also enjoy hearing from anyone at HP who can explain why
    this one small change was made on the HP.  Is math done differently
    on the HP architecture, or is the kernel time support different from
    the Vax/Sun?

    Thanks in advance for any words of wisdom.
----------------------------------------------------------------
Robert Allen, robert@spam.istc.sri.com
415-859-2143 (work phone, days)
----------------------------------------------------------------