From: Jonathan Wakely <jwakely@redhat.com>
To: Hans-Peter Nilsson <hp@axis.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Build-break in libstdc++-v3 at r14-1442-ge1240bda3e0bb1 for non-float128 targets
Date: Wed, 31 May 2023 16:32:18 +0100 [thread overview]
Message-ID: <CACb0b4=nDx9Q1-yELJrNTEUCSTkoJ0LSXZ21O5AzK30JFRssBA@mail.gmail.com> (raw)
In-Reply-To: <20230531152805.9D4732043D@pchp3.se.axis.com>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
On Wed, 31 May 2023 at 16:29, Hans-Peter Nilsson via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> Since I don't see a quick fix at r14-1444-g3f4853a5f00fab, I
> thought I'd better notify the author (I have written authors
> if there was more than one ;-) of suspect commits in the
> range r14-1425-g80ee7d02e8db48..e1240bda3e0b for the
> build-break at r14-1442-ge1240bda3e0bb1 for cris-elf, where
> I get:
>
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1330:47: error:
> '_Float128' is not supported on this target
> 1330 | from_chars(const char* first, const char* last, _Float128& value,
> | ^
>
Sorry, I'll fix or revert it today.
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1330:49: error:
> expected identifier before '_Float128'
> 1330 | from_chars(const char* first, const char* last, _Float128& value,
> | ^~~~~~~~~
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1330:49: error:
> '_Float128' is not supported on this target
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1330:49: error:
> expected ',' or '...' before '_Float128'
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc: In function
> 'std::from_chars_result std::from_chars(const char*, const char*, int)':
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1340:53: error: 'fmt'
> was not declared in this scope; did you mean 'fma'?
> 1340 | auto res = std::from_chars(first, last, ldbl_val, fmt);
> | ^~~
> | fma
> /x/gcc/libstdc++-v3/src/c++17/floating_from_chars.cc:1342:5: error:
> 'value' was not declared in this scope
> 1342 | value = ldbl_val;
> | ^~~~~
> make[5]: *** [Makefile:587: floating_from_chars.lo] Error 1
>
> brgds, H-P
>
>
next prev parent reply other threads:[~2023-05-31 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 15:28 Hans-Peter Nilsson
2023-05-31 15:32 ` Jonathan Wakely [this message]
2023-05-31 20:06 ` Jonathan Wakely
2023-06-01 4:21 ` Hans-Peter Nilsson
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='CACb0b4=nDx9Q1-yELJrNTEUCSTkoJ0LSXZ21O5AzK30JFRssBA@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=libstdc++@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).