From: Joseph Myers <joseph@codesourcery.com>
To: Martin Uecker <uecker@tugraz.at>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [C PATCH] Detect all variably modified types [PR108375]
Date: Fri, 17 Feb 2023 22:22:28 +0000 [thread overview]
Message-ID: <5311a213-e3b0-daaa-63bf-a7a23a98c3ec@codesourcery.com> (raw)
In-Reply-To: <90d59cd87874bf1c281f1c1ff8d7ab3074434ce2.camel@tugraz.at>
On Fri, 17 Feb 2023, Martin Uecker via Gcc-patches wrote:
> Here is a patch for PR108375.
This patch is OK.
> and another C FE patch for PR105660:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-February/611817.html
This one is also OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2023-02-17 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 18:17 Martin Uecker
2023-02-17 22:22 ` Joseph Myers [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=5311a213-e3b0-daaa-63bf-a7a23a98c3ec@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=uecker@tugraz.at \
/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).