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++/97549] [11 Regression] include/pstl rebase breaking <execution> Date: Tue, 23 Feb 2021 08:28:28 +0000 [thread overview] Message-ID: <bug-97549-4-ENVGyHIRZT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97549-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97549 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:7e647d71d556b73e84f4edd0733bcc83bc70ae1e commit r11-7339-g7e647d71d556b73e84f4edd0733bcc83bc70ae1e Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Feb 23 09:26:23 2021 +0100 libstdc++: Fix up parallel_backend_serial.h [PR97549] In GCC 10, parallel_backend.h just included parallel_backend_{serial,tbb}.h and did nothing beyond that, and parallel_backend_tbb.h provided directly namespace __pstl { namespace __par_backend { ... } } and defined everything in there, while parallel_backend_serial.h did: namespace __pstl { namespace __serial { ... } } and had this namespace __pstl { namespace __par_backend { using namespace __pstl::__serial; } } at the end. In GCC 11, parallel_backend.h does: namespace __pstl { namespace __par_backend = __serial_backend; } after including parallel_backend_serial.h or namespace __pstl { namespace __par_backend = __tbb_backend; } after including parallel_backend_tbb.h. The latter then has: namespace __pstl { namespace __tbb_backend { ... } } and no using etc. at the end, while parallel_backend_serial.h changed to: namespace __pstl { namespace __serial_backend { ... } } but has this leftover block from the GCC 10 times. Even changing that using namespace __pstl::__serial; to using namespace __pstl::__serial_backend; doesn't work, as it clashes with namespace __pstl { namespace __par_backend = __serial_backend; } in parallel_backend.h. 2021-02-23 Jakub Jelinek <jakub@redhat.com> PR libstdc++/97549 * include/pstl/parallel_backend_serial.h: Remove __pstl::__par_backend.
next prev parent reply other threads:[~2021-02-23 8:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-23 15:16 [Bug libstdc++/97549] New: " nathan at gcc dot gnu.org 2020-11-04 13:52 ` [Bug libstdc++/97549] [11 Regression] " redi at gcc dot gnu.org 2020-12-15 12:32 ` redi at gcc dot gnu.org 2020-12-15 12:37 ` redi at gcc dot gnu.org 2021-01-14 9:30 ` rguenth at gcc dot gnu.org 2021-02-19 11:08 ` jakub at gcc dot gnu.org 2021-02-23 8:28 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-23 9:10 ` jakub 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-97549-4-ENVGyHIRZT@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).