public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/61399] LDBL_MAX is incorrect with IBM long double format / overflow issues near large values Date: Tue, 03 Jun 2014 07:04:00 -0000 [thread overview] Message-ID: <bug-61399-4-5BR4a35cPH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61399-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61399 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I think lowering LDBL_MAX_EXP would be far worse than this. The double-double format is unusable for any real numerics in so many ways that this is just one small part of that, the variable precision from 106 to thousands of precision bits depending on exact value is far worse.
next prev parent reply other threads:[~2014-06-03 7:04 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-02 23:37 [Bug c/61399] New: " vincent-gcc at vinc17 dot net 2014-06-03 7:04 ` jakub at gcc dot gnu.org [this message] 2014-06-03 7:45 ` [Bug c/61399] " vincent-gcc at vinc17 dot net 2021-08-18 15:04 ` vincent-gcc at vinc17 dot net 2021-08-18 15:13 ` jakub at gcc dot gnu.org 2021-08-18 15:40 ` vincent-gcc at vinc17 dot net
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-61399-4-5BR4a35cPH@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: linkBe 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).