public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/100731] GCC 11 fails to build using GCC 4.8 because of missing includes Date: Sun, 23 May 2021 15:55:21 +0000 [thread overview] Message-ID: <bug-100731-4-OlNDGhJu3q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100731-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100731 --- Comment #2 from Harald van Dijk <harald at gigawatt dot nl> --- There are more missing or wrong includes here: looking at the code, it's also using functions from <stdio.h> without including that, but that one gets implicitly included for me even on this old G++ so happens to not cause an error. It's also using strrchr from <string.h> while only including <cstring> and not qualifying as std::strrchr, which will work on all GCC versions but is not correct.
next prev parent reply other threads:[~2021-05-23 15:55 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-23 15:43 [Bug bootstrap/100731] New: " harald at gigawatt dot nl 2021-05-23 15:44 ` [Bug bootstrap/100731] " harald at gigawatt dot nl 2021-05-23 15:55 ` harald at gigawatt dot nl [this message] 2021-05-25 7:26 ` [Bug c++/100731] [11/12 Regression] " rguenth at gcc dot gnu.org 2021-05-25 7:45 ` harald at gigawatt dot nl 2021-05-25 7:50 ` rguenther at suse dot de 2021-05-25 8:00 ` harald at gigawatt dot nl 2021-05-25 14:45 ` cvs-commit at gcc dot gnu.org 2021-05-25 16:27 ` harald at gigawatt dot nl 2021-05-25 17:18 ` redi at gcc dot gnu.org 2021-05-25 17:22 ` jakub at gcc dot gnu.org 2021-05-31 14:08 ` cvs-commit at gcc dot gnu.org 2021-07-09 17:26 ` [Bug c++/100731] [12 " jason at gcc dot gnu.org 2021-07-28 7:07 ` rguenth at gcc dot gnu.org 2021-12-28 12:06 ` pinskia at gcc dot gnu.org
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=bug-100731-4-OlNDGhJu3q@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).