From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>,
Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
gofrontend-dev <gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Don't include <linux/fs.h> in sysinfo.c
Date: Thu, 21 Jul 2022 13:52:40 +0200 [thread overview]
Message-ID: <c4ff5b29-0c8c-353d-5270-9a5aecb8bf59@suse.cz> (raw)
In-Reply-To: <CAFiYyc3kbKgqZTqcy_8TkzT2uD+yoqjCyh2OyJ0cZLGdjEX9Bw@mail.gmail.com>
On 7/21/22 12:19, Richard Biener via Gcc-patches wrote:
> On Wed, Jul 13, 2022 at 6:03 PM Ian Lance Taylor via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>>
>> This libgo patch stops including <linux/fs.h> when building
>> gen-sysinfo.go. Removing this doesn't change anything at least with
>> glibc 2.33. The include was added in https://go.dev/cl/6100049 but
>> it's not clear why. This should fix GCC PR 106266. Bootstrapped and
>> ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline.
>
> Btw, active branches are affected the same way - can you please backport?
I've just done that.
Martin
>
>> Ian
next prev parent reply other threads:[~2022-07-21 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 16:02 Ian Lance Taylor
2022-07-21 10:19 ` Richard Biener
2022-07-21 11:52 ` Martin Liška [this message]
2022-07-21 18:54 ` Ian Lance Taylor
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=c4ff5b29-0c8c-353d-5270-9a5aecb8bf59@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@golang.org \
--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).