From: Jonathan Wakely <jwakely@redhat.com>
To: Cassio Neri <cassio.neri@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v4] libstdc++: Remove unnecessary "& 1" from year_month_day_last::day().
Date: Tue, 14 Nov 2023 22:47:31 +0000 [thread overview]
Message-ID: <CACb0b4=xTBgH2saDq7OKf+tE+cMA6zoXnN5fbh2uwsVbYcfzgg@mail.gmail.com> (raw)
In-Reply-To: <20231111164458.46230-1-cassio.neri@gmail.com>
On Sat, 11 Nov 2023 at 16:46, Cassio Neri <cassio.neri@gmail.com> wrote:
>
> When year_month_day_last::day() was implemented, Dr. Matthias Kretz realised
> that the operation "& 1" wasn't necessary but we did not patch it at that
> time. This patch removes the unnecessary operation.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/chrono: Remove &1 from year_month_day_last::day().
> ---
> Previous versions of this patch failed to apply. I hope it works this time.
>
> OK for trunk?
Yes, thanks - pushed to trunk.
>
> libstdc++-v3/include/std/chrono | 24 ++++++++++++++----------
> 1 file changed, 14 insertions(+), 10 deletions(-)
>
> diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
> index 10e868e5a03..a826982803b 100644
> --- a/libstdc++-v3/include/std/chrono
> +++ b/libstdc++-v3/include/std/chrono
> @@ -1800,22 +1800,26 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
> {
> const auto __m = static_cast<unsigned>(month());
>
> - // Excluding February, the last day of month __m is either 30 or 31 or,
> - // in another words, it is 30 + b = 30 | b, where b is in {0, 1}.
> + // The result is unspecified if __m < 1 or __m > 12. Hence, assume
> + // 1 <= __m <= 12. For __m != 2, day() == 30 or day() == 31 or, in
> + // other words, day () == 30 | b, where b is in {0, 1}.
>
> - // If __m in {1, 3, 4, 5, 6, 7}, then b is 1 if, and only if __m is odd.
> - // Hence, b = __m & 1 = (__m ^ 0) & 1.
> + // If __m in {1, 3, 4, 5, 6, 7}, then b is 1 if, and only if, __m is
> + // odd. Hence, b = __m & 1 = (__m ^ 0) & 1.
>
> - // If __m in {8, 9, 10, 11, 12}, then b is 1 if, and only if __m is even.
> - // Hence, b = (__m ^ 1) & 1.
> + // If __m in {8, 9, 10, 11, 12}, then b is 1 if, and only if, __m is
> + // even. Hence, b = (__m ^ 1) & 1.
>
> // Therefore, b = (__m ^ c) & 1, where c = 0, if __m < 8, or c = 1 if
> // __m >= 8, that is, c = __m >> 3.
>
> - // The above mathematically justifies this implementation whose
> - // performance does not depend on look-up tables being on the L1 cache.
> - return chrono::day{__m != 2 ? ((__m ^ (__m >> 3)) & 1) | 30
> - : _M_y.is_leap() ? 29 : 28};
> + // Since 30 = (11110)_2 and __m <= 31 = (11111)_2, the "& 1" in b's
> + // calculation is unnecessary.
> +
> + // The performance of this implementation does not depend on look-up
> + // tables being on the L1 cache.
> + return chrono::day{__m != 2 ? (__m ^ (__m >> 3)) | 30
> + : _M_y.is_leap() ? 29 : 28};
> }
>
> constexpr
> --
> 2.41.0
>
prev parent reply other threads:[~2023-11-14 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 16:44 Cassio Neri
2023-11-14 22:47 ` Jonathan Wakely [this message]
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='CACb0b4=xTBgH2saDq7OKf+tE+cMA6zoXnN5fbh2uwsVbYcfzgg@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=cassio.neri@gmail.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).