Re: Ping: bug report 18108

[Carsten Lemmen <c dot lemmen at fz-juelich dot de>]

Hi all,

probably everyone has a bug which (s)he likes to get fixed soon.
I'd vote for PR 15809 which has been open since June and is obstructing 
me from further testing my source with gfortran.

Well, there are bugs which you can get around by circumventing it in 
your code (works in 50% of my open bugs) and there are others (like 
Martin's and the above 15809) where you can't do anything but wait it 
out till some more knowledgeable people (btw. I'm always amazed and I 
appreciate you guy's work very much, thanks!) get around to fixing it.

That raises two questions:

1) would it be good to have bug voting enabled for the fortran 
development? (I don't have an opinion on that)

2) Wouldn't it be great to comment on whether the bug is hindering you 
from testing further or whether it is just not working with original 
code (however, can be circumvented).  A blocking bug could then receive 
more attention


.... and those who can't fix gfortran themselves can go about testing 
and testing and testing ....

Cheers,
Carsten


Martin Reinecke wrote:
> Hi all,
>
> I'd like to bring the Fortran bug report #18108 (overloading does not
> work for functions) to your attention. I reported this bug about a month
> ago, and it appears to have bitten at least two other people in the 
> meantime.
> Unlike all other bugs I have reported so far, it has not been confirmed yet
> by anyone.
> This problem prohibits me from compiling my Fortran sources with gfortran,
> and consequently from submitting more bug reports for gfortran (or 
> confirming
> that it works flawlessly :).
> Please don't get me wrong: I don't want to complain that the bug is not 
> yet fixed.
> I'm just a bit worried that there is an apparent lack of interest in 
> this quite
> significant (I think) problem.
> That said, if I can be of any help with this thing, please let me know!
>
> Cheers,
>   Martin

-