public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "josep dot m dot perez at bsc dot es" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/36631]  New: [4.3 Regression] attribute always_inline  ->  sorry, unimplemented: recursive inlining
Date: Wed, 25 Jun 2008 17:08:00 -0000	[thread overview]
Message-ID: <bug-36631-16302@http.gcc.gnu.org/bugzilla/> (raw)

The following code generates a recursive inlining error in 4.3.[01] while it
did not in 4.[12]. Somehow, the bug requires having both always_inline
attributes.


template<typename T>
struct B {
        struct C {
                __attribute__((always_inline)) C(C const &c)
                {
                }
        };
        void __attribute__((always_inline)) g(C c)
        {
        }
};

void trigger(B<int> b, B<int>::C c)
{
        b.g(c);
}


Cleanup4.ii: In function 'void trigger(B<int>, B<int>::C)':
Cleanup4.ii:8: sorry, unimplemented: inlining failed in call to 'void
B<T>::g(B<T>::C) [with T = int]': recursive inlining
Cleanup4.ii:15: sorry, unimplemented: called from here


-- 
           Summary: [4.3 Regression] 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: josep dot m dot perez at bsc dot es
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2008-06-25 17:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 17:08 josep dot m dot perez at bsc dot es [this message]
2008-07-04 21:50 ` [Bug c++/36631] [4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-07-10 14:24 ` [Bug tree-optimization/36631] " rguenth at gcc dot gnu dot org
2008-07-31 14:45 ` hubicka at gcc dot gnu dot org
2008-08-07 15:26 ` rguenth at gcc dot gnu dot org
2008-08-27 22:10 ` jsm28 at gcc dot gnu dot org
2008-09-15 14:28 ` rguenth at gcc dot gnu dot org
2008-09-15 14:38 ` [Bug c++/36631] " rguenth at gcc dot gnu dot org
2008-10-21 12:16 ` jakub at gcc dot gnu dot org
2008-11-04 16:05 ` jakub at gcc dot gnu dot org
2008-11-04 16:45 ` jakub at gcc dot gnu dot org
2008-11-20  1:50 ` jakub at gcc dot gnu dot org
2008-11-20  1:52 ` [Bug c++/36631] [4.3 " jakub at gcc dot gnu dot org
2009-01-24 10:25 ` rguenth at gcc dot gnu dot org
2009-08-04 12:41 ` rguenth at gcc dot gnu dot org
2010-05-22 18:25 ` rguenth 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=bug-36631-16302@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).