public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i.nixman at autistici dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/94756] strtoflt128 assigns some subnormals incorrectly on MS Windows
Date: Thu, 19 Jan 2023 01:27:45 +0000	[thread overview]
Message-ID: <bug-94756-4-bqDNfYafUu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94756-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from niXman <i.nixman at autistici dot org> ---
Created attachment 54301
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54301&action=edit
patch

(In reply to niXman from comment #9)
> although I think these two bugs have the same cause...

right, it was the same bug and this bug was caused by 32-bit variable overflow.

the overflow was fixed for i686-mingw-w64, x86_64-mingw-w64, and for i686 and
x86_64 linux.

Jakiub, John, could you look please on attached patch?

  parent reply	other threads:[~2023-01-19  1:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25  7:14 [Bug libquadmath/94756] New: " sisyphus359 at gmail dot com
2023-01-17 21:25 ` [Bug libquadmath/94756] " i.nixman at autistici dot org
2023-01-18 10:51 ` i.nixman at autistici dot org
2023-01-18 10:53 ` i.nixman at autistici dot org
2023-01-18 18:40 ` jakub at gcc dot gnu.org
2023-01-18 18:43 ` i.nixman at autistici dot org
2023-01-18 18:45 ` i.nixman at autistici dot org
2023-01-18 18:49 ` i.nixman at autistici dot org
2023-01-18 19:08 ` jakub at gcc dot gnu.org
2023-01-18 19:10 ` i.nixman at autistici dot org
2023-01-18 19:11 ` i.nixman at autistici dot org
2023-01-19  1:27 ` i.nixman at autistici dot org [this message]
2023-03-02 23:42 ` cvs-commit at gcc dot gnu.org
2023-03-02 23:44 ` jakub at gcc dot gnu.org
2023-03-03  8:20 ` i.nixman at autistici dot org
2023-03-05 11:18 ` i.nixman at autistici dot org
2023-03-05 11:20 ` i.nixman at autistici dot org
2023-03-05 14:30 ` i.nixman at autistici dot org
2023-03-07 10:31 ` i.nixman at autistici dot org
2023-03-19  5:30 ` cvs-commit at gcc dot gnu.org
2023-03-20 10:28 ` jakub at gcc dot gnu.org
2023-05-02 20:15 ` cvs-commit at gcc dot gnu.org
2023-05-03  9:24 ` jakub at gcc dot gnu.org
2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org
2023-05-04  7: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-94756-4-bqDNfYafUu@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).