public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1041] c++tools: Include <cstdlib> for exit [PR100731] Date: Tue, 25 May 2021 14:45:19 +0000 (GMT) [thread overview] Message-ID: <20210525144519.5FF223939C11@sourceware.org> (raw) https://gcc.gnu.org/g:7a5e9a58fbe27d8b8f04cd18bc6e1dd736e3cd12 commit r12-1041-g7a5e9a58fbe27d8b8f04cd18bc6e1dd736e3cd12 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue May 25 16:44:35 2021 +0200 c++tools: Include <cstdlib> for exit [PR100731] This TU uses exit, but doesn't include <stdlib.h> or <cstdlib> and relies on some other header to include it indirectly, which apparently doesn't happen on reporter's host. The other <c*> headers aren't guarded either and we rely on a compiler capable of C++11, so maybe we can rely on <cstdlib> being around unconditionally. 2021-05-25 Jakub Jelinek <jakub@redhat.com> PR bootstrap/100731 * server.cc: Include <cstdlib>. Diff: --- c++tools/server.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/c++tools/server.cc b/c++tools/server.cc index 709955e7e2b..fae3e78dc5d 100644 --- a/c++tools/server.cc +++ b/c++tools/server.cc @@ -29,6 +29,7 @@ along with GCC; see the file COPYING3. If not see #include <csignal> #include <cstring> #include <cstdarg> +#include <cstdlib> // OS #include <unistd.h> #include <sys/types.h>
reply other threads:[~2021-05-25 14:45 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210525144519.5FF223939C11@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).