public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cassio Neri <cassio.neri@gmail.com>
To: "Koning, Paul" <Paul.Koning@dell.com>
Cc: Cassio Neri via Gcc-patches <gcc-patches@gcc.gnu.org>,
	 "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: More efficient std::chrono::year::leap.
Date: Fri, 21 May 2021 19:44:52 +0100	[thread overview]
Message-ID: <CAOfgUPiBscyfyhT_Mtx4mvWLm+ay1=OuG-J8tM=TjDuGDi27=A@mail.gmail.com> (raw)
In-Reply-To: <34C4F25A-6333-4C08-BBFF-8E86A5A9B764@dell.com>

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

I've checked the generated code and the compiler doesn't figure out
the logic. I added a comment to explain.

(Revised patch below and attached.)

Best wishes,
Cassio.

---

Simple change to std::chrono::year::is_leap. If a year is multiple of 100,
then it's divisible by 400 if and only if it's divisible by 16. The latter
allows for better code generation.

Tested on x86_64-pc-linux-gnu.

libstdc++-v3/ChangeLog:
libstdc++-v3/ChangeLog:

    * include/std/chrono:

diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index 4631a727d73..85aa0379432 100644
--- a/libstdc++-v3/include/std/chrono
+++ b/libstdc++-v3/include/std/chrono
@@ -1612,7 +1612,9 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
     constexpr uint32_t __offset       = __max_dividend / 2 / 100 * 100;
     const bool __is_multiple_of_100
       = __multiplier * (_M_y + __offset) < __bound;
-    return (!__is_multiple_of_100 || _M_y % 400 == 0) && _M_y % 4 == 0;
+    // Usually we test _M_y % 400 == 0 but, when it's already known that
+    // _M_y%100 == 0, then _M_y % 400==0 is equivalent to _M_y % 16 == 0.
+    return (!__is_multiple_of_100 || _M_y % 16 == 0) && _M_y % 4 == 0;
       }

       explicit constexpr

On Fri, May 21, 2021 at 7:05 PM Koning, Paul <Paul.Koning@dell.com> wrote:
>
>
>
> > On May 21, 2021, at 1:46 PM, Cassio Neri via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> >
> > Simple change to std::chrono::year::is_leap. If a year is multiple of 100,
> > then it's divisible by 400 if and only if it's divisible by 16. The latter
> > allows for better code generation.
>
> I wonder if the optimizer could be taught to do that.
>
> The change seems correct but it is very confusing; at the very least the reasoning you gave should be stated in a comment on that check.
>
>         paul
>
>

[-- Attachment #2: leap.patch --]
[-- Type: text/x-patch, Size: 1011 bytes --]

Simple change to std::chrono::year::is_leap. If a year is multiple of 100,
then it's divisible by 400 if and only if it's divisible by 16. The latter
allows for better code generation.

Tested on x86_64-pc-linux-gnu.

libstdc++-v3/ChangeLog:
libstdc++-v3/ChangeLog:

	* include/std/chrono:

diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index 4631a727d73..85aa0379432 100644
--- a/libstdc++-v3/include/std/chrono
+++ b/libstdc++-v3/include/std/chrono
@@ -1612,7 +1612,9 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 	constexpr uint32_t __offset       = __max_dividend / 2 / 100 * 100;
 	const bool __is_multiple_of_100
 	  = __multiplier * (_M_y + __offset) < __bound;
-	return (!__is_multiple_of_100 || _M_y % 400 == 0) && _M_y % 4 == 0;
+	// Usually we test _M_y % 400 == 0 but, when it's already known that
+	// _M_y%100 == 0, then _M_y % 400==0 is equivalent to _M_y % 16 == 0.
+	return (!__is_multiple_of_100 || _M_y % 16 == 0) && _M_y % 4 == 0;
       }

       explicit constexpr

  reply	other threads:[~2021-05-21 18:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 17:46 Cassio Neri
2021-05-21 18:05 ` Koning, Paul
2021-05-21 18:44   ` Cassio Neri [this message]
2021-06-23 11:45     ` Jonathan Wakely
2021-06-23 13:16       ` Jonathan Wakely
2021-06-23 17:51         ` Jonathan Wakely
2021-06-23 17:52           ` Jonathan Wakely
2021-06-24 11:42             ` Cassio Neri

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='CAOfgUPiBscyfyhT_Mtx4mvWLm+ay1=OuG-J8tM=TjDuGDi27=A@mail.gmail.com' \
    --to=cassio.neri@gmail.com \
    --cc=Paul.Koning@dell.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).