public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/100117] New: FAIL testsuite/17_intro/headers/c++1998/49745.cc with trunk glibc Date: Fri, 16 Apr 2021 14:13:59 +0000 [thread overview] Message-ID: <bug-100117-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100117 Bug ID: 100117 Summary: FAIL testsuite/17_intro/headers/c++1998/49745.cc with trunk glibc Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- I have seen (with r11-7986 , so sorry if it has been fixed already) FAIL: 17_intro/headers/c++1998/49745.cc (test for excess errors) which appears only when built against latest glibc 2.34 snapshot and works fine against glibc 2.33. libstdc++.log contains: /builddir/build/BUILD/gcc-11.0.1-20210405/libstdc++-v3/testsuite/17_intro/headers/c++1998/49745.cc:22: error: 'int truncate' redeclared as different kind of entity In file included from /usr/include/bits/sigstksz.h:24, from /usr/include/signal.h:315, from /builddir/build/BUILD/gcc-11.0.1-20210405/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/csignal:42, from /builddir/build/BUILD/gcc-11.0.1-20210405/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/stdc++.h:43, from <command-line>: /usr/include/unistd.h:1005: note: previous declaration 'int truncate(const char*, __off_t)' Maybe it would be nice if bits/sigstksz.h didn't include whole unistd.h but just bits/confname.h and used some __ prefixed alias with redirection for the sysconf call?
next reply other threads:[~2021-04-16 14:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 14:13 jakub at gcc dot gnu.org [this message] 2021-04-16 14:38 ` [Bug libstdc++/100117] " fw at gcc dot gnu.org 2021-04-16 14:46 ` jakub at gcc dot gnu.org 2021-04-16 14:59 ` fw at gcc dot gnu.org 2021-04-16 19:00 ` redi at gcc dot gnu.org 2021-08-13 22:22 ` slyfox at gcc dot gnu.org 2021-11-10 12:04 ` cvs-commit at gcc dot gnu.org 2021-11-10 12:05 ` redi at gcc dot gnu.org 2021-11-24 11:50 ` cvs-commit at gcc dot gnu.org 2022-04-26 13:12 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:03 ` rguenth 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-100117-4@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).