From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: rep.dot.nop@gmail.com,
Mike Stump via Gcc-patches <gcc-patches@gcc.gnu.org>,
Hans-Peter Nilsson <hp@axis.com>,
jwakely@redhat.com, Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long)
Date: Mon, 12 Jun 2023 10:35:06 +0200 [thread overview]
Message-ID: <20230612103506.0d9842fe@nbbrfq.loc> (raw)
In-Reply-To: <0334D52C-D33F-4261-8705-F3736D6F36B2@comcast.net>
On Sat, 10 Jun 2023 11:29:36 -0700
Mike Stump <mikestump@comcast.net> wrote:
> On Jun 9, 2023, at 2:47 PM, Bernhard Reutner-Fischer
> <rep.dot.nop@gmail.com> wrote:
> > But well. Either way, what
> > should we do about remote env, if there is one? If the target
> > supports it, send it and skip otherwise?
> So, to focus a
> conversation, which target, which host, canadian? Which part of the
> environment? What part is missing you want to fix? Want to unify
> between targets... and so on.
>
The most recent target where this came up again was GCN i think.
See the last block in
https://inbox.sourceware.org/gcc-patches/20230508195217.4897009f@nbbrfq/
and Thomas' reference therein to Tobias'
https://inbox.sourceware.org/gcc-patches/018bcdeb-b3bb-1859-cd0b-a8a92e26d3a0@codesourcery.com/
thoughts?
thanks,
next prev parent reply other threads:[~2023-06-12 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 16:20 Hans-Peter Nilsson
2023-06-09 17:18 ` Mike Stump
2023-06-09 17:49 ` Hans-Peter Nilsson
2023-06-09 21:47 ` Bernhard Reutner-Fischer
2023-06-10 18:29 ` Mike Stump
2023-06-12 8:35 ` Bernhard Reutner-Fischer [this message]
2023-06-12 22:26 ` Mike Stump
2023-06-09 20:40 ` Jonathan Wakely
2023-06-10 4:05 ` [PATCH] (Re: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long)) Hans-Peter Nilsson
2023-06-10 7:12 ` Jonathan Wakely
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=20230612103506.0d9842fe@nbbrfq.loc \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jwakely@redhat.com \
--cc=mikestump@comcast.net \
--cc=thomas@codesourcery.com \
/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).