gcc-13-20220821 is now available

2022-08-21 Thread GCC Administrator via Gcc
Snapshot gcc-13-20220821 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/13-20220821/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch master 
revision d6a39c25c05c6ed5df8ce49eda719d17e40e29bb

You'll find:

 gcc-13-20220821.tar.xz   Complete GCC

  SHA256=527b22c4a7d6d6314805a6685d9f521cf8c638dc3618f938722dcfea711ae1d8
  SHA1=acc0dd9aaa38c1bffa882a377bde0461d89cdac5

Diffs from 13-20220814 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-13
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.


Re: New/improved warning option for padding bytes

2022-08-21 Thread Eric Gallager via Gcc
On Fri, Aug 19, 2022 at 6:13 AM Jonas Rahlf via Gcc  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