From: Jerry DeLisle <jvdelisle@charter.net>
To: 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 82567
Date: Wed, 18 Oct 2017 01:14:00 -0000 [thread overview]
Message-ID: <afe7ba93-48ee-87ea-bd6b-d25a97d9f6a1@charter.net> (raw)
In-Reply-To: <359f2531-46d3-b2ce-666b-1267d28c1303@netcologne.de>
On 10/17/2017 03:36 PM, Thomas Koenig wrote:
> Hello world,
>
> this patch fixes a regression with long compile times,
> which came about due to our handling of array constructors
> at compile time. This, togeteher with a simplification in
> front end optimization, led to long compile times and large
> code.
>
> Regression-tested. OK for trunk and the other affected branches?
>
Well I know 42 is the answer to the ultimate question of the universe so this
must be OK. I just don't know what the question is.
OK and thanks,
Jerry
+#define CONSTR_LEN_MAX 42
+
next prev parent reply other threads:[~2017-10-18 1:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 22:36 Thomas Koenig
2017-10-18 1:14 ` Jerry DeLisle [this message]
2017-10-18 2:05 ` Steve Kargl
2017-10-18 11:40 ` Mikael Morin
2017-10-18 21:32 ` Thomas Koenig
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=afe7ba93-48ee-87ea-bd6b-d25a97d9f6a1@charter.net \
--to=jvdelisle@charter.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--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).