public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100361] gcc-11 for msp430-elf fails to build: src/c++17/floating_to_chars.cc:107: d2fixed_full_table.h:1283:23: error: size of array ‘POW10_SPLIT_2’ exceeds maximum object size ‘32767’
Date: Tue, 18 May 2021 13:51:58 +0000	[thread overview]
Message-ID: <bug-100361-4-43vqgxn4dC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100361-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> ---
(In reply to Patrick Palka from comment #3)

> Btw, we already disable the floating-point to_chars on targets without a
> binary64 double.  So is our test for detecting binary64 not accurate enough,
> or are these 16-bit targets whose double type really is binary64?

At least in the case of eSi-RISC, it is the latter.

  parent reply	other threads:[~2021-05-18 13:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 18:39 [Bug target/100361] New: " slyfox at gcc dot gnu.org
2021-05-18 12:23 ` [Bug libstdc++/100361] " amylaar at gcc dot gnu.org
2021-05-18 12:45 ` redi at gcc dot gnu.org
2021-05-18 13:43 ` ppalka at gcc dot gnu.org
2021-05-18 13:44 ` amylaar at gcc dot gnu.org
2021-05-18 13:51 ` amylaar at gcc dot gnu.org [this message]
2021-05-18 13:54 ` redi at gcc dot gnu.org
2021-05-18 14:39 ` amylaar at gcc dot gnu.org
2021-05-19 15:12 ` amylaar at gcc dot gnu.org
2021-05-19 15:56 ` redi at gcc dot gnu.org
2021-05-19 17:45 ` slyfox at gcc dot gnu.org
2021-05-20 12:26 ` cvs-commit at gcc dot gnu.org
2021-05-20 12:41 ` cvs-commit at gcc dot gnu.org
2023-06-09  9:55 ` redi 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-100361-4-43vqgxn4dC@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).