https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #9 from CVS Commits ---
The master branch has been updated by Aldy Hernandez :
https://gcc.gnu.org/g:01d7d459e433196b1faa4ee025a314266887fc59
commit r13-3336-g01d7d459e433196b1faa4ee025a314266887fc59
Author: Aldy Hernandez
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #8 from Martin Liška ---
(In reply to Arseny Solokha from comment #7)
> I believe it won't hurt to add a testcase to the test suite.
Sure, Aldy can you please do that?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #7 from Arseny Solokha ---
I believe it won't hurt to add a testcase to the test suite.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #5 from Arseny Solokha ---
I cannot reproduce this ICE w/ the current gcc 13.0.0 20221016 snapshot
(g:6366e3e8847af98d4728d55951534769d034d02a).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #4 from Andrew Macleod ---
Well, thats not really the problem here. We are casting
[irange] gimple_code [2, 2]
to a gimple_code, and getting:
[irange] gimple_code VARYING
Couple of issues.. one, we shouldnt bother casting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
Aldy Hernandez changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
--- Comment #2 from Andrew Macleod ---
Lets see try to remember
it can be ambiguous. The inversion of undefined is not necessarily expected
to be varying in all circumstances.. Likewise, inverting varying is still
varying in some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105820
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |13.0
CC|
