public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/24947] -Os should maximize inlining --param values.
Date: Mon, 21 Nov 2005 16:07:00 -0000	[thread overview]
Message-ID: <20051121160700.32250.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24947-8546@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from pinskia at gcc dot gnu dot org  2005-11-21 16:06 -------
(In reply to comment #7)
I'm pretty sure that if you run a poll of all the C++
> programmers, they'll tell you that they expect the former to always be inlined
> in an optimized build, while the latter ought to depend on some specific
> command-line parameters. 

Depends on which C++ developers and if they have really thought about all their
uses of inline (most have not even though they say they want functions declared
as inline to be inlined)?

Also there are examples of where respecting inline will just cause the compiler
to use so much memory/compile time is not funny.  An example is PR 8361.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24947


  parent reply	other threads:[~2005-11-21 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  0:58 [Bug c++/24947] New: " msharov at hotmail dot com
2005-11-20  1:31 ` [Bug c++/24947] " pinskia at gcc dot gnu dot org
2005-11-21  1:36 ` [Bug middle-end/24947] " pinskia at gcc dot gnu dot org
2005-11-21 15:07 ` msharov at hotmail dot com
2005-11-21 15:19 ` rearnsha at gcc dot gnu dot org
2005-11-21 15:35 ` msharov at hotmail dot com
2005-11-21 15:49 ` rearnsha at gcc dot gnu dot org
2005-11-21 16:01 ` msharov at hotmail dot com
2005-11-21 16:07 ` pinskia at gcc dot gnu dot org [this message]
2005-11-21 16:25 ` msharov at hotmail dot com
2006-08-21  5:35 ` pinskia at gcc dot gnu dot org
2006-08-21 12:45 ` hubicka at gcc dot gnu dot org

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=20051121160700.32250.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).