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: Fri, 20 Jun 2003 08:49:00 +0200 [thread overview]
Message-ID: <3ED71F6D00007732@ocpmta7.freegates.net> (raw)
In-Reply-To: <3ED71F6D000076F1@ocpmta7.freegates.net>
Hello again Dave,
> > 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 equival
>nt to
> > -finline limit.
> > "
> >
> > Anyway, I try 300, 200, 100 and stop at 50 without any more success :-(
> > (I can still try lower?)
>
Could it be different in 3.3? I try with 5 and no success but...
> Actually, I see that the `v
>l' from -finline-limit sets the parameters
> as follows in 3.4:
>
> set_param_value ("max-inline-insns", val);
> set_param_value ("max-inline-insns-single", val/2);
> set_param_value ("max-inline-insns-auto", val/2);
> set
>param_value ("max-inline-insns-rtl", val);
> if (val/4 < MIN_INLINE_INSNS)
> {
> if (val/4 > 10)
> set param_value ("min-inline-insns", val/4);
> else
> set_param_value ("min-inline-insns", 10);
> }
>
> You might also try
>-fno-default-inline and -fno-inline, but it's
> looking as if inlining isn't the driving factor in the size of
> the routine.
Yes the inlining is one factor:
The first works (see <http://lists.parisc-linux.org/pipermail/parisc-linux/2003-June/0
>0202.html>
;) and certainly the second too;
but also a better news:
(I definitely need to clean my glasses: in man default -finline-limit=600)
and it so works with -finline-limit= something between 350 (works) and 400
(failled). Now I am curio
>s to see the differences between --param and this
-finline-limit (if i have some time)?
===
Sorry to reply to myself but I continue my test and reading again gcc man
(well all gcc-3.0, -3.2 and -3.3 are installed on this box and I would also
have to prefer to read man -l /usr/share/man/man1/gcc-3.3.1.gz).
And also re-reading <http://gcc.gnu.org/PR?10160>
--param max-inline-insns=180 ... 5 # :( it fails
but otc
--param max-inline-insns-single=180 # ;) it works also (even if compile time
is
long versus -finline-limit=300)
So looks like very much PR=10160 excepted that here it is not only a performance
pb but also a failure of compilation.
Thanks for you understand,
Joel
ps: sorry also for bad quoting (pb with isp webmail)
---------------------------------
Tiscali ADSL: 19,50 euros/mois...abonnez-vous sur www.tiscali.be
prev parent reply other threads:[~2003-06-20 6:49 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
2003-06-19 17:48 ` John David Anglin
2003-06-20 5:47 ` Joel Soete
2003-06-20 6:49 ` Joel Soete [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=3ED71F6D00007732@ocpmta7.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