* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
@ 2023-04-22 12:54 ` sjames at gcc dot gnu.org
2023-04-22 13:21 ` dcb314 at hotmail dot com
` (10 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: sjames at gcc dot gnu.org @ 2023-04-22 12:54 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at gcc dot gnu.org,
| |amacleod at redhat dot com,
| |sjames at gcc dot gnu.org
--- Comment #1 from Sam James <sjames at gcc dot gnu.org> ---
Could you try bisect to speed up things?
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
2023-04-22 12:54 ` [Bug c/109593] " sjames at gcc dot gnu.org
@ 2023-04-22 13:21 ` dcb314 at hotmail dot com
2023-04-22 17:14 ` dcb314 at hotmail dot com
` (9 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dcb314 at hotmail dot com @ 2023-04-22 13:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
(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. Attempting a bisect.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
2023-04-22 12:54 ` [Bug c/109593] " sjames at gcc dot gnu.org
2023-04-22 13:21 ` dcb314 at hotmail dot com
@ 2023-04-22 17:14 ` dcb314 at hotmail dot com
2023-04-22 17:53 ` dcb314 at hotmail dot com
` (8 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dcb314 at hotmail dot com @ 2023-04-22 17:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
(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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (2 preceding siblings ...)
2023-04-22 17:14 ` dcb314 at hotmail dot com
@ 2023-04-22 17:53 ` dcb314 at hotmail dot com
2023-04-22 19:04 ` aldyh at gcc dot gnu.org
` (7 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dcb314 at hotmail dot com @ 2023-04-22 17:53 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #4 from David Binderman <dcb314 at hotmail dot com> ---
(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.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (3 preceding siblings ...)
2023-04-22 17:53 ` dcb314 at hotmail dot com
@ 2023-04-22 19:04 ` aldyh at gcc dot gnu.org
2023-04-22 19:14 ` dcb314 at hotmail dot com
` (6 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: aldyh at gcc dot gnu.org @ 2023-04-22 19:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Huh. I'm gonna guess:
commit 10e481b154c5fc63e6ce4b449ce86cecb87a6015
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Thu Jan 26 04:46:54 2023 +0100
Return true from operator== for two identical ranges containing NAN.
- if (known_isnan () || src.known_isnan ())
- return false;
-
return (real_identical (&m_min, &src.m_min)
&& real_identical (&m_max, &src.m_max)
&& m_pos_nan == src.m_pos_nan
If either operand is a NAN, m_min or m_max have garbage. Can you verify that's
the commit? Either way, I can take a look at it on Monday.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug c/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (4 preceding siblings ...)
2023-04-22 19:04 ` aldyh at gcc dot gnu.org
@ 2023-04-22 19:14 ` dcb314 at hotmail dot com
2023-04-22 19:36 ` [Bug tree-optimization/109593] " pinskia at gcc dot gnu.org
` (5 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: dcb314 at hotmail dot com @ 2023-04-22 19:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Aldy Hernandez from comment #5)
> Can you verify that's the commit?
git bisect says:
10e481b154c5fc63e6ce4b449ce86cecb87a6015 is the first bad commit.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (5 preceding siblings ...)
2023-04-22 19:14 ` dcb314 at hotmail dot com
@ 2023-04-22 19:36 ` pinskia at gcc dot gnu.org
2023-04-22 19:36 ` [Bug tree-optimization/109593] [14 Regression] " pinskia at gcc dot gnu.org
` (4 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-22 19:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Component|c |tree-optimization
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #6)
> (In reply to Aldy Hernandez from comment #5)
> > Can you verify that's the commit?
>
> git bisect says:
>
> 10e481b154c5fc63e6ce4b449ce86cecb87a6015 is the first bad commit.
r14-32-g10e481b154c5fc63
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] [14 Regression] valgrind error doing build of latest gcc trunk
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (6 preceding siblings ...)
2023-04-22 19:36 ` [Bug tree-optimization/109593] " pinskia at gcc dot gnu.org
@ 2023-04-22 19:36 ` pinskia at gcc dot gnu.org
2023-04-23 6:07 ` [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63 aldyh at gcc dot gnu.org
` (3 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-04-22 19:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
Version|13.0 |14.0
Summary|valgrind error doing build |[14 Regression] valgrind
|of latest gcc trunk |error doing build of latest
| |gcc trunk
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (7 preceding siblings ...)
2023-04-22 19:36 ` [Bug tree-optimization/109593] [14 Regression] " pinskia at gcc dot gnu.org
@ 2023-04-23 6:07 ` aldyh at gcc dot gnu.org
2023-04-23 8:02 ` dcb314 at hotmail dot com
` (2 subsequent siblings)
11 siblings, 0 replies; 13+ messages in thread
From: aldyh at gcc dot gnu.org @ 2023-04-23 6:07 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #8 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Created attachment 54908
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54908&action=edit
untested patch
Patch in testing. Does this fix the problem on the reporter's side?
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (8 preceding siblings ...)
2023-04-23 6:07 ` [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63 aldyh at gcc dot gnu.org
@ 2023-04-23 8:02 ` dcb314 at hotmail dot com
2023-04-23 9:04 ` cvs-commit at gcc dot gnu.org
2023-04-23 9:05 ` aldyh at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: dcb314 at hotmail dot com @ 2023-04-23 8:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #9 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to Aldy Hernandez from comment #8)
> Does this fix the problem on the reporter's side?
Looks good to me.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (9 preceding siblings ...)
2023-04-23 8:02 ` dcb314 at hotmail dot com
@ 2023-04-23 9:04 ` cvs-commit at gcc dot gnu.org
2023-04-23 9:05 ` aldyh at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-04-23 9:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:
https://gcc.gnu.org/g:5830953a446959c5d8d9b569ffcd3e3bb16a06dc
commit r14-174-g5830953a446959c5d8d9b569ffcd3e3bb16a06dc
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Sun Apr 23 08:04:55 2023 +0200
Handle NANs in frange::operator== [PR109593]
This patch...
commit 10e481b154c5fc63e6ce4b449ce86cecb87a6015
Return true from operator== for two identical ranges containing
NAN.
removed the check for NANs, which caused us to read from m_min and
m_max which are undefined for NANs.
gcc/ChangeLog:
PR tree-optimization/109593
* value-range.cc (frange::operator==): Handle NANs.
^ permalink raw reply [flat|nested] 13+ messages in thread
* [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63
2023-04-22 11:47 [Bug c/109593] New: valgrind error doing build of latest gcc trunk dcb314 at hotmail dot com
` (10 preceding siblings ...)
2023-04-23 9:04 ` cvs-commit at gcc dot gnu.org
@ 2023-04-23 9:05 ` aldyh at gcc dot gnu.org
11 siblings, 0 replies; 13+ messages in thread
From: aldyh at gcc dot gnu.org @ 2023-04-23 9:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
fixed
^ permalink raw reply [flat|nested] 13+ messages in thread