On Thu, 2 Jan 2025, Andi Kleen wrote:
Krister Walfridsson via Gcc <gcc@gcc.gnu.org> writes:
But running smtgcc on the test suite is not the best use case for the
tool -- it only detects bugs where the test triggers an unrelated bug
compared to what the test is checking, which should be uncommon. I
therefore plan to start testing by compiling real-world code and doing
some fuzzing. One problem is that this often finds the open bugs
mentioned in the previous section, making it time-consuming to check
if each new issue is a repeat. For example, running yarpgen gives me a
few failure reports per day of PR106883.
I would increase the priority of PR106883 if it blocks so much testing.
But does disabling the slsr pass not help?
Yes, I can disable the slsr pass, or just ignore all the problems detected
in it. But most of the bugs mentioned occur frequently enough that I have
the same problem with them, and there wouldn't be much left of the
compiler to check if I disable/ignore all of the affected passes...
I don't want to overstate the problem -- I'll manage. But it would be
great if a few of these PRs were fixed! :)
/Krister
