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++/114519] [14 Regression] GCC 14 trunk fails to compile chrono with -fno-char8_t -std=gnu++20
Date: Tue, 02 Apr 2024 20:13:57 +0000	[thread overview]
Message-ID: <bug-114519-4-uFxxvAzvXw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114519-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED
      Known to work|                            |13.2.0
      Known to fail|                            |14.0
            Summary|GCC 14 trunk fails to       |[14 Regression] GCC 14
                   |compile chrono with         |trunk fails to compile
                   |-fno-char8_t -std=gnu++20   |chrono with -fno-char8_t
                   |                            |-std=gnu++20

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed, thanks for the report.

  parent reply	other threads:[~2024-04-02 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 15:20 [Bug c++/114519] New: " janisozaur+gcc at gmail dot com
2024-03-28 15:26 ` [Bug libstdc++/114519] " pinskia at gcc dot gnu.org
2024-03-28 21:31 ` redi at gcc dot gnu.org
2024-04-02 20:12 ` cvs-commit at gcc dot gnu.org
2024-04-02 20:13 ` redi at gcc dot gnu.org [this message]
2024-04-08 16:45 ` [Bug libstdc++/114519] [14 Regression] " 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-114519-4-uFxxvAzvXw@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).