From: Xi Ruoyao <xry111@xry111.site>
To: Zopolis0 <creatorsmithmdt@gmail.com>,
Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 16/56] gcc: Re-add TYPE_METHODS.
Date: Sat, 26 Nov 2022 15:48:26 +0800 [thread overview]
Message-ID: <9b5cdf691510b783f42d3de6099c5bbe9b931236.camel@xry111.site> (raw)
In-Reply-To: <CAEYL+X-xBQnq+MkCzRF-r72OrztzagFfHUwF8KXEhExX6JJvRQ@mail.gmail.com>
On Sat, 2022-11-26 at 18:30 +1100, Zopolis0 via Gcc-patches wrote:
> > Re-adding a field to all types is a no-go
>
> To be entirely honest, my current priority is simply to get this
> merged so I can spend less time keeping up with upstream changes
> breaking everything and spend more time actually improving things. The
> additional labour cost for the maintainer who is making the change and
> understands it deeply is much less than what it takes for me to bisect
> the issue, find the commit, understand it and fix the issue.
No. Java was removed to reduce the maintenance burden, you can't just
reintroduce the burden and say "hey, I don't want to pay for the burden
so you please do it".
And we are in stage 3 now so it's not possible to merge 50+ patches
(completely not reviewed in stage 1) until GCC 14 stage 1 opens.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-11-26 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 8:40 Zopolis0
2022-11-25 20:20 ` Richard Biener
2022-11-26 0:16 ` Zopolis0
2022-11-26 1:54 ` Zopolis0
2022-11-26 7:22 ` Richard Biener
2022-11-26 7:30 ` Zopolis0
2022-11-26 7:48 ` Xi Ruoyao [this message]
2022-11-26 8:26 ` Zopolis0
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=9b5cdf691510b783f42d3de6099c5bbe9b931236.camel@xry111.site \
--to=xry111@xry111.site \
--cc=creatorsmithmdt@gmail.com \
--cc=gcc-patches@gcc.gnu.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).