public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Andi Kleen <ak@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: Inlining (was: GCC 3.3 release criteria)
Date: Wed, 26 Feb 2003 13:58:00 -0000	[thread overview]
Message-ID: <m3hear6yzj.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20030226114740.GA18775@wotan.suse.de>

Andi Kleen <ak@suse.de> writes:

| > | forces -Werror -Winline
| > 
| > Why so?
| 
| always_inline errors when the function cannot get inlined.

Thanks for the education and your patience.

But then if -fobey-inline doesn't error then there is something about it?

Matt, what does happen when a function can't be inlined?

-- Gaby

  reply	other threads:[~2003-02-26 11:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F0B5E2D8-48EA-11D7-A0F6-00039390D9E0@apple.com.suse.lists.egcs>
     [not found] ` <m3wujn90fs.fsf@uniton.integrable-solutions.net.suse.lists.egcs>
     [not found]   ` <20030226044029.A1163@kerberos.ncsl.nist.gov.suse.lists.egcs>
     [not found]     ` <m3isv78gp7.fsf@uniton.integrable-solutions.net.suse.lists.egcs>
2003-02-26 11:47       ` Andi Kleen
2003-02-26 11:53         ` Gabriel Dos Reis
2003-02-26 13:44           ` Andi Kleen
2003-02-26 13:58             ` Gabriel Dos Reis [this message]
2003-02-26 21:50               ` Matt Austern
2003-02-26 22:04                 ` Andi Kleen
2003-02-24 20:33 GCC 3.3 release criteria Andi Kleen
2003-02-25  0:54 ` Inlining (was: GCC 3.3 release criteria) Matt Austern
2003-02-25  6:43   ` Tolga Dalman
2003-02-25 18:01     ` Matt Austern
2003-02-25 19:51       ` Tolga Dalman
2003-02-25 20:47       ` Michel LESPINASSE
2003-02-25 21:22       ` Timothy J. Wood
2003-02-26  4:29       ` Gabriel Dos Reis
2003-02-26 10:10         ` Olivier Galibert
2003-02-26 11:05           ` Gabriel Dos Reis
2003-02-27 15:26             ` Allan Sandfeld
2003-02-25  8:09   ` Steven Bosscher
2003-02-25  8:31   ` Andi Kleen

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=m3hear6yzj.fsf@uniton.integrable-solutions.net \
    --to=gdr@integrable-solutions.net \
    --cc=ak@suse.de \
    --cc=gcc@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).