[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-11-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |13.0

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-11-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Aldy Hernandez changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-11-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #10 from CVS Commits --- The master branch has been updated by Aldy Hernandez : https://gcc.gnu.org/g:822a0823c012b912f0108a4da257cd97cbcdb7a3 commit r13-4125-g822a0823c012b912f0108a4da257cd97cbcdb7a3 Author: Aldy Hernandez Date:

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-11-08 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Bug 68097 depends on bug 24021, which changed state. Bug 24021 Summary: VRP does not work with floating points https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24021 What|Removed |Added

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-09-20 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #9 from CVS Commits --- The master branch has been updated by Aldy Hernandez : https://gcc.gnu.org/g:10d6109fe183d984a0377a7afe2854a0d794ebeb commit r13-2741-g10d6109fe183d984a0377a7afe2854a0d794ebeb Author: Aldy Hernandez Date:

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-09-19 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #8 from Aldy Hernandez --- (In reply to Richard Biener from comment #7) > Yes, I think fixed in that we can now record info on FP SSA names. There > are other bugs for specific things. > > What's not fixed is that we still recurse

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-09-19 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Richard Biener changed: What|Removed |Added Keywords||compile-time-hog --- Comment #7 from

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2022-09-17 Thread aldyh at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Aldy Hernandez changed: What|Removed |Added CC||aldyh at gcc dot gnu.org --- Comment

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2016-09-11 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Andrew Pinski changed: What|Removed |Added Depends on||24021 --- Comment #5 from Andrew Pinski

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2015-10-27 Thread rsandifo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #4 from rsandifo at gcc dot gnu.org --- Author: rsandifo Date: Tue Oct 27 11:52:54 2015 New Revision: 229423 URL: https://gcc.gnu.org/viewcvs?rev=229423=gcc=rev Log: Move signbit folds to match.pd Tested on x86_64-linux-gnu,

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2015-10-26 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 Richard Biener changed: What|Removed |Added Keywords||missed-optimization

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2015-10-26 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #2 from Marc Glisse --- If we are generalizing VRP, how about vectors? A single interval per vector would be enough for most of the benefit.

[Bug tree-optimization/68097] We should track ranges for floating-point values too

2015-10-26 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097 --- Comment #1 from Andrew Pinski --- I think I might have filed about this before.