[Bug 2055837]

[Adhemerval Zanella]

(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 received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2055837

Title:
  Wrong type for timeval.tv_usec on armhf/Noble (and other failures)

Status in GLibC:
  New
Status in glibc package in Ubuntu:
  Triaged

Bug description:
  I xfailed a whole stack of the "conform" tests on armhf, which
  presumably fail because of the change in default size of time_t (and
  off_t). We should work out what is going on here before release --
  maybe leaving them xfail is appropriate but I'm not confident to say
  that at this time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2055837/+subscriptions