public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Dale Johannesen <dalej@apple.com>, Kurt Garloff <garloff@suse.de>
Cc: Mike Stump <mrs@apple.com>,
	Denys Duchier <Denys.Duchier@ps.uni-sb.de>, <gcc@gcc.gnu.org>
Subject: Re: abysmal code generated by gcc 3.2
Date: Tue, 22 Oct 2002 06:03:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0210221049210.20702-100000@wotan.suse.de> (raw)
In-Reply-To: <DEF57036-E52B-11D6-8BE6-000393D76DAA@apple.com>

Hi,

On Mon, 21 Oct 2002, Dale Johannesen wrote:

> >> uh? except for max-inline-insns, I never heard of the others.  Are
> >> these new (and what do they mean? - is that maybe documented in CVS).
> >
> > I'll assume all of these are documented in the manual,
>
> No, they are not.  Perhaps the patch that added them
>
> 2002-04-27  Kurt Garloff <garloff@suse.de>
>
>          * tree-inline.c (inlinable_function_p): Improve heuristics
>          by using a smoother function to cut down allowable inlinable
> size.
>          * param.def: Add parameters max-inline-insns-single,
>          max-inline-slope, min-inline-insns that determine the exact
>          shape of the above function.
>          * param.h: Likewise.
>
> should be reverted until this is fixed.

A little bit too harsh I would say.  The documentation (which Kurt wrote)
just wasn't committed for some reason (I believe another person than Kurt
actually committed the patch on Kurt's behalf).

> (-fmax-inline-insns was broken at the same time so that it no longer
> works to increase the size limit.)


Ciao,
Michael.

  reply	other threads:[~2002-10-22  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  0:56 Denys Duchier
2002-10-21  7:37 ` Fergus Henderson
2002-10-21  8:48   ` Denys Duchier
2002-10-21 12:59 ` Mike Stump
2002-10-21 15:07   ` Denys Duchier
2002-10-21 15:12     ` Fergus Henderson
2002-10-21 15:37     ` Mike Stump
2002-10-21 16:06       ` Dale Johannesen
2002-10-22  6:03         ` Michael Matz [this message]
2002-10-22  8:30           ` Kurt Garloff
2002-10-22 11:29           ` Dale Johannesen
2002-10-21 18:43 ` Denys Duchier
2002-10-22  3:56   ` Richard Henderson
     [not found] <20021021142058.25276.qmail@web21104.mail.yahoo.com>
2002-10-21 10:29 ` Denys Duchier
2002-10-21 10:47   ` Joe Wilson
2002-10-21 11:01 Joe Wilson

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=Pine.LNX.4.33.0210221049210.20702-100000@wotan.suse.de \
    --to=matz@suse.de \
    --cc=Denys.Duchier@ps.uni-sb.de \
    --cc=dalej@apple.com \
    --cc=garloff@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@apple.com \
    /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).