public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/106941] New: Warn/Error conversion between opaque types in generic handling Date: Wed, 14 Sep 2022 12:42:23 +0000 [thread overview] Message-ID: <bug-106941-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106941 Bug ID: 106941 Summary: Warn/Error conversion between opaque types in generic handling Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-checking Severity: minor Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: linkw at gcc dot gnu.org CC: bergner at gcc dot gnu.org, hubicka at gcc dot gnu.org, rguenth at gcc dot gnu.org, segher at gcc dot gnu.org, unassigned at gcc dot gnu.org Depends on: 106833 Target Milestone: --- Target: powerpc*-linux-gnu In PR106833, Segher pointed out that we should emit warning or error messages for conversion between two opaque types even if they have the same mode, as documentation said conversion should not expected for opaque type. For now, rs6000_invalid_conversion has some checks which are mainly based on mode but they are target specific. As #c12 of PR106833, Segher expected this can be handled generically, no target code is needed for it. Since "we currently have only one type for each of our two opaque modes", give it a minor severity for now. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106833 [Bug 106833] Miss to handle OPAQUE_TYPE specially in verify_type
next reply other threads:[~2022-09-14 12:42 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-14 12:42 linkw at gcc dot gnu.org [this message] 2022-09-14 12:43 ` [Bug middle-end/106941] " linkw 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-106941-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).