public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: sgk@troutmask.apl.washington.edu, Jerry DeLisle <jvdelisle@charter.net>
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 82567
Date: Wed, 18 Oct 2017 11:40:00 -0000	[thread overview]
Message-ID: <cd3bc276-f315-1641-c784-0c77b9268d0e@orange.fr> (raw)
In-Reply-To: <20171018020506.GA4048@troutmask.apl.washington.edu>

Le 18/10/2017 à 04:05, Steve Kargl a écrit :
> On Tue, Oct 17, 2017 at 06:14:16PM -0700, Jerry DeLisle wrote:
>> 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
> 
> Actually, I was wondering about the choice myself.  With
> most common hardware having fairly robust L1 and L2 cache
> sizes, a double precision array constructor with 42
> elements only occupies 336 bytes.  Seems small.
> 
There is a -fmax-array-constructor=n option. Can’t we use it for the limit?

  reply	other threads:[~2017-10-18 11:40 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
2017-10-18  2:05   ` Steve Kargl
2017-10-18 11:40     ` Mikael Morin [this message]
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=cd3bc276-f315-1641-c784-0c77b9268d0e@orange.fr \
    --to=morin-mikael@orange.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    --cc=sgk@troutmask.apl.washington.edu \
    --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).