From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: "Richard Biener" <richard.guenther@gmail.com>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: [PATCH] Backport gcc-12: jobserver FIFO support
Date: Mon, 12 Dec 2022 12:42:17 +0100 [thread overview]
Message-ID: <Y5cTmeXrQP86Qhbg@tucnak> (raw)
In-Reply-To: <291363f6-970c-031f-0f27-f58a7195435f@suse.cz>
On Mon, Dec 12, 2022 at 12:39:36PM +0100, Martin Liška wrote:
> > I'm fine with backporting the whole
> > series to GCC 12 but I wonder if earlier still maintained versions are also
> > affected (noting that the series also addresses WPA streaming which is
> > not part of the "troubles" here).
>
> Yes, they are also affected.
>
> So ready for all active branches?
Can't you backport instead a minimal fix that will not change other stuff?
Jakub
next prev parent reply other threads:[~2022-12-12 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 10:07 Martin Liška
2022-12-10 7:03 ` Xi Ruoyao
2022-12-11 10:47 ` Richard Biener
2022-12-12 11:39 ` Martin Liška
2022-12-12 11:42 ` Jakub Jelinek [this message]
2022-12-12 12:05 ` Martin Liška
2022-12-22 10:35 ` Martin Liška
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=Y5cTmeXrQP86Qhbg@tucnak \
--to=jakub@redhat.com \
--cc=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.cz \
--cc=richard.guenther@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).