From: Andrew Benson <abenson@carnegiescience.edu>
To: sgk@troutmask.apl.washington.edu
Cc: Richard Biener <richard.guenther@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Optimization of add_dt_to_dt_list() in resolve.c
Date: Wed, 30 May 2018 18:37:00 -0000 [thread overview]
Message-ID: <6792787.IJseq7gilL@andrew-precision-3520> (raw)
In-Reply-To: <20180530182541.GA93366@troutmask.apl.washington.edu>
On Wednesday, May 30, 2018 11:25:41 AM PDT Steve Kargl wrote:
> On Wed, May 30, 2018 at 10:01:12AM -0700, Andrew Benson wrote:
> > On Wednesday, May 30, 2018 11:43:58 AM PDT Richard Biener wrote:
> > > On Tue, May 29, 2018 at 10:24 PM Andrew Benson
> > > <abenson@carnegiescience.edu>> >
> > > wrote:
> > > > Yes - definitely possible to remove gfc_dt_list entirely - new patch
> > > > is
> > > > attached.
> > >
> > > This looks good to me but it still requires review/ack from fortran
> > > people.
> >
> > Thanks - I'll wait on input from the fortran devs.
>
> You and Richard were having what appeared to be a productive
> exchange, so I thought I would sit on the side and let it
> reach a conclusion. I'll take a look at what you've done
> this weekend. Hopefully, others can also cast an eye over
> the patch as well.
Thanks - greatly appreciated!
> PS: Welcome to the wonderful wonder of gfortran hacking.
I suspect this is a slippery slope.... but so far it's been fun and
instructive for me at least!
-Andrew
--
* Andrew Benson: http://users.obs.carnegiescience.edu/abenson/contact.html
* Galacticus: https://bitbucket.org/abensonca/galacticus
next prev parent reply other threads:[~2018-05-30 18:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 22:53 Andrew Benson
2018-05-25 7:06 ` Richard Biener
2018-05-25 7:13 ` Richard Biener
2018-05-25 21:54 ` Andrew Benson
2018-05-28 9:54 ` Richard Biener
2018-05-29 20:25 ` Andrew Benson
2018-05-30 9:44 ` Richard Biener
2018-05-30 17:01 ` Andrew Benson
2018-05-30 18:25 ` Steve Kargl
2018-05-30 18:37 ` Andrew Benson [this message]
2018-05-30 20:43 ` Janus Weil
2018-05-30 22:22 ` Andrew Benson
2018-05-31 8:56 ` Janus Weil
2018-05-31 18:04 ` Andrew Benson
2018-06-01 6:14 ` Janus Weil
2018-06-11 18:45 ` Steve Kargl
2018-06-11 19:22 ` Andrew Benson
2018-06-14 5:15 ` Andrew Benson
2018-06-15 0:12 ` Steve Kargl
2018-06-15 7:59 ` Andrew Benson
2018-07-11 2:33 ` Andrew Benson
2018-07-20 16:29 ` Andrew Benson
2018-07-20 18:59 ` Janus Weil
2018-07-20 19:02 ` Andrew Benson
2018-07-20 19:10 ` Janus Weil
2018-07-20 20:04 ` Janus Weil
2018-07-20 20:22 ` Andrew Benson
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=6792787.IJseq7gilL@andrew-precision-3520 \
--to=abenson@carnegiescience.edu \
--cc=fortran@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/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).