From: Bernd Schmidt <bschmidt@redhat.com>
To: Bradley Lucier <lucier@math.purdue.edu>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Make disabled-optimization warning more informative; increase default max-gcse-memory
Date: Thu, 12 Nov 2015 16:57:00 -0000 [thread overview]
Message-ID: <5644C4F3.5030801@redhat.com> (raw)
In-Reply-To: <5644C1E0.7060307@math.purdue.edu>
> 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). Could also move the
initialization before the use.
Otherwise ok.
Bernd
next prev parent reply other threads:[~2015-11-12 16:57 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 [this message]
2015-11-12 17:08 ` Bradley Lucier
2015-11-12 21:12 ` Bradley Lucier
2015-11-12 22:28 ` Jeff Law
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=5644C4F3.5030801@redhat.com \
--to=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).