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)] testsuite: analyzer: expect alignment warning with -fshort-enums
Date: Sun, 19 Nov 2023 05:22:46 +0000 (GMT)	[thread overview]
Message-ID: <20231119052246.BA0D13858427@sourceware.org> (raw)

https://gcc.gnu.org/g:f893dacf4a161f69fd7c06f6fbdb41a9569e9eb8

commit f893dacf4a161f69fd7c06f6fbdb41a9569e9eb8
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sat Nov 18 02:11:53 2023 -0300

    testsuite: analyzer: expect alignment warning with -fshort-enums
    
    On targets that have -fshort-enums enabled by default, the type casts
    in the pr108251 analyzer tests warn that the byte-aligned enums may
    not be sufficiently aligned to be a struct connection *.  The function
    can't know better, the warning is reasonable, the code doesn't
    expected enums to be shorter and less aligned than the struct.
    
    Rather than use -fno-short-enums, I decided to embrace the warning on
    targets that have short_enums enabled by default.
    
    However, C++ doesn't issue the warning, because even with
    -fshort-enums, enumeration types are not TYPE_PACKED, and the
    expression is not sufficiently simplified by the C++ front-end for
    check_and_warn_address_or_pointer_of_packed_member to identify the
    insufficiently aligned pointer.  So don't expect the warning there.
    
    
    for  gcc/testsuite/ChangeLog
    
            * c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c:
            Expect "unaligned pointer value" warning on short_enums
            targets, but not in c++.
            * c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c:
            Likewise.

Diff:
---
 .../analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c        | 2 +-
 .../analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c b/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c
index c46ffe91a6b..d87853e0a9f 100644
--- a/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c
+++ b/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early-O2.c
@@ -61,7 +61,7 @@ static inline enum obj_type obj_type(const enum obj_type *t)
 }
 static inline struct connection *__objt_conn(enum obj_type *t)
 {
- return ((struct connection *)(((char *)(t)) - ((long)&((struct connection *)0)->obj_type)));
+ return ((struct connection *)(((char *)(t)) - ((long)&((struct connection *)0)->obj_type))); /* { dg-warning "unaligned pointer value" "warning" { target { short_enums && ! c++ } } } */
 }
 static inline struct connection *objt_conn(enum obj_type *t)
 {
diff --git a/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c b/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c
index ef34a76c50d..1c64de31982 100644
--- a/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c
+++ b/gcc/testsuite/c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c
@@ -60,7 +60,7 @@ static inline enum obj_type obj_type(const enum obj_type *t)
 }
 static inline struct connection *__objt_conn(enum obj_type *t)
 {
- return ((struct connection *)(((char *)(t)) - ((long)&((struct connection *)0)->obj_type)));
+ return ((struct connection *)(((char *)(t)) - ((long)&((struct connection *)0)->obj_type))); /* { dg-warning "unaligned pointer value" "warning" { target { short_enums && ! c++ } } } */
 }
 static inline struct connection *objt_conn(enum obj_type *t)
 {

             reply	other threads:[~2023-11-19  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  5:22 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-19  5:25 Alexandre Oliva
2023-11-19  4:44 Alexandre Oliva
2023-11-18  5:36 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=20231119052246.BA0D13858427@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: 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).