From: Eric Gallager <egall@gwmail.gwu.edu>
To: Jonas Rahlf <jonas.rahlf@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: New/improved warning option for padding bytes
Date: Sun, 21 Aug 2022 19:12:49 -0400 [thread overview]
Message-ID: <CAMfHzOuh=wGstsK4u_xxLTGHkDc0BjKmbDY8s=Y+FtwJeAJawg@mail.gmail.com> (raw)
In-Reply-To: <CAHJ7zASLFodZHOCX0YY2Cq_dKrOHaTGZcTeSCXGFYVvRKXNe2A@mail.gmail.com>
On Fri, Aug 19, 2022 at 6:13 AM Jonas Rahlf via Gcc <gcc@gcc.gnu.org> wrote:
>
> As a firmware developer I would appreciate a warning option about padding
> bytes, but only for such cases where you can reduce the number of padding
> bytes by rearranging the fields.
>
> The current -Wpadded warns about all padding bytes, which is annoying.
>
> The concept sounds simple: you rearrange all fields from large to small and
> check if the size changed.
>
> The goal is to more easily optimize RAM/flash in space constrained systems.
>
> Jonas
That sounds like bug 52981: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52981
prev parent reply other threads:[~2022-08-21 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 10:12 Jonas Rahlf
2022-08-21 23:12 ` Eric Gallager [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='CAMfHzOuh=wGstsK4u_xxLTGHkDc0BjKmbDY8s=Y+FtwJeAJawg@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=gcc@gcc.gnu.org \
--cc=jonas.rahlf@gmail.com \
/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).