GCC 13.3 Released
The GNU Compiler Collection version 13.3 has been released. GCC 13.3 is a bug-fix release from the GCC 13 branch containing important fixes for regressions and serious bugs in GCC 13.2 with more than 173 bugs fixed since the previous release. This release is available from the FTP servers listed here: https://sourceware.org/pub/gcc/releases/gcc-13.3.0/ https://gcc.gnu.org/mirrors.html Please do not contact me directly regarding questions or comments about this release. Instead, use the resources available from http://gcc.gnu.org. As always, a vast number of people contributed to this GCC release -- far too many to thank them individually!
Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
On 5/21/24 12:05 AM, Richard Biener via Gcc wrote: On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer 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
Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
> On May 21, 2024, at 9:57 AM, Jeff Law wrote: > > > > On 5/21/24 12:05 AM, Richard Biener via Gcc wrote: >> On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer 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? paul
Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
On 5/21/24 8:02 AM, Paul Koning wrote: On May 21, 2024, at 9:57 AM, Jeff Law wrote: On 5/21/24 12:05 AM, Richard Biener via Gcc wrote: On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer 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. jeff
Re: [committed] PATCH for Re: Stepping down as maintainer for ARC and Epiphany
On Tue, May 21, 2024 at 6:21 PM Jeff Law wrote: > > > > On 5/21/24 8:02 AM, Paul Koning wrote: > > > > > >> On May 21, 2024, at 9:57 AM, Jeff Law wrote: > >> > >> > >> > >> On 5/21/24 12:05 AM, Richard Biener via Gcc wrote: > >>> On Mon, May 20, 2024 at 4:45 PM Gerald Pfeifer 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 >
