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/111914] ICE with function pointer array as argument with non-constant size Date: Sun, 22 Oct 2023 02:31:44 +0000 [thread overview] Message-ID: <bug-111914-4-ZGfY74VC7k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111914-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111914 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |7.1.0 Keywords| |ice-checking, | |ice-on-valid-code Summary|GCC: 14: ICE when function |ICE with function pointer |pointer array as argument |array as argument with | |non-constant size --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed, goes back to before GCC 7, maybe before (-fchecking only exist in GCC 7+). Slightly better testcase: ``` __attribute__((always_inline)) static inline void f(int n, int (*a())[n]) { } void g(void) { int (*a())[1]; f(1, a); } ```
next prev parent reply other threads:[~2023-10-22 2:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-22 2:23 [Bug c/111914] New: GCC: 14: ICE when function pointer array as arguments 141242068 at smail dot nju.edu.cn 2023-10-22 2:31 ` pinskia at gcc dot gnu.org [this message] 2023-10-23 9:17 ` [Bug ipa/111914] ICE with function pointer array as argument with non-constant size rguenth at gcc dot gnu.org 2023-10-23 11:08 ` rguenth at gcc dot gnu.org 2023-10-23 11:29 ` rguenth at gcc dot gnu.org 2023-10-23 13:33 ` cvs-commit at gcc dot gnu.org 2023-10-23 13:33 ` rguenth 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-111914-4-ZGfY74VC7k@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).