Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Kaz Kylheku <864-117-4973@kylheku.com> Newsgroups: comp.compilers Subject: Re: bug fixes, Interpreters and caller-saved registers Date: Wed, 25 Oct 2023 17:19:17 -0000 Organization: Compilers Central Sender: johnl%iecc.com Approved: comp.compilers@iecc.com Message-ID: <23-10-007@comp.compilers> References: <23-10-001@comp.compilers> <23-10-002@comp.compilers> <23-10-003@comp.compilers> <23-10-004@comp.compilers> <23-10-005@comp.compilers> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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 X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:3534 On 2023-10-24, 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.