public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104883] <system_error> should define all std::errc enumerators
Date: Wed, 01 Feb 2023 21:23:23 +0000 [thread overview]
Message-ID: <bug-104883-4-i0810cxoCo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104883-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104883
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> Which causes errors when we rely on that being present, e.g. for AVR:
>
> /home/jwakely/src/gcc/build-avr/avr/libstdc++-v3/include/charconv: In
> function ‘std::to_chars_result std::__detail::__to_chars(char*, char*, _Tp,
> int)’:
> /home/jwakely/src/gcc/build-avr/avr/libstdc++-v3/include/charconv:132:28:
> error: ‘value_too_large’ is not a member of ‘std::errc’; did you mean
> ‘file_too_large’?
> 132 | __res.ec = errc::value_too_large;
> | ^~~~~~~~~~~~~~~
> | file_too_large
This specific problem is now fixed for avr, but the general problem remains.
next prev parent reply other threads:[~2023-02-01 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 15:20 [Bug libstdc++/104883] New: " redi at gcc dot gnu.org
2022-09-22 10:47 ` [Bug libstdc++/104883] " redi at gcc dot gnu.org
2022-09-22 21:59 ` redi at gcc dot gnu.org
2023-02-01 21:07 ` cvs-commit at gcc dot gnu.org
2023-02-01 21:23 ` redi at gcc dot gnu.org [this message]
2023-02-02 9:34 ` cvs-commit at gcc dot gnu.org
2023-03-16 16:51 ` cvs-commit 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-104883-4-i0810cxoCo@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).