[cfe-commits] C11 <stdatomic.h>

Richard Smith richard at metafoo.co.uk
Mon Sep 29 12:34:34 PDT 2014


Adding a __has_include_next check sounds good to me. We already do this for
several other headers.

Hal: if you're interested in driving this (rebasing the patch and adding
the include_next machinery), please go ahead.

On Thu, Sep 25, 2014 at 1:42 PM, Ed Schouten <ed at 80386.nl> wrote:

> On 22 September 2014 16:38, Hal Finkel <hfinkel at anl.gov> wrote:
> > Understood. I suggested exactly this (
> http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140915/115196.html).
> Does that work for you?
>
> Yes. That's perfect. Thanks!
>
> On a more general note, I'd love to see if Clang would eventually
> focus on providing built-ins that would allow OS authors to come up
> with the standard headers easily, instead of providing the headers
> themselves.
>
> For example, it would be pretty nice if we could write down things like:
>
> typedef __builtin_uint32_t uint32_t;
>
> #define LONG_MAX __builtin_max(long)
>
> etc.
>
> But don't let me hijack this thread. :-)
>
> --
> Ed Schouten <ed at 80386.nl>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140929/53d34a51/attachment.html>


More information about the cfe-commits mailing list