public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/101645] warn about neg of unsigned type should be added to -Wsign-conversion Date: Wed, 28 Jul 2021 17:55:54 +0000 [thread overview] Message-ID: <bug-101645-4-JedUoRhEu2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101645-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101645 --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- (I wrote this before comment 4 was added ...) What would the precise semantics of the suggested warning be? What kind of expressions do you expect to warn, and which should not? How would I suppress the warning if -x is exactly what I intended to write and it does exactly what I expect? For example, the implementation of std::align uses: inline void* align(size_t __align, size_t __size, void*& __ptr, size_t& __space) noexcept { if (__space < __size) return nullptr; const auto __intptr = reinterpret_cast<uintptr_t>(__ptr); const auto __aligned = (__intptr - 1u + __align) & -__align; // ... How would I prevent -__align from warning?
prev parent reply other threads:[~2021-07-28 17:55 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-27 15:21 [Bug c/101645] New: -Wsign-conversion misses negation of unsigned int matthew at wil dot cx 2021-07-27 15:27 ` [Bug c/101645] " jrtc27 at jrtc27 dot com 2021-07-27 19:06 ` [Bug c/101645] warn about neg of unsigned type should be added to -Wsign-conversion pinskia at gcc dot gnu.org 2021-07-27 21:27 ` jhubbard at nvidia dot com 2021-07-28 12:35 ` matthew at wil dot cx 2021-07-28 17:55 ` redi at gcc dot gnu.org [this message]
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-101645-4-JedUoRhEu2@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).