From: Jeff Law <jeffreyalaw@gmail.com>
To: "Vít Kabele" <vit.kabele@sysgo.com>, gcc-patches@gcc.gnu.org
Cc: vit@kabele.me
Subject: Re: [PATCH v2] Print padding size when aligning struct member
Date: Sat, 11 Mar 2023 08:35:53 -0700 [thread overview]
Message-ID: <06495ef5-7cb5-867f-bf00-588989f0b08c@gmail.com> (raw)
In-Reply-To: <20230224072835.12177-1-vit.kabele@sysgo.com>
On 2/24/23 00:28, Vít Kabele wrote:
> Hello,
>
> I changed the tested pattern to match even on targets with different
> alignment.
So this needs to wait for stage1 development to open -- we're in
regression bugfixing phase only right now. I would expect that to
happen in April/May.
You might consider changing the other similar message you added last
year to finalize_record_size to use the same format as this message for
the sake of consistency.
Jeff
next prev parent reply other threads:[~2023-03-11 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 12:41 [PATCH] " Vít Kabele
2023-02-07 13:08 ` Andreas Schwab
2023-02-07 14:09 ` Vit Kabele
2023-02-24 7:28 ` [PATCH v2] " Vít Kabele
2023-03-11 15:35 ` Jeff Law [this message]
2023-03-28 14:24 ` Vit Kabele
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=06495ef5-7cb5-867f-bf00-588989f0b08c@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vit.kabele@sysgo.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).