From: Paul Eggert <eggert@cs.ucla.edu>
To: "H.J. Lu" <hjl.tools@gmail.com>, Florian Weimer <fweimer@redhat.com>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Correct timespec implementation [BZ #26232]
Date: Wed, 15 Jul 2020 12:38:07 -0700 [thread overview]
Message-ID: <fb53968d-cc63-aefc-84ef-e31310bbb432@cs.ucla.edu> (raw)
In-Reply-To: <CAMe9rOoybYdjAMUGPjgSMGzWJ9Ngwka-XjYUP78qtXXsDhnPqg@mail.gmail.com>
On 7/14/20 6:17 AM, H.J. Lu via Libc-alpha wrote:
> No, it doesn't work on i686.
Could you give more details about why it doesn't work? Is it a GCC bug (and if
so, which version and what flags did you use)? Is it a bug in
INT_MULTIPLY_WRAPV? in INT_ADD_WRAPV? What code is generated and why is it
wrong? That sort of thing. If there's a bug in INT_*_WRAPV I'd like to fix it.
An advantage to using 'long long' over 'time_t' is that insulates the code from
possible future changes where time_t is unsigned (which POSIX allows).
Admittedly this is unlikely.
next prev parent reply other threads:[~2020-07-15 19:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 14:48 [PATCH v2] Fix time/tst-cpuclock1 intermitent failures Lucas A. M. Magalhaes
2020-02-17 16:44 ` Lucas A. M. Magalhaes
2020-02-18 12:44 ` Adhemerval Zanella
2020-02-19 16:42 ` Lucas A. M. Magalhaes
2020-02-19 18:51 ` Adhemerval Zanella
2020-02-20 18:17 ` [PATCH v3] " Lucas A. M. Magalhaes
2020-03-04 19:24 ` Matheus Castanho
2020-03-06 17:31 ` Lucas A. M. Magalhaes
2020-03-10 16:20 ` [PATCH v4] " Lucas A. M. Magalhaes
2020-03-10 16:30 ` Andreas Schwab
2020-03-10 17:45 ` Carlos O'Donell
2020-03-23 17:20 ` [PATCH v5] " Lucas A. M. Magalhaes
2020-03-23 21:06 ` Carlos O'Donell
2020-03-24 19:42 ` Lucas A. M. Magalhaes
2020-03-31 18:55 ` Carlos O'Donell
2020-03-31 11:34 ` [PATCH v6] " Lucas A. M. Magalhaes
2020-03-31 19:02 ` Carlos O'Donell
2020-04-03 19:24 ` [PATCH v7] " Lucas A. M. Magalhaes
2020-04-03 20:48 ` Carlos O'Donell
2020-04-07 13:59 ` [PATCH v8] " Lucas A. M. Magalhaes
2020-04-16 17:30 ` Lucas A. M. Magalhaes
2020-04-16 19:21 ` Carlos O'Donell
2020-04-21 17:44 ` [PATCH v9] " Lucas A. M. Magalhaes
2020-05-11 17:41 ` Lucas A. M. Magalhaes
2020-05-25 11:46 ` Lucas A. M. Magalhaes
2020-06-08 13:58 ` Lucas A. M. Magalhaes
2020-06-08 16:52 ` Carlos O'Donell
2020-06-12 15:28 ` [PATCH v10] " Lucas A. M. Magalhaes
2020-06-25 17:26 ` Lucas A. M. Magalhaes
2020-07-06 14:15 ` Lucas A. M. Magalhaes
2020-07-07 20:12 ` Carlos O'Donell
2020-07-10 23:07 ` Tulio Magno Quites Machado Filho
2020-07-11 14:45 ` H.J. Lu
2020-07-11 16:31 ` H.J. Lu
2020-07-13 23:30 ` [PATCH] Correct timespec implementation [BZ #26232] H.J. Lu
2020-07-14 2:35 ` Carlos O'Donell
2020-07-14 11:16 ` Florian Weimer
2020-07-14 11:42 ` H.J. Lu
2020-07-14 12:04 ` H.J. Lu
2020-07-14 12:18 ` Florian Weimer
2020-07-14 13:12 ` H.J. Lu
2020-07-14 13:14 ` Florian Weimer
2020-07-14 13:17 ` H.J. Lu
2020-07-15 19:38 ` Paul Eggert [this message]
2020-07-15 19:44 ` H.J. Lu
2020-07-14 13:08 ` Lucas A. M. Magalhaes
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=fb53968d-cc63-aefc-84ef-e31310bbb432@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).