public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Bradley Lucier <lucier@math.purdue.edu>,
	       Bernd Schmidt <bschmidt@redhat.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Make disabled-optimization warning more informative; increase default max-gcse-memory
Date: Thu, 12 Nov 2015 22:28:00 -0000	[thread overview]
Message-ID: <56451284.901@redhat.com> (raw)
In-Reply-To: <5644C797.8010107@math.purdue.edu>

On 11/12/2015 10:08 AM, Bradley Lucier wrote:
> On 11/12/2015 11:57 AM, Bernd Schmidt wrote:
>>> The expanded warning allowed me to see how much memory really was needed
>>> to apply gcse to some of my routines, and 128MB fixes my problem.  The
>>> limit has been 50MB for over 10 years, I think we can up it a bit now.
>>>   {
>>> +  unsigned int memory_request = n_basic_blocks_for_fn (cfun)
>>> +    * SBITMAP_SET_SIZE (max_reg_num ())
>>> +    * sizeof (SBITMAP_ELT_TYPE);
>>> +
>>
>> Formatting (wrap in parens to get it indented).
>
> Fixed.
>
>>
>> Otherwise ok.
>
> Thanks.
>
> Here's the reformatted patch (but without retesting).
>
> I don't have check-in privileges.
>
> Brad
>
>      * gcc/cprop.c (is_too_expensive): Remove.
>      (gcse.h): Include.
>      (one_cprop_pass): Call gcse_or_cprop_is_too_expensive, not
>      is_too_expensive.
>      * gcc/gcse.h (gcse_or_cprop_is_too_expensive): Declare.
>      * gcc/gcse.c (is_too_expensive): Rename to ...
>      (gcse_or_cprop_is_too_expensive): ... this.
>      Expand warning to add required size of max-gcse-memory.
>      (one_pre_gcse_pass): Use it.
>      (one_code_hoisting_pass): Use it.
>      * gcc/params.def (max-gcse-memory): Increase from 50MB to 128MB.
Committed on your behalf.

jeff

      parent reply	other threads:[~2015-11-12 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 16:44 Bradley Lucier
2015-11-12 16:57 ` Bernd Schmidt
2015-11-12 17:08   ` Bradley Lucier
2015-11-12 21:12     ` Bradley Lucier
2015-11-12 22:28     ` Jeff Law [this message]

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=56451284.901@redhat.com \
    --to=law@redhat.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lucier@math.purdue.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).