Strange behaviour when using type(*) and character(*) in GFortran

[everythingfunctional]

@Carltoffel

Do you mean that it is against the standard to pass an unallocated variable as an actual argument to a dummy argument that is neither allocatable nor optional?

Correct. If it worked with gfortran I would say it was coincidental, and that turning on certain run-time checking may have flagged it. Sounds like an interesting use case though.