https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63529
--- Comment #10 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Sat, Dec 06, 2014 at 04:38:53PM +0000, dominiq at lps dot ens.fr wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63529 > > --- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > > Not sure what correct etiquette is for checking on bug status, but this has > > been sitting for close to two months now, so I thought I would poke my head > > in again. > > Nasty answer: what did you do to fix it? > > I RTFM and saw at > https://gcc.gnu.org/onlinedocs/gfortran/Cray-pointers.html#Cray-pointers That's a tad bit harsh. I don't recall Russell reporting previous bugs/issues. Don't want to scare off a potential contributor. :) Russell, there is no "correct etiquette" when inferring about the status of a bug. Unfortunately, the reality of the situation is that there are too few gfortran developers and too many issues. That is, there is a man power problem. A gfortran developer typically fixes bugs that effect his own ability to use gfortran or, well, bugs that he knows how to fix. The individual who implemented the Cray pointer feature (and the person with the most intimate knowledge of how it works) hasn't contributed to gfortran in a long time, which is understandable in that the priorities of volunteers do change. Dominique's advise of not mixing vendor extensions with newer Fortran features (i.e., cray pointers and modules) is well intended. I know this above isn't what you want to read, but unfortunately, it is the reality of the situation.
