Bug reports

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug reports

Steve Kargl
The good news:

  According the gfortran wiki, we have fixed 213 bugs since
  the beginning of the year; and more importantly, only
  203 bugs have been reported!  This is also the first
  time in more than a year (if not longer) the total number
  of open bug reports (869) is below 870.  I have a patch
  submitted, which will bring us down to 868.

The bad news:

  There are still 869 open bug reports.

The real bad news (for gfortran users):

  A scan of the 869 open PRs shows that many/most of these
  are in areas of the compiler and the Fortran standard
  that I know zero about.  This means my time of fixing
  bugs is coming to a very slow pace (if not an end).  If
  you are a lurker on this list (or know someone) who
  depends on coarrays, OOP features, PDT, arcane option
  choices, etc, then you may want to get off the sidelines
  and help maintain the compiler.

--
Steve
Reply | Threaded
Open this post in threaded view
|

Re: Bug reports

NightStrike
On Sun, Aug 4, 2019, 12:08 PM Steve Kargl <[hidden email]>
wrote:

> The good news:
>
>   According the gfortran wiki, we have fixed 213 bugs since
>   the beginning of the year; and more importantly, only
>   203 bugs have been reported!  This is also the first
>   time in more than a year (if not longer) the total number
>   of open bug reports (869) is below 870.  I have a patch
>   submitted, which will bring us down to 868.
>
> The bad news:
>
>   There are still 869 open bug reports.
>
> The real bad news (for gfortran users):
>
>   A scan of the 869 open PRs shows that many/most of these
>   are in areas of the compiler and the Fortran standard
>   that I know zero about.  This means my time of fixing
>   bugs is coming to a very slow pace (if not an end).  If
>   you are a lurker on this list (or know someone) who
>   depends on coarrays, OOP features, PDT, arcane option
>   choices, etc, then you may want to get off the sidelines
>   and help maintain the compiler.
>
> --
> Steve
>

I hit one of those PDT bugs recently. I doubt I am capable of fixing it,
though I would be happy to help with testing.

>
Reply | Threaded
Open this post in threaded view
|

Re: Bug reports

Steve Kargl
On Sun, Aug 04, 2019 at 07:35:41PM -0400, NightStrike wrote:

> On Sun, Aug 4, 2019, 12:08 PM Steve Kargl <[hidden email]>
> wrote:
>
> > The real bad news (for gfortran users):
> >
> >   A scan of the 869 open PRs shows that many/most of these
> >   are in areas of the compiler and the Fortran standard
> >   that I know zero about.  This means my time of fixing
> >   bugs is coming to a very slow pace (if not an end).  If
> >   you are a lurker on this list (or know someone) who
> >   depends on coarrays, OOP features, PDT, arcane option
> >   choices, etc, then you may want to get off the sidelines
> >   and help maintain the compiler.
> >
>
> I hit one of those PDT bugs recently. I doubt I am capable of fixing it,
> though I would be happy to help with testing.
>

And, therein lies the problem.  You use a feature of the
language, which you clearly undestand, but are not motivated
to actual see that it works.

I have no need for PDTs nor anticipate that I'll ever need
PDTs, so have not motivation to care if PDTs work.

--
Steve
Reply | Threaded
Open this post in threaded view
|

Re: Bug reports

NightStrike
On Sun, Aug 4, 2019, 9:35 PM Steve Kargl <[hidden email]>
wrote:

> On Sun, Aug 04, 2019 at 07:35:41PM -0400, NightStrike wrote:
> > On Sun, Aug 4, 2019, 12:08 PM Steve Kargl <
> [hidden email]>
> > wrote:
> >
> > > The real bad news (for gfortran users):
> > >
> > >   A scan of the 869 open PRs shows that many/most of these
> > >   are in areas of the compiler and the Fortran standard
> > >   that I know zero about.  This means my time of fixing
> > >   bugs is coming to a very slow pace (if not an end).  If
> > >   you are a lurker on this list (or know someone) who
> > >   depends on coarrays, OOP features, PDT, arcane option
> > >   choices, etc, then you may want to get off the sidelines
> > >   and help maintain the compiler.
> > >
> >
> > I hit one of those PDT bugs recently. I doubt I am capable of fixing it,
> > though I would be happy to help with testing.
> >
>
> And, therein lies the problem.  You use a feature of the
> language, which you clearly undestand, but are not motivated
> to actual see that it works.
>
> I have no need for PDTs nor anticipate that I'll ever need
> PDTs, so have not motivation to care if PDTs work.
>
> --
> Steve
>

You have a much higher opinion of me and my skills than I do, so thank you
for that complement! :)

>
Reply | Threaded
Open this post in threaded view
|

Re: Bug reports

Steve Kargl
On Sun, Aug 04, 2019 at 09:58:33PM -0400, NightStrike wrote:

> On Sun, Aug 4, 2019, 9:35 PM Steve Kargl <[hidden email]>
> wrote:
>
> > On Sun, Aug 04, 2019 at 07:35:41PM -0400, NightStrike wrote:
> > > On Sun, Aug 4, 2019, 12:08 PM Steve Kargl <
> > [hidden email]>
> > > wrote:
> > >
> > > > The real bad news (for gfortran users):
> > > >
> > > >   A scan of the 869 open PRs shows that many/most of these
> > > >   are in areas of the compiler and the Fortran standard
> > > >   that I know zero about.  This means my time of fixing
> > > >   bugs is coming to a very slow pace (if not an end).  If
> > > >   you are a lurker on this list (or know someone) who
> > > >   depends on coarrays, OOP features, PDT, arcane option
> > > >   choices, etc, then you may want to get off the sidelines
> > > >   and help maintain the compiler.
> > > >
> > >
> > > I hit one of those PDT bugs recently. I doubt I am capable of fixing it,
> > > though I would be happy to help with testing.
> > >
> >
> > And, therein lies the problem.  You use a feature of the
> > language, which you clearly undestand, but are not motivated
> > to actual see that it works.
> >
> > I have no need for PDTs nor anticipate that I'll ever need
> > PDTs, so have not motivation to care if PDTs work.
> >
>
> You have a much higher opinion of me and my skills than I do, so thank you
> for that complement! :)
>

I did use some variation of the word "motivate" in 2 out
of 3 sentences.

I have no motivation to work on PDTs as I don't use them.

You have no movitation to help fix a feature within a tool
that you use.

--
Steve