subject:"\[Bug tree\-optimization\/83438\] \[8 Regression\] 435.gromacs miscompares"

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2018-01-15 Thread rguenth at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 Richard Biener changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2018-01-08 Thread law at redhat dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P1

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-29 Thread marxin at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #10 from Martin Liška --- > But there is something really wonky about this benchmark. There are times > when I fully expect it to pass and it fails and vice-versa. I'm really > starting to wonder if there's an uninit read in there o

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-21 Thread law at redhat dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #9 from Jeffrey A. Law --- My bisections keep landing on: commit bb173647d8221f86812f4e98942960b894e9e972 (HEAD, refs/bisect/bad) Author: hubicka Date: Thu Nov 23 15:56:28 2017 + * ipa-fnsummary.c (record_modified_

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-19 Thread law at redhat dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #8 from Jeffrey A. Law --- Doesn't look to be the same correctness issue I'm tracking right now as I get a mis-compare with and without those changes. Sigh.

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-19 Thread law at redhat dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #7 from Jeffrey A. Law --- It could well be the same problem. The fix for the codegen bug I'm tracking affects relax_sh.c from 435.gromacs. I'm still investigating.

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-19 Thread rguenther at suse dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #6 from rguenther at suse dot de --- On Tue, 19 Dec 2017, law at redhat dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 > > --- Comment #5 from Jeffrey A. Law --- > Richi, > > I've got a code correctness issue

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-19 Thread law at redhat dot com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #5 from Jeffrey A. Law --- Richi, I've got a code correctness issue I'm looking at with those changes. If you could pass along the .dom2 and .dom3 dumps for the 435.gromacs benchmark I could probably scan them for the issue without

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-19 Thread marxin at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org --- Comment #4

[Bug tree-optimization/83438] [8 Regression] 435.gromacs miscompares

2017-12-18 Thread rguenther at suse dot de

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 --- Comment #3 from rguenther at suse dot de --- On December 18, 2017 7:31:45 PM GMT+01:00, law at redhat dot com wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83438 > >Jeffrey A. Law changed: > > What|Removed