public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105308] Specialize for_each
Date: Tue, 19 Apr 2022 15:22:57 +0000	[thread overview]
Message-ID: <bug-105308-4-27zI1KroXK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105308-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105308

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm unclear what the request is. Are you proposing this for the parallel
std::for_each with an execution policy? That code comes from the PSTL project
which is part of LLVM, and maintained by Intel, so enhancements to it should
ideally be done upstream.

  reply	other threads:[~2022-04-19 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 14:54 [Bug libstdc++/105308] New: " glisse at gcc dot gnu.org
2022-04-19 15:22 ` redi at gcc dot gnu.org [this message]
2022-04-19 16:05 ` [Bug libstdc++/105308] " glisse at gcc dot gnu.org
2022-04-19 16:41 ` 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-105308-4-27zI1KroXK@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: link
Be 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).