Libstdc++
Sent: 10 June 2023 08:12
To: Hans-Peter Nilsson
Cc: Jonathan Wakely; libstdc++; gcc-patches
Subject: Re: [PATCH] (Re: Splitting up
27_io/basic_istream/ignore/wchar_t/94749.cc (takes too long))
On Sat, 10 Jun 2023, 06:18 Hans-Peter Nilsson via Libstdc++, <
libstd...@gcc.gnu.org>
On Jun 12, 2023, at 1:35 AM, Bernhard Reutner-Fischer
wrote:
>
> On Sat, 10 Jun 2023 11:29:36 -0700
> Mike Stump wrote:
>
>> On Jun 9, 2023, at 2:47 PM, Bernhard Reutner-Fischer
>> wrote:
>
>>>But well. Either way, what
>>> should we do about remote env,
On Sat, 10 Jun 2023 11:29:36 -0700
Mike Stump wrote:
> On Jun 9, 2023, at 2:47 PM, Bernhard Reutner-Fischer
> 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?
On Jun 9, 2023, at 2:47 PM, Bernhard Reutner-Fischer
wrote:
>
> On 9 June 2023 19:18:45 CEST, Mike Stump via Gcc-patches
> 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
>>
On Sat, 10 Jun 2023, 06:18 Hans-Peter Nilsson via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
> Thank you for your consideration. (Or is that phrase only used
> negatively?)
>
> > From: Jonathan Wakely
> > Date: Fri, 9 Jun 2023 21:40:15 +0100
>
> > test01, test02, test03 and test04 should run
Thank you for your consideration. (Or is that phrase only used negatively?)
> From: Jonathan Wakely
> Date: Fri, 9 Jun 2023 21:40:15 +0100
> test01, test02, test03 and test04 should run almost instantly. On my system
> they take about 5 microseconds each. So I don't think splitting those up
>
On 9 June 2023 19:18:45 CEST, Mike Stump via Gcc-patches
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
On Fri, 9 Jun 2023 at 17:20, Hans-Peter Nilsson wrote:
> Hi!
>
> The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
> about 10 minutes to run for cris-elf in the "gdb simulator"
> here on my arguably way-past-retirement machine (and it
> looks like it gained a minute with LRA). I've
> From: Mike Stump
> Date: Fri, 9 Jun 2023 10:18:45 -0700
> On Jun 9, 2023, at 9:20 AM, Hans-Peter Nilsson via Gcc-patches
> wrote:
> >
> > The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
> > about 10 minutes to run for cris-elf in the "gdb simulator"
>
> I'd let the libstdc++
On Jun 9, 2023, at 9:20 AM, Hans-Peter Nilsson via Gcc-patches
wrote:
>
> The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
> about 10 minutes to run for cris-elf in the "gdb simulator"
I'd let the libstdc++ people comment on specific things. I'll comment on
general things. We
Hi!
The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
about 10 minutes to run for cris-elf in the "gdb simulator"
here on my arguably way-past-retirement machine (and it
looks like it gained a minute with LRA). I've seen it
timing out every now and then on busy days with load >
`nproc`.
11 matches
Mail list logo
