From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Mike Stump <mikestump@comcast.net>,
Mike Stump via Gcc-patches <gcc-patches@gcc.gnu.org>,
Hans-Peter Nilsson <hp@axis.com>
Cc: jwakely@redhat.com, libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Splitting up 27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long)
Date: Fri, 09 Jun 2023 23:47:01 +0200 [thread overview]
Message-ID: <057BCABA-67C8-4309-B7DD-C9310B938727@gmail.com> (raw)
In-Reply-To: <7F48B21B-835B-4741-9B9E-660A2D302A67@comcast.net>
On 9 June 2023 19:18:45 CEST, Mike Stump via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> simulation ports. Maybe a 20-100x speedup? If you want to go this way I'd say do it in python at the bottom as it would be nice to switch over to python in the next 5-20 years and away from tcl.
Yes, i guess we have all pondered this for way long enough, but it is a lot of work still.
The nice side effect would be that we see such hogs easier and earlier, at least more comfortable. 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?
thanks,
next prev parent reply other threads:[~2023-06-09 21:47 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 [this message]
2023-06-10 18:29 ` Mike Stump
2023-06-12 8:35 ` Bernhard Reutner-Fischer
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=057BCABA-67C8-4309-B7DD-C9310B938727@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).