public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [PATCH] Include safe-ctype.h after C++ standard headers, to avoid over-poisoning
Date: Wed, 3 Apr 2024 10:01:47 +0100	[thread overview]
Message-ID: <006CAECF-937D-486E-BBCF-DFC5210C6302@sandoe.co.uk> (raw)
In-Reply-To: <89EB803D-902E-4E19-BDAF-6B697065443F@gmail.com>

Hi Richard,

> On 7 Mar 2024, at 13:40, FX Coudert <fxcoudert@gmail.com> wrote:
> 
>> I think it's an obvious change ...
> 
> Thanks, pushed.
> 
> Dimitry, I suggest you post the second patch for review.

Given that the two patches here (for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632) were considered obvious - and are needed on release branches.

OK for backporting?

(Gerald has volunteered to do the earlier ones, I have already made/tested the gcc-13 case)

thanks
Iain


  reply	other threads:[~2024-04-03  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 13:42 FX Coudert
2024-03-06 13:54 ` Sam James
2024-03-06 14:35   ` Iain Sandoe
2024-03-06 14:57     ` FX Coudert
2024-03-06 23:02       ` Dimitry Andric
2024-03-07  7:11         ` Iain Sandoe
2024-03-07  9:51           ` Richard Biener
2024-03-07 13:40             ` FX Coudert
2024-04-03  9:01               ` Iain Sandoe [this message]
2024-04-03  9:38                 ` Richard Biener
  -- strict thread matches above, loose matches on Subject: below --
2023-09-28 16:37 Dimitry Andric
2024-01-30 16:19 ` Jonathan Wakely

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=006CAECF-937D-486E-BBCF-DFC5210C6302@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=rguenther@suse.de \
    /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).