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)] c++: mark short-enums as packed
Date: Sun, 19 Nov 2023 06:31:11 +0000 (GMT)	[thread overview]
Message-ID: <20231119063111.645303858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:48dece46f1b5ea2fa7b3bf8c8165047484073a7c

commit 48dece46f1b5ea2fa7b3bf8c8165047484073a7c
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Sun Nov 19 01:22:31 2023 -0300

    c++: mark short-enums as packed
    
    Unlike C, C++ doesn't mark enums shortened by -fshort-enums as packed.
    This makes for undesirable warning differences between C and C++,
    e.g. c-c++-common/analyzer/null-deref-pr108251-smp_fetch_ssl_fc_has_early*.c
    triggers a warning about a type cast from a pointer to enum that, when
    packed, might not be sufficiently aligned.
    
    This change is not enough for that warning to trigger.  The tree
    expression generated by the C++ front-end is also a little too
    complicated for us get to the base pointer.  A separate patch takes
    care of that.
    
    
    for  gcc/cp/ChangeLog
    
            * decl.cc (finish_enum_value_list): Set TYPE_PACKED if
            use_short_enum, and propagate it to variants.

Diff:
---
 gcc/cp/decl.cc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/gcc/cp/decl.cc b/gcc/cp/decl.cc
index 038c5ab71f2..f6d5645d508 100644
--- a/gcc/cp/decl.cc
+++ b/gcc/cp/decl.cc
@@ -16881,6 +16881,12 @@ finish_enum_value_list (tree enumtype)
       /* If -fstrict-enums, still constrain TYPE_MIN/MAX_VALUE.  */
       if (flag_strict_enums)
 	set_min_and_max_values_for_integral_type (enumtype, precision, sgn);
+
+      if (use_short_enum)
+	{
+	  TYPE_PACKED (enumtype) = use_short_enum;
+	  fixup_attribute_variants (enumtype);
+	}
     }
   else
     underlying_type = ENUM_UNDERLYING_TYPE (enumtype);

             reply	other threads:[~2023-11-19  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-19  6:31 Alexandre Oliva [this message]
2023-11-19  8:11 Alexandre Oliva
2023-11-23 11:46 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=20231119063111.645303858D33@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).