public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106102] gcc/cp/mapper-resolver.cc fails to build against musl: musl-1.2.3-dev/include/sched.h:84:7: error: attempt to use poisoned "calloc" Date: Mon, 27 Jun 2022 12:03:56 +0000 [thread overview] Message-ID: <bug-106102-4-XWETiBZ0fQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106102-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106102 --- Comment #3 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- Aha, that makes sense. In this case include chain is: - c++tools/resolver.cc -> c++tools/resolver.h -> libcody/cody.hh -> libstdc++-v3/include/memory -> libstdc++-v3/include/bits/shared_ptr.h -> ... -> libstdc++-v3/include/x86_64-unknown-linux-musl/bits/gthr-default.h -> musl-1.2.3-dev/include/pthread.h -> musl-1.2.3-dev/include/sched.h [uses calloc()] AFAIU libstdc++-v3/include are all user-facing libraries and are expected to include system headers like <pthread.h>. It's a bit worrying that resolver.cc depends on <pthread.h> in such an indirect way. Would it be fair to say "system.h" needs to include <memory> for this case and be done with it? Does gcc do any system header wrapping by chance to minimize such leaks? I'm only asking because I noticed musl has different include order from glibc: https://github.com/NixOS/nixpkgs/issues/142066#issuecomment-1159568114. I tried to make include order alone closer to glibc and it did not fix the issue.
next prev parent reply other threads:[~2022-06-27 12:03 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-27 10:05 [Bug c++/106102] New: " slyfox at gcc dot gnu.org 2022-06-27 10:10 ` [Bug c++/106102] " sam at gentoo dot org 2022-06-27 10:51 ` rguenth at gcc dot gnu.org 2022-06-27 12:03 ` slyfox at gcc dot gnu.org [this message] 2022-06-27 14:50 ` slyfox at gcc dot gnu.org 2022-06-27 22:22 ` cvs-commit at gcc dot gnu.org 2022-06-27 23:00 ` slyfox at gcc dot gnu.org 2022-06-29 18:17 ` cvs-commit at gcc dot gnu.org 2022-07-02 15:22 ` cvs-commit at gcc dot gnu.org 2022-07-02 15:22 ` cvs-commit at gcc dot gnu.org 2022-07-02 15:26 ` slyfox 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-106102-4-XWETiBZ0fQ@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).