From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
Florian Weimer <fweimer@redhat.com>,
Nathan Chancellor <nathan@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
llvm@lists.linux.dev, linux-toolchains@vger.kernel.org
Subject: Re: [GIT PULL v2] Kbuild updates for v5.15-rc1
Date: Tue, 7 Sep 2021 09:52:47 -0500 [thread overview]
Message-ID: <20210907145247.GH1583@gate.crashing.org> (raw)
In-Reply-To: <20210906215218.GA920497@tucnak>
On Mon, Sep 06, 2021 at 11:52:18PM +0200, Jakub Jelinek wrote:
> On Mon, Sep 06, 2021 at 02:08:58PM -0700, Linus Torvalds wrote:
> There is a stddef.h include too and that's it
> (I must say I don't see the reason for that include though).
Yeah me neither. Maybe the header used NULL before?
> Other compiler provided headers (not talking about C++ now) also have no
> or very limited includes, including stddef.h, stdarg.h, stdatomic.h, etc.
> The only exceptions are tgmath.h which isn't usable without libc
> math.h/complex.h,
<tgmath.h> is only for hosted environments. That requires a C library
for GCC (we do not implement this stuff ourselves). The compiler and
the C library have to work together to get this done, and the relation
between GCC and Glibc has been a bit too tight for this, it is true.
But a kernel build is not in a hosted environment.
> in some cases stdint.h and limits.h which are in some
> configurations provided both by the C library and the compiler and include
> each other in that case (but e.g. stdint.h has an alternate version that
> only uses compiler provided builtin macros) and openacc.h.
On what targets is <stdint.h> still problematic? And <limits.h>?
Segher
next prev parent reply other threads:[~2021-09-07 14:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 23:30 [GIT PULL v2] Kbuild updates for v5.15-rc1 Masahiro Yamada
2021-09-03 22:53 ` Linus Torvalds
2021-09-03 23:04 ` Nathan Chancellor
2021-09-04 8:01 ` Florian Weimer
2021-09-04 13:19 ` Segher Boessenkool
2021-09-04 15:19 ` Florian Weimer
2021-09-04 16:19 ` Segher Boessenkool
2021-09-04 17:22 ` Linus Torvalds
2021-09-04 19:15 ` Segher Boessenkool
2021-09-04 19:58 ` Linus Torvalds
2021-09-06 15:46 ` Segher Boessenkool
2021-09-06 16:30 ` Linus Torvalds
2021-09-06 17:27 ` Segher Boessenkool
2021-09-06 18:11 ` Linus Torvalds
2021-09-06 18:27 ` Florian Weimer
2021-09-06 19:48 ` Segher Boessenkool
2021-09-06 20:14 ` Jakub Jelinek
2021-09-06 21:08 ` Linus Torvalds
2021-09-06 21:24 ` Linus Torvalds
2021-09-07 14:41 ` Segher Boessenkool
2021-09-06 21:52 ` Jakub Jelinek
2021-09-06 22:24 ` Linus Torvalds
2021-09-07 15:26 ` Segher Boessenkool
2021-09-07 14:52 ` Segher Boessenkool [this message]
2021-09-09 5:14 ` Masahiro Yamada
2021-09-07 14:29 ` Segher Boessenkool
2021-09-06 6:54 ` Florian Weimer
2021-09-06 16:02 ` Alexey Dobriyan
2021-09-08 3:09 ` Masahiro Yamada
2021-09-03 23:12 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210907145247.GH1583@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=clang-built-linux@googlegroups.com \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).