public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/101236] [12 Regression] bits/unique_ptr.h:658:48: error: invalid use of incomplete type ‘class llvm::APFloat’ since r12-1778-g17bc3848e065c0980523e1a1592f2f03b24b4f1c Date: Mon, 27 Dec 2021 15:02:29 +0000 [thread overview] Message-ID: <bug-101236-4-lw017JiAlh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101236-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101236 Bug 101236 depends on bug 101239, which changed state. Bug 101239 Summary: "Internal compiler error: Error reporting routines re-entered." in size_in_bytes_loc https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101239 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
prev parent reply other threads:[~2021-12-27 15:02 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-28 8:17 [Bug libstdc++/101236] New: [12 Regression] bits/unique_ptr.h:658:48: error: invalid use of incomplete type ‘class llvm::APFloat’ marxin at gcc dot gnu.org 2021-06-28 8:18 ` [Bug libstdc++/101236] [12 Regression] bits/unique_ptr.h:658:48: error: invalid use of incomplete type ‘class llvm::APFloat’ since r12-1778-g17bc3848e065c0980523e1a1592f2f03b24b4f1c marxin at gcc dot gnu.org 2021-06-28 9:13 ` rguenth at gcc dot gnu.org 2021-06-28 9:41 ` redi at gcc dot gnu.org 2021-06-28 10:18 ` marxin at gcc dot gnu.org 2021-06-28 10:25 ` redi at gcc dot gnu.org 2021-06-28 11:51 ` redi at gcc dot gnu.org 2021-06-28 13:23 ` cvs-commit at gcc dot gnu.org 2021-06-28 13:27 ` redi at gcc dot gnu.org 2021-07-02 11:15 ` cvs-commit at gcc dot gnu.org 2021-12-27 15:02 ` ppalka at gcc dot gnu.org [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=bug-101236-4-lw017JiAlh@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: linkBe 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).