From: Alexandre Oliva <oliva@adacore.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Jeff Law <jlaw@ventanamicro.com>,
"H . J . Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH 1/2] c-family: -Waddress-of-packed-member and casts
Date: Fri, 08 Dec 2023 23:22:26 -0300 [thread overview]
Message-ID: <or34wcazdp.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <20231122211235.3503229-1-jason@redhat.com> (Jason Merrill's message of "Wed, 22 Nov 2023 16:12:34 -0500")
On Nov 22, 2023, Jason Merrill <jason@redhat.com> wrote:
> Tested x86_64-pc-linux-gnu, OK for trunk?
FYI, Linaro's regression tester let me know that my patch reversal, that
expected this patch to go in instead, caused two "regressions".
https://linaro.atlassian.net/browse/GNU-1067
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
next prev parent reply other threads:[~2023-12-09 2:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 21:12 Jason Merrill
2023-11-22 21:12 ` [PATCH 2/2] c-family: rename warn_for_address_or_pointer_of_packed_member Jason Merrill
2023-12-09 2:22 ` Alexandre Oliva [this message]
2023-12-11 7:28 ` [PATCH 1/2] c-family: -Waddress-of-packed-member and casts Richard Biener
2024-02-07 16:19 ` Torbjorn SVENSSON
2024-02-22 8:51 ` [PING] " Torbjorn SVENSSON
2024-02-28 23:07 ` Jason Merrill
2024-03-09 9:02 ` [PATCH] testsuite: xfail test for arm Torbjörn SVENSSON
2024-03-09 9:23 ` Andrew Pinski
2024-03-11 10:23 ` [PATCH v2] testsuite: xfail test for short_enums Torbjörn SVENSSON
2024-03-12 13:21 ` Jason Merrill
2024-03-13 14:18 ` [comitted] testsuite: target " Torbjörn SVENSSON
2024-03-13 14:22 ` [PATCH v2] testsuite: xfail " Torbjorn SVENSSON
2024-03-15 8:33 ` [committed] testsuite: Added missing } in the dg-bogus comment [PR114343] Torbjörn SVENSSON
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=or34wcazdp.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jason@redhat.com \
--cc=jlaw@ventanamicro.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).