From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Fix PR 89174, segfault on allocate with MOLD
Date: Sun, 24 Feb 2019 20:08:00 -0000 [thread overview]
Message-ID: <20190224175024.GA26240@troutmask.apl.washington.edu> (raw)
In-Reply-To: <CAGkQGiJ9s9fr5uqq95wJsd=43nDw1_w4cyaJ8-XvU8GWpKWE8Q@mail.gmail.com>
On Sun, Feb 24, 2019 at 05:42:14PM +0000, Paul Richard Thomas wrote:
>
> > Of course, there could also be a more profound way of fixing this
> > bug :-)
>
> I wish that it were the case. I am unable to decide whether the design
> choices made for an F95 compiler have cause the add-ons to be
> intrinsically complicated or whether or whether F2018, extensions and
> legacy support is the cause of the complexity - probably both. Either
> way, profundity is rarely to be found in bugfixes.
>
flang project was going to port PGI's frontend to use llvm as
it middle/backend. A part of the port was to update PGI bits
to include modern Fortran. The flang developers have decided
to write an entirely new, from scratch, frontend. My conclusion
is our 15+ year-old decisions and the addition of newer features
(both modern Fortran and legacy) have complicated parts of the
compiler to an almost unmanageable state. You can probably
appreciate this better than most of us.
--
Steve
next prev parent reply other threads:[~2019-02-24 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 14:27 Thomas Koenig
2019-02-24 18:54 ` Paul Richard Thomas
2019-02-24 20:08 ` Steve Kargl [this message]
2019-02-25 15:05 Dominique d'Humières
2019-02-25 18:22 ` Thomas Koenig
2019-02-25 19:19 ` Steve Kargl
2019-02-25 21:58 ` Thomas König
2019-02-25 22:28 ` Steve Kargl
2019-02-25 22:45 ` Steve Kargl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190224175024.GA26240@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=tkoenig@netcologne.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).