Related articles |
---|
Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at (2023-10-13) |
Re: Interpreters and caller-saved registers tkoenig@netcologne.de (Thomas Koenig) (2023-10-15) |
Re: Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at (2023-10-19) |
Re: Interpreters and caller-saved registers tkoenig@netcologne.de (Thomas Koenig) (2023-10-22) |
Re: Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at (2023-10-24) |
Re: bug fixes, Interpreters and caller-saved registers 864-117-4973@kylheku.com (Kaz Kylheku) (2023-10-25) |
From: | Kaz Kylheku <864-117-4973@kylheku.com> |
Newsgroups: | comp.compilers |
Date: | Wed, 25 Oct 2023 17:19:17 -0000 |
Organization: | Compilers Central |
References: | 23-10-001 23-10-002 23-10-003 23-10-004 23-10-005 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="59455"; mail-complaints-to="abuse@iecc.com" |
Keywords: | GCC, errors |
Posted-Date: | 26 Oct 2023 07:51:26 EDT |
On 2023-10-24, anton@mips.complang.tuwien.ac.at <anton@mips.complang.tuwien.ac.at> wrote:
> In my experience with gcc maintainers, when I put in that effort, it
> is wasted, because
I sent a patch to the GCC patch mailing list in April 2022. A patch with
documentation updates and test cases. Pinged a number of times (most recently,
sometime this summer, I think). No reply, affirmative or negative.
Engaging GCC isn't the best way to spend one's time.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
NOTE: If you use Google Groups, I don't see you, unless you're whitelisted.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.