https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63529
--- Comment #7 from russelldub at gmail dot com --- (In reply to Dominique d'Humieres from comment #6) > AFAICT the ICE with "REAL :: ptee1(10)" has been fixed for gfortran 4.9.1 > and above (also for 4.8.4). I can't easily test with either of those, but the ICE doesn't happen for me with a trunk build, so I guess that's OK. > I also think the error for "REAL :: ptee1(*)" is right. Whether or not the assumed size array is allowed is one question. I don't know the answer but I can say that both ifort and pgf95 think it's fine. I can't find a definitive answer in the standards, but as cray-pointers aren't part of the standard, it's probably not the right way to handle that question. The second question is whether the emitted error is sufficient to allow one to fix the problem. It's true that omitting -fcray-pointer from the arguments does give a more informative error, but I would have tried a lot of other things before getting to that as I am trying to compile code that depends on cray pointers. It would be much better if the informative error showing the actual location of the issue was emitted when using -fcray-pointer.
