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++/59974] ostream crashes on large numbers under Windows
Date: Fri, 09 Jun 2023 09:45:00 +0000	[thread overview]
Message-ID: <bug-59974-4-O8rMk9tXTF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59974-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-06-09
             Status|UNCONFIRMED                 |NEW

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This should be submitted to the mailing lists for review.

Ideally, with copyright assignment from Stephen, or a DCO sign-off:
https://gcc.gnu.org/dco.html

If this is Stephen's first GCC contribution, then maybe we can accept it, as
it's only about 10 lines of logic.

I'd prefer if these changes were  guarded behind some #if check, so we don't
add unnecessary overhead on targets that don't need it. Or at the very least,
use __builtin_expect to predict that the branch for handling -1 is unlikely.

  parent reply	other threads:[~2023-06-09  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 23:28 [Bug libstdc++/59974] New: " steve at sk2 dot org
2014-01-28 23:29 ` [Bug libstdc++/59974] " steve at sk2 dot org
2014-01-28 23:33 ` pinskia at gcc dot gnu.org
2014-01-28 23:36 ` steve at sk2 dot org
2023-06-09  1:52 ` 10walls at gmail dot com
2023-06-09  9:45 ` redi at gcc dot gnu.org [this message]
2023-06-09 11:18 ` steve at sk2 dot 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-59974-4-O8rMk9tXTF@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).