Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 14 Aug 2019 20:13:31 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [RFC] final time64 switch-over patch series

On Wed, Aug 14, 2019 at 07:55:21PM -0400, Rich Felker wrote:
> It should be possible to do some macro magic to make features.h do a
> _T64() function-like macro that expands differently depending on the
> definition of _REDIR_TIME64 at the time it's expanded, but this will
> require that all archs define it to 0 or 1 rather than leaving it
> undefined when not used. Then we can just unconditionally do:
> 
> int aio_suspend(const struct aiocb *const [], int, const struct timespec *) _T64(__aio_suspend_time64);
> 
> etc.
> 
> Does this seem reasonable?

Hm, I think it's probably simpler/more readable just to have
alltypes.h define _T64(x) appropriately. I hate header mechanisms that
require you to trace back across arcane stuff in multiple places to
find how/where something is actually defined.

Rich

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.