All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@Bull.Net>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: Port of the posix timers to IA64
Date: Mon, 03 Mar 2003 14:12:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805954@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805949@msgid-missing>

David Mosberger wrote:
> 
> Yes, you need to make sure that anything that gets shifted more than
> 32 bits has the proper type.  In portable code, I sometimes prefer
> to use explicit type-casts, e.g.:
> 
>         ((size_t) 1) << 48
> 
> if the final value needs to be of type size_t, but that's largely
> a matter of taste.
> 
Thank you, the code now works.

However I still don't feel confortable with the port because I had to
change the size of timer_t from int to long. I did so just because the
posix timers functions are based on the longest integer available (using
BITS_PER_LONG).
But it's not so convenient because then the include files of the system
also have to be updated (include/bits/types.h). In addition 2^24 ids
available (when using 32 bits) are already a lot.

Do you think I should try to care about compatibility and change the
posix timers functions to work on ints or should I just use longs and
update the include files?

Eric


  reply	other threads:[~2003-03-03 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01  8:10 [Linux-ia64] Re: Port of the posix timers to IA64 David Mosberger
2003-03-03 14:12 ` Eric Piel [this message]
2003-03-05  1:44 ` David Mosberger
2003-03-12 18:37 ` Jes Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590709805954@msgid-missing \
    --to=eric.piel@bull.net \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.