From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Cc: Joern Rennecke <gnu@amylaar.uk>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
Date: Tue, 21 May 2024 07:57:15 -0600 [thread overview]
Message-ID: <87606d95-fdc6-4d2c-849a-6dbee60dac5f@gmail.com> (raw)
In-Reply-To: <CAFiYyc04g13gwAUP0XHXa=HONcPMNs_RDLSecTEfJoybyFTB6Q@mail.gmail.com>
On 5/21/24 12:05 AM, Richard Biener via Gcc wrote:
> On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>>
>> On Wed, 5 Jul 2023, Joern Rennecke wrote:
>>> I haven't worked with these targets in years and can't really do
>>> sensible maintenance or reviews of patches for them. I am currently
>>> working on optimizations for other ports like RISC-V.
>>
>> I noticed MAINTAINERS was not updated, so pushed the patch below.
>
> That leaves the epiphany port unmaintained. Should we automatically add such
> ports to the list of obsoleted ports?
Given that epiphany has randomly failed tests for the last 3+ years due
to bugs in its patterns, yes, it really needs to be deprecated.
I tried to fix the worst of the offenders in epiphany.md a few years
back and gave up. Essentially seemingly innocent changes in the RTL
will cause reload to occasionally not see a path to get constraints
satisfied. So a test which passes today, will flip to failing tomorrow
while some other test of tests will go the other way.
jeff
next prev parent reply other threads:[~2024-05-21 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1688582633587.6.46186@webmail-backend-production-7b8b7bc877-jfhdl>
2023-07-06 6:17 ` Richard Biener
2023-07-07 0:37 ` Jeff Law
2024-05-20 14:44 ` [committed] PATCH for " Gerald Pfeifer
2024-05-21 6:05 ` Richard Biener
2024-05-21 13:57 ` Jeff Law [this message]
2024-05-21 14:02 ` Paul Koning
2024-05-21 16:21 ` Jeff Law
2024-05-21 16:43 ` Richard Biener
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=87606d95-fdc6-4d2c-849a-6dbee60dac5f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=gnu@amylaar.uk \
--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).