Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R
relibc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • redox-os
  • relibc
  • Issues
  • #160

Closed
Open
Opened Feb 11, 2020 by Peter Limkilde Svendsen@plimkildeContributor

Change time_t to always-64-bit type

time_t is currently typedef'd in src/platform/types.rs as long (presumably following Linux' example). On platforms where long is 32 bits, this would make relibc susceptible to the year 2038 problem.

Since relibc/Redox currently does not support any 32-bit platforms, I suppose it would not be a breaking change to move to a redefinition as int64_t, at least for Redox. For eventual relibc compatibility with 32-bit Linux, we would need a platform-dependent time_t definition, or alternatively requiring kernel version 5.6+ (cf. this LKML post).

The BSDs have generally made the move to always-64-bit time_t.

Of course, such a change would need an accompanying change to the libc crate.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/relibc#160