public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/113050] New: -Wincompatible-pointer-types emitted as a warning, not an error, for __atomic_load Date: Sun, 17 Dec 2023 10:23:21 +0000 [thread overview] Message-ID: <bug-113050-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113050 Bug ID: 113050 Summary: -Wincompatible-pointer-types emitted as a warning, not an error, for __atomic_load Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: arsen at gcc dot gnu.org, fw at gcc dot gnu.org Target Milestone: --- Noticed this when building udisks. I suspect this is actually a dupe of PR69404, but I felt it was worth filing separately given it's interesting to have it warn-but-not-error. The expectation was that this would error (b/c of new 14 default), not just warn: ``` $ gcc -c udisksenumtypes.i udisksenumtypes.i: In function ‘udisks_get_type’: udisksenumtypes.i:5:3: warning: argument 2 of ‘__atomic_load’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types] 5 | __atomic_load(in, &out, 5); | ^~~~~~~~~~~~~ ``` It does the right thing with explicit -Werror=: ``` $ gcc -c udisksenumtypes.i -Werror=incompatible-pointer-types udisksenumtypes.i: In function ‘udisks_get_type’: udisksenumtypes.i:5:3: error: argument 2 of ‘__atomic_load’ discards ‘volatile’ qualifier [-Werror=incompatible-pointer-types] 5 | __atomic_load(in, &out, 5); | ^~~~~~~~~~~~~ cc1: some warnings being treated as errors ``` udisksenumtypes.i: ``` volatile long out; volatile long* in; void udisks_get_type() { __atomic_load(in, &out, 5); } ```
next reply other threads:[~2023-12-17 10:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-17 10:23 sjames at gcc dot gnu.org [this message] 2023-12-17 10:36 ` [Bug c/113050] " fw at gcc dot gnu.org 2023-12-17 10:38 ` sjames at gcc dot gnu.org 2023-12-17 10:40 ` fw at gcc dot gnu.org 2023-12-17 15:39 ` [Bug c/113050] __atomic_* builtins should use -Wdiscarded-qualifiers instead of -Wincompatible-pointer-types fw at gcc dot gnu.org 2023-12-20 16:24 ` cvs-commit at gcc dot gnu.org 2023-12-20 16:24 ` fw at gcc dot gnu.org 2023-12-21 6:38 ` sjames 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-113050-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).