Re: Interpreters and caller-saved registers

From	anton@mips.complang.tuwien.ac.at
Newsgroups	comp.compilers
Subject	Re: Interpreters and caller-saved registers
Date	2023-10-24 17:15 +0000
Organization	Compilers Central
Message-ID	<23-10-005@comp.compilers> (permalink)
References	<23-10-001@comp.compilers> <23-10-002@comp.compilers> <23-10-003@comp.compilers> <23-10-004@comp.compilers>

Show all headers | View raw

Thomas Koenig <tkoenig@netcologne.de> writes:
>anton@mips.complang.tuwien.ac.at <anton@mips.complang.tuwien.ac.at> schrieb:
>> 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.

In my experience with gcc maintainers, when I put in that effort, it
is wasted, because

1) the resulting bug report is resolved as invalid (e.g., PR25285) in
   less time than it took me to create it.  Moreover gcc maintainers
   who knew much less about the performance implications of the bug
   than I did (I had researched the topic for several years at that
   point), yet wrote patronizingly down to me; but that would have
   been forgiven if they had kept their part of the social contract
   and fixed the bug.

2) they confirm the bug and do nothing about it (PR93811).

3) they just do nothing about it (PR 93765).

In the present case, declaring the bug to be INVALID would be easy
given that the program uses features outside standard C, and I expect
that if you make such a bug report, it will be resolved as INVALID.
So why should anyone waste their time on it?  If you think they are
going to fix it, why don't you invest your time in it?

- anton
--
M. Anton Ertl
anton@mips.complang.tuwien.ac.at
http://www.complang.tuwien.ac.at/anton/

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