public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/111163] signed integer overflow in std::format("{:%S}",std::chrono::duration....)
Date: Sat, 26 Aug 2023 16:06:20 +0000	[thread overview]
Message-ID: <bug-111163-4-1Ke6MDSfmX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111163-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111163

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
We could also just have a "can_hh_mm_ss" check, as I think we use hh_mm_ss in
most places where we do these conversations. Then we would just check once, not
on every cast. I don't think we want to change the conversions inside the
hh_mm_ss constructor

  parent reply	other threads:[~2023-08-26 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 12:56 [Bug libstdc++/111163] New: " gcc at pauldreik dot se
2023-08-26 13:52 ` [Bug libstdc++/111163] " redi at gcc dot gnu.org
2023-08-26 13:57 ` redi at gcc dot gnu.org
2023-08-26 14:02 ` gcc at pauldreik dot se
2023-08-26 16:06 ` redi at gcc dot gnu.org [this message]
2023-08-31 13:22 ` redi at gcc dot gnu.org
2024-05-21  9:16 ` jakub at gcc dot gnu.org

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=bug-111163-4-1Ke6MDSfmX@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).