Re: Interpreters and caller-saved registers

Path	csiph.com!weretis.net!feeder6.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From	Thomas Koenig <tkoenig@netcologne.de>
Newsgroups	comp.compilers
Subject	Re: Interpreters and caller-saved registers
Date	Sun, 22 Oct 2023 18:43:47 -0000
Organization	Compilers Central
Sender	johnl%iecc.com
Approved	comp.compilers@iecc.com
Message-ID	<23-10-004@comp.compilers> (permalink)
References	<23-10-001@comp.compilers> <23-10-002@comp.compilers> <23-10-003@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="9924"; mail-complaints-to="abuse@iecc.com"
Keywords	interpreter, optimize
Posted-Date	23 Oct 2023 17:32:24 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:3531

Show key headers only | View raw

anton@mips.complang.tuwien.ac.at <anton@mips.complang.tuwien.ac.at> schrieb:
> Thomas Koenig <tkoenig@netcologne.de> writes:
>>It is well known that compilers in general and gcc specfically often
>>generate superflous register moves
> ...
>>However, if this got worse between releases, this is a regression.
>>Those get higher priority for fixing.  So, if it is reasonable
>>to generate a reduced test case (for which cvise, for example,
>>is an excellent tool) so filing a bug report would be a good thing.
>
> If you want to file such a bug report, I can give you the commit of
> Gforth before we added all the workarounds, where all the problems
> are visible without ado.

This reply shows an interesting aspect of compiler development that is
often overlooked: The social aspect.

Compiler writers generally want to improve their product, but they
also generally feel that bug submitters (at least those who don't have
a support contract) should also invest a minimum of work if he wants
something fixed, and a general "look at large package xyz, it'll be
obvious" is below that threshold. (This is the reason why gcc, for
example, asks for a complete and self-contained test case in its bug
reports.)

People who complain about bugs, but are not willing to put in that
minimum amount of work, are often ignored.

Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at - 2023-10-13 07:44 +0000
  Re: Interpreters and caller-saved registers Thomas Koenig <tkoenig@netcologne.de> - 2023-10-15 19:52 +0000
    Re: Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at - 2023-10-19 17:14 +0000
      Re: Interpreters and caller-saved registers Thomas Koenig <tkoenig@netcologne.de> - 2023-10-22 18:43 +0000
        Re: Interpreters and caller-saved registers anton@mips.complang.tuwien.ac.at - 2023-10-24 17:15 +0000
          Re: bug fixes, Interpreters and caller-saved registers Kaz Kylheku <864-117-4973@kylheku.com> - 2023-10-25 17:19 +0000

csiph-web