From: Yang Yujie <yangyujie@loongson.cn>
To: Florian Weimer <fweimer@redhat.com>
Cc: Yang Yujie <yangyujie@loongson.cn>,
Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, ro@cebitec.uni-bielefeld.de,
mikestump@comcast.net
Subject: Re: [PATCH] testsuite: Adjust for the new permerror -Wincompatible-pointer-types
Date: Fri, 8 Dec 2023 10:00:25 +0800 [thread overview]
Message-ID: <4u7zy3wdsavcpnancvri6pmbzhb6tlcihdrtgpksbw3ocznmgz@igmcgvdvz43w> (raw)
In-Reply-To: <87bkb2s748.fsf@oldenburg.str.redhat.com>
On Thu, Dec 07, 2023 at 10:18:47AM +0100, Florian Weimer wrote:
> * Yang Yujie:
>
> > With this patch, I also noticed a few errors in building unpatched older
> > software like expect-5.45.4, perl-5.28.3 and bash-5.0. Will this also be
> > the case when GCC 14 gets released?
>
> For Fedora, we keep pointers of the changes needed here:
>
> <https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/b/bash.md>
> <https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/e/expect.md>
> <https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/p/perl.md>
>
> (For perl, it looks like another change will be needed.)
>
> This also includes changes that we imported through rebases after we
> started tracking.
>
> We do not have control over the release schedule for those upstream
> projects, and of course there are many project which are more or less
> dormant and have not made a release in many years.
>
> Thanks,
> Florian
Got it. Thanks for the pointers to the fedora patches.
Yujie
prev parent reply other threads:[~2023-12-08 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 2:29 Yang Yujie
2023-12-06 12:12 ` Florian Weimer
2023-12-06 17:45 ` Jeff Law
2023-12-07 1:30 ` Yang Yujie
2023-12-07 1:35 ` Sam James
2023-12-07 1:42 ` Yang Yujie
2023-12-07 9:18 ` Florian Weimer
2023-12-08 2:00 ` Yang Yujie [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=4u7zy3wdsavcpnancvri6pmbzhb6tlcihdrtgpksbw3ocznmgz@igmcgvdvz43w \
--to=yangyujie@loongson.cn \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.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).