From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>
Subject: Re: [PATCH #4/4] testsuite: discard c++ exclusion on underaligned pointer warning
Date: Thu, 23 Nov 2023 12:27:22 -0800 [thread overview]
Message-ID: <42851797-FFC7-4D5E-A185-F67F4EC1F5A3@comcast.net> (raw)
In-Reply-To: <oril5xqhin.fsf@lxoliva.fsfla.org>
On Nov 19, 2023, at 6:34 PM, Alexandre Oliva <oliva@adacore.com> wrote:
>
> Having extended check_and_warn_address_or_pointer_of_packed_member to
> find the packed (short) enum pointer in the cast expression coming
> from the C++ front-end, and amended the C++ front end to mark short
> enums as TYPE_PACKED, C++ issues the same warning that C does for
> c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c,
> so drop the exclusion.
>
> Regstrapped on x86_64-linux-gnu, also tested on arm-eabi with default
> cpu on trunk, and with tms570 on gcc-13. Ok to install?
Ok.
prev parent reply other threads:[~2023-11-23 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 7:36 [PATCH] testsuite: analyzer: expect alignment warning with -fshort-enums Alexandre Oliva
2023-11-19 15:13 ` Jeff Law
2023-11-20 22:19 ` David Malcolm
2023-11-20 2:33 ` [PATCH #2/4] c++: mark short-enums as packed Alexandre Oliva
2023-11-20 19:55 ` Jason Merrill
2023-11-22 8:17 ` Alexandre Oliva
2023-11-22 18:12 ` Jason Merrill
2023-11-22 18:26 ` Jason Merrill
2023-11-29 9:39 ` Alexandre Oliva
2023-11-29 19:03 ` Jason Merrill
2023-11-30 7:21 ` Alexandre Oliva
2023-11-20 2:34 ` [PATCH #3/4] warn on cast of pointer to packed plus constant Alexandre Oliva
2023-11-20 2:34 ` [PATCH #4/4] testsuite: discard c++ exclusion on underaligned pointer warning Alexandre Oliva
2023-11-23 20:27 ` Mike Stump [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=42851797-FFC7-4D5E-A185-F67F4EC1F5A3@comcast.net \
--to=mikestump@comcast.net \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.org \
--cc=oliva@adacore.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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: link
Be 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).