From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org, paul@codesourcery.com
Cc: thayne@c2.net
Subject: Re: [Qemu-devel] [PATCH] target_posix_types.h
Date: Wed, 14 Nov 2007 14:06:58 -0700 (MST) [thread overview]
Message-ID: <20071114.140658.41652776.imp@bsdimp.com> (raw)
In-Reply-To: <200711142039.38427.paul@codesourcery.com>
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] target_posix_types.h
Date: Wed, 14 Nov 2007 20:39:36 +0000
> > This means that time_t had to be tracked down on varying architectures
> > to find the size and there was an assumption made that time_t is 32 bits
> > - which isn't true for all targets. The next problem is that if the
> > target is 32 bits but the host is 64 bits then there's a sign extension
> > problem because (time_t)-1 is used for an error condition. If you don't
> > correctly assign assign the 32-bit -1 to a 64-bit type then, rather than
> > -1, you get 4294967295.
>
> Is there any guarantee that time_t is a signed type? The fact that you said
> (time_t)-1 suggests it could be an unsigned type. If time_t is an unsigned
> type, then casting to a wider value is still wrong. You have to special-case
> the error condition.
>
> In the case of time_t this only becomes relevant after 32-bit time_t wrap in
> approx. 99 years time, but I'd expect there are cases where it matters.
The wrap on 32-bit signed time_t happens after ~68 years since the
next looming time thing in unix is 2038:
% date -r 2147483647
Mon Jan 18 20:14:07 MST 2038
% date -r 2147483648
Fri Dec 13 13:45:52 MST 1901
The standard says:
7.23 Date and time <time.h>
7.23.1 Components of time
[#3] The types declared are size_t (described in 7.17);
clock_t
and
time_t
which are arithmetic types capable of representing times;
Which is uselessly vague (no: it doesn't imply time_t is a signed
number or unsigned or even an int):
6.2.5 Types
...
[#21] Integer and floating types are collectively called
arithmetic types. Arithmetic types and pointer types are
collectively called scalar types. Array and structure types
are collectively called aggregate types.
Traditionally, time_t is defined as
typedef long time_t;
but recently you'll see it defined like so
typedef int32_t time_t;
or
typedef int64_t time_t;
Warner
next prev parent reply other threads:[~2007-11-14 21:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 15:59 [Qemu-devel] [PATCH] target_posix_types.h Thayne Harbaugh
2007-11-14 16:03 ` [Qemu-devel] Re: [PATCH] tget/tput deprecation Thayne Harbaugh
2007-11-14 16:08 ` Thayne Harbaugh
2007-11-14 18:21 ` Thayne Harbaugh
2007-11-14 19:02 ` Thayne Harbaugh
2007-11-16 4:16 ` Thayne Harbaugh
2007-11-14 16:25 ` [Qemu-devel] [PATCH] target_posix_types.h Jocelyn Mayer
2007-11-14 17:36 ` Thiemo Seufer
2007-11-14 17:54 ` Jocelyn Mayer
2007-11-14 18:20 ` Thayne Harbaugh
2007-11-14 18:32 ` Fabrice Bellard
2007-11-14 18:43 ` Thayne Harbaugh
2007-11-14 19:14 ` Fabrice Bellard
2007-11-14 19:53 ` Thayne Harbaugh
2007-11-14 20:39 ` Paul Brook
2007-11-14 21:06 ` Warner Losh [this message]
2007-11-14 21:25 ` Thayne Harbaugh
2007-11-14 21:19 ` Thayne Harbaugh
2007-11-14 21:37 ` Paul Brook
2007-11-14 19:56 ` Thayne Harbaugh
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=20071114.140658.41652776.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).