Re: [PATCH] PR fortran/78500 -- Yet another NULL pointer dereference

2016-11-24 Thread Janus Weil
Hi Steve, >> Just my usual request for a meaningful test-case name: This one could >> be class_result_4.f90. (I don't want to be pedantic about this, but in >> a growing testsuite of 4000+ files, I really think it makes sense to >> have meaningful names. It does have various advantages and, to be

Re: [PATCH] PR fortran/78500 -- Yet another NULL pointer dereference

2016-11-24 Thread Steve Kargl
On Thu, Nov 24, 2016 at 11:56:02AM +0100, Janus Weil wrote: > Hi Steve, > > > Regression tested on x86_64-*-freebsd. OK to commit? > > the patch is certainly ok. > > Just my usual request for a meaningful test-case name: This one could > be class_result_4.f90. (I don't want to be pedantic about

Re: [PATCH] PR fortran/78500 -- Yet another NULL pointer dereference

2016-11-24 Thread Andre Vehreschild
On Thu, 24 Nov 2016 11:56:02 +0100 Janus Weil wrote: > Hi Steve, > > > Regression tested on x86_64-*-freebsd. OK to commit? > > the patch is certainly ok. > > Just my usual request for a meaningful test-case name: This one could > be class_result_4.f90. (I don't want to be pedantic about

Re: [PATCH] PR fortran/78500 -- Yet another NULL pointer dereference

2016-11-24 Thread Janus Weil
Hi Steve, > Regression tested on x86_64-*-freebsd. OK to commit? the patch is certainly ok. Just my usual request for a meaningful test-case name: This one could be class_result_4.f90. (I don't want to be pedantic about this, but in a growing testsuite of 4000+ files, I really think it makes se

[PATCH] PR fortran/78500 -- Yet another NULL pointer dereference

2016-11-23 Thread Steve Kargl
Regression tested on x86_64-*-freebsd. OK to commit? 2016-11-23 Steven G. Kargl PR fortran/78500 * expr.c (gfc_check_vardef_contextm): YANPD * interface.c (matching_typebound_op): Ditto. 2016-11-23 Steven G. Kargl PR fortran/78500 * gfortran.dg/pr7