Skip to contentSkip to conversation

year 2038 problem on x86-64

DISCUSSION Andi Kleen 2 participants 2 messages Sep 22, 2004 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#2 lore raw
Quoted 2 lines · Pavel Machek

... __ARCH_WANT_SYS_TIME actually is set on x86-64.

But it's not used. It declares an own sys_time64 in arch/x86_64 By default the vsyscall code is used.

Also sys_time is legacy, most users should be using gettimeofday()

-Andi

#3 lore raw

Hi!

Quoted 5 lines
Quoted 2 lines

... __ARCH_WANT_SYS_TIME actually is set on x86-64.

But it's not used. It declares an own sys_time64 in arch/x86_64 By default the vsyscall code is used.

So should __ARCH_WANT_SYS_TIME be killed from x86_64?

Signature · 2 lines
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!