From: Hans-Peter Nilsson <hp@axis.com>
To: Jonathan Wakely <jwakely@redhat.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: Thu, 1 Jun 2023 06:21:09 +0200 [thread overview]
Message-ID: <20230601042109.EFBB120418@pchp3.se.axis.com> (raw)
In-Reply-To: <CACb0b4=NWhy7twvcAxF93NnbBqP_6htDfSvpyxKweQ0XRNw-Dw@mail.gmail.com> (message from Jonathan Wakely on Wed, 31 May 2023 21:06:16 +0100)
> From: Jonathan Wakely <jwakely@redhat.com>
> Date: Wed, 31 May 2023 21:06:16 +0100
> On Wed, 31 May 2023 at 16:32, Jonathan Wakely <jwakely@redhat.com> wrote:
> > 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.
> >
>
> It should be fixed at r14-1451-ga239a35075ffd8
JFTR: confirmed at r14-1451-ga239a35075ffd8, thanks!
brgds, H-P
prev parent reply other threads:[~2023-06-01 4:21 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
2023-05-31 20:06 ` Jonathan Wakely
2023-06-01 4:21 ` Hans-Peter Nilsson [this message]
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=20230601042109.EFBB120418@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.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).