public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/109644] New: Missing GIMPLE IL verification Date: Thu, 27 Apr 2023 08:41:02 +0000 [thread overview] Message-ID: <bug-109644-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109644 Bug ID: 109644 Summary: Missing GIMPLE IL verification Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org Target Milestone: --- We are missing GIMPLE IL verification of handled component operations on registers. There's only a subset of operations allowed and they should not stack but behave like UNARY ops. The subset allowed is REALPART_EXPR, IMAGPART_EXPR, VIEW_CONVERT_EXPR and BIT_FIELD_REF. In particular ops that require aggregate types such as ARRAY_REF and COMPONENT_REF are not allowed, but the missing IL verification makes those sneak through with the register wrapped in a VIEW_CONVERT_EXPR producing the aggregate type.
next reply other threads:[~2023-04-27 8:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-27 8:41 rguenth at gcc dot gnu.org [this message] 2023-04-27 8:43 ` [Bug middle-end/109644] " rguenth at gcc dot gnu.org 2023-04-27 10:31 ` rguenth at gcc dot gnu.org 2023-04-28 9:49 ` cvs-commit at gcc dot gnu.org 2023-04-28 9:49 ` 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-109644-4@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).