public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/113598] [11/12/13/14 Regression] GCC internal compiler error Date: Thu, 25 Jan 2024 16:07:45 +0000 [thread overview] Message-ID: <bug-113598-4-Xuj8Xvy0yk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113598-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113598 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|GCC internal compiler error |[11/12/13/14 Regression] | |GCC internal compiler error Known to work| |4.4.7, 4.8.1, 4.8.5 Known to fail| |4.9.0, 5.1.0 Target Milestone|--- |11.5 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced testcase: ``` struct Cpu { int op_nop(); }; typedef int(Cpu::*OpCode)(); void f() { new OpCode[256]{&Cpu::op_nop}; } ```
next prev parent reply other threads:[~2024-01-25 16:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-25 12:34 [Bug c++/113598] New: " jlame646 at gmail dot com 2024-01-25 15:44 ` [Bug c++/113598] " mpolacek at gcc dot gnu.org 2024-01-25 16:07 ` pinskia at gcc dot gnu.org [this message] 2024-01-25 16:22 ` [Bug c++/113598] [11/12/13/14 Regression] GCC internal compiler error since r0-124275 jakub at gcc dot gnu.org 2024-01-25 16:23 ` jakub at gcc dot gnu.org 2024-01-25 17:02 ` jason at gcc dot gnu.org 2024-01-25 20:22 ` cvs-commit at gcc dot gnu.org 2024-05-24 13:25 ` [Bug c++/113598] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-05-24 13:26 ` cvs-commit at gcc dot gnu.org 2024-05-24 18:38 ` cvs-commit at gcc dot gnu.org 2024-05-24 18:40 ` jason 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-113598-4-Xuj8Xvy0yk@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).