public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wouter dot vermaelen at scarlet dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/32492]  New: attribute always_inline  ->  sorry, unimplemented: recursive inlining
Date: Mon, 25 Jun 2007 10:01:00 -0000	[thread overview]
Message-ID: <bug-32492-8535@http.gcc.gnu.org/bugzilla/> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]

> cat bug.ii
__attribute__((always_inline)) void f1() {}
__attribute__((always_inline)) void f2(char) {}
void f3() { f1(); f2(0); }

> g++ bug.ii
bug.ii: In function ‘void f3()’:
bug.ii:2: sorry, unimplemented: inlining failed in call to ‘void f2(char)’:
recursive inlining
bug.ii:3: sorry, unimplemented: called from here


-- 
           Summary: attribute always_inline  ->  sorry, unimplemented:
                    recursive inlining
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: wouter dot vermaelen at scarlet dot be


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


             reply	other threads:[~2007-06-25 10:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 10:01 wouter dot vermaelen at scarlet dot be [this message]
2007-06-26 10:32 ` [Bug c++/32492] [4.3 Regression] " rguenth at gcc dot gnu dot org
2007-06-26 15:16   ` Daniel Jacobowitz
2007-06-26 12:14 ` mark at codesourcery dot com
2007-06-26 14:31 ` pinskia at gcc dot gnu dot org
2007-06-26 14:39 ` [Bug c/32492] " pinskia at gcc dot gnu dot org
2007-06-26 14:51 ` pinskia at gcc dot gnu dot org
2007-06-26 14:53 ` [Bug middle-end/32492] " pinskia at gcc dot gnu dot org
2007-06-26 15:03 ` rguenther at suse dot de
2007-06-26 16:30 ` drow at gcc dot gnu dot org
2007-06-26 20:46 ` rguenth at gcc dot gnu dot org
2007-06-26 21:07 ` rguenth at gcc dot gnu dot org
2007-06-26 21:25 ` rguenth at gcc dot gnu dot org
2007-06-26 21:33 ` pinskia at gcc dot gnu dot org
2007-06-26 21:55 ` rguenther at suse dot de
2007-06-26 21:59   ` Andrew Pinski
2007-06-26 21:59 ` pinskia at gmail dot com
2007-06-27 14:01 ` rguenth at gcc dot gnu dot org
2007-06-27 15:05 ` rguenth at gcc dot gnu dot org
2008-06-11 10:07 ` josep dot m dot perez at bsc dot es
2008-06-16  9:24 ` josep dot m dot perez at bsc dot es

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=bug-32492-8535@http.gcc.gnu.org/bugzilla/ \
    --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).