[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUpy=xpQ3wJ0RahYJ+Bkwf3EL5KPWvmOqs_vQG5cXGwGg@mail.gmail.com>
Date: Wed, 14 May 2014 12:44:28 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: James Hogan <james.hogan@...tec.com>,
Ley Foon Tan <lftan@...era.com>,
Linux-Arch <linux-arch@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Chung-Lin Tang <cltang@...esourcery.com>,
Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 01/25] asm-generic: Change time_t and clock_t to 64 bit
On Wed, May 14, 2014 at 5:47 AM, H. Peter Anvin <hpa@...or.com> wrote:
> On 05/13/2014 03:22 AM, James Hogan wrote:
>>> When we export this posix_types.h file for user software, they need to
>>> define this config, eg: CONFIG_32BIT_TIME to use 32 bit time. Is this
>>> what we want to do?
>>
>> Yeh, good point, that won't work.
>
> How about:
>
> #include <asm-generic/types/time32.h>
>
> The asm-generic/types/ directory can be used for all kinds of type
> templates, like int-ll64.h and the (now removed) former int-l64.h.
That should more or less work. But better call it time-l.h, as time_t
should be 64-bit on 64-bit architectures. Else 32/64-bit architectures
still need an #ifdef.
Will time_t stay "long" (and not become "long long") on 64-bit?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists