public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100111] [10/11 Regression] `-fno-elide-constructors` with `constexpr` ctors causes ICE in GCC 10.3 Date: Fri, 16 Apr 2021 14:01:46 +0000 [thread overview] Message-ID: <bug-100111-4-1K8CJKLZ28@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100111-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100111 --- Comment #6 from Liu Hao <lh_mouse at 126 dot com> --- I have bootstrapped GCC 10.3.1 on `i686,x86_64}-w64-mingw32` successfully and verified that this patch fixed the error.
next prev parent reply other threads:[~2021-04-16 14:01 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 5:37 [Bug c++/100111] New: `-fno-elide-constructors` " lh_mouse at 126 dot com 2021-04-16 7:36 ` [Bug c++/100111] [10/11 Regression] `-fno-elide-constructors` with `constexpr` ctors " rguenth at gcc dot gnu.org 2021-04-16 8:14 ` jakub at gcc dot gnu.org 2021-04-16 9:04 ` jakub at gcc dot gnu.org 2021-04-16 10:16 ` jakub at gcc dot gnu.org 2021-04-16 11:11 ` lh_mouse at 126 dot com 2021-04-16 14:01 ` lh_mouse at 126 dot com [this message] 2021-04-16 14:10 ` jason at gcc dot gnu.org 2021-04-16 15:44 ` cvs-commit at gcc dot gnu.org 2021-04-17 3:33 ` [Bug c++/100111] [10 " jason at gcc dot gnu.org 2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:53 ` jakub at gcc dot gnu.org 2022-04-13 14:18 ` cvs-commit at gcc dot gnu.org 2022-05-06 20:30 ` cvs-commit at gcc dot gnu.org 2022-05-12 20:13 ` cvs-commit at gcc dot gnu.org 2022-05-12 21:15 ` 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-100111-4-1K8CJKLZ28@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).