[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-28 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 Paul Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-28 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #23 from Paul Thomas --- Author: pault Date: Sat Oct 28 08:53:19 2017 New Revision: 254196 URL: https://gcc.gnu.org/viewcvs?rev=254196=gcc=rev Log: 2017-10-28 Paul Thomas PR fortran/81758 *

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-28 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #22 from Paul Thomas --- Author: pault Date: Sat Oct 28 08:49:26 2017 New Revision: 254195 URL: https://gcc.gnu.org/viewcvs?rev=254195=gcc=rev Log: 2017-10-28 Paul Thomas PR fortran/81758 *

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-26 Thread liakhdi at ornl dot gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #21 from DIL --- Greatly appreciate!

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-26 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #20 from paul.richard.thomas at gmail dot com --- Hi Dmitry, I will persist with 81758 until I have a satisfactory testcase and then I promise that I will move to 80850. Cheers Paul On 26 October 2017 at 15:20, liakhdi at ornl

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-26 Thread liakhdi at ornl dot gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #19 from DIL --- Hi Paul, Great, thanks a lot! That was pretty quick. Upon a chance, as there is still a momentum :), could you please take a brief look at bug #80850 to see whether it may be related since you mentioned "allocation

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-26 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #18 from Paul Thomas --- Created attachment 42480 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42480=edit A patch that fixes the problem Following your tip, Dimtry, this does the job and regtests OK. Will fix up a testcase

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-23 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #17 from paul.richard.thomas at gmail dot com --- Hi Dmitry, That's great. I'll let you know how I get on when I return. I knew that it had to be a complicated pointer assignment or allocation with source but couldn't deduce it by

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-23 Thread liakhdi at ornl dot gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #16 from DIL --- Hi Paul, Thanks for looking into this issue. I ran the debugger again. The vtab corruption occurs upon the first encounter in function VectorIterElement() in line 720 of gfc_vector.F90. Just to make sure, that line

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-23 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #15 from Paul Thomas --- Hi DIL, On reflection, this is OK and agrees with your diagnosis: > val_p._vptr = (struct __vtype__STAR * {ref-all}) &__vtab__STAR; > val_p._len = 0; > val_p._data = 0B; > cep._vptr = (struct

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-21 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #14 from Paul Thomas --- The chunk of offending code: val_p=>NULL(); cep=>NULL() cep=>this%element(offset,errc) if(errc.eq.GFC_SUCCESS.and.associated(cep)) then val_p=>cep%get_value(errc) is

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-21 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #13 from Paul Thomas --- (In reply to Thomas Koenig from comment #12) > And with r241439, the test fails. > > Andre, any ideas? This is sufficiently similar to PR82312 that I applied the patch for it to 7-branch (which I had to do

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-16 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #12 from Thomas Koenig --- And with r241439, the test fails. Andre, any ideas?

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-16 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #11 from Thomas Koenig --- With r241438, the test passes.

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-16 Thread liakhdi at ornl dot gov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #10 from DIL --- (In reply to Thomas Koenig from comment #9) > I just checked on powerpc64 with a rather current trunk with > > gfc::bank testing status:0 (PASSED): Performance: > 2888199.6889235629 >

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-16 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 --- Comment #9 from Thomas Koenig --- I just checked on powerpc64 with a rather current trunk with gfc::bank testing status:0 (PASSED): Performance: 2888199.6889235629 gfc::vector testing status:0 (PASSED):

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab

2017-10-15 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 Dominique d'Humieres changed: What|Removed |Added Keywords||wrong-code Priority|P3