https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #6 from David Binderman ---
(In reply to Aldy Hernandez from comment #5)
> Can you verify that's the commit?
git bisect says:
10e481b154c5fc63e6ce4b449ce86cecb87a6015 is the first bad commit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #5 from Aldy Hernandez ---
Huh. I'm gonna guess:
commit 10e481b154c5fc63e6ce4b449ce86cecb87a6015
Author: Aldy Hernandez
Date: Thu Jan 26 04:46:54 2023 +0100
Return true from operator== for two identical ranges containing NA
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #4 from David Binderman ---
(In reply to David Binderman from comment #3)
> Git range seems to be e6b050da8a4513ab..cbddd574a78529b9, which is 52
> commits.
Now downto 603fc926fee69ab3..10e481b154c5fc63, which is 13 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #3 from David Binderman ---
(In reply to David Binderman from comment #2)
> That's a range of 416 commits. Attempting a bisect.
Git range seems to be e6b050da8a4513ab..cbddd574a78529b9, which is 52 commits.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #2 from David Binderman ---
(In reply to Sam James from comment #1)
> Could you try bisect to speed up things?
I think my last valgrind build, dated 20230311, with
git hash 5de5e977aa0b653e was ok.
That's a range of 416 commits. At
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Sam James changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org,
