public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: fkaufman@ee.ethz.ch, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, sensorflo@bigfoot.com
Subject: Re: optimization/10500: despite -Winline no warnings emited
Date: Fri, 25 Apr 2003 18:34:00 -0000	[thread overview]
Message-ID: <20030425183405.13817.qmail@sources.redhat.com> (raw)

Synopsis: despite -Winline no warnings emited

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Apr 25 18:34:04 2003
State-Changed-Why:
    Confirmed. Here's a self-contained testcase:
    -----------------------
    struct CFoo
    {
      int foo(int i);
      inline int foo_inline1(int sw, int i);
    };
    
    inline int CFoo::foo_inline1( int sw, int i )
    {
      switch (sw)
        {
          case 0: return i;
          case 10: return i*2;
          case 20: return i+3;
          case 30: return i^4;
          case 40: return i%4;
          case 50: return i*i;
          case 60: return i-i*2;
          case 70: return i*8;
          case 80: return i/44;
          case 90: return i*100;
        }
      return 0;
    }
    
    int CFoo::foo( int i )
    { return foo_inline1(40, i);
    }
    ---------------------------------
    The assembler output still contains the call to
    foo_inline1, up to present 3.4. It's arguable if the
    fact that it is not inlined is a bug, but it should at
    least warn if -Winline is given -- the latter doesn't
    happen.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10500


             reply	other threads:[~2003-04-25 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 18:34 bangerth [this message]
2003-04-29  7:57 steven

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=20030425183405.13817.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=fkaufman@ee.ethz.ch \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=sensorflo@bigfoot.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).