public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/95592] Collision with struct _Cosh when Cross compiling libstdc++ Date: Wed, 28 Oct 2020 12:50:36 +0000 [thread overview] Message-ID: <bug-95592-4-mIvUeKmlg1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95592-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95592 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:72a87d82e0d0741d75c72c8f3d2fc070e3a02b5f commit r11-4476-g72a87d82e0d0741d75c72c8f3d2fc070e3a02b5f Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Oct 28 12:35:44 2020 +0000 libstdc++: Fix name clash with _Cosh in QNX headers [PR 95592] This replaces unqualified names like _Cosh with struct std::_Cosh to ensure there is no ambiguity with other entities with the same name. libstdc++-v3/ChangeLog: PR libstdc++/95592 * include/bits/valarray_after.h (_DEFINE_EXPR_UNARY_OPERATOR) (_DEFINE_EXPR_BINARY_OPERATOR, _DEFINE_EXPR_BINARY_FUNCTION): Use elaborated-type-specifier and qualified-id to avoid ambiguities with QNX system headers. * testsuite/26_numerics/valarray/95592.cc: New test.
next prev parent reply other threads:[~2020-10-28 12:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-08 22:58 [Bug libstdc++/95592] New: " kevin at arilabs dot net 2020-06-08 23:01 ` [Bug libstdc++/95592] " kevin at arilabs dot net 2020-06-08 23:02 ` kevin at arilabs dot net 2020-10-28 12:50 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-28 12:51 ` redi at gcc dot gnu.org 2021-03-29 20:01 ` cvs-commit at gcc dot gnu.org 2021-03-29 20:03 ` redi 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-95592-4-mIvUeKmlg1@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).