From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v3] c: Extend the -Wpadded message with actual padding size
Date: Sat, 9 Jul 2022 11:07:42 -0600 [thread overview]
Message-ID: <75044605-38ee-032c-ea7e-664c39ad82c8@gmail.com> (raw)
In-Reply-To: <YrlkhETL4ZhFCU6X@czspare1-lap.sysgo.cz>
On 6/27/2022 2:04 AM, Vit Kabele wrote:
> gcc/ChangeLog:
>
> * stor-layout.cc (finalize_record_size): Extend warning message.
>
> gcc/testsuite/ChangeLog:
>
> * c-c++-common/Wpadded.c: New test.
Thanks. I've pushed this to the trunk.
jeff
prev parent reply other threads:[~2022-07-09 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 19:37 [PATCH] " Vit Kabele
2022-06-17 12:56 ` Eric Gallager
2022-06-17 14:06 ` Marek Polacek
2022-06-20 13:50 ` Vit Kabele
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 [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=75044605-38ee-032c-ea7e-664c39ad82c8@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).