From: Vit Kabele <vit.kabele@sysgo.com>
To: polacek@redhat.com
Cc: vit@kabele.me, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c: Extend the -Wpadded message with actual padding size
Date: Mon, 20 Jun 2022 15:50:10 +0200 [thread overview]
Message-ID: <YrB7EQFuCgSXHSEz@czspare1-lap.sysgo.cz> (raw)
In-Reply-To: <YqyKYu76ofyqZk7h@redhat.com>
I fixed the formatting and added the test.
The test has first element 32bit so that it should work on both 32 and
64bit architectures, even without the aligned attribute.
If there is some better way how to write the test properly formatted
(i.e. not on a single line), please let me know.
-- >8 --
Subject: [PATCH] c: Extend the -Wpadded message with actual padding size
When the compiler warns about padding struct to alignment boundary, it
now also informs the user about the size of the alignment that needs to
be added to get rid of the warning.
This removes the need of using pahole or similar tools, or manually
determining the padding size.
Tested on x86_64-pc-linux-gnu.
gcc/ChangeLog:
* stor-layout.cc (finalize_record_size): Extend warning message.
gcc/testsuite/ChangeLog:
* c-c++-common/Wpadded.c: New test.
Signed-off-by: Vit Kabele <vit.kabele@sysgo.com>
---
gcc/stor-layout.cc | 7 ++++++-
gcc/testsuite/c-c++-common/Wpadded.c | 10 ++++++++++
2 files changed, 16 insertions(+), 1 deletion(-)
create mode 100644 gcc/testsuite/c-c++-common/Wpadded.c
diff --git a/gcc/stor-layout.cc b/gcc/stor-layout.cc
index 765f22f68b9..88923c4136b 100644
--- a/gcc/stor-layout.cc
+++ b/gcc/stor-layout.cc
@@ -1781,7 +1781,12 @@ finalize_record_size (record_layout_info rli)
&& simple_cst_equal (unpadded_size, TYPE_SIZE (rli->t)) == 0
&& input_location != BUILTINS_LOCATION
&& !TYPE_ARTIFICIAL (rli->t))
- warning (OPT_Wpadded, "padding struct size to alignment boundary");
+ {
+ tree pad_size
+ = size_binop (MINUS_EXPR, TYPE_SIZE_UNIT (rli->t), unpadded_size_unit);
+ warning (OPT_Wpadded,
+ "padding struct size to alignment boundary with %E bytes", pad_size);
+ }
if (warn_packed && TREE_CODE (rli->t) == RECORD_TYPE
&& TYPE_PACKED (rli->t) && ! rli->packed_maybe_necessary
diff --git a/gcc/testsuite/c-c++-common/Wpadded.c b/gcc/testsuite/c-c++-common/Wpadded.c
new file mode 100644
index 00000000000..e8f1044a36b
--- /dev/null
+++ b/gcc/testsuite/c-c++-common/Wpadded.c
@@ -0,0 +1,10 @@
+/* { dg-do compile } */
+/* { dg-options "-Wpadded" } */
+
+/*
+ * The struct is on single line, because C++ compiler emits the -Wpadded
+ * warning at the first line of the struct, while the C compiler at the last
+ * line of the struct definition. This way the test passes on both
+ */
+struct S { __UINT32_TYPE__ i; char c; }; /* { dg-warning "padding struct size to alignment boundary with 3 bytes" } */
+
--
2.30.2
next prev parent reply other threads:[~2022-06-20 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 19:37 Vit Kabele
2022-06-17 12:56 ` Eric Gallager
2022-06-17 14:06 ` Marek Polacek
2022-06-20 13:50 ` Vit Kabele [this message]
2022-06-20 23:05 ` Andrew Pinski
2022-06-22 8:34 ` Vit Kabele
2022-06-22 8:47 ` Andrew Pinski
2022-06-22 11:50 ` [PATCH v2] " Vit Kabele
2022-06-27 8:04 ` [PATCH v3] " Vit Kabele
2022-07-09 17:07 ` Jeff Law
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=YrB7EQFuCgSXHSEz@czspare1-lap.sysgo.cz \
--to=vit.kabele@sysgo.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.com \
--cc=vit@kabele.me \
/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).