public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Lewis Hyatt <lhyatt@gmail.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c: Fix location for _Pragma tokens [PR97498]
Date: Sun, 31 Jul 2022 09:24:06 -0600	[thread overview]
Message-ID: <19698f34-543c-d436-33bf-b18153f7ad7e@gmail.com> (raw)
In-Reply-To: <CAA_5UQ6V0Pphvj9DZsx5SvaQOfW3UBW4U+mJ8uKw8vJPnkDC4w@mail.gmail.com>



On 7/31/2022 6:44 AM, Lewis Hyatt wrote:
> On Sat, Jul 30, 2022 at 10:43 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>>> There was a request to backport this
>>> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97498#c7) since it is
>>> relevant to this one:
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106267. Is that OK as
>>> well for any of the current release branches please? It will work fine
>>> as far back as 10. Thanks...
>> Generally we try to focus mostly on codegen issues and regressions on
>> the release branches, but it's not a strict rule.  Given this has been
>> on the trunk for nearly a couple weeks without issues, feel free to go
>> ahead and backport per Martin's request.
>>
>> jeff
> Thank you, I'll do that. One question, does a backport need to be an
> exact cherry-pick, or is it OK if I need to tweak a few things as
> well? I wasn't sure if I need to re-post the patch here in that case.
> The patch itself applies to gcc 12 branch fine, however I think I need
> a couple small changes to the testsuite parts. Thanks...
I personally prefer cherry-pick when we can, but as you note, sometimes 
minor twiddling is necessary, particularly as you go to older and older 
branches.  If you need to make minor changes, go ahead.  Consider the 
patch pre-approved with any minor changes you need to make to work with 
the branch and just post the patch with a note that it was installed as 
pre-approved.

Jeff

      reply	other threads:[~2022-07-31 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 20:52 Lewis Hyatt
2022-07-10  3:58 ` Jeff Law
2022-07-10 20:51   ` Lewis Hyatt
2022-07-11  9:27     ` Enhance '_Pragma' diagnostics verification in OMP C/C++ test cases (was: [PATCH] c: Fix location for _Pragma tokens [PR97498]) Thomas Schwinge
2022-07-12  6:33       ` XFAIL 'offloading_enabled' diagnostics issue in 'libgomp.oacc-c-c++-common/reduction-5.c' [PR101551] (was: Enhance '_Pragma' diagnostics verification in OMP C/C++ test cases) Thomas Schwinge
2022-07-12 11:50         ` Lewis Hyatt
2022-07-12 13:10           ` Tobias Burnus
2022-07-13 22:30             ` Lewis Hyatt
2022-07-17 15:24   ` [PATCH] c: Fix location for _Pragma tokens [PR97498] Lewis Hyatt
2022-07-31  2:43     ` Jeff Law
2022-07-31 12:44       ` Lewis Hyatt
2022-07-31 15:24         ` Jeff Law [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=19698f34-543c-d436-33bf-b18153f7ad7e@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lhyatt@gmail.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).