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 ipa/109607] New: IPA replaces stmt with invalid gimple Date: Mon, 24 Apr 2023 12:53:46 +0000 [thread overview] Message-ID: <bug-109607-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109607 Bug ID: 109607 Summary: IPA replaces stmt with invalid gimple Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- On cfghooks.cc we replace BIT_FIELD_REF <*this_8(D), 8, 56> with BIT_FIELD_REF <VIEW_CONVERT_EXPR<const struct profile_count>(ISRA.814), 8, 56> in ipa_param_body_adjustments::modify_expression. The replacement seems to be of type 'unsigned long'. This is (should be) invalid GIMPLE unless ISRA.814 is made a non-register. Note when replacing memory with register BIT_FIELD_REFs have to be careful with endianess (IIRC), thus the replacement looks dangerous anyway. A fix for PR109594 will make us trip over this new IL checking during bootstrap.
next reply other threads:[~2023-04-24 12:53 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-24 12:53 rguenth at gcc dot gnu.org [this message] 2023-04-24 12:57 ` [Bug ipa/109607] " rguenth at gcc dot gnu.org 2023-04-26 11:05 ` rguenth at gcc dot gnu.org 2023-04-26 13:16 ` jamborm at gcc dot gnu.org 2023-04-27 10:31 ` cvs-commit at gcc dot gnu.org 2023-04-27 10:31 ` 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-109607-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).