Re: scan-*-dump-times across multiple functions considered harmful

2025-07-07 Thread David Malcolm via Gcc
On Thu, 2025-07-03 at 10:12 +0100, Joern Wolfgang Rennecke wrote: > > On 02/07/2025 18:59, David Malcolm wrote: >   ... > > Brainstorming some ideas on other possible approaches on making our > > tests less brittle; for context I did some investigation back in > > 2018 > > about implementing "op

Re: scan-*-dump-times across multiple functions considered harmful

2025-07-03 Thread Joern Wolfgang Rennecke
On 02/07/2025 18:59, David Malcolm wrote: ... Brainstorming some ideas on other possible approaches on making our tests less brittle; for context I did some investigation back in 2018 about implementing "optimizations remarks" like clang does: diagnostics about optimization decisions, so you

Re: scan-*-dump-times across multiple functions considered harmful

2025-07-02 Thread David Malcolm via Gcc
On Tue, 2025-07-01 at 23:04 +0100, Joern Wolfgang Rennecke wrote: > Quite often I see a test quickly written to test some new feature > (bug > fix, extension or optimization) that has a couple of functions to > cover > various aspects of the feature, checked all together with a single > scan-tre