gfortran links to bug lists

[Daniel Franke]

2007/7/19, Jerry DeLisle <jvdelisle@verizon.net>:
> > I find it a bit concerning that the focus has shifted so far to F2003
> > that I have had to resurrect my own Bugzilla lists.  Is this really what
> > we want to be doing right now?  If so, OK, I'll plough my own furrow but
> > I'd rather that we all pulled together.
>
> I agree we need to focus on the bug list.

Are there any features and corner cases of F95 that are not
implemented yet? Do we have any means to track the overall progress?


> > What do you all think?  Am I wasting my energy or are others also
> > committed to a systematic development of gfortran?
>
> I don't have many words to offer here.  All I know is that I am focusing on
> the bugs that I can.

I think, this summarizes the current efforts for most of us. It's
definitely the same for me, browse bugzilla and take a pick.
Obviously, the easy ones are picked first, but no one will touch the
more involved ones.


> Maybe we should take a month and focus a few of us on one area and see what
> we can do.  I am OK with that.

How about "Bug of the week/month"? A maintainter picks one of the
longstanding bugs most shy away from and we try to get rid of it
together in a focused effort. A first proposal for this could be
PR29606 (Derived type I/O should have been handled via the frontend).
Paul writes:

"This is a general problem for gfortran.  A pointer to a component of an array
of derived types cannot, at the moment be represented. Some brave soul need to
come up with a proposal as to how to do it and then to change every single
client for array descriptors in gfortran.  I periodically contemplate how to do
it and recoil in horror at the size of the job."

If this is done, PR30625 (Array pointers to components of derived type
arrays do not work) should be fixed easily as well?

Just my thoughts.

Regards
     Daniel

-- 
82megaohm.de, 82 Mio. – Und einer ist durchgebrannt ...