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? -Andi
