public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] warn on cast of pointer to packed plus constant Date: Sun, 19 Nov 2023 07:02:17 +0000 (GMT) [thread overview] Message-ID: <20231119070217.987563876053@sourceware.org> (raw) https://gcc.gnu.org/g:9d7a231e7496533834e194131a0971a533534d3b commit 9d7a231e7496533834e194131a0971a533534d3b Author: Alexandre Oliva <oliva@adacore.com> Date: Sun Nov 19 01:25:01 2023 -0300 warn on cast of pointer to packed plus constant c-c++-common/analyzer/null-deref-pr108251-smp-fetch_ssl_fc_has_early.c gets an unaligned pointer value warning on -fshort-enums targets in C, but not in C++. The former simplifies the offset-and-cast expression enough that check_and_warn_address_or_pointer_of_packed_member finds no more than a type cast of the base pointer, but in C++, the entire expression, with cast, constant offsetting, and cast again, is retained, and that's too much for the warning code. Or rather it was. It's easy enough to take the base pointer from PLUS_POINTER_EXPR, and a constant offset can't possibly increase alignment for just any pointer of laxer alignment, so we can safely disregard the offset. This should improve the warning even in C, if the packed enum is at a nonzero offset into the containing struct. for gcc/c-family/ChangeLog * c-warn.cc (check_and_warn_address_or_pointer_of_packed_member): Take the base pointer from PLUS_POINTER_EXPR when the addend is constant. Diff: --- gcc/c-family/c-warn.cc | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/gcc/c-family/c-warn.cc b/gcc/c-family/c-warn.cc index d2938b91043..39f5ddc577c 100644 --- a/gcc/c-family/c-warn.cc +++ b/gcc/c-family/c-warn.cc @@ -3108,9 +3108,17 @@ check_and_warn_address_or_pointer_of_packed_member (tree type, tree rhs) do { - while (TREE_CODE (rhs) == COMPOUND_EXPR) - rhs = TREE_OPERAND (rhs, 1); - orig_rhs = rhs; + do + { + orig_rhs = rhs; + while (TREE_CODE (rhs) == COMPOUND_EXPR) + rhs = TREE_OPERAND (rhs, 1); + /* Constants can't increase the alignment. */ + while (TREE_CODE (rhs) == POINTER_PLUS_EXPR + && TREE_CONSTANT (TREE_OPERAND (rhs, 1))) + rhs = TREE_OPERAND (rhs, 0); + } + while (orig_rhs != rhs); STRIP_NOPS (rhs); nop_p |= orig_rhs != rhs; }
next reply other threads:[~2023-11-19 7:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-19 7:02 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-11-23 11:46 Alexandre Oliva 2023-11-19 8:32 Alexandre Oliva 2023-11-19 8:18 Alexandre Oliva 2023-11-19 8:11 Alexandre Oliva 2023-11-19 6:31 Alexandre Oliva
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=20231119070217.987563876053@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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).