Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Jonathan Wakely via Gcc-patches
On Thu, 17 Nov 2022 at 09:57, Daniel Krügler wrote: > Am Do., 17. Nov. 2022 um 10:48 Uhr schrieb Jonathan Wakely < > jwak...@redhat.com>: > > > > > > > > On Thu, 17 Nov 2022 at 09:47, Jonathan Wakely > wrote: > >> > >> > >> > >> On Thu, 17 Nov 2022 at 09:25, Daniel Krügler > wrote: > >>> > >>>

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Ville Voutilainen via Gcc-patches
On Thu, 17 Nov 2022 at 11:57, Daniel Krügler via Libstdc++ wrote: > > Do you really want me to stop working on the missing time zone support to > > test and commit that change? > > I do not. I was reviewing and hoping to make a useful comment. Looks like someone's crunching to make a stage3 dea

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Daniel Krügler via Gcc-patches
Am Do., 17. Nov. 2022 um 10:48 Uhr schrieb Jonathan Wakely : > > > > On Thu, 17 Nov 2022 at 09:47, Jonathan Wakely wrote: >> >> >> >> On Thu, 17 Nov 2022 at 09:25, Daniel Krügler >> wrote: >>> >>> Am Do., 17. Nov. 2022 um 10:07 Uhr schrieb Jonathan Wakely >>> : >>> > >>> > >>> > >>> > On Thu, 17

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Jonathan Wakely via Gcc-patches
On Thu, 17 Nov 2022 at 09:47, Jonathan Wakely wrote: > > > On Thu, 17 Nov 2022 at 09:25, Daniel Krügler > wrote: > >> Am Do., 17. Nov. 2022 um 10:07 Uhr schrieb Jonathan Wakely >> : >> > >> > >> > >> > On Thu, 17 Nov 2022, 06:30 Daniel Krügler via Libstdc++, < >> libstd...@gcc.gnu.org> wrote: >>

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Jonathan Wakely via Gcc-patches
On Thu, 17 Nov 2022 at 09:25, Daniel Krügler wrote: > Am Do., 17. Nov. 2022 um 10:07 Uhr schrieb Jonathan Wakely > : > > > > > > > > On Thu, 17 Nov 2022, 06:30 Daniel Krügler via Libstdc++, < > libstd...@gcc.gnu.org> wrote: > >> > >> Am Mi., 16. Nov. 2022 um 22:00 Uhr schrieb Jonathan Wakely via

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Daniel Krügler via Gcc-patches
Am Do., 17. Nov. 2022 um 10:07 Uhr schrieb Jonathan Wakely : > > > > On Thu, 17 Nov 2022, 06:30 Daniel Krügler via Libstdc++, > wrote: >> >> Am Mi., 16. Nov. 2022 um 22:00 Uhr schrieb Jonathan Wakely via >> Libstdc++ : >> > >> > Tested x86_64-linux. Pushed to trunk. >> > >> > -- >8 -- >> > >> > W

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-17 Thread Jonathan Wakely via Gcc-patches
On Thu, 17 Nov 2022, 06:30 Daniel Krügler via Libstdc++, < libstd...@gcc.gnu.org> wrote: > Am Mi., 16. Nov. 2022 um 22:00 Uhr schrieb Jonathan Wakely via > Libstdc++ : > > > > Tested x86_64-linux. Pushed to trunk. > > > > -- >8 -- > > > > We can use an array instead of a std::vector, and we can av

Re: [committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-16 Thread Daniel Krügler via Gcc-patches
Am Mi., 16. Nov. 2022 um 22:00 Uhr schrieb Jonathan Wakely via Libstdc++ : > > Tested x86_64-linux. Pushed to trunk. > > -- >8 -- > > We can use an array instead of a std::vector, and we can avoid the > binary search for the common case of a time point after the most recent > leap second. On one sy

[committed] libstdc++: Improve performance of chrono::utc_clock::now()

2022-11-16 Thread Jonathan Wakely via Gcc-patches
Tested x86_64-linux. Pushed to trunk. -- >8 -- We can use an array instead of a std::vector, and we can avoid the binary search for the common case of a time point after the most recent leap second. On one system where I tested this, utc_clock::now() now takes about 16ns instead of 31ns. libstdc