From: Xi Ruoyao <xry111@xry111.site>
To: "Martin Li�0�8ka" <mliska@suse.cz>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Cc: "Jakub Jelinek" <jakub@redhat.com>,
"Arsen Arsenovi�0�4" <arsen@aarsen.me>,
"Richard Biener" <richard.guenther@gmail.com>
Subject: Re: [PATCH] Backport gcc-12: jobserver FIFO support
Date: Sat, 10 Dec 2022 15:03:13 +0800 [thread overview]
Message-ID: <a7bcae4e11dcb721080a344e70e71244392ed26b.camel@xry111.site> (raw)
In-Reply-To: <8b594fb7-343d-ca34-20c7-e15f6315c884@suse.cz>
On Fri, 2022-12-09 at 11:07 +0100, Martin Liška wrote:
> Hi.
>
> As make 4.4 has been release, it switches to FIFO by default. That makes
> troubles to the latest GCC release, version 12. Right now, we've been using
> the following 4 patches in openSUSE gcc12 package:
>
> 1270ccda70ca09f7d4fe76b5156dca8992bd77a6
> 53e3b2bf16a486c15c20991c6095f7be09012b55
> fed766af32ed6cd371016cc24e931131e19b4eb1
> 3f1c2f89f6b8b8d23a9072f8549b0a2c1de06b03
>
> Would it be fine to backport it to gcc-12 branch? Arsen asked me the today
> as Gentoo people want it as well.
I'd vote a +1, I've applied them to a GCC 12.2 build and used it to
build many packages with -flto=auto. GCC seems communicating with make-
4.4 correctly with these patches.
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-12-10 7:03 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 [this message]
2022-12-11 10:47 ` Richard Biener
2022-12-12 11:39 ` Martin Liška
2022-12-12 11:42 ` Jakub Jelinek
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=a7bcae4e11dcb721080a344e70e71244392ed26b.camel@xry111.site \
--to=xry111@xry111.site \
--cc=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).