Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: anton@mips.complang.tuwien.ac.at (Anton Ertl)
Newsgroups: comp.arch
Subject: Re: Privilege Levels Below User
Date: Mon, 10 Jun 2024 07:04:10 GMT
Organization: Institut fuer Computersprachen, Technische Universitaet Wien
Lines: 33
Message-ID: <2024Jun10.090410@mips.complang.tuwien.ac.at>
References: <jai66jd4ih4ejmek0abnl4gvg5td4obsqg@4ax.com> <Z9I8O.13$2JEf.11@fx14.iad> <5h%8O.4327$wDZ.776@fx48.iad> <v428v9$2o803$1@dont-email.me> <v464c4$73tb$1@dont-email.me>
Injection-Date: Mon, 10 Jun 2024 09:14:29 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="60f29ca21e25855be1abdc6acb2f37f0";
	logging-data="268994"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19wqS3SIsHDqK8y/g0sDXcI"
Cancel-Lock: sha1:cd0LWJvqerHgSCNRubRIX82HAfk=
X-newsreader: xrn 10.11
Bytes: 2049

Terje Mathisen <terje.mathisen@tmsw.no> writes:
>Modern Unix typically provides 64-bit time_t seconds and a (effectively) =
>
>30-bit ns field, so you can store them in a 96-bit container but I don't =
>
>think anyone does that?

man time_t tells me:

|time_t
|              ...
|              Used for time in seconds.  According to POSIX, it  shall  be  an
|              integer type.

|timespec
|              ...
|              struct timespec {
|                  time_t  tv_sec;  /* Seconds */
|                  long    tv_nsec; /* Nanoseconds */
|              };
|
|              Describes times in seconds and nanoseconds.
|
|              Conforming to: C11 and later; POSIX.1-2001 and later.

So if you have a 64-bit time_t, the C standard does that, and POSIX
does it earlier.  Typical ABIs pad struct timespec to 128 bits,
though.

- anton
-- 
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
  Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>