-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[FEATURE] "portable" implementation for POSIX's uint64_t time. #18849
Copy link
Copy link
Open
Labels
Arch: avrIssues related to all AVR(8-bit or 32-bit) architecturesIssues related to all AVR(8-bit or 32-bit) architecturesArch: avr32Issues related to AVR32 (32-bit) architectureIssues related to AVR32 (32-bit) architectureArch: avr8Issues related to AVR (8-bit) architectureIssues related to AVR (8-bit) architectureArch: mipsIssues related to the MIPS architectureIssues related to the MIPS architectureArch: risc-vIssues related to the RISC-V (32-bit or 64-bit) architectureIssues related to the RISC-V (32-bit or 64-bit) architectureArch: simulatorIssues related to the SIMulatorIssues related to the SIMulatorArch: x86Issues related to the x86 architectureIssues related to the x86 architectureArch: xtensaIssues related to the Xtensa architectureIssues related to the Xtensa architectureArch: z16Issues related to the Z16 architectureIssues related to the Z16 architectureArch: z80Issues related to the Z80 architectureIssues related to the Z80 architectureArea: DocumentationImprovements or additions to documentationImprovements or additions to documentationArea: KernelKernel issuesKernel issuesArea: ModularityNeeded to support modular architectureNeeded to support modular architectureArea: PosixPosix issuesPosix issuesArea: StandardsNuttX application interfaces must compy to standardsNuttX application interfaces must compy to standardsBoard: allType: EnhancementNew feature or requestNew feature or requestType: Improvement
Milestone
Metadata
Metadata
Assignees
Labels
Arch: avrIssues related to all AVR(8-bit or 32-bit) architecturesIssues related to all AVR(8-bit or 32-bit) architecturesArch: avr32Issues related to AVR32 (32-bit) architectureIssues related to AVR32 (32-bit) architectureArch: avr8Issues related to AVR (8-bit) architectureIssues related to AVR (8-bit) architectureArch: mipsIssues related to the MIPS architectureIssues related to the MIPS architectureArch: risc-vIssues related to the RISC-V (32-bit or 64-bit) architectureIssues related to the RISC-V (32-bit or 64-bit) architectureArch: simulatorIssues related to the SIMulatorIssues related to the SIMulatorArch: x86Issues related to the x86 architectureIssues related to the x86 architectureArch: xtensaIssues related to the Xtensa architectureIssues related to the Xtensa architectureArch: z16Issues related to the Z16 architectureIssues related to the Z16 architectureArch: z80Issues related to the Z80 architectureIssues related to the Z80 architectureArea: DocumentationImprovements or additions to documentationImprovements or additions to documentationArea: KernelKernel issuesKernel issuesArea: ModularityNeeded to support modular architectureNeeded to support modular architectureArea: PosixPosix issuesPosix issuesArea: StandardsNuttX application interfaces must compy to standardsNuttX application interfaces must compy to standardsBoard: allType: EnhancementNew feature or requestNew feature or requestType: Improvement
Type
Fields
Give feedbackNo fields configured for Task.
Is your feature request related to a problem? Please describe.
uint64_t.sys/types.h[3] defines:long longtype is not natively supported.This is a long standing challenge discussed on our mailing list [4][5].
Related PR: #18840, #14460, apache/nuttx-apps#3468.
[1] https://pubs.opengroup.org/onlinepubs/9799919799/
[2] https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/time.h.html
[3] https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/sys_types.h.html
[4] https://www.mail-archive.com/dev@nuttx.apache.org/msg12060.html
[5] https://www.mail-archive.com/dev@nuttx.apache.org/msg14534.html
Describe the solution you'd like
int64_ttype as default.int64_ttype that will solve size increase, slow down, and non-atomic time access protections, but still assure POSIX compliant interface.Describe alternatives you've considered
No response
Verification