From: Richard Biener <richard.guenther@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Paul Koning <paulkoning@comcast.net>,
Gerald Pfeifer <gerald@pfeifer.com>,
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 18:43:23 +0200 [thread overview]
Message-ID: <CAFiYyc0yuzxjp9CWPNKvM18ipJkkSDVRUVNragyS211freHeGw@mail.gmail.com> (raw)
In-Reply-To: <12d4646e-6af3-4c2d-ade1-2ec06cf08551@gmail.com>
On Tue, May 21, 2024 at 6:21 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 5/21/24 8:02 AM, Paul Koning wrote:
> >
> >
> >> On May 21, 2024, at 9:57 AM, Jeff Law <jeffreyalaw@gmail.com> wrote:
> >>
> >>
> >>
> >> 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.
> >
> > Does LRA make that issue go away, or does it not help?
> LRA didn't trivially work on epiphany. I didn't care enough about the
> port to try and make it LRA compatible.
In that case LRA will make the issue go away (the port, that is ...).
Richard.
>
> jeff
>
prev parent reply other threads:[~2024-05-21 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1688582633587.6.46186@webmail-backend-production-7b8b7bc877-jfhdl>
2024-05-20 14:44 ` Gerald Pfeifer
2024-05-21 6:05 ` Richard Biener
2024-05-21 13:57 ` Jeff Law
2024-05-21 14:02 ` Paul Koning
2024-05-21 16:21 ` Jeff Law
2024-05-21 16:43 ` Richard Biener [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=CAFiYyc0yuzxjp9CWPNKvM18ipJkkSDVRUVNragyS211freHeGw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=gnu@amylaar.uk \
--cc=jeffreyalaw@gmail.com \
--cc=paulkoning@comcast.net \
/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).