public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8387: [3.3 regression] -finline-limit behavior changed; new inlining flags need doc Date: Tue, 11 Mar 2003 02:26:00 -0000 [thread overview] Message-ID: <20030311022601.12518.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8387; it has been noted by GNATS. From: Daniel Jacobowitz <drow@mvista.com> To: pfeifer@dbai.tuwien.ac.at, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, garloff@suse.de, dalej@apple.com Cc: Subject: Re: c/8387: [3.3 regression] -finline-limit behavior changed; new inlining flags need doc Date: Mon, 10 Mar 2003 21:24:01 -0500 The patch for this has been committed to the 3.3 branch and HEAD now, right? By this patch: 2003-03-06 Kurt Garloff <garloff@suse.de> Geoffrey Keating <geoffk@apple.com> Dale Johannesen <dalej@apple.com> * params.def: Introduce parameter max-inline-insns-rtl for a separate limit for the RTL inliner. * params.h: Likewise. * integrate.c (function_cannot_inline_p): Use it. * toplev.c (decode_f_option): Set multiple parameters controlling inlining with -finline-limit. * params.def: Fix orthographic and typographic errors. * doc/invoke.texi: Document parameters controlling inlining and the way -finline-limit sets multiple of them. * tree.h (struct tree_decl): Introduce inlined_function_flag, recording whether the function became eligible for inlining by a compiler flag rather than the declaration. Provide DID_INLINE_FUNC macro to access it. * c-decl.c (grokdeclarator): Set DID_INLINE_FUNC. * cp/decl.c (grokfndecl): Likewise. * toplev.c (rest_of_compilation): Likewise. * cp/optimize (maybe_clone_body): Copy DID_INLINE_FUNC. * print-tree.c (print_node): Report it. * params.def: Introduce new max-inline-insns-auto limit. * params.h: Likewise. * tree-inline.c (inlinable_function_p): Apply it to functions with DID_INLINE_FUNC set. * toplev.c (decode_f_option): Initialize it from -finline-limit value. * doc/invoke.texi: Document new parameter. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-03-11 2:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-11 2:26 Daniel Jacobowitz [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-11 5:01 drow 2003-03-11 2:46 Dale Johannesen 2003-02-22 21:24 ebotcazou 2003-02-11 21:56 Steven Bosscher 2003-02-11 20:16 Steven Bosscher
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=20030311022601.12518.qmail@sources.redhat.com \ --to=drow@mvista.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).