public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/31510] Wrong type for timeval.tv_usec on 32-bit archs with _TIME_BITS=64
Date: Wed, 20 Mar 2024 12:27:41 +0000	[thread overview]
Message-ID: <bug-31510-131-P6ar4wZLSP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31510-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31510

--- Comment #4 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Joseph Myers from comment #2)
> Shouldn't we fix how suseconds_t is defined in glibc in the 64-bit time
> case? It's not as if any interfaces in glibc use suseconds_t other than as
> part of struct timeval (though we should still warn in NEWS about potential
> compatibility issues for any interfaces using suseconds_t in third-party
> libraries).

That's why I am not fully sure which would be the best way, since this strictly
is an ABI break.  

At least using the timespec trick to keep the type as currently defined should
not cause any issue (since the type holds all potential values), and it should
be back-portable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-03-20 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 11:24 [Bug time/31510] New: " simon.chopin at canonical dot com
2024-03-19 11:30 ` [Bug time/31510] " sam at gentoo dot org
2024-03-19 12:15 ` adhemerval.zanella at linaro dot org
2024-03-19 20:21 ` jsm28 at gcc dot gnu.org
2024-03-19 20:22 ` jsm28 at gcc dot gnu.org
2024-03-20 12:27 ` adhemerval.zanella at linaro dot org [this message]
2024-03-20 13:48 ` simon.chopin at canonical dot com

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=bug-31510-131-P6ar4wZLSP@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).