From: "Joel Soete" <jsoe0708@tiscali.be>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: g++ (3.3): ...Error: Field out of range
Date: Thu, 19 Jun 2003 19:27:25 +0200 [thread overview]
Message-ID: <3ED70CF100007B7A@ocpmta2.freegates.net> (raw)
In-Reply-To: <200306191540.h5JFeWGN021982@hiauly1.hia.nrc.ca>
Hey Dave,
> Putting me on the CC list of the PR would be appreciated.
May be have you already recieved this:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11254
[...]
> These are the options that provide detailed control for inlining:
>
> --param max-inline-insns-rtl=<value> The maximum number of instructions
for
> the RTL inliner
> --param min-inline-insns=<value> The number of instructions in a
single
> functions still eligible to inlining after a lot recursive inlining
> --param max-inline-slope=<value> The slope of the linear function
> throttling inlining after the recursive inlining limit has been reached
is
> given by the negative reciprocal value of this parameter
> --param max-inline-insns=<value> The maximum number of instructions
by
> repeated inlining before gcc starts to throttle inlining
> --param max-inline-insns-auto=<value> The maximum number of instructions
> when automatically inlining
> --param max-inline-insns-single=<value> The maximum number of instructions
> in a single function eligible for inlining
> The RTL is not used by C or C++ anymore. Look in the GCC file params.def
> for the defaults and discussion. I think reducing PARAM_MAX_INLINE_INSNS
> from its default of 600 to something in the range of 200-300, or less will
> help. You might also make the slope more aggressive. I know that changes
> are needed to build LyX (see <http://gcc/gnu.org/PR?10160>).
Ah, in fact I well read it also but do not figure out because of man comment:
"max-inline-insns
If an function contains more than this many instructions, it
will not be inlined. This option is precisely equivalent to
-finline-limit.
"
Anyway, I try 300, 200, 100 and stop at 50 without any more success :-(
(I can still try lower?)
Thanks again for all,
Joel
---------------------------------
Tiscali ADSL: 19,50 euros/mois...abonnez-vous sur www.tiscali.be
next prev parent reply other threads:[~2003-06-19 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 7:08 [parisc-linux] g++ (3.3): ...Error: Field out of range Joel Soete
2003-06-17 15:08 ` [parisc-linux] " John David Anglin
2003-06-18 11:55 ` Joel Soete
2003-06-18 15:12 ` John David Anglin
2003-06-18 16:38 ` Joel Soete
2003-06-18 17:12 ` John David Anglin
2003-06-19 13:27 ` Joel Soete
2003-06-19 15:40 ` John David Anglin
2003-06-19 17:27 ` Joel Soete [this message]
2003-06-19 17:48 ` John David Anglin
2003-06-20 5:47 ` Joel Soete
2003-06-20 6:49 ` Joel Soete
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=3ED70CF100007B7A@ocpmta2.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/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